Professional Documents
Culture Documents
CDMA2000
1 Abstract
Universal Mobile Telecommunications Service (UMTS) and CDMA2000 have emerged as two of the full-fleged 3G wireless standards to support both the radio and network functions based on the IMT-2000 framework. This paper surveys the two architectures in terms of their radio access and core networks technologies.
2 Overview
UMTS and CDMA2000 standards are designed to deliver wireless services with better performance, greater costeffectiveness and significantly more content than the 2G counterpart. Besides offering traditional voice communication, 3G data capability offers Internet and Intranet services for multimedia application, high-speed business transaction and telemetry.
the success of GSM, and on the GSM operators existing investment in infrastructure. The first stage of service and network evolution is from todays GSM systems, through the implementation of GPRS, to commercial UMTS networks (see Figure 1). The UMTS core network can continue to use the current 2G network structure to process voice and packet data. The major introduction of UMTS are a new air interface1 operating at around 2GHz, and a packet-based network architecture which supports both voice and data services.
2.1 UMTS
UMTS is the European member of the IMT2000 family of third generation cellular mobile standards. The goal of UMTS is to enable networks that offer true global roaming and to support a wide range of voice, data and multimedia services. Data rates offered by UMTS are: vehicular - 144 kbit/s; pedestrian 384 kbit/s;in-building 2Mb/s. The new UMTS networks will build on
A UMTS network consists of three interacting domains (see Figure 2): User Equipment (UE), UMTS Terrestrial Radio Access Network (UTRAN), and Core Network (CN). The UE is a mobile that communicates with UTRAN via the air-interface. UTRAN provides the air interface access method for the UE. CN provides switching, routing, and transit for user traffic. It also stores databases and provides network management functions.
From the specification and standardization point of view, both UE and UTRAN consist of completely new
authentication algorithms, and supports subscription information for the ME. Figure 3 shows the Cu interface that allows the USIM to communicate with the ME .
USIM
Cu ME Figure 3: UE architecture
protocols, the design of which is based on the needs of the new W-CDMA radio technology. On the contrary, the definition of CN is adopted from GSM network. This gives the system with new radio technology a global base of known and rugged CN technology that accelerates and facilitates its introduction, and enables such competitive advantages as global roaming.
A UTRAN consists of two distincts elements: Node B and Radio Network Controller (RNC). The main functions of the UTRAN archtecture are to:
Share and reuse of voice and packet Share and reuse of GSM
infrastructure
3.2.1
Node B
radio terminal used for communicating over the Uu interface (air-interface). Module (USIM) is a smartcard that stores subscribers identity and encryption keys, performs
A Node B (logically corresponds to the GSM Base Station) converts data flow between the Iub and Uu interfaces. Its main duty is to perform the physical layer processing, e.g. modulation, coding, interleaving, rate adaptation, spreading, etc.
3.2.2
An RNC (logically corresponds to the GSM Base Station Controller) controls the radio resources in its domain. RNC is the service access point for all services UTRAN providing to the Core Network. It also terminates the Radio Resource Control Protocol (RRC) that defines the messages and procedures between UE and UTRAN. A UTRAN may consist of one or more Radio Network Sub-Systems (RNS). An RNS is a sub-network within UTRAN that consists of one RNC and one or more Node B. RNCs which belongs to different RNS can be connected to each other via the Iur interface. The logical function of an RNC is further divided into controlling, serving, and drift. The controlling RNC administers the Node B for load and congestion control. It also executes admission control and channel code allocation for new radio links to be established by the Node B.
The serving RNC is the RNC that terminates both the Iu and Iub links from the core network and user equipment respectively. It performs L2 (MAC layer) processing of data to/from the radio interface. Mobility management functions such as power control, handoff decision, etc are also handled by the serving RNC. Note that one UE connected to the UTRAN has one and only one SRNC. The drift RNC compliments the serving RNC by providing diversity when the UE is in the state of inter-RNC soft handoff (which requires two RNCs). During the handoff, the drift RNC does not perform L2 processing; rather it routes data transparently between the Iub and Iur interfaces.
Node B
RNC
Node B RNS
3.3.1
lub
lur
Node B
RNC
Node B RNS
An HLR is a database located in the users home system that stores the users service profile. A service profile is created when a new user subscribes to the system, and remained as long as the subscription is active. It consists of information such as user service type and roaming permission etc.
Network layer represents standard transport technology selected for UTRAN without any UTRAN-specific changes.
The vertical planes are further divided into control, user, transport network control, and transport network user planes. The control plane is used for all UMTS-specific control signalling. It includes the Application Protocol (RANAP in Iu, RNSAP in Iur, and NBAP in Iub), and the signalling bearer for transporting the Application Protocol messages. All information transmitted and received by the user such as a voice call or packet data are transported via the user plane. The Transport Network Control Plane is a plane that acts between the control plane and the user plane. It is used for all control signalling within the transport layer. It includes the ALCAP protocol to set up the transport bearers for the user plane. It also includes signalling bearer needed for the ALCAP. Noticed that the introduction of the transport network control plane makes it possible for the Application Protocol in the Radio Network Control Plane to be completely independent of the technology selected for the Data Bearer in the User Plane. Finally the Transport Network User Plane handles the data bearer and signalling bearer in the user plane.
Network-to-Network Interfaces (SAALNNI). SAAL-NNI is further divided into Service Specific Co-ordination Function (SSCF), Service Specific Connection Oriented Protocol (SSCOP) and ATM AAL-5 layers. SSCF and SSCOP are specifically designed for signalling transport in ATM networks while AAL-5 is used for segmenting data into ATM cells. The Transport Network Control Plane protocol stack consists of signalling protocol for setting up AAL2 connections (Q.2630.1 and Q.2150.1) running on top of the SS7 protocols similar to those aforementioned.
4.1.1 Iu-CS
UMTS physical layer is not specified in the standard. It can be any off-the-shelf transmission technologies such as SONET, STM-1, and E1. However, ATM is the transport mechanism to be used across all three planes of the Transport Network Layer.
4.1.2 Iu-PS
In the Transport Network User Plane, an alternative IP-based signalling bearer is specified. This signalling bearer consists of M3UA, Simple Control Transmmission Protocol (SCTP), and Internet Protocol (IP). The SCTP layer is specifically designed for signalling transport in the Internet.
The Radio Network Layer Control Plane protocol stack consists of RANAP running on top of broadband SS7 protocols. The Transport Network Layer User Plane counterpart uses Signalling Connection Control Part (SCCP), Message Transfer Part (MTP3-b), Signalling ATM Adaptation Layer for
Figure 7: Iu-PS interface protocol stack
In the Iu PS User Plane, multiple packet data flows are multiplexed onto one or several AAL5 Permanent Virtual
Circuits. The GPRS Tunnelling Protocol (GTP-U) is the multiplexing layer that provides identities for individual packet data flow. Each flow uses UDP connectionless transport and IP addressing. No protocols are required in the Transport Network Control Plane since establishing GTP tunnel requires only identifier for the tunnel, and the IP addresses for both directions are already included in the RANAP messages.
4.2.1 Iur-1
Iur-1 provides the basic functionality of RNSAP signalling needed for mobility of users between two RNCs, excluding exchange of any user data traffic. If this interface is not available, the only way for a user connected to one RNC to utilize a cell in another RNC is to disconnect itself from the first RNC. Other services provided by Iur-1 include support of SRNC relocation, inter-RNC registration area update, inter-RNC packet paging.
4.2.2 Iur-2
Iur-2 provides dedicated channel between two RNCs to support the interRNC soft handover and allow the anchoring of the SRNC during when the UE is utilizing the dedicated channels for as long as the user has an active connection to the circuit-switched domain. To achieve this, the user plane frame protocol for dedicated channels (DCH FP) is used to defines data frames to carry user data and control frames to exhange measurement information. User data frames are normally routed transparently between DRNC and SRNC. The Transport Network Control Plane Protocol uses Q.2630.1 to set up AAL2 connections. Each dedicated channel is conveyed over one transport connection, except the coordinated DCH used to obtain unequal error protection in the air interface.
Basic Inter-RNC mobility Dedicated Channel Traffic Common Channel Traffic Global Resource Management
For this reason, the Iur signalling protocol Radio Network System Application Part (RNSAP) is divided into four different modules: Iur-1 thru Iur-4
4.2.3 Iur-3
This functionality allows handling of common and shared channel data streams across the Iur interface. It requires the Common Transport Channel module of RNSAP and the Iur Common
Transport Channel Frame Protocol (CCH FP). The Q.2630.1 signalling protocol of the Transport Network Control Plane is needed if AAL2 connections are used.
4.2.4 Iur-4
Iur-4 provides signalling to support enhanced radio resource and O&M features across the Iur interface. It is implemented via the global module of RNSAP and does not require any User Plane Protocol, since there is no transmission of user data across the Iur interface.
In order to understand the above two protocols, the logical model of Node B must be first understood. Referring to Figure 10, a common signalling link exists between the RNC and the Node B. There is also a set of traffic termination point each controlled by a dedicated signalling link. One traffic termination point controls a number of mobiles having dedicated resources in the Node B, and the corresponding traffic is conveyed through dedicated data ports. Common data ports outside the traffic termination points are used to convey RACH, FACH, and PCH traffic. The User Plane Iub frame protocols define the structures of the frames and the basic in-band control procedures for every type of transport channel (ie. RACH, FACH, and PACH). Finally, Q.2630.2 signalling is used for dynamic management of the AAL2 connections used in the User Plane.
The Iub signalling interface is divided into two components: the common Node B Application Part (NBAP) that defines the signalling procedures across the common signalling link, and the dedicated NBAP that used in the dedicated signalling link.
The main function of Common NBAP is the setup of the first radio link of one UE, and selection of the traffic termination point. It also handles RACH, FACH, and PCH channels.
point for handling of this UE context, and every subsequent signalling related to this mobile is exchanged with dedicated NBAP procedures across the dedicated control port of the given Traffic Termination Point.
visited AAA server using the IP protocol within the IP network. The servers contacted by the PDSN or local AAA server may reside in other IP domains and be operated by other cellular operators.
provider network may be the users home access provider or, in roaming cases, the visited access provider network is used. Access mobility management is achieved using existing air interface procedures that include interactions with Visited Location Registers (VLR) and Home Location Registers (HLR). Information about access service parameters are maintained in the access service profile stored in the HLR and cached in the VLR while the mobile station is registered in the service provider access network. There is an open interface defined between the RN and the Packet Data Serving Node (PDSN) known as the R-P interface. The PDSN interacts with the local or
The Radio Network consists of two logical components: Packet Control Function (PCF) and Radio Resources Control (RRC). The primary function of the PCF is to establish, maintain, and terminate L2 connection to the PDSN. It also communicates with the RRC to request and manage radio resources in order to relay packets to and from the mobile station. During hard handoff to another RRC, the serving PCF forwards its information to the target PCF to reestablish packet data session to the PDSN. Finally PCF is responsible for collecting accounting information and forward them to the PDSN. RRC supports authentication and authorization of the mobile station for
radio access. It also supports air interface encryption to the mobile station.
The home network that provides IP based data services to the user.
PDSN. However, there is no IP address mobility beyong this PDSN. Mobile IP provides IP routing service to a public IP network and/or secure IP routing service to predefined private IP networks. The mobile user is able to use either a static IP address or dynamically assigned IP address belonging to its home IP network HA. Regardless of whether the mobile is assigned a static or dynamic IP address, it should have a static and persistent HA address to allow seamless handoff between RNs that are connected to separate PDSNs. Figure 12 and 13 illustrates a Simple IP and Mobile IP network respectively.
delivery of data. Assured means received data are acknowledged, loss and out-of-order data are selectively retransmitted, and duplicate data are discarded. Addressing sublayer presents only on the common channels. Its function is to assign and match sender and receiver mobile addresses of the following types: IMSI and ESN, ESN, IMSI, IMSI and ESN, TMSI. Utility sub-layer assembles and reasembles LAC PDU by adding message type, encryption, radio environment report, LAC padding and length, and arranging LAC PDU with L3 PDU. Finally, SAR sublayer converts PDU to bitstream (and vice versa), and adds message length and CRC.
6.2 Mobile IP
Mobile IP (MIP) introduces a framework of procedures, messages, and message formats that enables a mobile user to change handoff from one PDSN to another without requiring alteration of its IP address, which would otherwise disrupt L3 and higher operations. MS, PDSN and HA all support Mobile IP agent advertisement, MIP extensions, reverse tunnelling, etc.
7 Conclusion
UMTS and CDMA2000 architecture both share the same IMT-2000 vision to provide high bandwidth wireless internet access. Although each approach receives substantial influence from its predecessor, both architecture are designed to be IP-centric with welldefined air and wire interfaces. The requirement of seamless convergence of traditional voice transmission and increasing demand of data delivery will create new business opportunities for manufacturers, operators and providers of content and applications.
8 References
[1] 3GPP Technical Specification 25.401 UTRAN Overall Description [2] 3GPP Technical Specification 25.410 UTRAN Iu Interface: General Aspects and Principles [3] 3GPP Technical Specification 25.420 UTRAN Iu Interface: General Aspects and Principles [4] 3GPP Technical Specification 25.430 UTRAN Iub Interface: General Aspects and Principles
[6] 3GPP2 P.R0001 Version 1.0.0: Wireless IP Architecture Based on IETF Protocols [7] 3GPP2 C.S0003-A: Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems [8] 3GPP2 C.S0004-0: Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems