1、 TIA/EIA STANDARD TDMA Third Generation Wireless - Personalization of Mobile Equipment (ME) TIA/EIA-136-036 APRIL 2001 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of ANSI/TIA/EIA-136-036-2001 Approved: April 23, 2001 TIA/EI
2、A-136-036NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining wit
3、h minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Stan
4、dards and Publications preclude their voluntary use by those other than TIA/EIA members, whether the standard is to be used either domestically or internationally. Standards and Public ations are adopted by TIA/EIA in accordance with the American National Standards Institute (ANSI) patent policy. By
5、 such action, TIA/EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. Note: The users attention is called to the possibility that compliance with this document may require use of one or more inventions cov
6、ered by patent rights. By publication of this standard, Interim Standard, or TSB, no position is taken with respect to the validity of those claims or of any patent rights in connection therewith. The patent holder(s) so far identified have, however, filed statements of willingness to grant licenses
7、 under those rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such licenses. Details may be obtained from the standards developer. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requir
8、ements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 4027-036+A, formulated under the cognizance of the TIA TR-45.3Subcommittee on T
9、ime Division Digital Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2001 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 PRICE: Please refer to current Catalog of EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or call Global
10、 Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Organizations may obtain permission to reproduce a limited nu
11、mber of copies through entering into a license agreement. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 TIA/EIA-136-036iForewordThis document references publications develop
12、ed by ETSI (European Telecommunications StandardsInstitute). These referenced publications are freely available at http:/www.etsi.orgTIA/EIA-136-036iiTHIS PAGE INTENTIONALLY LEFT BLANKTIA/EIA-136-036iiiContents11 INTRODUCTION 122 SOC PERSONALIZATION 132.1 OPERATION OF A SOC PERSONALIZED ME 243 SOC P
13、ERSONALIZATION AND DE-PERSONALIZATION CYCLE . 253.1 PERSONALIZATION CYCLE. 263.2 DE-PERSONALIZATION CYCLE . 373.3 OVER THE AIR DEPERSONALIZATION CYCLE. 383.3.1 OTA De-personalization Functionality. 393.3.2 Over The Air Depersonalization Messages. 41011TIA/EIA-136-036ivTables1Table 1: Codes used by e
14、ach personalization category. 12Table 2: Format of TP-UD when the ME Identity indicates IMEI . 43Table 3: Format of TP-UD when the ME Identity indicates ESN 44Table 4: ME Identity. 55Table 5: Format of the Response Message when the ME Identity indicates IMEI. 56Table 6: Format of the Response Messag
15、e when ME Identity indicates ESN 57Table 7: Definition of Status code 58TIA/EIA-136-03611 Introduction1Personalization of Mobile Equipment (ME) is based on the current personalization feature and mechanisms2defined in ETSI TS 122 022. A new category called SOC Personalization category is added to th
16、e existing3five categories in ETSI TS 122 022. Table 1 below describes the personalization categories and the4information each category requires. SOC Personalization allows the ME to be locked to an TIA/EIA-1365system code (SOC and MCC) or multiple TIA/EIA-136 system codes. The SOC personalization c
17、ategory6may be utilized with other GSM personalization categories such that an ME is locked to multiple7personalization categories (e.g. SOC level and Network).89Table 1: Codes used by each personalization category10PersonalizationcategoryNetwork(MCC, MNC)NetworkSubset(IMSI digits 7,8)SP(GID1)Corpor
18、ate(GID2)R-UIM(IMSI digits9 to 15)TIA/EIA-136System(Home SOC andMCC)1Network G57Network Subset G57G57Service ProviderCorporate G57G57G57R-UIM G57G57 G57SOC G5711Note 1: MCC is only necessary when the Home SOC is in the National SOC range see12TIA/EIA-136-123 and TIA/EIA-136-005.13142 SOC Personaliza
19、tion15SOC Personalization allows an operator to personalize an ME to a particular TIA/EIA-136 system code or16multiple TIA/EIA-136 system codes. An ME is SOC Personalized by storing the TIA/EIA-136 system17codes and setting a SOC Personalization Indicator to “on“ in the ME.1819Whenever an R-UIM is i
20、nserted, or the Mobile Station (MS) is powered up with an R-UIM already in20place, the required codes are read from the R-UIM and compared to the embedded codes stored in the ME.21If any of the values read from the R-UIM are the same as the ME based values then the MS shall allow22normal operation (
21、assuming that all other personalization checks have been successfully completed). If no23match is found then the MS shall only allow emergency service.2425The SOC Personalization feature shall be controlled by a SOC Control Key (SCK) which has to be entered26into the ME in-order to SOC de-personaliz
22、e it. The SCK shall be of the same format as the other GSM27control keys and additionally shall follow the same security precautions as defined in ETSI TS 122 022,28clause 14.2930In order to support the SOC personalization feature the ME shall have storage for the SOC personalization31indicator and
23、the TIA/EIA-136 system codes that the ME is locked to.3233As stated in ETSI TS 122 022, personalizing the ME to multiple codes for a particular category (via the34Cooperative Network List, see GSM 11.11, or some other mechanism) is possible. It shall additionally be35possible to SOC personalize an M
24、E to multiple values of TIA/EIA-136 system codes via a Cooperative36SOC List (stored on the R-UIM) or some other mechanism.373839TIA/EIA-136-03622.1 Operation of a SOC personalized ME1The SOC personalization check described below is performed whenever an R-UIM is inserted or the ME2powered up with a
25、n R-UIM already in place.34The personalization check is as follows. When more than one personalization category is active in the ME,5normal mode of operation includes performing any outstanding personalization checks:67a) Check if the ME is SOC personalized: The ME checks its SOC personalization ind
26、icator. If it is set8to “off”, the personalization checks shall be stopped. The remaining steps are skipped and the MS9enters the normal mode of operation. If it is set to “on“, then:1011b) Check if the R-UIM supports the Home-SOC-MCC file: The ME checks that the R-UIM supports12the Home-SOC-MCC fil
27、e;1314c) Check the code(s): The ME reads the Home-SOC-MCC file from the R-UIM and extracts the SOC15and MCC (if required) information and compares them against the (list of) value(s) stored in the ME.1617If (b) fails or no match is found in (c) or any of the checks related to any other enabled categ
28、ory fail, then18the MS may display an appropriate message (e.g. “Incorrect Card”) and shall go into emergency call only19mode, otherwise the MS goes into the normal mode of operation.20213 SOC Personalization and De-Personalization22Cycle23243.1 Personalization Cycle2526The process of SOC personaliz
29、ation can only be carried out on a currently unpersonalized ME, (i.e. if the27SOC personalization indicator is set to “off“). Access to the SOC personalization process shall be restricted28in order to prevent unauthorized, accidental or unwanted personalization. Other restrictions are described in29
30、ETSI TS 122 022, clause 13. The SOC personalization process results in the SOC Control Key being set, a30SOC personalization indicator being set to “on“ and the storage in the ME of the TIA/EIA-136 system31code(s) to which the ME is being personalized.3233The SOC personalization process is as follow
31、s:3435a) The TIA/EIA-136 system codes are entered into the ME. This may be accomplished by one of the36following means:37 The ME reads the information from the Home-SOC-MCC file on the R-UIM and extracts the38required codes (i.e. SOC and MCC) for locking to a single operator. If the R-UIM does not39
32、support the Home-SOC-MCC file, or the Home-SOC-MCC codes are set to default values, then40the personalization process shall be aborted with an appropriate error message.41 The ME reads the Co-operative SOC List (CSL) from the R-UIM and extracts the list of42TIA/EIA-136 system codes for locking to mu
33、ltiple operators;43 Keypad entry44 Manufacturer defined process.45TIA/EIA-136-0363b) The ME carries out the pre-personalization checks contained in ETSI TS 122 022 clause 13. If they all1pass, the TIA/EIA-136 system codes are stored in the ME. If any fail, the personalization process shall2be termin
34、ated.3c) The SOC Control Key is in the ME. This may be entered via the keypad by the user or by a4manufacturer-defined process.5d) The SOC personalization indicator is set to “on“.673.2 De-personalization Cycle89To de-personalize the ME, the correct SOC Control Key shall be entered. It is optional w
35、hether or not an R-10UIM is inserted in the ME. If an R-UIM is inserted, then de-personalization shall be offered whether or not11the personalization check passes or fails.1213De-personalization should be possible by keypad entry. If there is no keypad entry, then an alternative14ME-based solution s
36、hould be provided. Other de-personalization methods may also be provided such as a15network initiated process whereby the control key is sent to the MS over-the-air. This may be performed16using the GHOST teleservice.1718The de-personalization process is as follows:19a) the SOC Control Key is entere
37、d into the ME;20b) if the entered SOC Control Key is the same as the one in the ME, the SOC personalization indicator is21set to “off“.22If the entered and stored SOC Control Key values differ, the de-personalization process shall be stopped.23The ME remains personalized and the stored code(s) and S
38、OC Control Keys shall be left unchanged.2425Once the mobile equipment is depersonalized, any R-UIM may be used to obtain the appropriate service.2627283.3 Over the Air Depersonalization Cycle29303.3.1 OTA De-personalization Functionality3132As an optional ME feature, the ME may be de-personalized ov
39、er-the-air (OTA) by the network. The33network, network subset, SP, corporate and SOC categories may be de-personalized in this way. More than34one category may be de-personalized at the same time. The process results in the relevant personalization35indicator(s) being set to “off“. The ME must be re
40、gistered on a network.3637The identity of the ME to be de-personalized and the Control Key(s) of the personalization categories to be38de-personalized are sent directly to the ME using a GHOST teleservice message. The ME performs checks39on both the ME Identity and the key values and the outcome of
41、the attempted de-personalization(s) is40acknowledged to the network.4142The network de-personalizes the ME by the following process:43441. A GHOST message carrying an SMS PDU is sent by the network to the MS, the message being45marked as being destined for the ME only and for the purposes of ME de-p
42、ersonalization (see ETSI TS46TIA/EIA-136-0364123 040). The User Data of the SMS contains the de-personalization key(s) and the ME identity1indicating either the IMEI or the ESN of the ME (see 3.3.2). If the ME supports the feature, then it2shall not display the data on the ME.32. The ME compares the
43、 values of the ME identity and the key(s) sent by the network with the4corresponding values stored in the ME. If they are the same, the relevant personalization indicator(s) is5(are) set to “off“.63. If the ME identity values differ, the personalization status of all categories shall be left unchang
44、ed.74. If any key values differ, the corresponding personalization status shall be left unchanged.85. The ME shall originate a GHOST message with TP-DA set to the TP-OA of the received De-9personalization message. The TP-UD shall be coded as defined in Table 5 (or Table 6 as appropriate)10to indicat
45、e the result of the attempted de-personalization process (see 3.3.2).11123.3.2 Over The Air Depersonalization Messages13141. The ME-specific de-personalization GHOST messages sent by the network to de-personalize the ME15shall be coded according to ETSI TS 123 040 with the TP-UD field coded as follo
46、ws:16Table 2: Format of TP-UD when the ME Identity indicates IMEI17Character Description1 - 31 Operator specific text padded with spaces tocharacter 31.32 ME Identity33 - 40 SOC control key41 - 48 Network control key49 - 56 Network subset control key57 - 64 SP control key65 - 72 Corporate control ke
47、y73 - 88 IMEI18Table 3: Format of TP-UD when the ME Identity indicates ESN19Character Description1 - 31 Operator specific text padded with spaces tocharacter 31.32 ME Identity33 - 40 SOC control key41 - 48 Network control key49 - 56 Network subset control key57 - 64 SP control key65 - 72 Corporate c
48、ontrol key73 - 76 ESN20For the ME Identity and each control key, the most significant digit is coded first in the string, e.g.21character 33 is the most significant digit of SCK.2223All characters are coded according to the default alphabet described in ETSI TS 123 038.2425TIA/EIA-136-0365The string
49、 “FFFFFFFF“ shall be used in place of a key to indicate that de-personalization of that category is1not required.23Table 4: ME Identity4Description CodeIMEI 0000 0000ESN 0000 0001562. The acknowledgement to the ME De-personalization message shall have TP-User-Data coded7according to the default alphabet described in ETSI TS 123 038 as below:8Table 5: Format of the Response Message when the ME Identity indicates IMEI9Character Description1-16 IMEI of ME17 Network personalization status18 Network subset personalization status19 SP personalization status20 Corporate personalization
