# US 2019/0378114 A1 · Method of managing an emergency mode transaction procedure, and an associated device

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0378114 A1
- Document ID: US20190378114A1
- Status: Published application
- Kind: A1
- Application number: 16/433,562
- Filed: 2019-06-06
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: Idemia France
- Applicants: Idemia France
- Inventors: Benoit MOUROUX; Aghiles ADJAZ
- Web page: https://patentgrep.com/patent/US20190378114A1

## CPC

- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06Q 20/3226: {Use of secure elements separate from M-devices}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/2048: {where the redundant components share neither address space nor persistent storage}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/327: {Short range or proximity payments by means of M-devices}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q 20/354: {Card activation or deactivation}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/401: {Transaction verification}
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04W 12/03: Protecting confidentiality, e.g. by encryption
- H04W 12/06: Authentication
- H04W 4/30: Services specially adapted for particular environments, situations or purposes
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method and device for managing an emergency procedure of an emergency transaction mode that can be activated in the event of a computer attack on or a failure of a transaction network. The method may be carried out by an electronic device suitable for performing a transaction in a normal mode or in the emergency mode. The method performs operations that may include receiving an activation command for activating the emergency mode procedure, where the command includes an identifier of the procedure and first encrypted data; verifying the activation command, which includes verifying the first encrypted data; and if verification of the command is successful, activating the emergency procedure.

## Claims

### Claim 1

A method of managing an emergency procedure of an emergency transaction mode that can be activated in the event of a computer attack on or a failure of a transaction network, the method being carried out by an electronic device suitable for performing a transaction in a normal mode or in the emergency transaction mode, said method comprising:
receiving an activation command for activating said emergency procedure, the activation command comprising an identifier of the emergency procedure and first encrypted data;
verifying the activation command, comprising verifying said first encrypted data;
if verification of the activation command is successful, activating the emergency procedure;
after activating the emergency procedure and after initializing a transaction between the electronic device and a reader, sending a message to said reader comprising a consultation request to consult a normal mode server of the transaction network; and
on receiving a message indicating that consultation of the normal mode server has failed, sending a cryptogram to said reader, the cryptogram comprising at least one information element about said emergency procedure.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the first encrypted data is an authentication code calculated as a function of a private key, said private key being obtained by using the identifier of said emergency procedure.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the verifying comprises verifying that the value of the identifier of said emergency procedure is greater than the value of a procedure identifier stored in the electronic device.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the at least one information element about said emergency procedure of the cryptogram comprises one or more of the following:
a starting date for said emergency procedure;
an ending date for said emergency procedure;
said identifier of said emergency procedure; and
an indication whereby said cryptogram was generated while carrying out said emergency procedure.

### Claim 5 (depends on 1)

The method according to claim 1, wherein said received message comprises a transaction date, and the emergency procedure comprises:
verifying that the transaction date lies between a starting date and an ending date for the emergency procedure; and
if the transaction date is earlier than the starting date or later than the ending date for the procedure, deactivating said emergency procedure.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the received message comprises the amount of the transaction, and the method further comprises:
incrementing a transaction number count;
incrementing a transaction amount count; and
if the incremented transaction number count is less than a transaction number threshold value and if the transaction amount count is less than a transaction amount threshold value, accepting the transaction.

### Claim 7 (depends on 1)

The method according to claim 1, further comprising: authenticating a user of the electronic device, and
wherein verifying the activation command is carried out only if the authenticating is successful.

### Claim 8 (depends on 1)

The method according to claim 1, further comprising deactivating said emergency procedure on receiving a deactivation command for deactivating said emergency procedure.

### Claim 9 (depends on 1)

An electronic device configured for carrying out the method according to claim 1.

### Claim 10

(canceled)

### Claim 11

A non-transitory computer readable data medium storing a computer program comprising instructions that, when executed by a processor of an electronic device, perform a method for managing an emergency procedure of an emergency transaction mode that can be activated in the event of a computer attack on or a failure of a transaction network, the method comprising:
receiving an activation command for activating the emergency procedure, the activation command comprising an identifier of the emergency procedure and first encrypted data;
verifying the activation command, including verifying the first encrypted data;
if verification of the activation command is successful, activating the emergency procedure;
after activating the emergency procedure and after initializing a transaction between the electronic device and a reader, sending a message to the reader, the message comprising a consultation request to consult a normal mode server of the transaction network; and
upon receiving a message indicating that consultation of the normal mode server has failed, sending a cryptogram to the reader, the cryptogram comprising at least one information element about said emergency procedure.
