This document specifies standards for transport protocols and signaling protocols used to establish transport bearers over the UTRAN Iu interface. It defines the protocol stacks for both the circuit switched and packet switched domains, including the use of ATM, AAL2, IP, UDP, GTP and various signaling protocols. The document also covers areas like addressing, quality of service, and congestion control.
In this presentation file, High level structure of the LTE/SAE system is presented. Main resource for the presentation is chapter 2 of Christopher Cox-An Introduction to LTE_ LTE, LTE-Advanced, SAE, VoLTE and 4G Mobile Communications-Wiley (2014).
This presentation covers:
How evolution has happened from First Generation Mobile Communication Systems to present day 3G/UMTS/WCMDA systems
Brief introduction of each Generation: GSM - 2G, 2.5 G - GPRS, 2.75G - EDGE, 3G and then LTE/4G
In this presentation file, High level structure of the LTE/SAE system is presented. Main resource for the presentation is chapter 2 of Christopher Cox-An Introduction to LTE_ LTE, LTE-Advanced, SAE, VoLTE and 4G Mobile Communications-Wiley (2014).
This presentation covers:
How evolution has happened from First Generation Mobile Communication Systems to present day 3G/UMTS/WCMDA systems
Brief introduction of each Generation: GSM - 2G, 2.5 G - GPRS, 2.75G - EDGE, 3G and then LTE/4G
Top 5 Social Media Networks. 5 Best Practices.RezStream
They like me, they really like me! Over the past 10 years, “like” is a term that marketers have been paying attention to, but are your social media followers liking what you’re sharing? Through this webinar, Stephanie will cover the top five networks for the hospitality industry and best practices to engage your fan base.
You have a wonderful property, exceptional service and guest relations, but somehow you’re not seeing online bookings. Join RezStream’s VP of Business Development, Josh, as he shows you what’s stopping your guest from booking and how to resolve these issues to see direct bookings in the future.
Giract has been researching the global savory ingredients and value added intermediates markets since 1990 and has produced many ground breaking studies in Europe, North and South America and Asia. Giract has published its latest study covering these key ingredients.
When you look out into your lobby, we bet a lot of people are looking down at their smartphones or tablets. We live in a world where internet access is at our fingertips wherever we go and making sure that your website performs well on all different types of devices is becoming standard. Don’t fall behind the times with a website that isn’t responsive! Lyles shares the benefits and importance of a responsive website design and how it helps with your conversions compared to other mobile options.
Giract has been researching the global savory ingredients and value added intermediates markets since 1990 and has produced many ground breaking studies in Europe, North and South America and Asia. It has now prepared a review of the key added-value savory intermediates across the world.
Products examined are process flavors (keys and finished flavorings), meat/soup seasonings and snack seasonings.
In the age of responsive websites and savvy web users, RezStream shares the advantages and benefits of using a Content Management System (CMS) to publish and edit your website. Be in control of your website's content even if you don't understand website design and coding.
We all know showing up in a search engine’s results page is extremely important, but are you taking advantage of all the different ways to show up in those results? We talk a lot about SEO but in this webinar, Liz will share five beneficial Pay Per Click (PPC) features and how you can target specific audiences with Google AdWords to get the visitors you want! Learn about the keyword bidding process, how PPC gives your site instant exposure in search results, and how you can test different sets of advertisements.
81% of travelers abandon their online booking but there is an opportunity to influence them to complete their reservation. In this webinar, learn what remarketing is and how it can be successful in driving visitors back into your booking engine.
RezStream Webinar: The mobile revolution - recap & trendsRezStream
More travelers are booking with mobile devices and smartphones and your website and marketing efforts need to be tailored for this specific audience. See how the trend grew and how you can prepare for the future.
3GPP TR 22.885 study on LTE support for V2X servicesYi-Hsueh Tsai
The vehicular communication in this study, referred to as Vehicle-to-Everything (V2X), contains the following three different types:
- Vehicle to Vehicle (V2V) Communications
- Vehicle to Infrastructure (V2I) Communications
- Vehicle to Pedestrian (V2P) Communications
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2 (Release 8)
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Connector Corner: Automate dynamic content and events by pushing a button
25414 3d0
1. 3GPP TS 25.414 V3.13.0 (2003-03)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
UTRAN Iu interface data transport and transport signalling
(Release 1999)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
3. Release 1999
3
3GPP TS 25.414 V3.13.0 (2003-03)
Contents
Foreword ............................................................................................................................................................4
1
Scope........................................................................................................................................................5
2
References................................................................................................................................................5
3
Definitions and abbreviations ..................................................................................................................6
3.1
3.2
Definitions ............................................................................................................................................................... 6
Abbreviations .......................................................................................................................................................... 6
4
ATM Layer ..............................................................................................................................................6
4.1
General .................................................................................................................................................................... 6
5
Circuit switched domain ..........................................................................................................................7
5.1
Transport network user plane .................................................................................................................................. 7
5.1.1
General............................................................................................................................................................... 7
5.1.2
ATM Adaptation Layer 2................................................................................................................................... 7
5.1.2.1
AAL2-Segmentation and Reassembly Service Specific Convergence Sublayer (I.366.1) ................................. 7
5.1.2.2
AAL2-specification (I.363.2)............................................................................................................................. 7
5.2
Transport network control plane.............................................................................................................................. 7
5.2.1
General............................................................................................................................................................... 7
5.2.2
Signalling protocol (ALCAP) ............................................................................................................................ 8
5.2.2.1
AAL2 Signalling Protocol (Q.2630.1) ............................................................................................................... 8
5.2.3
Signalling transport converter ............................................................................................................................ 8
5.2.3.1
AAL2 MTP3B Signalling Transport Converter (Q.2150.1) .............................................................................. 8
5.2.4
MTP3b (Q.2210) ............................................................................................................................................... 8
5.2.5
SSCF-NNI (Q.2140) .......................................................................................................................................... 8
5.2.6
SSCOP (Q.2110) ............................................................................................................................................... 8
5.2.7
ATM Adaptation Layer Type 5 (I.363.5) .......................................................................................................... 8
6
Packet switched domain...........................................................................................................................8
6.1
Transport network user plane .................................................................................................................................. 8
6.1.1
General............................................................................................................................................................... 8
6.1.2
GTP-U ............................................................................................................................................................... 9
6.1.3
UDP /IP ............................................................................................................................................................. 9
6.1.4
ATM Adaptation Layer Type 5 (I.363.5) .......................................................................................................... 9
6.1.5
IP/ATM.............................................................................................................................................................. 9
6.2
Transport network control plane............................................................................................................................ 10
7
Broadcast Domain..................................................................................................................................10
7.1
Transport network user plane ................................................................................................................................ 10
7.1.1
General............................................................................................................................................................. 10
7.1.2
TCP/IP ............................................................................................................................................................. 10
7.1.3
ATM Adaptation Layer Type 5 (I.363.5) ........................................................................................................ 10
7.1.4
IP/ATM............................................................................................................................................................ 10
7.2
Transport network control plane............................................................................................................................ 11
Annex A (informative):
Change history ...............................................................................................12
3GPP
4. Release 1999
4
3GPP TS 25.414 V3.13.0 (2003-03)
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
5. Release 1999
1
5
3GPP TS 25.414 V3.13.0 (2003-03)
Scope
The present document specifies the standards for user data transport protocols and related signalling protocols to
establish user plane transport bearers over the UTRAN Iu interface.
2
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1]
ITU-T Recommendation I.361 (11/95): "B-ISDN ATM layer specification".
[2]
ITU-T Recommendation I.363.2 (9/97): "B-ISDN ATM adaptation layer specification: Type 2
AAL".
[3]
ITU-T Recommendation I.363.5 (8/96): "B-ISDN ATM adaptation layer specification: Type 5
AAL".
[4]
ITU-T Recommendation I.366.1 (6/98): "Segmentation and Reassembly Service Specific
Convergence Sublayer for the AAL Type 2".
[5]
ITU-T Recommendation E.164 (5/97): "The international public telecommunication numbering
plan".
[6]
ITU-T Recommendation Q.2110 (7/94): "B-ISDN ATM adaptation layer - Service Specific
Connection Oriented Protocol (SSCOP)".
[7]
ITU-T Recommendation Q.2140 (2/95): "B-ISDN ATM adaptation layer - Service Specific
Coordination Function for Support of Signalling at the Network Node Interface (SSCF-NNI)".
[8]
ITU-T Recommendation Q.2150.1 (12/99): "AAL type 2 signalling transport converter on
broadband MTP".
[9]
ITU-T Recommendation Q.2210 (7/96): "Message transfer part level 3 functions and messages
using the services of ITU-T Recommendation Q.2140".
[10]
ITU-T Recommendation Q.2630.1 (12/99): "AAL type 2 signalling protocol (Capability Set 1)".
[11]
ITU-T Recommendation X.213 (11/95): "Information technology - Open systems interconnection Network Service Definition".
[12]
IETF RFC 768 (August 1980): "User Datagram Protocol".
[13]
IETF RFC 791 (September 1981): "Internet Protocol".
[14]
IETF RFC 2684 (September 1999): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
[15]
IETF RFC 2225 (April 1998): "Classical IP and ARP over ATM".
[16]
IETF RFC 2460 (December 1998): "Internet Protocol, Version 6 (IPv6) Specification".
[17]
3GPP TS 29.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
3GPP
6. Release 1999
6
3GPP TS 25.414 V3.13.0 (2003-03)
[18]
IETF RFC 793 (September 1981): "Transmission Control Protocol".
[19]
IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS Field) in
the Ipv4 and Ipv6 Headers".
[20]
ITU-T Implementor's guide (12/99) for recommendation Q.2210 (07/96).
[21]
ITU-T Recommendation E.191 (03/00): "B-ISDN addressing".
3
Definitions and abbreviations
3.1
Definitions
For the purposes of the present document, the following terms and definitions apply:
Access Link Control Application Part (ALCAP): generic name for the transport signalling protocols used to set-up
and teardown transport bearers
3.2
Abbreviations
For the purposes of the present document, the following abbreviations apply:
AAL
AESA
ALCAP
ARP
ATM
CN
GTP
IP
LIS
MTP3b
NSAP
PDU
RFC
RNC
SA
SABP
SABS
SAR
SCSF-NNI
SSCOP
SSCS
TCP
UDP
VC
ATM Adaptation Layer
ATM End System Address
Access Link Control Application Part
Address Resolution Protocol
Asynchronous Transfer Mode
Core Network
GPRS Tunnelling Protocol
Internet Protocol
Logical IP Subnet
Message Transfer Part level 3 for Q.2140
Network Service Access Point
Protocol Data Unit
Request For Comment
Radio Network Controller
Service Area
Service Area Broadcast Protocol
Service Area Broadcast Service
Segmentation and Reassembly
Service Specific Coordination Function-Network Node Interface
Service Specific Connection Oriented Protocol
Service Specific Convergence Sublayer
Transmission Control Protocol
User Datagram Protocol
Virtual Circuit
4
ATM Layer
4.1
General
ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T
Recommendation I.361 [1]. The structure of the cell header used in the UTRAN Iu interface is the cell header format
and encoding at NNI (see figure 3/I.361).
3GPP
7. Release 1999
7
5
Circuit switched domain
5.1
Transport network user plane
5.1.1
3GPP TS 25.414 V3.13.0 (2003-03)
General
Figure 1 shows the protocol stack for the transport network user plane on the Iu interface towards the circuit switched
domain.
AAL-2 SAR SSCS (I.366.1)
AAL2 (I.363.2)
ATM
Figure 1
5.1.2
5.1.2.1
ATM Adaptation Layer 2
AAL2-Segmentation and Reassembly Service Specific Convergence
Sublayer (I.366.1)
Service Specific Segmentation and Reassembly (SSSAR) sublayer of ITU-T Recommendation I.366.1 [4] is used for the
segmentation and reassembly of AAL2 SDUs (i.e., only SSSAR is used from I.366.1).
5.1.2.2
AAL2-specification (I.363.2)
AAL2 shall be used according to ITU-T Recommendation I.363.2 [2].
5.2
Transport network control plane
5.2.1
General
Figure 2 shows the protocol stack for the transport network control plane on the Iu interface towards the circuit switched
domain.
AAL2 connection signalling
(Q.2630.1)
AAL2 Signalling Transport
Converter for MTP3b (Q.2150.1)
MTP3b
SSCF-NNI
SSCOP
AAL5
ATM
Figure 2
3GPP
8. Release 1999
5.2.2
5.2.2.1
8
3GPP TS 25.414 V3.13.0 (2003-03)
Signalling protocol (ALCAP)
AAL2 Signalling Protocol (Q.2630.1)
ITU-T Recommendation Q.2630.1 [10] shall be used for establishing AAL2 connections towards the circuit switched
domain.
The AAL2 transport layer uses the embedded E.164 or other AESA variants of the NSAP addressing formats [11, 21].
Native E.164 [5] addressing shall not be used.
Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH request primitive
of ITU-T Recommendation Q.2630.1 [10].
If there is an AAL2 switching function in the transport network layer of the interface, the AAL2 Link Characteristics
parameter (ALC) shall be included in the Establish Request message of AAL2 signalling protocol.
5.2.3
5.2.3.1
Signalling transport converter
AAL2 MTP3B Signalling Transport Converter (Q.2150.1)
The AAL2 MTP3b Signalling Transport Converter shall be used according to ITU-T Recommendation Q.2150.1 [8].
5.2.4
MTP3b (Q.2210)
MTP3b shall be used according to ITU-T Recommendation Q.2210 [9 and 20].
5.2.5
SSCF-NNI (Q.2140)
SSCF-NNI shall be used according to ITU-T Recommendation Q.2140 [7].
5.2.6
SSCOP (Q.2110)
SSCOP shall be used according to ITU-T Recommendation Q.2110 [6].
5.2.7
ATM Adaptation Layer Type 5 (I.363.5)
AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
6
Packet switched domain
6.1
Transport network user plane
6.1.1
General
Figure 3 shows the protocol stack for the transport network user plane on the Iu interface towards the packet switched
domain.
3GPP
9. Release 1999
9
3GPP TS 25.414 V3.13.0 (2003-03)
GTP-U
UDP
IP
AAL5
ATM
Figure 3
The protocol architecture for the User Plane of the Iu interface towards the packet switched domain shall be GTP-U [17]
over UDP over IP over AAL5 over ATM. One or several AAL5/ATM permanent VC's may be used as the common
layer 2 resources between the UTRAN and the packet switched domain of the CN.
One switched VC may be used per user flow. The standardisation of the procedures and protocols for use of Switched
VC is outside the scope of 3GPP.
Congestion control shall be performed over the Iu user plane toward the packet switched domain using buffer
management and no flow control.
6.1.2
GTP-U
The GTP-U [17] protocol shall be used over the Iu interface toward the packet switched domain.
6.1.3
UDP /IP
The path protocol used shall be UDP [12], which is specified in RFC 768.
The UDP port number for GTP-U shall be as defined in [17].
IPv4 [13] (RFC 791) shall be supported, IPv6 [16] (RFC 2460) support is optional.
There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall
send downstream packets of a given RAB to the RNC IP address (received in RANAP) associated to that particular
RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address
(received in RANAP) associated to that particular RAB.
6.1.4
ATM Adaptation Layer Type 5 (I.363.5)
AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the packet switched
domain. Multiple VCs may be used over the interface. An association shall be made between a VC and the IP addresses
that are related to this VC in the peer node side. This association shall be made using O&M or using "ATM Inverse
ARP" when PVCs are used.
When PVCs are used, quality of service differentiation shall only be performed at the IP layer using differentiated
services [19].
6.1.5
IP/ATM
When the association mentioned in 6.1.4 is made using 0&M, the "LLC encapsulation" option of "Multiprotocol
Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
When the association mentioned in 6.1.4 is made using "ATM Inverse ARP", "Classical IP and ARP over ATM"
protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP
packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in RFC
2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in RFC 2684 [14].
3GPP
10. Release 1999
10
3GPP TS 25.414 V3.13.0 (2003-03)
"Classical IP and ARP over ATM" allows routers to be members of one or more LISs. The CN side of the Iu interface
shall provide IP routing functionalities. The RNC side of the Iu interface may provide routing functionalities. If the RNC
side of the Iu interface does not provide routing functionalities, the RNC routing tables shall include default route
entries.
6.2
Transport network control plane
ALCAP is not required over the Iu interface towards the packet switched domain.
7
Broadcast Domain
7.1
Transport network user plane
7.1.1
General
Figure 4 shows the protocol stack for the transport network user plane on the Iu interface towards the Broadcast domain.
TCP
IP
AAL5
ATM
Figure 4
The protocol architecture for the Service Area Broadcast Plane of the Iu interface shall be TCP over IP over AAL5 over
ATM.
7.1.2
TCP/IP
The path protocol used shall be TCP, which is specified in RFC793 [18]. IPv4 [13] (RFC 791) shall be supported, IPv6
[16] (RFC 2460) support is optional.
The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.
The 3452 destination port number shall be used by both entities (RNC or CN) whenever it sets up a new TCP
connection. When it sends SABP messages on an existing TCP connection, the sending entity (RNC or CN) shall use as
TCP destination port number either 3452 if it was the initiator of this TCP connection, or the TCP source port number
that was received from the peer entity that had initiated this existing TCP connection.
7.1.3
ATM Adaptation Layer Type 5 (I.363.5)
AAL5 shall be used according to ITU-T Recommendation I.363.5.
AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the broadcast domain.
Multiple VCs may be used over the interface. An association shall be made between a VC and the IP addresses that are
related to this VC in the peer node side. This association shall be made using O&M or using ATM Inverse ARP
according to Classical IP over ATM when PVCs are used.
7.1.4
IP/ATM
When the association mentioned in 7.1.3 is made using O&M, the "LLC encapsulation" option of "Multiprotocol
Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
3GPP
11. Release 1999
11
3GPP TS 25.414 V3.13.0 (2003-03)
When the association mentioned in 7.1.3 is made using "ATM Inverse ARP", "Classical IP and ARP over ATM"
protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP
packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in RFC
2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in RFC 2684 [14].
7.2
Transport network control plane
ALCAP is not required over the Iu interface towards the broadcast domain.
3GPP
12. Release 1999
12
3GPP TS 25.414 V3.13.0 (2003-03)
Annex A (informative):
Change history
TSG RAN#
Version
RAN_04
-
-
-
RAN_05
RAN_06
RAN_07
RAN_08
RAN_09
3.0.0
3.1.0
3.2.0
3.3.0
3.4.0
RP-99747
RP-000237
RP-000375
RAN_10
RAN_11
3.5.0
3.6.0
RP-000614
RP-010112
3.6.0
3.7.0
Approved at TSG RAN #10
Approved at TSG RAN #11
RAN 13
RAN 14
RAN 15
RAN 16
RAN 16
RAN18
RAN19
3.7.0
3.8.0
3.9.0
3.10.0
3.10.0
3.11.0
3.12.0
001
018
020
022
023
024
021
028
031
033
036r1
041
053
Change history
New
Subject/Comment
Version
3.0.0
Approved at TSG RAN #4 by correspondence and placed
under Change Control
3.1.0
Approved at TSG RAN #5
3.2.0
Approved at TSG RAN #6
3.3.0
Approved at TSG RAN #7
3.4.0
Approved at TSG RAN #8
3.5.0
Approved at TSG RAN #9
RP-010580
RP-010850
RP-020165
RP-020402
RP-020402
RP-020742
RP-030054
3.8.0
3.9.0
3.10.0
3.11.0
3.11.0
3.12.0
3.13.0
Reference corrections
Reference corrections
AAL5 used to transport IP packet for Broadcast Domain
Correction of Aesa formats
Inclusion of TCP Port Number for SABP
Correction to Iu-ps IP/ATM
TCP Port number
CR
Tdoc RAN
3GPP