1、 TIA-1134-1-2009 APPROVED: AUGUST 1, 2009 REAFFIRMED: DECEMBER 2, 2013 TIA-1134-1 (Addendum to TIA-1134) August 2009Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces NOTICE TIA Engineering Standards and Publications are designed to serve the public
2、 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 Standards a
3、nd 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 domestica
4、lly 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 Standard
5、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 regulatory
6、 limitations before its use. (From Project No. 3-0285-AD1-RF1, 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
7、 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”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR.
8、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 accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into
9、, 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, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not
10、 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 one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation,
11、 development 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, 4thedition) then (i) TIA disclaims any duty or obligation t
12、o 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 no
14、t 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
15、 OR 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 C
16、OMPLIANCE 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 R
17、ELATING 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 (IN
18、CLUDING 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-1 i Table of Cont
19、ents 1 Foreword. xv 2 1 Introduction.1-1 3 1.1 Overview.1-1 4 1.1.1 Purpose1-1 5 1.1.2 Scope.1-1 6 1.1.3 Document Convention 1-1 7 1.2 References.1-1 8 1.2.1 Normative References.1-1 9 1.2.2 Informative References.1-2 10 1.3 Terminology1-3 11 1.3.1 Acronyms1-3 12 1.3.2 UMB Definitions 1-4 13 1.3.3 U
20、MB Notations.1-6 14 1.3.3.1 Tunneling of Reverse-link Route Protocol Packet 1-6 15 1.3.3.2 Tunneling of Forward-link Route Protocol Packet .1-6 16 1.4 UMB IOS Architecture Reference Model 1-8 17 1.4.1 Network Element Functional Descriptions.1-8 18 1.4.1.1 Access Gateway 1-8 19 1.4.1.2 Evolved Base S
21、tation.1-9 20 1.4.1.3 Session Reference Network Controller .1-9 21 1.4.2 Reference Point Descriptions1-9 22 1.4.3 Protocol Interface Descriptions.1-9 23 1.5 Message Body, Coding, Ordering, and Interpretation of IEs1-10 24 1.6 Forward Compatibility Guidelines .1-11 25 1.7 Message Processing Guideline
22、s1-11 26 1.8 Message Definition Guidelines.1-12 27 1.9 UMB IOS Assumptions 1-12 28 1.9.1 Connectivity Assumptions among Network Elements .1-13 29 1.9.2 PMIP Bearer Tunnel Management Guidelines .1-13 30 1.9.3 UMB Mobility Concepts.1-14 31 1.9.4 UMB Security Key Concepts1-14 32 1.10 UMB Feature Descri
23、ptions .1-16 33 1.10.1 Explicitly Supported Features.1-16 34 1.10.1.1 AT Originates a UMB Session1-16 35 1.10.1.2 Route Set Add and Remove 1-16 36 1.10.1.3 Session Negotiation.1-16 37 TIA-1134-1 ii 1.10.1.4 UMB Data Delivery (both AT Terminated and AT Originated).1-16 1 1.10.1.5 Forward and Reverse
24、Link Serving eBS (FLSE/RLSE) Switch .1-16 2 1.10.1.6 Data Attachment Point (DAP) Handoff 1-16 3 1.10.1.7 Idle and Active Session Reference Transfer .1-16 4 1.10.1.8 Idle State Mobility and Paging1-16 5 1.10.1.9 Packet Data Session Release .1-16 6 1.10.1.10 UMB Session Release .1-16 7 1.10.1.11 AT an
25、d Network Initiated Neighbor Discovery 1-16 8 2 UMB IOS Interfaces .2-1 9 2.1 Transport Network IP Quality of Service (QoS) Framework for GRE Tunnels.2-1 10 2.2 IAS (Inter-ANRI Signaling) Interface 2-1 11 2.2.1 IAS Interface Network/Transport Protocol Specification.2-1 12 2.2.2 IAS Interface Message
26、 Procedures .2-2 13 2.2.2.1 IAS-Session Information Request .2-3 14 2.2.2.1.1 Successful Operation.2-3 15 2.2.2.1.1.1 Session Information Retrieval triggered by RouteOpenRequest.2-3 16 2.2.2.1.1.2 Session Information Retrieval triggered by Session Updated.2-3 17 2.2.2.1.1.3 Session Information Retri
27、eval Triggered by UMB Session Release Procedure 18 Initiated by SRNC .2-4 19 2.2.2.1.2 Failure Operation.2-4 20 2.2.2.2 IAS-Session Information Response.2-4 21 2.2.2.2.1 Successful Operation.2-4 22 2.2.2.2.1.1 Session Retrieval as a result of RouteOpenRequest2-4 23 2.2.2.2.1.2 Session Retrieval as a
28、 result of Session Update 2-5 24 2.2.2.2.2 Failure Operation.2-6 25 2.2.2.3 IAS-Session Information Update Request.2-7 26 2.2.2.3.1 Successful Operation.2-7 27 2.2.2.3.2 Failure Operation.2-7 28 2.2.2.4 IAS-Session Information Update Response 2-7 29 2.2.2.4.1 Successful Operation.2-7 30 2.2.2.4.2 Fa
29、ilure Operation.2-8 31 2.2.2.5 IAS-SRNC Transfer Request 2-9 32 2.2.2.5.1 Successful Operation.2-9 33 2.2.2.5.2 Failure Operation.2-9 34 2.2.2.6 IAS-SRNC Transfer Response2-10 35 2.2.2.6.1 Successful Operation.2-10 36 2.2.2.6.1.1 SRNC Transfer to ANRI in the current Route Set 2-10 37 TIA-1134-1 iii
30、2.2.2.6.1.2 SRNC Transfer to outside the current Route Set.2-11 1 2.2.2.6.2 Failure Operation.2-12 2 2.2.2.7 IAS-Session Release .2-13 3 2.2.2.7.1 Successful Operation.2-14 4 2.2.2.7.1.1 Session Release for AT in Connected State 2-14 5 2.2.2.7.1.2 Session Release for AT in Idle State .2-14 6 2.2.2.7
31、.2 Failure Operation.2-14 7 2.2.2.8 IAS-Session Release Ack2-14 8 2.2.2.8.1 Successful Operation.2-14 9 2.2.2.8.2 Failure Operation.2-15 10 2.2.2.9 IAS-UATI Update .2-15 11 2.2.2.9.1 Successful Operation.2-15 12 2.2.2.9.1.1 UATI Change Operation .2-15 13 2.2.2.9.1.2 Route Set Add Operation 2-15 14 2
32、.2.2.9.2 Failure Operation.2-16 15 2.2.2.10 IAS-UATI Update Ack .2-16 16 2.2.2.10.1 Successful Operation.2-16 17 2.2.2.10.2 Failure Operation.2-16 18 2.2.2.11 IAS-Paging Request 2-17 19 2.2.2.11.1 Successful Operation.2-17 20 2.2.2.11.2 Failure Operation.2-17 21 2.2.2.12 IAS-Paging Request Ack.2-17
33、22 2.2.2.12.1 Successful Operation.2-17 23 2.2.2.12.2 Failure Operation.2-18 24 2.2.2.13 IAS-Page .2-18 25 2.2.2.13.1 Successful Operation.2-18 26 2.2.2.13.2 Failure Operation.2-18 27 2.2.2.14 IAS-Page Ack2-19 28 2.2.2.14.1 Successful Operation.2-19 29 2.2.2.14.2 Failure Operation.2-19 30 2.2.2.15 I
34、AS-Neighbor Discovery Request.2-19 31 2.2.2.15.1 Successful Operation.2-19 32 2.2.2.15.2 Failure Operation.2-20 33 2.2.2.16 IAS-Neighbor Discovery Report.2-20 34 2.2.2.16.1 Successful Operation.2-20 35 2.2.2.16.2 Failure Operation.2-20 36 2.2.2.17 IAS-Neighbor Discovery Report Ack .2-21 37 TIA-1134-
35、1 iv 2.2.2.17.1 Successful Operation.2-21 1 2.2.2.17.2 Failure Operation.2-21 2 2.2.2.18 IAS-Reject.2-21 3 2.2.2.18.1 Successful Operation.2-21 4 2.2.2.18.2 Failure Operation.2-21 5 2.2.3 IAS Interface Protocol Procedures2-21 6 2.2.3.1 Procedure for Maintaining the Access Counter.2-21 7 2.2.3.2 Proc
36、edure for Including Derived MSK Parameter SSIR in the Session State 8 Information Record IE.2-22 9 2.2.3.3 Procedure for Determining whether the Derived MSK is Valid .2-22 10 2.2.3.4 Procedure for Maintaining the Route Counter 2-23 11 2.2.3.5 Procedure for Maintaining the Session Signature .2-23 12
37、2.2.3.6 Exclusive Control of Session State Information Record.2-24 13 2.2.3.6.1 Unlock State 2-24 14 2.2.3.6.2 Lock State2-24 15 2.2.3.7 Procedure for Inclusion of RADIUS Attributes 2-25 16 2.3 IPT (IP Tunneling) Interface.2-25 17 2.3.1 IPT Interface Network/Transport Protocol Specification .2-25 18
38、 2.3.2 IPT data L2TPv3 Headers.2-26 19 2.3.3 IPT Interface Network/Transport Protocol Procedure 2-27 20 2.3.3.1 IPT Packet Tunneling Operations .2-27 21 2.3.3.1.1 GRE packet is Received from the AGW while the AT is active.2-27 22 2.3.3.1.2 Forward-link IPT Packet is Received while the AT is active2-
39、28 23 2.3.3.1.3 Forward-link Packet is Received either through GRE or IPT while the AT is Idle 2-29 24 2.3.3.1.4 Reverse-link IP Packet is Received.2-29 25 2.3.3.1.5 Reverse-link IPT Packet is Received 2-29 26 2.3.4 IPT Interface Protocol Procedure2-30 27 2.3.4.1 Procedure for Maintaining DAP Counte
40、r2-30 28 2.3.5 IPT Interface Message Procedures2-30 29 2.3.5.1 IPT-Notification 2-31 30 2.3.5.1.1 Successful Operation.2-31 31 2.3.5.1.1.1 FLSE Switch Operation - Target FLSE Procedure .2-31 32 2.3.5.1.1.2 FLSE Switch Operation - Source FLSE Procedure.2-31 33 2.3.5.1.1.3 FLSE Switch Operation - DAP
41、Procedure 2-32 34 2.3.5.1.1.4 RLSE Switch Operation - Target RLSE Procedure 2-32 35 2.3.5.1.1.5 RLSE Switch Operation - Source RLSE Procedure2-32 36 2.3.5.1.1.6 DAP Switch Operation2-32 37 TIA-1134-1 v 2.3.5.1.1.7 Connection Close Operation .2-33 1 2.3.5.1.1.8 Connection Lost Operation .2-33 2 2.3.5
42、.1.1.9 Route Set Add Operation 2-34 3 2.3.5.1.1.10 Route Set Remove Operation2-34 4 2.3.5.1.1.11 Packet Data Session Release .2-34 5 2.3.5.1.2 Failure Operation.2-35 6 2.3.5.2 IPT-Notification Ack.2-35 7 2.3.5.2.1 Successful Operation.2-35 8 2.3.5.2.1.1 FLSE Switch Operation - Source FLSE Procedure.
43、2-35 9 2.3.5.2.1.2 FLSE Switch Operation - Target FLSE Procedure .2-36 10 2.3.5.2.1.3 RLSE Switch Operation - Source RLSE Procedure2-36 11 2.3.5.2.1.4 RLSE Switch Operation - Target RLSE Procedure 2-36 12 2.3.5.2.1.5 DAP Switch Operation - FLSE Procedure 2-36 13 2.3.5.2.1.6 DAP Switch Operation - DA
44、P Procedure .2-37 14 2.3.5.2.2 Failure Operation.2-37 15 2.3.5.3 IPT-Flush.2-37 16 2.3.5.3.1 Successful Operation.2-37 17 2.3.5.3.1.1 FLSE Switch Operation - Source FLSE Procedure.2-37 18 2.3.5.3.1.2 FLSE Switch Operation - Target FLSE Procedure .2-37 19 2.3.5.3.1.3 RLSE Switch Operation - Source RL
45、SE Procedure2-37 20 2.3.5.3.1.4 RLSE Switch Operation - Target RLSE Procedure 2-37 21 2.3.5.3.2 Failure Operation.2-37 22 2.3.5.4 IPT-Reject .2-38 23 2.3.5.4.1 Successful Operation.2-38 24 2.3.5.4.2 Failure Operation.2-38 25 2.4 LLT (Link-Layer Tunneling) Interface.2-38 26 2.4.1 LLT Interface Networ
46、k/Transport Protocol Specification2-38 27 2.4.2 LLT Interface Network/Transport Protocol Procedure.2-41 28 2.4.2.1 LLT Packet Tunneling Operations 2-41 29 2.4.2.1.1 An ANRI Generates a Unicast Link-layer Packet.2-41 30 2.4.2.1.2 An ANRI Receives a Unicast Forward-link LLT Packet2-42 31 2.4.2.1.3 An
47、ANRI Receives a Reverse-link LLT Packet2-42 32 2.4.2.1.4 An RLSE Receives a Tunneled Link-layer Packet Over the Air for Another Route2-43 33 2.4.2.1.5 An eBS Needs to Tunnel a Broadcast Message through Another eBS .2-44 34 2.5 PMIP (Proxy Mobile IP) Interface2-44 35 2.5.1 PMIP Signaling Interface2-4
48、5 36 2.5.1.1 PMIP Signaling Interface Network/Transport Protocol Specification 2-45 37 TIA-1134-1 vi 2.5.1.2 PMIP Tunnel Establishment2-45 1 2.5.1.2.1 Initial PMIP Tunnel Setup with the AGW 2-46 2 2.5.1.2.1.1 Successful Operation.2-46 3 2.5.1.2.1.2 Failure Operation.2-47 4 2.5.1.2.2 eBS Added to the
49、 Route Set2-48 5 2.5.1.2.2.1 Successful Operation.2-48 6 2.5.1.2.2.2 Failure Operation.2-48 7 2.5.1.2.3 eBS Becomes the DAP2-49 8 2.5.1.3 PMIP Signaling-Only Binding 2-49 9 2.5.1.3.1 PMIP Signaling-Only Binding Establishment Procedures2-49 10 2.5.1.3.2 PMIP Signaling-Only Binding Configuration.2-49 11 2.5.1.3.3 AGW Sends Data Notification to SRNC or eBS.2-49 12 2.5.1.3.3.1 Successful Operation.2-49 13 2.5.1.3.3.2 Failure Operation.2-50 14 2.5.1.4 PMIP Registration Refresh2-50 15 2.5.1.4.1 PMIP Registration Refresh Procedures.2-50 16 2.5.1.4.1.1 Successful Operation.2-50 17 2.5.1.4.1.2 Fail
