1、 TIA-1151-2009 APPROVED: JANUARY 1, 2009 REAFFIRMED: DECEMBER 2, 2013 TIA-1151 January 2009Signaling Conformance Specification for Ultra Mobile Broadband Air Interface NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings be
2、tween 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 preclude
3、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 Publications
4、 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 purport to
5、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 trademarks
6、 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-0322-RF1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approv
7、ed 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 (“IPR”), inclu
8、ding 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, all in accor
9、dance 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 involved, no
10、r 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 Document contains
11、 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, alternate
12、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 voluntary dis
13、closure (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(s) or publi
14、shed 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 OR IMPLIED
15、, 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 DISCLAIMS ANY AN
16、D 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 PRODUCED OR R
17、ENDERED 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 FOR LOSS
18、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 THE USE OF
19、 THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0091 v1.0 CONTENTS FOREWORD Xv 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 REFERENCES Xvi 1 Overview .1-1 1.1 Scope of This Document1-1 1.2 Objectives1
20、-1 1.3 Requirements Language 1-1 1.4 Document Organization.1-1 1.5 Abbreviations, Acronyms and Terms1-2 1.6 Notation 1-4 2 Basic QoS Management Protocol Tests 2-1 2.1 Basic QoS Management Protocol Access Terminal Tests 2-1 2.1.1 AT Protocol Initialization for InUse Instance.2-2 2.1.2 Stream binding
21、at the AT.2-3 2.1.3 ReservationKKRoRAllowedFwd/Rev Negotiation be AT.2-4 2.1.4 Reservation Closed State Requirements for the AT.2-5 2.1.5 Reservation Open State Requirements for the AT.2-7 2.2 Basic QoS Management Protocol Access Network Tests .2-11 2.2.1 ANSupportedQoSProfiles Negotiation.2-11 2.2.
22、2 AN Protocol Initialization for InUse Instance 2-11 2.2.3 Stream binding at the AN 2-13 2.2.4 Reservation Closed State Requirements for the AN 2-13 2.2.5 Reservation Open State Requirements for the AN 2-15 3 Radio Link Protocol Tests 3-17 3.1 Basic Radio Link Protocol Access Terminal Tests.3-17 3.1
23、.1 AT Transmitter Initiated SAR Reset3-17 3.1.2 AT SAR Receiver response to AN Transmitter Initiated Reset3-20 3.1.3 AT Receiver Initiated SAR Reset.3-21 3.1.4 AT Response to AN Receiver Initiated SAR Reset3-22 3.1.5 StreamEarlyOpenRev Test .3-23 3.1.6 Retransmissions when PhysicalLayerNAKEnableRev
24、is set to 0x013-23 3.1.7 NakAckEnableFwd set to 0x01 and NakDelayTimerSingleCarrier Usage 3-24 3.1.8 ATReceiverStatus transmission when NakAckEnableFwd is set to 0x02.3-25 i 3GPP2 C.S0091 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 3.1.9 AT RL
25、P retransmission when NakAckEnableRev attribute is set to 0x02 .3-26 3.1.10 Flush procedure at the AT.3-27 3.1.11 AbortTimer and OutOfOrderDeliveryFwd Usage at AT3-28 3.1.12 TransmitterStatus Message .3-30 3.2 Basic Radio Link Protocol Access Network Tests .3-31 3.2.1 AN Response to ATReceiverStatus
26、 message .3-31 3.2.2 ANReceiverStatus transmission when NakAckEnableRev is set to 0x02.3-32 3.2.3 Flush procedure at the AN 3-32 3.2.4 AbortTimer Usage at AN 3-33 4 Route Protocol Tests .4-1 4.1 Basic RouteProtocol Access Terminal Tests .4-1 4.1.1 AT Initial Route Establishment Test 4-1 4.1.2 RouteC
27、reation Header transmission in WaitingToOpen state.4-2 4.1.3 RouteCreation with Decentralized SRNC .4-2 4.1.4 Access ATI with Session Active 4-3 4.1.5 Extended Headers with multiple PCP packets in MAC packet4-4 4.1.6 ATI Header Transmission and Reception in BindATI State.4-5 4.1.7 AT Behavior Upon R
28、eceiving various Error Codes4-6 4.2 Basic Route Protocol Access Network Tests .4-8 4.2.1 ATI Header Transmission by the AN 4-8 5 Session Control Protocol Tests 5-1 5.1 Basic Session Control Protocol Access Terminal Tests.5-1 5.1.1 Initial Session Configuration .5-1 5.1.2 Negotiation and Deletion of
29、Personalities.5-3 5.1.3 Soft-Switch and Hard-Switch across Personalities.5-5 5.1.4 Soft-Commit of Static Attributes at Personality Negotiation .5-8 5.1.5 Configuration Message Processing.5-9 5.1.6 SessionSignature Validation5-10 5.1.7 TransactionID Increment.5-11 5.1.8 ATInitiatedConfigurationAllowe
30、d set to 0x0000 .5-12 5.1.9 AttributeReset Message Response .5-12 5.1.10 SessionClose Message Response .5-13 ii 3GPP2 C.S0091 v1.0 CONTENTS 5.1.11 ConfigurationReject Message Transmission .5-14 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 5.1.12 Connection C
31、losed during Session Configuration.5-15 5.1.13 FastConfigurationRequest Processing 5-16 5.2 Basic Session Control Protocol Access Network Tests 5-17 5.2.1 Initial Session Configuration5-17 5.2.2 TransactionID Increment.5-19 6 Route Control Protocol Tests .6-1 6.1 Route Control Protocol Access Termin
32、al Tests .6-1 6.1.1 Initial Route Establishment .6-1 6.1.2 RouteClose and Transmission and Response6-2 6.1.3 DAPMoveRequest Transmission.6-3 6.1.4 UATIAssignment Message Processing.6-4 6.1.5 LinkIDAssignment Message Processing6-5 6.2 Basic Route Control Protocol Access Network Tests.6-6 6.2.1 AN Ini
33、tial Route Establishment Test 6-6 7 Connection Control Protocol Tests.7-1 7.1 Basic Air Link Management Protocol Access Terminal Tests 7-1 7.1.1 Redirect Message processing7-1 7.1.2 Registration Message Transmission .7-1 7.1.3 ConnectionKeepAlive Message Transmission .7-3 7.2 Basic Initialization St
34、ate Protocol Access Terminal Tests .7-3 7.2.1 UnSupported IPSI7-3 7.3 Basic Idle State and Connected State Protocol Access Terminal Tests7-4 7.3.1 ConnectionClose and Page Processing .7-4 7.3.2 AN Basic Connected State Protocol Tests.7-4 7.4 Overhead Message Protocol Access Terminal Tests 7-5 7.4.1
35、ChannelInfoValidityTimers Functionality.7-5 7.5 Basic Active Set Management Protocol Access Terminal Tests .7-5 7.5.1 PilotReport Transmission Tests7-5 7.5.2 VCQI Message Transmission Test 7-6 7.5.3 MACResourceAck Message Transmission Test .7-7 7.5.4 SectorIDResponse Transmission Tests.7-7 iii 3GPP2
36、 C.S0091 v1.0 CONTENTS iv 1 2 3 4 8 Security Functions Tests.8-1 8.1 Basic Key Exchange Protocol Access Terminal Tests .8-1 8.1.1 KeyRequest and KeyComplete message transmission 8-1 9 Figures .9-1 3GPP2 C.S0091 v1.0 (This foreword is not part of this Standard) 1 2 3 4 5 6 This standard was prepared
37、by Technical Specification Group C of the Third Generation Partnership Project 2 (3GPP2). This standard is a companion to the Ultra Mobile Broadband (UMB)1air interface standards. This specification provides a set of procedures that the access terminal and the access network can use to conduct the s
38、ignaling conformance tests in a laboratory environment. 1Ultra Mobile Broadband and (UMB) are trade and service marks owned by the CDMA Development Group (CDG). v 3GPP2 C.S0091 v1.0 REFERENCES 1 2 3 4 5 6 7 9 11 13 15 17 19 21 23 25 26 27 28 29 30 31 32 33 34 35 The following standards and documents
39、 contain provisions, which, through reference in this text, constitute provisions of this specification. 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 possibilit
40、y of applying the most recent editions of the standards indicated below. Normative References 1 C.S0084-000-0, Overview for Ultra Mobile Broadband (UMB) Air Interface 8 Specification. 2 C.S0084-001-0, Physical Layer for Ultra Mobile Broadband (UMB) Air Interface 10 Specification. 3 C.S0084-002-0, MA
41、C Layer for Ultra Mobile Broadband (UMB) Air Interface 12 Specification. 4 C.S0084-003-0, Radio Link Layer for Ultra Mobile Broadband (UMB) Air Interface 14 Specification. 5 C.S0084-004-0, Application Layer for Ultra Mobile Broadband (UMB) Air Interface 16 Specification. 6 C.S0084-005-0, Security Fu
42、nctions for Ultra Mobile Broadband (UMB) Air Interface 18 Specification. 7 C.S0084-006-0, Connection Control Plane for Ultra Mobile Broadband (UMB) Air 20 Interface Specification. 8 C.S0084-007-0, Session Control Plane for Ultra Mobile Broadband (UMB) Air Interface 22 Specification. 9 C.S0084-008-0,
43、 Route Control Plane for Ultra Mobile Broadband (UMB) Air Interface 24 Specification. vi 3GPP2 C.S0038-A v1.0 REFERENCES 1 2 3 5 7 Informative References 10 C.S0084-009-0, Broadcast-Multicast Upper Layer for Ultra Mobile Broadband 4 (UMB) Air Interface Specification. 11 C.R1001, Administration of Pa
44、rameter Value Assignments for cdma2000 Spread 6 Spectrum Standards, Release E. vii 3GPP2 C.S0091 v1.0 REFERENCES viii 1 2 No Text.3GPP2 C.S0091 v1.0 1 0OVERVIEW 1 1.1 9Scope of This Document 2 These technical requirements form a standard for signaling conformance in UMB data systems. These requireme
45、nts ensure that compliant access terminals and compliant access networks can execute tests in meeting the objectives stated in X1.2X. 3 4 5 7 8 9 11 12 13 14 15 16 17 18 20 22 24 25 27 28 30 32 33 35 36 1.2 10Objectives 6 The objective of the test procedures contained herein is to demonstrate that a
46、ccess terminal/access network implementation of signaling functionality in a cabled test environment at nominal levels is in conformance with X1X-X9X. 1.3 11Requirements Language 10 “Shall” and “shall not” identify requirements to be followed strictly to conform to the standard and from which no dev
47、iation 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 possibility o
48、r 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. 1.4 12Document Organization 19 This d
49、ocument is organized into the following sections: Section 1 Overview: This section describes the document scope and objectives as 21 well as document organization, list of acronyms and notations. Section 2 Basic QoS Management Tests: This section describes the test setups, 23 procedures and minimum requirements for the Basic QoS Management Protocol (BQMP) tests. Section 3 Basic Radio Link Protocol Tests: This section describes the test setups, 26 procedures and minimum requirements for the Basic Radio Link Protocol (BRLP) tests. Section 4 Basic Route P
