- About this Guide
- Overview
- Configuring Control Plane in CUPS
- Monitoring and Troubleshooting Control Plane in CUPS
- 5G NSA for SAEGW in CUPS
- ADC Over Gx
- Addition of IP Pool in IP Group
- APN ACL Support
- APN AMBR Traffic Policing
- APN Data Tunnel MTU Size Configuration
- APN and APN Profile-Based User Plane Selection for CUPS
- Bearer Inactivity Timeout
- Bulk Statistics Support
- Cisco Ultra Traffic Optimization with VPP
- Change Notification Support for Pure S
- Charging Action Configuration Change Support for Existing Sessions Gy and Gz Interface
- CP Call Summary Log
- Dedicated Bearer Establishment without PCRF
- EDNS Support
- Disable Radius Accounting
- DSCP Markings For Collapse Calls
- Dynamic and ADC Charging Rule Names
- Dynamic APN and IP Pool Support
- Dynamic User Plane Selection
- ECS Regular Expression Support
- End Marker Packets
- Enterprise Onboarding in CUPS
- Event-based CDRs for CUPS
- Event Data Records in CUPS
- Error Indication and GTPU Path Failure Detection
- Firewall Support in CUPS
- GGSN in CUPS
- Gx-alias Enhancement
- FUI Redirection
- ICSR Bulk Statistics
- Idle Timer for SAE-GW Sessions
- IFTASK Hyperthreading
- Indirect Forwarding Tunnel
- IP Pool Management
- IPSec in CUPS
- L2 Marking Support
- L3, L4, and L7 Rule Combination in Ruledef
- Local Policy in CUPS
- Load/Overload and UP Data Throttling Support on Sx
- LTE - Wi-Fi Seamless Handover in CUPS
- Monitor Subscriber for CUPS
- MPLS Support on VPC-SI for CUPS
- Multiple Control Plane Support on User Plane
- Multiple UP Group Support
- MOCN Special Handling of CRA and CNR
- NAT Support
- NAT ALG Support
- Netloc and RAN/NAS Cause Code
- Network Trigerred Service Restoration
- Network Provided Location Indication
- Nexthop Forwarding Support IPv4/v6 Address
- NSO-based Configuration Management
- NSO Orchestration for 4G CUPS
- NSH Traffic Steering
- PDI Optimization
- P-GW CDR in CUPS
- P-GW Restart Notification
- Post Processing Interaction for DCCA
- Priority Recovery Support for VoLTE Calls
- QoS Group of Ruledefs Support
- RADIUS in C-Plane
- RADIUS Server State
- Rate Limiting Function (RLF)
- S2a Interface Support
- S2b Interface Support
- S6b Support
- S-GW CDR in CUPS
- S-GW New Call Rejection
- SAEGW Idle Buffering with DDN Delay and DDN Throttling
- Secondary RAT Usage During GnGp Handover
- Self-overload Detection and Admission Control of Sx at UP
- Smart Licensing
- Software Management Operations
- Standard QCI Support
- Static IP Assignment from RADIUS
- Support for Duplicate New Call
- Suspend and Resume Notification for Pure-S Calls
- TACACS+ Over IPSec
- Tariff Time Support
- URL Blacklisting
- User Plane Node Bring Down Procedure
- User Plane Selection based on TAC Range
- Virtual APN in CUPS
- VoLTE Support in CUPS
- Volume Reporting over Gx
- VPP Support
- VRF Support for CUPS
- X-Header Insertion and Encryption
Bearer Inactivity Timeout
Revision History
Note |
Revision history details are not provided for features introduced before release 21.24. |
Revision Details |
Release |
---|---|
First introduced |
Pre 21.24 |
Feature Description
Bearer inactivity timeout feature in CUPS enables the deletion of bearers that utilizes less data traffic than the configured threshold value, by monitoring the activity on the respective bearer. This allows for more efficient use of radio resources. The configuration of bearer inactivity timer and the threshold value of the traffic is done under APN configuration mode for P-GW, and APN Profile configuration mode for S-GW. The bearer inactivity timer can also be configured to exclude the default-bearer/primary-bearer from monitoring the bearer inactivity.
The Control Plane in CUPS supports the following bearer inactivity timer configuration options:
-
timeout bearer-inactivity [ gbr | non-gbr ] dur_seconds volume-threshold { downlink | total | uplink } bytes
-
timeout bearer-inactivity exclude-default-bearer
Based on the bearer inactivity configuration, a new bearer-level URR is created and associated with every PDR that is created for a bearer. When the timer expiry is detected, the User Plane monitors if the intended volume threshold is reached for the bearer, and sends a session usage report if bearer inactivity is detected. The Control Plane, after receiving the usage report, initiates the deletion of the respective bearer with disconnect reason set as "Bearer Inactivity Timeout".