CDMA Equipment Identity Register – Phase 1
Design Requirements
CDG Document 207
Version 1.0
26 May 2011
CDMA Development Group
575 Anton Boulevard, Suite 560
Costa Mesa, California 92626
PHONE +1 888 800-CDMA
+1 714 545-5211
FAX +1 714 545-4601
http://www.cdg.org
cdg@cdg.org
Notice
Each CDG member acknowledges that CDG does not review the
disclosures or contributions of any CDG member nor does CDG verify
the status of the ownership of any of the intellectual property rights
associated with any such disclosures or contributions. Accordingly, each
CDG member should consider all disclosures and contributions as being
made solely on an as-is basis. If any CDG member makes any use of
any disclosure or contribution, then such use is at such CDG member's
sole risk. Each CDG member agrees that CDG shall not be liable to any
person or entity (including any CDG member) arising out of any use of
any disclosure or contribution including any liability arising out of
infringement of intellectual property rights.
This document approved via CDG Resolution 2003.2 on 8 December
2003.
1
Contents
2
1. Introduction ................................................................................................................................ 1
3
1.1 Summary ............................................................................................................................ 1
4
1.2 Acronyms and Abbreviations ............................................................................................. 1
5
1.3 Technical Assistance ......................................................................................................... 2
6
2. Overview and Background ........................................................................................................ 3
7
2.1 Overview ............................................................................................................................ 3
8
2.2 Background ........................................................................................................................ 3
9
3. System Requirements ............................................................................................................... 4
10
4. Subsystems ................................................................................................................................ 7
11
4.1 Mobile Station..................................................................................................................... 7
12
4.2 Equipment Register ............................................................................................................ 7
13
4.3 Provisioning System ........................................................................................................... 9
14
5. Design Requirements ................................................................................................................ x
15
5.1 Call Flows ........................................................................................................................... x
16
5.1.1 Restrict Account with Black Listed Device ..........................................................xi
17
5.1.2 Remove Account Restrictions with New Device ............................................... xiv
18
5.1.3 Deny Account with Black Listed Device ............................................................ xvi
19
5.1.4 Remove Account Restrictions via Customer Service Call ............................... xviii
20
5.1.5 Query a Device: Based on Age of Record .........................................................xx
21
5.1.6 Query a Device: Based on Empty Record......................................................... xxi
22
5.2 Database (ER) Requirements ........................................................................................ xxiii
23
5.3 Network Requirements ................................................................................................... xxiv
24
5.4 Interface Requirements ................................................................................................... xxv
25
6. Appendix ................................................................................................................................ xxvi
26
7. References ............................................................................................................................ xxvii
27
Ref Doc 207, Ver 1.0
9 April 2020
ii
Figures
1
2
No table of figures entries found.
Tables
3
4
5
6
Table 1-1: Acronyms and Abbreviations ....................................................................... 1
Table 3-1 System Requirements .................................................................................. 6
Table 6-1 State Table ......................................... Ошибка! Закладка не определена.
7
8
9
Ref Doc 207, Ver 1.0
9 April 2020
iii
Revision History
1
Date
26 May 2011
Version
1.0
Description
Initial CDG release
2
Ref Doc 207, Ver 1.0
9 April 2020
iv
1. Introduction
1
2
1.1 Summary
4
This document specifies the design requirements for a CDMA Equipment Identity
Register as part of new subsystem called the Equipment Registry.
5
1.2 Acronyms and Abbreviations
3
Table 1-1: Acronyms and Abbreviations
6
Acronym
Meaning
3GPP2
3rd Generation Partnership Partnership 2
CEIR
Central EIR
EIA
Electronics Industry Association
EIR
International Forum on ANSI-41 Standards Technology
ER
Equipment Registry
ESN
Electronic Serial Number
HW ID
Hardware Identifier
IMSI
International Mobile Subscriber Identity
MDN
Mobile Dialed Number
MEID
Mobile Equipment Identifier
MIN
Mobile Identification Number
MS
Mobile Station
NV
Non-volatile
pESN
pseudo-ESN
pRUIMID
pseudo-RUIMID
RUIM
Removable User Identity Module
RUIMID
RUIM Identification
SMS
Short Message Service
SMSC
Short Message Service Center
Ref Doc 207, Ver 1.0
9 April 2020
1
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
1
2
3
Acronym
Meaning
TIA
Telecommunication Industry Association
UIM ID
User Identity Module Identifier
1.3 Technical Assistance
For any questions or comments regarding this document, contact CDG at the address
on the cover of this document.
Ref Doc 207, Ver 1.0
9 April 2020
2
2. Overview and Background
1
2
2.1 Overview
10
The Equipment Identity Register (EIR) project provides operators with a mean to
improve management of devices seeking to access the commercial CDMA networks that
do not adhere to specifications governing device hardware identification. The project will
be split into two phases. Phase 1 will be a short term design that permits EIR vendors to
supplement the existing Electronic Serial Number (ESN) tracker solution deployed today.
Phase 2 will be a long term design that will require some changes in 3GPP2
specifications and infrastructure upgrade to allow for a more harmonized approach for
the ecosystem. This document will focus on Phase 1 design requirements.
11
2.2 Background
3
4
5
6
7
8
9
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
There are many CDMA markets where tracking of mobile devices is either required or
highly desired. The CDMA specifications as they exist today have resulted in a
fragmented and often proprietary approach to addressing this need. For example, in
India the use of ESN tracker applications and databases have provided operators with a
means to obtain device specific information (ESN or MEID, Software version, device
model, etc) via SMS messages. However, the commercial ESN tracker solutions,
although similar in principle, differ from operator to operator. Additionally, the ESN
tracker solutions that are deployed in the Indian market do not give the operator a
means to identify, disallow network access, or otherwise manage devices that do not
have properly formated or missing ESN or Mobile Equipment Identifier (MEID) values.
This project seeks to address the gap that exists in this area by introducing a new entity
called Equipment Registry (ER). The ER will bridge the gap between the existing
capabilities of the ESN Tracker and the rest of the core network. The ER will introduce
the EIR database that will store the MEID value and status, and it will provide the
necessary logic and function to restrict/deny/allow access to the network services.
Ref Doc 207, Ver 1.0
9 April 2020
3
3. System Requirements
1
2
3
The following section contains the system requirements defined by participating
operators [2].
Req.
No.
Requirement
Nodes Impacted
SYS-1
Network shall maintain the database of
ESN/MEIDs of all the devices
registered in the network
ESN/MEID
database
SYS-2
Network should maintain age(time
since the record was updated) of each
ESN/MEID record
ESN/MEID
database
SYS-3
Network should be able to Query the
subscription for its ESN/MEID
MS, SMSC, ER
SYS-4
Network shall be able to identify invalid
ESN/MEID values such as:
EIR
a) ESN/MEID values which are not
allocated as per TIA
b) ESN/MEID values which are null or
all zero
c) ESN/MEID values defined by
operators or regulators (e.g. all
ones or other default values used
by manufacturers)
SYS-5
Network shall maintain a white list
(allowed), grey list (track), and black list
(block) according to operator rules
EIR
SYS-6
Network shall identify ESN/MEID of
stolen devices (this may be a subset of
the black list)
EIR
Ref Doc 207, Ver 1.0
9 April 2020
4
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
Req.
No.
Requirement
Nodes Impacted
SYS-7
Network should have access to central
database (Central-EIR) for all
participating CDMA Networks
EIR, CEIR
SYS-8
Network should make available
operators updated local
black/white/grey list database
information to the central-EIR, so as to
prevent cloning across networks and
keeping database information up to
date.
EIR, CEIR
SYS-9
Network’s local EIR should be
updated/synchronized with the CentralEIR periodically.
EIR, CEIR
SYS-10
Network shall block services to
subscribers with registered devices
with Invalid or Blacklisted ESN/MEID
ER, Provisioning
System
SYS-11
Network should be able to Identify the
device model, version and other
"device type" information
ESN database
SYS-12
Equipment Registry shall support all
the possible device and Subscription
Identifiers (ESN, MEID, MDN and/or
IMSI)
ER
SYS-13
ER shall support MEID ranges of
00000000 00000000 to FFFFFFFF
FFFFFFFF.
ER
Ref Doc 207, Ver 1.0
9 April 2020
5
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
Req.
No.
Requirement
Nodes Impacted
SYS-14
ER entity shall support interfaces to the
following subsystems:
Provisioning
System, CEIR,
SMSC
a) Provisioning System
b) CEIR (if present)
c) SMSC (if device query function is
supported)
Table 3-1 System Requirements
1
2
Ref Doc 207, Ver 1.0
9 April 2020
6
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
4. Subsystems
1
2
4.1 Mobile Station
6
It is assumed that the mobile station is capable of sending an ESN tracking message to
a pre-defined destination address specific to a carrier network. The ESN tracking
message is an SMS message, which at a minimum provides a mapping between
subscription identifier and the mobile station hardware identifier(s).
7
There can be two types of mobile stations:
3
4
5
8

NV based device – The ESN tracker algorithm is implemented on the device. The
ESN tracker message provides a mapping between the subscription identifier
and the HW ID of the device (MEID).

RUIM based device (ME+RUIM) – The ESN tracker message is typically
implemented on the RUIM. In some cases, the ESN tracker message may be
implemented on the device. In either case, the ESN tracker message sent to the
network, would at a minimum provide a mapping between the subscription
identifier, RUIM hardware ID (UIM ID/pUIMID) and ME hardware ID (MEID).
9
10
11
12
13
14
15
20
The ESN tracker message may have additional information such as the mobile
equipment (ME) make, model and sw version information. The design details of the ESN
tracker application (for example, events triggering the transmission of the message, retry
mechanisms, failure handling etc) are specific to a carrier, and varies depending on the
carrier requirements.
21
4.2 Equipment Registry
16
17
18
19
22
23
24
25
26
The main function of the Equipment Registry (ER) is to determine the status of the
subscription and the associated device (ME) hardware ID (black/gray/white listed), and
take appropriate action. Upon receiving an ESN tracker message, the ER may take one
of the following actions:

o
27
28
29
30
If the received MEID is “White/Gray Listed”, and the subscription state is “Valid”

Action taken: None
If the received MEID is “Black Listed” and subscription state is “Valid”
o
Action taken: Transition subscription state to “Restrict”. Alternatively, the
subscription state can optionally transition to “Deny“based on certain
Ref Doc 207, Ver 1.0
9 April 2020
7
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
operator defined criteria1 - ER restricts the type of calls allowed by this
subscription or completely denies access to services by this account, via
the Provisioning Subsystem.
1
2
3
4

If the MEID is “Black Listed” and the subscription state is “Restrict”
o
5
6
7
8

If the MEID is “White/Gray Listed” and the subscription state is “Restrict
o
9
10
11
12
13
14
15
16
Action taken: No action taken. Alternatively, the subscription state can
optionally transition to “Deny” based on certain operator defined criteria1
– ER denies subscription access, via the Provisioning System.
Action taken: Transition subscription state to “Valid” after removing
Account Restrictions - ER removes the restrictions (transition account to
“Valid” state) on the type of calls allowed by this subscription, via the
Provisioning Subsystem.
The ER should allow the subscription state to be changed from “Valid”/”Restrict” to
“Deny” via the customer service portal or the Provisioning System. The only way to
change the subscription status from “Deny” to “Valid”/“Restrict” is via the customer
service portal or the Provisioning System.
17
1 This document does not define the cirteria. It is up to the operator to decide whether to define and use
such criteria.
Ref Doc 207, Ver 1.0
9 April 2020
8
CDMA Equipment Identity Register - Phase 1 Design RequirementsОшибка! Используйте вкладку "Главная
Account State:
VALID
Account State:
RESTRICT
te
up
r
I/P
CS
o
CS
I/P
ro v
Sy
s
u
ys
vS
(a
nd
M
ad BL EID
di AC :
tio K
n
a
lc
ri t
e
ri a
)
)
e:
ia
at
St K riter
D C lc
I
E A
M BL iona
t
di
ad
d
n
(a
pd
da
ate
MEID State:
WHITE
State:
MEID K
BLAC
ME
ID
WH State:
IT
GR E/
AY
MEID State:
BLACK
Account State:
DENY
1
2
3
4
5
6
7
Figure 4-1 Subscriber Account Status State Machine
4.3 Provisioning System
The Provisioning System is presumed to have the capability to Update/Restrict/Deny
subscription account status. It is expected the Provisioning System can provide an
interface to ER to initiate subscription account status changes.
Ref Doc 207, Ver 1.0
9 April 2020
9
Ошибка! Неизвестное имя свойства документа.
Contents
5. Design Requirements
The following sections describe the design requirements that apply to the Phase 1 Equipment
Identity Register as defined by participating operators.
5.1 Call Flows
The following call flows describe the procedures to be followed for each use case. Steps that
are colored red indicate an area where development/enhancements will be required at the ESN
Tracker database. Steps that are colored in blue indicate an area where development will be
require at the EIR solution.
Qualcomm Confidential and Proprietary
x
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.1.1 Restrict Account with Black Listed Device
Use case: An MEID has been flagged with as black listed at the central or local EIR database,
and is used to access the network, the subscriber account will be restricted. (SYS-10)
AA
Equipment Registry
ESN
Tracker
MS
Central EIR
BB
TIA MEID DB
Local EIR
(Phase I)
Serving System
Provision
Server
HLR
VLR
MSC
A
B
C
D
E
F
G
H
I
Figure 5-1 Restrict Account with Black Listed Device
A. Mobile Subscriber (MS) sends required information to the network via ESN Tracker application
B. ESN tracking message triggers ER logic
C. ER logic performs check: MEID format, MEID status (Black, Grey, White), subscription account
status (Restrict, Deny, Valid)
- Check determines MEID status is Black
- Check determines Subscription Account status is “Valid”
D. ER triggers an update of the MS’s service profile via the Provisioning interface, and it includes the
MDN, ESN or UIMID, and Profile changes.
Qualcomm Confidential and Proprietary
xi
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
Profile changes: Restrict Terminating calls, Restrict Originating calls to Cust Serv Num only,
Restrict SMS Orig
E. The Provisioning Server (PS) updates the MS service profile at the HLR to restict the account.
NOTE: It is presumed that the MDN is passed to the PS, and a translation to MIN is done.
F. Per [1] Section 4.20 QualificationDirective, the HLR reports the change in the MS’s service profile
by sending a QUALDIR to the VLR where the MS is registered. (Parameters: MIN, ESN or UIMID,
MYTYP, QUALCODE, Profile)
Parameters
Usage
Type
MIN
Served MS MIN
ESN or UIMID
MYTYP
Served MS ESN or UIMID
HLR vendor identification
R2
R
QUALCODE
Profile:
[CallingFeaturesIndicator]
Type of qualification=profile only
Subscriber's profile information:
Authorization and activity states for features.
[OriginationIndicator]
Type of calls MS is allowed to originate.
[Digits(Restriction)]
Selected NPA-NXX or NPA-NXX-XXXX
allowed for call origination as indicated in
OriginationIndicator.
R
[TerminationRestrictioncode]
Type of calls MS is allowed to terminate.
R
[SMS-OriginationRestrictions]
Defines the type of messages the MS is
allowed to originate.
R
[SMS-TerminationRestrictions]
Defines the type of messages the MS is
allowed to terminate.
R
MBC3
MBC
R
R
G. The VLR sends an empty qualdir to the HLR
H. The VLR reports the change in the MS’s service profile by sending a QUALDIR to the Serving
MSC. (Parameters: MIN, ESN or UIMID, MYTYP, QUALCODE, Profile, LOCID)
I.
Parameters
Usage
Type
MYTYP
LOCID
VLR vendor identification
Location area identity of MS, if
available.
MBC
O4
Upon receipt of the QUALDIR, the Serving MSC may discontinue any call or service 5 in progress,
and sends an empty qualdir to the HLR
2 Required (R) parameter for the scenario.
3 Mandatory for Backward Compatibility (MBC) identifies a parameter that is not used for the scenario but mandatory
based on backward compatibility with previous versions of TIA/EIA-41.
4 Optional (O) parameter for the scenario.
Qualcomm Confidential and Proprietary
xii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
AA. The Local EIR is updated with the latest information on valid MEID assignments by the most
efficient method available. Today, an email is sent upon request with the information requested.
BB. The Local EIR synchronizes with the Central EIR database to update the black listed MEID data.
5 Termination of a call or service by the Serving MSC is dependent on the particular infrastructure capabilities.
Qualcomm Confidential and Proprietary
xiii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.1.2 Remove Account Restrictions with New Device
Use case: Remove account restrictions when the user moves the RUIM from a black listed
device to a different device (presumably, a non-black listed device).
AA
Equipment Registry
ESN
Tracker
MS
Local EIR
(Phase I)
Central EIR
BB
TIA MEID DB
Serving System
Provision
Server
HLR
VLR
MSC
A
B
C
D
E
F
G
H
I
Figure 5-2 Remove Account Restrictions with New Device
A. Non-black listed MS with restricted RUIM sends ESN tracker update to ESN tracker DB
B. ESN tracking message triggers ER logic
C. ER logic performs check: MEID format, MEID status (Black, Grey, White), subscription account
status (Restrict, Deny, Valid)
- Check determines MEID status is white
- Check determines Subscription Account Status is ”Restrict”
D. ER triggers an update of the MS’s service profile via the Provisioning interface, and it includes the
MDN, ESN or UIMID, and Profile changes.
Qualcomm Confidential and Proprietary
xiv
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
Remove profile changes: Restrict Terminating calls, Restrict Originating calls to Cust Serv
Num only, Restrict SMS Orig
E. The Provisioning Server (PS) updates the MS service profile at the HLR to remove account
restictions.
NOTE: It is presumed that the MDN is passed to the PS, and a translation to MIN is done.
F. Per [1] Section 4.20 QualificationDirective, the HLR reports the change in the MS’s service profile
by sending a QUALDIR to the VLR where the MS is registered. (Parameters: MIN, ESN or UIMID,
MYTYP, QUALCODE, Profile)
Parameters
Usage
Type
MIN
ESN or UIMID
MYTYP
QUALCODE
Profile:
[CallingFeaturesIndicator]
Served MS MIN
Served MS ESN or UIMID
HLR vendor identification
Type of qualification=profile only
Subscriber's profile information:
Authorization and activity states for features.
R
R
MBC
MBC
R
[OriginationIndicator]
Type of calls MS is allowed to originate.
[Digits(Restriction)]
Selected NPA-NXX or NPA-NXX-XXXX
allowed for call origination as indicated in
OriginationIndicator.
R
[TerminationRestrictioncode]
Type of calls MS is allowed to terminate.
R
[SMS-OriginationRestrictions]
Defines the type of messages the MS is
allowed to originate.
R
[SMS-TerminationRestrictions]
Defines the type of messages the MS is
allowed to terminate.
R
R
G. The VLR sends an empty qualdir to the HLR
H. The VLR reports the change in the MS’s service profile by sending a QUALDIR to the Serving
MSC.
I. Upon receipt of the QUALDIR, the Serving MSC may discontinue any call or service in progress,
and sends an empty qualdir to the HLR
AA. The Local EIR is updated with the latest information on valid MEID assignments by the most
efficient method available. Today, an email is sent upon request with the information requested.
BB. The Local EIR synchronizes with the Central EIR database to update the black listed MEID data.
Qualcomm Confidential and Proprietary
xv
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.1.3 Deny Account with Black Listed Device
Use case: Deny account network access when the user attempts to use a device that has been
identified as a stolen. NOTE: Reauthorization is required via Customer Service agent/line.
AA
Equipment Registry
ESN
Tracker
MS
Local EIR
(Phase I)
Central EIR
BB
TIA MEID DB
Serving System
Provision
Server
HLR
VLR
MSC
A
B
C
D
E
F
G
H
I
Figure 5-3 Deny Account with Black Listed Device
If the operator desires to deny network access instead of placing restrictions, when a black
listed device is used to access the network the following procedures shall be supported:
A. EUIMID, MEID sent to ESN Tracker DB by device
B. ESN tracking message triggers ER logic
C. ER logic performs check: MEID format, MEID status (Black, Grey, White listed),
subscription account status (Restrict, Deny, Valid)
D. If result of above check requires, ER triggers an update of the MS’s service profile via
Provisioning Server, and it includes the MDN and UIMID.
E. The Provisioning Server updates the MS service profile at the HLR to deny the account.
Qualcomm Confidential and Proprietary
xvi
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
F. Per [1] Section 4.20 QualificationDirective, the HLR reports the change in the MS’s
service profile by sending a QUALDIR to the VLR where the MS is registered.
(Parameters: MIN, UIMID, MYTYP, QUALCODE, AUTHDEN, DENAUTHPER)
Parameters
Usage
Type
QUALCODE
AUTHDEN
DENAUTHPER
Type of qualification=validation only
Authorization denied indication with reason.
Indicates the duration of time the VLR should
retain a record and suppress re-registrations
for the authorization denied MS.
MBC
R
R
G. The VLR sends an empty qualdir to the HLR
H. Tthe VLR reports the change in the MS’s service profile by sending a QUALDIR to the
Serving MSC. (Parameters: MIN, UIMID, MYTYP, QUALCODE, AUTHDEN, LOCID)
I. Upon receipt of the QUALDIR, the Serving MSC may discontinue any call or service in
progress, and sends an empty qualdir to the HLR
AA. The Local EIR is updated with the latest information on valid MEID assignments by the most
efficient method available. Today, an email is sent upon request with the information requested.
BB. The Local EIR synchronizes with the Central EIR database to update the black listed MEID data.
Qualcomm Confidential and Proprietary
xvii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.1.4 Remove Account Restrictions via Customer Service Call
Use case: The user has had their account restricted, and chooses to call Customer Service to
get the issue resolved.
Equipment Registry
Customer
Service
Interface
AA
ESN
Tracker
Local EIR
(Phase I)
Central EIR
BB
TIA MEID DB
Serving System
Provision
Server
HLR
VLR
MSC
A
B
C
D
E
F
G
H
Figure 5-4 Re-authorize Restricted Account
If the operator desires to re-authorize network access for a user account, the following
procedures shall be supported:
A. Customer Service Agent (directly or via provisioning system) initiates re-authorization event for
MS, and updates the subcription account to remove restrictions.
B. The Provisioning System sends a trigger to ER that a subscription update has occurred.
C. ER logic resets MEID status (Grey, White listed), if applicable, and sets Subscription Account
Status to “Valid”
D. The Provisioning Server (PS) updates the MS service profile at the HLR to remove account
restictions.
Qualcomm Confidential and Proprietary
xviii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
NOTE: It is presumed that the MDN is passed to the PS, and a translation to MIN is done.
E. Per [1] Section 4.20 QualificationDirective, the HLR reports the change in the MS’s service profile
by sending a QUALDIR to the VLR where the MS is registered. (Parameters: MIN, ESN or UIMID,
MYTYP, QUALCODE, Profile)
Parameters
Usage
Type
MIN
ESN or UIMID
MYTYP
QUALCODE
Profile:
[CallingFeaturesIndicator]
Served MS MIN
Served MS ESN or UIMID
HLR vendor identification
Type of qualification=profile only
Subscriber's profile information:
Authorization and activity states for features.
R
R
MBC
MBC
R
[OriginationIndicator]
Type of calls MS is allowed to originate.
[Digits(Restriction)]
Selected NPA-NXX or NPA-NXX-XXXX
allowed for call origination as indicated in
OriginationIndicator.
R
[TerminationRestrictioncode]
Type of calls MS is allowed to terminate.
R
[SMS-OriginationRestrictions]
Defines the type of messages the MS is
allowed to originate.
R
[SMS-TerminationRestrictions]
Defines the type of messages the MS is
allowed to terminate.
R
R
F. The VLR sends an empty qualdir to the HLR
G. The VLR reports the change in the MS’s service profile by sending a QUALDIR to the Serving
MSC
H. Upon receipt of the QUALDIR, the Serving MSC may discontinue any call or service in progress,
and sends an empty qualdir to the HLR
AA. The Local EIR is updated with the latest information on valid MEID assignments by most efficient
method available. Today, an email is sent upon request with the information requested.
BB. The Local EIR synchronizes with the Central EIR database to update the black listed MEID data.
Qualcomm Confidential and Proprietary
xix
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.1.5 Query a Device: Based on Age of Record
Use case: The EIR record of a specific user account has not been updated for a configurable
amount of time, and the EIR sends an SMS-PP message to the subscriber to initiate an ESN
Tracker message.
AA
Equipment Registry
ESN
Tracker
MS
Central EIR
BB
TIA MEID DB
Local EIR
(Phase I)
SMSC
A
B
C
D
Figure 5-5 Query Device Based on Record Age
Qualcomm Confidential and Proprietary
xx
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
A. If the network and RUIM card supports it, the local EIR database performs a
check for records that have not been updated for a configurable amount of time
using Date of last record update and current Time of Day.
B. The local EIR sends an SMS message with a Teleservice ID of CATPT via the
SMSC.
C. The SMSC sends this SMS message to the subsciber device.
D. The subscriber devices sends an ESN Tracker message to the database.
5.1.6 Query a Device: Based on Empty Record
Use case: The ER record of a specific user account has never received an ESN Tracker report
for a configurable amount of time following activation of a new subscriber account, and the EIR
sends an SMS-PP message to the subscriber to initiate an ESN Tracker message.
Qualcomm Confidential and Proprietary
xxi
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
AA
Equipment Registry
ESN
Tracker
MS
Central EIR
BB
TIA MEID DB
Local EIR
(Phase I)
SMSC
A
B
C
D
Figure 5-6 Query Device with an Empty Record
A. If the network and RUIM card supports it, the local EIR database performs a
check for records that have not received any ESN Tracker messages for a
configurable amount of time as Date of record creation is not set and Account
Status is Valid.
B. The local EIR sends an SMS message with a Teleservice ID of CATPT via the
SMSC.
C. The SMSC sends this SMS message to the subsciber device.
Qualcomm Confidential and Proprietary
xxii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
D. The subscriber devices sends an ESN Tracker message to the database
5.2 Database (ER) Requirements
5.2.1. Depending on local government regulations, there shall be a database of all
registered devices and provisioned subscriptions that is maintained by the operator
within the network. (SYS-1)
5.2.2. There may be a central database (central-EIR) containing the following information for
device flagged as black listed accessible to all participating CDMA networks. (SYS-7)
a.
b.
c.
d.
e.
f.
ESN or MEID (as applicable)
Date of record creation
Date of last record update
MEID Status (White, Grey, Black)
MEID Status Reason (Invalid, Stolen, Cloned, Valid)
MEID Status Source (Local, Central)
5.2.3. If available, the central-EIR shall be accessible by all participating CDMA networks.
5.2.4. If available, the ER shall synchronize with the central EIR database on a configurable
periodic basis. (SYS-9)
5.2.5. At a minimum, the local database shall contain the following information for each
registered device: (SYS-2, SYS-5, SYS-6, SYS-12, SYS-13)
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
IMSI and/or MDN (as supported by ESN tracker)
ESN or MEID (as applicable)
EUIMID
Date of record creation
Date of last record update
Subscription Account Status (Restricted, Denied, Valid)
Device model number
Device software version
MEID Status (White, Grey, Black)
MEID Status Reason (Invalid, Stolen, Cloned, Valid)
MEID Status Source (Local, Central)
5.2.6. Whenever a new suscriber account is activated, the ER should allow the creation of a
new record in the ESN tracker database containing the IMSI.
5.2.7. If supported by the network, and MS, the database shall support sending a trigger
event to the network to query a device for the following two scenarios: Age of record
has reached a configurable time limit; the account has been activated for a
configurable time limit with no ESN Tracker event received.
5.2.8. The database shall support a flexible method of input (via manual entry of data, flat
file containing MEID range updates, future web portals for automatic updates) of
MEID format information as provided by either TIA or MSAI. (SYS-4)
5.2.9. The database shall perform a check on the MEID format to verify it is of a valid format
and range. (SYS-4)
Qualcomm Confidential and Proprietary
xxiii
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.2.10. The database shall perform a check on the reported MEID value to determine the
MEID status.
5.2.11. The database shall provide the Provisioning server with MDN and/or MIN in addition
to the UIMID when requesting profile changes to the subscription.
5.2.12. The local database shall provide the operator with an interface to gather
consumption and usage behavior for each registered device.
5.2.13. The local database shall provide the operator (Customer Service) with an interface
to change Subscription Account Status, MEID Status, and Device Status following
operator defined business rules.
5.3 Network Requirements
5.3.1. The network shall maintain a database of all registered devices when required by
local government regulations.
5.3.2. The network may support querying a subscriber for its device ESN or MEID through
already existing interfaces such as SMS-PP messages.
5.3.3. The network shall prevent or restrict use of available services if a registered device is
set to a MEID Status of black in the EIR database.
5.3.4. The network shall allow use of available services if a registered device is set to a
MEID Status of white or grey in the EIR database.
Qualcomm Confidential and Proprietary
xxiv
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
5.4 Interfaces
ER – CSI/Prov System interface
Work in progress
ER – SMSC interface
Work in progress
ER – CEIR interface
Work in progress
MS – ER interface
Work in progress
Qualcomm Confidential and Proprietary
xxv
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
6. Appendix
Qualcomm Confidential and Proprietary
xxvi
May contain U.S. and international export controlled information
Ошибка! Неизвестное имя свойства документа.
Contents
7. References
1. ANSI/TIA/EIA Standard 41-D, Cellular Radiotelecommunications Intersystem
Operation.
2. EIR Requirements v0.2
Qualcomm Confidential and Proprietary
xxvii
May contain U.S. and international export controlled information
1
Qualcomm Confidential and Proprietary
28
May contain U.S. and international export controlled information