IMPORTANT:
Feature Description
How It Works
Establishment of Direct Tunnel
Direct Tunnel Activation for Primary PDP Context
Direct Tunnel Activation for UE Initiated Secondary PDP Context
RAB Release with Direct Tunnel
IMPORTANT:
Iu Release with Direct Tunnel
IMPORTANT:
Service Request with Direct Tunnel
Downlink Data Notification with Direct Tunnel when UE in Connected State
Downlink Data Notification with Direct Tunnel when UE in Idle State
Intra SGSN Routing Area Update without SGW Change
| Scenario | Old RNC Status | Old RNC RAB | Old RNC DT Status | PLMN Change | NEW RNC DT Status | S-GW Change | SGSN Action |
|---|---|---|---|---|---|---|---|
| Intra RAU | Not Present | No RAB | Supported | No | Supported | No | No RAB establishment with new RNC. No Modify Bearer Request to S-GW |
| Intra RAU | Present | No RAB | Supported | No | Supported | No | No RAB establishment with new RNC. No Modify Bearer Request to S-GW |
| Intra RAU | Present | Some RABs | Supported | Do not care | Supported | No | Only the present RABs are established. MBR sent to S-GW with the bearers with RABs that are be modified and the rest released. The bearers without RABs will be deactivated post RAU. If PLMN changed then MBR will carry the new PLMN ID. |
| Intra RAU | Not Present | No RAB | Supported | Yes | Supported | No | No RAB establishment with new RNC. MBR is sent with only PLMN change. Bearer Context will not carry any TEID. |
| Intra RAU | Present | No RAB | Supported | Yes | Supported | No | Same as above. |
| Intra RAU | Not Present | No RAB | Not Supported | No | Supported | No | No RAB establishment with new RNC. Modify Bearer Request to S-GW with DTF set and no user FTEID. |
| Intra RAU | Present | No RAB | Not Supported | No | Supported | No | Same as above. |
| Intra RAU | Present | Some RABs | Not Supported | Do not care | Supported | No | Only the present RABs are established. MBR sent to S-GW with the bearers with RABs to be modified and the rest to be released. The bearers without RABs will be deactivated post RAU. If PLMN changed then MBR will carry the new PLMN ID.Modify Bearer. |
| Intra RAU | Not Present | No RAB | Not Supported | Yes | Supported | No | No RAB establishment with new RNC. MBR is sent with only PLMN change. SGSN will page / Service req / establish RABs when a downlink data notification is received. |
| Intra RAU | Present | No RAB | Not Supported | Yes | Supported | No | Same as above. |
| Intra RAU: New RNC does not support Direct Tunnel. No SGW relocation | |||||||
| Intra RAU | Not Present | No RAB | Supported | Do not care | Not Supported | No | No RAB establishment with new RNC. SGSN sends Modify Bearer Request to S-GW with S4U TEID. If there is change in PLMN ID, then new PLMN ID will be carried. |
| Intra RAU | Present | No RAB | Supported | Do not care | No Supported | No | Same as above. |
| Intra RAU | Present | Some RABs | Supported | Do not care | Not supported | No | Only the present RABs are established. MBR sent to S-GW with all bearers having S4U TEID. If there is change in PLMN ID, the new PLMN ID will be carried. |
Routing Area Update with S-GW Change
| Scenario | Old RNC Status | Old RNC RAB | Old RNC DT Status | PLMN Change | NEW RNC DT Status | S-GW Change | SGSN Action |
|---|---|---|---|---|---|---|---|
| Intra RAU: Both RNCs support Direct Tunnel. SGW relocation | |||||||
| Intra RAU | Not Present | No RAB | Supported | Do not care | Supported | Yes | Send CSR request to new S-GW with DTF flag but no S4U / S12U FTEID. S-GW will send its S12U TEID that SGSN stores as part of DP's remote TEID. SGSN will not initiate any MBR request to S-GW since no RABs are established with new RNC. If S-GW subsequently gets downlink data, SGSN will get DDN and establish RABs and send MBR. |
| Intra RAU | Present | No RAB | Supported | Do not care | Supported | Yes | Same as above. |
| Intra RAU | Present | Some RABs | Supported | Do not care | Supported | Yes | Send CSR request to new S-GW with DTF flag but no S4U / S12U FTEID. S-GW sends its S12U TEID. RABs that are present will be established with new RNC. MBR will be initiated only with those RABs that are present; rest of bearers to be removed. |
| Intra RAU: Old RNC does not support Direct Tunnel. SGW relocation | |||||||
| Intra RAU | Not Present | No RAB | Not Supported | Do not care | Supported | Yes | Send CSR request to new S-GW with DTF flag but no S4U / S12U FTEID. S-GW sends its S12U TEID that SGSN stores as part of our DP's remote TEID. SGSN will not initiate any MBR request to S-GW since no RABs are established with new RNC. If S-GW subsequently gets downlink data, SGSN gets DDN and establishes RABs and sends MBR. |
| Intra RAU | present | No RAB | Not Supported | Do not care | Supported | Yes | Same as above. |
| Intra RAU | Present | Some RABs | Not SUpported | Do not care | Supported | Yes | Send CSR request to new S-GW with DTF flag but no S4U / S12U FTEID. S-GW sends its S12U TEID. RABs that are present will be established with new RNC and MBR will be initiated only with those RABs that are present and the rest as bearers to be removed. |
| Intra RAU: New RNC does not support Direct Tunnel. SGW relocation | |||||||
| Intra RAU | Not Present | No RAB | Supported | Do not care | Not Supported | Yes | CSR request without DTF flag and with S4U FTEID. |
| Intra RAU | Present | No RAB | Supported | Do not care | Not Supported | Yes | CSR request without DTF flag and with S4U FTEID. |
| Intra RAU | Present | Some rABs | Supported | Do not care | Not Supported | Yes | CSR request without DTF flag and with S4U FTEID. No deactivation of PDPs. |
Intra SRNS with S-GW Change
Intra SRNS without S-GW Change
| Old RNC DT Status | New RNC DT Status | S-GW Relocation | Behavior |
|---|---|---|---|
| Supported | Supported | No | Relocation Request to Target RNC is sent with S-GW S12 U FTEID. Modify Bearer Request to S-GW is sent with RNC S12 U FTEID. |
| Supported | Not Supported | No | Relocation Request to Target RNC is sent with SGSN S4 U FTEID. Modify Bearer Request to S-GW is sent with SGSN S4 U FTEID |
| Not Supported | Supported | No | Relocation Request to Target RNC is sent with S-GW S12U FTEID. Modify Bearer Request to S-GW is sent with RNC S12 U FTEID. |
| Not Supported | Supported | Yes | Create Session Request to new S-GW is sent with DTF flag set and no user plane FTEID. Even if S-GW sent S4U FTEID in CSR Response SGSN internally treats that as an S12U FTEID and continues the relocation. Relocation Request to Target RNC is sent with S12 U FTEID received in Create Session Response. Modify Bearer Request to new S-GW is sent with RNC S12U FTEID |
| Supported | Not Supported | Yes | Create Session Request to new SGW is sent with S4 U FTEID. Relocation Request to Target RNC is sent with SGSN U FTEID.Modify Bearer Request is sent with SGSN S4U FTEID. |
| Supported | Supported | Yes | SGSN sends a Create Session Request to new SGW with DTF flag set and no user plane FTEID.Even if S-GW sent S4U FTEID in CSR Response, SGSN will internally treat that as S12U FTEID and continue the relocation. Relocation Request to the Target RNC is sent with the S12 U FTEID received in the Create Session Response. Modify Bearer Request to new S-GW is sent with RNC U FTEID. |
New SRNS with S-GW Change and Direct Data Transfer
New SRNS with S-GW Change and Indirect Data Transfer
| Target RNC DT Status | Direct Forwarding | S-GW Relocation | Behavior |
|---|---|---|---|
| Supported | No | No | Relocation Request with SGW S12U FTEID received in Forward Relocation Request. SGSN includes RNC U FTEID in Forward Relocation Response. RNC U FTEID is also sent in Modify Bearer Request with DTF flag set. |
| Supported | Yes | No | Relocation Request with SGW S12U FTEID received in Forward Relocation Request. In Forward Relocation Response RNC U FTEID is included. And in Modify Bearer Request RNC U FTEID is sent and DTF flag is set. |
| Supported | No | Yes | Create Session Request with DTF flag set and no user plane FTEID. Relocation Request is sent is SGW S12U FTEID received in Create Session Response. Even if SGW sent S4U FTEID in CSR Response we will internally treat that as S12U FTEID and continue the relocation. Create Indirect Data Forwarding Tunnel Request is sent with RNC FTEID received in Relocation Request Acknowledge.In Forward Relocation Response SGW DL U FTEID received in Create IDFT response is sent. Modify Bearer Request is send with DTF set and RNC U FTEID. |
| Supported | Yes | Yes | Create Session Request with DTF flag set and no user plane FTEID. Relocation Request is sent with SGW S12U FTEID received in Create Session Response. Even if SGW sent S4U FTEID in CSR Response we will internally treat that as S12U FTEID and continue the relocation. In Forward Relocation Response RNC FTEID is sent and Modify Bearer Request is sent with DTF flag set and RNC U FTEID |
Old SRNS with Direct Data Transfer
Old SRNS with Indirect Data Transfer
| Source RNC DT Status | Direct Forwarding | S-GW Relocation | Behavior |
|---|---|---|---|
| Supported | No | No | Forward Relocation Request is send with SGW S12 U FTEID. If peer is MME, IDFT is applied. Then a Create Indirect Data Forwarding Tunnel Request is sent with User plane FTEID received in the Forward Relocation Response. This will be the eNB user plane FTEID. The SGW DL forwarding user plane FTEID received in the Create Indirect Data Forwarding Tunnel Response is sent in the Relocation Command. |
| Supported | Yes | No | Forward Relocation Request is sent with SGW S12 U FTEID. The eNB / RNC user plane FTEID received in the Forward Relocation Response is sent in the Relocation Command. |
| Supported | No | Yes | Forward Relocation Request is sent with SGW S12 U FTEID. If peer is MME, IDFT is applied. Then Create Indirect Data Forwarding Tunnel Request is sent with eNB User plane FTEID received in the Forward Relocation Response. The SGW DL forwarding user plane FTEID received in the Create Indirect Data Forwarding Tunnel Response is sent in the Relocation Command. |
| Supported | Yes | Yes | Forward Relocation Request is sent with SGW S12 U FTEID. The eNB / RNC use plane FTEID received in the Forward Relocation Response is sent in the Relocation Command. |
Network Initiated Secondary PDP Context Activation
PGW Init Modification when UE is Idle
Limitations
Standards Compliance
Configuring Direct Tunnel on an S4-SGSN
Enabling Direct Tunnel to RNCs
Verifying the Call-Control Profile Configuration
show call-control-profile
full name <profile_name>
Call Control Profile
Name = ccprofile1
...
Re-Authentication : Disabled
Direct Tunnel : Not Restricted
GTPU Fast Path : Disabled
..
Verifying the RNC Configuration
show iups-service
name <service_name>
IService name : iups1
...
Available RNC:
Rnc-Id : 1
Direct
Tunnel : Not Restricted
Monitoring and Troubleshooting Direct Tunnel
show subscribers sgsn-only
show gmm-sm statistics sm-only
show gmm-sm
statistics sm-only
Activate PDP Contexts:
Total Actv PDP Ctx:
3G-Actv
Pdp Ctx: 1 2G-Avtv Pdp Ctx: 0
Gn Interface: 1 Gn Interface: 0
S4 Interface: 1 S4 Interface: 0
Total Actv Pdp Ctx:
with Direct Tunnel: 1
Direct Tunnel Bulk Statistics