TIA-928-A-1[E]-2014 MAP Support for the Mobile Equipment Identity (MEID) (Incorporates Addendum 1 03 2014).pdf

1、 TIA-928-A-1 April 2014MAP Support for the Mobile Equipment Identity (MEID) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of produ

2、cts, 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 conforming to suc

3、h 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 (ANSI) pate

4、nt 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 requirement

5、s. 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. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA o

6、r this committee of the products or services of the company. (From Project No. TIA-PN-928-A-1, formulated under the cognizance of the TIA TR-45 Mobile (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 Docu

7、ment may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no s

8、earch or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligatio

9、n 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 conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or

10、non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other S

11、SO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA di

12、sclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending

13、 patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of 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 conte

14、nts 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 IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCUR

15、ACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND 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 WAR

16、RANTIES 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 PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIREC

17、T 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 FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRA

18、CT, 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 THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITAT

19、IONS. 3GPP2 X.S0008-A v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Rev. 0 v1.0 Initial Publication June 2004Rev. 0 v2.0 Annexes A clarifications October 2005Rev. 0 v3.0 Annex A Technical Specification Group Core Network; Mobile Ap

20、plication Part (MAP) Specification.CDMA 3GPP2 C.S0001,2,3,4,5,6-E v3.0. cdma2000 Spread Spectrum Systems. June 2011.MAP 3GPP2 X.S0004-E. Mobile Application Part (MAP).Note: 3GPP2 X.S0004-E is a set of specifications and is a non-specific reference.3GPP2 N.S0005-0 v1.0. Wireless Radiotelecommunicatio

21、ns Intersystem Operations. 1997.MEID Binding 3GPP2 S.S0152-0 v1.0. Security Framework for Binding of Access Subscription with Devices. December 2013.CSIM 3GPP2 C.S0065-B v2.0. cdma2000 Application on UICC for Spread Spectrum Systems. January 2011.EUIMIDStg1 3GPP2 S.R0111 v2.0. Expanded R-UIM Identif

22、ier, Stage 1 Requirements. May 2007.3GPP2 X.S0008-A v2.0Assumptions1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859602MEIDStg1 3GPP2 S.R0048-A v2.0. 3G Mobile Equipment Identifier (MEID) Stage 1. April 2004.RUIM 3GPP2 C.S0023-B v1.0. Remov

23、able User Identity Module for Spread Spectrum Systems. May 2004.23.003 3GPP TS 23.003 10.2.0. Numbering, addressing and identification. June 2011.1. MEID-equipped mobiles do not have a true ESN. They transmit either UIMID (includingpUIMID) or pseudo-ESN as ESNThese MSs may also transmit an MEID_ME o

24、r SF_EUIMID under some circumstances.2. The MEID_ME and SF_EUIMID are not used for authentication.3. The CheckMEID operation is optional.The following editorial conventions are used for this document: red cross-out with change bars indicates text that is being deleted from X.S0004. Changes to X.S000

25、4 are shown in blue, underlined text with change bars. Entirely new sections for X.S0004 just have a change bar.In figures, blue dashed arrows indicate interfaces outside the scope of X.S0004 and N.S0005, andare included for illustrative purposes only.1.5 Assumptions1.6 Editorial Conventions3GPP2 X.

26、S0008-A v2.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859603 X.S0004-000-E Modifications2 MODIFICATIONSCardExpanded UIMID (EUIMID)Mobile Equipment (ME)Mobile Equipment Identifier (MEID)MEID_MEMEID_SIGPseudo-ESN (pESN)Pseudo-UIMID (pUIMI

27、D)X.S0004-000-EThis section provides additional definitions for the introductory matter for (part 000). SeeAnnex C for further information regarding some of the terms used in this specification.A subscriber identity module, either or .A unique Card identifier that is longer than the unique UIMID it

28、replaces and that is used inconjunction with pUIMID. May be an SF_EUIMID.A wireless transceiver device, without the Card.A protocol element that is either an MEID_ME or an SF_EUIMID.A 56-bit number that, in conjunction with pESN, replaces ESN as the unique identifier of an ME.An electronic signature

29、 cryptographically computed using the credentials associated with theMEID_ME (see ). This signature is used by the network to enforce the binding of acdma2000 1x subscription to a specific Mobile Station or to a group of Mobile Stations.A 32-bit number derived from the MEID_ME and used in place of t

30、he electronic serial number. Thehigh order 8 bits are always 0x80 and the remaining 24 bits are derived using the SHA-1 algorithmas defined in .A 32-bit number derived from the EUIMID and used in place of the UIMID. The high order 8 bitsare always 0x80 and the remaining 24 bits are derived using the

31、 SHA-1 algorithm as defined in.X.S0004-ER-UIM CSIMCDMAMEID BindingCDMACDMA3GPP2 X.S0008-A v2.0X.S0004-000-E Modifications1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859604Short Form Expanded UIMID (SF_EUIMID)UIMIDA 56-bit number that, in

32、conjunction with pUIMID, may replace UIMID as the unique identifier ofa Card (see ).A 32-bit number used to uniquely identify a Card or a pUIMID (that satisfies some protocolrequirements but does not uniquely identify a CDMA Card).CDMA EUIMIDStg1CDMA3GPP2 X.S0008-A v2.0123456789101112131415161718192

33、0212223242526272829303132333435363738394041424344454647484950515253545556575859605 N.S0005-0 Chapter 3 Modificationscheckmeid MEIDSTATUSstatus request (MEID or MEID_ME)abcdefCHECKMEID MEIDSTATREQ MSID, RECORD_TYPE (MEID or MEID_ME)status response MEID or MEID_MEstatreq MEID or MEID_ME3 CHAPTER 3 MOD

34、IFICATIONS3.1 Check MEID Procedure (new)MSEIR VLR MSCN.S0005-0This section provides information flows for MEID support according to the structure of .This scenario illustrates the Check MEID procedure. In this case, the VLR does not have the MEIDof the MS and initiates the Status Request operation t

35、o retrieve it.a. The VLR sends a to the Serving MSC with the MSID parameter set to identify thetarget MS. The RECORD_TYPE parameter is set to request the MEID or MEID_MEinformation record.b. Optionally, the MSC sends a message to the MS requesting the MEID orMEID_ME information record.c. The MS retu

36、rns its MEID or MEID_ME in the message. If MEID is returned, itmay be MEID_ME or SF_EUIMID and the protocol does not identify which type of identifieris being returned.d. The MSC sends a with the requested MEID to the VLR.e. The VLR can now check the MEID or MEID_ME in the EIR database. The VLR send

37、s theMEID to the EIR in the .f. The EIR returns the requested equipment status to the VLR in the . The status maybe , , , or .N.S0005-0Parts 3xxstatus requeststatus responseNormal Block Track No EntrySTATREQstatreqCHECKMEIDcheckmeidCMTSTRT3GPP2 X.S0008-A v2.0Unsuccessful Status Request (new)12345678

38、91011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606abcdMS reject orderstatreq STATREQ MSID, Record_Type (MEID or MEID_ME)status request(MEID or MEID_ME)3.2 Unsuccessful Status Request (new)MSVLR MSCThis scenario illustrates an unsuccessful StatusR

39、equest operation.a. The VLR sends a to the Serving MSC with the MSID parameter set to identify thetarget MS. The Record_Type parameter is set to request the MEID or MEID_ME informationrecord.b. The MSC sends a message to the MS requesting the MEID or MEID_MEinformation record.c. The MS cannot provid

40、e the requested information (e.g. because it does not support the correctrevision of ) and sends the .d. The MSC sends an empty to the VLR to indicate that the messagewas not received from the MS.STATREQstatreqstatus requestCDMA MS reject orderstatus responseSTRT3GPP2 X.S0008-A v2.012345678910111213

41、14151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859607 MEID-Based Subscription Validation in the VisitedNetwork - Authentication Not Active in Serving MSC(new)abcdefgh3.3 MEID-Based Subscription Validation in the Visited Network - Authentication Not Active in

42、 Serving MSC (new)VLR HLRThis scenario illustrates the use of a provisioned MEID value in validating an MS (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

43、 be made.a. The MS acquires a CDMA system and registers based on SID/NID change. The MS does notinclude MEID in the message (e.g., because the acquired system does not indicatesupport of MEID). The MS is not solicited to provide authentication parameters. The MSsupplies an indication of its own supp

44、ort of MEID.b. Because the MS supplied an indication of its own support of MEID, yet the MSC does not havethe MEID of the MS, the MSC solicits the MEID or MEID_ME of the MS by way of a message over the radio interface.c. The MS responds with a message that includes the MEID or MEID_ME.d. The MSC sen

45、ds a to the VLR. The includes the MEID value transmitted bythe MS.e. The VLR forwards the to the MS HLR.f. Based on the existence of a provisioned MEID value for this subscription, and the presence ofthe MEID parameter in the , the HLR includes an MEID comparison in the validationof the subscription

46、. The HLR then registers the indicated MS and returns a to theServing VLR. The includes the MEIDValidated parameter to inform the ServingVLR/MSC that the MEID associated with the system access has been validated.g. The VLR sends a to the MSC. The MEID received at step-c is stored at the ServingMSC f

47、or use in validating subsequent system accesses by the MS.h. Optionally, the MSC confirms the success of the registration event to the MS.registerregnot MEIDValidatedREGNOT MSID, MEIDstatus request (MEID or MEID_ME)status response (MEID or MEID_ME)REGNOT MSID, MEIDregnot MEIDValidatedregister accept

48、Serving Systemregisterstatusrequeststatus responseREGNOT REGNOTREGNOTREGNOTregnotregnotregnotMS MSCRNTRNT3GPP2 X.S0008-A v2.0MEID-Based Subscription Validation in the Visited Network -Authentication Active in Serving MSC (new)12345678910111213141516171819202122232425262728293031323334353637383940414

49、24344454647484950515253545556575859608abcdefghijkl3.4 MEID-Based Subscription Validation in the Visited Network -Authentication Active in Serving MSC (new)HLRVLRThis scenario illustrates the use of a provisioned MEID value in validating an MS (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.Authentication is active in the visited system, yet the MS is marked as No authentication requiredin the