ETSI TR 125 933-2003 Universal Mobile Telecommunications System (UMTS) IP transport in UTRAN《全球移动通信系统(UMTS) UTRAN中的IP传输(3GPP TR 25 933 版本5 3 0 第5次发布)》.pdf

《ETSI TR 125 933-2003 Universal Mobile Telecommunications System (UMTS) IP transport in UTRAN《全球移动通信系统(UMTS) UTRAN中的IP传输(3GPP TR 25 933 版本5 3 0 第5次发布)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 125 933-2003 Universal Mobile Telecommunications System (UMTS) IP transport in UTRAN《全球移动通信系统(UMTS) UTRAN中的IP传输(3GPP TR 25 933 版本5 3 0 第5次发布)》.pdf（139页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 125 933 V5.4.0 (2003-12)Technical Report Universal Mobile Telecommunications System (UMTS);IP transport in UTRAN(3GPP TR 25.933 version 5.4.0 Release 5)ETSI ETSI TR 125 933 V5.4.0 (2003-12) 1 3GPP TR 25.933 version 5.4.0 Release 5 Reference RTR/TSGR-0325933v540 Keywords UMTS ETSI 650 Route

2、des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded fr

3、om: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall b

4、e the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available

5、 at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media

6、. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Tr

7、ade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 125 933 V5.4.0 (2003-12) 2 3GPP TR 25.933 version 5.4.0 Release 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ET

8、SI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is availa

9、ble from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced

10、 in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or r

11、eports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TR 125

12、 933 V5.4.0 (2003-12) 3 3GPP TR 25.933 version 5.4.0 Release 5 Contents Intellectual Property Rights2 Foreword.2 Foreword.10 1 Scope 11 2 References 11 3 Definitions, symbols and abbreviations .14 3.1 Definitions14 3.2 Symbols14 3.3 Abbreviations .14 4 Introduction 15 4.1 Task Description 15 4.2 Rat

13、ionale for IP Transport15 5 Requirements16 5.1 General requirements .16 5.2 Independence to Radio Network Layer 16 5.3 Services required by the upper layers of user planes of Iu .16 5.4 Services required by the upper layers of user planes of Iur and Iub.17 5.5 Coexistence of the two transport option

14、s .17 5.6 Quality of Service.17 5.7 Efficient utilization of transport resources .18 5.8 Layer 2/Layer 1 independence .18 5.9 Transport Bearer Identification 18 5.10 Transport Network Architecture and Routing 18 5.10.1 Network elements .18 5.11 Radio Network Signalling Bearer.18 6 Study Areas 19 6.1

15、 External standardization .19 6.2 User plane proposed solutions19 6.2.1 CIP solution 19 6.2.1.1 CIP Container19 6.2.1.2 CIP Packets .19 6.2.1.2.1 Segmentation and Re-assembly.19 6.2.1.2.2 CIP Packet Header Format 20 6.2.1.2.3 The CIP Packet Header Fields in Detail. .20 6.2.1.2.4 Discussion of the CI

16、P Packet Header Field Sizes21 6.2.2 LIPE solution21 6.2.2.1 Details of Multiplexed Header 22 6.2.2.2 Basic Header .22 6.2.2.3 Extensions .22 6.2.3 PPP-MUX based solution .23 6.2.3.1 PPP Multiplexed Frame Option Over HDLC23 6.2.3.2 PPP Multiplexed Frame Option Over ATM/AAL5 24 6.2.3.3 PPP Multiplexed

17、 Frame Option Over L2TP Tunnel (TCRTP) .25 6.2.4 MPLS solution26 6.2.4.1 MPLS General Description .26 6.2.4.2 Routing with MPLS 26 6.2.4.3 Support for QoS requirements.27 6.2.4.4 Efficient, QoS-enabled transmission over routed domains with MPLS27 6.2.4.5 Efficient transmission over narrowband (point

18、-to-point) links with MPLS29 6.2.4.5.1 MPLS Header Compression “Session Negotiation“ 29 6.2.4.5.1.1 Using RSVP-TE to negotiate “MPLS Simple Header Compression“30 6.2.4.5.1.2 Using LDP signalling for “MPLS Simple Header Compression“ session negotiation 30 ETSI ETSI TR 125 933 V5.4.0 (2003-12) 4 3GPP

19、TR 25.933 version 5.4.0 Release 5 6.2.4.5.2 Handling of large packets over narrowband links .30 6.2.5 AAL2 based solution 31 6.2.6 Usage of UDP Lite for IP UTRAN.31 6.2.6.1 Background .31 6.2.6.2 UDP Lite .31 6.3 QoS.32 6.3.1 Fragmentation.32 6.3.1.1 General32 6.3.1.2 IP fragmentation33 6.3.1.3 Frag

20、mentation to facilitate delay sensitive traffic .33 6.3.1.4 Application level fragmentation33 6.3.1.5 Layer 2 fragmentation solution .34 6.3.2 Sequence information .34 6.3.3 Error detection 34 6.3.4 Flow Classification in IP Networks 34 6.3.4.1 Classification based on RNL information.34 6.3.4.2 Clas

21、sification based on TNL information .35 6.3.5 Classification Configuration .35 6.3.5.1 Transport bearer based classification 35 6.3.5.2 Packet per packet classification.35 6.3.6 UTRAN Hop-by-Hop QoS Approach.36 6.3.7 UTRAN End-to-End QoS Approach 36 6.4 Transport network bandwidth utilization .36 6.

22、4.1 General issues .37 6.4.1.1 Multiplexing37 6.4.1.1.1 Location of multiplexing in transport network37 6.4.1.1.1.1 Scenario 1: .37 6.4.1.1.1.2 Scenario 2: .38 6.4.1.1.1.3 Scenario 3: .38 6.4.1.2 Resource Management 39 6.4.1.3 Header Compression Techniques39 6.4.1.3.1 Technical evaluation39 6.4.1.3.

23、1.1 Use of Differential Coding.40 6.4.1.3.1.2 Comparison40 6.4.1.3.2 UTRAN Evaluation.40 6.4.1.3.3 Use of Negotiation.40 6.4.2 Solution Comparison data.40 6.5 User plane transport signalling.41 6.5.1 Solution without ALCAP41 6.5.1.1 Principle 41 6.5.1.2 Solution without using additional RNL Paramete

24、rs42 6.5.1.2.1 On Iub - Iur42 6.5.1.2.2 Inter-working on Iu43 6.5.1.3 Solution with higher flexibility and complexity using additional RNL parameters44 6.5.1.4 Provisioning and Dynamic Selection of the Transport Option44 6.5.1.4.1 On Iub44 6.5.1.4.2 Inter-working on Iu44 6.5.1.4.3 Interworking on Iu

25、r45 6.5.1.4.3.1 Provisioning of transport capabilities 45 6.5.1.4.3.2 Indicate dynamically in a signaling message the IP Transport Option Availability or ATM Preference 45 6.5.1.4.3.3 Benefits 45 6.5.1.4.3.4 Drawbacks .45 6.5.2 LIPE solution46 6.5.2.1 Alternative I Solution:.46 6.5.2.1.1 LIPE Signal

26、ling Channel.47 6.5.2.1.2 Tunnel Setup Procedure.47 6.5.2.1.3 Connection Set up Procedure 47 6.5.2.1.4 Tunnel tear down.47 6.5.2.1.5 Connection tear down48 6.5.2.2 Alternative II Solution: .48 6.6 Layer 1 and layer 2 independence 48 ETSI ETSI TR 125 933 V5.4.0 (2003-12) 5 3GPP TR 25.933 version 5.4.

27、0 Release 5 6.6.1 Options for L2 specification .48 6.6.1.1 General48 6.6.1.2 L2 not standardized.48 6.6.1.3 L2 standardized.49 6.7 Radio Network Signalling bearer .49 6.7.1 Iub RNL signalling bearer 49 6.7.1.1 SCTP characteristics .49 6.7.1.2 Proposal 149 6.7.1.3 Proposal 250 6.7.1.4 Use of SCTP50 6

28、.7.2 RNSAP Signalling 51 6.7.3 RANAP Signalling .51 6.7.4 PCAP signalling52 6.7.5 SCCP/M3UA versus SUA 52 6.7.6 Interworking of SCCP/M3UA and SUA 53 6.7.6.1 Interworking in native SS7 networks 53 6.7.6.2 Interworking in SS7 and SigTran Networks .54 6.7.6.3 Interworking in UTRAN .58 6.7.6.4 SCCP and

29、SUA interworking in detail59 6.7.6.4.1 Establishment of SUA connectivity.59 6.7.6.4.2 SEP Failover60 6.7.6.4.3 Successful ASP Failover scenario .60 6.7.6.4.4 Message mapping between SCCP and SUA61 6.7.6.5 Conclusions.62 6.7.7 Iub Signalling Bearer Comparison Data .62 6.7.7.1 Comparison TCP, UDP, SCT

30、P .62 6.7.7.1.1 User service .62 6.7.7.1.2 Reliability 62 6.7.7.1.3 Availability62 6.7.7.1.4 Defence/Security .63 6.7.7.1.5 Performance.63 6.7.7.1.6 RNL changes .64 6.7.7.1.7 Implementation Difficulty .64 6.7.7.1.8 Maturity.64 6.7.7.1.9 Interoperability 64 6.7.7.1.10 Operational aspects64 6.7.7.2 Su

31、mmary.65 6.7.8 Reference Architecture for ENUM based Services 65 6.7.8.1 Key requirements/assumptions of the mobility services using ENUM.65 6.7.8.2 Some definitions .66 6.7.8.3 System solution based on ENUM .67 6.7.8.4 Service discovery/IP address retrieval of end service nodes.67 6.8 Addressing69

32、6.8.1 General addressing requirements69 6.8.2 Bearer addressing solutions 70 6.8.2.1 Destination IP addresses and destination UDP ports as connection identifiers.70 6.9 IP transport and routing architecture aspects71 6.9.1 Flexibility of IP architectures71 6.9.2 Hosts and routers 71 6.9.3 IPv6 aspec

33、ts 73 6.9.3.1 Improved Performance73 6.9.3.2 Autoconfiguration .73 6.9.3.3 IPv6 to IPv4 interworking.73 6.9.3.3.1 Network Address/Port Translators-Protocol Translators (NAPT-PT).74 6.9.3.3.2 Stateless IP/ICMP Translation Algorithm (SIIT) 74 6.9.3.3.3 Dual stack74 6.9.3.4 Tunneling 76 6.9.3.5 Summary

34、.76 6.10 Backward compatibility with R99-R4/Coexistence with ATM nodes .77 6.10.1 General77 6.10.2 Interworking Options78 6.10.2.1 Dual Stack operation within Rel.5 RNCs78 ETSI ETSI TR 125 933 V5.4.0 (2003-12) 6 3GPP TR 25.933 version 5.4.0 Release 5 6.10.2.1.1 Interworking with PWE3-capable ATM Swi

35、tch .79 6.10.2.2 Transport Network Layer IWU.80 6.10.2.2.1 Issue on TNL IWU control protocol81 6.10.3 Conclusion 83 6.10.4 UTRAN Architecture considerations83 6.10.5 ATM/IP Interworking solution proposals.84 6.10.5.1 Bearer control proposal using IETF SIP/SDP.84 6.10.5.1.1 Description 85 6.10.5.1.2

36、Bearer control between IP and ATM nodes signalling examples85 6.10.5.1.3 Use of SIP for Interworking between UTRAN ATM interfaces and UTRAN IP interfaces.87 6.10.5.1.3.1 Description.87 6.10.5.1.3.1.1 Inter Working Problem Summary 87 6.10.5.1.3.1.2 Approach/Aims 87 6.10.5.1.3.1.3 Using SIP as a Trans

37、port Bearer Signalling Protocol.87 6.10.5.1.3.1.4 Implementation 87 6.10.5.1.3.1.4.1 ACK message.87 6.10.5.1.3.1.4.2 Communication of endpoint information and session identification89 6.10.5.1.3.1.4.2.1 SIP header fields.90 6.10.5.1.3.1.4.2.2 SDP parameters90 6.10.5.1.3.1.4.2.3 Example message .91 6

38、.10.5.2 Bearer Control proposal using a new protocol (Q.IP-ALCAP), optimised for concatenation with AAL Type 2 links .92 6.10.5.2.1 Overall Scenario for Q.IP-ALCAP 93 6.10.5.2.2 Protocol Stack for Q.IP-ALCAP95 6.10.5.2.3 Example: Connection Establishment on Iur 95 6.10.5.3 IP-ALCAP based on Q.2630.9

39、6 6.10.5.3.1 Benefits96 6.10.5.3.2 IP-specific information in Q.2630 in Served User Transport (SUT) parameter 97 6.10.5.3.2.1 Served User Transport parameter in Q.263097 6.10.5.3.2.2 Structure of information.98 6.10.5.4 Use of IETF RSVP for ATM/IP interworking 100 6.10.5.4.1 Working scenarios .100 6

40、.10.5.4.1.1 ATM UTRAN Node initiated RL Setup procedure .100 6.10.5.4.1.2 IP UTRAN Node initiated RL Setup procedure 102 6.10.5.4.1.3 RSVP considerations .103 6.10.5.5 Inter-working with a PWE3-Capable ATM Switch 103 6.10.6 Coexistence between Rel.5 and R99/R4 Iur Control Plane using SUA protocol105

41、 6.10.6.1 Connecting an Rel.5 RNC to a R99/R4 RNC105 6.11 Synchronization107 6.12 Security 107 6.12.1 Security Threats 107 6.12.2 Security Operation in IP networks107 6.12.2.1 IPSec architectures107 6.12.2.2 SCTP Security features .107 6.12.2.3 Firewalls and other systems 108 6.13 Iu-cs/Iu-ps harmon

42、ization.108 6.13.1 GTP-U for Iu user plane .108 6.13.1.1 Iu PS108 6.13.1.2 Iu CS .108 6.13.1.3 GTP header for the Iu-PS user plane.108 6.13.1.4 User plane header simplification considerations for the Iu-PS .109 6.13.1.5 Proposed GTP-U-like header scenario “A“ for real-time applications110 6.13.1.6 G

43、TP-U-like alternative header scenario “B“ for real-time applications 110 6.13.1.7 Comparison of the GTP-U header and the possible new scenarios “A“ and “B“ 111 6.13.1.8 Motivation for GTP-U.112 6.13.2 RTP for Iu-cs interface .112 6.13.2.1 Reasons for selecting an RTP/UDP/IP based Iu-cs User Data Tra

44、nsport stack 112 6.13.2.2 Motivation for not choosing the RTP alternative 113 6.13.2.2.1 General 113 6.13.2.2.2 Commonality with Nb interface 113 6.13.2.2.3 Special RTP capability 113 6.13.2.2.4 Bandwidth utilization 114 ETSI ETSI TR 125 933 V5.4.0 (2003-12) 7 3GPP TR 25.933 version 5.4.0 Release 5

45、7 Agreements and associated agreed contributions.114 7.1 External standardization .114 7.2 QoS differentiation.114 7.3 Transport network bandwidth utilization .115 7.3.1 Multiplexing .115 7.4 User plane transport signalling.115 7.5 Layer 1 and layer 2 independence 115 7.6 Radio Network Signalling be

46、arer .115 7.7 Addressing116 7.8 Transport architecture and routing aspects.116 7.9 Backward compatibility with R99-R4/Coexistence with ATM nodes .117 7.10 Synchronization118 7.11 Security 118 7.12 Iu-cs/Iu-ps harmonization.118 7.13 Iur/Iub User plane protocol stacks118 7.14 Iu-cs/Iu-ps user plane pr

47、otocol stacks 118 7.14.1 Iu-cs 118 7.14.2 Iu-ps 119 7.15 IP version issues .119 8 Specification Impact and associated Change Requests119 8.1 TS 25.401 .119 8.1.1 Impacts119 8.1.2 List of Change Requests .119 8.2 TS 25.410 .120 8.2.1 Impacts120 8.2.2 List of Change Requests .120 8.3 TS 25.411 .120 8.

48、3.1 Impacts120 8.3.2 List of Change Requests .120 8.4 TS 25.412 .120 8.4.1 Impacts120 8.4.2 List of Change Requests .120 8.5 TS 25.413 .120 8.5.1 Impacts120 8.5.2 List of Change Requests .120 8.6 TS 25.414 .120 8.6.1 Impacts120 8.6.2 List of Change Requests .120 8.7 TS 25.415 .121 8.7.1 Impacts121 8

49、.7.2 List of Change Requests .121 8.8 TS 25.420 .121 8.8.1 Impacts121 8.8.2 List of Change Requests .121 8.9 TS 25.422 .121 8.9.1 Impacts121 8.9.2 List of Change Requests .121 8.10 TS 25.423 .121 8.10.1 Impacts121 8.10.2 List of Change Requests .121 8.11 TS 25.424 .121 8.11.1 Impacts121 8.11.2 List of Change Requests .121 8.12 TS 25.426 .122 8.12.1 Impacts122 8.12.2 List of Change Requests .122 8.13 TS 25.430 .122 8.13.1 Impacts122 8.13.2 List of Change Requests .122 8.14 TS 25.432 .122 8.14.1 Impacts122 ETSI ETSI TR 125 933 V5.4.0 (2003-12) 8 3GPP TR 25.933 version 5.4.0