See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/267544777

Nomadism/FMC Use Cases and AAA Impact

Article

CITATION READS

1 57

13 authors, including:

Pieter Nooren Benoit Radier

TNO France Télécom
17 PUBLICATIONS   136 CITATIONS    26 PUBLICATIONS   122 CITATIONS   

SEE PROFILE SEE PROFILE

Gabor Kovacs
Budapest University of Technology and Economics
17 PUBLICATIONS   71 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

autonomic management and control View project

LEXNET View project

All content following this page was uploaded by Pieter Nooren on 21 November 2014.

The user has requested enhancement of the downloaded file.

BroadBand Europe Geneva, Switzerland
11-14 December 2006

Nomadism/FMC Use Cases and AAA Impact

Hans Mickelsson*), Arnoud van Neerbosα), Pieter Noorenα), Mark Prinsα), Karsten Oberle+), Dávid JochaΩ), Benoit Radierδ)
Gábor Kovács∂), Mohit Thakur∆), Iñigo Pinilla∏), Enrique Areizaga∏, António Gamelas#), Arkadiusz Sitekт),

MUSE consortium [1] aims to define and propose an

Abstract
access network architecture supporting quadruple play, that
In the Access Networks architectures world, the
is High Speed Internet (HSI), VoIP and IPTV with the
evolution to the Fixed Mobile Convergence (FMC) concept
possibility to be nomadic. A first very high-level view of
implies reengineering the basic pillars of the
the Fixed Mobile Convergence challenges was given in [3].
communication structure. The location barrier is being
In this paper the focus is on the main requirements on a
broken. Users want their services to be available “anytime,
multiservice architecture supporting nomadism and session
anywhere”. It leads to the final integration of fixed and
continuity. In particular the key function, namely the
mobile networks or FMC.
Authentication, Authorization and Accounting (AAA)
In order to understand the impact of FMC within the aspect to support the nomadic user in both private and
access networks, this paper presents three use cases related public environments is being investigated.
to the nomadism, session continuity and public access
For the sake of a common language a short description
through private WLAN. High-level requirements to
of the most important definitions and their relations to each
accomplish such features are derived. The case by case
other are given below, all based on definitions developed by
analysis is done with the focus on the key requirement:
ETSI and ITU-T [2].
Authentication, Authorization, and Accounting (AAA).
Roaming
This analysis identifies the impacts/challenges that must be
considered to evaluate FMC AAA framework that focus on
Nomadism
Nomadism Session
Session
Continuity
Continuity Continuous Mobility
access network ability to provide nomadism and session
continuity. Handover Seamless
SeamlessHandover
Handover

Introduction1 Figure 1. MUSE view on FMC-related definitions.

Fixed Mobile Convergence and nomadism will have a Nomadism: “Ability of the user to change his network
large impact on the next generation broadband access access point on moving; when changing the network access
architectures. Nomadism that typically will occur in a fixed point, the user's service session is completely stopped and
access domain, within or between fixed access players, put then started again, i.e. there is no session continuity or
new requirements on how authentication should be handover possible. It is assumed that normal usage pattern
performed for non-stationary users. In addition it also put is that users shutdown their service session before moving
requirements on how to ensure QoS, charging, etc. for to another access point”
nomadic users. FMC adds even more requirements such as Session Continuity: “Ability of the user or terminal to
roaming between home and visited domains belonging to change the network access point while maintaining the
different providers as well as on the degree of the service ongoing session. This may include a session break and
continuity when moving within and between networks. resume, or a certain degree of service interruption or loss of
Many of these challenges has been addressed and partly data while changing to the new access point.”
solved in a mobile context. However, many challenges
Roaming: “Ability of the user to access services
remain when these two worlds merge and fixed services
according to his/her profile while moving outside of his/her
become mobile and vice versa.
subscribed home network, i.e. by using an access point of a
visited network. This requires the ability of the user to get
*)
Ericsson AB, Torshamnsgatan 23, 16480 Stockholm, Sweden,
hans.mickelsson@ericsson.com access in the visited network, the existence of an interface
α)
TNO Informatie- en Communicatietechnologie, [arnoud.vanneerbos; between home network and visited network, as well as a
pieter.nooren;mark.prins]@tno.nl roaming agreement between the respective network
∆)
Siemens Corporate Technology IC2,Otto-Hahn-Ring 6, D-81730 Munich, operators.”
Germany, mohit.thakur@siemens.com
+) Alcatel Research & Innovation, Lorenzstrasse 10, D- 70435 Stuttgart, FMC Use Cases
karsten.oberle@alcatel.de
∏)
Robotiker, Parque Tecnologico Ed 202, E-48170 Zamudio, Spain, To be able to derive the most relevant requirements,
[ipinilla, enrique]@robotiker.es three use cases for nomadism and FMC have been
Ω)
Ericsson Hungary, TrafficLab, 1117 Budapest, Irinyi József út 4-20, developed. A short description aiming to cover
Hungary, david.jocha@ericsson.com combinations of nomadism and session continuity for
#)
Portugal Telecom Inovação, Rua Engº José Ferreira Pinto Basto, 3810-
106 Aveiro, agamelas@ptinovacao.pt
different services over different access technologies are
∂)
Budapest University of Technology and Economics, H-1117 Budapest, given below.
Magyar tudósok útja 2, kovacsg@tmit.bme.hu
т)
Telecom Poland, Obrzezna 7, 02-691 Warszawa,
arkadiusz.sitek@telekomunikacja.pl
δ)
France Telecom, 2 avenue Pierre Marzin, 22307 Lannion
benoit.radier@orange-ftgroup.com

Page 1 of 6
BroadBand Europe
Use case #1: Nomadism use case with video call and
IPTV service upgrade
Jose has a broadband access with High Speed Internet to
his home and subscribes to two services: IPTV (HDTV
quality) and video-telephony including the nomadic feature
options. He is visiting his mother. As a nomadic subscriber,
he will be able to access his subscribed services from
different locations. At his parents’ place, who also have a
High Speed Internet subscription, he starts their PC and
access the Web portal of his Service provider. He
authenticates himself (by means of token or an
username/password) and due to the nomadic characteristic
associated to his services, he gains access to them according
to the service profile.
Then he initiates a video over IP call from the PC to his
video capable multimedia phone at home using his own
subscription to let his wife know his whereabouts. Next, he
uses the Internet to access his media-center (which can be
located either in his CPN (Customer Premises Network) or
at another location) where he has stored all the pictures
from his daughter’s last birthday, and shows them on the
TV screen at his parents home. After watching the pictures
he decides to watch a film with his parents. They do have a
standard IPTV subscription but have just bought a new
HDTV set. As Jose has a HDTV subscription, he contacts
his service provider and upgrades the IPTV service to
HDTV. Now, they sit all together watching the film in
HDTV quality, while Jose´s wife keeps the ability to stay at
home watching other IPTV channels of her own choice.
Figure 2. Jose shows his mother the photos of his daughter's
birthday and watch HDTV film with them.
Use case #2: Session Continuity with conversational
services (Voice and Video over IP)
Bob works for a company that has customers all over
the world. Bob can do most of his work at home, but
sometimes he prefers to be at the company office to consult
with a colleague or to meet a customer.
This afternoon he and a colleague have an appointment
with a customer to discuss a new project. He decided to
walk to the company building as he lives only 2 km away.
As he is about to leave home his multimedia IP phone
rings (the phone is connected to his wireless home network
that is connected to the fixed access network). On the
display Bob sees that his colleague is trying to reach him
via video call. Bob decides to answer the call in the video
Geneva, Switzerland
11-14 December 2006
mode. His colleague tells him that he will probably be a bit
late to the meeting.
While they discuss some details for the meeting, Bob
leaves home. Shortly after his phone gets out of the reach of
the wireless home network (WiFi), it connects to a WiMAX
(or UMTS) base station (Figure 3). Since bandwidth is
more expensive on this network, Bob receives a message on
his screen asking whether he wants to continue with the
video path. Since video is not really important while
walking, Bob decides to save money and tells his colleague
that he will end the video path (the applicability of this
feature depends on the tariff arrangements). The audio path
stays active, so they will be able to continue their
conversation. According to Bob’s preferences, the video
path will be re-established as soon as the cost of bandwidth
is low enough again.
Arriving at the company’s site, the phone connects
automatically with the company’s wireless network (WiFi)
and the video connection becomes active again. At his
office, he transfers the running video call from the mobile
terminal (WiMAX, UMTS) to his notebook connected to a
fixed access network.
Company's
Bob's home building
Access network Park
Home Gateway
802.11b/g
audio + video
audio+video
Wifi / WiMAX /
UMTS
audio
Figure 3. Bob’s walk to the company’s office.
Use case #3: Nomadic user with public access over
private domain
After the meeting at the office Bob returns home.
Walking through the park he feels a bit hungry. He
remembers that his refrigerator is almost empty and that
there was no time left to go to the supermarket. Fortunately,
there are some very good food delivery services available in
his area. He decides to order a pizza via the website of
‘Mario’s Pizza Place’, because the pizza’s on the website
look always very tasty. When he comes near the houses on
the other side of the park, he turns on his multimedia device
which searches for available WiFi networks. Some of the
houses nearby provide public access over their private WiFi
network. According to the network settings on his
multimedia device, Bob gets connected to one of these
networks and orders the pizza over the Internet. Bob now
has a comfortable 20 minutes for his walk home (Figure 4).
Page 2 of 6
BroadBand Europe Geneva, Switzerland
11-14 December 2006

Private network owner who so they will be able to continue their

offers public network access
Bob's home conversation.
to visitors

Access network
Access network At his office he transfers the running AA
video call from the mobile terminal Continue
SEC AA
session on
(WiMAX, UMTS) to his Notebook different
HOV SEP
connected to a fixed access ROA LOC
terminal
Home Gateway Home Gateway
network. LOC

settop box
Use Case 3
Some of the houses nearby provide
AA
802.11b/g
public access over their private WiFi
Public ACC
network. According to the network
802.11b/g Television
access over ARD AA
settings on his multimedia device,
a private RP LOC
Bob gets connected to one of these
domain SEC
networks and orders the pizza over
Bobs multi media device
LOC
the Internet.
Figure 4. Bob uses a public access over a private domain -Authentication, authorization (AA) and accounting
(ACC) is discussed in the next section.
FMC requirements from the use cases
-Media adaptation (MEA) may be necessary when a
The use cases presented above imply some high level
nomadic user or device changes his connection point and
requirements. Without giving an extensive requirement list
the service quality or access characteristics at the new
here, the main network and service related aspects of these
location are different. This should be automatically done by
requirements are presented. The table below shows how the
the content provider or the connectivity provider. If media
various FMC aspects can be derived from each use case.
adaptation is not possible, the user has to deactivate the
The acronyms are explained below the table.
current service and activate another service with the same
Table 1. FMC aspects of the three use cases
content but with the quality related to the new location.
User Network Service
Use case description
aspects related related -Access rights to a domain (ARD): A nomadic user can
Use Case 1 find two kinds of access rights in a visited domain: public
.. he starts his parents PC and
Access to
AA
AA
or private. In case of public access the visitor can connect
access the Web portal of this SP
services from
authenticates himself and due to his remote terminal
ACC
ARD
SEC without the intervention of the owner. Typical use cases are
SEP
nomadic features, he has access to NRP
LOC
LOC the public WLAN in the continuous mobility case and the
all his services.
Video call
free Internet access point through a fixed private network
He then initiates a video over IP call service can be ARD
ACC
MEA for nomadic users in the discrete mobility case. In the
from the PC to his video capable used from a NRP
multimedia phone at home using his different LOC
SEC
SEP
private access case, the access owner may restrict the access
own subscription access network
connection
MSA
LOC to the visited domain.
..he uses the Internet to access his SEP
Photo viewing
-Resource policy (RP): Although the owner of the
media-center, where he has stored Remote access
all the pictures from his daughter’s to private
ARD
NLR
software (e.g. visited network grants the access to the visiting user, the
webserver) or
last birthday, and shows it on the TV server SEC
FTP server in visitor’s resources (e.g. by means of rate limitation) can be
screen at his parents home the CPN
DRM
restricted. Such access resource policy can be applied by
MEA owner of the visited CPN, by the NAP or by the nomadic
SEP
As Jose has a HDTV subscription, DRM ACC LOC user’s device itself.
he contacts his service provider and Service quality
upgrades the IP TV service to HDTV upgrade for a
ARD
NRP
Jose logs-on
onto his -Service environment policy (SEP) is related to the
nomadic user LOC account to
requests the
service set available for a nomadic user away from his
video stream in home network. At home the user can access all subscribed
Simultaneous
HDTV format.
services, but when away only a subset of them can be
sessions from
different ACC
available. The service environment may be restricted by the
Jose´s wife stays home watching locations MSA operator, by the packager, by the owner of the visited CPN,
other IPTV channels
or by the nomadic user himself. The nomadic users may be
accounted on SEP
same
subscriber
contract
provided with the substitute services that replace the
Use Case 2 original ones that can not be offered by visited service
Session
continuity
provider.
Shortly after, his phone gets out of between
AA
ACC -Digital Rights Management (DRM) may impose several
private home
the reach of the wireless home
network and a
SEC SEP constraints for nomadic services, e.g. restriction to access
network, the phone is connected to HOV LOC
a WIMAX (or UMTS) base station.
WiMAX /
UMTS network
ROA the media stream only through a specific device, or
constraints in terms of time or number of users per service.
LOC
or public
hotspot
Since bandwidth is more expensive See also MSA.
on this network, Bob receives a -Network resource policy (NRP): Network resources
message on his screen asking Media
whether he wants to continue with adaptation ACC must be allocated and managed properly in the aggregation
based on ACC MEA
the video path. Since video is not network LOC SEP network by the Network Access Provider for each nomadic
really important while walking, Bob capability and
decides to save money and tells his price
LOC
user. This aspect impacts media adaptation and QoS issues.
colleague that he will end the video
path. The audio path stays active,

Page 3 of 6
BroadBand Europe
-Security, privacy (SEC): User traffic separation and
encryption in case of wireless environment, support for
VPN services and keep the security and privacy for both
nomadic and local users.
-Network Layer Reachability (NLR): Users and
terminals must be addressable at layer 3, while maintaining
security and privacy, supporting firewall and/or NAT
(Network Address Translator) in a CPN.
-Roaming (ROA): Roaming between different operators'
networks. The users should be able to access their profile
via different access networks.
-Handover (HOV): Continuous service access
independently from the terminal, location or available
bandwidth.
-Location (LOC): Location of the user must be known
by the network, even when session continuity or continuous
mobility are ensured. Geographical location must be known
by the services (eg. in order to support emergency calls,
geographical services, billing …)
-Multiple access to the same service (MSA): If service
environment allows, the user may use the same service from
multiple different locations simultaneously.
Requirements should cover the above mentioned aspects
and can be grouped as CPN related (ARD, RP, NLR, SEC),
access network related (NRP, AA, ACC, ROA, SEC, HOV,
LOC) and service specific requirements (SEP, AA, ACC,
DRM, MEA, MSA, LOC).
AAA requirements per use case
The first challenge on AAA is to find the requirements
and corresponding solutions to nomadism. It is important to
understand what type of authentication is suited for a
nomadic user and what options exist for AAA in a public
(hot-spot) and private (residential) scenarios.
The alternatives described take into account the
IP-forwarding model developed in MUSE [1] but are also
aligned with DSLF TR-101 [4]. The scenarios will be
demonstrated during MUSE nomadism lab-trials planned
for December 2006.
The increasing number of ways (wireless or wire-line)
to access the services by a user adds more requirements to
the existing models of the AAA solutions. These
requirements can be quite complicated depending on the
scenario of how the service is being accessed. In our three
use cases, we try to cover most of the possible scenarios in
accessing a service by the nomadic/mobile user.
Use Case 1 depicts the users effort to access his/her
desired services from a remote location (nomadism). From
the authentication point of view, the user would be required
to use some credentials to authenticate him/her for gaining
access to his/her services. Possible methods are e.g. by
login/password, tokens, or SIM card. Every method has its
pros and cons. Where there is an ease of having login and
password being cracked, there is also a hassle of carrying a
SIM card all the time with the user (even though it provides
more security and better credentials). From the network
provider point of view, the problem is much more complex
Geneva, Switzerland
11-14 December 2006
than simply accessing the services as the network provider
in addition to grant access to its IP network has to deal with
QoS adaptation for particular service (e.g. IPTV).
Authentication could be based on:
1. Per Device.
2. Per Session.
3. Per End-user
The above mentioned authentication techniques could
be implemented using different frameworks by different
operators/providers. As the service provider is generally the
one to authenticate the user and authorize access to the
services, a mutual agreement in terms of policing and trust
issues between the service provider and the connectivity
provider is assumed.
Considering use case 1, the user (Jose) changes his
location from his home to his parents home and tries to
access the his services over his parents terminal using his
own account. The CPE (Customer Premises Equipment)
launches an authentication request to its access node present
in the Network Access Provider (NAP), which in turn
extends the request from the CPE to the Network Service
Provider (NSP) through the Connectivity Provider (CP).
The NSP checks the user’s identity in order to authenticate
and authorize this user, based on the credentials supplied by
the CPE. Finally, the 2-way connection is established i.e. an
High Speed Internet. In terms of the video over IP, SIP
protocol provides solution to authenticate user against the
ASP. Conversational services over IP employ service
mobility - the SIP's inherent feature to become nomadic.
Another challenge of Use Case 1 is when the nomadic
user wants to upgrade the quality of IPTV. User accesses
his HDTV content from a terminal that is not his own.
Considering the requirements carefully, it can be assumed
that the provisioning of the HDTV service involves the
bandwidth and QoS parameters negotiation. Other initial
IPTV service already running on the same access line
should not be overlooked.
Within this paper, in order to study the AAA
requirements for the service upgrade, it is considered that
there is only one ASP (Application Service Provider, i.e.
IPTV service provider) in the network. Both José and his
parents are served by the same ASP and thus neither
roaming nor SLA (Service Level Agreement) are
considered between the different business role players. In
this scenario, end-user will be authenticated per device (Set-
top box). Therefore when José moves to his parents’ place
he can directly access his ASP service manager via his
parents’ Set-top box using his own credentials. On the other
hand, when José requests to watch the film and to upgrade
the IPTV quality, the ASP service manager will request to
authenticate José as a valid user based on end-
user/customer credentials. Upon successful authentication
of José, the different elements in the access network should
enhance their QoS capabilities to be able to deliver the TV
stream in HDTV quality to the Set-top box owned by Jose´s
parents. Figure 5 depicts the scenario described above in
Page 4 of 6
BroadBand Europe Geneva, Switzerland
11-14 December 2006

which nomadic user authentication and QoS adaptation on allow him to access his services regardless of the access
different network elements takes place. network he attaches to. EAP-AKA as well as EAP-SIM
within IKEv2 could be used for mutual authentication to
create an IPsec security association for a tunnel between UE
and Packet Data Gateway (PDG). PDG is the gateway to
the compatible services domain between fixed and mobile
network. I-WLAN architecture provides either "direct IP
access" (directly to the Internet) or "3GPP IP access"
(through the 3G provider intranet) to UE with a common
authentication based on credentials provided by mobile
operator (Figure 6). It must be noted that I-WLAN provides
solely network layer authentication. Service layer
authentication is out of scope of I-WLAN specification and
must be carried out by appropriate protocols (e.g. SIP).
Figure 5. Nomadic user authentication in Single ASP
environment.
Use case 1 becomes a challenge for AAA framework
due to the possible access to various services from a single
access line. For example:
1. Enhanced IPTV service accessed from Jose
parents’ place using Jose’s account
2. Normal IPTV service accessed from Jose’s place
using Jose’s account.
3. Other possible services like gaming and video on
demand.
The key motivation for use case 1 is to let nomadic user
to enjoy his/her services at its best as if he/she was at home.
However, making AAA process completely transparent to
the user is not only up to the service provider but the
connectivity provider as well. User has to be authenticated
Figure 6. Distributed access AAA architecture based on
and network elements have to be reconfigured to support
I-WLAN and service AAA architecture based on IMS.
increased bandwidth demand. Finally the service
Another solution to authorize nomadic user access the
consumption has to be accounted, so the user (José) will
provider’s network is based on SIP. SIP based service
receive the fee included in his/her ordinary bill.
authentication is a mandatory method in IMS (also in case
Use case 2 covers the mobile aspects of user nature in I-WLAN provides secure network access mechanism). SIP
accessing the services. User requirement to maintain the does not require network layer tunnelling (IPsec) to be used
session of the Voice and Video over IP call, poses between mobile terminal and the network. The access proxy
significant challenges concerning session continuity and - Session Border Controller (SBC) grants mobile terminal
differences of the AAA architectures between the various the access to the service provider network. To support use
access network providers. Different frameworks have been case 2 the service layer mutual authentication employing
proposed to support the AAA interworking by 3GPP and SIP registration mechanisms (AKA, SIM) may be
WiMAX forum. In MUSE, we study these requirements to sufficient. Security of the SIP signalling and media flows
work out a novel, robust and scalable AAA architecture for can be provided by SIPSecure and SecureRTP thanks to
the future deployments of the nomadic services. TLS (Figure 7).
According to Use Case 2, mobile terminal must have SBC is able to provide location information via
several radio interfaces operating different technologies interworking with CLF (Connectivity Session Location and
(WLAN, UMTS, WiMax). While in the move, Bob Repository Function). Accurate location information is used
authenticates itself against the different access networks. A as a criteria o control mobility according to user profile and
mutual authentication based on single credential and air link is inevitable to manage emergency calls.
encryption must be used since security of the networks Bob
attaches to can not be taken for granted. Finally, Bob
transfers his call from mobile terminal to his office
notebook. Consequently, AAA mechanism can not be based
on device authentication. Two authentication solutions have
been proposed in Muse for Use Case 2: I-WLAN and SIP.
Considering the SAE 3GPP frameworks, I-WLAN
solution offers a good way to authenticate the user and

Page 5 of 6
BroadBand Europe
Figure 7: Distributed AAA architecture based on SIP.
Use case 3 focuses on the aspect of accessing services over
a private network owned by somebody else. The difference
between use cases 1, 2 and 3 is that in the latter one the
owner of the private network does not necessarily have to
know the visitor. From a AAA point of view different
business scenarios are possible. We study following two.
In the first scenario the visitor authenticates against his
service provider who has a direct relationship with the
host’s NAP. Due to the relationship, it is possible to support
QoS in the access network, e.g. by separating the host’s and
visitor’s traffic by means of VLANs.
In the second scenario the visitor authenticates against a
third party (like FON [8]). QoS in the access network can
only be supported if the third party has a direct relationship
with the host’s SP. For both cases the party who
authenticates the visitor in order to provide network access
must have a relationship with both the visitor and the host.
Furthermore a number of security aspects are
considered: protecting the host from a malicious visitor and
protecting the visitor from a malicious host. The related
aspect is whether the residential gateway of the host can be
trusted or not by the provider who authenticates the visitor.
FMC/Session Continuity
Conversational services require change of the network
attachment point to be unnoticeable to the end user. Time
consuming AAA process makes this requirement not easy
to fulfil. In the multiprovider environment, ASP is the one
mainly interested to provide session continuity as it
manages the sessions. Since SIP is the dominant control
protocol for conversational services, SIP mobility is a
natural choice to support session continuity. SIP itself
provides the means to do that (re-INVITE, REFER),
however performance of such solutions is far too poor to
support real time services. IP soft handover [7] is a
promising concept to assure the mobility of the terminal
causes minimal service disruption. During IP soft handover
RTP packets are replicated by SBC to be delivered to both
interfaces of the dual mode terminal. It requires SBC to
implement SIP B2BUA and RTP proxy functionalities and
mobile terminal to implement RTP filtering function.
View publication stats
Geneva, Switzerland
11-14 December 2006
Terminal authenticates itself in front of the ASP, NSP and
NAP before communication channel is established. During
the move, successive re-INVITE messages are
authenticated and intercepted by the B2BUA (SBC). It
allows SIP-controlled IP soft handover to maintain two
parallel connections between the moving terminal and the
correspondent node via two access networks. AAA process
is performed via new access network while real time flows
are still received via old access network. Consequently,
authentication does not bring any disruption in terms of
delay it introduces. Since AAA process can take a while,
SIP-controlled IP soft handover brings limitations in terms
of handover frequency and movement speed.
Standardisation
Contributions to the standardisation bodies on both
nomadism (DSLForum) and FMC (TISPAN) are one of the
goals of MUSE consortium.
Conclusions
The demand for “anytime and anywhere” services
availability constantly grows. FMC technologies are being
developed to provide nomadism, session continuity,
continuous mobility and roaming between the fixed and
mobile networks. At the same time multiprovider and
multiservice networks are being worked out [1]. To support
that effective AAA mechanisms have to be build up. MUSE
consortium [1] has developed three use cases that cover
nomadism, session continuity and public access through
private WLAN. These use cases became the basis for the
general network requirements development (with stress put
on AAA). Based on that an AAA framework has been
proposed to provide solution that can bring use cases into
the reality. This paper presents both use cases, requirements
and AAA architecture to support described services.
Acknowledgments
This work was supported by the IST FP6 Integrated
Project MUSE (Multi Service Access Everywhere).
References
1. MUSE (Multi Service Access Everywhere),
http://www.ist-muse.org
2. ETSI TR 180 000, V1.1.1, 02/2006
3. Melander, B. et al, “FMC from a fixed access
perspective”, Mobile Summit Mykonos, 06/2006
4. “Migration to Ethernet-based DSL aggregation”, DSLF
TR-101, 04/2006
5. 3G TS 24.228 - “Signalling flows for the IP Multimedia
call control based on SIP and SDP – Stage 2/3”,10/2006
6. J. Rosenberg. et al, “SIP: Session Initiation Protocol”,
IETF RFC 3261, 06/2002
7. Nilanjan Banerjee ”Seamless SIP-based mobility for
multimedia applications” IEEE Network 04/2006
8. FON WiFi Community, http://www.fon.com
Page 6 of 6