Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
ASN Paging Controller and Location Registry Overview
▀ Introduction
▄ Cisco ASR 5000 Series Product Overview
OL-22938-01
Step
Description
4
Upon receipt of the R4 LU_Req message, a relay PC ASN adds the Anchor PC Relocation Destination TLV to initiate PC
relocation to. The message is forwarded to the Anchor PC ASN. New Anchor PC ASN starts timer TR4_LU_Request.
relocation to. The message is forwarded to the Anchor PC ASN. New Anchor PC ASN starts timer TR4_LU_Request.
5
Refer to section 4.13 for the call flow. If the current Anchor PC ASN retains context information for the MS, including its
Authenticator ID, the current Anchor PC ASN initiates a Context Request procedure with the Anchor Authenticator ASN.
If the Anchor Authenticator ASN has valid key material for the MS, it returns AK context for the MS to the Anchor PC
ASN.
Authenticator ID, the current Anchor PC ASN initiates a Context Request procedure with the Anchor Authenticator ASN.
If the Anchor Authenticator ASN has valid key material for the MS, it returns AK context for the MS to the Anchor PC
ASN.
6
The current Anchor PC ASN sends an R4 LU_Rsp message back to the new Anchor PC ASN and starts timer
TR4_LU_Conf. The message includes the MSID, BSID, Authenticator ID, assigned PGID, Paging Offset, Paging Cycle,
Anchor PC ID TLVs, and Location Update Status TLV set to Accept. The Anchor PC Relocation Request Response TLV
is set to Accept to indicate that the Current Anchor PC ASN accepted the PC_Relocation_Req and the Anchor PC ID TLV
is set to the identifier of New Anchor PC ASN ID which was received in the Anchor PC Relocation Destination TLV in the
R4 LU_Req message. The R4 LU_Rsp message also includes MS Info TLV containing MS context for transfer to the new
Anchor PC ASN.If the new Anchor PC ASN does not request PC Relocation, the current Anchor PC MAY still request to
perform the procedure by including the PC Relocation Indication TLV. If the new Anchor PC does not accept the
relocation, it reports a failure in step 17.
TR4_LU_Conf. The message includes the MSID, BSID, Authenticator ID, assigned PGID, Paging Offset, Paging Cycle,
Anchor PC ID TLVs, and Location Update Status TLV set to Accept. The Anchor PC Relocation Request Response TLV
is set to Accept to indicate that the Current Anchor PC ASN accepted the PC_Relocation_Req and the Anchor PC ID TLV
is set to the identifier of New Anchor PC ASN ID which was received in the Anchor PC Relocation Destination TLV in the
R4 LU_Req message. The R4 LU_Rsp message also includes MS Info TLV containing MS context for transfer to the new
Anchor PC ASN.If the new Anchor PC ASN does not request PC Relocation, the current Anchor PC MAY still request to
perform the procedure by including the PC Relocation Indication TLV. If the new Anchor PC does not accept the
relocation, it reports a failure in step 17.
7
Upon receipt of the R4 LU_Rsp message from current Anchor PC ASN, new Anchor PC ASN stops timer TR4_LU_Req,
stores the MS context received from current Anchor PC ASN, updates the Paging Information (Paging Group ID, Paging
Cycle, Paging Offset), forwards the R4 LU_Rsp message on to the Serving ASN, and starts timerTR4_LU_Conf.
stores the MS context received from current Anchor PC ASN, updates the Paging Information (Paging Group ID, Paging
Cycle, Paging Offset), forwards the R4 LU_Rsp message on to the Serving ASN, and starts timerTR4_LU_Conf.
8
Upon receipt of the R4 LU_Rsp message, the Serving ASN-GW stops timer TR4_LU_Req, sends an R6 LU_Rsp message
to the S-BS, and starts timerTR6_LU_Conf. The message includes the Location Update Status TLV set to Accept, MS Info,
AK Context, Anchor PC ID, and old Anchor PC ID TLV. The message may include the paging Information TLV if they
were included in the corresponding R4 message.
to the S-BS, and starts timerTR6_LU_Conf. The message includes the Location Update Status TLV set to Accept, MS Info,
AK Context, Anchor PC ID, and old Anchor PC ID TLV. The message may include the paging Information TLV if they
were included in the corresponding R4 message.
9
Based on the AK and AK context received from the current Anchor PC, the Serving BS (associated with Local PC/Relay
PC) successfully authenticates the RNG_REQ message received from the MS. The serving BS sends a RNG_RSP message
with HMAC/CMAC and Successful Location Update Response indication to the MS.
PC) successfully authenticates the RNG_REQ message received from the MS. The serving BS sends a RNG_RSP message
with HMAC/CMAC and Successful Location Update Response indication to the MS.
10
The Serving BS sends an R6 LU_Cnf message to the serving ASN-GW with Location Update TLV indicating success.
Upon receipt of the message, the serving ASN-GW stops timer TR6_LU_Conf.
Upon receipt of the message, the serving ASN-GW stops timer TR6_LU_Conf.
11
The Serving ASN sends an R4 LU_Cnf message with a successful LU indication to new Anchor PC ASN (as indicated by
the Anchor PC ID received from the BS) and stops timer TR6_LU_Req. Alternatively, the Relay PC ASN forwards
LU_Cnf to the ASN associated with new Anchor PC with the result indication reassigned by Relay PC. Upon receipt of the
message, new Anchor PC ASN stops timer TR4_LU_Conf.
the Anchor PC ID received from the BS) and stops timer TR6_LU_Req. Alternatively, the Relay PC ASN forwards
LU_Cnf to the ASN associated with new Anchor PC with the result indication reassigned by Relay PC. Upon receipt of the
message, new Anchor PC ASN stops timer TR4_LU_Conf.
12
Upon receipt of the LU_Cnf message, the new Anchor PC ASN sends an R4 PC_Relocation_Ind to the Anchor DP/FA
ASN, and starts timer TR4_PC_Reloc_Upd_ADP.
ASN, and starts timer TR4_PC_Reloc_Upd_ADP.
13
The Anchor DP/FA ASN updates the Anchor PC for the MS with the new Anchor PC ASN ID and responds with an R4
PC_Relocation_Ack message confirming the Anchor PC update. Upon receipt of the message, the new Anchor PC ASN
stops timer TR4_PC_Reloc_Upd_ADP. The new Anchor PC ASN hosts the Anchor PC function and becomes the new
current Anchor PC ASN for the MS. The Anchor PC is de-allocated from the old current Anchor PC ASN.
PC_Relocation_Ack message confirming the Anchor PC update. Upon receipt of the message, the new Anchor PC ASN
stops timer TR4_PC_Reloc_Upd_ADP. The new Anchor PC ASN hosts the Anchor PC function and becomes the new
current Anchor PC ASN for the MS. The Anchor PC is de-allocated from the old current Anchor PC ASN.
14
Simultaneous with sending PC_Relocation_Ind to Anchor DP/FA, the new Anchor PC sends an R4 PC Relocation
Indication to Anchor Authenticator ASN to inform the change of the Anchor PC, and starts timer TR4-
PC_Reloc_Upd_AA.
Indication to Anchor Authenticator ASN to inform the change of the Anchor PC, and starts timer TR4-
PC_Reloc_Upd_AA.
15
The Anchor Authenticator ASN updates the Anchor PC for the MS with the New Anchor PC ASN ID and responds with an
R4 PC_Relocation_Ack message confirming the Anchor PC update. Upon receipt of the message, the New Anchor PC
ASN stops timer TR4-PC_Reloc_Upd_AA. At this point, New Anchor PC ASN hosts the Anchor PC function and
becomes the new Current Anchor PC ASN for the MS. The Anchor PC is de-allocated from the old Current Anchor PC
ASN.
R4 PC_Relocation_Ack message confirming the Anchor PC update. Upon receipt of the message, the New Anchor PC
ASN stops timer TR4-PC_Reloc_Upd_AA. At this point, New Anchor PC ASN hosts the Anchor PC function and
becomes the new Current Anchor PC ASN for the MS. The Anchor PC is de-allocated from the old Current Anchor PC
ASN.