Advances in Wireless Networks

ECE 617
Contents
Unit I Introduction
Unit II WirelessIP NetworkArchitectures
Unit III IPMultimediaSubsystemsandApplication
Unit IV MobilityManagement
Unit V Qualityof Service
Mobility Management
BasicIssuesinMobilityManagement
MobilityManagement inIP Networks
MobilityManagement in3GPP Packet Networks
Mobility Management in 3GPP2 Packet Data
Networks
MobilityManagement inMWIFNetworks
Comparison of Mobility Management in IP, 3GPP,
and3GPP2Networks
Basic Issues in Mobility Management
Impact of Naming and Addressing on Mobility
Management
LocationManagement
Packet DeliverytoMobileDestinations
Handoffs
Roaming
Types of Mobility
Terminal mobility
discrete
continuous
User mobility
Servicemobility
Basic Mobility Management Requirements
Support all formsof mobility
Support mobilityfor all typesof applications
Support mobilityacrossheterogeneousradiosystems
Support session(service) continuity
Global roaming
Basic Functional Components
Location management
Packet delivery to mobiles
Handoff and roaming
Network Access Control
Authentication
Authorization
Accounting
Impact of Naming and Addressing on
Mobility Management
A terminals address typically identifies a network
attachment point
Atelephonenumber inaPSTNnetwork identifies aport ona
PSTNswitchrather thanthetelephoneset itself.
An IP terminals IP address identifies an attachment point to
anIP network.
Terminal-independent user names:
International Mobile Subscriber Identifier (IMSI):
independent of theterminal usedbytheuser
Network AccessIdentifier (NAI): maketheIP terminal names
independent of theterminalsaddresses
Email address, SIPURI, etc.
Location Management
Location Update Strategies
Location Discovery (Paging)
Interactions between Location Update and Paging
Location Update Strategies
Whenamobileshouldperformlocationupdates?.
everytimethemobilechangesitsnetworkattachment points
group network attachment points into location areas and
only keeps track of which location areaeach mobileis likely
in when the user and the network haveno traffic to send to
eachother
A network may use multiple types of location areas
simultaneously
The location areas used in a radio access network can be
different from the location areas used for location
management inthecorenetwork.
Location Update
Time-basedupdate
Movement-basedupdate
Distance-basedupdate
Parameter-basedupdate
alsoreferredtoasprofile-basedupdate
Implicit update
Probabilisticupdate
Movement-based vs. distance-based
location update strategies
Location Discovery (Paging)
A network performs paging by sending one or multiple paging
messages to a paging area where the mobile is likely to be
located
Pagingareasdonot havetobeidentical tolocationareas
Upon receivinga pagingmessage, a mobile needs to update its
precisecurrent locationwiththenetwork
The mobile may also need to establish the necessary
connectivitywiththenetwork
Issues with Paging
Paging should be done within a reasonable time
constraint.
How to construct paging areas?
Static or dynamic
How to search a paging area to locate a mobile?
Paging Strategies
Blanket paging
Sequential paging
Other pagingstrategies
Geographicpaging
Grouppaging
Individualizedpaging
Interactions between Location Update and
Paging
Overhead
networkresourcesconsumedbylocationupdatesandpaging
Performance:
e.g.,paginglatency
Complexity
Packet Delivery to Mobile Destinations
Direct Delivery
mayroutepacketsalongthemost direct paths
needtoknowwhether destinationisamobileor fixedhost
require every originator to implement protocols for
determiningadestinationslocation
RelayedDelivery
mobilityanchor pointscouldbecometrafficandperformance
bottlenecks
Strategies for delivering packets to mobiles
Integrated Delayed Delivery and Direct Delivery
strategies
Handoffs
HandoffsinanIP-basedwirelessnetwork mayoccur at
different protocol layers
Handoffs at each protocol layer may occur in different
scopes
Handoffscanbehardor soft
Layers of Handoff
Physical layer
Logical linklayer
IPlayer
Mobilityat different protocol layerscanbemanagedby
different protocols
Mobility management at the IP layer may be
independent of mobility management at the lower
protocol layers
Scopes of Handoff
Intra-subnet handoff
Inter-subnet handoff
Inter-router handoff
Soft Handoff
Datadistributionandselection
SelectionandDistributionUnit (SDU)
Datacontent synchronization
Roaming
Roaming is the process whereby a user moves into a
visiteddomain.
Homedomain: maintainaservicesubscriptionaccount
Visited domain: does not have an account of a user moves
intothisdomain
Capabilities to Support Roaming
Networkaccesscontrol for visitingmobiles
Roaming Agreement between the mobiles home
domainandthevisiteddomains
Session continuity while a user crosses domain
boundaries
Roaming
Roaming Broker
Mobility Management in IP Networks
NamingandAddressingof IP Terminals
MobileIPv4
MIPv4Regional Registration
PagingExtensionstoMobileIPv4
MobileIPv6
SIP-basedMobilityManagement
Cellular IP
HAWAII
Naming and Addressing of IP Terminals
IPaddress
newIP addressfor newsubnet
multiplenetworkinterfaceswithdifferent IP addresses
NetworkAccessIdentifier (NAI)
username@realm
Mobile IPv4
Agent Discovery
Movement Detection
LeavingtheHomeNetwork
EnteringandStayinginaVisitedNetwork
ReturningtotheHomeNetwork
Mobile-HomeAuthenticationExtension
Vendor/ Organization Specific Extensions to Mobile IP
Messages
ReverseTunneling
Limitationsof MIPv4
MIPv4RouteOptimization
Mobility Issues in IP Networks
Onceamobileterminal movestoanewsubnet
Acorrespondent nodeneedstousethemobilesnew
IPaddress
It is difficult to force every possible
correspondent nodeto keep track when amobile
terminal may changeits IP address and what the
mobilesnewaddresswill be
Changing IP address will cause on-going TCP sessions
tobreak
Ensureon-goingTCP connectiondoesnot break
Restorequicklyif TCP connectionbreaks
Home Network
Home address: a globally unique and routable IP
address
preconfiguredor dynamicallyassigned
Home network: the network whose network address
prefix matches that of the mobile terminals home
address
Homeagent (HA)
maintain up-to-date location information for the
mobile
intercept packets addressed to the mobiles home
address
tunnel packetstothemobilescurrent location
Foreign Network
Care-of Address(CoA)
assignedtothemobilebytheforeignnetwork
a mobile uses its CoA to receive IP packets in the foreign
network
ForeignAgent (FA)
Provides CoAs and other necessary configuration
information (e.g., address of default IP router) to visiting
mobiles.
De-tunnels packets arriving fromthe tunnel froma visiting
mobiles home agent and then delivers the packets to the
visitingmobile.
Acts as the IP default router for packets sent by visiting
mobileterminals.
Helps visiting mobiles to determine whether they have
movedintoadifferent network.
Care-of Address (CoA)
ForeignAgent CoA
HAtunnelspacketstoFA
FAde-tunnelspacketsanddeliverstothemobile
Co-locatedCoA
HAtunnelspacketstothemobiledirectly
Packet flows between a correspondent
host and a mobile: mobile uses FA CoA
Packet flows between a correspondent host and
a mobile: mobile uses co-located CoA
Agent Discovery
The process for a mobile terminal to discover the
mobility agents and receive information from these
agents
Achieved by the mobility agents advertising their
services and system information to the mobiles via
Agent Advertisement messages
A mobilemay solicit an Agent Advertisement message
from any mobility agent by sending an Agent
Solicitationmessage
Mobile-AgentsMulticast Groupaddress224.0.0.11
Uses the Internet Control Message Protocol (ICMP)
Router DiscoveryMessage
ICMPRouter Advertisement Message
ICMPRouter SolicitationMessage
Agent Advertisement
ICMP Router Advertisement message with extensions to
carryMIPv4specificinformation
MobilityAgent Advertisement Extension
indicate that an ICMP Router Advertisement message is also a
MIPv4Agent Advertisement message
carryinformationspecifictoaMIPv4mobilityagent
Prefix-LengthsExtension(optional)
indicatethenetwork prefixlength (in bits) of each Router Address
advertised
Structure of Mobile IP Agent Advertisement
message
Mobility Agent Advertisement Extension
R (Registration required)
B (Busy)
H (Home agent)
F (Foreign agent)
M (Minimal encapsulation)
G (GRE encapsulation)
r (Reserved)
T (Reverse tunneling)
MIPv4 Mobility Agent Advertisement Extension
to ICMP Router Advertisement message
Movement Detection
Use the Lifetime field in Agent Advertisement
messages
Usenetwork prefixes
requires the mobile to know the network prefix
lengthsof theoldandthenewnetworks
Others
indicationsof changesinlower layer
Leaving the Home Network
ARP (Address Resolution Protocol) REQUEST
Sender Protocol Address
Target Protocol Address
Sender Hardware Address
ARP REPLY
ARP Cache
Entering and Staying in a Visited Network
Amobilewill havetoacquireaCoA
Themobilewill thenregister theCoAwithHA
Locationupdate
HA will then tunnel packets addressed to the
mobileshomeaddresstothisnewCoA
FA CoAvs. Co-located CoA
FA CoARegistration must be done via the FA
If FA wants to deny network access discard the Registration
Request
generate a Registration Reply to the mobile
Co-located CoA
oRegistration may be done directly with the HA, unless the FA
requires registration via the FA
oThe FA can force a mobile to register through the FA by
setting the R flag in the Agent Advertisement it sends to the
mobiles
MIPv4 Registration Message Flows
Registration Request
In addition to registeringaCoA, amobileterminal can
alsouseRegistrationRequest messagesto
Discover theaddressof ahomeagent
Discover the mobiles home address, if the mobile is not
configuredwithahomeaddress
Renewaregistrationthat isduetoexpire
Deregister withtheHAwhenthemobilereturnshome
MIPv4 Registration Request message format
Format of Registration Request
Type
S: Simultaneousbindings
B: Broadcast datagrams
D: Decapsulationbymobileterminal
M: Minimal encapsulation
G: GREencapsulation
r: Thisfieldwill alwaysbezeroandignoredonreception
T: ReverseTunnelingrequested
x: Thisfieldwill alwaysbezeroandignoredonreception
Lifetime
Azerolifetimeindicatesarequest for deregistration.
Registration Reply
Code: avalueindicatingtheresult of thecorresponding
RegistrationRequest
Lifetime
Successful registration: the number of seconds
remaining before the registration is considered
expired
zero: indicate that the mobile terminal has been
deregistered
Failedregistration: thisfieldshouldbeignored
MIPv4 Registration Reply message format
Returning to the Home Network
Broadcast GratuitousARPover thehomenetwork
Bothmobileterminal andHAmaydoit
DeregistrationRequest
Mobile-Home Authentication Extension
SecurityParameter Index(SPI)
a 4-octet identifier used to identify a security
context betweenamobileanditshomeagent
Authenticator
a number calculated by applying an authentication
algorithmonthemessagethat needstobeprotected
HMAC-MD5: default authenticationalgorithm
Mobile-Home Authentication Extensions to
Mobile IP messages
Fields protected by MIP Mobile-Home
Authentication Extension
Reverse Tunneling
Ingress filtering: outgoing packets from a visiting mobile
may not be able to go through the IP access router in the
visitednetwork
RFC 3024: specifies how reverse tunneling works when a
mobileusesForeignAgent CoA
T flaginAgent Advertisement
T flaginRegistrationRequest
Packet delivery
Direct DeliveryStyle: FAasdefault router
EncapsulatingDeliveryStyle
Mobile IPv4 reverse tunneling
MIPv4 Route Optimization
Allowacorrespondent node(CN) to beawareof amobiles
current CoA and then tunnel packets to the destination
mobilesCoAdirectly
Binding Cache: maintained by a CN to map the mobiles
homeaddressestotheir CoAs
BindingUpdate: HAinformsCNthemobilescurrent CoA
Asecurityassociation betweentheCNandtheHAneeds to
beestablished
scalability
MIPv4 route optimization
MIPv4 Regional Registration
Long handoff delay in basic MIPv4: a mobile has to
register withitsHAeverytimeit changesitsCoA
MIPv4Regional Registration: allowamobiletoregister
itsnewCoAlocallywithitsvisitednetworkdomain
Each network domain consists of two or more hierarchical
levelsof foreignagents
GatewayForeignAgent (GFA)
MIPv4 Regional Registration
Registration
MIPregistration: movetoanewGFA
Regional registration: movebetween FAs connected to
asameGFA
Regional Registration Request: sent by amobileto aGFA via
theFAtoinitiateregional registration.
Regional Registration Reply: sent by a GFA to a mobile in
responsetoaRegional RegistrationRequest.
Paging Extensions to Mobile IPv4
PaginginMobileIP(P-MIP)
ActiveTimer: determineamobileisinactiveor idlestate
activestate: standardMIP
idlestate: maynot performMIP registration
noexplicit signalingmessages
RegisteredFA
theFAthroughwhichamobileperformeditslast MIP registration
responsible for keeping track of whether the mobile is in active or idle state by
usingActiveTimer
anFAisrequiredoneachIP subnet
PagingArea: an idlemobiledoes not haveto performMIP registration
whenmovinginsidethesamepagingarea
PagingAreaIdentifier (PAI): carriedbyAgent Advertisement
A mobile compares the PAIs received fromdifferent FAs to determine whether it
hasmovedintoanewPagingArea.
Paging Extensions to Mobile IPv4
Mobile IPv6
Similar conceptsasinMIPv4, but noFA
Mobilesuseonlyco-locatedcare-of addresses.
Standard IPv6 Neighbor Discovery can be used to help
mobilestodetect movement
Binding: association between amobiles homeaddress
anditscare-of address
BindingUpdate
BindingAcknowledgment
Authentication of BU and BA messages is achieved using
IPsec
MIPv6 address binding with home agent
Packet Delivery
Bi-directional tunnelingmode
Acorrespondent host doesnot havetouseMobileIPv6
Routeoptimizationmode
Route optimization is designed to be an integral part of
MIPv6
MIPv6 Bi-directional Tunneling Mode of
Operation
MIPv6 Route Optimization
Binding Update
SequenceNumber
A (Acknowledge): request aBA messagebereturned upon receipt
of theBUmessage
H (Home Registration): request that the receivingnode act as the
sendingnodesHA
L (Link-Local Address Compatibility): set when the home address
hasthesameinterfaceidentifier asthelink-local address
K (Key Management Mobility Capability): indicate whether the
protocol used for establishing the IPsec security association can
survivemovement
onlyvalidinaBUmessagesent toaHA
Reserved
Lifetime: the number of time units remaining before the binding
expires
Mobility Options: avariable-length field that contains oneor more
MobilityOptionsinaType-Length-Valueformat
Mobility Options
OptionsinBU
AlternativeCare-of Addressoption: carryamobilesCoA
Binding Authorization Data option: carry security-related
information needed by the receiving node to authenticate
andauthorizetheBUmessage
NonceIndicesoption: usedbyCNtoauthenticateaBUfroma
mobile
onlyusedwhentheBUmessageissent toaCN
Binding Acknowledgment
Statue: indicate the status of how the corresponding BU
messageisprocessed
K: indicatewhether theprotocol usedbyHAfor establishingthe
IPsecsecurityassociationcansurvivemovement
Reserved
SequenceNumber: copiedfromthecorrespondingBU
Lifetime
MobilityOptions
BindingAuthorizationDataoption
Binding Refresh Advice option: used by a home agent to
informamobilehowoften themobileshould sendanewBU
messagetothehomeagent.
Hierarchical Mobile IPv6 Registration
Forwarding from the previous care-of address
Local home agent
Mobile IPv6 "forwarding from previous
care-of address" mechanisms
One approach to support hierarchical
Mobile IPv6 registration
SIP-based Mobility Management
Mainreasonsfor SIP-basedmobilitymanagement
SIP is currently the protocol of choice for signaling and control of real-
timevoiceandmultimediaapplicationsover IP networks.
Significant efforts in theresearch community and theindustry havebeen
devotedtosupportingmobilityusingSIP.
SIP appears to be the only application-layer protocol that can be readily
extendedtosupport terminal mobilitytoday.
SIPalreadysupportsuser mobility.
Key difference between SIP-based mobility management and
Mobile IP: SIP servers may only participate in setting up the
applicationsessionsbetweentheendusers
SIP-based Mobility Management
Movement Detection
Pre-Session Terminal Mobility
Mid-Session Terminal Mobility Support
Limitations of IP Mobility Using SIP
Movement Detection
Detection of an IP network change and acquiringnew
IP addresses may be achieved using any available
means to themobileand do not haveto bepart of the
SIPprotocol.
Should inform the SIP application of the address
change
Pre-Session Terminal Mobility
A SIP Redirect Server in a mobiles home network
tracks the mobiles current location and provides the
location information to a caller so that the caller can
contact themobileat its newlocation directly to setup
aSIP session
The SIP Redirect Server in a users home network
learns about the users current location fromthe SIP
REGISTRATIONmessagesreceivedfromtheuser
SIP-based pre-session terminal mobility
management
Location update for supporting SIP-based
terminal mobility
Mid-Session Terminal Mobility Support
Mobile sends a new SIP INVITE message to invite the
correspondent host to re-establish the SIP session to
themobilesnewlocation
Mobile also updates its location with its home SIP
Redirect Server
SIP-based mid-session terminal mobility
management
Limitations of IP Mobility Using SIP
Amobilewill havetoregister itsnewIP addresswitha
SIP server inthemobileshomenetworkeverytimethe
mobilechangesitsIPaddress
long handoff delays when the mobile is far away from its
homenetwork
maybesolvedbyhierarchical registration
It is difficult for SIP-based mobility management to
keep aTCP session alivewhileamobilechanges its IP
address
amobileterminal andacorrespondent host mayuseaSIP
EYE
agent to hide the IP address change fromthe on-going TCP
sessions
Cellular IP
Designedtosupport fast handoff inawireless network
of limitedsize, for example, anetwork withinthesame
administrativedomain
Reduce handoff latency by eliminating the need for a
mobile to changeits IP address whilemovinginside a
Cellular IP network
Usehost-specificrouting
routingandpacket forwardingbasedonthefull IP address
maintain a host-specific downlink route for forwarding
packets to each individual mobile, rather than maintaininga
route for each IP address prefix as with regular IP routing
protocols
Cellular IP
Paging in Cellular IP networks
HAWAII
Similar toCellular IP, HAWAII (Handoff-AwareWireless
Access Internet Infrastructure) is designed to support
fast handoff and paging inside a wireless network
under asingleadministrativedomain
reducehandoff latency
usehost-specificrouting
HAWAII and Cellular IP differ in routing and mobility
management implementations.
HAWAII
HAWAII mobile power-up procedure
HAWAII path setup schemes
Handoff between HAWAII domains using Mobile IP
Mobility Management in 3GPP Packet Networks
Packet Mobility Management (PMM) Context and
States
LocationManagement for Packet-SwitchedServices
RoutingAreaUpdate
ServingRNSRelocation
HardHandoffs
PagingInitiatedbyPacket-SwitchedCoreNetwork
ServiceRequest Procedure
Handoff and Roaming Between 3GPP and Wireless
LANs
Overview
As discussedinUnit 2, all packet-switcheduser datatoand
fromamobileisfirst sent tothemobilesservingGGSN
The mobile and its servingGGSN use a host-specific route
toexchangeuser data
Therefore, mobility management in 3GPP PS domain is, in
essence, to manage the changes of the host-specific route
betweeneachmobileanditsservingGGSN
Amobiledoesnot havetomaintainall thetrafficbearersin
the RAN or the CN if it does not expect to send or receive
user datasoon
The mobile does not even need to maintain its dedicated
signalingconnectiontotheSGSNat all times
Various Scopes of Mobility
Inter-NodeBHandoff
ChangeRadioBears
Inter-RNCHandoff
ChangeIuBearsandRadioBears
Inter-SGSNHandoff
UpdatethePDP context; establishanewCNBears; changeIuBears
andRadioBears
Inter-GGSNHandoff
Create a new PDP context; establish a new CN Bears; change Iu
BearsandRadioBears
Scope of mobility in 3GPP packet-switched
domain
Packet Mobility Management (PMM) Context
and States
PMMcontext:
aset of informationusedbythenetworktotrackthemobiles
location
PMMstate
Which network connections (bearers) between the mobile
andtheSGSNshouldbemaintainedfor themobile
Howthemobileslocationshouldbetrackedbythenetwork
MaintainedbySGSNandmobilestation
PMM States
PMM-DETACHED State
PMM-CONNECTED State
PMM-IDLE State
PMM-DETACHED State
ThereisnocommunicationbetweenthemobileandtheSGSN
The mobile and the SGSN do not have valid location or routing
informationfor themobile
Themobile does not react to systeminformation related to the
SGSN
TheSGSNcannot reachthemobile
PMM-CONNECTED State
The SGSN and the mobile have established a PMM context for
themobile.
A dedicated signaling connection is established between the
mobileandtheSGSN.
A mobiles location insidetheRANis tracked by theRNCs at an
accuracylevel of radiocells.
PMM-IDLE State
TheSGSNandthemobilehaveestablishedthePMMcontextsfor
themobile.
Nosignalingor trafficconnectionexists betweenthemobileand
theSGSN.
ThemobileslocationistrackedbytheSGSNat anaccuracylevel
of aRoutingArea.
ThemobileisreachablebytheCNviapaging.
PDP Context
When the mobiles PMM state transitions from PMM-
CONNECTED to PMM-IDLE subsequently, the mobiles
existing active PDP contexts will continue to remain in
ACTIVEstateontheGGSNandtheSGSN.
Reduce the time for a mobile to change from PMM-IDLE
statebacktoPMM-CONNECTEDstate
Make it easier for the PS CN domain to support paging
AllowtheGGSNtoalwaysknowamobilesservingSGSN
GGSNsdonot havetobeawareof thepagingoperations
3GPP PMM state transition machines
Synchronization
PMM states of the mobile and the SGSN may lose
synchronization
Will becorrected
WhenperformingRoutingAreaUpdate
Whenperformingpaging
Location Management for Packet-Switched
Services
LocationConcepts
LocationTracking
Location Concepts
TheRANusesthefollowinglocationconcepts
Cell Area(or Cell)
UTRAN Registration Area(URA): an areacovered by aset of
cells
TheCNusesthefollowinglocationconcepts
Location Area (LA): a group of Cells used by the CS CN
domain to track the locations of mobiles that are using CS
services
RoutingArea(RA): agroupof CellsusedbythePSCNdomain
totrackthelocationsof mobilesthat areusingPSservices
3GPP Location Management for Packet
Services
LA vs. RA
LA
OneLAishandledbyonlyoneMSC/ VLR.
Each LA is identified by a globally unique Location Area
Identifier (LAI).
When a mobile moves inside a LA, it does not have to
performlocationupdatewiththeCNCSdomain.
RA
OneRAishandledbyonlyoneSGSN.
Each RA is identified by a globally unique Routing Area
Identifier (RAI).
When a mobile moves inside a RA, it does not have to
performlocationupdatewiththeCNPSdomain.
OneRA cannot belongto morethan oneLA whileeach
LAmaycontainmultipleRAs.
Structures of 3GPP Location Area Identifier
and Routing Area Identifier
Location Tracking
PMM-IDLEstate
RRC-IDLE mode: the mobiles location is tracked at the RA
level bytheSGSNs
RRC-CONNECTED mode: the SGSNs will also track the
mobileslocationat theRAlevel
PMM-CONNECTEDstate
RRC-CONNECTED mode: the mobiles serving SGSN will
know the mobiles serving RNC because the serving SGSN
maintains a signaling connection through the mobiles
servingRNCtothemobile
RRC States
RRC-CONNECTEDmode:
A mobile in RRC-CONNECTEDmode has an established RRC
connection.
RRC-IDLEmode:
A mobile in RRC-IDLE mode has not established any RRC
connection.
The same RRC connection is used by the mobile to
transport all signalingtraffic and user traffic for its CS
andPSservices.
Routing Area Update (RAU)
Intra-SGSN Routing Area Update
Inter-SGSN Routing Area Update
When to Perform RAU ?
ThemobileentersanewRoutingArea.
Themobilesperiodicroutingareaupdatetimer expires.
The mobile is directed by the network to re-establish its
RRCconnection.
ThemobilesNetworkCapabilitychanges.
A mobiles Network Capability is a set of information describing
themobilesnonradio-relatedcapability. For example, information
neededfor performingcipheringandauthentication.
Intra-SGSN Routing Area Update
MobilehastobeinPMM-CONNECTEDstate
Mobile initiates RA update by sending a Routing Area
UpdateRequest tothetarget SGSN
P-TMSI
Old RAI: used by the target SGSN to determine whether the
RAUpdateisintra-SGSNor inter-SGSN
P-TMSI Signature
UpdateType
NetworkCapability
3GPP Intra-SGSN routing area update
procedure
Inter-SGSN Routing Area Update
Thetarget SGSNisdifferent fromthesourceSGSN
Thetarget SGSNwill sendaSGSNContext Request messagetothesource
SGSNtoaskthesourceSGSNtovalidatethemobilesP-TMSI
ThesourceSGSNwill
Uponpositivevalidationof theP-TMSI
SGSNContext Response: carryPMMcontext andPDP context
SRNSContext Request
Uponnegativevalidationof theP-TMSI
The source SGSN will send an appropriate error cause to the target
SGSN, which will trigger the target SGSN to initiate the security
proceduresdirectlywiththemobiletoauthenticatethemobile.
If this authentication is positive, the target SGSN will send another
SGSN Context Request message to the source SGSN to retrieve the
mobilesPMMcontext andPDP context.
After RAU,thehost-specificrouteisalsoupdated
Inter-SGSN Routing Area Update Procedure
Serving RNS Relocation
Relocate I
u
connections from the old serving RNC to the new
servingRNC
This section assumes that before the relocation, the mobiles
serving RNC is using the I
ur
interface to forward signaling and
user traffic to another RNC, which in turn delivers the user
traffictothemobile.
Serving RNS Relocation
Procedure
Only the source RNC can initiate Serving RNS Relocation.
Based on measurement results of the quality of the radio
channels to the mobile and based on its knowledge of the
RANtopology
Send a RANAP Relocation Required message to the source
SGSNRelocationType: UEnot Involvedor UEInvolved
SourceID: Identifier of thesourceRNC
Target ID: Identifier of thetarget RNC
SourceRNCtotarget RNCtransparent container: information
needed by thetarget RNCto performservingRNCrelocation
includingsecurityinformation,RRCcontext
Procedure for Serving RNS Relocation
Hard Handoffs
Inter-RNChardhandoff without I
ur
interface
Only the source RNC can initiate the inter-RNC hard handoff
process.
RANAP RelocationRequiredmessagetothesourceSGSN
RelocationType: UEInvolved
Relocation Request Acknowledge: Carry an extra information
element - Target RNCtoSourceRNCTransparent Container
contain all theradio-related information that themobilewill
need in order to tune its radio to the radio channels of the
target RNS
3GPP PS Domain hard handoff
Paging Initiated by Packet-Switched Core
Network
AmobileinPMM-IDLE state
The SGSN initiates paging by sending a RANAP Paging
messagetoeveryRNCintheRoutingArea
Identitiesof themobiletobepaged
CNDomainIdentifier
Area
TwotypesinsideRAN
Type1Paging
NodedicatedRRCconnection
UsePagingChannel
Type2Paging
UsededicatedRRCconnection
3GPP Paging in packet switched domain
Service Request Procedure
Usedbyamobile
in PMM-IDLE state: request theestablishment of asignalingconnection between
themobileandtheSGSN
in PMM-CONNECTED state: request resource reservation for the mobiles active
PDPcontexts
SGSN takes actions based on the Service Type in the received
ServiceRequest
DATA
asignalingconnectionbetweenthemobileandtheSGSNwill beestablished
theRABswill beallocatedfor themobilesactivePDPcontexts
SIGNALING
Only a signaling connection between the mobile and the SGSN will be
established
ServiceRequest isacknowledged
Mobile in PMM-CONNECTEDstate and Service Type is DATA: SGSN will return a
ServiceAccept
Mobile in PMM-IDLE state and Service Type is SIGNALING: SGSN does not send
anyexplicit signalingmessage
3GPP Mobile-initiated Service Request
Procedure
Handoff and Roaming Between 3GPP and
Wireless LANs
Handoff between3GPP andIP networksusingMobileIP
Sample signaling flow for handoff between 3GPP and IP
networksusingMIPv4
Mobileterminalswithdual homeaddresses
Handoff between 3GPP and IP networks
using Mobile IP
Sample signaling flow for handoff between
3GPP and IP networks using MIPv4
Mobile terminals with dual home
addresses
Mobility Management in 3GPP2 Packet
Data Networks
Packet DataServiceStates
LocationManagement for Packet DataServices
Handoffsfor SupportingPacket DataServices
Fast Inter-PDSNHandoff
PagingandSendingUser DatatoaDormant Mobile
Overview
As discussed in Unit 2, all user IP packets to and fromamobile
are sent first to the mobiles serving PDSN, which in turn
forwardsthepacketstowardstheir final destinations.
A mobileand its servingPDSN maintains aPPP connection and
useit asthelinklayer for exchanginguser IP packets.
RadioBearer betweenthemobileandaBSC
A8connectionbetweenBSCandaPCF
A10 connection (i.e., R-P connection) between the PCF and the mobiles
servingPDSN
An optional P-P (PDSN-to-PDSN) connection between the mobiles
servingPDSNandatarget PDSNtosupport fast inter-PDSNhandoff
Intra-PDSN Handoff
Themobiles PPP connection to its servingPDSNdoes not need
tochange.
Themobiledoesnot needtochangeitsIP address.
Themobile does not have to performregistration with its homeagent if
MobileIP isused.
Some or all of the bearers that make up the path of the PPP
connectionmayneedtobechanged.
Inter-BTShandoff: changeRadioBearers
Inter-BSChandoff: changeRadioBearers, A8/ A9connections
Inter-PCF handoff: change Radio Bearers, A8/ A9 and A10/ A11
connections
Inter-PDSN Handoff
Regular Inter-PDSN Handoff
The target PDSN becomes the mobiles new serving PDSN as a result of
the handoff.
The mobile will have to establish a PPP connection to the target PDSN and
configure a network protocol (i.e., IPv4 or IPv6) over the PPP connection
as part of the handoff process.
If Mobile IP is used, the mobile will need to acquire a new care-of address
and register it with the mobiles Mobile IP home agent.
Fast Inter-PDSN Handoff
The mobiles serving PDSN remains unchanged during and after the
handoff as long as the mobile has an active packet data session.
The mobile continues to use the same PPP connection.
The mobile does not have to change its care-of address.
The mobile does not have to perform registration with its Mobile IP
home agent.
The serving PDSN tunnels downlink PPP frames to the target PDSN.
A PDSN-to-PDNS (P-P) connection will need to be established
between the serving PDSN and the target PDSN.
Scopes of mobility in a 3GPP2 packet data
network
Packet Data Service States
ACTIVE/ CONNECTEDstate
DORMANT state
NULL/ INACTIVEstate
3GPP2 Packet Data Service State
transitions
ACTIVE/ CONNECTED State
A bidirectional traffic radio channel is established
betweenthemobileandtheBSC.
The A8/ A9 and A10/ A11 connections are established
for themobile.
The mobile and its serving PDSN maintains a PPP
connection.
When Mobile IP is used for mobility management, the
mobile will have already performed Mobile IP
registrationwithitshomeagent.
DORMANT State
No traffic radio channel exists between themobileand
theBSC.
NoA8connectionexistsfor themobile.
ThemobilesA10connectionismaintained.
The PPP connection between the mobile and its
servingPDSNwill bemaintained.
NULL/ INACTIVE State
There is no traffic radio channel between the mobile
andtheBSC.
No A8/ A9 or A10/ A11 connection exists for the
mobile.
No PPP connection exists between themobile and the
PDSN.
State Maintenance
ThePacket DataServiceStates aremaintained in both
PCFandmobileterminal.
The PDSN will not be aware whether a mobile is in
Activeor DORMANT state.
Location Management for Packet Data
Services
Packet Zone: geographical areaservedbyasinglePCF
uniquelyidentifiedbyaPacket ZoneID(PZID)
Each BS periodically broadcasts, over the broadcast
radiochannels,thePZIDof thePacket Zoneit serves.
A dormant mobile will be able to receive such
broadcast systeminformation and use it to determine
whether it hasmovedintoanewPacket Zone.
3GPP2 does not define any new protocol, message, or
procedureuniquelyfor performingPacket Zoneupdate.
The procedure for inter-PCF dormant handoff is used to
servethepurposeof Packet Zoneupdate.
Location Management Strategies
Power-upandpower-downlocationupdate
Time-based
Distance-based
Zone-based
Parameter-based
Orderedupdate
Implicit locationupdate
Handoffs for Supporting Packet Data
Services
Inter-BSCHardHandoff withintheSamePCF
Inter-PCF Hard Handoff within the Same PDSNfor Active
Mobiles
Regular Inter-PDSNHardHandoff for ActiveMobiles
Inter-PCFDormant Handoff withintheSamePDSN
Handoffs in 3GPP2 Network
Handoffs rely heavily on the circuit-switched network
entities.
Handoffs for both circuit-switched and packet-
switchedservicesarecontrolledlargelybytheMSC.
Inter-BSC Hard Handoff within the Same
PCF
InitiatedbythesourceBSCandcontrolledbytheMSC
BSCs and MSC use A1 signaling interface to exchange signaling
messages
Handoff Required: carry, among other information, one or
moretarget radiocellsfor themobiletobehandedoff to
TheMSCwill construct alist of candidatetarget radio cells
basedon:
receivedintheHandoff Requiredmessage
theinformationit maintains
Handoff Request ACK: carry information regarding the
characteristicsof theradiochannelsinthetarget radiocell
Inter-BSC hard handoff in cdma2000 RAN
Inter-PCF Hard Handoff within the Same
PDSN for Active Mobiles
InitiatedbythesourceBSC
Handoff Required: carry information to indicate that the
requested handoff is for packet-switched services and is an
inter-PCFhardhandoff
PDSNIPAddress
Protocol Type: identifies the Link-Layer protocol used at themobileand
itsservingPDSNtoexchangeuser IP packets
A11RegistrationRequest
AsdiscussedinUnit 2, theA11RegistrationRequest usesthesame
format astheMIPv4RegistrationRequest.
Care-of Addressfield: set totheIPaddressof thetarget PCF
HomeAgent field: set totheIPaddressof thePDSN
HomeAddress field: set to zero to indicatethat therequested A10
connectionisfor supportinganintra-PDSNhandoff
3GPP2 intra-PDSN hard handoff for active
mobile
Regular Inter-PDSN Hard Handoff for
Active Mobiles
No P-P interface is implemented between the mobiles serving
PDSNandthetarget PDSN.
Thetarget PCF will havetoselect atarget PDSNfor eachmobile
that isperforminginter-PDSNhandoff.
Howto determinewhich PDSNshould bethetarget PDSNfor amobileis
animplementationissue.
Thetarget PDSN becomes the mobiles new servingPDSN after
thehandoff.
Themobile needs to establish a new PPP connection to thetarget PDSN
duringthehandoff process.
Themobilehas to useanew care-of address after it is handed off to the
target PDSN.
Themobilewill needtoperformMobileIPregistration.
3GPP2 regular inter-PDSN hard handoff for
active mobile
Inter-PCF Dormant Handoff within the
Same PDSN
Initiatedbyamobile
May be performed when the mobile detects a change of the Packet
ZoneID(PZID), NetworkID(NID) or SystemID(SID)
When triggered by a change of PZID, it also serves the purpose of Packet Zone
update.
ThemaintaskistoestablishanewA10connectionbetweenthetarget
PCFandthePDSN.
The A11 Registration Reply message to the target PCF carries an
indicationtoinformthetarget PCF whether thePDSNhasuser datato
sendtothemobileat themoment.
If thePDSNhasnouser datatosendtothemobile: Thetarget PCF will replytothe
target BSCwithanA9-Release-A8Completemessage.
If thePDSN has user datato send to themobile: Thetarget PCF will reply to the
target BSCwithanA9-Connect-A8message.
Assignment Failure: carry aFailureCausevalueindicatingPacket Call
GoingDormant rather thananyreal failure
3GPP2 intra-PDSN dormant handoff
Fast Inter-PDSN Handoff
CanonlybesupportedwhenamobileisinACTIVEstate
The mobiles serving PDSN remains unchanged as long as the
mobilesPacket DataServiceStateremainsinACTIVEstate.
Themobiledoesnot renegotiateitsPPP connection.
3GPP2 Fast inter-PDSN handoff: User
traffic flow
Signaling Flow and User Traffic Flow
A11RegistrationRequest
Home Address field: set to the IP address of the
mobilesservingPDSN
A nonzero HomeAddress field tells thetarget PDSN
that aP-P connectionshouldbeset up.
P-PRegistrationRequest
set the"SimultaneousBindings"flag(i.e.,theSflag)
Care-of Address=IPaddressof thetarget PDSN
HomeAddress=0.0.0.0
Home Agent =IP address of the mobiles serving
PDSN
3GPP2 fast inter-PDSN handoff: signaling
flow and user traffic flow
Enter DORMANT State
When the mobile plans to transition into DORMANT
state, its serving PDSN will have to be changed to the
target PDSNfirst.
As an A10 connection has already been established
between the target PCF/ BSC and the target PDSN
duringthefast inter-PDSNhandoff process, themobile
will only need to establish a PPP connection to the
target PDSNbeforethemobilechangesintoDORMANT
state.
Change Target PDSN
Target PDSN 2 can use the same procedure described
above to establish a P-P connection to the mobiles
servingPDSN.
Themobiles servingPDSNcan bicast user PPP frames
tobothtarget PDSN1andtarget PDSN2.
3GPP2 fast inter-PDSN handoff from target
PDSN 1 to target PDSN 2
Paging and Sending User Data to a
Dormant Mobile
The packet data network is unaware of any paging
processat all.
Paging is carried out by circuit-switched network
entities (i.e., the MSC and the BSC) using the existing
paging protocol and procedures designed for circuit-
switchedservices.
APDSNalwaysforwardstheIP packetsdestinedtoany
dormant or active mobile along the existing PPP
connection and the existing A10 connection for the
mobiletowardthePCF.
Dormant mobiles ensurethat thePDSNknowsits sourcePCF
by performing Packet Zone updates whenever it crosses a
Packet Zoneboundary
Paging Flow
The PCF will issue an A9 Base Station (BS) Service
Request to the last BSC (lets call it BSC 1) to trigger
BSC1toinitiatetheprocesstolocatethemobileandto
allocate all the resources needed for the mobile to
receiveuser packets
The BSC 1 will initiate the BS initiated Mobile-
terminated Call Setup Procedure used in the circuit-
switched portion of the 3GPP2 network to locate the
mobile and to set up the network resources for the
mobile
3GPP2 Paging for packet data services
Mobility Management in MWIF Networks
Use IP-based protocols defined or being developed by the IETF
to support mobility
Main functional entities for mobility management Mobile
Attendant (MA)
Home Mobility Manager (HMM)
Home IP Address Manager
IP Address Manager
Location Server
Geographical Location Manager (GLM)
Global Name Server (GNS)
Service Discovery Server
MWIF recommended IETF protocols for the interface references
point between the mobility management functional entities.
MWIF Mobility Management Functional
Entities and their Interactions
MWIF Handoff Procedure
Comparison of Mobility Management in IP,
3GPP, and 3GPP2 Networks
Similarity:
They all use the Relayed Delivery strategy as the basic
strategyfor deliveringpacketstomobiles.
In particular, amobility anchor point is used for trackingthe
mobileslocationsandfor relayingpacketstomobiles.
Differences
The ways packets are transported from one mobility
protocol entitytoanother.
Regular IP, IP-in-IPtunnel, GTP, GRE, etc.
How location management is related to route
management.
Regular IP routing, host-specificrouting, etc.
Whether andhowpagingissupported.
Simplified mobility management models
used by Mobile IP, Mobile IP Regional
Registration, and SIP mobility
Simplified mobility management models used
in 3GPP, 3GPP2, and IP micro-mobility
management protocols