1、 TIA-1074-1 E APPROVED: MARCH 1, 2006 REAFFIRMED: JUNE 21, 2012 TIA-1074-1 E March 2006OTA Support for MEID Addendum 1 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating
2、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 and Publications shall not in any respect preclude any member or non-member of TIA from manufacturin
3、g 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 domestically or internationally. Standards and Publications are adopted by TIA in accordance with the Americ
4、an 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 or Publication. This Standard does not purport to address all safety problems associated with its u
5、se 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 limitations before its use. (From Project No. 3-0207-AD1E, formulated under the cognizance of the
6、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 Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this
7、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 search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIA
8、s 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 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 licens
9、ing 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 non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been compl
10、ied 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 SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendat
11、ion or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) 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 s
12、uch Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) 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 the other SSO shall not
13、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 services or any claims of compl
14、iance 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 ITS NONINFRINGEMENT OF AN
15、Y 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 HEALTH EFFECTS OF THE CONT
16、ENTS 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 LIMITATION ANY AND ALL INDIRECT
17、, 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 POSSIBILITY OF SUCH DAMAGE
18、S. 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-1074-1 E 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960i Co
19、ntentsOTA SUPPORT FOR MEIDCONTENTSList of FiguresivList of Tables.vForewordviRevision History.viiIntroduction11 Scope.12 Normative References.13 Editorial Conventions1OTA Subscriber Feature Modifications.22 Subscriber Feature Description.22.1 Over-The-Air Service Provisioning (OTASP)22.1.1 Normal Pr
20、ocedures With Successful Outcome2MAP Part 000 Modifications.52 Part Structure.52.3 References.52.3.1 Normative References53 Definitions and Documentation Conventions.53.1 Definitions.54 Symbols and Abbreviations.6CDMA OTA Automatic Roaming Information Flow Modifications74.1.C1 Transport Encryption P
21、arameters to Serving MSC for OTA.74.32.C1 Serving MSC Attachment to an OTAF94.32.C2 Exchange of OTASP Data Messages.114.32.C3 OTAF Request to Initiate MSC Procedures.124.CC.1 OTAF Request to Initiate AC Procedures148.CC.1a Serving MSC Attached to the Initial and Desired CSC.178.CC.1b Serving MSC Att
22、ached to the Initial and Desired CSC (ALT)198.CC.2a OTASP Call Redirected from Initial CSC to Desired CSC - Initial OTAF not Attached to Serving MSC218.CC.2b Serving MSC Redirected from Initial CSC to Desired CSC238.CC.2c OTASP Call Redirected from Initial CSC to Desired CSC - Initial OTAF Initially
23、 Attached to Serving MSC268.CC.3 A-key Generation.28TIA-1074-1 EContents123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960ii8.CC.4 SSD Update When SSD is Not Shared308.CC.5 Re-Authentication for Voice Privacy, Message Encryption or Both318
24、.CC.7 AC Request to Commit A-Key328.CC.8 AC Request to Release Resources.33TCAP Modifications.341 Application Services.341.3 TCAP Formats and Procedures341.3.2 Component Portion341.3.2.3 TCAP RETURN ERROR Component.342 Operation Definitions.382.2 AuthenticationDirective.382.6 AuthenticationStatusRep
25、ort.392.7 BaseStationChallenge.402.20 FeatureRequest.412.42 OTASPRequest422.50 RegistrationNotification.432.61 SMSDeliveryPointToPoint.44MAP Parameter Signaling Protocol Modifications452.234 SMS_CauseCode45CDMA OTA Signaling Procedures Modifications.494.1 Authentication Directive494.1.3 VLR Receivin
26、g AuthenticationDirective INVOKE494.6 Base Station Challenge.514.6.2 VLR Receiving BaseStationChallenge INVOKE.514.6.3 HLR Receiving BaseStationChallenge INVOKE.524.6.4 AC Receiving BaseStationChallenge INVOKE534.47 SMS Notification544.47.1 HLR Initiating SMSNotification INVOKE.545.C1 OTAF Attachmen
27、t with Serving MSC.545.C1.1 MSC Obtaining a TRN545.C1.3 MSC Receiving an SMDPP INVOKE to Attach with OTAF.555.C2 OTAF Attachment with Serving MSC (ALT).565.C2.2 OTAF Requesting TRN from an Alternate OTAF (ALT)565.C2.4 OTAF Initiating MSC Redirection of an OTASP Call (ALT)575.C3 Exchange of OTASP Dat
28、a Message.605.C3.1 OTAF Initiating SMDPP INVOKE for OTASP Data Message Exchange.605.C4 MSC PROCEDURE TRIGGERS FOR OTASP615.C4.1 OTAF Initiating SMDPP INVOKE for MS Registration615.C4.3 OTAF Initiating SMDPP INVOKE to Record New MSID625.C7 OTASP Request.635.C7.1 OTAF Initiating OTASPRequest INVOKE63T
29、IA-1074-1 E 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960iii Contents5.C7.3 AC Receiving an OTASPREQ INVOKE64TIA-1074-1 EList of Figures12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535
30、4555657585960ivLIST OF FIGURESFigure 4.1.C1 Transport Encryption Parameters to the Serving MSC for OTA.7Figure 4.32.C1 Serving MSC Attachment to an OTAF9Figure 4.32.C2 Exchange of OTASP Data Messages.11Figure 4.32.C3 OTAF Request to Initiate MSC Procedures.12Figure 4.CC.1 OTAF Request to Initiate MS
31、C Procedures.14Figure 8.CC.1a Serving MSC Attached to the Initial and Desired CSC.17Figure 8.CC.1b Serving MSC Attached to the Initial and Desired CSC (ALT).19Figure 8.CC.2a OTASP Call Redirected from Initial CSC to Desired CSC - Initial OTAF not Attached to Serving MSC21Figure 8.CC.2b Serving MSC R
32、edirected from Initial CSC to Desired CSC.23Figure 8.CC.2c OTASP Call Redirected from Initial CSC to Desired CSC - Initial OTAF Initially Attached to Serving MSC26TIA-1074-1 E 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960v List of Tab
33、lesLIST OF TABLESMAP Part 000 ModificationsTable 2 Symbols and Abbreviations6TCAP ModificationsTable 4 Error Codes.37CDMA OTA Signaling Procedures ModificationsTable 2 VLR AuthenticationDirective Response.50Table 14 VLR BaseStationChallenge Response51Table 15 HLR BaseStationChallenge Response52Table
34、 16 AC BaseStationChallenge Response53Table 5.C2.4 Originating MSC RedirectionDirective Response for OTASP.59Table 5.C7.3 AC OTASPRequest Response70TIA-1074-1 EForeword123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960viFOREWORD(This forew
35、ord is not part of this Standard.)This document presents a recommended plan for the implementation of Over-The-Air (OTA)support for the Mobile Equipment Identity (MEID).This document is organized into the following sections:Introduction. This section defines the scope of this document.OTA Subscriber
36、 Feature Modifications. This section specifies the OTA SubscriberFeature modifications needed to support the MEID.MAP Part 000 Modifications. This section specifies the MAP Part 000 modificationsneeded to support the MEID for OTA.CDMA OTA Automatic Roaming Information Flow Modifications. This sectio
37、nspecifies the CDMA OTA automatic roaming information flow modifications required forthe MEID.TCAP Modifications. This section defines new MAP RETURN ERROR Error Codevalues for UnrecognizedMEID and forUnrecognizedMDN.MAP Operations Signaling Protocol Modifications. This section specifies the MAPoper
38、ations signaling protocol modifications needed to add the MEID parameter for OTA.MAP Parameters Signaling Protocol Modifications. This section specifies the MAPparameters signaling protocol modifications needed to support the MEID for OTA.CDMA OTA Signaling Procedures Modifications. This section spe
39、cifies the CDMAOTA signaling procedures modifications for the MEID.TIA-1074-1 E 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960vii Revision HistoryREVISION HISTORYRevision Date Remarks0 November 2005 Initial Publication1 E February 2006
40、 Updated PublicationTIA-1074-1 ERevision History123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960viiiThis page is intentionally left blank.TIA-1074-1 E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
41、4950515253545556575859601ScopeIntroductionINTRODUCTIONThis Standard presents a recommended plan for the implementation of Over-The-Air (OTA)support for the Mobile Equipment Identity (MEID).1ScopeThe purpose of this document is to specify the modifications to MAP and OTA for OTAsupport of the MEID.2
42、Normative ReferencesThe following specifications and standards contain provisions which, through reference in thistext, constitute provisions of this document. At the time of publication, the editions indicatedwere valid. All standards and specifications are subject to revision, and parties to agree
43、mentsbased on this document are encouraged to investigate the possibility of applying the most recenteditions of the standards indicated below. ANSI and TIA maintain registers of currently validnational standards published by them.Telecommunications Industry AssociationMAP TIA-41-E, Mobile Applicati
44、on Part (MAP); 2004MEID TIA-928-B, MAP Support for the Mobile Equipment Identity (MEID); 2005OTA TIA/EIA/IS-725-A, Cellular Radiotelecommunications Intersystem Operations Over-the-Air Service Provisioning (OTASP) and Parameter Administration(OTAPA); 19993 Editorial ConventionsThe following editorial
45、 conventions are used for this document: underline: additioncross out: deletion change bar: indicates additions or deletions new sub-sections are identified in the sub-section headingTIA-1074-1 EOTA Subscriber Feature Modications12345678910111213141516171819202122232425262728293031323334353637383940
46、41424344454647484950515253545556575859602 Subscriber Feature DescriptionOTA SUBSCRIBER FEATURE MODIFICATIONSThis section specifies the OTA Subscriber Feature modifications needed to support the MEID.2 Subscriber Feature Description2.1Over-The-Air Service Provisioning (OTASP)2.1.1 Normal Procedures W
47、ith Successful OutcomeNormal Operation With Successful Outcome(See OTA MAIN, page 6)This section describes a typical sequence of procedures for OTASP invoked from the MS,which results in a successful outcome. It is a service provider specific decision whether tocomplete the procedure in one or multi
48、ple steps.1. A user acquires an OTASP capable MS.2. The user must provide a charged battery or external power source for the MS beforeproceeding with OTASP.3. The user is within the desired home system of the desired service provider service area,or obtains information on how to contact the service
49、provider from outside the desiredservice provider service area.4. The user “powers-on” the MS.5. The user selects which NAM to program (if multiple NAMs are supported).6. A service provider is selected. The following are some of the means by which a serviceprovider may be selected: The MS may be programmed to attempt OTASP with one or more serviceproviders. The MS may scan for all available service providers, and present the user with alist from which to choose. The user may explicitly specify a service provider by entering the OTASP fea
