3G Direct Tunnel Configuration

OPERATION DIRECTIONS

1/1543-AXB 250 05/8 Uen AY

Copyright

© Ericsson AB 2008–2015. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing. Ericsson
shall have no liability for any errors or damage of any kind resulting from the
use of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Contents

Contents

1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1

2 Prerequisites 1
2.1 Planning 2
2.2 User 2
2.3 Equipment 3

3 Configuring 3GDT 3
3.1 Configuring the RNC 4
3.2 Configuring the S12 Interface Capability of SGWs 5
3.3 Configuring 3GDT for UE Not in the HPLMN 5
3.4 Configuring the 3GDT Prefix 5
3.5 Configuring the DtGgsnList 6
3.6 Configuring the DtApnList and the DtTacList 7
3.7 Configuring the 3GDT Decision Method for GGSNs 8
3.8 Configuring the 3GDT Decision Method for UE 8
3.9 Configuring 3GDT for the Default APN 10
3.10 Configuring the 3GDT Decision Method Based on Service
Request Frequency 10
3.11 Configuring the DNS 11
3.12 Configuring the HLR 11
3.13 Activating 3GDT 12
3.14 Verifying the SGSN-MME Operation 12
3.15 Checkpointing the Configuration 13

4 Supplementary Configuration 13
4.1 Deactivating 3GDT 13
4.2 Enabling and Disabling 3GDT Support Check 13

5 Examples for Configuring 3GDT 14

5.1 Configuring the RNC 15
5.2 Configuring the S12 Interface Capability of SGWs 15
5.3 Configuring 3GDT for UE Not in the HPLMN 15

1/1543-AXB 250 05/8 Uen AY | 2015-11-20

3G Direct Tunnel Configuration

5.4 Configuring the 3GDT Prefix 15

5.5 Configuring the DtGgsnList 15
5.6 Configuring the DtApnList and the DtTacList 16
5.7 Configuring the 3GDT Decision Method for GGSNs 16
5.8 Configuring the 3GDT Decision Method for UE 17
5.9 Configuring 3GDT for the Default APN 17
5.10 Configuring the 3GDT Based on Service Request
Frequency 18
5.11 Configuring the DNS 18
5.12 Configuring the HLR 18
5.13 Activating 3GDT 19

1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Prerequisites

1 Introduction

This document describes how to configure 3G Direct Tunnel (3GDT) on the

SGSN-MME for WCDMA Systems. The optional configuration of DNS and
HLR is also included.

For information about 3GDT, see 3G Direct Tunnel.

1.1 Scope
This document covers the following topics:

• Available operations

• Configuration examples

• Configuration Prerequisites

• Configuration procedures for activating and deactivating 3GDT

• A flowchart describing the configuration in sequence

Note: The detailed configuration of the DNS, the HLR, and the GPRS
backbone network is not covered in this document.

For information about the parameters configured in this document, see

Parameter Description.

This document does not cover installation of the SGSN-MME, which must be
performed by the site installation engineers.

1.2 Target Groups

This document is intended for personnel performing configuration of 3GDT in
the SGSN-MME.

2 Prerequisites

This section outlines the prerequisites for the configuration.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 1

 3G Direct Tunnel Configuration

2.1 Planning
In the planning phase of the configuration, the following requirements must be
fulfilled:

• The GPRS backbone network supports 3GDT.

• The RNC, GGSN, and Access Point Names (APNs) are 3GDT compliant.

• For an SGSN-MME using the Gn interface, the following information

specifying the 3GDT compliant UE and GGSNs must be available:

0 Optionally, the 3GDT prefix considered for the configuration of the

DNS, the SGSN-MME, and the HLR.

Note: The 3GDT prefix configuration must be identical in all network

elements. The prefix is case sensitive.

If a 3GDT APN prefix is used, the SGSN default APN cannot

be configured with the prefix.

0 Optionally, the list of 3GDT compliant GGSNs (DtGgsnList).

Note: When using the GGSN IP address list, the 3GDT prefix is not
needed in the subsequent DNS query and in the DNS server.

0 Optionally, the list of 3GDT enabled APNs or 3GDT disabled APNs

(DtApnList).

0 Optionally, the list of 3GDT enabled Type Allocation Codes (TACs) or

3GDT disabled TACs (DtTacList).

• For an SGSN-MME using the S4 interface, the following information

specifying the 3GDT compliant UE must be available:

0 Optionally, the list of 3GDT enabled APNs or 3GDT disabled APNs

(DtApnList).

0 Optionally, the list of 3GDT enabled TACs or 3GDT disabled TACs

(DtTacList).

• The license-key file containing the license for the 3GDT feature is loaded.
For more information, see Installing Licenses.

2.2 User
The person performing configuration and planning must have a solid
understanding in the following areas:

• How to work in UNIX®

• GPRS communication in the WCDMA Systems

2 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Configuring 3GDT

• Operation of the DNS, the HLR, and the SGSN-MME

2.3 Equipment
To preform 3GDT procedures, use the equipment for configuring the DNS
and the HLR.

3 Configuring 3GDT

For a flowchart on how to configure 3GDT, see Figure 1.

To display the configuration classes and parameters related to 3GDT, use the
get_config_area -can 3GDirectTunnel CLI command.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 3

 3G Direct Tunnel Configuration

Configuring 3GDT for the SGSN- Configuring 3GDT for the SGSN-
MME using the Gn interface MME using the S4 interface
START START

Configuring the RNC Configuring the RNC

Configuring the 3GDT Prefix Configuring the S12 Interface

Capability of SGWs

Configuring the DtGgsnList Configuring 3GDT for

UE Not in the HPLMN

Configuring the DtApnList Configuring the DtApnList

and the DtTacList and the DtTacList

Configuring the 3GDT

Decision Method for GGSNs

Configuring the 3GDT Configuring the 3GDT

Decision Method for UE Decision Method for UE

Configuring 3GDT for

the Default APN

Configuring the 3GDT Configuring the 3GDT

Decision Method Based on Decision Method Based on
Service Request Frequency Service Request Frequency

Configuring the DNS

Configuring the HLR

Activating 3GDT Activating 3GDT

Verifying the Verifying the

SGSN-MME Operation SGSN-MME Operation

Checkpointing the Configuration Checkpointing the SC

3GDT Configuration 3GDT Configuration

COMPLETED COMPLETED
Figure 1 The 3GDT Configuration Flowchart

3.1 Configuring the RNC

Configure the 3GDT compliant RNCs in the SGSN-MME.

Instructions

1. Specify that an RNC is 3GDT compliant by using the modify_rnc CLI

command.

For an example, see Section 5.1 on page 14.

4 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Configuring 3GDT

3.2 Configuring the S12 Interface Capability of SGWs

Configuring the DtSgwS12Supported parameter specifies whether the S12
interface is supported by SGWs.

The default value of this parameter is true, which means that SGWs support
the S12 interface.

Note: This configuration is valid only for the SGSN-MME using the S4
interface.

Instructions

1. Configure the DtSgwS12Supported parameter by using the modify_dt

CLI command.

For an example, see Section 5.2 on page 15.

3.3 Configuring 3GDT for UE Not in the HPLMN

Configuring the DtS4VplmnAllowed parameter specifies whether the direct
tunnel is supported for UE not in the Home PLMN (HPLMN).

The default value of this parameter is true, which means the direct tunnel is
supported for UE not in the HPLMN.

Note: This configuration is valid only for the SGSN-MME using the S4
interface.

Instructions

1. Configure the DtS4VplmnAllowed parameter by using the modify_dt

CLI command.

For an example, see Section 5.3 on page 15.

3.4 Configuring the 3GDT Prefix

When using the 3GDT prefix, set the prefix in the SGSN-MME to specify the
3GDT compliant UE and GGSNs. The 3GDT prefix identifies the subscriber per
APN combination in the HLR and 3GDT compliant GGSN per APN combination
in the DNS , see Section 3.11 on page 11 and Section 3.12 on page 11.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 5

 3G Direct Tunnel Configuration

Note:

• If a 3GDT APN prefix is used, the SGSN default APN cannot be

configured with the prefix.

• To decrease the number of DNS entries in the DNS server, use the
GGSN IP address list in the SGSG-MME to decide if the GGSN
is 3GDT compliant. This means the same DNS query is used
whether 3GDT is used or not. To decrease the number of entries
in the HLR, use the APN list and the TAC list in the SGSN-MME
to determine whether 3GDT is allowed for a given subscriber per
APN combination.

• This configuration is valid only for the SGSN-MME using the Gn

interface.

Instructions

1. Set the DtPrefix parameter by using the modify_dt CLI command.

For an example, see Section 5.4 on page 15.

3.5 Configuring the DtGgsnList

Configuring the DtGgsnList is an alternative method for selecting 3GDT
compliant GGSNs comparing with the DNS configuration, see Section 3.7 on
page 8.

The DtGgsnList is a list configured in the SGSN-MME where the 3GDT

compliant GGSN IP addresses are defined. By using the list, the 3GDT
configuration in the DNS server is not necessary. If some of the IP addresses
in the DNS match those of the DtGgsnList, the SGSN-MME selects them as
3GDT candidates and uses one of them when setting up 3GDT connections
for the PDP context.

Note:

• Configure all control plane IP addresses for each 3GDT compliant

GGSN.

• This configuration is valid only for the SGSN-MME using the Gn

interface.

Instructions

If using the DtGgsnList method, follow the step below:

1. Configure the DtGgsnList by using the create_dt_ggsn_address and the

delete_dt_ggsn_address CLI commands.

For an example, see Section 5.5 on page 15.

6 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Configuring 3GDT

3.6 Configuring the DtApnList and the DtTacList

The DtApnList method, the DtTacList method, the HLR configuration, or
a combination of them can be chosen for selecting 3GDT compliant UE, see
Section 3.8 on page 8.

The DtApnList is a list configured in the SGSN-MME where the 3GDT

enabled APN Network Identifiers (NIs) or the 3GDT disabled APN NIs are
defined. By using the list, the configuration on a basis of subscriber level in the
HLR is not necessary. The maximum number of entries is 300.

The DtApnList can be used as either an APN whitelist (3GDT enabled

APNs) or an APN blacklist (3GDT disabled APNs) depending on the value
of the DtSelectionMode parameter. If it is used as an APN whitelist and
a requested APN matches an entry in DtApnList, the PDP context is
considered as a candidate for 3GDT. However, if it is used as an APN blacklist
and a requested APN matches an entry in DtApnList, the PDP context is
not considered as a candidate for 3GDT. For an example of how to configure
the list, see Section 5.6 on page 16.

Note: The APN whitelist and APN blacklist cannot be used simultaneously.
Only one of them can be chosen by setting the DtSelectionMode
parameter. When switching between the APN whitelist and APN
blacklist, the DtApnList must be deleted and reconfigured manually.

The DtTacList is a list configured in the SGSN-MME where the 3GDT

enabled TACs or 3GDT disabled TACs are defined. The first eight digits of the
TAC is International Mobile Equipment Identity Software Version (IMEISV). By
using the list, it is possible to select the 3GDT candidate for a PDP context
based on user terminal type. The maximum number of entries is 1000.

The DtTacList can be used as either a TAC whitelist (3GDT enabled TACs)
or TAC blacklist (3GDT disabled TACs) depending on the setting of the
DtSelectionMode parameter. If it is used as a TAC whitelist and the TAC
extracted from the IMEISV for a subscriber matches an entry in DtTacList,
the PDP context is considered as a candidate for 3GDT. However, if it is used
as a TAC blacklist and the TAC extracted from the IMEISV for a subscriber
matches an entry in DtTacList, the PDP context is not considered as a
candidate for 3GDT.

Note: The TAC whitelist and the TAC blacklist cannot be used simultaneously.
Only one of them can be chosen by setting the DtSelectionMode
parameter. When switching between TAC whitelist and TAC blacklist,
the DtTacList must be deleted and reconfigured.

To use the DtTacList method (TAC-based 3GDT configuration), set the

parameter IuIdentityImeiEnabled to true. Then the IMEISV is fetched
from the UE at each performed authentication procedure during attach and
inter-SGSN RAU.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 7

 3G Direct Tunnel Configuration

Note: The DtApnList and the DtTacList can be left empty.

If DtApnList is used as an APN whitelist and a wildcard (*) is

included or it is used as an APN blacklist and left empty, every APN is
considered as a candidate for 3GDT. If DtApnList is used as an APN
blacklist and a wildcard (*) is included or it is used as an APN whitelist
and left empty, no APN is considered as a candidate for 3GDT.

Instructions

If using the DtApnList method, follow the step below:

1. Configure DtApnList by using the create_dt_apn and the delete_dt_apn

CLI commands.

If using the DtTacList method, follow the steps below:

1. Set the IuIdentityImeiEnabled parameter by using the modify_iu

CLI command.

2. Configure DtTacList by using the create_dt_tacand the delete_dt_tac

CLI commands.

For an example, see Section 5.6 on page 16.

3.7 Configuring the 3GDT Decision Method for GGSNs

Configure the 3GDT decision method for GGSNs: GGSN IP address list or
3GDT APN prefix.

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

Instructions

1. Set the DtGgsnList parameter by using the modify_dt CLI command.

For an example, see Section 5.7 on page 16.

3.8 Configuring the 3GDT Decision Method for UE

The parameter DtSelectionMode defines whether the subscription data
is analyzed, DtApnList or DtTacList is used as a whitelist or blacklist to
determine if the PDP context is a candidate for 3GDT. It also defines the
behavior when no match is found. The following values can be configured
in the parameter:

1 By using this value, only subscription data is analyzed

to determine whether the PDP context is a candidate
for 3GDT.

8 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Configuring 3GDT

Note: This value is valid only for the SGSN-MME

using the Gn interface.

Note: If this value is configured for the SGSN-MME

using the S4 interface, the DtSelectionMode
parameter is ignored. The tunnel mode for the
SGSN-MME using the S4 interface depends
on other conditions, such as the value of the
DtSgwS12Supported parameter, and the
value of the DtS4VplmnAllowed parameter.

2 By using this value, both DtApnList and DtTacList

are used as whitelists. If a match is found in either
DtApnList or DtTacList, the PDP context is
considered as a candidate for 3GDT. If neither
DtApnList nor DtTacList has a match, subscription
data is analyzed to determine whether the PDP context
is a candidate for 3GDT.

Note: The subscription data analysis is valid only for

the SGSN-MME using the Gn interface.

3 By using this value, only DtApnList is used as a

whitelist. If a match is found, the PDP context is
considered as a candidate for 3GDT. If no match is
found, 3GDT will not be used for this PDP context.

4 By using this value, only DtTacList is used as a

whitelist. If a match is found, the PDP context is
considered as a candidate for 3GDT. If no match is
found, 3GDT will not be used for this PDP context.

5 By using this value, both DtApnList and DtTacList

are used as whitelists. Only when a match is found in
both DtApnList and DtTacList is the PDP context
considered as a candidate for 3GDT. If a match is not
found in both DtApnList and DtTacList, 3GDT will
not be used for this PDP context.

6 By using this value, only DtApnList is used as a

blacklist. If a match is found, the PDP context is not
considered as a candidate for 3GDT. If no match is
found, 3GDT will be used for this PDP context.

7 By using this value, only DtTacList is used as a

blacklist. If a match is found, the PDP context is not
considered as a candidate for 3GDT. If no match is
found, 3GDT will be used for this PDP context.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 9

 3G Direct Tunnel Configuration

8 By using this value, both DtApnList and DtTacList

are used as blacklists. If a match is found in either
DtApnList or DtTacList, the PDP context is
not considered as a candidate for 3GDT. If neither
DtApnList nor DtTacList has a match, 3GDT will be
used for this PDP context.

The default value of this parameter is 1.

Instructions

1. Set the DtSelectionMode parameter by using the modify_dt CLI

command.

For an example, see Section 5.8 on page 17.

3.9 Configuring 3GDT for the Default APN

If the DtSelectionMode parameter is set to 3, the parameter
DtAllowForDefaultApn can be used to determine whether to use 3GDT
for the default APN, when there is a fallback after APN redirection. The value
true means that 3GDT is used for the default APN, whereas the value false
means that 3GDT is not used. By default, the value of this parameter is false.

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

Instructions

1. Enable the licensed feature APN Redirection by using the modify_feature

CLI command.

2. Set the DtSelectionMode parameter to 3 and the DtAllowForDefault

Apn parameter to true by using the modify_dt CLI command.

3. Configure the default APN or a wildcard (*) in DtApnList by using the

create_dt_apn CLI command.

For an example, see Section 5.9 on page 17.

3.10 Configuring the 3GDT Decision Method Based on

Service Request Frequency
Optionally, the operator can decide whether to configure the 3GDT based on
Service Request frequency by setting the value of DtServiceFrequency
parameter to true and configuring the corresponding 3GDT decision criteria.
By setting the value of DtServiceFrequency parameter to false, the 3GDT
based on Service Request frequency is disabled.

10 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Configuring 3GDT

Instructions

1. To enable the 3GDT decision based on Service Request Frequency, set

the DtServiceFrequency parameter to true by using the modify_dt
CLI command.

2. Configure the DtMeasurementInterval, DtThresholdNumber and

NoDtPeriod parameter by using the modify_dt CLI command to create
the 3GDT decision criteria.

For an example, see Section 5.10 on page 17.

3.11 Configuring the DNS

Note: The APNs already configured in the DNS server must not be modified.
This is to ensure backward compatibility.

For each APN intended for 3GDT, an additional entry is required in the DNS
server for each 3GDT compliant GGSN that supports the APN.

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

Use the following format for the entry:

3gdt_prefix.APN

The variables are as follows:

3gdt_prefix The prefix specified in Section 3.4 on page 5.

APN The original APN entry.

Instructions

1. To create a new entry in the DNS table, see the vendor documentation.

For an example, see Section 5.11 on page 18.

3.12 Configuring the HLR

It is possible to use the DtApnList method, the HLR configuration, or both.

If the HLR configuration is to be used, each combination of UE and APN

intended for 3GDT requires an additional entry created in the IMSI subscription
data in the HLR.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 11

 3G Direct Tunnel Configuration

Note:

• The APNs already configured in the HLR must not be modified.

This is to ensure backward compatibility. This is to ensure
backward compatibility.

• This configuration is valid only for the SGSN-MME using the Gn

interface.

Use the following format for the entry:

3gdt_prefix.APN(s)

The variables are as follows:

3gdt_prefix The prefix specified in Section 3.4 on page 5.

APN(s) The original APN entry subscribed.

Instructions

1. To create an entry in the HLR table, see the vendor documentation.

For an example of configuring the HLR, see Section 5.12 on page 18.

3.13 Activating 3GDT

Activating 3GDT does not affect the active PDP contexts.

When the state of the 3GDT feature parameter is set, the configuration stored
in a pending configuration area must be checked in consistency and activated
for 3GDT to come into effect.

Instructions

1. To enable 3GDT, set the state of the 3gdt feature parameter to on by

using the modify_feature CLI command.

2. Check the consistency of the feature parameter configuration by using the

check_config CLI command.

3. Activate the pending feature parameter configuration by using the

activate_config_pending CLI command.

For an example of activating 3GDT, see Section 5.13 on page 19.

3.14 Verifying the SGSN-MME Operation

It is recommended to verify the SGSN-MME operation by performing a health
check on the SGSN-MME.

12 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Supplementary Configuration

Instructions

1. Perform a health check on the SGSN-MME, see Health Check.

3.15 Checkpointing the Configuration

Perform a checkpoint to ensure that the current configuration is stored
persistently.

Instructions

Checkpoint the configuration using the checkpoint CLI command:

checkpoint { -cpn CheckpointName } –default_sc SetAsDefaultSc

4 Supplementary Configuration

This section describes supplementary configuration.

4.1 Deactivating 3GDT

Deactivating 3GDT only affects the non-active PDP contexts.

Instructions

1. To disable the feature, set the state of the 3gdt feature parameter to off
by using the modify_feature CLI command.

2. Check the consistency of the feature parameter configuration by using the

check_config CLI command.

3. Activate the pending feature parameter configuration by using the

activate_config_pending CLI command.

4.2 Enabling and Disabling 3GDT Support Check

In the case of an Inter-SGSN Routing Area Update (ISRAU), it is risky if not
all GGSNs in the home network support 3GDT, since a new SGSN cannot
determine whether the connected GGSN supporting 3GDT.

In the case of a pre-release 7 GGSN, error indications from the RNC are treated
as though they come from the SGSN, then the GGSN deletes the PDP context

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 13

 3G Direct Tunnel Configuration

without informing the SGSN. This results in a hanging PDP context in the UE
and the SGSN, which is resolved at the next connection establishment.

With a release 7 GGSN, the PDP context is not deleted but the SGSN is
informed, and the Radio Access Bearer (RAB) can be re-established.

During an ISRAU, therefore, the SGSN-MME checks whether the GGSN

supports 3GDT based on 3GPP release 7, using the optional Private Extension
Information Element (IE) in the Forward Relocation Request and SGSN Context
Response messages. If no optional Private Extension IE exists, it means the
GGSN does not support 3GDT based on 3GPP release 7 or the old SGSN does
not support the optional Private Extension IE, so 3GDT is not used.

Instructions

1. To disable the check for the optional Private Extension IE, set the
DtIgnoreGGSNIp parameter by using the modify_dt CLI command.

5 Examples for Configuring 3GDT

Stop!

Every operator should carefully examine what parameters to configure and

what values to give them. The parameter values in the examples are not in any
way recommended values.

This section includes the configuration examples according to the configuration

flowchart in Section 3 on page 3.

For more information about available operations for 3GDT, see 3G Direct
Tunnel (CLI).

For more information about available operations for feature management, such
as creating, deleting, displaying, and modifying a configuration, see Feature
Management (CLI).

14 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Examples for Configuring 3GDT

5.1 Configuring the RNC

For configuration instructions, see Section 3.1 on page 4.

In this example, an RNC is specified as 3GDT compliant.

modify_rnc –rn Slussen –dt true

For more information on available operations for the RNC in the SGSN-MME,
see RNC (CLI).

5.2 Configuring the S12 Interface Capability of SGWs

For configuration instructions, see Section 3.2 on page 4.

Note: This configuration is valid only for the SGSN-MME using the S4
interface.

modify_dt -dsss true

5.3 Configuring 3GDT for UE Not in the HPLMN

For configuration instructions, see Section 3.3 on page 5.

Note: This configuration is valid only for the SGSN-MME using the S4
interface.

modify_dt -dsva true

5.4 Configuring the 3GDT Prefix

For configuration instructions, see Section 3.4 on page 5.

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

In this example, the 3GDT prefix is specified as '3gdt'.

modify_dt -dp 3gdt

Note: The default value of the DtPrefix parameter is 3gdt. The prefix is
case sensitive.

5.5 Configuring the DtGgsnList

The DtGgsnList is configured by adding and removing GGSN IP addresses.
For configuration instructions, see Section 3.5 on page 6.

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 15

 3G Direct Tunnel Configuration

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

In this example, DtGgsnList is extended with an additional entry.

create_dt_ggsn_address -ip 10.0.2.23 -gn Gothenburg

5.6 Configuring the DtApnList and the DtTacList

The DtApnList and the DtTacList are configured by adding and removing
APNs and TACs respectively. For configuration instructions, see Section 3.6 on
page 6.

In this example, DtApnList and DtTacList are extended with additional

entries.

create_dt_apn -an ERICSSON.COM

create_dt_tac -tac 35726302 -utm SonyEricssonXperiaX1

5.7 Configuring the 3GDT Decision Method for GGSNs

With the use of the DtGgsnList parameter, the 3GDT configuration in the
DNS server is not necessary. Otherwise, for each APN intended for 3GDT, an
additional entry is required in the DNS server for each 3GDT compliant GGSN
that supports the APN.

Note: The APN must not be modified as it is already configured in the DNS
server. This is to ensure backward compatibility.

In Example 1, DtGgsnList is defined and DtApnList is used as a whitelist.

For the query apn1, the DNS gets the following addresses: a3,a4,a1,a2. The
SGSN uses these addresses at PDP activation for APN apn1 as follows:

• a1 and a2 in round-robin algorithm

• a1 or a2 with direct tunnel

The SGSN tries the addresses a1, a2, a3 and a4 in round-robin algorithm and
in dt GGSN address list first. If the SGSN does not get a response from a1 and
a2, it tries a3 and a4, which does not use direct tunnel.

modify_dt -dgl true

create_dt_ggsn_address -ip GgsnIpAddress -gn a1
create_dt_ggsn_address -ip GgsnIpAddress -gn a2
create_dt_apn -apn apn1
modify_dt -dsm 3
Example 1 DtGgsnList defined, DtApnList used as whitelist

16 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Examples for Configuring 3GDT

In Example 2, the DNS gets the addresses: a3,a4,a1,a2 for the query apn1.
The SGSN uses these addresses at PDP activation for APN apn1 as follows:

• a1 and a2 in round-robin algorithm if TAC, extracted from the IMEISV for

the subscriber, matches tac1.

• a1 or a2 with direct tunnel (3GDT).

• a1 to a4 in round-robin algorithm if TAC, extracted from the IMEISV for

the subscriber, does not match tac1.

• a1, a2, a3, or a4 with dual tunnel.

The SGSN tries the addresses a1, a2, a3 and a4 in round-robin algorithm and
in dt GGSN address list first. If the SGSN does not get response from a1 and
a2, it tries a3 and a4, which do not use direct tunnel.

modify_dt -dgl true

create_dt_ggsn_address -ip GgsnIpAddress -gn a1
create_dt_ggsn_address -ip GgsnIpAddress -gn a2
create_dt_apn -apn apn1
modify_dt -dsm 5
create_dt_tac -tac tac1
Example 2 DtGgsnList Defined, both DtApnList and DtTacList Used as
Whitelists

5.8 Configuring the 3GDT Decision Method for UE

For configuration instructions, see Section 3.8 on page 8.

In this example, both DtApnList and DtTacList are used as blacklists.

modify_dt -dsm 8

5.9 Configuring 3GDT for the Default APN

For configuration instructions, see Section 3.9 on page 10.

Note: This configuration is valid only for the SGSN-MME using the Gn
interface.

The following example shows how to use 3GDT for the default APN.

modify_feature -name apn_redirection -state on

modify_dt -dsm 3 -dada true

create_dt_apn -an ERICSSON.COM

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 17

 3G Direct Tunnel Configuration

5.10 Configuring the 3GDT Based on Service Request

Frequency
For configuration instructions, see Section 3.10 on page 10. The following
example shows how to configure the 3GDT based on Service Request
frequency.

gsh modify_dt -dsf true -dtn 2 -dmi 1 -ndp 5

5.11 Configuring the DNS

For configuration instructions, see Section 3.11 on page 11.

Note:

• This is an example only. Please see the vendor documentation for

how to create entries in the DNS table.

• This configuration is valid only for the SGSN-MME using the Gn

interface.

In this example, the DNS table is extended with an additional entry for an APN
pointing to a GGSN supporting 3GDT.

APN: 3gdt.ERICSSON.COM

Where the original APN entry is ERICSSON.COM and the DtPrefix is defined
as 3gdt.

5.12 Configuring the HLR

For configuration instructions, see Section 3.12 on page 11.

Note:

• This is an example only. Please see the vendor documentation for

how to create entries in the HLR table.

• This configuration is valid only for the SGSN-MME using the Gn

interface.

In this example, the entries are created in the HLR table.

The 3gdt_prefix is defined as 3gdt. The original APN entry is

ERICSSON.COM. The following line defines a 3gdt.ERICSSON.COM APN
with an APNID equal to 1978:

HGAPI:APN1="3gdt.",APN2="ERICSSON.COM",APNID=1978;

18 1/1543-AXB 250 05/8 Uen AY | 2015-11-20

 Examples for Configuring 3GDT

The following line defines a subscriber PDP context with an APN identifier
equal to 1978 and an extended QOS identifier equal to 1500 for a subscriber
with an IMSI number equal to 12345678:

HGPDI:IMSI=12345678,EQOSID=1500,APNID=1978;

This subscriber PDP context is used for dynamic addressing. The associated
PDP context type is IP version 4. No charging characteristics are
associated. The subscriber is not allowed to use the APN in the Visitor Public
Land Mobile Network (VPLMN).

5.13 Activating 3GDT

For configuration instructions, see Section 3.13 on page 12.

In this example, the license-controlled feature 3GDT is enabled and activated.

modify_feature -name 3gdt -state on

check_config

activate_config_pending

1/1543-AXB 250 05/8 Uen AY | 2015-11-20 19