Controlling Notify-Request during Inter-RAT TAU/HO
Transcript of Controlling Notify-Request during Inter-RAT TAU/HO
Controlling Notify-Request during Inter-RATTAU/HO
This chapter describes the following topics:
• Feature Summary and Revision History, on page 1• Feature Changes, on page 2• Command Changes, on page 2• Performance Indicator Changes, on page 3
Feature Summary and Revision HistorySummary Data
MMEApplicable Product(s) or FunctionalArea
• ASR 5500
• VPC-DI
• VPC-SI
Applicable Platform(s)
Disabled – Configuration RequiredFeature Default
Not applicableRelated Changes in This Release
• Command Line Interface Reference
• MME Administration Guide
Related Documentation
Revision History
Revision history details are not provided for features introduced before releases 21.2 and N5.1.Important
Controlling Notify-Request during Inter-RAT TAU/HO1
ReleaseRevision Details
21.3 and later releasesIn this release, sending the Notify-Request during 3G to 4G TAU or HO can becontrolled using the new tau inter-rat notify-request CLI command introduced inthe Call Control Profile Configuration mode.
Pre 21.2First introduced.
Feature ChangesIn this release, sending the Notify-Request during 3G to 4G Tracking Area Update (TAU) or handover (HO)can be optionally controlled. A new CLI command tau inter-rat notify-request introduced in the Call ControlProfile configuration mode enables MME to send the Notify-Request.
Previous Behavior:When UE does a TAU/HO from peer MME/SGSN, the GGSN/P-GW IP address givenby the peer node in context response was compared with the MIP6-IP-Address given by the HSS in UpdateLocation Answer (ULA) message. If these two IP addresses are different, then MME used to send theNotify-Request after receiving ULA. This behavior was not dependent on any configuration.
New Behavior:When UE does a TAU/HO from peer MME/SGSN, and the GGSN/P-GW IP address givenby the peer node in context response andMIP6-IP-Address given by the HSS in ULA are different, thenMMEwill not send the Notify-Request. A new CLI command tau inter-rat notify-request is added in the CallControl Profile Configuration mode to control sending the Notify-Request. By default, MME will not sendthe Notify-Request in the above-mentioned scenario.
e3kj
The diameter suppress notify-request CLI command under HSS Peer Service has higher priority than thetau inter-rat notify-request CLI command under Call Control Profile.
Important
Command Changes
tau inter-ratIn the Call Control Profile Configuration mode, the tau inter-rat command has been enhanced to enablesending the Notify-Request to HSS during inter-RAT TAU/HO.
configurecall-control-profile profile_name
[ remove ] tau inter-rat notify-requestend
Notes:
• The tau inter-rat notify-request command is disabled by default.
• The remove tau inter-rat notify-request command disables sending the Notify-Request during inter-RATTAU/HO.
Controlling Notify-Request during Inter-RAT TAU/HO2
Controlling Notify-Request during Inter-RAT TAU/HOFeature Changes
Performance Indicator Changes
show configuration verboseThe default output of this command is:
call-control-profile cc1remove tau inter-rat notify-request
The output of this command when notify-request is enabled:
call-control-profile cc1tau inter-rat notify-request
Controlling Notify-Request during Inter-RAT TAU/HO3
Controlling Notify-Request during Inter-RAT TAU/HOPerformance Indicator Changes
Controlling Notify-Request during Inter-RAT TAU/HO4
Controlling Notify-Request during Inter-RAT TAU/HOshow configuration verbose