TIA-136-034-A-2002 TDMA Third Generation Wireless- R-UIM C ME Interface Procedures (ANSI APPROVAL WITHDRAWN JUNE 12 2015).pdf

1、 ANSI/TIA-136-034-A-2002 APPROVED: APRIL 15, 2002 APPROVED: SEPTEMBER 18, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-034-A (Revision of TIA-136-034) April 2002TDMA Third Generation Wireless- R-UIM- ME Interface Procedures NOTICE TIA Engineering Standards and Publications are designed to serve the public

2、interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards an

3、d Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestical

4、ly or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard o

5、r Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory

6、limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. ANSI/TIA-PN-136.034-A-WD, formulated under the cognizance of the TIA TR-45 Mobil

7、e (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may in

8、volve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a

9、statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or co

10、nditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as res

11、pects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwis

12、e), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such

13、 Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of

14、 the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or servic

15、es or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND

16、ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR H

17、EALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITA

18、TION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE P

19、OSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA/EIA-136-034-A-2013 iForeword This document references publications developed by ETSI (European Tele

20、communications Standards Institute). These referenced publications are freely available at http:/www.etsi.org TIA/EIA-136-034-A-2013 ii Contents 1 Introduction1 1.1 R-UIM documents .1 2 Function the composite R-8 UIM is comprised of the current SIM specification and this ancillary document. 9 10 1.1

21、 R-UIM documents 11 12 13 Definitions, Terms, Symbols and References are provided in TIA/EIA-136-030. 14 TIA/EIA-136-034-A-2013 2 2 Function at present the default value XX=00 is the only one defined. 4 #When the error in P1 or P2 is caused by the addressed record being out of range, then the return

22、 code 94 02 shall be used. 5 NOTE: XX gives the correct length or states that no additional information is given (XX = 00). 6 Table 1 shows for each command the possible status conditions returned (marked by an asterisk *). 7 TIA/EIA-136-034-A-2013 111 Table 1: Commands and status words 2 3 OK Busy

23、Mem Staus Refer. Status Security Status Application Independent Errors Commands 90 00 91 03 91 XX 9EXX 9F 03 9F 04 9F 06 9F nn 93 00 92 0X92 40 94 00 94 02 94 04 94 08 98 02 98 04 98 08 98 10 98 34 98 40 98 50 67 XX 6BXX6DXX6EXX6F XXAsk Random * * * * * Update SSD * * * * * * Confirm SSD * * * * * *

24、 * Internal Authenticate * * * * * * Generate Key * * * * * * A-Key Validation * * * * * * CMEA Encryption * * * * * * Get Call Count * * * * * * * * * * * * Set Call Count * * * * * * * * * * * * * Update Call Count * * * * * * * * * * * * 4 The responses 91 XX, and 93 00 and 9E XX can only be give

25、n by an R-UIM supporting an R-UIM Application Toolkit, to an 5 ME also supporting R-UIM Application Toolkit. 6 7 TIA/EIA-136-034-A-2013 12 3 Application Protocol 1 2 When involved in TIA/EIA-136 administrative management operations, the R-UIM interfaces with 3 appropriate terminal equipment. These o

26、perations are outside the scope of the present document. 4 5 When involved in TIA/EIA-41 network operations the R-UIM interfaces with an ME with which messages 6 are exchanged. A message can be a command or a response. 7 8 A TIA/EIA-136 command/response pair is a sequence consisting of a command and

27、 the associated 9 response. 10 11 A TIA/EIA-136 procedure consists of one or more TIA/EIA-136 command/response pairs, which are 12 used to perform all or part of an application-oriented task. A procedure shall be considered as a whole, 13 that is to say, that the corresponding task is considered suc

28、cessful if, and only if, the entire procedure 14 is completed. The ME shall ensure that, when operated according to the manufacturers manual, any 15 unspecified interruption of the sequence of command/response pairs, contained in a given procedure, 16 leads to the abortion of the procedure itself. 1

29、7 18 A TIA/EIA-136 session is defined as the interval of time beginning at the completion of the R-UIM 19 initialization procedure and ending either with the start of the TIA/EIA-136 session termination 20 procedure, or immediately following the interruption of the SIM/ME interface. 21 22 During the

30、 TIA/EIA-41 network operation phase, the ME plays the role of the master and the R-UIM 23 plays the role of the slave. Some procedures at the R-UIM/ME interface require MMI interactions. The 24 descriptions hereafter do not intend to infer any specific implementation of the corresponding MMI. 25 26

31、The list of procedures at the R-UIM/ME interface in TIA/EIA-41 network operation is as follows: 27 General Procedures 28 R-UIM Management Procedures 29 CHV related Procedures 30 TIA/EIA-41 Based Authentication Procedures 31 Subscription related Procedures 32 33 3.1 General Procedures 34 35 The gener

32、al procedures for Reading an EF, Updating an EF, and Increasing an EF are defined in clause 36 11.1 of GSM 11.11. 37 38 3.2 R-UIM Management Procedures 39 40 The R-UIM shall connect, activate and deactivate in accordance with the Operating Procedures defined in 41 clause 4.3.2 of GSM 11.11. The ME p

33、erforms the IMSI request via GSM Initialization Procedure. 42 43 The ME then executes the Select DFTIA-EIA-136command. If DFTIA-EIA-136exists then the R-UIM is 44 TIA/EIA-136 capable. The ME shall then perform the R-UIM Protocol Version Request. A TIA/EIA-136 45 R-UIM is required to support the elem

34、entary files and procedures defined for the Protocol Version defined 46 in the R-UIM Protocol Version EF, and any previous Protocol Versions. If the R-UIM Protocol Version 47 Request fails, then the ME shall assume PV1 for the R-UIM. If the R-UIM Protocol Version Request 48 succeeds, then the ME sha

35、ll perform the SIM Application Toolkit(SAT) Profile Download procedure, as 49 defined in GSM 11.14. The Profile Download Procedure includes the TERMINAL PROFILE command, 50 TIA/EIA-136-034-A-2013 13which notifies the R-UIM of the MEs Protocol Version. If no Protocol Version is provided by the ME, 1

36、then the R-UIM shall assume PV1 for the ME. The mobile station Protocol Version is defined by the 2 lower of the ME Protocol Version (see TIA/EIA-136-123) and the R-UIM Protocol Version. 3 4 The ME then executes the Select EFGA-PHASE command. If the select is successful, the ME shall perform 5 the G

37、SM-ANSI-136 SIM Phase ID Request. A GSM-TIA/EIA-136 capable R-UIM is required to support 6 the elementary files and procedures defined for the phase defined in EFGA-PHASE, and any previous GSM-7 ANSI-136 phases. The ME must operate at the level defined by the lower of its own GSM-ANSI-136 8 Phase ID

38、 or the GSM-ANSI-136 Phase ID of the R-UIM. 9 10 . The ME shall perform the R-UIM Service Table Request per 3.2.9.8, herein, and the SIM Service Table 11 Request per GSM 11.11 clause 11.2.6. Service and facilities which are unique to TIA/EIA-136 are 12 indicated in the SAT Profile Download and the R

39、-UIM Service Table, while those services and facilities 13 which are common to both GSM and TIA/EIA-136 are provided in the SAT Profile Download and the 14 SIM Service Table. 15 16 Also as part of the management phase, the ME shall retrieve the Protocol Priority Indicator value by 17 performing an A

40、NSI-136 Usage Indicator Request. The ME shall then perform the Home System Operator 18 Code and Mobile Country Code Request, which shall be required to perform any personalization checks, if 19 required, in-order to determine whether the current R-UIM will be allowed to operate. 20 21 Based upon the

41、 Protocol Priority Indicator value, the ME shall perform the Core Initialization and TDMA 22 Initialization procedures. 23 24 Upon completion of this, the ME is free to request any user data information it may require, (see GSM 25 11.11, sub-clause 11.5). Note however, that the reading of this infor

42、mation may occur prior to this point 26 i.e. after reading the initial initialization data (GSM or TIA/EIA-136). 27 28 3.2.1 R-UIM Initalization 29 30 3.2.1.1 GSM Initialization 31 The ME runs GSM initialization to obtain IMSI as specified in ETSI GSM 11.11 clauses 11.2.1 and 32 11.4.2. 33 34 3.2.1.

43、2 Core Initialization 35 The ME runs the following procedures using the READ command: 36 MIN request 37 ACCOLC request 38 SID request 39 Initial Paging Channel request 40 S-ESN request 41 COUNTsp request 42 Positive/Favoured SID List request 43 Negative/Forbidden SID List request 44 Registration Thr

44、eshold request 45 46 TIA/EIA-136-034-A-2013 14 3.2.1.3 TDMA Initialization 1 The ME runs the following procedures using the READ command: 2 IRDB Parameters request 3 NAM PSIDs/RSIDs request 4 Test Registration PSIDs/RSIDs request 5 Reg. Accept PSIDs/RSIDs request 6 Band and Sub-Band Priority Order r

45、equest 7 Band History Table request 8 DCCH History Table request (conditional on IRDB Parameter value) 9 Additional User Registration Parameters request 10 Partner SID List request 11 Partner SOC List request 12 Favoured SOC List request 13 Forbidden SOC List request 14 Alpha Tag request 15 Triggere

46、d Scan Timers request 16 TeleService Server Address Info request 17 SS Feature Code Table request 18 IRDB Version Table request 19 User Group ID Info request 20 21 3.2.2 TIA/EIA-136 Session Termination 22 23 The ME shall perform the following updates 24 BHT Table update 25 DHT Table update (conditio

47、nal on IRDB Parameter value) 26 Additional User Registration Parameters update 27 28 3.2.3 NAM Information Procedures 29 30 3.2.3.1 Mobile Identification Number 31 Request: The ME performs the reading procedure with the EFMIN32 Update: The ME performs the updating procedure with the EFMIN 33 34 3.2.

48、3.2 Access Overload Class 35 Request: The ME performs the reading procedure with the EFACCOLC36 Update: The ME performs the updating procedure with the EFACCOLC 37 38 3.2.3.3 System Identification of Home System 39 Request: The ME performs the reading procedure with the EFSID40 Update: The ME perfor

49、ms the updating procedure with the EFSID 41 42 3.2.3.4 Home System Operator Code and Mobile Country Code 43 Request: The ME performs the reading procedure with the EFHOME-SOC-MCC44 45 3.2.3.5 Initial Paging Channel 46 Request: The ME performs the reading procedure with the EFIPC47 Update: The ME performs the updating procedure with the EFIPC 48 49 TIA/EIA-136-034-A-2013 153.2.3.6 Group ID 1 Req