4 G Mobile Network Architecture
4 G Mobile Network Architecture
1. INTRODUCTION
The horizontal structure will change terminals, services, and the way
services are managed. The horizontal structure will allow different
combinations of service functionalities in the terminal equipment as depicted
in Figure 2. The ovals show possible combinations of services in single
terminals.
Horizontal networks will not only make existing services easier and more
widely applicable, but also create a platform for the integration of various
new services and applications into the same terminals.
New terminal applications in horizontal networks can be divided into
simple fixed-purpose terminals and intelligent terminals. Possible fixed-
purpose terminals can be wearables (watches, eyeglasses, clothes) or
appliances (light switches, doors, micro-ovens). Intelligent terminals include
Personal Digital Assistants (PDA), Smart Phones or Media Terminals.
Simple terminals will connect to Personal Area Networks (PANS) or
Domestic Area Networks. Intelligent terminals apply to Local Area
Networks (LAN) or public access networks. They will have software and
content-defined functionalities that allow various applications within one
device.
4G Mobile Network Architecture 185
Mobile Station (MS): The mobile station is the user terminal, which
consists of a radio transceiver, signal processors, display, and a Subscriber
Identity Module (SIM card). The SIM card enables the usage of services and
personal mobility.
4G Mobile Network Architecture 187
Base Station Subsystem (BSS): The Base Station Subsystem has two
components, the Base Transceiver Station (BTS) and the Base Station
Controller (BSC). The radio transceivers are located in BTSs. The BTS also
manages the radio-link with MS. The Base Station Controller manages one
or more BTSs and handles radio resources, such as radio-channel setup,
frequency hopping, and handovers.
Mobile Services Switching Center (MSC): The Mobile services
Switching Center is the central component of the Network Subsystem. MSC
is like a normal switch in PSTN or ISDN. MSC also handles all the functions
needed to manage mobile subscribers, including registration, authentication,
location updating, handovers and call routing. The roaming functionality of
GSM is provided by the Home Location Register (HLR) and Visitor
Location Register (VLR) together with the MSC. The MSC has no
information about particular mobile stations; this information is stored in
VLRs and HLRs.
Home Location Register (HLR): This functional entity is a data base in
charge of the management of mobile subscribers. A Public Land Mobile
Network (PLMN) may contain one or several HLRs. The number of HLRs
depends on the number of mobile subscribers, on the capacity of the
equipment and on the organization of the network. The HLR contains two
kinds of information: subscription information and some location
information that enables the charging and routing of calls toward the MSC
where the MS is located (e.g., the MS roaming number, the MSC address).
Visitor Location Register (VLR): This controls mobile stations roaming
in the MSC area it is in charge of. When a mobile station enters a new
location area it starts its registration procedure. The MSC in charge of that
area notices this registration and transfers the identity of the location area
where the MS is situated to the Visitor Location Register. If this MS is not
yet registered, the VLR and the HLR exchange information to allow the
proper handling of calls involving the MS.
between the GSM BSS (Base Station Subsystem) and external networks is
routed through the GSM network via the MSC (Mobile Services Switching
Center) and the GMSC (Gateway MSC), while the packet switched
transmission is routed via the GPRS components SGSN (Serving GPRS
Support Node) and the GGSN (Gateway GPRS Support Node). The UTRAN
(UMTS Terrestrial Radio Access Network) will be interconnected to this
core network via two NUS (Inter Working Units), one between the Iu
interface and the GSM A interface, and another between the Iu interface and
the GPRS Gb interface (see Figure 4). This architecture makes it possible for
both GSM and UMTS customers to be connected both to circuit switched
networks (e.g., PSTN and N-ISDN) and packet switched networks (e.g. the
Internet and intranets). Additionally, users should also be able to roam
between GSM and UMTS networks. [8]
Some terminals will have limited memory and processing capability, and
power consumption by any kind of terminal should be minimized by
avoiding any unnecessary activity. Therefore, all possible mobility related
functions should be executed by servers leaving as few functions as possible
for terminals to execute. Terminals will cost less when no additional
software and processing capability is required, and only servers will need to
be upgraded.
As some terminals, also base stations (access points) will have limited
processing capability. Increasing processing capability would cause base
stations to cost more, which is highly undesirable. Bluetooth and WLAN
access points have maximum coverage of roughly about 100m, depending on
power and surroundings. With such a short distance coverage, a relatively
large number of base stations are needed. Thus, expensive base stations
could dramatically increase the overall cost of a network.
new architecture has to operate smoothly with both low and high coverage
base stations.
New 4G terminals and the whole 4G architecture will support both VoIP
(Voice over IP) and current World Wide Web (WWW) based services.
Currently WWW provides a vast amount of services that will not be
modified for 4G terminals. Therefore 4G terminals must be able to
communicate with current protocols to achieve Web based service access.
4. 4G ARCHITECTURE
The fourth generation (4G) of mobile networks will offer mobile services
based on high-speed wireless connections, IP mobility, intelligent terminals,
and World Wide Web type services. 4G operators are the most likely service
and content providers to use different kinds of radio access technologies.
Radio access can be based on private corporate LANs, public wireless LANs
or mobile LANs installed on trains, airplanes, and so on. Handhelds, laptops,
and mobile phones will be used to access the Internet and local services.
4G location area (4GLA) diameter can be from 100m to 1 kilometer.
Figure 5 presents the 4G-network architecture. The idea is to use Session
Initiation Protocol (SIP) [2]. Every home location area contains a SIP
redirect server, which is responsible for maintaining the current location of
users. The home SIP redirect server is analogous to HLR in GSM network
architecture. When a call is made, the home SIP redirect server returns the
current address of called party. The SIP client of the caller then makes
another call to this particular address (or addresses - SIP redirect server can
return several addresses).
192 Kalle Ikkelä, Marko Myllynen, Juha Heinänen and Olli Martikainen
Every location area where visitors are allowed, contain a visitor SIP
proxy (Outbound proxy), which is analogous to VLR in GSM network.
Every visitor in a foreign network registers with the home SIP redirect server
if they want to be reachable. This registration can be done in several ways as
described in [7]. We propose that only Outbound proxy intercept and User-
initiated proxy registrations are used. Both these registration methods use
Outbound proxy to forward SIP registration messages. In the case of
Outbound proxy intercept, terminals send registration messages to their
home network, but Outbound proxy intercepts these messages and changes
the visitor address to point itself. In the case of the User-initiated proxy
registration, the terminal recognizes it is visiting a foreign network and sends
registration messages to the Outbound proxy that then forwards the
messages to the terminal's home network. Thus, all incalls and outcalls
involving a visiting user travel through the outbound SIP proxy.
The use of Outbound proxy for all registrations allows network operators
to collect statistics and possible billing information and also to reduce the
number of SIP registrations. In this way, several location areas can be
combined to one 4G service area (4GSA). By using hierarchical registration
[9], the home location area SIP redirect server is updated only when a
terminal moves from one service area to another. SIP redirect server
4G Mobile Network Architecture 193
redirects SIP calls to the Outbound proxy that forwards calls to the terminal
in its current location in the visited network.
With SIP, users can be reached globally. The same effect could be
achieved using Mobile IP [5], but the triangle routing creates problems. The
data transferred from a server to the user's terminal is routed via a home
agent, which is a non-optimal situation. The usage of SIP enables direct
point-to-point data transfer.
5. MICRO MOBILITY
The term micro mobility here refers to mobility inside a single location
area. Micro mobility is needed when terminals move around using different
base stations and IP sub-networks. The requirement for micro mobility
means that the terminal is able to use the same IP address all the time to keep
TCP (or other higher layer) connections alive when the terminal moves to
another base station cell or IP sub-network. Micro mobility is controlled by
the gateway router responsible for the location area.
In the 4G architecture we are working with, base stations are invisible to
the IP layer of terminals. When a terminal sends an IP packet, it sends it to
the gateway that all base stations are connected to. Base stations only relay
layer 2 packets between terminals and the gateway. Link layer mobility is
managed is done by the device drivers of terminals and base stations. Thus,
if all base stations belong to the same IP sub-network, no additional IP layer
mobility management is required for any part of the network. However, we
are experimenting with multicast to neighbouring base stations to ensure
smooth handovers.
In the case of several IP sub-networks additional mobility management is
needed. Several IP sub-networks are required for scalability, thus using a
single IP sub-network is not a solution in the case of large networks. The
problem of using several IP sub-networks is the following: when a terminal,
using IP subnet A address moves to IP subnet B area, all IP packets destined
to it are routed to IP subnet A. Thus, the terminal will not receive any of
these packets. The IP address can not be changed without breaking live TCP
connections, so we will need a solution which allows a terminal to use an IP
sub-network address of IP subnet A in all other IP subnets, too.
We are experimenting with a Proxy ARP [6] and DHCP [4] based
scheme. Firstly, a terminal is granted an IP address by the means of DHCP
with short lease time (lifetime) when the terminal enters to the local network.
The terminal starts sending DHCP Renewing Requests when more than half
of the lease time is passed. Secondly, when the gateway receives Renewing
Requests it updates its routing caches. When IP packets destined to a
194 Kalle lkkelä, Marko Myllynen, Juha Heinänen and Olli Martikainen
terminal arrive to the gateway, packets are routed to the correct IP subnet
based on the updated routing cache. In the handover phase the packets can
be multicasted to both old and new sub-networks. The address requested to
be renewed will be renewed even if the terminal has moved to another IP
sub-network. Thus, the terminal is able to use several IP sub-networks
without changing its IP address. Lastly, when other hosts in the network are
communicating with the terminal that has moved to another IP subnet,
gateway uses Proxy ARP to relay ARP requests to the moved terminal.
Again, the terminal will be able to communicate even if it has moved to
other IP sub-network.
This solution requires an intelligent gateway that can perform these
actions. The evaluation of the scalability of the proposed solution is work for
the future.
6. ROAMING
Roaming to a new 4G location area requires several functions to be
accomplished in order to be able to use the services of the local network and
the global network, the Internet. These functions are described in this
section.
As a new terminal roams to a location area, the terminal must acquire an
IP address provided by the new network. This can be done, for example,
with DHCP or Mobile IP. Without such an address a terminal cannot
communicate with the network.
If the previous step succeeds and no additional restrictions apply on the
network, a user will then be able to use both global and local services as well
as to make VoIP calls to other parties (outcalls) on the local or other
networks. In order to be able to receive incoming VoIP calls (incalls) and
other SIP based contacts, the terminal must also be registered with the local
SIP proxy.
A user with a terminal may roam to another location area whilst having
open TCP or SIP initiated connections. A TCP connection is established
between two IP addresses and is used to transmit data between those two
endpoints. If either of the used IP addresses becomes unreachable, then the
TCP connection will die. Therefore, when roaming with open TCP
connections, the terminal's IP address must remain unchanged in order to
preserve the TCP connections. This is usually done with Mobile IP.
However, in our experiment we manage IP addresses granted by the location
area DHCP so that they can be kept in the neighbouring location areas. The
smooth location update is then carried out by multicasting the IP packets
arriving at the terminal to both location areas involved.
4G Mobile Network Architecture 195
7. CONCLUSIONS
In this paper we have presented our research on the fourth generation
mobile network architecture. The architecture is analogous to GSM. SIP is
used to enable incalls and outcalls even when the terminal is visiting a
foreign network. Our future work will include scalability testing of the
proposed micro mobility management scheme and analyzing the issue of
roaming between different types of mobile networks.
REFERENCES
[1] ISO/IEC 8802-1 1:1999(E), ANSI/IEEE Std 802.11, 1999 edition.
[2] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP: Session Initiation
Protocol", RFC 2543, March 1999.
[3] Bluetooth SIG, Specification of the Bluetooth System – Version 1 .0 B, Specification
Volume 1 & 2, December 1999.
[4] Droms, R., Dynamic Host Configuration Protocol, RFC 2131, March 1997.
[5] Perkins, C., IP Mobility Support, RFC 2002, October 1996.
[6] Postel, J., Multi-LAN Address Resolution, RFC 925, October 1984.
[7] Schulzrinne, H., SIP Registration, Internet Draft, October 2000.
[8] Martikainen O., Nyman E., Räsänen J., Koponen P., Terminal Mobility in Broadband
Networks, PWC'1998, 1998.
[9] Wedlund, E., Schulzrinne, H., Mobility Support using SIP. Second ACM/IEEE
International Conference on Wireless and Mobile Multimedia, August 1999.
[10] Biggs, Dean, SIP Call Control: Call Handoff, Internet Draft, January 2001.