SGSN Service Configuration Procedures

1. Create all the contexts you will use in your configuration. Refer to the “System Element Configuration Procedures” chapter in the System Administration Guide.
2. Create and configure the Frame Relay interface(s) and Ethernet interface(s). Refer to the “System Element Configuration Procedures” chapter in the System Administration Guide.
3. Configure SS7 routing domains. Use the procedure in Configuring an SS7 Routing Domain. The concept of an SS7 routing domain is not a standard SS7 concept. It is a concept specific to this platform which groups a set of SS7 feature configuration together to facilitate the management of the SS7 connectivity resources for an SGSN service.
4. Configure GTT. The GTT configuration is used to set rules for GTT and define the GTT databases. Follow the procedure in Configuring GTT.
5. Configure SCCP-Networks. The purpose of an SCCP network is to isolate the higher protocol layers above SCCP and the application itself from SS7 connectivity issues, as well as, to provide a place for global SCCP configuration specific to SGSN services. Use the procedure in Configuring an SCCP Network.
6. Configure MAP services. The MAP service configuration is used by the SGSN service to communicate with many of the nodes on the narrow band-SS7 network part of the network such as HLR, EIR, GSM-SCF, GMLC and SMS-GMSC/SMS-IWMSC. The purpose of having an isolated map configuration is to enable different application services to use the map service to communicate with other map entities in the network. Use the procedure in Configuring a MAP Service.
7. Configure SGTP. The SGTP service configures the parameters used for GTP Tunneling. At the minimum, interfaces for GTP-C and GTP-U must be configured. Use the procedure in Configuring an SGTP Service.
8. Configure the SGSN service. All the parameters specific to the operation of an SGSN are configured in the SGSN service configuration mode. SGSN services use other configurations like MAP and IuPS to communicate with other elements in the network. The system can support multiple SGSN services. Use the procedure in Configuring an SGSN Service (3G only).
9. Configure the GPRS service. All of the parameters needed for the system to perform as a an SGSN in a GPRS network are configured in the GPRS service. The GPRS service uses other configurations such as SGTP and MAP to communicate with other network entities and setup communications between the BSS and the GGSN. Use the procedure in Configuring a GPRS Service (2.5G only).
10. Configure the Network Service Entity Instance. This identifies the NSEI to use and associates it with a Network Service Virtual Connection Identifier. Use the procedure in Configuring a Network Service Entity.
11. Configure DNS. This configuration enables domain name resolution and specifies the DNSs to use for lookup. Use the procedure in Configuring DNS Client.
12. Configure GTPP Accounting. This configures GTPP-based accounting for subscriber PDP contexts. Use the procedure in Configuring GTPP Accounting Support.
13. Configure Frame Relay DLCI paths and bind them to NSEI links as needed. Refer to Creating and Configuring Frame Relay Interfaces and Ports in the System Administration Guide.
14. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

1. Create the contexts needed. Refer to the System Element Configuration Procedures chapter in the System Administration Guide.
2. Create any interfaces needed in the appropriate context. Refer to the System Element Configuration Procedures chapter in the System Administration Guide for IP (broadcast Ethernet) interfaces and for ATM interfaces.
3. Configure SS7 routing domains. The SS7 routing domain is proprietary concept to provide a combined configuration for the SS7 links, linksets, and related parameters. SS7 routing domain configurations are common to both SIGTRAN and MTP3-B networks. Use the procedure in Configuring an SS7 Routing Domain.
4. Configure global title translations (GTT). The GTT configuration is used to set rules for GTT and to define the GTT databases. Follow the procedure in Configuring GTT.
5. Configure SCCP networks. The SCCP network (layer) provides services to protocol layers higher in the SS7 protocol stack, for example RANAP and TCAP. The SCCP layer is also responsible for GTT. As well, all the SS7 routing domains (created in step 3) will be associated with an SCCP network. Use the procedure in Configuring an SCCP Network.
6. Configure MAP services. The MAP service configuration is used by the SGSN service to communicate with many of the nodes in the SS7 network, such as the HLR, EIR, GSM-SCF, GMLC and SMS-GMSC/SMS-IWMSC. Having an isolated MAP configuration enables different application services to use the MAP service to communicate with other MAP entities in the network. Use the procedure in Configuring a MAP Service.
7. Configure IuPS services. A set of parameters define the communication path between the SGSN service and radio network controllers (RNCs) in a UMTS IuPS service. Use the procedure in Configuring an IuPS Service (3G only).
8. Configure SGTP services. The SGTP service configures the parameters used for GTP Tunneling. At a minimum, interfaces for GTP-C and GTP-U must be configured. Use the procedure in Configuring an SGTP Service.
9. Configure the SGSN service. All the parameters specific to the operation of an SGSN are configured in the SGSN service configuration mode. SGSN services use other configurations like MAP and IuPS to communicate with other elements in the network. The system can support multiple SGSN services. Use the procedure in Configuring an SGSN Service (3G only).
10. Configure DNS clients. This configuration enables domain name resolution and specifies the DNSs to use for lookup. Use the procedure in Configuring DNS Client.
11. Optional: Configure operator policies. Operator policies are not required for SGSN operation, however, they provide the operator with a powerful method for determining call handling. SGSN operator policies specify rules governing the services, facilities and privileges available to a single subscriber or groups of subscribers. Use the procedure in Configuring SGSN Operator Policies.
12. Configure GTPP Accounting. This configures GTPP-based accounting for subscriber PDP contexts. Use the procedure in Configuring GTPP Accounting Support.
13. Configure ATM PVCs and bind them to interfaces or SS7 links as needed. Refer to Creating and Configuring ATM Interfaces and Ports in the System Administration Guide.
14. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

1. Create the contexts needed. Refer to the System Element Configuration Procedures chapter in the System Administration Guide.
2. Create any interfaces needed in the appropriate context refer to the System Element Configuration Procedures chapter in the System Administration Guide.
   1. For IP (broadcast Ethernet) interfaces, refer to Creating and Configuring Ethernet Interfaces and Ports in the System Administration Guide.
   2. For ATM interfaces (3G) refer to Creating and Configuring ATM Interfaces and Ports in the System Administration Guide.
   3. For Frame Relay interfaces (2.5G) refer to Creating and Configuring Frame Relay Interfaces and Ports in the System Administration Guide.
3. Configure SS7 routing domains. The SS7 routing domain is a non-standard, proprietary SS7 concept specific to this platform. SS7 routing domains provide a combined configuration for the SS7 links, linksets, and related parameters for SS7 connectivity resources for an SGSN service. SS7 routing domain configurations are common to both SIGTRAN and MTP3-B networks. Use the procedure in Configuring an SS7 Routing Domain.
4. Configure global title translations (GTT). The GTT configuration is used to set rules for GTT and to define the GTT databases. Follow the procedure in Configuring GTT.
5. Configure SCCP networks. The SCCP network (layer) provides services to protocol layers higher in the SS7 protocol stack, for example RANAP and TCAP. The SCCP layer is also responsible for GTT (step 4) and every SS7 routing domain (step 3) will be associated with an SCCP network. Use the procedure in Configuring an SCCP Network.
6. Configure MAP services. The MAP service configuration is used by the SGSN service to communicate with many of the nodes in the SS7 network, such as the HLR, EIR, GSM-SCF, GMLC and SMS-GMSC/SMS-IWMSC. Having an isolated MAP configuration enables different application services to use the MAP service to communicate with other MAP entities in the network. Use the procedure in Configuring a MAP Service.
7. Configure IuPS services. A set of parameters define the communication path between the SGSN service and radio network controllers (RNCs) in a UMTS IuPS service. Use the procedure in Configuring an IuPS Service (3G only).
8. Configure SGTP services. The SGTP service configures the parameters used for GTP Tunneling. At a minimum, interfaces for GTP-C and GTP-U must be configured. Use the procedure in Configuring an SGTP Service.
9. Configure the GPRS service. All of the parameters needed for the system to perform as a an SGSN in a GPRS network are configured in the GPRS service. The GPRS service uses other configurations such as SGTP and MAP to communicate with other network entities and setup communications between the BSS and the GGSN. Use the procedure in Configuring a GPRS Service (2.5G only).
10. Configure the Network Service Entity Instance. This identifies the NSEI to use and associates it with a Network Service Virtual Connection Identifier. Use the procedure in Configuring a Network Service Entity.
11. Configure DNS. This configuration enables domain name resolution and specifies the DNSs to use for lookup. Use the procedure in Configuring DNS Client.
12. Configure GTPP Accounting. This configures GTPP-based accounting for subscriber PDP contexts. Use the procedure in Configuring GTPP Accounting Support.
13. Configure ATM PVCs and bind them to interfaces or SS7 links as needed. Refer to Creating and Configuring ATM Interfaces and Ports in the System Administration Guide.
14. Configure Frame Relay DLCI paths and bind them to NSEI links as needed. Refer to Creating and Configuring Frame Relay Interfaces and Ports in the System Administration Guide.
15. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

1. Configure, 2G, 3G or Dual Access SGSN service support. Refer to the 2.5G SGSN Service Configuration, 3G SGSN Service Configuration, or Dual Access SGSN Service Configuration sections in this chapter for the configuration
2. Configure and associate the EGTP service. The EGTP service is required to support communication between the SGSN and the EPC SGW over the S4 interface using the GTPv2 protocol. Refer to the Configuring and Associating the EGTP Service (S4 Only) procedure.
3. Configure DNS for APN resolution. Configurables must be set to enable the default DNS client on the SGSN to resolve EPC PGW and SGW addresses. Refer to the Configuring the DNS Client Context for APN and SGW Resolution procedure.
4. Configure the S6d Diameter Interface. The S6d interface is used by the SGSN to communicate with the HSS. The HSS is a master user database that contains all subscription related information, Refer to the Configuring the S6d Diameter Interface (S4 Only) procedure.
5. Configure the S13’ (S13 prime) interface. This interface is used to perform Mobile Equipment (ME) identity check procedure between the SGSN and Equipment Identity Registry. Refer to the Configuring the S13’ Interface (S4 Only) procedure.
6. Configure QoS mapping between EPC elements and the SGSN. The S4-SGSN communicates QoS parameters towards the SGW/ PGW and EPC UEs in different formats. Operators must configure the SGSN quality of service (QoS) parameters as a call-control-profile that will ensure proper QoS mapping between the S4-SGSN, SGW/PGW and UEs. Refer to the Configuring QoS Mapping for EPC-Capable UEs Using the S4 Interface (S4 Only) procedure.
7. Optional. Configure the interface type used by the S4-SGSN to communicate with the peer SGSN. Refer to the Configuring the Peer SGSN Interface Type (S4 Only, Optional) procedure.
8. Optional. Configure Gn interface selection for EPC-capable UEs based on an operator policy. By default, the SGSN selects the S4 interface for EPC-capable UEs when the EGTP service is configured. However, operators have the option to forcefully select the Gn interface for these UEs. Refer to the Configuring Gn Interface Selection Based on an Operator Policy (S4 Only, Optional) procedure.
9. Optional. Configure a custom MME group ID. For operators who are using LAC ranges between 32768 and 65535 in UMTS/GPRS deployments, rather than for MMEs in LTE deployments, the SGSN provides a workaround to ensure backward compatibility. Refer to the Configuring a Custom MME Group ID (S4 Only, Optional) procedure.
10. Optional. Configure the S-GW for a RAI. If operators wish to bypass DNS resolution for obtaining the EPC S-GW address, the S4-SGSN can select a locally configured S-GW by performing a local look-up for the current RAI. Refer to the Configuring the Selection of an SGW for RAI (S4 Only, Optional) procedure.
11. Optional. Configure a Local PGW Address. For operators who wish to bypass DNS resolving an EPC P-GW address, the SGSN can be configured with a local P-GW address as part of an APN profile. Refer to the Configuring a Local PGW Address (S4 Only, Optional) procedure.
12. Optional. Configure the peer MME address. If operators wish to bypass DNS to resolve the peer MME address, the SGSN supports the local configuration of a peer MME address for a given MME group (LAC) and MME code (RAC). Refer to Configuring the Peer MME Address (S4 Only, Optional) procedure.
13. Optional. Configure the Idle Mode Signaling Reduction (ISR) feature. The ISR is a license-enabled feature allows the UE to roam between LTE and 3G networks while reducing the frequency of TAU and RAU procedures due to the UE selecting E-UTRAN or UTRAN networks. Refer to the Configuring the ISR Feature (S4 Only, Optional) procedure.
14. Optional. Enable the setup of indirect data forwarding tunnels (IDFT) between the eNodeB and the RNC via the SGW during connected mode handovers. This allows for connected mode handovers between the UTRAN and E-UTRAN networks across the S3 (S4-SGSN-to-MME) interface. Refer to Configuring IDFT for Connected Mode Handover (S4 Only, Optional).

1. In global configuration mode, create a GTT association with a unique name.
2. In GTT association configuration mode, define the type of digit analysis to be used; “fixed” is the generally used digit analysis and if specified, also define the length of the digits to be analyzed. This is represented using action IDs.
3. In GTT association configuration mode, define the GT format (1 to 4) for which the analysis needs to be applied.
4. In the GT format configuration mode, specify the numbering plan and the nature of address to be used. Note that a separate GTT association needs to be created for a combination of numbering plan, nature of address, and GT format.

   IMPORTANT:

   There are many different ways to configure a GTT association and the needs of every network are different. Please refer to the Global Title Translation Association Configuration Mode chapter in the Command Line Interface Reference for the commands available.

5. In global configuration mode, create a GTT address map, with a unique name, for a specific global title address.
6. In GTT address map configuration mode, associate a specific GTT association and the action ID.
7. In GTT address map configuration mode, define the routing indicator to be included in the Called-party Address in the out-going SCCP message along with the destination of the message using the option out-address.

   IMPORTANT:

   There are many different ways to configure a GTT Address Map and the needs of every network are different. Please refer to the GTT Address Map Configuration Mode chapter in the Command Line Interface Reference for the commands available.

Example Configuration

configure

   global-title-translation
association instance <inst#>

      action id <id> type <action_type> start-digit <num> end-digit <num>

      gt-format <format_num>

      exit

   global-title-translation
address-map instance <inst#>

      associate gtt-association <assoc#> action id <id>

      gt-address <gt_addr_prefix>

      out-address <name>

         ssf <sub_svc_fld>

         routing-indicator <route_ind>

         ni-indicator <addr_ind>

         ssn <sub_sys_num>

         point-code <pt_code>

         end

1. In global configuration mode, specify an identification number for this SCCP network configuration and the signaling variant.
2. Specify the self point code of the SGSN.
3. Specify the SS7 routing domain with which to associate this SCCP network configuration.
4. If using GTT (Global Title Translation), specify the name of a GTT address map to use.
5. Configure a destination point code and give it a name.
6. Configure the destination point code version.
7. Configure the destination point code subsystem number.

Example Configuration

configure

   sccp-network <id_number> variant <v_type>

      self-pointcode <sp_code>

      associate ss7-routing-domain <rd_id>

      global-title-translation
address-map <map_name>

      destination dpc <dp_code> name <name>

      destination dpc <dp_code> version <ver_type>

      destination dpc <dp_code> ssn <ss_number>

      end

1. In the context config mode, create a MAP service and give it a name.
2. In MAP Service configuration mode, configure the SCCP network that defines SS7 connectivity for SCCP applications.
3. Configure the parameters to contact the HLR.
4. In HLR configuration mode, specify the HLR pointcodes that should be associated with specific IMSI prefixes.
5. Configure the HLR pointcode to use as the default.
6. Optional: Enable the Short Message Service functionality.
7. Optional: Configure the SMS routing.

Example Configuration

configure

   context <context_name>

      map-service <map_name>

         access-protocol sccp-network <sccp_network_id>

         equipment-identity-register
point-code <pnt_code>

         hlr

            imsi any point-code

            default policy routing

            exit

         short-message-service

            smsc-routing  imsi-starts-with <prefix> point-code <sms_pc>

            end

1. In context configuration mode for the SGSN service, create an IuPS service and give it a unique name.
2. In IuPS service configuration mode, specify the ID of the SCCP network to use for access protocol parameters.
3. Bind an address of an IP interface defined in the current context to use for GTPU connections to the RNC.
4. Specify an RNC to configure with a unique ID and the MCC and MNC associated with the RNC.
5. In RNC configuration mode, specify the RNCs point code.
6. Specify the LAC ID and RAC ID associated with the RNC.

   IMPORTANT:

   Appropriate interfaces (i.e., physical, loopback, secondary) must be defined prior to configuring the IuPS service or the GTP-U IP address will decline to bind to the service.

Example Configuration

configure

   context <context_name>

      iups-service <iups_name>

         access-protocol sccp-network <sccp_network_id>

         gtpu bind address <ip_address>

         rnc id <rnc_id> mcc <mcc_num> mnc <mnc_num>

            pointcode <rnc_pc>

            lac <lac_id> rac <rac_id>

1. Create an SGTP service and give it a unique name, in context configuration mode.
2. Specify the IP address of an interface in the current context to use for GTP-C.
3. Specify the IP address of an interface in the current context to use for GTP-U.

   IMPORTANT:

   Appropriate interfaces (i.e., physical, loopback, secondary) must be defined prior to configuring the SGTP service or the GTP-U IP address will decline to bind to the service.

Example Configuration

configure

   context <name>

      sgtp-service <name>

         gtpc bind address <address>

         gtpu bind address <address>

         end

1. In context configuration mode, create a Gs service and give it a unique name. Usually Gs service is defined in the same context in which MAP service is defined because the MSC/VLR, HLR, EIR, and SMS-C are reachable via the STP or SGW connected to the SGSN.
2. Specify the name of the SCCP network that identifies the SS7 access protocols.
3. Specify the target SS7 sub-system number (SSN), of the Base Station System Application Part (BSSAP), for communication. Without this bit of configuration, the Gs service can not start.
4. Identify a location area code, in either a pooled or non-pooled configuration, relevant to the MSC/VLR. This step can be repeated as needed.
5. Define the MSC/VLR by identifying its ISDN number, its SS7 point code, and the BSSAP SSN used to communicate with it. Repeat this step to define multiple MSC/VLRs. (Note: SSN only needs to be defined if the routing defined is to the MSC/VLR is PC+SSN.)

Example Configuration

configure

   context <name>

      gs-service <name>

         associate-sccp-network <id>

         bssap+ ssn <ssn>

         non-pool-area <id> use-vlr <vlr_id> lac <lac_id>

         vlr <vlr_id> isdn-number <isdn_number> bssap+ ssn <ssn> point-code <vlr_pt_code>

         end

1. In Context configuration mode, create an SGSN service and give it a unique name.
2. Specify the Core Network (CN) ID that will identify this SGSN service on the CN.
3. Specify the E.164 number to identify this SGSN service.
4. Configure the maximum number of PDP contexts that a UE can establish.
5. Specify the MAP service and the context in which it is configured that this SGSN service should use.
6. Specify the IuPS service name and the context in which it is configured for the SGSN service to use for RAN protocol settings.

   IMPORTANT:

   If a direct tunnel is to be established, GTP-U direct tunneling must be enabled in both the IuPs service and in the call-control-profile. For the IuPS service, the DT must be enabled per RNC; DT is enabled by default on RNCs.

7. Specify the SGTP service and the context in which it is configured for this SGSN service to use for GTP configuration.
8. Specify the CDR types that the SGSN service should generate.
9. Specify the context in which GTPP accounting is configured. If the accounting context is not specified the current context is assumed.
10. Configure the charging characteristics profile. (Number of buckets for the max change condition, volume limit, time limit, and tariff time switch values should be defined individually according to requirements for each of the charging characteristics profiles.
11. Optional: Specify the Gs service name and the context in which it is configured.   

    IMPORTANT:

    Session Management (SM) and GPRS Mobility Management (GMM) settings can be configured as needed using the SGSN configuration mode commands;sm <keyword> andgmm <keyword>. Refer to the SGSN Service Configuration Mode chapter in the GPRS/UMTS Command Line Interface Reference.

Example Configuration

configure

   context <context_name>

      sgsn-service <svc_name>

         core-network id <cn_id>

         sgsn-number <sgsn_number>

         max-pdp-contexts per-ms <max_number>

         { mobile-application-part-service | associate
map-service } <map_name> context <map_context>

         ran-protocol iups-service <iups_svc_name> context <iups_context>

         { sgtp-service | associate
sgtp-service } <svc_name> 
context <name>

         accounting cdr-types [ mcdr | scdr ]

         accounting context <acct_context>

         cc profile <profile_number> interval <seconds>

         { gs-service context  | associate
gs-service } <ctxt> service <gs_service_name>

         end

1. In Context configuration mode, create a GPRS service instance and give it a unique name.
2. Specify the context in which the accounting parameters have been configured.
3. Create a PLMN definition for the GPRS service to include the identity of the mobile country code (MCC) and the mobile network code (MNC).
4. Associate other services (such as a MAP or Gs or SGTP service) and their configurations with this GPRS service. This command should be repeated to associate multiple service types and/or multiple instances.
5. Define the network service entity identifier (NSEI) of one or more remote SGSNs with their location area code (LAC) and routing area code (RAC). This step can be repeated to associate multiple peer-NSEIs.
6. Specify the E.164 number to identify this SGSN.
7. Configure the charging characteristic(s).
8. Specify the types of CDRs to generate.

Example Configuration

configure

   context <context_name>

      gprs-service <gprs_service_name>

         accounting <ctxt>

         plmn id mcc <mcc_num> mnc <mnc_num>

         { service | associate
service | }<service_type> <service_name> context <service_ctxt>

         peer-nsei <peer_nsei_id> lac <lac_id> rac <rac_id>

         sgsn-number <sgsn_isdn_number>

         cc profile <id> buckets <value>

         cc profile <id> interval <value>

         accounting cdr-types <cdr_type>

         end

1. In context configuration mode, enable DSN lookup.
2. Specify the DNS to use for lookups; maximum of two DNS addresses can be used.
3. Create a DNS client with a unique name.
4. In DNS Client configuration mode, bind the DNS client to the IP address of an interface in the current context.

Example Configuration

configure

   context <context_name>

      ip domain-lookup

      ip name-servers <ip_address>

      dns-client <name>

         bind address <ip_address>

         end

1. Create the GTPP group in accounting context by applying the example configuration in the Creating GTPP Group section.
2. Configure the charging agent and GTPP server (CGF) related parameters for the GTPP accounting support by applying the example configuration in the Configuring GTPP Group section.
3. Verify your GTPP group and accounting configuration by following the steps in the Verifying GTPP Group Configuration section.
4. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Creating GTPP Group

configure

   context <vpn_ctxt_name>

      gtpp group <gtpp_group_name>
-noconfirm

      end

Configuring GTPP Group

configure

   context <vpn_ctxt_name>

      gtpp group <gtpp_group_name>

         gtpp charging-agent
address <ip_address> [ port <port> ]

         gtpp server <ip_address> [ max <msgs >] [ priority <priority>]

         gtpp dictionary <dictionaries>

         gtpp max-cdrs <number_cdrs> [ wait-time <dur_sec> ]

         gtpp transport-layer { tcp | udp }

         end

1. Access Context Configuration Mode.
2. Create and configure the EGTP service in the desired context.
3. Configure the interface type for the EGTP service.
4. Configure the validation mode for the EGTP service. The default is standard.
5. Associate the EGTP service with the configured 2.5G service (if configured).
6. Associate the EGTP service with the configured 3G service (if configured).

Example Configuration

config

   context <context_name>

      egtp-service <service_name>

         gtpc { bind { ipv4-address <ipv4_address> [ ipv6-address <ipv6_address> ] }

         interface-type interface-sgsn

         validation-mode { custom1 | standard }

         end

config

   context <context_name>

      gprs-service <gprs_service_name>

         associate egtp-service <egtp_service_name> [ context <context_name> ]

         end

config

   context <context_name>

      sgsn-service <sgsn_service_name>

         associate egtp-service <egtp_service_name> [ context <context_name> ]

         end

1. Access Call Control Profile Configuration Mode and create a call control profile.
2. Configure the DNS client context to resolve PGW UEs via the context the DNS client is configured.
3. Configure the DNS client context to resolve SGW UEs via the context where the DNS client is configured.

Example Configuration

config 

    call-control-profile <name>

      dns-pgw context <dns_client_context_name>

      dns-sgw context <dns_client_context_name>

      end

1. Configure a Diameter Endpoint for the S13’ interface.
2. Configure the HSS Peer Service and Interface association for the S13’ interface.
3. Associate the HSS Peer Service with the SGSN and GPRS services for the S13’ interface.
4. Optional. Configure an operator policy S13-based interface selection call control profile for the S13’ interface.

1. Access Call Control Profile Configuration Mode and create a call-control-profile.
2. Configure the QoS ARP settings.
3. Exit back to the Local prompt and re-access Call Control Profile Configuration Mode.
4. Create a second call-control-profile.
5. Configure the QoS pre-emption or vulnerability capabilities.

Example Configuration

config

   call-control-profile <cc_profile_name>

      qos gn-gp arp high-priority <hi_prior_value> medium-priority <med_prior_value>

      end

config

   call-control-profile <cc-profile-name> 
 

      qos gn-gp  pre-emption { capability { may-trigger-pre-emption | shall-not-trigger-pre-emption } | vulnerability { not-pre-emptable | pre-emptable } }

      end

1. Access the Call Control Profile configuration for the peer SGSN.
2. Configure the interface type to be used for communication between the S4-SGSN and the peer SGSN. s16 must be specified if the peer SGSN is an S4-SGSN.

Example Configuration

config

   call-control-profile <cc_profile_name>

      sgsn-address rac <rac value> lac <lac value> [nri <val> ] prefer { local | fallback-for-dns} address ipv4 <ipv4 addr> interface { gn | s16 }

      end

1. Access Call Control Profile Configuration Mode.
2. Create a call-control-profile.
3. Configure the SGSN to forcefully select the Gn interface.

Example Configuration

config

   call-control-profile <cc_profile_name>

      sgsn-core-nw-interface { gn | s4 }

      end

1. Access LTE Network Global MME ID Management Database Configuration Mode.
2. Specify the PLMN MCC and MNC values.
3. Configure the low and high end values of the LAC range to be used.
4. Access the context in which the SGSN (3G) service is configured.
5. Associate the 3G service (if configured), with the MME’s Network Global MME ID Management Database that contains the custom list of MME Group IDs.
6. Access the context in which the 2G GPRS service is configured.
7. Associate the 2G service, if configured, with the MME’s Network Global MME ID Management Database that contains the custom list of MME Group IDs.

Example Configuration

config

   lte-policy

      network-global-mme-id-mgmt-db

         plmn
mcc <mcc_value> mnc <mnc_value> mme-group-id-range first           <low_end_of_range> last <high_end_of_range>

         exit

      exit

   context <context_name>

      sgsn-service <sgsn_service_name>

         associate network-global-mme-id-mgmt-db

         end

config

   context <context_name>

      gprs-service <gprs_service_name>

         associate network-global-mme-id-mgmt-db

         end

1. Access Global Configuration Mode.
2. Access LTE Policy Configuration Mode.
3. Create a TAI Management Database and enter TAI Management Database Configuration Mode.
4. Create a TAI Management Object and enter TAI Management Object Configuration Mode.
5. Configure the RAI. Specify the RAI MCC, MNC, LAC and RAC values.
6. Configure the SGW address serving the RAI. Specify the IPv4 or IPv6 address, the S5-to-S8 protocol as GTP, and the load balancing Weight for this SGW. On the S4-SGSN, only GTP is supported as the protocol option.
7. Access SGSN Service Configuration Mode and associate the configured UTRAN (3G) service with the S-GW addresses and their associated RAIs.
8. Access GPRS Service Configuration Mode and associate the configured GERAN (2G) and service with the S-GW addresses and their associated RAIs.
9. Optional. Associate the SGW address-to-RAI mapping with an operator policy.

Example Configuration

config

   lte-policy

      tai-mgmt-db <tai_mgmt_db_name>

         tai-mgmt-ojb <obj_name>

            rai mcc <mcc_value> mnc <mnc_value> lac <lac_value> rac <rac_value>

            sgw-address <ipv4_addr> | <ipv6_addr> s5-s8-protocol gtp weight             <number>

            end

config

   context <context_name>

      sgsn-service <sgsn_service_name>

         associate tai-mgmt-db <tai_mgmt_db_name>

         end

config

   context <context_name>

      gprs-service <gprs_service_name>

         associate tai-mgmt-db <tai_mgmt_db_name>

         end

config

   call-control-profile <cc_profile_name>

      associate tai-mgmt-db <tai_mgmt_db_name>

      end

1. Access APN Profile Configuration Mode and create an APN profile.
2. Specify the address resolution mode for the PGW as local.
3. Configure the P-GW address.
4. Configure the load balancing weight preference for the P-GW.

Example Configuration

config

   apn-profile <apn_profile_name>

      address-resolution-mode local

      pgw-address <ipv4_address | ipv6_address> weight <weight_preference>

      end

1. Access Call Control Configuration Mode and create a call-control-profile.
2. Configure the peer MME Group ID LAC and RAC values.
3. Specify a local preference for selection of the peer MME address.
4. Specify the local MME address to use for lookup instead of a DNS query.
5. Specify the interface type to use when communicating with the peer MME. The interface must be s3.

Example Configuration

config

   call-control-profile <cc-profile-name>

      peer-mme mme-groupid  <lac_value> mme-code  <rac_code>  prefer local address <ipv4_address | ipv6_address> interface { gn [ s3 ] | s3 [ gn ] } 

      end

1. Access Call Control Configuration Mode.
2. Create a call-control-profile.
3. Enable the Idle Mode Signaling Reduction feature for 3G (UMTS) network access
4. Set the T3323 timeout value that the configured SGSN service will send to the UE in Attach Accept and RAU Accept messages.

Example Configuration

config

   call-control-profile <cc-profile-name>

      idle-mode-signaling-reduction
access-type umts

      end

config

   context <context_name>

      sgsn-service <sgsn_service_name>

         gmm T3323-timeout <dur_mins>

         end

Example Configuration

config

   context <context_name>

      iups-service <iups_service_name>

         rnc id <rnc_id>

            no enb-direct-data-forward

            end

1. Configure a line card for either SONET or SDH.
2. Configure APS for a SONET line card or MPS for an SDH line card. Use the configuration example below:

Example Configuration

config

   card
27

      framing
sdh e1

      header-type
4-byte

      initial-e1-framing
standard

      redundancy
aps-mode

      service-type
frame-relay

      no
shutdown

      end