What is ggsn pgw

Chinese English. Mobile Signaling. MNO Solution. About Us. Company News. Press Releases. Our High-performing Core Network. Beyond that, it also allocates an IP address to all UEs and enforces different policies regarding IP user traffic such as packet filtering. Number portability is one of the reasons why an MVNO has to interconnect with all the national operators.

If a subscriber is porting his number to another network you have to send and receive calls and SMSs. It will receive an answer and try to do a delivery according to the answer. A full MVNO architecture needs to be tested for every technical aspect. For every service package there are multiple scenarios that need to be tested. It is fully configured and intended for use as a VoLTE test bed and learning environment. Returns and Refunds Policy. Managing Report Generation. Creating Reports.

Generating Reports. Rogue Access Points. Viewing Rogue Access Points. Filtering Rogue Access Points. Marking Rogue Access Points. Locating a Rogue Access Point. Historical Client Stats.

Viewing AP Client Statistics. Ruckus AP Tunnel Stats. Core Network Tunnel Stats. Troubleshooting Client Connections. Troubleshooting through Spectrum Analysis. Managing Events and Alarms. Configuring Event Threshold. Configuring Alarms. Administering the Controller. Managing Administrator and Roles. Creating User Groups. Resource Group Details. Creating Administrator Accounts.

Unlocking an Administrator Account. Configuring Administrator Accounts. Working with AAA Servers. Enabling the Access Control List. Creating Account Security. Backing Up and Restoring Clusters. Creating a Cluster Backup. Restoring a Cluster Backup. Restoring from an FTP Server. Backing up Cluster Configuration.

Scheduling a Configuration Backup. Downloading a Copy of the Configuration Backup. Restoring a System Configuration Backup. Upgrading the Controller. Performing the Upgrade. Uploading an AP Patch File. Verifying the Upgrade. Rolling Back to a Previous Software Version. Upgrading the Data Plane. Uploading the Switch Firmware to the Controller.

Managing Licenses. Viewing Installed Licenses. Importing Installed Licenses. Synchronizing Controller with the License Server. Downloading License Files. Configuring the License Server.

Configuring License Bandwidth. ZoneDirector to SmartZone Migration. Monitoring Administrator Activities. Applying Scripts. Viewing Scripts. Viewing Script Execution Summary. Viewing and Downloading Logs. Available System Logs for platforms. SoftGRE Support. Supported Deployment Scenario. SoftGRE Events. SoftGRE Alarms. Replacing Hardware Components. Installing or Replacing Hard Disk Drives.

Ordering a Replacement Hard Disk. Removing the Front Bezel. Installing a Hard Drive in a Carrier. Reinstalling the Front Bezel. Replacing PSUs. Replacing System Fans. Replacing a Controller Node. Backing Up and Resorting the Cluster. Step 4: Restoring the Cluster Backup to the Controller. Restoring to a Single Node Environment. Restoring to a Multi-Node Environment. Replacing a Single Node in a Cluster. Replacing Multiple Nodes in a Cluster. Backing Up and Restoring Configuration.

Backed Up Configuration Information. Backing Up Configuration. Backing Up Configuration from the Web Interface. Restoring Configuration. Restoring Configuration to a Single Node Environment. Restoring Configuration to Multi Node Environment.

Restoring Configuration to a Single Node in a Cluster. GnGp Handoff in Roaming Scenario. Other remaining things work as in non-roaming scenario.

As specified by the standards, a CDR is not generated when a session starts. CDRs are generated according to the interim triggers configured using the charging characteristics configured for the GGSN, and a CDR is generated when the session ends.

GTPP version 2 is always used. All CDR fields are R4. If the system is configured to reject the charging characteristics from the SGSN, the GGSN can be configured with its own that can be applied based on the subscriber type visiting, roaming, or home at the APN level. GGSN charging characteristics consist of a profile index and behavior settings. The profile indexes specify the criteria for closing accounting records based specific criteria.

IP address pools are configured on the GGSN for many reasons, although one of them is so that the pool subnets can be automatically advertised to the network. These are connected routes and are advertised for all non-tunneling pools. A configuration explicit-route-advertise is provided to the IP pool configuration and when this option is enabled, the subnet s of the pool are not added to routing table and routing protocols like OSPF and BGP do not know of these addresses and hence do not advertise the subnet s.

As calls come up, and addresses from this pool with the "explicit-route-advertise" flag are used, the assigned addresses are added to the routing table and these addresses can be advertised by OSPF or BGP through the network or the "redistribute connected" command. When a subscriber connects to GGSN B with an IP address from the same pool, the subscriber will be assigned the requested IP address and the routing domain will then learn its host route.

When the subscriber disconnects, the route is removed from the routing table and the routing domain is updated. The explicit-route-advertise option can be applied and removed from the pool at any time and the routing tables are updated automatically. IP Policy Forwarding enables the routing of subscriber data traffic to specific destinations based on configuration.

This functionality can be implemented in support of enterprise-specific applications i. Subscriber specific Next Hop Forwarding - Forwards all packets for a specific subscriber. An IP pool is configured with the address of a next hop gateway and data packets from all subscribers using the IP pool are forward to that gateway.

Subscriber Next Hop forwarding is also very simple. In the subscriber configuration a nexthop forwarding address is specified and all data packets for that subscriber are forwarded to the specified nexthop destination. ACL-based Policy Forwarding gives you more control on redirecting data packets. ACLs are applied first. If ACL-based Policy Forwarding and Pool-based Next Hop Forwarding or Subscriber are configured, data packets are first redirected as defined in the ACL, then all remaining data packets are redirected to the next hop gateway defined by the IP pool or subscriber profile.

Allows the use of small packets for bulk data with good line efficiency. Allows the use of small packets for delay sensitive low data-rate traffic. Jacobson in It is commonly known as VJ compression. By default IP header compression using the VJ algorithm is enabled for subscribers.

You can also turn off IP header compression for a subscriber. The increased address space allows for future subscriber growth beyond what is currently possible in IPv4.

Native IPv6 support on the Gi interface allows support for packets coming from or destined to a mobile over the Gi interface. IPv6 address assignment is supported from a dynamic or static pool via standard 3GPP attributes.

Overlapping address space or resource pools are supported if they are in different VPNs. IP resources are grouped into separate routing domains know as contexts. The VPN subsystem creates and maintains each context and the resources associated with them. The existing IPv4 model of interface and route notification will be extended to support IPv6. Expanded addressing capabilities with bit for address as compared to 32 bits in IPv4.

Improved support of extensions and options. Link-local addresses will be automatically added to Ethernet type interfaces. ICMPv6 is a protocol for IPv6 networks to allow error reporting and check connectivity via echo messages. The forwarding lookup is based on a longest prefix match of the destination IPv6 address. In Release 9. Multi Protocol Label Switching MPLS is an operating scheme or a mechanism that is used to speed up the flow of traffic on a network by making better use of available network paths.

It generates a fixed-length label to attach or bind with the IP packet's header to control the flow and destination of data. Overlapping IP Address Pools provides a mechanism for allowing operators to more flexibly support multiple corporate VPN customers with the same private IP address space without the expensive investments in physically separate routers, or expensive configurations using virtual routers.

The system supports two type of overlapping pools: resource and overlap. Overlapping type pools can be used for both dynamic and static, and use VLANs and a next hop forwarding address to connect to the VPN customer.

When forwarding traffic upstream, the GGSN uses the tunnel and forwarding information in the IP pool configuration, so overlapping pools must be configured in the APN for this feature to be used.

This scalability allows operators, who wish to provide VPN services to customers using the customer's private IP address space, need not be concerned about escalating hardware costs, or complex configurations. From In pre-release Templates for all of the possible APNs that subscribers will be accessing must be configured within the system.

Up to 2, APNs can be configured on the system. Charging characteristics use SGSN-supplied or use configured.

IP address allocation method static or dynamic. A total of 11 PDP contexts are supported per subscriber. These could be all primaries, or 1 Primary and 10 secondaries or any combination of primary and secondary.

Note that there must be at least one primary PDP context in order for secondaries to come up. With support of this functionality the GGSN service supports the peer profile to allow flexible profile based configuration to accommodate growing requirements of customizable parameters with default values and actions for peer nodes of GGSN.

A new framework of peer-profile and peer-map is introduced for configuration. Peer-map config matches the peer-profile to be applied to a particular criteria. Peer-map can then be associated with GGSN service. With support of this feature the Operators can configure a profile which can be applied to a specific set of peers.

For example, have a different retransmission timeout for foreign peers as compared to home peers. This feature allows a single host or url rule to be applied to two different addresses, one with and one without the port number appended. As adding the port to the address is optional, this means that the number of rules could be halved.

Browser applications can sometimes appended the port number to the host or url when sending the host or URL fields. RFC for example states that port should be appended but if it is omitted then 80 should be assumed. When configuring rules to define the content, as the web browser may provide the port number, even if it is the default one of 80 for HTTP, then two of each URL are needed. This feature provides a means to configure the rule such that the traffic is matched irrespective of the presence of a port number.

For more information on enhanced charging service, refer Enhanced Charging Service Administration Guide. Provides operator control over the prioritization of different types of traffic. Quality of Service QoS support provides internal processing prioritization based on needs, and DiffServ remarking to allow external devices to perform prioritization. The feature described here is internal prioritization and DiffServ remarking for external prioritization. External prioritization i. Alternatively, you can configure "pass-through", whereby the ToS value will pass through unchanged.

In the downlink direction, the ToS value of the subscriber packet is not changed, but you can configure what to use for the ToS value of the outer GTP tunnel. Priority : Dictates the order in which the servers are used allowing for multiple servers to be configured in a single context. Routing Algorithm : Dictate the method for selecting among configured servers. The specified algorithm dictates how the system distributes AAA messages across the configured AAA servers for new sessions.

Once a session is established and an AAA server has been selected, all subsequent AAA messages for the session will be delivered to the same server. In the event that a single server becomes unreachable, the system attempts to communicate with the other servers that are configured. Instead of having a single list of servers per context, this feature provides the ability to configure multiple server groups.

Each server group, in turn, consists of a list of servers. This default server group is available to all subscribers in that context through the realm domain without any configuration.

It provides a facility to create "user defined" RADIUS server groups, as many as excluding "default" server group , within a context. VPN customers often use private address space which can easily overlap with other customers. The subscriber addresses are supported with overlapping pools which can be configured in the same virtual routing context.

Previously, the above scenarios were supported, albeit only when the overlapping addresses were configured in different contexts. The new feature utilizes the same concept as overlapping IP pools such that every overlapping NAS-IP address is giving a unique next-hop address which is then bound to an interface that is bound to a unique VLAN, thereby allowing the configuration to exist within the same context.

The next hop address determines the interface and VLAN to use. The number of Radius NAS-IP addresses that can be configured is limited by the number of loopback addresses that can be configured. The system's support for various routing protocols and routing mechanism provides an efficient mechanism for ensuring the delivery of subscriber data packets. GGSN node supports Routing Protocol in different way to provide an efficient mechanism for delivery of subscriber data.

Static Routes : The system supports the configuration of static network routes on a per context basis. Network routes are defined by specifying an IP address and mask for the route, the name of the interface in the currant context that the route must use, and a next hop IP address. IP packets are routed "as is", meaning they are not encapsulated in any further protocol headers as they transit the network. Variable length subnetting, areas, and redistribution into and out of OSPF are supported.

OSPF routing is supported in accordance with the following standards:. EBGP is supported with multi-hop, route filtering, redistribution, and route maps. The network command is support for manual route advertisement or redistribution. Prefix match based on route access list. Modification of AS path through path prepend. Route Access Lists : The basic building block of a routing policy, route access lists filter routes based upon a specified range of IP addresses.

IP Prefix Lists : A more advanced element of a routing policy. Route Maps : Route-maps are used for detailed control over the manipulation of routes during route selection or route advertisement by a routing protocol and in route redistribution between routing protocols.

In this manner, throughput load is distributed across multiple paths, typically to lessen the burden on any one route and provide redundancy. In general, the Session Trace capability records and forwards all control activity for the monitored subscriber on the monitored interfaces. Management initiation via direct CLI configuration. Management initiation at AAA with trace activation via authentication response messages over Gx reference interface.

Signaling based activation through signaling from subscriber access terminal. The session level trace function consists of trace activation followed by triggers. The time between the two events is treated much like Lawful Intercept where the UMTS network element buffers the trace activation instructions for the provisioned subscriber in memory using camp-on monitoring. Trace files for active calls are buffered as XML files using non-volatile memory on the local dual redundant hard drives on the system.

The Trace Depth defines the granularity of data to be traced. Six levels are defined including Maximum, Minimum and Medium with ability to configure additional levels based on vendor extensions. This feature provides the ability for operators to apply Charging Characteristics CC from the AAA server instead of a hard coded local profile during access authentication.

All 16 profile behaviors can be defined explicitly or the default configuration for that profile is used. This information is passed on the interfaces like Gx, Gy, and Ga. Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or outage.

Typically, these conditions are temporary i. However, continuous or large numbers of these error conditions within a specific time interval may be indicative of larger, more severe issues. With this capability, the operator can configure threshold on these resources whereby, should the resource depletion cross the configured threshold, a SNMP Trap would be sent. Alert : A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval.

Alarm : Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. Generation of specific traps can be enabled or disabled on the chassis. Ensuring that only important faults get displayed. Logs : The system provides a facility called threshold for which active and event logs can be generated.

As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING. Logs are supported in both the Alert and the Alarm models. Alarm System : High threshold alarms generated within the specified polling interval are considered "outstanding" until a the condition no longer exists or a condition clear alarm is generated.

The Alarm System is used only in conjunction with the Alarm model. For more information on threshold crossing alert configuration, refer Thresholding Configuration Guide.