Académique Documents
Professionnel Documents
Culture Documents
OPERATION DIRECTIONS
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.
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
1 Introduction
1.1 Scope
This document covers the following topics:
• Available operations
• Configuration examples
• Configuration Prerequisites
Note: The detailed configuration of the DNS, the HLR, and the GPRS
backbone network is not covered in this document.
This document does not cover installation of the SGSN-MME, which must be
performed by the site installation engineers.
2 Prerequisites
2.1 Planning
In the planning phase of the configuration, the following requirements must be
fulfilled:
• The RNC, GGSN, and Access Point Names (APNs) are 3GDT compliant.
Note: When using the GGSN IP address list, the 3GDT prefix is not
needed in the subsequent DNS query and in the DNS server.
• 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:
2.3 Equipment
To preform 3GDT procedures, use the equipment for configuring the DNS
and the HLR.
3 Configuring 3GDT
To display the configuration classes and parameters related to 3GDT, use the
get_config_area -can 3GDirectTunnel CLI command.
Configuring 3GDT for the SGSN- Configuring 3GDT for the SGSN-
MME using the Gn interface MME using the S4 interface
START START
Instructions
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
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
Note:
• 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.
Instructions
Note:
Instructions
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 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.
Instructions
Note: This configuration is valid only for the SGSN-MME using the Gn
interface.
Instructions
Instructions
Note: This configuration is valid only for the SGSN-MME using the Gn
interface.
Instructions
Instructions
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.
3gdt_prefix.APN
Instructions
1. To create a new entry in the DNS table, see the vendor documentation.
Note:
3gdt_prefix.APN(s)
Instructions
For an example of configuring the HLR, see Section 5.12 on page 18.
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
Instructions
Instructions
4 Supplementary Configuration
Instructions
1. To disable the feature, set the state of the 3gdt feature parameter to off
by using the modify_feature CLI command.
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
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.
Instructions
1. To disable the check for the optional Private Extension IE, set the
DtIgnoreGGSNIp parameter by using the modify_dt CLI command.
Stop!
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).
For more information on available operations for the RNC in the SGSN-MME,
see RNC (CLI).
Note: This configuration is valid only for the SGSN-MME using the S4
interface.
Note: This configuration is valid only for the SGSN-MME using the S4
interface.
Note: This configuration is valid only for the SGSN-MME using the Gn
interface.
Note: The default value of the DtPrefix parameter is 3gdt. The prefix is
case sensitive.
Note: This configuration is valid only for the SGSN-MME using the Gn
interface.
Note: The APN must not be modified as it is already configured in the DNS
server. This is to ensure backward compatibility.
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:
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.
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:
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 -dsm 8
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.
Note:
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.
Note:
HGAPI:APN1="3gdt.",APN2="ERICSSON.COM",APNID=1978;
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).
check_config
activate_config_pending