Esn Tracking Tata

8/10/2019 Esn Tracking Tata

1/26

TTL ESN Tracking Application in RUIM based handsets

Document No. - CTT/Specifications/ESN Tracking/v3.3Corporate Terminals Team

24thFebruary, 2011

Tata Teleservices Limited


2/26

CDMA TerminalsESN 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 ESNTRACKINGAPPLICATION STEPS ............................................................................................ 74.2 SMSFORMAT ................................................................................................................................. 8

5. TRIGGERS EXPLAINED..................................................................................................................11

5.1 POWER-UP EVENT .........................................................................................................................115.2

MOBILE ORIGINATED SMS/VOICE CALL/DATA CALL EVENT ........................................................11

5.3

MOBILE TERMINATED SMS/VOICE CALL EVENT ..........................................................................115.4 UTKMENU SELECTION EVENT .....................................................................................................11

5.5 NETWORK INITIATED SMSEVENT ................................................................................................115.6 UTKMENU OPTION FROM RUIMCARD EVENT ............................................................................12

7. APPENDIX I: RUIM EF DETAILS ..................................................................................................14

7.1 EF_RUIM_ID ...............................................................................................................................147.2 EF_ME_ESN ...............................................................................................................................157.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


3/26


Application




3

Revision History

Date Version Description15tJanuary 2007 1.0 Initial release

16tJanuary 2007 2.0 Changed the SMS format

12tApril 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

6tMarch 2009 3.1 Destination number changed from 3751 to 9223053751

Modification to Send SMS at invalid MIN check

Updated Logs

8tApril 2009 3.2 Destination number changed from 9223053751

to 09223053751Updated Sample Logs

24tFebruary, 2011 3.3 Added additional triggers

References

Sr.No

Version Standard

1 TTL Specification for ESN Tracking for RUIMCard

TTL Document

2. TTL_Phone_Lock_Spec_Ver4.3 TTL Document

3. TIA-EIA/IS-637A

4. C.S0023 (Removable User Identity Module forSpread Spectrum Systems)


4/26


Application




4

1. Objective

The objective is to capture the serial number i.e. ESN/Pseudo-ESN/MEID of the RUIM baseddevices 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.


5/26


Application




5

2. Terms Used

EF 6F38 (ESN_ME): This EF stores the (up to) 56-bit Electronic Serial Number or MEIDor pseudo-ESN of the Mobile Equipment (ME) to which the RUIM is attached. Thisnumber is transferred to the RUIM when the Mobile Equipment determines that the RUIMhas 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 beused for CAVE. The value 0 indicates ESN_ME will be used, and the value 1 similarlyindicates 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 themobile 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 forMEID/pESN & RUIM_MEID/pRUIM_ID. Depending on the handset support appropriateunique identity MEID or pESN or RUIM_MEID or pRUIM_ID should be used.

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


6/26


Application




6

3. Few Important Parameters

Stored in the RUIM

RUIM_ID/RUIM_MEID/pRUIM_IDIMSI_MA-Key (Not accessible by the ME)SSD (Not accessible by the ME)COUNT (Not used currently)

Stored in the ME

ESN/MEID/pESN


7/26


Application




7

4. ESN tracking related requirements

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

Category 1:- AutomaticA) Power Up EventB) Mobile Originated Voice call/SMS/Data callC) Mobile Terminated Voice Call/SMSD) UTK Menu Selection Event

Category 2:- On demandA) UTK menu option from RUIM cardB) Network Initiated SMS

The application shall be a masked application (not visible on device UI) on the handset softwarewhich will pick up the handset ESN/pESN/MEID & RUIM_ID/pRUIM_ID/MEID pair and send it asa pre-formatted SMS to a pre-defined location. These SMSs will be sent when triggered byparticular 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 SendMEIDwhich 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 MSapplication 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 shalltry as per retry logic mentioned below.

The network-initiated trigger is independent of the other triggers and device shall send track SMSas 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 TATAMIN 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


8/26


Application




8

a) The ESN Tracking Application will read the RUIM_ID and ESN_ME pair andcompare it to the previously stored RUIM_ID and ESN_ME pair. AND ONLY IF thepair is not identical; the application shall send the ESN tracking message. Uponreceipt 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 3Acknowledgment the application should try to resend the SMS 3 times with aninterval of 20 sec for 2

ndretry and a 30 sec delay for 3

rdretry.

If failed thrice the application shall be disabled for this session and MS shall notset 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 smswith respective type upon occurrence of respective event. The retry mechanism incase 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 usersknowledge.

The ME shall not display

1. The SMS message being sent to the server2. 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 tracksms.

The SMS shall be sent to 09223053751and 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 TRACKCard Vendor code XXXXXXHandset Vendor name

ABCDEFGHIJHandset Vendor Model No.KLMNOPQRSTType of SMS

UVRUIM_IDRUIM_ID:xxxxxxxxxxxxxxHandsetESNESN_ME:

xxxxxxxxxxxxxxSoftwareversionofhandsetXXXXXXXXXXXXXXXVersio

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

ofhandset

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


9/26


Application




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 SAMSUNGFFF SCHB529FFF NW A1000AB5600002 A1000AB5600000 HAC500MRT01F

FFF

V3

XXXXXXX Card Vendor codeKeep this as FFFFFF by default.

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

vendor name will be OLIVEFFFFF

KLMNOPQRSTHandset 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 UpOS/OV/OD signifiesMobile Originated SMS (OS) /Voice call

(OV)/ Data Call (OD)TS/TV signifiesMobile Terminated SMS (TS)/Voice call

(TV)UT signifiesUTK Menu selectionNW signifies-- Network InitiatedUM 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 forESN 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 lessthan 15 characters please suffix FF. e.g:HAC500MRT01FFFF.

YZ Version e.g. V1, V2, V3


10/26


Application




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 NWRUIM_ID: A1000AB5600002 ESN_ME:A1000AB5600000 HAC6000DT01FFFF V3

In case of MO SMS/CALL/DATASMS shall be:

TRACK FFFFFF SAMSUNGFFF SCHB529FFF OS/OV/OD RUIM_ID: A1000AB5600002ESN_ME: A1000AB5600000 HAC6000DT01FFFF V3

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

In case of UTK Menu selection shall be:

TRACK FFFFFF SAMSUNGFFF SCHB529FFFUT 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. shouldbe sent in proper order.

The Number of characters to be sent in SMS shall be 103characters i.e. NUM FIELD of theUser 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 withinstipulated time or receives negative acknowledgement the Application should re-send the SMSthree timesand set the counter or flag internally to indicate that SMS sending had failed and willbe re-sent on next power on. Separate flags for all triggers shall be maintained independently.


11/26


Application




11

5. Triggers Explained

Following are the triggers:

A) Power Up EventB) Mobile Originated SMS/Voice call/Data EventC) Mobile Terminated SMS/Voice call EventD) UTK Menu selection EventE) Network Initiated SMS EventF) 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 smswith 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 i f sent successfullydevice shall set the flag as sms sent else shall retry thrice and set the flag as not sent and shallwait 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 successfullydevice shall set the flag as sms sent else shall retry thrice and set the flag as not sent and shallwait 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 trackingsms 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 theESN.

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


12/26


Application




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 (2Bits)

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 aNetwork 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 typeUM,the device shall treat this SMS as a trigger to send UM type ESN tracking SMSfrom itsapplication. If sent successfully device shall set the flag as sms sent else shall follow retrymechanism.


13/26


Application




13

6. Conflict

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

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

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


14/26


Application




14

7. Appendix I: RUIM EF details

7.1 EF_RUIM_ID


15/26


Application




15

7.2 EF_ME_ESN

7.3 EF_SF_EUIMID


16/26


Application




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 MessageRecord_HeaderRECORD_LENGTHRaw=(107) byteLOG_CODERaw=(4101) 0x1005MESSAGE_TIMESTAMPRaw=(48245266986369088) 12:37:20.261MSG_LENGTHRaw=(95) 95byteMSG_TYPERaw=(4) Data Burst MessageSDU_AND_PDU_PADDING_LENGTHRaw=(728) 728bits

Data Burst MessageFDSCH_LAYER2_BEG_FIELDSACK_SEQRaw=(2)MSG_SEQRaw=(2)ACK_REQRaw=(1)ENCRYPTIONRaw=(0)

DATA_BURST_MESSAGEMSG_NUMBERRaw=(1)BURST_TYPERaw=(3) Short Message ServicesNUM_MSGSRaw=(1)

NUM_FIELDSRaw=(86)Short Message ServicesSMS_MSG_TYPERaw=(0) Point-to-PointSMS Point-to-PointSMS_DATA_BURST_PAYLOAD

PARAMETER_IDRaw=(0) Teleservice IdentifierPARAMETER_LENRaw=(2)Teleservice IndentifierIDENTIFIERRaw=(4098) CDMA Cellular Messaging TeleservicePARAMETER_IDRaw=(4) Destination AddressPARAMETER_LENRaw=(7)Destination Address

DIGIT_MODERaw=(0)NUMBER_MODERaw=(0)NUM_FIELDSRaw=(11)

CHARiRaw=(10) 0CHARiRaw=(9) 9CHARiRaw=(2) 2CHARiRaw=(2) 2CHARiRaw=(3) 3CHARiRaw=(10) 0


17/26


Application




17

CHARiRaw=(5) 5CHARiRaw=(3) 3CHARiRaw=(7) 7CHARiRaw=(5) 5CHARiRaw=(1) 1

ReservedRaw=(0)

PARAMETER_IDRaw=(6) Bearer Reply OptionPARAMETER_LENRaw=(1)Bearer Reply OptionREPLY_SEQRaw=(0)RESERVEDRaw=(0)PARAMETER_IDRaw=(8) Bearer DataPARAMETER_LENRaw=(67)Bearer Data

SUBPARAMETER_IDRaw=(0) Message Identifier

SUBPARAM_LENRaw=(3)

Message IdentifierMESSAGE_TYPERaw=(2) SubmitMESSAGE_IDRaw=(488)HEADER_INDRaw=(0)

SUBPARAMETER_IDRaw=(1) User DataSUBPARAM_LENRaw=(60)

User Datamsg_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')


18/26


Application




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')


19/26


Application




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')


20/26


Application




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 MessageRecord_Header

RECORD_LENGTHRaw=(59) byteLOG_CODERaw=(4103) 0x1007MESSAGE_TIMESTAMPRaw=(48245229906597056) 12:25:33.020MSG_LENGTHRaw=(47) 47bytePDRaw=(0)MSG_IDRaw=(9)SDU_AND_PDU_PADDING_LENGTHRaw=(330) 330bitsData Burst Message

FCSCH_LAYER2_BEG_FIELDSFCSCH_LAYER2_ARQ_FIELDSACK_SEQRaw=(0)MSG_SEQRaw=(0)ACK_REQRaw=(1)VALID_ACKRaw=(0)FCSCH_LAYER2_ADDR_FIELDSADDR_TYPERaw=(2) IMSIADDR_LENRaw=(5)

IMSI_CLASSRaw=(0)

IMSI_CLASS_0_TYPEIMSI_CLASS_0_TYPERaw=(0) IMSI_S includedRESERVEDRaw=(0)IMSI_SIMSI_SRaw=(16348451977) (085) 565-5248IMSI_S2Raw=((085)) (085)IMSI_S1Raw=(565-5248) 565-5248

DATA_BURST_MESSAGEMSG_NUMBERRaw=(1)BURST_TYPERaw=(3) Short Message ServicesNUM_MSGSRaw=(1)

NUM_FIELDSRaw=(30)Short Message Services

SMS_MSG_TYPERaw=(0) Point-to-PointSMS Point-to-Point

SMS_DATA_BURST_PAYLOADPARAMETER_IDRaw=(0) Teleservice IdentifierPARAMETER_LENRaw=(2)Teleservice IndentifierIDENTIFIERRaw=(4098) CDMA Cellular Messaging TeleservicePARAMETER_IDRaw=(2) Originating Address


21/26


Application




21

PARAMETER_LENRaw=(3)Originating AddressDIGIT_MODERaw=(0)NUMBER_MODERaw=(0)NUM_FIELDSRaw=(3)

CHARi Raw=(1) 1CHARi Raw=(2) 2CHARi Raw=(1) 1

PARAMETER_IDRaw=(8) Bearer DataPARAMETER_LENRaw=(15)Bearer Data

SUBPARAMETER_IDRaw=(0) Message IdentifierSUBPARAM_LENRaw=(3)

Message IdentifierMESSAGE_TYPERaw=(1) DeliverMESSAGE_IDRaw=(0)

HEADER_INDRaw=(0)SUBPARAMETER_IDRaw=(15) Message Display ModeSUBPARAM_LENRaw=(1)

Message Display ModeMSG_DISPLAY_MODERaw=(3) 3

RESERVED_DISP_MODE_6_BITS = 32 (0x20)SUBPARAMETER_IDRaw=(1) User DataSUBPARAM_LENRaw=(5)

User DataMSG_ENCODINGRaw=(0) SMS-Based MS-MPC protocolNUM_FIELDSRaw=(3)

CHARi Raw=(69) [0x45] ECHARi Raw=(83) [0x53] S

CHARi Raw=(78) [0x4e] NSUBPARAMETER_IDRaw=(6) Deferred Delivery Time - AbsoluteSUBPARAM_LENRaw=(1)Deferred Delivery Time - Absolute

SMS_DATE_AND_TIMEYEARRaw=(200) 2000

MONTHRaw=(--)


22/26


Application




22

The MS sends the ESN Tracking SMS

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



Reverse Channel Traffic Messageprotocol_rev = 6 (0x6) (IS2000 Rev 0)chan_type = 4 (0x4) (Reverse Traffic)chan

rtc_msg

genmsg_type = 4 (0x4) (Data Burst)

rtc_bursthdr

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_parmsparameter_id = 0 (0x0) (Teleservice Identifier)teleservice_id

telesvc_id = 4098 (0x1002) (CDMA Cellular Messaging Teleservice)sms_parms[1]

sms_pp_parmsdigit_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)


23/26


Application




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_identifiermessage_type = 2 (0x2) (Submit)message_id = 18 (0x12)

bd[1]subparameter_id = 1 (0x1) (User Data)user_datamsg_encoding = 2 (0x2) (7-bit ASCII - 7 bits)num_fields = 103 (0x67)

sm_tp_user_data_ascii_7user_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) (' ')


24/26


Application




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')


25/26


Application




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')


26/26


Application




10. Appendix IV: ESN tracking application flow

Esn Tracking Tata

Documents

Transcript of Esn Tracking Tata