1、 TIA-158-1E November 2011Over-the-Air Service Provisioning for MEID Equipped Mobile Stations in Spread Spectrum Systems 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 manufacturi
3、ng 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 Ameri
4、can 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
5、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 limitations before its use. (From Project No. 3-0180-AD1, 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. C.S0066-0 v2.0 2008 3GPP2. Revision History Revision Description Date C.S0066-0 v1.0 Initial publication 27 August 2004 C.S0066-
19、0 v2.0 25 July 2008 C.S0066-0 v2.0 i CONTENTS 1 1 INTRODUCTION.1-1 2 2 Changes required for Enhanced Protocol Capability Messaging2-1 3 3.3 Programming Procedure.2-1 4 3.3.1 OTASP Data Message Processing2-1 5 3.5.1.17 Extended Protocol Capability Response Message2-2 6 4.3 Programming Data Download2-
20、8 7 4.3.1 OTA Data Message Processing.2-8 8 4.5.1.7 Protocol Capability Request Message.2-8 9 C.S0066-0 v2.0 ii REFERENCES 1 The following standards are referenced in this text. At the time of publication, the editions 2 indicated were valid. All standards are subject to revision, and parties to agr
21、eements 3 based upon this document are encouraged to investigate the possibility of applying the 4 most recent editions of the standards indicated below. ANSI and TIA maintain registers of 5 currently valid national standards published by them. 6 1. TIA/EIA-95-B, Mobile Station-Base Station Compatib
22、ility Standard for Dual-Mode Spread 7 Spectrum Cellular System, March 1999. 8 2. TIA/EIA/IS-683, Over-the-Air Service Provisioning of Mobile Stations in Wideband 9 Spread Spectrum Systems, February 1997. 10 3. 3GPP2 C.S0016-0, Over-the-Air Service Provisioning of Mobile Stations in Spread 11 Spectru
23、m Systems, December 1999. 12 4. 3GPP2 C.S0016-A, Over-the-Air Service Provisioning of Mobile Stations in Spread 13 Spectrum Systems, December 2001. 14 5. 3GPP2 C.S0016-B, Over-the-Air Service Provisioning of Mobile Stations in Spread 15 Spectrum Standards, October 2002. 16 6. Reserved. 17 7. 3GPP2 C
24、.S0005-D, “Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread 18 Spectrum Systems Release D”, March 2004. 19 8. 3GPP2 C.S0006-D, “Analog Signaling Standard for cdma2000 Spread Spectrum 20 Systems Release D”, March 2004. 21 9. 3GPP2 C.S0024-A, “cdma2000 High Rate Packet Data Air Interface S
25、pecification”, 22 March 2004. 23 10. 3GPP2 S.R0048-A, 3G Mobile Equipment Identifier (MEID) Stage 1, May 2004. 24 11. 3GPP2 C.S0057-0, Band Class Specification for cdma2000 Spread Spectrum Systems, 25 February 2004. 26 12. 3GPP2 C.S0023-C, Removable User Identity Module for Spread Spectrum Systems,
26、June 27 2006. 28 29 30 31 C.S0066-0 v2.0 1-1 1 INTRODUCTION 1 This Standard was prepared by Technical Specification Group C of the Third Generation 2 Partnership Project 2 (3GPP2). This Standard presents recommendations for supporting a 3 mobile station equipped with a Mobile Equipment IDentifier (M
27、EID) 10 in the OTASP 4 Systems defined in 2, 3, 4 and 5. 5 The OTASP feature allows a potential wireless service subscriber to activate (i.e., become 6 authorized for) new wireless service, and allows an existing wireless subscriber to make 7 changes in existing services without the intervention of
28、a third party. 8 For the initial provisioning, the Electronic Serial Number (ESN) is used to identify the 9 mobile station. ESN is a 32-bit number assigned by the mobile station manufacturer, 10 uniquely identifying the mobile station equipment. Due to the ESN exhaustion, the MEID 11 was introduced
29、in the cdma20001 systems as the alternative to ESN for new mobile 12 stations complying with 7. 13 During the migration period from ESN to MEID, Pseudo-ESN is used by the MEID-14 equipped mobile stations. Pseudo-ESN is a 32-bit number derived from MEID and used in 15 place of ESN. For the provisioni
30、ng, however, Pseudo-ESN may not be used to uniquely 16 identify a particular mobile station since Pseudo-ESN is not unique. 17 In order to solve this problem, the following new capability is introduced in this Standard. 18 Enhanced Protocol Capability Messaging - This provides the means for the base
31、 station 19 to ascertain the detailed capabilities of the mobile station, such as supported band 20 classes, operating modes, MEID, SF_EUIMID and LF_EUIMID. 21 This Standard uses the same structure and section numbering as 2, 3, 4 and 5, 22 except for all the references. Sections of this Standard th
32、at remain unchanged relative to 23 2, 3, 4 and 5 are represented using ellipses contained within brackets (.). Modified 24 sections are either reproduced in their entirety or use the . notation to represent 25 unchanged portions. Within modified sections, change bars indicate the specific 26 paragra
33、phs, figures, or table cells that have changed. Within modified paragraphs and 27 table cells, strike-throughs indicate deleted text and underlines indicate new text. 28 1 cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners
34、 (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. C.S0066-0 v2.0 1-2 1 No text. 2 C.S0066-0 v2.0 2-1 2 CHANGES REQUIRED FOR ENHANCED PROTOCOL CAPABILITY MESSAGING 1 2
35、3.3 Programming Procedure 3 3.3.1 OTASP Data Message Processing 4 The mobile station shall discard all OTASP Data Messages received, if the programming 5 procedure is not initiated as described in 3.2 or when the mobile station is in any state, 6 substate or task other than the CDMA Conversation Sub
36、state or the analog Conversation Task. 7 If the mobile station is in the Mobile Station Control on the Traffic Channel State, the mobile 8 station shall send the Mobile Station Reject Order with ORDQ equal to 00000010. 9 While in the CDMA Conversation Substate or the analog Conversation Task, the mo
37、bile station 10 shall process OTASP Data Messages as follows: 11 12 7. Protocol Capability Request Message: If the Protocol Capability Request Message contains 13 the OTASP_P_REV field and the mobile station is able to parse it, then the mobile 14 station shall send the Extended Protocol Capability
38、Response Message within 750 ms 15 after receiving the message; otherwise, the mobile station shall send a Protocol 16 Capability Response Message within 750 ms after receiving the message.The mobile 17 station shall send a Protocol Capability Response Message or an Extended Protocol 18 Capability Re
39、sponse Message within 750 ms after receiving the message. If the 19 Protocol Capability Request Message contains the OTASP_P_REV field and the mobile 20 station is able to parse it, then the mobile station shall send the Extended Protocol 21 Capability Response Message; otherwise, the mobile station
40、 shall send the Protocol 22 Capability Response Message. 23 24 C.S0066-0 v2.0 2-2 3.5.1.17 Extended Protocol Capability Response Message 1 The Extended Protocol Capability Response Message has the following variable-length format: 2 Field Length (bits) OTASP_MSG_TYPE (00010000) 8 OTASP_MOB_P_REV 8 M
41、OB_FIRM_REV 16 MOB_MODEL 8 NUM_FEATURES 8 NUM_FEATURES occurrences of the following features: FEATURE_ID 8 FEATURE_P_REV 8 NUM_CAP_RECORDS 8 NUM_CAP_RECORDS occurrences of the following records: CAP_RECORD_TYPE 8 CAP_RECORD_LEN 8 Type-specific field 8 RECORD_LEN 3 OTASP_MSG_TYPE - OTASP Data Message
42、 type. 4 The mobile station shall set this field to 00010000. 5 OTASP_MOB_P_REV - OTASP Mobile Protocol Revision. 6 The mobile station shall set this field to the value shown in the 7 following table. 8 C.S0066-0 v2.0 2-3 1 OTASP_MOB_P_REV (Binary) Associated Standard 00000000 2 00000001 3 00000010
43、4 00000011 5 00000100 Reserved2 All other values are reserved. 2 MOB_FIRM_REV - Mobile station firmware revision number. 3 The mobile station shall set this field to the value of the 4 MOB_FIRM_REVp permanent mobile station indicator (see F.2.1 5 of 1, 7). 6 MOB_MODEL - Mobile station manufacturers
44、model number. 7 The mobile station shall set this field to the value of the 8 MOB_MODELp permanent mobile station indicator (see F.2.1 of 9 1, 7). 10 NUM_FEATURES - Number of Features. 11 The mobile station shall set this field to the number of features 12 supported by the mobile station using the O
45、TASP protocol. 13 FEATURE_ID - Feature Identifier. 14 The mobile station shall set this field according to Table 3.5.1.7-1 15 to indicate the feature supported by the mobile station. 16 FEATURE_P_REV - Feature protocol version. 17 The mobile station shall set this field according to Table 3.5.1.7-1
46、18 to indicate the protocol version of the feature supported by the 19 mobile station. 20 NUM_CAP_RECORDS - Number of Capability Records. 21 The mobile station shall set this field to the number of Capability 22 Records contained in the Extended Protocol Capability Response 23 Message. 24 25 The mob
47、ile station shall include all the records requested in the corresponding Protocol 26 Capability Request Message. The mobile station shall include the following fields for each 27 capability record to be included: 28 2 This value is reserved for designating the next revision of 5. C.S0066-0 v2.0 2-4
48、1 CAP_RECORD_TYPE - Capability Record Type. 2 The mobile station shall set this field to the record type value 3 shown in Table 3.5.1.17.1-1 corresponding to the type of this 4 information record. 5 CAP_RECORD_LEN - Capability Record Length. 6 The mobile station shall set this field to the number of
49、 octets 7 included in the type-specific fields of this information record. If 8 the mobile station doesnt support a requested 9 CAP_RECORD_TYPE or supports a requested 10 CAP_RECORD_TYPE, but doesnt have a value, the mobile station 11 shall include the CAP_RECORD_TYPE with the 12 CAP_RECORD_LEN field set to 00000000. 13 Type-specific field - Type-specific field. 14 The mobile station shall set these fields to the information as 15 specified in 3.5.1.17.1 for the specific type of records. 16 17 3.5.1.17.1 Ca
