1、 TIA-1121.008-1-2009 APPROVED: MAY 1, 2009 REAFFIRMED: DECEMBER 2, 2013 TIA-1121.008-1 May 2009Route Control Plane for Ultra Mobile Broadband (UMB) Air Interface Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstan
2、dings 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 p
3、reclude 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 Publ
4、ications 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 pur
5、port 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 tr
6、ademarks 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-0272.008-AD1-RF1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Documen
7、t 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 Document may involve the use of intellectual property right
8、s (“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 TIAs attention, a statement from the holder thereof is request
9、ed, 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 licensing terms or conditions, which are instead left to the part
10、ies 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 complied with as respects the Document or its contents. If the D
11、ocument 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 manda
12、tory, 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
13、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 constitute identification to TIA of a claim of Essential Pa
14、tent(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, EX
15、PRESS 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
16、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 CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT
17、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, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING D
18、AMAGES 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 ELEME
19、NT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0084-008-0 v3.0 CONTENTS iii FOREWORD.xi 1 NOTES . xiii 2 REFERENCES xiii 3 1 Introduction1-1 4 2 Basic Route Control Protocol.2-1 5 2.1 Overview2-1 6 2.2 Primitives, Local Commo
20、n Data, and Public Data2-2 7 2.2.1 Commands 2-2 8 2.2.2 Return Indications.2-2 9 2.2.3 Procedure Calls .2-3 10 2.2.4 Local Common Data 2-3 11 2.2.5 Public Data2-3 12 2.3 Protocol Data Unit.2-3 13 2.4 Procedures and Messages for the InConfiguration Instance of the Protocol2-4 14 2.4.1 Protocol Initia
21、lization for the InConfiguration Protocol Instance.2-4 15 2.4.2 Procedures 2-4 16 2.4.3 Message Formats.2-4 17 2.5 Procedures and Messages for the InUse Instance of the Protocol .2-4 18 2.5.1 Procedures 2-4 19 2.5.1.1 Protocol Initialization for the InUse Protocol Instance.2-4 20 2.5.1.2 Hard Commit
22、 Procedures.2-5 21 2.5.1.3 Soft Commit Procedures 2-5 22 2.5.1.4 UATI Assignment Processing2-5 23 2.5.1.5 LinkID Procedures .2-6 24 2.5.1.6 DataAttachementPoint Procedures.2-6 25 2.5.1.6.1 Access Terminal Procedures.2-6 26 2.5.1.6.2 Access Network Procedures2-8 27 2.5.1.7 SessionAnchor Procedures.2-
23、9 28 2.5.1.7.1 Access Terminal Procedures.2-9 29 2.5.1.7.2 Access Network Procedures2-9 30 2.5.1.8 WaitingToOpen State .2-10 31 3GPP2 C.S0084-008-0 v3.0 CONTENTS iv 2.5.1.8.1 Access Terminal Requirements 2-10 1 2.5.1.8.2 Access Network Requirements .2-12 2 2.5.1.9 Open State 2-12 3 2.5.1.9.1 Access
24、Terminal Requirements 2-12 4 2.5.1.9.2 Access Network Requirements .2-15 5 2.5.1.10 WaitingToClose State.2-15 6 2.5.2 Message Formats 2-16 7 2.5.2.1 RouteOpenRequest2-16 8 2.5.2.2 RouteOpenAccept 2-18 9 2.5.2.3 RouteClose 2-20 10 2.5.2.4 DAPMoveRequest.2-22 11 2.5.2.5 DAPAssignment.2-22 12 2.5.2.6 R
25、outeMap2-24 13 2.5.2.7 RouteMapAck 2-25 14 2.5.2.8 RouteMapRequest .2-26 15 2.5.2.9 UATIAssignment2-26 16 2.5.2.10 UATIComplete .2-27 17 2.5.2.11 RouteCreate 2-28 18 2.5.2.12 RouteOpenReject.2-31 19 2.5.2.13 LinkIDAssignment .2-32 20 2.5.2.14 DAPMoveRequestRequest 2-32 21 2.5.2.15 RouteOpenRequestRe
26、quest2-33 22 2.5.2.16 RouteCreateFailure2-33 23 2.5.2.17 RestartNetworkInterface .2-33 24 2.5.2.18 DAPMoveReject2-34 25 2.5.3 Interface to Other Protocols.2-34 26 2.5.3.1 Commands Sent2-34 27 2.5.3.2 Indications 2-34 28 2.6 Configuration Attributes .2-35 29 2.6.1 Simple Attributes 2-35 30 2.6.2 Comp
27、lex Attributes .2-35 31 2.6.2.1 ATassistedDAPMoveMode Attribute .2-35 32 3GPP2 C.S0084-008-0 v3.0 CONTENTS v 2.7 Non-Attribute Data2-36 1 2.7.1 PagingID2-36 2 2.7.2 SessionSeed 2-37 3 2.8 Protocol Numeric Constants 2-37 4 2.9 Session State Information2-38 5 6 3GPP2 C.S0084-008-0 v3.0 CONTENTS vi No
28、text.1 3GPP2 C.S0084-008-0 v3.0 FIGURES vii Figure 2-1. Route Control Protocol State Diagram (Access Terminal) 2-1 1 Figure 2-2. Route Control Protocol State Diagram (Access Network) .2-2 2 3 3GPP2 C.S0084-008-0 v3.0 FIGURES viii No text.1 3GPP2 C.S0084-008-0 v3.0 TABLES ix Table 2-1. RouteOpenReque
29、stReason encoding2-17 1 Table 2-2. CloseReason encoding .2-21 2 Table 2-3. AllowedPersonalityType encoding.2-30 3 Table 2-4. RejectReason encoding 2-31 4 Table 2-5. RejectReason encoding 2-34 5 Table 2-6. Configuration Attributes 2-35 6 7 3GPP2 C.S0084-008-0 v3.0 TABLES x No text.1 3GPP2 C.S0084-008
30、-0 v3.0 FOREWORD xi (This foreword is not part of this Standard) 1 This Standard was prepared by Technical Specification Group C of the Third Generation 2 Partnership Project 2 (3GPP2). This Standard is the Route Control Plane part of the Ultra 3 Mobile Broadband (UMB)1air interface. Other parts of
31、this Standard are: 4 Overview for Ultra Mobile Broadband (UMB) Air Interface Specification 5 Physical Layer for Ultra Mobile Broadband (UMB) Air Interface Specification 6 MAC Layer for Ultra Mobile Broadband (UMB) Air Interface Specification 7 Radio Link Layer for Ultra Mobile Broadband (UMB) Air In
32、terface Specification 8 Application Layer for Ultra Mobile Broadband (UMB) Air Interface Specification 9 Security Functions for Ultra Mobile Broadband (UMB) Air Interface Specification 10 Connection Control Plane for Ultra Mobile Broadband (UMB) Air Interface Specification 11 Session Control Plane f
33、or Ultra Mobile Broadband (UMB) Air Interface Specification 12 Broadcast-Multicast Upper Layers for Ultra Mobile Broadband (UMB) Air Interface 13 Specification 14 Other Standards may be required to implement this system and are listed in the References 15 section of each part. 16 This standard provi
34、des a specification for land mobile wireless systems based upon cellular 17 principles. This Standard is one part of the IMT-2000 CDMA Multi-Carrier, IMT-2000 18 CDMA MC, also known as cdma20002. 19 1Ultra Mobile Broadband and (UMB) are trade and service marks owned by the CDMA Development Group (CD
35、G). 2cdma2000is 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), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the
36、United States. 3GPP2 C.S0084-008-0 v3.0 FOREWORD xii No text.1 3GPP2 C.S0084-008-0 v3.0 REFERENCES xiii The following documents contain provisions, which, through reference in this text, 1 constitute provisions of this document. References are either specific (identified by date of 2 publication, ed
37、ition number, version number, etc.) or non-specific. For a specific reference, 3 subsequent revisions do not apply. For a non-specific reference, the latest version applies. 4 In the case of a reference to a 3GPP2 document, a non-specific reference implicitly refers to 5 the latest version of that d
38、ocument in the same Release as the present document. 6 7 1 C.S0084-000-0, Overview for Ultra Mobile Broadband (UMB) Air Interface 8 Specification. 9 2 C.S0084-001-0, Physical Layer for Ultra Mobile Broadband (UMB) Air Interface 10 Specification. 11 3 C.S0084-002-0, MAC Layer for Ultra Mobile Broadba
39、nd (UMB) Air Interface 12 Specification. 13 4 C.S0084-003-0, Radio Link Layer for Ultra Mobile Broadband (UMB) Air Interface 14 Specification. 15 5 C.S0084-004-0, Application Layer for Ultra Mobile Broadband (UMB) Air Interface 16 Specification. 17 6 C.S0084-005-0, Security Functions for Ultra Mobil
40、e Broadband (UMB) Air 18 Interface Specification. 19 7 C.S0084-006-0, Connection Control Plane for Ultra Mobile Broadband (UMB) Air 20 Interface Specification. 21 8 C.S0084-007-0, Session Control Plane for Ultra Mobile Broadband (UMB) Air 22 Interface Specification. 23 9 Reserved. 24 10 C.S0084-009-
41、0, Broadcast-Multicast Upper Layer for Ultra Mobile Broadband 25 (UMB) Air Interface Specification. 26 11 C.R1001, Administration of Parameter Value Assignments for cdma2000 Spread 27 Spectrum Standards. (Informative) 28 3GPP2 C.S0084-008-0 v3.0 REFERENCES xiv No text.1 Introduction 3GPP2 C.S0084-00
42、8-0 v3.0 1-1 1 INTRODUCTION 1 Route Control Plane consists of following protocols: 2 Route Control Protocol 3 3GPP2 C.S0084-008-0 v3.0 Introduction 1-2 No text.1 Basic Route Control Protocol 3GPP2 C.S0084-008-0 v3.0 2-1 2 BASIC ROUTE CONTROL PROTOCOL 1 2.1 Overview 2 The Route Control Protocol resid
43、es in the Control Plane. The Route Control Protocol 3 performs the following functions: 4 Controls the creation and deletion of Routes. 5 Maintains mapping between Route identifier (RouteID) and Access Network identifier 6 (ANID). 7 Maintains identity of the DataAttachmentPoint (DAP) Route and Sessi
44、onAnchor Route. 8 UATI and PagingID assignment. 9 A Route consists of an InUse protocol stack associated with an access network. 10 This protocol can be in one of three states: 11 WaitingToOpen State: In this state, a Route to the access network is not configured yet. 12 In this state, the access te
45、rminal sends a RouteOpenRequest message to the access 13 network (unless the access terminal entered this state to perform registration) and 14 waits for the response. 15 Open State: In this state, a Route to the access network is configured (i.e., access 16 network has access terminals session). 17
46、 WaitingToClose State: This state applies only to the access network. In this state the 18 access network waits for the Route close procedure to complete. 19 Figure 2-1 provides an overview of the access terminal states and state transitions. 20 21 Figure 2-1. Route Control Protocol State Diagram (A
47、ccess Terminal) 22 3GPP2 C.S0084-008-0 v3.0 Basic Route Control Protocol 2-2 Figure 2-2 provides an overview of the access network states and state transitions. 1 2 Figure 2-2. Route Control Protocol State Diagram (Access Network) 3 2.2 Primitives, Local Common Data, and Public Data 4 2.2.1 Commands
48、 5 This protocol defines the following commands: 6 CreateNewStack(PilotID) 7 CloseRoute 8 DeleteOldRoutes 9 QueryRouteMap 10 2.2.2 Return Indications 11 This protocol returns the following indications: 12 RouteOpened 13 RouteClosed 14 UATIAssigned(RouteID) 15 DAPAssigned(RouteID) 16 RouteCreated(Rou
49、teCounter) 17 LinkInitialized 18 Basic Route Control Protocol 3GPP2 C.S0084-008-0 v3.0 2-3 2.2.3 Procedure Calls 1 CREATE_ID_TAG 2 Inputs: SequenceNumber 3 Outputs: IDTagSize, IDTag 4 2.2.4 Local Common Data 5 This protocol defines the following Local Common Data (i.e., AT only): 6 PagingIDList 7 RouteCounterGlobal 8 RouteMap (RouteID and ANID of all Routes in Open State) 9 DAPRefreshTime 10 RetryDelayANID 11 CurrentATI (see 1) 12 SessionSignature 13 DAPLinkID 14 SessionAnchorR
