• UCC cnSGW-C - Release Change Reference
  • About cnSGW
    • 5G Architecture
    • cnSGW-C Overview
    • Deploying and Configuring cnSGW-C through Operations Center
    • Smart Licensing Support
    • cnSGW-C Rolling Software Update
    • Pods and Services Reference
    • 3GPP RAN/NAS Cause Codes Support
    • Access Bearer Release Support
    • APN Profile Support
    • Change Notification Request Handling
    • Clear Subscriber Request
    • Context Replacement Support
    • Dedicated Bearer Support
    • Delete Bearer and Delete Session Request
    • Downlink Data Notification
      • Feature Summary and Revision History
      • Feature Description
      • DDN Message Handling
        • Feature Description
        • How it Works
          • Call Flows
            • Downlink Data Notification Success Call Flow
            • Downlink Data Notification Failure Call Flow
            • No User Connect Retry Timer Call Flow
        • Feature Configuration
      • Control Messages Triggered DDN Support
      • DDN Advance Features
    • DSCP Marking Support
    • Dynamic Routing by Using BGP
    • Emergency Call Support
    • Extended and Non-Standard QCI Values Support and Validation
    • eMPS/WPS Support
    • Failure and Error Handling Support
    • GTPC and Sx Path Management
    • GTPU Error Indication
    • GTPU Path Failure
    • GTPv2 and Sx Messages Retransmission and Timeout Handling
    • GTPv2 Load/Overload Support
    • GTPv2 Message Validation
    • IDFT Support
    • Idle Session Timeout Settings
    • Initial Attach Support
    • Inter System RAT Handover
    • Intra-MME and Inter-MME Handover Procedures
    • MCC/MNC Configuration in the SGW Service
    • Message Interactions Support
    • Modify and Delete Bearer Command Support
    • Modify Bearer Request Support
    • Monitor Subscriber and Protocol Support
    • Multiple PDN Attach or Detach Procedures
    • Performance Optimization Support
    • Presence Reporting Area
    • Redundancy Support
    • Service Configuration Enhancements
    • SGW Charging Support
    • SGW Relocation Support
    • Sx Load/Overload Control Handling
    • Stale Session Handling and Clearing
    • Update Bearer Request and Response
    • UPF Selection Support
    • VoLTE Call Prioritization
    • cnSGW-C Troubleshooting
  • Sample cnSGW Configuration
  • Statistics and KPI Reference

No User Connect Retry Timer Call Flow

This section describes the No User Connect Retry Timer call flow.

No User Connect Retry Timer Call Flow
No User Connect Retry Timer Call Flow Description

Step

Description

1

Received DDN ACK success at the S11-GTP-EP pod.

2

The transaction started while sending the DDN ends here.

S11-GTP-EP sends the DDN ACK success to the SGW-service pod.

3

No User Connect Retry timer is started at the SGW-C pod. This timer is configurable.

SGW-service pod updates the CDL.

4

SGW-service pod sends the DDN Request to the S11-GTP-EP pod, when:

  • The DDN Failure Indication/MBR is not received

  • No User Connect Retry timer expires.

A new transaction S-T1 is created.

5

A new E-T2 transaction is created.

S11-GTP-EP pod forwards the DDN Request to MME.

6

MME sends the DDN Response to the S11-GTP-EP.

7

The transaction E-T2 started at step four is complete.

S11-GTP-EP forwards the DDN Response Success to the SGW-service pod.

8

S-T1 transaction started at step two is completed.

No User Connect Retry timer is started at the SGW-C pod. This timer is configurable.

SGW-service pod updates the CDL.

9

If DDN Failure Indication/MBR is not received, No User Connect Retry expiry triggered.

A new transaction S-T3 is created.

SGW-service pod sends the background IPC request for Sx Modification request to the PFCP-EP pod (DROBU flag and Apply Action as BUFFER).

10

A new transaction P-T4 is created.

PFCP-EP pod sends the Sx Modification Request to the SGW-U pod.

11

PFCP-PE pod receives the Sx Modification Response.

12

The transaction P-T4 started at step nine is complete.

PFCP-EP pod sends the background IPC response to the SGW-service pod.

13

The transaction S-T3 started at step eight is complete.

CDL is updated.

Copyright © 2024, Cisco Systems, Inc. All rights reserved.