02_CT54132EN51GLA1_IMEI_Data.pdf

IMEI Data

CT54132EN51GLA1

© Nokia Solutions and Networks 2015.

1

Contents

IMEI Data 1

1 IMEI Data 3

1.1 CheckIMEI Functionality 6

1.2 IMEI Data 8

1.3 How are handsets or IMEIs reported? 10

1.4 IMEI Data: DIT Diagram 12

1.5 device2g3g Object Class 14

1.6 eirColour Object Class 16

1.7 deviceType2g3g Object Class 18

1.8 Provisioning Individual IMEIs 20

1.9 Dynamic Provisioning of Individual IMEIs 22

2 Accessing IMEI Data 25

2.1 LDAP Access 27

2.2 ldapsearch Example 28

2.3 Search Scope 30

2.4 Filters 31

2.5 LDAP Query for an Individual IMEI 32

2.6 Using LDAP to Add an Individual IMEI 34

3 Exercises 35

3.1 Review Questions 36

3.2 Lab Exercise: Accessing IMEI Data (device2g3g) 37

4 IMEI Range Data (Optional Session) 41

4.1 IMEI Range: DIT Diagram 43

4.2 Management Server Login 44

4.3 Management Server Home Page 46

4.4 Access IMEI Ranges via Management Server 49

4.5 View an IMEI Range 50

4.6 Add an IMEI Range 52

IMEI Data

IMEI Data

CT54132EN51GLA1


2

4.7 Using LDAP to query IMEI ranges 54

4.8 Using LDAP to add IMEI ranges 56

5 Exercises 57

6 Solutions 59

IMEI Data

CT54132EN51GLA1


3

1 IMEI Data

1 © Nokia Solutions and Networks 2015

IMEI DataOne-EIR

Fig. 1

IMEI Data

CT54132EN51GLA1


4

IMEI Data

CT54132EN51GLA1


5

© Nokia Solutions and Networks 2015

Learning Elements

• Describe the basic checkIMEI functionality.

• Describe the IMEI data held on the One-EIR and how it is provisioned.

• View and edit the IMEI data held on the EIR via LDAP.

Fig. 2

IMEI Data

CT54132EN51GLA1


6

1.1 CheckIMEI Functionality

For each CheckIMEI message received by the Front End, a database query occurs on the Back End.

1. Front End receives CheckIMEI message.

2. LDAP query sent from Front End to Back End (routing DSA). An internal

database query is carried out by the routing DSA to determine if the IMEI data is present on any of the Back End DSAs. If the IMEI is present, the status is retrieved and sent in the LDAP response to the Front End, which passes the

status to the network in the CheckIMEI response.

3. Database query carried out internally by the routing DSA to retrieve the IMEI

data.

If the IMEI data is present, the routing DSA responds to the LDAP query with the list color (status) of the IMEI. The front end will use this status value in the CheckIMEI response.

If the IMEI is not present the LDAP query will indicate that the IMEI is not found,

and the front end will (normally) use a status of white in the CheckIMEI response.

IMEI Data

CT54132EN51GLA1


7

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


CheckIMEI Functionality

• The EIR’s main function is to check the status of the IMEI

• IMEI data is typically stored on the Back End DSAs

• The Front End will query the Back End

Back End

Routing DSA

BE DSA nBE DSA 1

2. LDAP

EIR FE DSA

1. CheckIMEI

3. Database query

Fig. 3

IMEI Data

CT54132EN51GLA1


8

1.2 IMEI Data

Individual IMEIs: this is the typical way of storing IMEI data (as individual entries).

Each IMEI code is added to the database as an individual entry (although the actual provisioning process can be carried out in bulk).

The first 14 digits of the IMEI are stored.

The status (grey or black list status) can be added either at the same time or later.

The status can be changed from grey to black, or black to grey.

TIP

There is no specific ‘white list’ for individual IMEIs. If the IMEI is not specified as being on the black or grey list it is assumed to be on the white list.

IMEI Ranges: the use of ranges is optional.

Black and grey ranges are for use if whole batches of handsets are stolen or faulty. White ranges can be added to identify batches of handsets produced by manufacturers.

The start and end IMEI are stored as 15 digits, including a zero to represent the check digit. Matching is done on the first 14 digits only.

TIP

Ranges are not typically used by operators because IMEIs are usually reported individually, not in batches. Another reason is that the central GSMA IMEI DB only

uploads and downloads individual IMEIs. This typically means that only individual black and grey IMEIs are provisioned in the One-EIR.

IMEI Data

CT54132EN51GLA1


9

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


IMEI Data

• IMEI data is typically stored on the Back End DSAs.

– Single IMEI codes are stored individually as 14 digits.

IMEI = 12345678901450

• IMEI ranges can optionally be stored on the Front End.

– Each range is identified by the first and last IMEI in the range.

– Range IMEIs are stored as 15 digits but only the first 14 digits are used in matching.

Start IMEI = 1234356789012000

End IMEI = 123456789012990

• Most operators do not store IMEI ranges because IMEIs are usually reported individually, not in batches.

Fig. 4

IMEI Data

CT54132EN51GLA1


10

1.3 How are handsets or IMEIs reported?

When a subscriber reports a stolen handset they may or may not know the IMEI of the handset. The operator typically has a legal duty to verify that the handset is

owned by the subscriber reporting it stolen. Their records will have this information if the handset was issued as part of a subscription contract.

If the handset is not linked to a subscription then the operator may be unable to identify the IMEI of the handset. In this case the operator may only be able to block

the subscriber’s IMSI and not the IMEI.

The policing data stored on the One-EIR (the policing data for IMEI and IMSI) allows

the operator to use the subscriber’s IMSI to identify the IMEI of the handset.

IMEI Data

CT54132EN51GLA1


11

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


How are handsets or IMEIs reported?

An IMEI may be reported in various ways:

• Subscriber reports stolen handset to the operator

– Operator identifies IMEI, confirms ownership and adds IMEI to the black list

• Police request operator to track a handset

– Operator identifies IMEI and adds IMEI to the grey list

• A batch of handsets has a manufacturing fault

– Operator adds the range of IMEI codes to the black list

• Operator receives IMEI updates from other operators via central IMEI DB.

– IMEI codes reported by other operators are added to the grey and black lists

The EIR itself may identify IMEI fraud:

• Policing features can highlight potential fraud.

Fig. 5

IMEI Data

CT54132EN51GLA1


12

1.4 IMEI Data: DIT Diagram

An individual IMEI is stored as a device2g3g entry. The status of the IMEI is stored as an eirColour child entry. An IMEI may or may not have a eirColour child entry, and

may in fact have both a grey and a black eirColour child entry:

eirColour (eirType=grey): the presence of an eirType=grey entry indicates that the

IMEI has been reported as suspicious. The IMEI is now on the ‘grey list’.

eirColour (eirType=black): a presence of an eirType=black entry indicates that the

IMEI has been reported as stolen or lost. The IMEI is now on the ‘black list’.

No eirColour child entry: this indicates that the IMEI has been dynamically provisioned to the database. These IMEIs that are known to belong to a home subscriber and are white listed.

TIP Note the following:

If an IMEI has been placed on the grey list and is subsequently placed on the

black list, both a grey and black eirColour entry may exist for that IMEI. If this is the case the black status will take precedence.

When a checkIMEI occurs a query is made to the back end. Both the black and grey status is queried in the same request.

Both the grey and black eirColour entries hold the same type of attributes including:

o Reason for the equipment being listed,

o Date and time of being provisioned to the EIR.

IMEI Data

CT54132EN51GLA1


13

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


IMEI Data: DIT Diagram

A device2g3g entry is added for each individual IMEI

An eirColour child entry is added if IMEI is grey or black listed

A deviceType2g3g entry is added for each Type Allocation Code

tenant

Configuration

cntdbDs

Element

root

ds=device

o=default

device2g3g

imei=<imei>

eirColour

eirType=black

eirColour

eirType=grey

deviceType

2g3g

tac=<tac>

Fig. 6

IMEI Data

CT54132EN51GLA1


14

1.5 device2g3g Object Class

The purpose of each device2g3g entry is to specify one IMEI code.

RDN attribute:

imei. The value will be the first 14 digits of the IMEI.

Other attributes:

imsiHistory. This is used for IMEI policing functionality (this is discussed in detail in

another One-EIR course).

TOOLS

Refer to the EIR 5.0 C-NTDB DIT document for details of the device2g3g object class.

IMEI Data

CT54132EN51GLA1


15

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


device2g3g Object Class

Each device2g3g entry specifies an IMEI:

tenantConfiguration

cntdbDsElement

root

ds=device

o=default

device2g3g

imei=<imei>

eirColour

eirType=black

eirColour

eirType=grey

device2g3g

Fig. 7

IMEI Data

CT54132EN51GLA1


16

1.6 eirColour Object Class

TIP

Note that a device2g3g entry may or may not have an eirColour child entry. An eirColour child entry will only exist if the device (the IMEI) has been placed on the grey or black list (i.e. if it has been reported, or if fraud is suspected).

The purpose of each eirColour entry is to specify the status of the IMEI stored in its

parent device2g3g entry.

RDN attribute:

eirType. The value will be either grey or black.

Other attributes are used to specify:

The manufacturing details of the handset

The reason for the IMEI being grey or black listed

The source of the request to grey or black list it.

TOOLS

Refer to the EIR 5.0 C-NTDB DIT document for a full list of the eirColour attributes.

IMEI Data

CT54132EN51GLA1


17

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


eirColour Object Class

Each eirColour entry specifies:

• the status of an IMEI (grey or black)

• the manufacturing details of the IMEI

tenantConfiguration

cntdbDsElement

root

ds=device

o=default

device2g3g

imei=<imei>

eirColour

eirType=black

eirColour

eirType=grey

eirColour eirColour

Fig. 8

IMEI Data

CT54132EN51GLA1


18

1.7 deviceType2g3g Object Class

The Type Allocation Code (TAC) consists of the first 8 digits of an IMEI. It identifies the type of phone (manufacturer, model, screen resolution, device bands and device

technologies).

The EIR stores TAC information. Each deviceType2g3g entry stores information for

one TAC.

The EIR outputs statistics about the number of checkIMEIs received for each TAC.

RDN attribute:

TAC value. The value will be 8 digits.

Other attributes:

deviceManufacturer (e.g. NSN)

deviceModel (e.g. M65)

deviceBands (e.g. 1800)

deviceScreenResolution (e.g. 1280x768)

deviceTechnologies (e.g. NONE)

TOOLS

Refer to the EIR 5.0 C-NTDB DIT document.

IMEI Data

CT54132EN51GLA1


19

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


deviceType2g3g Object Class

Each deviceType2g3g entry specifies a TAC

• Type allocation code

• Basic manufacturer’s details for the type of device

tenant

Configuration

cntdbDs

Element

root

ds=device

o=default

device2g3g

imei=<imei>

eirColour

eirType=black

eirColour

eirType=grey

deviceType2g3g

tac=<tac>

deviceType2g3g

Fig. 9

IMEI Data

CT54132EN51GLA1


20

1.8 Provisioning Individual IMEIs

Direct provisioning by the operator occurs for each IMEI that is reported as stolen or invalid. These IMEIs will therefore be on the grey or black list and will have an

eirColour child entry to indicate this.

Dynamic provisioning occurs for all home subscribers’ IMEIs that are used on the

network during normal subscriber activity. These IMEIs will not have a black or grey eirColour child entry, and will therefore be on the white list.

Dynamic provisioning occurs if the One-EIR is configured to carry out IMSI policing which requires the IMEI to be present in the database. Policing is covered in more

detail in another One-EIR course.

During the first few weeks of the EIR being live on a network the number of IMEIs

being provisioned dynamically will be high. A configuration parameter exists to enable throttling so that the rate of dynamic provisioning does not impact on the

performance of the system.

TIP In both cases the first 14 digits of the IMEI are provisioned.

The actual provisioning interface used to provision individual IMEI codes directly into

the database depends on the EIR deployment.

IMEI Data

CT54132EN51GLA1


21

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


Provisioning individual IMEIs

• Manual and Automatic IMEI provisioning:

– The operator can provision IMEIs as part of a manual process.

An IMEI device2g3g entry is added when the IMEI is reported stolen

An eirColour entry is added at the same time

– The EIR application can provision IMEIs dynamically.

An IMEI device2g3g entry is added on receipt of checkIMEI if:

the IMSI policing feature is enabled

and the IMEI belongs to a home subscriber

and the IMSI is also present in the checkIMEI

An IMEI that is provisioned dynamically will typically not have an eirColour child entry.

The EIR can provision IMEI device2g3g objects across multiple back end DSAs using a load sharing technique.

Fig. 10

IMEI Data

CT54132EN51GLA1


22

1.9 Dynamic Provisioning of Individual IMEIs

If the IMSI Policing feature is enabled on the EIR, the following functionality will occur:

CheckIMEI received by the EIR. If the IMSI is present in the message and the IMSI belongs to a home subscriber the IMEI is added to the database.

CheckIMEI response of white is sent by the EIR.

The next time a CheckIMEI relating to this IMEI is received, the EIR will find the IMEI in the database and will carry out IMSI Policing functionality (described in

detail later in this course). The EIR will respond with the white status unless policing information indicates that the IMEI should be blocked.

If the IMEI is reported stolen, the operator will update the IMEI data to add the eirColour child entry (black).

The next checkIMEI that is received for this IMEI will result in a checkIMEI response of black, and the handset will be blocked from using the network.

TIP

Over time, an IMEI entry is created in the database for each home subscriber. This allows the operator to carry out IMSI policing for all IMEIs owned by home subscribers.

IMEI Data

CT54132EN51GLA1


23

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


• IMEI entries are added dynamically by the EIR

Dynamic Provisioning of Individual IMEIs

EIRMSC/

SGSN

CheckIMEI (IMEI & IMSI)

CheckIMEI Response (White)

CheckIMEI (IMEI & IMSI)

CheckIMEI Response (White)

Handset reported stolen

Check IMEI (IMEI & IMSI)

Check IMEI Response (Black)

IMEI added to database if IMSI belongs to a home subscriber

Subsequent queries will find the IMEI in the database

Next CheckIMEI will result in the IMEI being blocked

IMEI black listed by operator

Fig. 11

IMEI Data

CT54132EN51GLA1


24

IMEI Data

CT54132EN51GLA1


25

2 Accessing IMEI Data


Accessing IMEI Data One-EIR

Fig. 12

IMEI Data

CT54132EN51GLA1


26

IMEI Data

CT54132EN51GLA1


27

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

2.1 LDAP Access


LDAP Access

LDAP is an open protocol used for accessing data in directory servers such as the EIR database.

Provisioning clients will access and update information in the database via LDAP connections.

The default connection port for LDAP connections is 16611.

A username and password will be required for data access.

The LDAP root object name will be specific to each operator’s implementation.

Fig. 13

IMEI Data

CT54132EN51GLA1


28

2.2 ldapsearch Example

The example ldapseach command below consists of the following options:

Host: -h <hostname>

Port: -p <portnumber>

User: -D “<username>”

Password: -W (to be prompted for the password)

Base DN: -b “<DN>” (position in the database where the search is to begin)

Search scope: -s base (one, sub)

Filter: objectclass=*

Attributes: In this example no attributes have been listed (requested). This will

result in all attributes being returned.

TIP Note that the following parameters may be different for each customer’s system:

Hostname ‘localhost’ may be used to run the command on the local server if the

EIR implementation is combined on one DSA. Use the IP of the routing server if the EIR implementation uses a separate (distributed) backend over an LDAP

connection.

Username may differ to the name used below.

WARNING

LDAP root object (dc=C-NTDB in the example below) may not be the same on all systems.

TIP

You can use the "org -ci ldapRootObjName sdfcontrol" cli command to

find out the root object name of your directory database.

IMEI Data

CT54132EN51GLA1


29

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

ldapsearch Example

ldapsearch options for Linux:

ldapsearch -x -h localhost -p 16611 -D "cn=sdfrun" -W -b “imei=11223344000162,ds=device,

o=default, dc=C-NTDB” -s base objectclass=*

ldapsearch -h localhost -p 16611 -D "cn=sdfrun" -b “imei=11223344000162,ds=device,

o=default, dc=C-NTDB” -s base objectclass=*

-x option not required -W option not required

host port user password prompt base dn

search scope filter

• ldapsearch options for Solaris:

Fig. 14

IMEI Data

CT54132EN51GLA1


30

2.3 Search Scope

ldapsearches have a scope option (-s) that gives three different search levels:

base: returns only the entry at the base DN.

one: returns all entries one level below the base DN.

sub: returns the entry at the base DN and all entries below that.


-s sub

Returns data for

the base DN and

all entries below it.

-s oneReturns data for all entries one level below the base DN

-s baseReturns data for the base DN only

Search scope

ldapsearch scope options

Entry

EntryEntry

Entry Entry

Entry

Fig. 15

IMEI Data

CT54132EN51GLA1


31

2.4 Filters

Object class included in search (in the example below): returns all information for the requested object class

Attribute included in search (in the example below): returns specific attribute value for the requested object class


Filters

Object class included in search:

Attribute included in search:

ldapsearch -h localhost -p 16611 -D cn=sdfrun -b “imei=11223344000162,ds=device,

o=default, dc=C-NDTB” -s sub objectclass=eirColour


o=default, dc=C-NTDB” -s sub objectclass=eirColour eirType

objectclass=eirColour

Search scope is -s sub

-s sub

Object class filter specifies which entries to return

Attribute filter specifies the attribute required

eirType

Fig. 16

IMEI Data

CT54132EN51GLA1


32

2.5 LDAP Query for an Individual IMEI

The ldapsearch command below is the kind of search that the EIR FE (front end) will perform to query the status of an individual IMEI on the back end.

Search for an individual IMEI entry and any possible eirColour child entries by IMEI:

ldapsearch -h localhost -p 16611 -D cn=sdfrun -b "imei=11223344000162, ds=device, o=default, dc=C-NTDB" -s sub objectClass=*

Example output from the query above:

dn: imei=11223344000162,ds=device,o=default,dc=C-NTDB

imei: 11223344000162

objectClass: device2g3g

imsiHistory: 1234567890|443322009900880

IMEI Data

CT54132EN51GLA1


33

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


LDAP query for an individual IMEI

The EIR FE queries the database for an individual IMEI:

Example output if the IMEI is black listed:


o=default, dc=C-NTDB" -s sub objectClass=eirColour

dn: eirType=black,imei=11223344000162,ds=device,o=default,dc=C-NTDB

eirType: black

objectClass: eirColour

eirEquipReason: 1

eirEquipOrganisationID: SRI

eirEquipDeviceManufacturer: Nokia

eirEquipDeviceMarketingName: Nokia3301

eirEquipProcessedDate: 12122008

eirEquipProcessedTime: 01:12

eirEquipImeiInstances: 1

eirEquipDuplicates: unique

eirEquipComm: Blocked_by_SRI

eirEquipClarifyReason: Daia

eirEquipSourceOfRequest: Ciprian

Fig. 17

IMEI Data

CT54132EN51GLA1


34

2.6 Using LDAP to Add an Individual IMEI

The ldapadd command below specifies an input file that holds the information about the entry that is being added.

The input file is in LDIF format (LDAP Data Interchange Format):

dn: <distinguished name>

<attrdesc>: <attrvalue>



dn: imei=55443322119001,ds=DEVICE,o=DEFAULT,dc=C-NTDB

imei: 55443322119001


dn: eirType=black,imei=55443322119001,ds=DEVICE,o=DEFAULT,dc=C-NTDB

eirType: black


eirEquipReason: 3658

eirEquipOrganisationID: IdeaCell 2

eirEquipDeviceManufacturer: Motorola501

eirEquipDeviceMarketingName: IntelCeleron





eirEquipComm: !@#$%̂ *

eirEquipClarifyReason: tvlagoa22

eirEquipSourceOfRequest: SUBSCRIBER

Using LDAP to add an individual IMEI

Add a device2g3g entry using ldapadd and an input file:

Where addDevice2g3g.ldif input file contains:

ldapadd -h localhost -p 16611 -D "cn=sdfrun" -f addDevice2g3g.ldif Input file-f addDevice2g3g.ldif

dn: imei=55443322119001,ds=DEVICE,o=DEFAULT,dc=C-NTDB

device2g3g

dn: eirType=black,imei=55443322119001,ds=DEVICE,o=DEFAULT,dc=C-NTDB

eirColour

Fig. 18

IMEI Data

CT54132EN51GLA1


35

3 Exercises


IMEI Data - ExercisesOne-EIR

Fig. 19

IMEI Data

CT54132EN51GLA1


36

3.1 Review Questions

1. How does the Operator know the IMEI of a stolen handset?

2. The One-EIR can store IMEI data in two different ways. Name the ways IMEIs

can be stored:

3. Why do Operators normally only use the lists of individual IMEIs and not the ranges of IMEIs?

4. Does your own EIR system use IMEI ranges? (you may or may not know this)

5. If so, does your system use the White range? (you may or may not know this)

6. If an IMEI is on both the black list and the grey list, which list takes precedence (i.e. which result will be sent back to the network in the checkIMEI response)?

7. In a distributed system, the EIR Front End and Back End parts of the system

each store different IMEI data. Which type is stored on which part?

a) Front End: _____________________________________________________

b) Back End: _____________________________________________________

IMEI Data

CT54132EN51GLA1


37

3.2 Lab Exercise: Accessing IMEI Data (device2g3g)

The trainer will provide the address and login details to access the EIR command line.

The trainer will provide instructions to access some ldapscripts that you will use

during this exercise.

The trainer will also supply you with an IMEI(s) to use during these exercises. Write

down your range here: _______________________________________________

1. Open a terminal session onto the EIR Front End using the details supplied by the Trainer.

2. Follow the instructions for accessing the ldap scripts.

3. Carry out an ldapsearch for your IMEI. Use the following search using your own

IMEI value. Note that the LDAP root object name (o=NSN,c=US) may be different on your system. Note also that the username (cn=<user>) and password may be specific to the system and may not be the sdfrun user.

ldapsearch -h localhost -p 16611 -D cn=<user> -b

"imei=<imei>,ds=device,o=default,<db root>" -s base

objectClass=*

4. Does the IMEI have an IMSI history listed? If so, how many entries are in the

history?

5. What is the format of the imsiHistory value?

6. Carry out the same ldapsearch, this time using the -s sub option (for a subtree

search) and a filter for the status. Use the following search using your own IMEI value:

ldapearch -h localhost -p 16611 -D cn=<user> -b

"imei=<imei>,ds=device,o=default,<db root>" -s sub

objectClass=eirColour eirType

IMEI Data

CT54132EN51GLA1


38

7. What is the status of your IMEI? (i.e. which list is it on?)

8. Add an IMEI entry using ldapadd and an input file. Ask the trainer for a unique

IMEI value to use.

a) The input file may be present on the training system. Edit the input file using vi.

You need to change the IMEI number where it occurs (3 places, shown in bold in the example below) so that it is your new IMEI. If you are unsure about using vi, ask the trainer to demonstrate editing and adding the new IMEI. The

input file contains similar data to the following:

dn: imei=<imei>,ds=DEVICE,o=DEFAULT,dc=C-NTDB

imei: <imei>


dn: eirType=black,imei=<imei>,ds=DEVICE,o=DEFAULT,dc=C-

NTDB

eirType: black


eirEquipReason: 3658

eirEquipOrganisationID: IdeaCell 2

eirEquipDeviceManufacturer: Motorola501

eirEquipDeviceMarketingName: IntelCeleron





eirEquipComm: !@#$%^*

eirEquipClarifyReason: tvlagoa22

eirEquipSourceOfRequest: SUBSCRIBER

b) Now add the data using the ldapadd command

ldapadd –h localhost –p 16611 –D cn=sdfrun –f <input_file>

IMEI Data

CT54132EN51GLA1


39

9. Carry out a subtree ldapsearch for the IMEI entry you just added.

ldapsearch –h localhost –p 16611 –D cn=<user> -b

"imei=<imei>,ds=device,o=default,<db root>" –s sub

objectClass=*

IMEI Data

CT54132EN51GLA1


40

IMEI Data

CT54132EN51GLA1


41

4 IMEI Range Data (Optional Session)


IMEI Range Data (optional session)One-EIR

Fig. 20

IMEI Data

CT54132EN51GLA1


42

WARNING

This section is only necessary if the operator is storing IMEI data in ranges on the EIR front end DSA.

The use of ranges as a way of storing IMEIs is optional.

If used, ranges are provisioned as white, grey or black, although it is unusual to

provision white lists.

The EIR will only query the IMEI ranges if an individual IMEI match has not been

found in the back end data.

When a query is made on the front end, the black ranges are searched first, then

the grey ranges.

IMEI Data

CT54132EN51GLA1


43

4.1 IMEI Range: DIT Diagram

White, grey and black range entries all hold the same type of attributes:

Attribute Description Example Values

eirStartImei This attribute identifies the range object and is the first IMEI in the range.

12345678901000

eirEndImei The last IMEI in the range. 12345678901999

comment A comment. Stolen


IMEI Range: DIT Diagram

IMEI ranges are held on the EIR front end

dsa

sbConfig

eirService

root

config=sb

dsaid=<>

sbaid=eir

eirRngList

eirListType=white

eirRngList

eirListType=black

eirWhiteRng

eirStartImei=<imei>

eirBlackRng

eirStartImei=<imei>

eirGreyRng

eirStartImei=<imei>

eirRngList

eirListType=grey

Fig. 21

IMEI Data

CT54132EN51GLA1


44

4.2 Management Server Login

The Management Server typically runs on a web server machine that is connected to the One-EIR via a TCP/IP connection. It uses the LDAP protocol to communicate

with the Directory Server.

The Machine name can also be used for the path to management server:

http://<machine name>/login.xml

Access control is implemented on the Management Server to limit a user’s access to

particular data.

TOOLS

Refer to the Management Server Installation Guide for more details about the

Management Server implementation.

TIP

Note that only one session should be opened at a time for one user from one terminal.

IMEI Data

CT54132EN51GLA1


45

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


Management Server Login

To load the Management Server:

• Open your favoured internet browser.

• Enter the following path into the address bar:

– http://<machine IP address>/login.xml

• Enter your User Name & Password, then click Login

Address Path

User Name &

Password

Click Login

Fig. 22

IMEI Data

CT54132EN51GLA1


46

4.3 Management Server Home Page

The Management Server home page gives you access to the following:

Main Menu

o Management server standard menu items.

Management Server

o User and group administration.

Directory Server

o Configuration and control data for One-NDS functionality.

o SS7 signaling data.

Equipment Identity Register (EIR)

o Application configuration data

o IMEI range data.

Application Developers Workbench (ADW)

o Application functionality control & configuration data.

IMEI Data

CT54132EN51GLA1


47

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


Management Server Home Page

Home page is the start page for all users.

User and group

administration data

One-NDS & SS7

configuration data

EIR configuration &

IMEI ranges

Additional

configuration data

Main Menu

Fig. 23

IMEI Data

CT54132EN51GLA1


48

IMEI Data

CT54132EN51GLA1


49

4.4 Access IMEI Ranges via Management Server

The use of ranges is optional.

If ranges are used by the Operator, normally only the grey and black ranges are used and not the white ranges. This means an operator will check if an IMEI is on the black

or grey lists, and if not, will assume that the IMEI is on the white list.

When a checkIMEI is received, the One-EIR application queries the individual IMEI

data first, and will only query the range data if it fails to find an individual IMEI match. When the ranges are queried, the black ranges are searched first, then the grey

ranges.


Access IMEI Ranges via Management Server

From the Home page select Entry Management

This provides access to IMEI Ranges:

Add an IMEI range

View an IMEI range

Fig. 24

IMEI Data

CT54132EN51GLA1


50

4.5 View an IMEI Range

TIP When viewing an existing range via Management Server, it is necessary to know the Start IMEI.

This is the first IMEI in the range.

In fact, Management Server will only return a range if the Start IMEI is specified, and

it is not possible to search using an IMEI that occurs within the range.

WARNING This is a limitation of Management Server.

IMEI Data

CT54132EN51GLA1


51

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


View an IMEI Range

• Specify the Start IMEI then select Submit.

• The range details will be displayed:

Submit

Fig. 25

IMEI Data

CT54132EN51GLA1


52

4.6 Add an IMEI Range

For each range, the following data is required:

Entry Type: Black, Grey or White. This is a mandatory field.

Start IMEI: The first IMEI in the range. This is a mandatory field.

End IMEI: The last IMEI in the range. This is a mandatory field.

Comment: A reason or description for the range. This is an optional field.

TIP Note that the Start and End IMEIs can be 14, 15 or 16 digits in length. When set as 15 digits long, the number must end with a final digit of 0.

In all cases, range matching is only performed on the first 14 digits of the IMEI in the

received message.

IMEI Data

CT54132EN51GLA1


53

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


Add an IMEI Range

• Select Add Range Entry

• Specify range details then select Add to complete the action:

Add

Add Range Entry

Fig. 26

IMEI Data

CT54132EN51GLA1


54

4.7 Using LDAP to query IMEI ranges

The One-EIR application accesses IMEI Ranges using an API, not LDAP.

API can search for an individual IMEI within a range.

The user has access using LDAP.

LDAP can search for the start IMEI, but not an IMEI within the range.

ldapsearch –h localhost –p 16611 –D cn=sdfrun –b

“eirStartImei=1122334400016000,

eirListType=black,sbaId=eir,config=sb, dsaId=1,o=NSN,c=US” –s

base objectClass=*

LDAP can search for all ranges of one color type (i.e. one object class).

ldapsearch –h localhost –p 16611 –D cn=sdfrun –b

“eirListType=black,sbaId=eir, config=sb,dsaId=1,o=NSN,c=US” –s

sub objectClass=eirBlackRng

WARNING

Note that the LDAP root name will be the Front End root name (in this example o=NSN, c=US). It is different to the Back End root name and will be different for each customer.

The ldapsearch command shown in the slide below uses an object class filter that will

return only eirBlackRng entries.

TIP

Note that the LDAP search functionality has a limitation on the amount of data that can be returned (unless the One-NDS is configured to stream the results back to the user). If streaming is not configured the result will only return the first 50k of data.

These ldapsearch commands used here are examples that can be executed on a

Solaris system. Note that the user will be prompted for the password.

IMEI Data

CT54132EN51GLA1


55

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


dn: eirStartImei=911223340000000,eirListType=black,sbaId=eir,config=sb,dsaId=1,<ldapRoot>

eirStartImei: 911223340000000

objectClass: eirBlackRng

eirEndImei: 911223349999990

eirEquipComment: Nokia 1234




eirEndImei: 112233440169990

eirEquipComment: Fault batch

• Query ranges using ldapsearch:

• The output from this command lists Black Range entries:

Using LDAP to query IMEI ranges

ldapsearch -h localhost -p 16611 -D cn=sdfrun -b "sbaid=eir,config=sb,

dsaid=1,<ldapRoot>" -s sub objectClass=eirBlackRng Object class filterobjectClass=eirBlackRng

Fig. 27

IMEI Data

CT54132EN51GLA1


56

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

4.8 Using LDAP to add IMEI ranges

The ldapadd command below specifies an input file that holds the information about the entry that is being added.

The input file is in LDIF format (LDAP Data Interchange Format):

dn: <distinguished name>






eirEndImei: 1122334400018999

eirEquipComment: Stolen batch

dn: eirStartImei=1122334400022000,eirListType=grey,sbaId=eir,config=sb,dsaId=1,<ldapRoot>


objectClass: eirGreyRng

eirEndImei: 1122334400022999

eirEquipComment: Suspect batch

• Add ranges using ldapadd and an input file

• Where the addRanges.ldif input file contains:

Using LDAP to add IMEI ranges

ldapadd -h localhost -p 16611 -D "cn=sdfrun" -f addRanges.ldif

dn: eirStartImei=112233440180000,eirListType=black,sbaId=eir,config=sb,dsaId=1,<ldapRoot>”

dn: eirStartImei=112233440220000,eirListType=grey,sbaId=eir,config=sb,dsaId=1,<ldapRoot>



eirEndImei: 112233440189990

eirEquipComment: Stolen batch

Attributes


objectClass: eirGreyRng

eirEndImei: 112233440229990

eirEquipComment: Suspect batch

Input file-f addRanges.ldif

Object DN

Fig. 28

IMEI Data

CT54132EN51GLA1


57

5 Exercises


IMEI Data - ExercisesOne-EIR

Fig. 29

IMEI Data

CT54132EN51GLA1


58

5.1 Lab Exercise: Accessing Range Date (optional)

This exercise is only necessary if the operator uses IMEI ranges.

Managing IMEI Ranges via Management Server:

The trainer will provide a Management Server URL, username and password.

The trainer will also supply you with a range of IMEIs to use for this exercise. Write down your range here: _______________________________________________

1. Open a web browser and log into the Management Server using the details

supplied by the Trainer.

2. Using the instructions in the training notes, add a range of IMEIs.

IMEI Data

CT54132EN51GLA1


59

6 Solutions


IMEI Data - SolutionsOne-EIR

Fig. 30

IMEI Data

CT54132EN51GLA1


60

6.1 Answers to Review Questions

1. How does the Operator know the IMEI of a stolen handset?

The subscriber reporting the stolen handset may know the IMEI. The operator can (normally) identify ownership based on information held by the operator.

The One-EIR (if used with NSN NT HLR product) can record information that links the IMEI to the subscriber's IMSI, thereby identifying the IMEI by use of the IMSI.

2. The One-EIR can store IMEI data in two different ways. Name the ways IMEIs

can be stored:

In ranges.

As Individual IMEIs.

3. Why do Operators normally only use the lists of individual IMEIs and not the

ranges of IMEIs?

IMEIs are usually reported individually, not in batches. Therefore most, if not all, IMEIs are stored individually.

4. Does your own EIR system use IMEI ranges? (you may or may not know this)

Answer is as per customer's EIR configuration.

5. If so, does your system use the White range? (you may or may not know this)

Answer is as per customer's EIR configuration.

6. If an IMEI is on both the black list and the grey list, which list takes precedence (i.e. which result will be sent back to the network in the checkIMEI response)?

Black status takes precedence and therefore the result of "black" will be sent

to the network.

7. In a distributed system, the EIR Front End and Back End parts of the system

each store different IMEI data. Which type is stored on which part?

a) Front End: __Ranges of IMEIs ____________________________________

b) Back End: __Individual IMEIs__________________________________

IMEI Data

CT54132EN51GLA1


61

Documents

02_CT54132EN51GLA1_IMEI_Data.pdf