TIA-928-2[E]-2006 TIA-41 Support for the Mobile Equipment Identity (MEID) Addendum to TIA-928《TIA-41对移动设备识别(MEID)的支持》.pdf

《TIA-928-2[E]-2006 TIA-41 Support for the Mobile Equipment Identity (MEID) Addendum to TIA-928《TIA-41对移动设备识别(MEID)的支持》.pdf》由会员分享，可在线阅读，更多相关《TIA-928-2[E]-2006 TIA-41 Support for the Mobile Equipment Identity (MEID) Addendum to TIA-928《TIA-41对移动设备识别(MEID)的支持》.pdf（62页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA STANDARD TIA-41 Support for the Mobile Equipment Identity (MEID) TIA-928-2E January 2006TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Industry Association Provided by IHS under license wit

2、h EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvem

3、ent 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 and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not confo

4、rming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute

5、 (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 or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory

6、 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 limitations before its use. (From Standards Proposal No. 3-0083-AD2E, formulated under the cognizance of the TIA TR-45.2 Subcommi

7、ttee on Time Division Digital Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICA

8、TIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under license with

9、 EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyrigh

10、t permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/about/faqDetail.cfm?id=18 OR Telecommunications Industry Association Sta

11、ndards (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 m

12、ay involve 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 attentio

13、n, a 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

14、or conditions, 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 a

15、s respects the Document or its contents. 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 services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR

16、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 ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIM

17、S 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 HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODU

18、CED 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 LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES F

19、OR 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 POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF TH

20、E USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 E1234567891011

21、12131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Revision HistoryThis document is subject to change.Ver. Date RemarksTIA-928 August, 2004 Initial PublicationTIA-928-1 June, 2005 Addendum 1TIA-928-2 E October, 2005 Enhanced addendum 2Copyright Telecomm

22、unications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960iMAP Support for the Mobi

23、le Equipment Identity (MEID)ContentsNormative References1Informative References1Assumptions.1Editorial Conventions 11 TIA-41.000-E Modifications 22 TIA-41-D Chapter 3 Modifications 32.1 Check MEID procedure. 32.2 Unsuccessful Status Request. 42.3 MEID-Based Subscription Validation in the Visited Net

24、work - Authentication Not Active in Serving MSC. 52.4 MEID-Based Subscription Validation in the Visited Network - Authentication Active in Serving MSC . 72.5 MEID-Based Subscription Validation in the Visited Network - Origination with Authenti-cation . 92.6 MEID-Based Subscription Validation in the

25、Visited Network - Validation Fails 112.7 MEID Support in Visited Network But Not in HLR. 133 TIA-41.5xx-E Modifications 153.1 Application Services 153.1.1 MAP Operations. 153.1.2 Operation Definitions. 153.2 Map Parameters. 193.2.1 General . 193.2.2 Parameter Definitions 204 TIA-41.6xx-E Signaling P

26、rocedures .264.1 Autonomous or Power-On Registration 264.2 Idle MS Origination. 274.3 MSC Receives MEID of MS (new) 325 Registration Notification .335.1 MSC Initiating MS Registration 335.2 HLR Receiving RegistrationNotification INVOKE 366 (NEW) Check MEID 426.1 VLR Initiating a Check MEID 426.2 EIR

27、 Receiving a Check MEID Request 43Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 E123456789101112131415161718192021222324252627282930313233343536373839404142434445464

28、748495051525354555657585960ii7 (NEW) Status Request 457.1 VLR Initiating a Status Request 457.2 MSC Receiving a StatusRequest INVOKE.458 Operation Timer Values 479 TIA-41.540-E Operation Changes for MEID 4810 TIA-41.550-E Parameter Changes for MEID50Annex A: Decimal Representation of MEID(Informativ

29、e)51Annex B: Check Digit Calculation(Informative)52Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 E1234567891011121314151617181920212223242526272829303132333435363738

30、394041424344454647484950515253545556575859601NORMATIVE REFERENCESGSM MAP 3GPP TS 29.002. 3rd Generation Partnership Project; Technical SpecificationGroup Core Network; Mobile Application Part (MAP) Specification.CDMA TIA-2000-D. cdma2000 Spread Spectrum Systems. March 2004.MEIDStg1 3GPP2 S.R0048-A v

31、2.0. 3G Mobile Equipment Identifier (MEID) Stage 1.April 2004.MAP TIA-41-E. Wireless Radiotelecommunications Intersystem Operations. 2004.TIA-41-D. Wireless Radiotelecommunications Intersystem Operations. 1997.INFORMATIVE REFERENCESMEIDPROC 3GPP2 SC.R4001. Global Wireless Equipment Numbering Adminis

32、trationProcedures. February 2004.MEIDGDL 3GPP2 SC.R4002-0 v2.0. Mobile Equipment Identifier (MEID) AssignmentGuidelines and Procedures. November 2004.RUIM TIA IS-820-B. Removable User Identity Module for Spread Spectrum Systems.May 2004.ASSUMPTIONS1. MEID-equipped mobiles do not have a true ESN. The

33、y transmit either UIMID or pseudo-ESN as ESNThese MSs may also transmit an MEID under some circumstances.2. The MEID is not used for authentication.3. The CheckMEID operation is optional. If an operator chooses to use this operation, thecriteria for use may include whether the MS is equipped with a

34、Removable UIM.EDITORIAL CONVENTIONSThe following editorial conventions are used for this document:underline: addition.cross out: deletion.change bar: indicates additions or deletions.Red text indicates a change for TIA-928-2 E.Copyright Telecommunications Industry Association Provided by IHS under l

35、icense with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 E1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859602 TIA-41.000-E Modifications1TIA-41.000-EMODIFICATIONSThis section provides modi

36、fications for the introductory matter for TIA-41 (part 000).Pseudo-ESN (pESN)A 32-bit number derived from the MEID and used in place of the electronic serial number. The highorder 8 bits are always 0x80 and the remaining 24 bits are derived using the SHA-1 algorithm asdefined in CDMA.Copyright Telec

37、ommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 ETIA-41-D Chapter 3 Modifications12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455

38、565758596032TIA-41-D CHAPTER 3 MODIFICATIONSThis section provides information flows for MEID support according to the structure of TIA-41Parts 3xx.2.1 Check MEID procedureThis scenario illustrates the Check MEID procedure. In this case, the VLR does not have the MEIDof the MS and initiates the Statu

39、s Request operation to retrieve it.a. The VLR sends a STATREQto the Serving MSC with the MSID parameter set to identify thetarget MS. The RECORD_TYPE parameter is set to request the MEID information record.b. Optionally, the MSC sends a status requestmessage to the MS requesting the MEIDinformation

40、record.c. The MS returns its MEID in the status responsemessage.d. The MSC sends a statreqwith the requested MEID to the VLR.e. The VLR can now check the MEID in the EIR database. The VLR sends the MEID to the EIRin CHECKMEID.f. The EIR returns the requested equipment status to the VLR in the checkm

41、eid. The status maybe Normal, Block, Track, or No Entry.statreq MEIDcheckmeid MEIDSTATUSstatus requestabcdefCHECKMEID MEIDCMTSTATREQ MSID, RECORD_TYPE (MEID)STRTMSEIR VLR MSCstatus response MEIDCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo r

42、eproduction or networking permitted without license from IHS-,-,-TIA-928-2 E1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859604 Unsuccessful Status Request2.2 Unsuccessful Status Request This scenario illustrates an unsuccessful StatusRequ

43、est operation.a. The VLR sends a STATREQto the Serving MSC with the MSID parameter set to identify thetarget MS. The Record_Type parameter is set to request the MEID information record.b. The MSC sends a status requestmessage to the MS requesting the MEID information record.c. The MS cannot provide

44、the requested information (e.g. because it does not support the correctrevision of CDMA) and sends the MS Reject Order.d. The MSC sends an empty statreqto the VLR to indicate that the status responsemessagewas not received from the MS.abcdSTRTMSVLR MSCMS reject orderstatreq STATREQ MSID, Record_Type

45、 (MEID)status requestCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-928-2 EMEID-Based Subscription Validation in the Visited Network - Authentication Not Active in Serving

46、MSC12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596052.3 MEID-Based Subscription Validation in the Visited Network - Authentication Not Active in Serving MSCThis scenario illustrates the use of a provisioned MEID value in validating an MS

47、 (subscription). Inthis scenario the Serving MSC utilizes the Status Request/Status Response operation on the CDMAradio interface as a means to obtain the MEID of the MS so that a comparison can be made.a. The MS acquires a CDMA system and registers based on SID/NID change. The MS doesnot include ME

48、ID in the Register message (e.g., because the acquired system does notindicate support of MEID). The MS is not solicited to provide authentication parameters.The MS supplies an indication of its own support of MEID.b. Because the MS supplied an indication of its own support of MEID, yet the MSC does nothave the MEID of the MS, the MSC solicits the MEID of the MS by way of a StatusRequest message over the radio interface.c. The MS responds with a Status Response message that includes the MEID.d. The MSC sends a REGNOTto the VLR. The REGNOTi