Esn Tracking Tata

TTL ESN Tracking Application in RUIM based handsets
Document No. - CTT/Specifications/ESN Tracking/v3.3

Corporate Terminals Team

24
th
February, 2011
Tata Teleservices Limited

CDMA Terminals ESN Tracking
Application
Document CTT/Specifications/ESN Tracking/v3.3
Revision Version 3.3
Date

24th February, 2011

2
Table of Content

1. OBJECTIVE ......................................................................................................................................... 4
2. TERMS USED ...................................................................................................................................... 5
3. FEW IMPORTANT PARAMETERS ................................................................................................ 6
4. ESN TRACKING RELATED REQUIREMENTS............................................................................ 7
4.1 ESN TRACKING APPLICATION STEPS ............................................................................................ 7
4.2 SMS FORMAT ................................................................................................................................. 8
5. TRIGGERS EXPLAINED..................................................................................................................11
5.1 POWER-UP EVENT .........................................................................................................................11
5.2 MOBILE ORIGINATED SMS/VOICE CALL/DATA CALL EVENT ........................................................11
5.3 MOBILE TERMINATED SMS/VOICE CALL EVENT ..........................................................................11
5.4 UTK MENU SELECTION EVENT .....................................................................................................11
5.5 NETWORK INITIATED SMS EVENT ................................................................................................11
5.6 UTK MENU OPTION FROM RUIM CARD EVENT ............................................................................12
7. APPENDIX I: RUIM EF DETAILS ..................................................................................................14
7.1 EF_RUIM_ID ...............................................................................................................................14
7.2 EF_ME_ESN ...............................................................................................................................15
7.3 EF_SF_EUIMID...........................................................................................................................15
8. APPENDIX II: SAMPLE LOG FOR CATEGORY 1 TRIGGERS ...............................................16
9. APPENDIX III: SAMPLE LOGS FOR CATEGORY 2 TRIGGERS ............................................20
10. APPENDIX IV: ESN TRACKING APPLICATION FLOW ......................................................26

Application
Date

24th February, 2011

3
Revision History

Date Version Description
15
th
January 2007 1.0 Initial release
16
th
January 2007 2.0 Changed the SMS format

12
th
April 2007 3.0 Added MEID support
Added SMS Trigger for First MT Voice/SMS after activation
Flowchart added
ESN Tracking SMS version changed to V2

6
th
March 2009 3.1 Destination number changed from 3751 to 9223053751
Modification to Send SMS at invalid MIN check
Updated Logs
8
th
April 2009 3.2 Destination number changed from 9223053751
to 09223053751
Updated Sample Logs
24
th
February, 2011

3.3 Added additional triggers

References

Sr.
No
Version Standard
1 TTL Specification for ESN Tracking for RUIM
Card
TTL Document
2. TTL_Phone_Lock_Spec_Ver4.3 TTL Document
3. TIA-EIA/IS-637A
4. C.S0023 (Removable User Identity Module for
Spread Spectrum Systems)

Application
Date

24th February, 2011

4
1. Objective

The objective is to capture the serial number i.e. ESN/Pseudo-ESN/MEID of the RUIM based
devices so as to have a database of the RUIM_ID and ESN/Pseudo-ESN/MEID pair.

Few of the applications of this database are

To be able to identify a handset model
Identify user handset buying trend
Inventory management and other logistics

ESN tracking is a mandatory requirement for all RUIM based TTL devices.

Application
Date

24th February, 2011

5
2. Terms Used

EF 6F38 (ESN_ME): This EF stores the (up to) 56-bit Electronic Serial Number or MEID
or pseudo-ESN of the Mobile Equipment (ME) to which the RUIM is attached. This
number is transferred to the RUIM when the Mobile Equipment determines that the RUIM
has been inserted.
EF 6F31 (UIMID): This is the ID of the RUIM.
EF 6F42 (UIMID indicator): This indicator dictates whether ESN_ME or UIMID will be
used for CAVE. The value 0 indicates ESN_ME will be used, and the value 1 similarly
indicates UIMID will be used.
EF 6F74 (SF_EUIMID): This EF stores the 56-bit electronic identification number (ID)
unique to the R-UIM.
EF 6F22 (IMSI_M): This EF stores the five components of IMSI_M.( TIA-EIA/IS-820A)
Handset MEID Mobile Equipment Identifier (MEID). A 56-bit number assigned by the
mobile station manufacturer, uniquely identifying the mobile station equipment.
Pseudo-ESN - A 32 bit number derived from MEID and used in place of ESN.

Imp Note: ESN & RUIM_ID have been used generically throughout the document for
MEID/pESN & RUIM_MEID/pRUIM_ID. Depending on the handset support appropriate
unique identity MEID or pESN or RUIM_MEID or pRUIM_ID should be used.

Refer to Appendix for detailed description of the above-mentioned terms.

Application
Date

24th February, 2011

6
3. Few Important Parameters
Stored in the RUIM
RUIM_ID/RUIM_MEID/pRUIM_ID
IMSI_M
A-Key (Not accessible by the ME)
SSD (Not accessible by the ME)
COUNT (Not used currently)
Stored in the ME
ESN/MEID/pESN

Application
Date

24th February, 2011

7
4. ESN tracking related requirements

The TTL Handsets shall have a trigger based preloaded application residing on the terminal
software that will send the SMS with ME_ESN upon receipt of triggers. TTL has employed five
methods of triggering this ESN application to obtain ESN_ME.

Category 1:- Automatic
A) Power Up Event
B) Mobile Originated Voice call/SMS/Data call
C) Mobile Terminated Voice Call/SMS
D) UTK Menu Selection Event

Category 2:- On demand
A) UTK menu option from RUIM card
B) Network Initiated SMS

The application shall be a masked application (not visible on device UI) on the handset software
which will pick up the handset ESN/pESN/MEID & RUIM_ID/pRUIM_ID/MEID pair and send it as
a pre-formatted SMS to a pre-defined location. These SMSs will be sent when triggered by
particular events like Power Up, UTK Menu Selection, Mobile Originated Call/SMS/data call,
Mobile Terminated Call/SMS and Network Initiated SMS.

The UTK menu option from RUIM card will reside in RUIM card as UTK menu option Send
MEID which will be similar to other UTK menu option. On selection of UTK menu option by user,
the RUIM card will send ESN tracking sms with type UM which shall be blocked by MS
application and MS shall originate ESN tracking sms with the type UM.

The Tracking SMS shall be sent on all mentioned triggers. In case of failure, the application shall
try as per retry logic mentioned below.

The network-initiated trigger is independent of the other triggers and device shall send track SMS
as and when it receives NW trigger.

4.1 ESN Tracking Application Steps

Steps of execution of ESN Tracking application are as follow:

User switches ON the handset.

Device shall write its ESN/MEID during power on procedure on to RUIM EF ESN_ME.

The handset software shall read the IMSI_M check if its a valid MIN as defined in TATA
MIN range (TTL_Phone_Lock_Spec_Ver6.0).

a) If the MIN is ABOVE RANGE the terminals shall send the SMS.
b) If the MIN is BELOW RANGE the terminals shall send the SMS.
c) If the phone has a default MIN the phone shall not send an SMS until the phone
gets proper valid min after activation.

If any card with non-default MIN is inserted in the terminal then on Power-UP

Application
Date

24th February, 2011

8
a) The ESN Tracking Application will read the RUIM_ID and ESN_ME pair and
compare it to the previously stored RUIM_ID and ESN_ME pair. AND ONLY IF the
pair is not identical; the application shall send the ESN tracking message. Upon
receipt of L3 ACK, the PU flag shall be set.
b) If the SMS is not sent successfully i.e. the phone does not receive Layer 3
Acknowledgment the application should try to resend the SMS 3 times with an
interval of 20 sec for 2
nd
retry and a 30 sec delay for 3
rd
retry.
If failed thrice the application shall be disabled for this session and MS shall not
set the PU flag and shall try to send the PU ESN tracking SMS on next power on.
c) Application shall wait for other mentioned triggers and shall send ESN tracking sms
with respective type upon occurrence of respective event. The retry mechanism in
case of failure shall be same as for PU (refer point b).

4.2 SMS Format

Format and behavior of the SMS to be sent to the pre-defined location is described below.

The Terminal should send an SMS with the necessary information to the server without end users
knowledge.

The ME shall not display

1. The SMS message being sent to the server
2. Any Acknowledgement of the SMS received from the server. Even if Delivery
acknowledgement is on in sms setting, it shall not send Dack=1 while sending ESN track
sms.

The SMS shall be sent to 09223053751 and the encoding technique used shall be 7 bit ASCII,
independent of the ME language mode.

The format of the SMS shall be as follows:

Keyword TRACK<space>Card Vendor code XXXXXX<space>Handset Vendor name
ABCDEFGHIJ<space>Handset Vendor Model No.KLMNOPQRST<space>Type of SMS
UV<space>RUIM_IDRUIM_ID:<space>xxxxxxxxxxxxxx<space>HandsetESNESN_ME:
<space>xxxxxxxxxxxxxx<space>SoftwareversionofhandsetXXXXXXXXXXXXXXX<space>Versio
n YZ

Keywor
d
Card
Vendor
code
Handset
Vendor name
Handset
Vendor
Model No.
Type
of
SMS
RUIM_ID/
RUIM_M
EID
ESN_ME Software
Version
of
handset
Versi
on

5 digits 6 digits 10 digits 10 digits 2
digits
14 digits 14 digits 15 digits 2
digits
TRACK XXXX
XX
ABCDEFGHIJ KLMNOPQR
ST
UV xxxxxxxxx
xxxxx
xxxxxxxx
xxxxxx
xxxxxxx
xxxxxxx
x
YZ

Application
Date

24th February, 2011

9
TRACK FFFFFF MOTOROLAF
F
MOTO123FF
F
PU A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3
TRACK FFFFFF SAMSUNGFF
F
SCHB529FFF OS/O
V/OD
A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3
TRACK FFFFFF OLIVEFFFFF OLC2040 FFF TS/T
V
A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3
TRACK FFFFFF HUAWEIFFF
F
HWC2830
FFF
UT A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3
TRACK FFFFFF ZTEFFFFFFF ZTES185FFF UM A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3
TRACK FFFFFF SAMSUNGFF
F
SCHB529
FFF
NW A1000AB5
600002
A1000AB
5600000
HAC500
MRT01F
FFF
V3

XXXXXXX Card Vendor code Keep this as FFFFFF by default.

ABCDEFGHIJ Handset Vendor name This should be Handset manufacturer name. If
Vendor name less than 10 characters please suffix FF. For e.g. Olive is 5 characters so the
vendor name will be OLIVEFFFFF

KLMNOPQRST Handset Vendor Model No. - This should be 10 characters Model name of
device. If less than 10 characters please suffix FF For instance MOTOW210FF, SCHB529FFF
etc

UV Type of SMS PU signifies-- Power Up
OS/OV/OD signifiesMobile Originated SMS (OS) /Voice call
(OV)/ Data Call (OD)
TS/TV signifiesMobile Terminated SMS (TS)/Voice call
(TV)
UT signifiesUTK Menu selection
NW signifies-- Network Initiated
UM signifies-- UTK Menu option from RUIM card

RUIM_ID: Device shall read RUIM_ID from EF 6F74 of RUIM card. Length shall be 8 digits for
ESN and 14 Hex digits for MEID. In case of ESN FF shall be padded to make the length of 14
hex digits.

ESN_ME: ESN/ MEID of the device. Length shall be 8 digits for ESN and 14 Hex digits for MEID.
In case of ESN FF shall be padded to make the length of 14 hex digits.

Software version of handset: This should be 15 characters software version of handset. If less
than 15 characters please suffix FF. e.g: HAC500MRT01FFFF.

YZ Version e.g. V1, V2, V3

Application
Date

24th February, 2011

10

For e.g. SMS that will be sent out

In case of power up would be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF PU RUIM_ID: A1000AB5600002 ESN_ME:
A1000AB5600000 HAC500MRT01FFFF V3

In case of Network Initiated SMS shall be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF NW RUIM_ID: A1000AB5600002 ESN_ME:
A1000AB5600000 HAC6000DT01FFFF V3

In case of MO SMS/CALL/DATA SMS shall be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF OS/OV/OD RUIM_ID: A1000AB5600002
ESN_ME: A1000AB5600000 HAC6000DT01FFFF V3

In case of MT SMS/CALL SMS shall be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF TS/TV RUIM_ID: A1000AB5600002
ESN_ME: A1000AB5600000 HAC6000DT01FFFF V3

In case of UTK Menu selection shall be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF UT RUIM_ID: A1000AB5600002 ESN_ME:
A1000AB5600000 HAC6000DT01FFFF V3

In case of UTK Menu option from RUIM card shall be:
TRACK FFFFFF SAMSUNGFFF SCHB529FFF UM RUIM_ID: A1000AB5600002 ESN_ME:
A1000AB5600000 HAC6000DT01FFFF V3

Note:
The format of the ESN & RUIM ID should be in HEX.
The order of the ESN & RUIM ID should be as displayed on the Handset & RUIM Card
(The ESN and UIM_ID are stored in reversed order in RUIM Elementary Files) i.e. should
be sent in proper order.
The Number of characters to be sent in SMS shall be 103 characters i.e. NUM FIELD of the
User Data in Data Burst message should be 103.
The whole content of ESN track SMS shall be in capitals.

Responsibility for re-trying lies with the Application. If a valid response is not received within
stipulated time or receives negative acknowledgement the Application should re-send the SMS
three times and set the counter or flag internally to indicate that SMS sending had failed and will
be re-sent on next power on. Separate flags for all triggers shall be maintained independently.

Application
Date

24th February, 2011

11
5. Triggers Explained

Following are the triggers:

A) Power Up Event
B) Mobile Originated SMS/Voice call/Data Event
C) Mobile Terminated SMS/Voice call Event
D) UTK Menu selection Event
E) Network Initiated SMS Event
F) UTK Menu option from RUIM card Event

Details are described as below:

5.1 Power-up Event

The Power-Up event shall be used as the trigger to the application to send the ESN tracking sms
with type PU.

5.2 Mobile Originated SMS/Voice call/Data Call Event

The device shall use first MO SMS/Voice call/Data call event as trigger with SMS tyoe as below:
MO SMS shall use keyword as OS,
MO voice shall use keyword as OV,
MO Data call shall use keyword as OD.
Any of the above event (whichever occurs first) shall be used as trigger and if sent successfully
device shall set the flag as sms sent else shall retry thrice and set the flag as not sent and shall
wait for remaining Mobile originated events.

5.3 Mobile Terminated SMS/Voice call Event

The device shall use first MT SMS/Voice call event as trigger with SMS type as below:
MT SMS shall use keyword as TS,
MT voice shall use keyword as TV.

Any of the above event (whichever occurs first) shall be used as trigger and if sent successfully
device shall set the flag as sms sent else shall retry thrice and set the flag as not sent and shall
wait for remaining Mobile terminated events.

5.4 UTK Menu Selection Event

Whenever the User selects UTK Menu, this Event shall be used as a trigger to send ESN tracking
sms with type UT. If sent successfully device shall set the flag as sms sent else shall follow retry
mechanism. The ESN tracking application from RUIM card must be blocked by device.

5.5 Network Initiated SMS Event

In this event the handset receives an SMS from network (Refer APPENDIX III) requesting the
ESN.

On receiving this SMS the Handset shall check the originating address ending with 121, user
data ESN and Message Display sub parameter to send NW initiated ESN tracking SMS.

Application
Date

24th February, 2011

12

The ME shall not display

1. SMS message received from the server.
2. SMS shall not be saved in the Inbox.

RESERVED - The RSERVED bits can have following values:

MSG_DISPLAY_MODE (2
Bits)
RESERVED
(6 Bits)
Remarks
11 10 00 00 SMS PP-Download (VAS)
11 11 00 00 PRL UPDATE are enabled by PP-
Download
11 01 00 00 PRL UPDATE are enabled

The Backend server shall use RESERVED value 10 00 00 to indicate to the ME that it is a
Network Initiated ESN Tracking trigger.

5.6 UTK Menu option from RUIM card Event

On selection of SEND MEID menu from UTK, the RUIM card will initiate the SMS with type
UM, the device shall treat this SMS as a trigger to send UM type ESN tracking SMS from its
application. If sent successfully device shall set the flag as sms sent else shall follow retry
mechanism.

Application
Date

24th February, 2011

13
6. Conflict

TTL RUIM Cards also have the same trigger based ESN Tracking preloaded application residing
on the card, which will send the SMS to an 11 Digit Destination Number 09223053751 with
ESN_ME upon receipt of the similar triggers. The device shall parse the PDU from RUIM card to
detect the SMS with destination address as 09223503751 and content TRACK to block the
RUIM initiated ESN Tracking SMS.

Simultaneous events may occur which can also result in trigger conflict, In such case the triggers
shall be handled on first come first serve basis.

The delay between SMSs of 2 triggers shall be 30 sec.

Application
Date

24th February, 2011

14
7. Appendix I: RUIM EF details

7.1 EF_RUIM_ID

Application
Date

24th February, 2011

15
7.2 EF_ME_ESN

7.3 EF_SF_EUIMID

Application
Date

24th February, 2011

16
8. Appendix II: Sample log for Category 1 triggers

SMS Sent from Handset on triggers (Power-up /Menu Selection/SMS PP)

RecNo : 517 : 03/04/2009 12:37:20.261 : Short Message Services (LOG_CODE 0x1005)

State Variables: BAND_CLASS=1 MOB_P_REV=6 P_REV=6 P_PREV_IN_USE=6

Reverse Channel Traffic Message
Record_Header
RECORD_LENGTH Raw=(107) byte
LOG_CODE Raw=(4101) 0x1005
MESSAGE_TIMESTAMP Raw=(48245266986369088) 12:37:20.261
MSG_LENGTH Raw=(95) 95 byte
MSG_TYPE Raw=(4) Data Burst Message
SDU_AND_PDU_PADDING_LENGTH Raw=(728) 728 bits
Data Burst Message
FDSCH_LAYER2_BEG_FIELDS
ACK_SEQ Raw=(2)
MSG_SEQ Raw=(2)
ACK_REQ Raw=(1)
ENCRYPTION Raw=(0)
DATA_BURST_MESSAGE
MSG_NUMBER Raw=(1)
BURST_TYPE Raw=(3) Short Message Services
NUM_MSGS Raw=(1)
NUM_FIELDS Raw=(86)
Short Message Services
SMS_MSG_TYPE Raw=(0) Point-to-Point
SMS Point-to-Point
SMS_DATA_BURST_PAYLOAD

PARAMETER_ID Raw=(0) Teleservice Identifier
PARAMETER_LEN Raw=(2)
Teleservice Indentifier
IDENTIFIER Raw=(4098) CDMA Cellular Messaging Teleservice
PARAMETER_ID Raw=(4) Destination Address
Destination Address
DIGIT_MODE Raw=(0)
NUMBER_MODE Raw=(0)
NUM_FIELDS Raw=(11)

CHARi Raw=(10) 0
CHARi Raw=(9) 9
CHARi Raw=(2) 2
CHARi Raw=(2) 2
CHARi Raw=(3) 3
CHARi Raw=(10) 0

Application
Date

24th February, 2011

17
CHARi Raw=(5) 5
CHARi Raw=(3) 3
CHARi Raw=(7) 7
CHARi Raw=(5) 5
CHARi Raw=(1) 1
Reserved Raw=(0)

PARAMETER_ID Raw=(6) Bearer Reply Option
Bearer Reply Option
REPLY_SEQ Raw=(0)
RESERVED Raw=(0)
PARAMETER_ID Raw=(8) Bearer Data
Bearer Data
SUBPARAMETER_ID Raw=(0) Message Identifier
SUBPARAM_LEN Raw=(3)

Message Identifier
MESSAGE_TYPE Raw=(2) Submit
MESSAGE_ID Raw=(488)
HEADER_IND Raw=(0)
SUBPARAMETER_ID Raw=(1) User Data

User Data
msg_encoding = 2 (0x2) (7-bit ASCII - 7 bits)
num_fields = 103 (0x67)
sm_tp_user_data_ascii_7
user_data_7_bit[0] = 84 (0x54) ('T')
user_data_7_bit[1] = 82 (0x52) ('R')
user_data_7_bit[2] = 65 (0x41) ('A')
user_data_7_bit[3] = 67 (0x43) ('C')
user_data_7_bit[4] = 75 (0x4b) ('K')
user_data_7_bit[5] = 32 (0x20) (' ')
user_data_7_bit[6] = 79 (0x4f) ('F')
user_data_7_bit[7] = 67 (0x43) ('F')
user_data_7_bit[8] = 83 (0x53) ('F')
user_data_7_bit[9] = 79 (0x4f) ('F')
user_data_7_bit[10] = 77 (0x4d) ('F')
user_data_7_bit[11] = 72 (0x48) ('F')
user_data_7_bit[12] = 32 (0x20) (' ')
user_data_7_bit[13] = 70 (0x46) ('M')
user_data_7_bit[14] = 70 (0x46) ('O')
user_data_7_bit[15] = 70 (0x46) ('T')
user_data_7_bit[16] = 70 (0x46) ('O')
user_data_7_bit[17] = 70 (0x46) ('R')
user_data_7_bit[18] = 70 (0x46) ('O')
user_data_7_bit[19] = 70 (0x46) ('L')
user_data_7_bit[20] = 70 (0x46) ('A')
user_data_7_bit[21] = 70 (0x46) ('F')
user_data_7_bit[22] = 70 (0x46) ('F')

Application
Date

24th February, 2011

18
user_data_7_bit[23] = 32 (0x20) (' ')
user_data_7_bit[24] = 70 (0x46) ('M')
user_data_7_bit[25] = 70 (0x46) ('O')
user_data_7_bit[26] = 70 (0x46) ('T')
user_data_7_bit[27] = 70 (0x46) ('O')
user_data_7_bit[28] = 70 (0x46) ('W')
user_data_7_bit[29] = 70 (0x46) ('2')
user_data_7_bit[30] = 70 (0x46) ('1')
user_data_7_bit[31] = 70 (0x46) ('0')
user_data_7_bit[32] = 70 (0x46) ('F')
user_data_7_bit[33] = 70 (0x46) ('F')
user_data_7_bit[34] = 32 (0x20) (' ')
user_data_7_bit[35] = 80 (0x50) ('P')
user_data_7_bit[36] = 85 (0x55) ('U')
user_data_7_bit[37] = 32 (0x20) (' ')
user_data_7_bit[38] = 82 (0x52) ('R')
user_data_7_bit[39] = 85 (0x55) ('U')
user_data_7_bit[40] = 73 (0x49) ('I')
user_data_7_bit[41] = 77 (0x4d) ('M')
user_data_7_bit[42] = 95 (0x5f) ('_')
user_data_7_bit[43] = 73 (0x49) ('I')
user_data_7_bit[44] = 68 (0x44) ('D')
user_data_7_bit[45] = 58 (0x3a) (':')
user_data_7_bit[46] = 32 (0x20) (' ')
user_data_7_bit[47] = 65 (0x41) ('A')
user_data_7_bit[48] = 49 (0x31) ('1')
user_data_7_bit[49] = 48 (0x30) ('0')
user_data_7_bit[50] = 48 (0x30) ('0')
user_data_7_bit[51] = 48 (0x30) ('0')
user_data_7_bit[52] = 48 (0x30) ('0')
user_data_7_bit[53] = 49 (0x31) ('1')
user_data_7_bit[54] = 49 (0x31) ('1')
user_data_7_bit[55] = 57 (0x39) ('9')
user_data_7_bit[56] = 65 (0x41) ('A')
user_data_7_bit[57] = 65 (0x41) ('A')
user_data_7_bit[58] = 69 (0x45) ('E')
user_data_7_bit[59] = 53 (0x35) ('5')
user_data_7_bit[60] = 54 (0x36) ('6')
user_data_7_bit[61] = 32 (0x20) (' ')
user_data_7_bit[62] = 69 (0x45) ('E')
user_data_7_bit[63] = 83 (0x53) ('S')
user_data_7_bit[64] = 78 (0x4e) ('N')
user_data_7_bit[65] = 95 (0x5f) ('_')
user_data_7_bit[66] = 77 (0x4d) ('M')
user_data_7_bit[67] = 69 (0x45) ('E')
user_data_7_bit[68] = 58 (0x3a) (':')
user_data_7_bit[69] = 32 (0x20) (' ')
user_data_7_bit[70] = 65 (0x41) ('A')
user_data_7_bit[71] = 48 (0x30) ('0')
user_data_7_bit[72] = 48 (0x30) ('0')
user_data_7_bit[73] = 48 (0x30) ('0')
user_data_7_bit[74] = 48 (0x30) ('0')

Application
Date

24th February, 2011

19
user_data_7_bit[75] = 48 (0x30) ('0')
user_data_7_bit[76] = 49 (0x31) ('1')
user_data_7_bit[77] = 55 (0x37) ('7')
user_data_7_bit[78] = 67 (0x43) ('C')
user_data_7_bit[79] = 65 (0x41) ('A')
user_data_7_bit[80] = 50 (0x32) ('2')
user_data_7_bit[81] = 54 (0x36) ('6')
user_data_7_bit[82] = 67 (0x43) ('C')
user_data_7_bit[83] = 67 (0x43) ('C')
user_data_7_bit[84] = 32 (0x20) (' ')
user_data_7_bit[85] = 70 (0x46) ('M')
user_data_7_bit[86] = 70 (0x46) ('O')
user_data_7_bit[87] = 70 (0x46) ('T')
user_data_7_bit[88] = 70 (0x46) ('O')
user_data_7_bit[89] = 70 (0x46) ('W')
user_data_7_bit[90] = 70 (0x46) ('2')
user_data_7_bit[91] = 70 (0x46) ('1')
user_data_7_bit[92] = 70 (0x46) ('0')
user_data_7_bit[93] = 70 (0x46) ('M')
user_data_7_bit[94] = 70 (0x46) ('R')
user_data_7_bit[95] = 70 (0x46) ('T')
user_data_7_bit[96] = 70 (0x46) ('0')
user_data_7_bit[97] = 70 (0x46) ('1')
user_data_7_bit[98] = 70 (0x46) ('F')
user_data_7_bit[99] = 70 (0x46) ('F')
user_data_7_bit[100] = 32 (0x20) (' ')
user_data_7_bit[101] = 86 (0x56) ('V')
user_data_7_bit[102] = 49 (0x31) ('3')

Application
Date

24th February, 2011

20
9. Appendix III: Sample Logs for category 2 triggers

Sample Log: Network Initiated SMS serving as a trigger to send the ESN SMS.



Paging Channel Message
Record_Header
RECORD_LENGTH Raw=(59) byte
LOG_CODE Raw=(4103) 0x1007
MESSAGE_TIMESTAMP Raw=(48245229906597056) 12:25:33.020
MSG_LENGTH Raw=(47) 47 byte
PD Raw=(0)
MSG_ID Raw=(9)
SDU_AND_PDU_PADDING_LENGTH Raw=(330) 330 bits
Data Burst Message
FCSCH_LAYER2_BEG_FIELDS
FCSCH_LAYER2_ARQ_FIELDS
ACK_SEQ Raw=(0)
MSG_SEQ Raw=(0)
ACK_REQ Raw=(1)
VALID_ACK Raw=(0)
FCSCH_LAYER2_ADDR_FIELDS
ADDR_TYPE Raw=(2) IMSI
ADDR_LEN Raw=(5)
IMSI_CLASS Raw=(0)

IMSI_CLASS_0_TYPE
IMSI_CLASS_0_TYPE Raw=(0) IMSI_S included
RESERVED Raw=(0)
IMSI_S
IMSI_S Raw=(16348451977) (085) 565-5248
IMSI_S2 Raw=((085)) (085)
IMSI_S1 Raw=(565-5248) 565-5248
DATA_BURST_MESSAGE
MSG_NUMBER Raw=(1)
BURST_TYPE Raw=(3) Short Message Services
NUM_MSGS Raw=(1)
NUM_FIELDS Raw=(30)
Short Message Services
SMS_MSG_TYPE Raw=(0) Point-to-Point
SMS Point-to-Point
SMS_DATA_BURST_PAYLOAD
PARAMETER_ID Raw=(0) Teleservice Identifier
Teleservice Indentifier
IDENTIFIER Raw=(4098) CDMA Cellular Messaging Teleservice
PARAMETER_ID Raw=(2) Originating Address

Application
Date

24th February, 2011

21
Originating Address
DIGIT_MODE Raw=(0)
NUMBER_MODE Raw=(0)
NUM_FIELDS Raw=(3)
CHARi Raw=(1) 1
CHARi Raw=(2) 2
CHARi Raw=(1) 1
PARAMETER_ID Raw=(8) Bearer Data
Bearer Data
SUBPARAMETER_ID Raw=(0) Message Identifier
Message Identifier
MESSAGE_TYPE Raw=(1) Deliver
MESSAGE_ID Raw=(0)
HEADER_IND Raw=(0)
SUBPARAMETER_ID Raw=(15) Message Display Mode
Message Display Mode
MSG_DISPLAY_MODE Raw=(3) 3
RESERVED_DISP_MODE_6_BITS = 32 (0x20)
SUBPARAMETER_ID Raw=(1) User Data
User Data
MSG_ENCODING Raw=(0) SMS-Based MS-MPC protocol
NUM_FIELDS Raw=(3)
CHARi Raw=(69) [0x45] E
CHARi Raw=(83) [0x53] S
CHARi Raw=(78) [0x4e] N
SUBPARAMETER_ID Raw=(6) Deferred Delivery Time - Absolute
Deferred Delivery Time - Absolute
SMS_DATE_AND_TIME
YEAR Raw=(200) 2000
MONTH Raw=(--)

Application
Date

24th February, 2011

22

The MS sends the ESN Tracking SMS

Sample Log: SMS Sent from Handset on Network Initiated SMS trigger



Reverse Channel Traffic Message
protocol_rev = 6 (0x6) (IS2000 Rev 0)
chan_type = 4 (0x4) (Reverse Traffic)
chan
rtc_msg
gen
msg_type = 4 (0x4) (Data Burst)
rtc_burst
hdr
ack_seq = 2 (0x2)
msg_seq = 1 (0x1)
ack_req = 1 (0x1)
encryption = 0 (0x0)
msg_number = 1 (0x1)
burst_type = 3 (0x3)
num_msgs = 1 (0x1)
burst_data
sms_msg
sms_msg_type = 0 (0x0) (SMS Point-to-Point)
num_parms = 3 (0x3)
sms_parms[0]
sms_pp_parms
parameter_id = 0 (0x0) (Teleservice Identifier)
teleservice_id
telesvc_id = 4098 (0x1002) (CDMA Cellular Messaging Teleservice)
sms_parms[1]
sms_pp_parms
digit_mode = 0 (0x0)
number_mode = 0 (0x0)
num_fields = 11 (0xb)
sms_digit[0] = 10 (0xa) (0)
sms_digit[1] = 9 (0x9) (9)
sms_digit[2] = 2 (0x2) (2)
sms_digit[3] = 2 (0x2) (2)
sms_digit[4] = 3 (0x3) (3)
sms_digit[5] = 10 (0xa) (0)
sms_digit[6] = 5 (0x5) (5)
sms_digit[7] = 3 (0x3) (3)
sms_digit[8] = 7 (0x7) (7)
sms_digit[9] = 5 (0x5) (5)
sms_digit[10] = 1 (0x1) (1)

Application
Date

24th February, 2011

23
sms_parms[2]
sms_pp_parms
parameter_id = 8 (0x8) (Bearer Data)
bearer_data
header_ind = 0 (0x0)
num_subparms = 2 (0x2)
bd[0]
subparameter_id = 0 (0x0) (Message Identifier)
message_identifier
message_type = 2 (0x2) (Submit)
message_id = 18 (0x12)
bd[1]
subparameter_id = 1 (0x1) (User Data)
user_data
msg_encoding = 2 (0x2) (7-bit ASCII - 7 bits)
num_fields = 103 (0x67)
sm_tp_user_data_ascii_7
user_data_7_bit[0] = 84 (0x54) ('T')
user_data_7_bit[1] = 82 (0x52) ('R')
user_data_7_bit[2] = 65 (0x41) ('A')
user_data_7_bit[3] = 67 (0x43) ('C')
user_data_7_bit[4] = 75 (0x4b) ('K')
user_data_7_bit[5] = 32 (0x20) (' ')
user_data_7_bit[6] = 79 (0x4f) ('F')
user_data_7_bit[7] = 67 (0x43) ('F')
user_data_7_bit[8] = 83 (0x53) ('F')
user_data_7_bit[9] = 79 (0x4f) ('F')
user_data_7_bit[10] = 77 (0x4d) ('F')
user_data_7_bit[11] = 72 (0x48) ('F')
user_data_7_bit[12] = 32 (0x20) (' ')
user_data_7_bit[13] = 70 (0x46) ('M')
user_data_7_bit[14] = 70 (0x46) ('O')
user_data_7_bit[15] = 70 (0x46) ('T')
user_data_7_bit[16] = 70 (0x46) ('O')
user_data_7_bit[17] = 70 (0x46) ('R')
user_data_7_bit[18] = 70 (0x46) ('O')
user_data_7_bit[19] = 70 (0x46) ('L')
user_data_7_bit[20] = 70 (0x46) ('A')
user_data_7_bit[21] = 70 (0x46) ('F')
user_data_7_bit[22] = 70 (0x46) ('F')
user_data_7_bit[23] = 32 (0x20) (' ')
user_data_7_bit[24] = 70 (0x46) ('M')
user_data_7_bit[25] = 70 (0x46) ('O')
user_data_7_bit[26] = 70 (0x46) ('T')
user_data_7_bit[27] = 70 (0x46) ('O')
user_data_7_bit[28] = 70 (0x46) ('W')
user_data_7_bit[29] = 70 (0x46) ('2')
user_data_7_bit[30] = 70 (0x46) ('1')
user_data_7_bit[31] = 70 (0x46) ('0')
user_data_7_bit[32] = 70 (0x46) ('F')
user_data_7_bit[33] = 70 (0x46) ('F')
user_data_7_bit[34] = 32 (0x20) (' ')

Application
Date

24th February, 2011

24
user_data_7_bit[35] = 80 (0x50) ('N')
user_data_7_bit[36] = 85 (0x55) ('W')
user_data_7_bit[37] = 32 (0x20) (' ')
user_data_7_bit[38] = 82 (0x52) ('R')
user_data_7_bit[39] = 85 (0x55) ('U')
user_data_7_bit[40] = 73 (0x49) ('I')
user_data_7_bit[41] = 77 (0x4d) ('M')
user_data_7_bit[42] = 95 (0x5f) ('_')
user_data_7_bit[43] = 73 (0x49) ('I')
user_data_7_bit[44] = 68 (0x44) ('D')
user_data_7_bit[45] = 58 (0x3a) (':')
user_data_7_bit[46] = 32 (0x20) (' ')
user_data_7_bit[47] = 65 (0x41) ('A')
user_data_7_bit[48] = 49 (0x31) ('1')
user_data_7_bit[49] = 48 (0x30) ('0')
user_data_7_bit[50] = 48 (0x30) ('0')
user_data_7_bit[51] = 48 (0x30) ('0')
user_data_7_bit[52] = 48 (0x30) ('0')
user_data_7_bit[53] = 49 (0x31) ('1')
user_data_7_bit[54] = 49 (0x31) ('1')
user_data_7_bit[55] = 57 (0x39) ('9')
user_data_7_bit[56] = 65 (0x41) ('A')
user_data_7_bit[57] = 65 (0x41) ('A')
user_data_7_bit[58] = 69 (0x45) ('E')
user_data_7_bit[59] = 53 (0x35) ('5')
user_data_7_bit[60] = 54 (0x36) ('6')
user_data_7_bit[61] = 32 (0x20) (' ')
user_data_7_bit[62] = 69 (0x45) ('E')
user_data_7_bit[63] = 83 (0x53) ('S')
user_data_7_bit[64] = 78 (0x4e) ('N')
user_data_7_bit[65] = 95 (0x5f) ('_')
user_data_7_bit[66] = 77 (0x4d) ('M')
user_data_7_bit[67] = 69 (0x45) ('E')
user_data_7_bit[68] = 58 (0x3a) (':')
user_data_7_bit[69] = 32 (0x20) (' ')
user_data_7_bit[70] = 65 (0x41) ('A')
user_data_7_bit[71] = 48 (0x30) ('0')
user_data_7_bit[72] = 48 (0x30) ('0')
user_data_7_bit[73] = 48 (0x30) ('0')
user_data_7_bit[74] = 48 (0x30) ('0')
user_data_7_bit[75] = 48 (0x30) ('0')
user_data_7_bit[76] = 49 (0x31) ('1')
user_data_7_bit[77] = 55 (0x37) ('7')
user_data_7_bit[78] = 67 (0x43) ('C')
user_data_7_bit[79] = 65 (0x41) ('A')
user_data_7_bit[80] = 50 (0x32) ('2')
user_data_7_bit[81] = 54 (0x36) ('6')
user_data_7_bit[82] = 67 (0x43) ('C')
user_data_7_bit[83] = 67 (0x43) ('C')
user_data_7_bit[84] = 32 (0x20) (' ')
user_data_7_bit[85] = 70 (0x46) ('M')
user_data_7_bit[86] = 70 (0x46) ('O')

Application
Date

24th February, 2011

25
user_data_7_bit[87] = 70 (0x46) ('T')
user_data_7_bit[88] = 70 (0x46) ('O')
user_data_7_bit[89] = 70 (0x46) ('W')
user_data_7_bit[90] = 70 (0x46) ('2')
user_data_7_bit[91] = 70 (0x46) ('1')
user_data_7_bit[92] = 70 (0x46) ('0')
user_data_7_bit[93] = 70 (0x46) ('M')
user_data_7_bit[94] = 70 (0x46) ('R')
user_data_7_bit[95] = 70 (0x46) ('T')
user_data_7_bit[96] = 70 (0x46) ('0')
user_data_7_bit[97] = 70 (0x46) ('1')
user_data_7_bit[98] = 70 (0x46) ('F')
user_data_7_bit[99] = 70 (0x46) ('F')
user_data_7_bit[100] = 32 (0x20) (' ')
user_data_7_bit[101] = 86 (0x56) ('V')
user_data_7_bit[102] = 49 (0x31) ('3')

Application
Date

24th February, 2011

26
10. Appendix IV: ESN tracking application flow

Esn Tracking Tata

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Esn Tracking Tata

Hochgeladen von

Copyright:

Verfügbare Formate

TTL ESN Tracking Application in RUIM based handsets

Document No. - CTT/Specifications/ESN Tracking/v3.3

Das könnte Ihnen auch gefallen