1、 TIA-1150-2009 APPROVED: JANUARY 1, 2009 REAFFIRMED: DECEMBER 2, 2013 TIA-1150 January 2009Highly Detectable Pilot Specification for cdma2000High Rate Packet Data Air Interface NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misundersta
2、ndings 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 and Publications shall not in any respect
3、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 domestically or internationally. Standards and Pub
4、lications 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 or Publication. This Standard does not pu
5、rport 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 limitations before its use. Any use of t
6、rademarks 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. PN-3-0321-1-RF1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document wil
7、l 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 involve the use of intellectual property rights (“I
8、PR”), 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 statement from the holder thereof is requested, a
9、ll 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 conditions, which are instead left to the parties i
10、nvolved, 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 respects the Document or its contents. If the Docume
11、nt 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 otherwise), whether such reference consists of mandatory,
12、 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 such Normative Reference; (ii) TIAs policy of encouragement of vo
13、luntary 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 constitute identification to TIA of a claim of Essential Patent(
14、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 compliance with the contents of the Document. ALL WARRANTIES, EXPRESS
15、 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 ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCL
16、AIMS 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 PR
17、ODUCED 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 DAMAGE
18、S 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 DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF
19、 THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.P0093-0 v1.0 CONTENTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 FOREWORD . ix REFERENCES xi 1 Overview . 1-1 1.1 Scope of this Document . 1-1
20、1.2 Requirements Language 1-1 1.3 Architecture Reference Model 1-1 1.4 Protocols . 1-2 1.4.1 Interfaces 1-2 1.4.2 InUse and InConfiguration Protocol Instances . 1-2 1.4.2.1 Procedures and Messages 1-2 1.4.2.1.1 Commit Procedures 1-2 1.4.2.2 InConfiguration Protocol Instance Instantiation . 1-2 1.4.2
21、.3 InUse Protocol Instance Instantiation 1-3 1.4.2.4 Protocol Initialization . 1-3 1.4.3 Protocol Negotiation . 1-3 1.5 HDP Channel 1-3 1.6 Terms 1-3 1.7 Notation 1-4 2 HDP Protocol Suite 2-1 2.1 Overview 2-1 2.2 Basic Protocol Numbers . 2-1 2.3 Default HDP Protocol Suite 2-1 2.3.1 Overview 2-1 2.3.
22、2 Primitives and Public Data . 2-1 2.3.2.1 Return Indications . 2-1 2.3.2.2 Public Data 2-1 2.3.3 Protocol Data Unit . 2-1 2.3.4 Protocol Initialization . 2-1 2.3.4.1 Protocol Initialization for the InConfiguration Instance of the Protocol Suite 2-1 2.3.4.2 Protocol Initialization for the InUse Inst
23、ance of the Protocol Suite 2-2 i 3GPP2 C.P0093-0 v1.0 CONTENTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 2.3.5 Procedures and Messages for the InConfiguration Instance of the Protocol Suite . 2-2 2.3.5.1 Procedures 2-2 2.3.5.2 Commit Procedures . 2-2 2
24、.3.5.3 Message Formats . 2-3 2.3.5.3.1 ConfigurationRequest 2-3 2.3.5.3.2 ConfigurationResponse 2-3 2.3.6 Procedures and Messages for the InUse Instance of the Protocol Suite 2-4 2.3.6.1 Procedures 2-4 2.3.6.2 Message Formats . 2-4 2.3.6.3 Interface to Other Protocols . 2-4 2.3.6.3.1 Indications . 2
25、-4 2.3.7 Configuration Attributes 2-4 2.3.8 Protocol Numeric Constants 2-4 2.3.9 Session State Information . 2-4 2.4 Generic HDP Protocol Suite . 2-5 2.4.1 Introduction 2-5 2.4.1.1 Basic Protocol Numbers . 2-5 2.4.1.2 Public Data 2-5 2.4.1.3 Messages . 2-5 2.4.2 Generic HDP Protocol Suite Initializa
26、tion . 2-5 2.4.2.1 Protocol Initialization for the InConfiguration Instance of the Generic HDP Protocol Suite 2-5 2.4.3 Procedures and Messages for the InConfiguration Instance of the Generic HDP Protocol Suite . 2-6 2.4.3.1 Procedures 2-6 2.4.3.2 Commit Procedures . 2-6 2.4.3.3 Message Formats . 2-
27、7 2.4.3.3.1 ConfigurationRequest 2-7 2.4.3.3.2 ConfigurationResponse 2-7 2.4.4 Procedures and Messages for the InUse Instance of the Generic HDP Protocol Suite . 2-8 2.4.4.1 HDP MAC Protocol . 2-8 ii 3GPP2 C.P0093-0 v1.0 CONTENTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 2
28、7 28 29 30 31 32 2.4.4.1.1 Overview 2-8 2.4.4.1.2 Public Data 2-8 2.4.4.1.3 Protocol Data Unit 2-8 2.4.4.1.4 Procedures . 2-9 2.4.4.1.4.1 Access Network Requirements 2-9 2.4.4.1.4.1.1 HDPOverhead Message Transmission . 2-9 2.4.4.1.4.1.2 Timing 2-9 2.4.4.1.4.1.2.1 Planned Coloring 2-10 2.4.4.1.4.1.2.
29、2 Random Coloring 2-11 2.4.4.1.4.2 Access Terminal Requirements . 2-13 2.4.4.1.4.2.1 HDPOverhead Message Processing . 2-13 2.4.4.1.5 Message Format . 2-13 2.4.4.1.5.1 HDPOverhead Message 2-13 2.4.4.2 HDP Physical Layer Protocol 2-17 2.4.4.2.1 Overview 2-17 2.4.4.2.2 Procedures . 2-17 2.4.4.2.2.1 Acc
30、ess Terminal Requirements . 2-17 2.4.4.2.2.2 Access Network Requirements 2-17 2.4.4.2.2.2.1 Frequency Parameters 2-17 2.4.4.2.2.2.2 Power Output Characteristics . 2-17 2.4.4.2.2.2.3 Modulation Characteristics . 2-17 2.4.4.2.2.2.3.1 Forward Channel Structure 2-17 2.4.4.2.2.2.3.2 HDP Channel 2-20 2.4.
31、4.2.2.2.3.2.1 Modulation . 2-20 2.4.4.2.2.2.3.2.2 Orthogonal Spreading . 2-20 The HDP Channel shall be orthogonally spread using the Walsh cover denoted by the parameter HDPWalshCover. . 2-20 2.4.4.2.2.2.3.2.3 Scaling 2-20 2.4.4.2.2.2.3.3 Time Division Multiplexing 2-20 2.4.4.2.2.2.3.4 Quadrature Sp
32、reading 2-20 2.4.4.2.2.2.3.5 Filtering 2-20 2.4.4.2.2.2.3.6 Synchronization and Timing . 2-21 iii 3GPP2 C.P0093-0 v1.0 CONTENTS iv 1 2 3 4 5 6 7 2.4.5 Interface to Other Protocols . 2-21 2.4.5.1 Commands Sent 2-21 2.4.5.2 Indications 2-21 2.4.6 Configurable Attributes . 2-21 2.4.7 Protocol Numerical
33、 Constants . 2-21 2.4.8 Session State Information . 2-21 3GPP2 C.P0093-0 v1.0 FIGURES 1 2 3 4 5 6 7 8 9 10 11 Figure 2.4.4.1.4.1.2.1-1 Architecture Reference Model . 1-1 Figure 2.4.4.1.4.1.2.1-1 Generic HDP Protocol Suite 2-5 Figure 2.4.4.1.4.1.2.1-1 An Example of Planned Coloring . 2-10 Figure 2.4.
34、4.1.4.1.2.1-2 HDP Slot Transmit Timing for Planned Coloring (a) for T/768 mod 3 = 0 (b) T/768 mod 3 = 1 (c) T/768 mod 3 = 2 . 2-11 Figure 2.4.4.1.4.1.2.2-1 HDP Slot Transmit Timing for Random Coloring . 2-13 Figure 2.4.4.2.2.2.3.1-1 Forward Channel Structure 2-18 Figure 2.4.4.2.2.2.3.1-2. Forward Li
35、nk Slot Structure 2-19 Figure 2.4.4.2.2.2.3.1-4. HDP Channel Structure . 2-20 v 3GPP2 C.P0093-0 v1.0 FIGURES vi 1 This page is intentionally left blank. 3GPP2 C.P0093-0 v1.0 TABLES 1 2 3 4 5 6 Table 2.4.4.1.4.1.2.1-1 HDPOffset2(C,T) for Planned Coloring, if NumHDPSlot = 0 . 2-10 Table 2.4.4.1.4.1.2.
36、2-1 HDP Color Code . 2-12 Table 2.4.4.1.4.1.2.2-2 HDPOffset2 for Random Coloring, if NumHDPSlot = 0 2-12 Table 2.4.7-1 Numeric Constants . 2-21 vii 3GPP2 C.P0093-0 v1.0 TABLES viii 1 This page is intentionally left blank. 3GPP2 C.P0093-0 v1.0 FOREWORD 1 2 3 4 5 6 7 (This foreword is not part of this
37、 Standard) This Standard was prepared by Technical Specification Group C of the Third Generation Partnership Project 2 (3GPP2). This Standard contains the highly detectable pilot specifications of the CDMA High Rate Packet Data Air Interface Specification 1 of the IMT-2000 CDMA Multi-Carrier Mode. O
38、ther specifications are required to complete the air interface and the rest of the system. ix 3GPP2 C.P0093-0 v1.0 FOREWORD x 1 This page is intentionally left blank. 3GPP2 C.P0093-0 v1.0 REFERENCES 1 2 3 4 5 6 8 10 11 The following standards contain provisions that, through reference in this text,
39、constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated
40、 below. 1 3GPP2 C.S0024-B Version 2.0, cdma2000 High Rate Packet Data Air Interface 7 Specification, March 2007. 2 3GPP2 C.S0057-C Version 1.0, Band Class Specification for cdma2000 Spread 9 Spectrum Systems, July 2008. xi 3GPP2 C.P0093-0 v1.0 REFERENCES xii 1 This page is intentionally left blank.
41、3GPP2 C.P0093-0 v1.0 1 OVERVIEW 1 1.1 Scope of this Document 2 These technical requirements form the compatibility standard for cdma20001highly detectable pilot systems. These requirements ensure that a compliant access terminal can obtain service through any access network conforming to this standa
42、rd. These requirements do not address the quality or reliability of that service, nor do they cover equipment performance or measurement procedures. 3 4 5 6 7 9 10 11 12 13 14 15 16 17 18 19 20 21 23 1.2 Requirements Language 8 Compatibility, as used in connection with this standard, is understood t
43、o mean: Any access terminal can obtain service through any access network conforming to this standard. Conversely, all access networks conforming to this standard can service access terminals. “Shall” and “shall not” identify requirements to be followed strictly to conform to the standard and from w
44、hich no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain po
45、ssibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical, or causal. Footnotes appear at variou
46、s points in this standard to elaborate and further clarify items discussed in the body of the standard. 1.3 Architecture Reference Model 22 The architecture reference model is presented in Figure 2.4.4.1.4.1.2.1-1. 24 25 26 Figure 2.4.4.1.4.1.2.1-1 Architecture Reference Model The access terminal, t
47、he access network, and the sector are formally defined in 1.6. 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000is a registered trademark of the
48、 Telecommunications Industry Association (TIA-USA) in the United States. 1-1 3GPP2 C.P0093-0 v1.0 The reference model includes the air interface between the access terminal and the access network. The protocols used over the air interface are defined in this standard. 1 2 5 6 7 8 1.4 Protocols 3 1.4
49、.1 Interfaces 4 This standard defines a set of interfaces for communications between a protocol executing in one entity and the same protocol executing in the other entity. The generic term “entity” is used to refer to the access terminal and the access network. Protocols in this standard have three types of interfaces: Headers and messages are used for communications between a protocol executing in 9 one entity and the same protocol executing in the other entity. 10 Indications are used by a protocol to convey information regarding the occurrence of 11 an event. Any pr
