1、 TIA-1134 August 2009 Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces NOTICE 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 34 35 36 TIA Engineering Standards and Publications are designed to serve the p
2、ublic interest through eliminating misunderstandings 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 Standa
3、rds and Publications shall not in any respect 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 dome
4、stically or internationally. Standards and Publications 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 Stan
5、dard or Publication. This Standard does not purport 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 regul
6、atory limitations before its use. (From Project No. 3-0285, formulated under the cognizance of the 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 ch
7、anged 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”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. Whe
8、n 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 accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, t
9、he 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, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not wa
10、rrant 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 one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, de
11、velopment or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4th edition) then (i) TIA disclaims any duty or obligation to
12、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 disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply;
13、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 published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not
14、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, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS O
15、R APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY 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 COM
16、PLIANCE 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 RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR REL
17、ATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, 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 (INCL
18、UDING 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 THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-1134 i 1 2 3 4 5 6 7 8 9
19、 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 Table of Contents Foreword xiv 1 Introduction.1-1 1.1 Overview.1-1 1.1.1 Purpose1-1 1.1.2 Scope.1-1 1.1.3 Document Convention 1-1 1.2 References.1-1 1.2.1 Normative References.1-1 1.2.2 Informative References.1-3 1.
20、3 Terminology1-3 1.3.1 Acronyms1-3 1.3.2 UMB Definitions 1-4 1.3.3 UMB Notations.1-5 1.3.3.1 Tunneling of Reverse-link Route Protocol Packet 1-5 1.3.3.2 Tunneling of Forward-link Route Protocol Packet .1-6 1.4 UMB IOS Architecture Reference Model 1-7 1.4.1 Network Element Functional Descriptions.1-8
21、 1.4.1.1 Access Gateway 1-8 1.4.1.2 Evolved Base Station.1-8 1.4.1.3 Session Reference Network Controller .1-9 1.4.2 Reference Point Descriptions1-9 1.4.3 Protocol Interface Descriptions.1-9 1.5 Message Body, Coding, Ordering, and Interpretation of IEs1-10 1.6 Forward Compatibility Guidelines .1-10
22、1.7 Message Processing Guidelines1-11 1.8 Message Definition Guidelines.1-12 1.9 UMB IOS Assumptions 1-12 1.9.1 Connectivity Assumptions among Network Elements .1-12 1.9.2 PMIP Bearer Tunnel Management Guidelines .1-13 1.9.3 UMB Mobility Concepts.1-13 1.9.4 UMB Security Key Concepts1-14 1.10 UMB Fea
23、ture Descriptions .1-16 1.10.1 Explicitly Supported Features.1-16 1.10.1.1 AT Originates a UMB Session1-16 1.10.1.2 Route Set Add and Remove 1-16 1.10.1.3 Session Negotiation.1-16 TIA-1134 ii 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 34 35 36 37 1.10.1
24、4 UMB Data Delivery (both AT Terminated and AT Originated).1-16 1.10.1.5 Forward and Reverse Link Serving eBS (FLSE/RLSE) Switch .1-16 1.10.1.6 Data Attachment Point (DAP) Handoff 1-16 1.10.1.7 Idle and Active Session Reference Transfer .1-16 1.10.1.8 Idle State Mobility and Paging1-16 1.10.1.9 Pac
25、ket Data Session Release .1-16 1.10.1.10 UMB Session Release .1-16 1.10.1.11 AT and Network Initiated Neighbor Discovery 1-16 2 UMB IOS Interfaces .2-1 2.1 Transport Network IP Quality of Service (QoS) Framework for GRE Tunnels.2-1 2.2 IAS (Inter-ANRI Signaling) Interface 2-1 2.2.1 IAS Interface Net
26、work/Transport Protocol Specification.2-1 2.2.2 IAS Interface Message Procedures .2-2 2.2.2.1 IAS-Session Information Request .2-3 2.2.2.1.1 Successful Operation.2-3 2.2.2.1.1.1 Session Information Retrieval triggered by RouteOpenRequest.2-3 2.2.2.1.1.2 Session Information Retrieval triggered by Ses
27、sion Updated.2-4 2.2.2.1.1.3 Session Information Retrieval Triggered by UMB Session Release Procedure Initiated by SRNC .2-4 2.2.2.1.2 Failure Operation.2-4 2.2.2.2 IAS-Session Information Response.2-4 2.2.2.2.1 Successful Operation.2-4 2.2.2.2.1.1 Session Retrieval as a result of RouteOpenRequest2-
28、4 2.2.2.2.1.2 Session Retrieval as a result of Session Update 2-5 2.2.2.2.2 Failure Operation.2-6 2.2.2.3 IAS-Session Information Update Request.2-7 2.2.2.3.1 Successful Operation.2-7 2.2.2.3.2 Failure Operation.2-7 2.2.2.4 IAS-Session Information Update Response 2-7 2.2.2.4.1 Successful Operation.2
29、7 2.2.2.4.2 Failure Operation.2-8 2.2.2.5 IAS-SRNC Transfer Request 2-9 2.2.2.5.1 Successful Operation.2-9 2.2.2.5.2 Failure Operation.2-9 2.2.2.6 IAS-SRNC Transfer Response2-9 2.2.2.6.1 Successful Operation.2-10 2.2.2.6.1.1 SRNC Transfer to ANRI in the current Route Set 2-10 TIA-1134 iii 1 2 3 4 5
30、 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 34 35 36 37 2.2.2.6.1.2 SRNC Transfer to outside the current Route Set.2-11 2.2.2.6.2 Failure Operation.2-12 2.2.2.7 IAS-Session Release .2-13 2.2.2.7.1 Successful Operation.2-13 2.2.2.7.1.1 Session Release for AT in Co
31、nnected State 2-13 2.2.2.7.1.2 Session Release for AT in Idle State .2-13 2.2.2.7.2 Failure Operation.2-13 2.2.2.8 IAS-Session Release Ack2-14 2.2.2.8.1 Successful Operation.2-14 2.2.2.8.2 Failure Operation.2-14 2.2.2.9 IAS-UATI Update .2-14 2.2.2.9.1 Successful Operation.2-14 2.2.2.9.1.1 UATI Chang
32、e Operation .2-14 2.2.2.9.1.2 Route Set Add Operation 2-15 2.2.2.9.2 Failure Operation.2-15 2.2.2.10 IAS-UATI Update Ack .2-15 2.2.2.10.1 Successful Operation.2-15 2.2.2.10.2 Failure Operation.2-16 2.2.2.11 IAS-Paging Request 2-16 2.2.2.11.1 Successful Operation.2-16 2.2.2.11.2 Failure Operation.2-1
33、6 2.2.2.12 IAS-Paging Request Ack.2-16 2.2.2.12.1 Successful Operation.2-16 2.2.2.12.2 Failure Operation.2-17 2.2.2.13 IAS-Page .2-17 2.2.2.13.1 Successful Operation.2-17 2.2.2.13.2 Failure Operation.2-18 2.2.2.14 IAS-Page Ack2-18 2.2.2.14.1 Successful Operation.2-18 2.2.2.14.2 Failure Operation.2-1
34、8 2.2.2.15 IAS-Neighbor Discovery Request.2-19 2.2.2.15.1 Successful Operation.2-19 2.2.2.15.2 Failure Operation.2-19 2.2.2.16 IAS-Neighbor Discovery Report.2-19 2.2.2.16.1 Successful Operation.2-19 2.2.2.16.2 Failure Operation.2-19 2.2.2.17 IAS-Neighbor Discovery Report Ack .2-20 TIA-1134 iv 1 2 3
35、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 34 35 36 37 38 2.2.2.17.1 Successful Operation.2-20 2.2.2.17.2 Failure Operation.2-20 2.2.2.18 IAS-Reject.2-20 2.2.2.18.1 Successful Operation.2-20 2.2.2.18.2 Failure Operation.2-20 2.2.3 IAS Interface Protocol Proce
36、dures2-20 2.2.3.1 Procedure for Maintaining the Access Counter.2-20 2.2.3.2 Procedure for Including Derived MSK Parameter SSIR in the Session State Information Record IE.2-21 2.2.3.3 Procedure for Determining whether the Derived MSK is Valid .2-21 2.2.3.4 Procedure for Maintaining the Route Counter
37、2-22 2.2.3.5 Procedure for Maintaining the Session Signature .2-22 2.2.3.6 Exclusive Control of Session State Information Record.2-23 2.2.3.6.1 Unlock State 2-23 2.2.3.6.2 Lock State2-23 2.3 IPT (IP Tunneling) Interface.2-23 2.3.1 IPT Interface Network/Transport Protocol Specification .2-24 2.3.2 IP
38、T data L2TPv3 Headers.2-24 2.3.3 IPT Interface Network/Transport Protocol Procedure 2-26 2.3.3.1 IPT Packet Tunneling Operations .2-26 2.3.3.1.1 GRE packet is Received from the AGW while the AT is active.2-26 2.3.3.1.2 Forward-link IPT Packet is Received while the AT is active2-27 2.3.3.1.3 Forward-
39、link Packet is Received either through GRE or IPT while the AT is Idle.2-27 2.3.3.1.4 Reverse-link IP Packet is Received.2-27 2.3.3.1.5 Reverse-link IPT Packet is Received 2-28 2.3.4 IPT Interface Protocol Procedure2-28 2.3.4.1 Procedure for Maintaining DAP Counter2-28 2.3.5 IPT Interface Message Pr
40、ocedures2-29 2.3.5.1 IPT-Notification 2-29 2.3.5.1.1 Successful Operation.2-29 2.3.5.1.1.1 FLSE Switch Operation - Target FLSE Procedure .2-29 2.3.5.1.1.2 FLSE Switch Operation - Source FLSE Procedure.2-30 2.3.5.1.1.3 FLSE Switch Operation - DAP Procedure 2-30 2.3.5.1.1.4 RLSE Switch Operation - Tar
41、get RLSE Procedure 2-30 2.3.5.1.1.5 RLSE Switch Operation - Source RLSE Procedure2-31 2.3.5.1.1.6 DAP Switch Operation2-31 2.3.5.1.1.7 Connection Close Operation .2-31 TIA-1134 v 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 34 35 36 37 2.3.5.1.1.8 Connect
42、ion Lost Operation .2-32 2.3.5.1.1.9 Route Set Add Operation 2-32 2.3.5.1.1.10 Route Set Remove Operation2-33 2.3.5.1.1.11 Packet Data Session Release .2-33 2.3.5.1.2 Failure Operation.2-33 2.3.5.2 IPT-Notification Ack.2-33 2.3.5.2.1 Successful Operation.2-33 2.3.5.2.1.1 FLSE Switch Operation - Sour
43、ce FLSE Procedure.2-34 2.3.5.2.1.2 FLSE Switch Operation - Target FLSE Procedure .2-34 2.3.5.2.1.3 RLSE Switch Operation - Source RLSE Procedure2-34 2.3.5.2.1.4 RLSE Switch Operation - Target RLSE Procedure 2-34 2.3.5.2.1.5 DAP Switch Operation - FLSE Procedure 2-35 2.3.5.2.1.6 DAP Switch Operation
44、 DAP Procedure .2-35 2.3.5.2.2 Failure Operation.2-35 2.3.5.3 IPT-Flush.2-35 2.3.5.3.1 Successful Operation.2-35 2.3.5.3.1.1 FLSE Switch Operation - Source FLSE Procedure.2-35 2.3.5.3.1.2 FLSE Switch Operation - Target FLSE Procedure .2-35 2.3.5.3.1.3 RLSE Switch Operation - Source RLSE Procedure2-
45、35 2.3.5.3.1.4 RLSE Switch Operation - Target RLSE Procedure 2-35 2.3.5.3.2 Failure Operation.2-36 2.3.5.4 IPT-Reject .2-36 2.3.5.4.1 Successful Operation.2-36 2.3.5.4.2 Failure Operation.2-36 2.4 LLT (Link-Layer Tunneling) Interface.2-36 2.4.1 LLT Interface Network/Transport Protocol Specification2
46、36 2.4.2 LLT Interface Network/Transport Protocol Procedure.2-39 2.4.2.1 LLT Packet Tunneling Operations 2-39 2.4.2.1.1 An ANRI Generates a Unicast Link-layer Packet.2-39 2.4.2.1.2 An ANRI Receives a Unicast Forward-link LLT Packet2-40 2.4.2.1.3 An ANRI Receives a Reverse-link LLT Packet2-40 2.4.2.
47、1.4 An RLSE Receives a Tunneled Link-layer Packet Over the Air for Another Route2-41 2.4.2.1.5 An eBS Needs to Tunnel a Broadcast Message through Another eBS .2-42 2.5 PMIP (Proxy Mobile IP) Interface2-42 2.5.1 PMIP Signaling Interface2-43 2.5.1.1 PMIP Signaling Interface Network/Transport Protocol
48、Specification 2-43 TIA-1134 vi 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 34 35 36 37 2.5.1.2 PMIP Tunnel Establishment2-43 2.5.1.2.1 Initial PMIP Tunnel Setup with the AGW 2-44 2.5.1.2.1.1 Successful Operation.2-44 2.5.1.2.1.2 Failure Operation.2-45 2.
49、5.1.2.2 eBS Added to the Route Set2-45 2.5.1.2.2.1 Successful Operation.2-46 2.5.1.2.2.2 Failure Operation.2-46 2.5.1.2.3 eBS Becomes the DAP2-46 2.5.1.3 PMIP Signaling-Only Binding 2-47 2.5.1.3.1 PMIP Signaling-Only Binding Establishment Procedures2-47 2.5.1.3.2 PMIP Signaling-Only Binding Configuration.2-47 2.5.1.3.3 AGW Sends Data Notification to SRNC or eBS.2-47 2.5.1.3.3.1 Successful Operation.2-47 2.5.1.3.3.2 Failure Operation.2-47 2.5.1.4 PMIP Registration Refresh2-47 2.5.1.4.1 PMIP Registration Refresh Procedures.2-47 2.5.1.4.1.1 Successful Operation.2-48 2.5.1.4.1.2 Failure Operat
