01 CT54131EN51GLA1 One-EIR Product Overview

One-EIR Overview

One-EIR Overview

Contents One-EIR Overview 1 Definitions 1.1 Definition of an Equipment Identity Register 1.2 Definition of an IMEI 1.3 IMEI Lists held on the EIR 1.4 Position of the EIR in a 3GPP Network 1.5 EIR Functionality (GSM/UMTS) 1.6 EIR Functionality (LTE) 1.7 Legal Requirements for IMEI Validation 1.8 GSM Global IMEI Database 2 One-EIR Overview 2.1 One-EIR is NSN's EIR Product 2.2 One-EIR Architecture 2.3 One-EIR and Management Server 2.4 One-EIR and System Monitor 2.5 One-EIR Processing Overview 2.6 One-EIR Benefits 2.7 Check your understanding 3 Exercise 4 Solution

CT54131EN51GLA1 © Nokia Solutions and Networks 2015.

1 5 6 8 10 12 14 16 18 20 23 24 26 28 31 32 34 35 37 41

1

One-EIR Overview

CT54131EN51GLA1

2

© Nokia Solutions and Networks 2015.

One-EIR Overview

Learning Elements • • • • • •

Define an Equipment Identity Register Define the IMEI Describe the IMEI lists held on the EIR Introduce the One-EIR product from NSN Describe the architecture and interfaces of the One-EIR List the functions, features and benefits of the One-EIR

1

© Nokia Solutions and Networks 2015

Fig. 1


3

One-EIR Overview

CT54131EN51GLA1

4


One-EIR Overview

1

Definitions

Fig. 2


5

One-EIR Overview

1.1

Definition of an Equipment Identity Register

The Equipment Identification Register (EIR) is a core network application. It’s primary use is to prevent fraudulent use of handsets by maintaining lists of stolen and invalid devices (an invalid device for example may be a model of handset that is known to have a manufacturing defect). Fraud prevention is a legal requirement in some countries. A secondary use is to identify each handset used in the network. Operators can use this functionality to identify handset changes, and to trigger an external system to automatically send new configuration to devices as a result. The EIR uses the IMEI (International Mobile Equipment Identifier) to identify each device (e.g. a handset) that uses the operator’s network.

 The EIR is notified by the network of each IMEI that uses the network.  If an IMEI is listed as being stolen or invalid the EIR will block the handset from using the network. The IMEI and the EIR are defined in the GSM 3GPP standards including the following documents:

 3GPP Release 5 TS 23.003 Numbering, Addressing and Identification. This document covers the format of the IMEI.

 3GPP Release 5 TS 22.016 International Mobile station Equipment Identities. This document covers the use of the EIR.

 3GPP Release 5 TS 29.002 MAP Specification. This document covers the MAP Check IMEI message.

CT54131EN51GLA1

6


One-EIR Overview

Definition of an Equipment Identity Register • A core network component used to identify devices • Identifies and validates devices used in the network • Used for fraud prevention: – Maintains a list of stolen and invalid handsets – Blocks stolen and invalid handsets from using the network

• Used for device identification: – Identifies the device type (manufacturer and model) in use – Enables the operator to respond to device upgrades


1

Fig. 3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . . . . . . . . © Nokia . Solutions . . and . Networks . . .2015.. . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

7

One-EIR Overview

1.2

Definition of an IMEI

The International Mobile Equipment Identity (IMEI) identifies the make and model of a handset as well as identifying each handset. The IMEISV (International Mobile Equipment Identity and Software Version Number) is the IMEI format that has been in use since 2003. pre-2003 IMEI codes are being phased out and replaced by IMEISV. This training course refers to IMEI meaning both formats. TIP Type *#06# into phone to display the IMEI / IMEISV. Each IMEISV consists of :

 The Type Allocation Code (TAC): this is a combination of the Reporting Body ( a central body that issues the codes to handset manufacturers) and the Type Identifier. The TAC is used to identify the make and model of the handset. An EIR can block a handset if the TAC does not correspond to an approved type.

 The Serial Number: this is assigned to individual handsets by the manufacturer.  The Software Version: this identifies the software version number of the handset. The IMEI format prior to 2003 used a 6-digit TAC (Type Approval Code) followed by a 2-digit Final Assembly Code (FAC), which was a manufacturer-specific code indicating the location of the device’s construction.

CT54131EN51GLA1

8


One-EIR Overview

Definition of an IMEI • International Mobile Equipment Identity • Unique to every handset and 3G device (data card) – IMEI: 15 digit code (used prior to 2003) Type Allocation Code

Serial Number

Check Digit

8 digits

6 digits

1 digit

– IMEISV: 16 digit code (new format used since 2003)

Type Allocation Code

Serial Number

Software Version

8 digits

6 digits

2 digits


1

Fig. 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . . . . . . . . © Nokia Solutions and Networks 2015. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

9

One-EIR Overview

1.3

IMEI Lists held on the EIR

IMEI codes are flagged with a color on the EIR, corresponding to three different equipment statuses. The equipment status of a mobile phone determines whether it is allowed to use the network. Color lists:

 Any IMEI that is flagged as being on the black list will be blocked from using the network.

 Any IMEI that is flagged as being on the grey list will be allowed to use the network but will be monitored.

 The white list is the default value that any IMEI has if it is not flagged as black or grey listed. TIP In practice, operators do not keep an actual list of all IMEIs that are allowed to use the network because the list would be so large that it would be inefficient. Instead, any IMEI that is not on the black or grey list is assumed to be on the white list. If an IMEI is on the grey and the black list, the black list takes precedence and a black response will be returned.

CT54131EN51GLA1

10


One-EIR Overview

IMEI Lists Held on the EIR An EIR stores IMEI codes and their status There are three possible status values: • Black List – IMEI codes that are barred from using the network • Grey List – IMEI codes that are allowed to use the network but have their usage tracked by operators

• White List – IMEI codes that are allowed to use the network – In practice, most operators do not maintain white lists


1

Fig. 5


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

11

One-EIR Overview

1.4

Position of the EIR in a 3GPP Network

An EIR is part of the core network and is capable of providing service to the GSM, UMTS and LTE (long term evolution) networks. TIP Note that the One-EIR 5 release currently supports the GSM and UMTS networks only. The LTE network will be supported in the One-EIR 5.0 SP1 release. The basic call flow of the request:

 A subscriber turns on their handset or uses their handset.  Network entity (MSC, SGSN or MME) sends a request to the EIR. The request differs depending on the network: – Check IMEI (used by GSM and UMTS networks) – Identity Check Request (used by LTE and UMTS networks)

 EIR processes the request and responds.  MSC / SGSN / MME either allows network service to continue or blocks the handset, based on the response from the EIR.

CT54131EN51GLA1

12


One-EIR Overview


1

Fig. 6


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

13

One-EIR Overview

1.5

EIR Functionality (GSM/UMTS)

MSCs and SGSNs may send a CheckIMEI (possibly via a signaling transfer point, not shown) for a percentage of the following events depending on configuration at the MSC / SGSN:

 IMSI attach  Location Update  Mobile Originated calls and Mobile Terminated calls  SMS-Mobile Originated and SMS-Mobile Terminated TIP Note that the IMSI may also be present in the message if the MSC/SGSN is configured to provide it. The IMSI can be used for additional functionality on the EIR. The possible responses from the EIR are:

 checkIMEI Result provides list color (white, grey or black). A black response will disable the handset. A grey response may cause the MSC to carry out tracking if it is configured to do so.

 checkIMEI Error (one of the following): – Unknown Equipment (if IMEI not found). The SMC/SGSN can be configured to block handsets that return this status. This response will only be sent if the white list is being explicitly checked, In reality, operators assume an IMEI is white listed if it is not found on the black or grey lists, therefore this response is not likely to occur. – System Failure. A task cannot be performed because of a problem in another entity. – Unexpected Data Value. The data type is formally correct but its value or presence is unexpected in the current context.

CT54131EN51GLA1

14


One-EIR Overview

EIR Functionality (GSM/UMTS)

• The CheckIMEI is triggered by the MSC or SGSN • The EIR performs the CheckIMEI operation


1

Fig. 7


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

15

One-EIR Overview

1.6

EIR Functionality (LTE)

An MME (Mobile Management Entity) may send an ECR (Identity Check Request).

TIP Note that the IMSI may also be present in the message.

The possible responses from the EIR are:

 Identity Check Answer Success: provides list color (white, grey or black).  Identity Check Answer Error: Unknown Equipment (if IMEI not found).

CT54131EN51GLA1

16


One-EIR Overview

EIR Functionality (LTE)

• The Identity Check Operation is triggered by the MME • The EIR performs the Identity Check Operation


1

Fig. 8


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

17

One-EIR Overview

1.7

Legal Requirements for IMEI Validation

Fraud prevention is a legal requirement in some countries

 Prevents fraudulent use of stolen handsets  Designed to reduce handset crime Where there is a legal requirement, all operators within that country or region will share information via a centralized database:

 E.g. all operators in the UK share information about: –

Reported IMEIs (Black and Grey)

–

Newly manufactured IMEIs (White)

There is no legal requirement for operators to share information with operators in other regions

CT54131EN51GLA1

18


One-EIR Overview

Legal Requirements for IMEI Validation Fraud prevention is a legal requirement in some countries • Prevents fraudulent use of stolen handsets • Designed to reduce handset crime

Where there is a legal requirement, all operators within that country or region will share information via a centralised database: • E.g. all operators in the UK share information about: – Reported IMEIs (Black and Grey) – Newly manufactured IMEIs (White)

There is no legal requirement for operators to share information with operators in other regions © Nokia Solutions and Networks 2015

1

Fig. 9


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

19

One-EIR Overview

1.8

GSM Global IMEI Database

The GSM Association (GSMA) provides a service to network operators by acting as a global repository of type approved IMEI ranges and blacklisted IMEIs. This central IMEI database is known as the IMEI DB (previously CEIR) and is used by network operators to share blacklisted IMEIs with other operators in the same region or country. The concept of an IMEI and EIR are part of the original GSM specification. But the real world today is significantly different from the original vision Operators download only a national or regional subset of the IMEI DB data i.e. IMEIs that were reported by another network within that country or within a region in which operators share information. Operators can be reluctant to use an EIR. Typically it is national governments that mandate it. Governments are keen to reduce mobile theft crime, operators are keen to maximize subscriber counts and revenue. An operator can still charge for calls that are made from a stolen handset.

TIP Find more information about the IMEI DB:

 The GSM website www.gsmworld.com  Specific information about the IMEI DB http://www.gsmworld.com/our-work/programmes-and-initiatives/fraud-andsecurity/imei_database.htm

CT54131EN51GLA1

20


One-EIR Overview

GSM Global IMEI Database GSM Association maintains a global database of IMEI data to enable sharing of information • It is called the IMEI DB (previously called CEIR)

An operator may share IMEI data with the IMEI DB • Upload data about black and grey listed IMEIs from their own EIR • Download data about black and grey IMEIs that other operators uploaded

Each operator maintains their own EIR • The EIR can block handsets being used in the operator’s own network


1

Fig. 10


. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

21

One-EIR Overview

CT54131EN51GLA1

22


One-EIR Overview

2

One-EIR Overview

One-EIR Overview One-EIR

1


Fig. 11


23

One-EIR Overview

2.1

One-EIR is NSN's EIR Product

 MAP Release 5 and Release 6 Release 5 checkIMEI allows an IMSI to be provided in the User Information Field of the opening MAP message. This is used for IMEI and IMSI association and policing features.

 Proprietary Extensions Proprietary extensions allow the IMSI to be made available in the CheckIMEI message. This allows the subscriber’s IMSI to be used in other features. It is the method by which the IMSI and IMEI policing functionality is implemented.

 IMEI and IMSI association and policing (optional feature) This allows operators to check that the combination of IMSI and IMEI are valid and supports the blocking of handsets based on the IMSI status.

 Type Allocation Code (TAC) statistics The TAC defines the manufacturer and model of a handset.

 Handset inventory information Information is stored about handsets used in the network (manufacturer, model, screen resolution etc).

 IMEI Database Synchronization (optional feature) The EIR can exchange daily updates with the GSM Association’s IMEI Database.

 Selective Subscriber Handset Type Restriction The Operation can define sets of allowed and non-allowed handsets for subscribers. This functionality can be applied to subscriptions that include subsidized handsets to discourage early termination of the subscription package.

CT54131EN51GLA1

24


One-EIR Overview

One-EIR is NSN’s EIR Product

• Provides standard EIR functionality: – 3GPP-compliant Equipment Identity Register for GSM, UMTS and LTE networks – Support for MAP Release 5 and 6 – Supports White, Grey and Black lists to prevent fraud

• Additional key features: – – – – – –

Support for proprietary extensions IMSI/IMEI association and policing Type Allocation Code (TAC) statistics TAC handset inventory information IMEI Database synchronisation Selective Subscriber Handset Type Restriction © Nokia Solutions and Networks 2015

1

Fig. 12

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . Solutions . . and . Networks . . .2015.. © Nokia . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

25

One-EIR Overview

2.2

One-EIR Architecture

System architecture

 The One-EIR application and the One-NDS database are hosted on separate hardware.

 The separate One-NDS database can be distributed to increase storage capacity.  This type of implementation is suitable for larger operators, where the amount of data is already large or is expected to increase over time.

 With this architecture, the One-NDS database can be accessed by multiple applications, one of which is the One-EIR.

 This implementation is suitable if multiple applications are using the same data. Hardware:

 The EIR application (EIR Front End) is deployed on ATCA hardware running Red Hat Linux.

CT54131EN51GLA1

26


One-EIR Overview

One-EIR 5.0 ‘System’ Architecture


1

Fig. 13


. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

27

One-EIR Overview

2.3

One-EIR and Management Server

 Management Server (MS) is a web-based graphical user interface. It’s main purpose is to view and edit data that controls the behavior of the One-EIR application.

 MS user login access permissions determine which data can be viewed or edited.  MS capabilities: – View and update One-EIR and One-NDS configuration & control data. – Add, view, update and delete signaling link data. – Add, view, update and delete IMEI ranges. – Manage LDAP users for the One-NDS Directory. – Manage users for the MS.

 MS limitations: – Can only view or edit one IMEI range at a time. – Not possible to bulk provision IMEI ranges.

 A typical MS implementation would consist of: – Two servers, both installed with the MS. – Each instance of MS will connect to a different front end node to provide redundancy. – The connection protocol between MS and the front end is LDAP. – When deployed with the solution architecture MS can access front end data only.

CT54131EN51GLA1

28


One-EIR Overview

One-EIR and Management Server • Management Server is a web-based user interface • Connects to One-EIR using LDAP over TCP/IP • May be used to view and edit the following: – Application control and configuration data – Signalling link data – IMEI range data used by the One-EIR application Management Server LDAP

One-EIR (front end only) © Nokia Solutions and Networks 2015

1

Fig. 14


. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

29

One-EIR Overview

CT54131EN51GLA1

30


One-EIR Overview

2.4

One-EIR and System Monitor

One-EIR can be integrated to NetAct (NSN’s network management system) or a third party network management system via System Monitor 2.0. This allows fault and performance management of the One-EIR.

One-EIR and System Monitor

• System Monitor provides a fault and performance interface between the EIR nodes and the NMS – Serves geographically distributed systems – Presents aggregate view to NMS  Interpreted from all servers’ data  Reduces quantity of alarms, and increases quality of information NetAct or NMS NE3S SNMP System Monitor One-EIR (NDS, ADM, PGW, NTF nodes)


1

Fig. 15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . Solutions . . and . Networks . . .2015.. © Nokia . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

31

One-EIR Overview

2.5

One-EIR Processing Overview

The One-EIR receives checkIMEI MAP messages from an entity in the signaling network (MSC, SGSN or MME, depending on the type of network). On receipt of a checkIMEI message the EIR will perform the following functionality:

 Extract the IMEI and extract the IMSI if it is present.  Carry out a database search using the IMSI value, if present. – If the policing feature is enabled, carry out policing checks related to the IMSI. – If the SSHTR feature is enabled, check the device set. – If, after these checks, the device (IMEI) is found to be blacklisted, the EIR returns a black color result to the network and does not carry out the IMEI check.

 Carry out a database search using the IMEI value. – Check the status of the IMEI (black, grey or white). – If the policing feature is enabled, carry out policing checks related to the IMEI. – Raises any alarms and generates any log file entries if required by current configuration. For example, a log entry to specify that the IMEI was blacklisted. – Raises notifications if required by configuration. For example, notify an external system that a grey listed IMEI was used.

 Respond to the network. The EIR will return one of the following results: – A MAP checkIMEI response: this will contain the color list status (black, grey or white). – A MAP error: for example that the IMEI was unknown or not present in the original message.

CT54131EN51GLA1

32


One-EIR Overview

One-EIR Processing Overview • An overview of the functionality carried out by the One-EIR: Extract IMEI Extract IMSI (if present)

Check IMEI

Policing feature (optional) Query database using IMSI

SSHTR feature (optional)

If blacklisted

Return result

If not blacklisted

Colour check Query database using IMEI

Policing feature (optional)

Return result

If required

Raise alarms and generate logs

Raise notifications


1

Fig. 16


. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

33

One-EIR Overview

2.6

One-EIR Benefits

One-EIR 3.0 Benefits • Security – With equipment identity and control, theft of mobile phones can be discouraged. – Suspicious IMSI/IMEI combinations can be blocked. – Irregular changes in patterns of IMSI/IMEI combinations can be used to send alarms for operator to alert authorities of suspicious behaviors

• Scalability – From small start-up configurations to large scale deployments with multiple applications – Whether it’s a small standalone system for 10 000 subscribers to 100 Million and above subscribers, One-EIR scales as operators demands it to scale

• Flexibility – Deployed in standalone or distributed configurations – Deployed as part of a multi application data hosting environment © Nokia Solutions and Networks 2015

1

Fig. 17

34

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . . . . . .© Nokia . .Solutions . .and .Networks . .2015. . . . . . . . .

One-EIR Overview

2.7

Check your understanding

Check your understanding What have you learned about the EIR? • What is EIR? • What MAP message does the EIR process? What do you know about your own EIR system? • Is your One-EIR data co-located with other applications? • Is it a distributed system? • Is IMSI and IMEI policing enabled? • Does your One-EIR use the IMEI DB Interface?


1

Fig. 18

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CT54131EN51GLA1 . Solutions . . and . Networks . . .2015.. © Nokia . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

35

One-EIR Overview

CT54131EN51GLA1

36


One-EIR Overview

3

Exercise

Product Overview - Exercises One-EIR

1


Fig. 19


37

One-EIR Overview

3.1

Review Questions

1. What is the main function of an EIR?

2. What does IMEI stand for?

3. What is the purpose of the IMEI?

4. The checkIMEI MAP message is used to validate IMEIs. When is a checkIMEI message sent to the EIR?

5. Which network entities may send checkIMEI requests to an EIR?

6. What are the possible checkIMEI responses that an EIR can return?

7. For each possible color status that the EIR can return, state whether the handset will be allowed to use the network or blocked from using the network: a) White b) Grey c) Black 8. If "Unknown Equipment" status is returned what does this mean and will the network allow the handset to be used?

CT54131EN51GLA1

38


One-EIR Overview

9. Which of the following is correct? a) An EIR checks the IMEI of any handset that uses the network. b) An EIR checks the IMEI of handsets belonging to home subscribers only. c) An EIR checks the IMEI of handsets belonging to visiting subscribers only. 10. If a handset is reported stolen in one network, how long will it be before the handset is black listed on another network that shares IMEI data?


39

One-EIR Overview

CT54131EN51GLA1

40


One-EIR Overview

4

Solution

Product Overview - Solutions One-EIR

1


Fig. 20


41

One-EIR Overview

4.1

Answers to Review Questions

1. What is the main function of an EIR? To prevent fraudulent use of handsets in the network. 2. What does IMEI stand for? International Mobile Equipment Identity. 3. What is the purpose of the IMEI? To uniquely identify each handset. 4. The checkIMEI MAP message is used to validate IMEIs. When is a checkIMEI message sent to the EIR? A checkIMEI message may be sent when the following events occur:

 IMSI attach  Location Update  Mobile Originated call or SMS  Mobile Terminated call or SMS 5. Which network entities may send checkIMEI requests to an EIR? MSC, SGSN, and MME 6. What are the possible checkIMEI responses that an EIR can return?

 A result: either white, grey or black.  An error: unknown equipment, system failure or unexpected data value. 7. For each possible color status that the EIR can return, state whether the handset will be allowed to use the network or blocked from using the network: a) White allowed b) Grey allowed c) Black blocked

CT54131EN51GLA1

42


One-EIR Overview

If "Unknown Equipment" status is returned what does this mean and will the network allow the handset to be used? An error: unknown equipment, system failure or unexpected data value. 8. Which of the following is correct? a) An EIR checks the IMEI of all handsets currently being used in that network. b) An EIR checks the IMEI of home subscribers only. c) An EIR checks the IMEI of visiting subscribers only. 9. If a handset is reported stolen in one network, how long will it be before the handset is black listed on another network that shares IMEI data? Depends on the mechanism used to update the EIR, but if daily updates are uploaded and downloaded from a central source (e.g. the GSM IMEI database) a block could be implemented within 24 hours.


43

01 CT54131EN51GLA1 One-EIR Product Overview

Recommend Documents