Cisco Cisco ASR 5500 トラブルシューティングガイド
ASR 5x00 Series SGSN Authentication and PTMSI
Reallocation Best Practices
Reallocation Best Practices
Document ID: 119148
Contributed by Krishna Kishore DV, Sujin Anagani, and Parthasarathy
M, Cisco TAC Engineers.
M, Cisco TAC Engineers.
Jun 12, 2015
Contents
Introduction
Overview
SGSN Authentication and PTMSI Signature Procedure Blocks
Why Authentication and PTMSI Signature Reallocation is Required
Problem
Stabilization Approach
Fix Plan
Configuration Guidelines
Troubleshoot
Risks
Command Syntax
Overview
SGSN Authentication and PTMSI Signature Procedure Blocks
Why Authentication and PTMSI Signature Reallocation is Required
Problem
Stabilization Approach
Fix Plan
Configuration Guidelines
Troubleshoot
Risks
Command Syntax
Introduction
This document provides a basic explanation of the benefits of the authentication procedure frequency
configuration, Packet Temporary Mobile Subscriber Identity (PTMSI), and PTMSI signature reallocation.
Specifically, this document is for an optional third−generation Partnership Project mobility management
procedure for 2G and 3G on Serving GPRS Support Node (SGSN) that runs on Aggregated Service Router
(ASR) 5000 Series.
configuration, Packet Temporary Mobile Subscriber Identity (PTMSI), and PTMSI signature reallocation.
Specifically, this document is for an optional third−generation Partnership Project mobility management
procedure for 2G and 3G on Serving GPRS Support Node (SGSN) that runs on Aggregated Service Router
(ASR) 5000 Series.
This document explains these best practices:
Authentication frequency setting
•
PTMSI reallocation
•
PTMSI signature reallocation
•
The impact if you do not configure the authentication frequency setting and the PTMSI reallocation
and signature reallocation (based on experience from customer cases)
and signature reallocation (based on experience from customer cases)
•
Configuration guidelines and the impact on external interfaces
•
Options to troubleshoot issues
•
Overview
The authentication, PTMSI, and PTMSI signature reallocation framework under the call control profile
enables the operator to configure authentication or allocation of the PTMSI and PTMSI signature per
subscriber in the 2G and 3G SGSN and the Mobile Management Entity (MME). In the SGSN, authentication
can currently be configured for these procedures − attach, service−request, routing−area−update (RAU),
short−messaging−service, and detach.
enables the operator to configure authentication or allocation of the PTMSI and PTMSI signature per
subscriber in the 2G and 3G SGSN and the Mobile Management Entity (MME). In the SGSN, authentication
can currently be configured for these procedures − attach, service−request, routing−area−update (RAU),
short−messaging−service, and detach.