Important: Some of the features may not be available in this release. Kindly contact your local Cisco representative for more information on supported features.
• For more information on supported features, refer Features and Functionality sections.
•
• System Management Cards (SMC): Provides full system control and management of all cards within the ASR 5000 platform. Up to two SMC can be installed; one active, one redundant.
• Packet Services Cards (PSC/PSC2): Within the ASR 5000 platform, PSCs/PSC2s provide high-speed, multi-threaded EPS Bearer context processing capabilities for MME services. Up to 14 PSCs/PSC2s can be installed, allowing for multiple active and/or redundant cards.
• Switch Processor Input/Outputs (SPIOs): Installed in the upper-rear chassis slots directly behind the SPCs/SMCs, SPIOs provide connectivity for local and remote management, central office (CO) alarms. Up to two SPIOs can be installed; one active, one redundant.
• Line Cards: The following rear-loaded line cards are currently supported by the system:
• Ethernet 10/100 and/or Ethernet 1000 Line Cards: Installed directly behind PSCs, these cards provide the physical interfaces to elements in the LTE/SAE network. Up to 26 line cards should be installed for a fully loaded system with 13 active PSCs/PSC2, 13 in the upper-rear slots and 13 in the lower-rear slots for redundancy. Redundant PSCs/PSC2s do not require line cards.
• Quad Gig-E Line Cards (QGLCs):The 4-port Gigabit Ethernet line card is used in the ASR 5000 system only and is commonly referred to as the Quad-GigE Line Card or the QGLC. The QGLC is installed directly behind its associated PSC/PSC2 to provide network connectivity to the packet data network.
• 10 Gig-E Line Cards(XGLCs): The 10 Gigabit Ethernet Line Card is used in the ASR 5000 system only and is commonly referred to as the XGLC. The XGLC supports higher speed connections to packet core equipment, increases effective throughput between the ASR 5000 and the packet core network, and reduces the number of physical ports needed on the ASR 5000.
• Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots directly behind the SPCs/SMCs, RCCs utilize 5 Gbps serial links to ensure connectivity between Ethernet 10/100/Ethernet 1000/Quad Gig-E/10 Gig-E line cards and every PSC/PSC2 in the system for redundancy. Two RCCs can be installed to provide redundancy for all line cards and PSCs/PSC2a.Important: Additional information pertaining to each of the application and line cards required to support LTE/SAE services is located in the Hardware Platform Overview chapter of the Product Overview Guide.
• S1-MME Interface: This interface is the reference point for the control plane protocol between eNodeB and MME. S1-MME uses S1- Application Protocol (S1-AP) over Stream Control Transmission Protocol (SCTP) as the transport layer protocol for guaranteed delivery of signaling messages between MME and eNodeB (S1).
• S3 Interface: This is the interface used by the MME to communicate with SGSNs on the same Public PLMN for interworking between GPRS/UMTS and LTE network access technology. This interface serves as both the signalling and data path for establishing and maintaining subscriber UE contexts.
• S6a Interface: This is the interface used by the MME to communicate with the Home Subscriber Server (HSS). The HSS is responsible for transfer of subscription and authentication data for authenticating/authorizing user access and UE context authentication. The MME communicates with the HSSs on the PLMN using Diameter protocol.
• S10 Interface: This is the interface used by the MME to communicate with MME in same PLMN or on different PLMNs. This interface is also used for MME relocation and MME to MME information transfer or handoff.
• S11 Interface: This interface provides communication between MME and Serving Gateways (SGW) for information transfer using GTPv2 protocol.
• S13 Interface: This interface provides communication between MME and Equipment Identity Register (EIR). This interface is not supported in this release.
• S101 Interface: This interface provides communication between MME and High Rate Packet Data (HRPD) access node in a 3GPP2 network. It uses an application layer protocol S101-AP to enable interactions between Evolved Packet System (EPS) and HRPD access node to allow for pre-registration and handover signalling with the target system. The S101 interface supports procedures for pre-registration, session maintenance, and active handoffs between E-UTRAN and HRPD networks.
• DNS Interface: MME supports DNS interface to locate the S-GW in EPS core network. The MME uses the Tracking Area List as fully qualified domain name (FQDN) to locate the address of the S-GW to establish the call with.
• Gr Interface: This is the interface used by the MME to communicate with the Home Location Register (HLR) via a eGTP-to-MAP (Mobile Application Part) protocol convertor. This interface is used for network initiated UE contexts.Important: MME Software also supports additional interfaces. For more information on additional interfaces, refer Features and Functionality - Licensed Enhanced Feature Software section.
Important: To configure the basic service and functionality on the system for MME service, refer configuration examples provide in MME Administration Guide.
• 3GPP TS 36.412 V8.4.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Access Network (E-UTRAN); S1 signaling transport (Release 8)
• 3GPP TS 36.413 V8.4.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8)
• EMM Common Procedures: An EMM common procedure can always be initiated when a NAS signalling connection exists.
• EMM Specific Procedures: This procedure provides Subscriber Detach or de-registration procedure.
• EMM Connection Management Procedures: This procedure provides connection management related function like Paging procedure.
• 3GPP TS 29.274 V8.1.0 (2009-03): 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 (Release 8)Important: For more information on GTPv2 configuration, refer eGTP Service Configuration in MME Service Administration Guide.
Note: In the current release the IPv4 interfaces are used to provide connectivity to the TCE. Trace activation is based on IMSI or IMEI and only Maximum Trace Depth is supported in this release.For more information on this feature, refer Configuring Subscriber Session Tracing chapter in MME Service Administration Guide.
• 3GPP TS 23.401 V8.1.0 (2008-03): 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8)
• 3GPP TS 29.272 V8.1.1 (2009-01): 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol (Release 8)
• 3GPP TS 33.401 V8.2.1 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE): Security Architecture; (Release 8)
• EPS Bearer Identity: An EPS bearer identity uniquely identifies EPS bearers within a user session for attachment to the E-UTRAN access and EPC core networks. The EPS Bearer Identity is allocated by the MME. There is a one to one mapping between EPS Radio Bearers via the E-UTRAN radio access network and EPS Bearers via the S1-MME interface between the eNodeB and MME. There is also a one-to-one mapping between EPS Radio Bearer Identity via the S1 and X2 interfaces and the EPS Bearer Identity assigned by the MME.
• Globally Unique Temporary UE Identity (GUTI): The MME allocates a Globally Unique Temporary Identity (GUTI) to the UE. A GUTI has; 1) unique identity for MME which allocated the GUTI; and 2) the unique identity of the UE within the MME that allocated the GUTI.
• Tracking Area Identity (TAI): Provides the function to assign the TAI list to the mobile access device to limit the frequency of Tracking Area Updates in the network. The TAI is the identity used to identify the tracking area or group of cells in which the idle mode access terminal will be paged when a remote host attempts to reach that user. The TAI consists of the Mobile Country Code (MCC), Mobile Network Code (MNC) and Tracking Area Code (TAC).
• MME S1-AP UE Identity (MME S1-AP UE ID): This is the temporary identity used to identify a UE on the S1-MME reference point within the MME. It is unique within the MME per S1-MME reference point instance.Caution: Only if the operator or Operation and Maintenance system is sure that there is spare capacity in the rest of the pool, the operator or Operation and Maintenance system might use the load re-balancing procedure to move some load off an MME. However, extreme care is needed to ensure that this load re-balancing does not overload other MMEs within the pool area (or neighboring SGSNs) as this might lead to a much wider system failure.
•Important: MME management functionality is enabled by default for console-based access. For GUI-based management support, refer Web Element Management System.
Important: For more information on command line interface based management, refer Command Line Interface Reference.
• System: Provides system-level statistics
• Card: Provides card-level statistics
• Port: Provides port-level statistics
• MME: Provides MME service statistics
• GTPC: Provides GPRS Tunneling Protocol - Control message statistics
• GTPU: Provides GPRS Tunneling Protocol - User message statistics
• 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. The alert is generated then generated and/or sent at the end of the 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. The alert is generated then generated and/or sent at the end of the polling interval.
• SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values.
• 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.
• 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. “Outstanding” alarms are reported to the system's alarm subsystem and are viewable through the Alarm Management menu in the Web Element Manager.Important: For more information on threshold crossing alert configuration, refer Thresholding Configuration Guide.
Important: Some of the following features require the purchase of an additional license to implement the functionality with the MME service.
• Task recovery mode: Wherein one or more session manager failures occur and are recovered without the need to use resources on a standby packet processing card. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active packet processing cards. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager.
• Full packet processing card recovery mode: Used when a PSC or PSC2 hardware failure occurs, or when a packet processing card migration failure happens. In this mode, the standby packet processing card is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated packet processing card perform session recovery.Important: For more information on session recovery support, refer Session Recovery chapter in System Enhanced Feature Configuration Guide.
• PDN Access: Subscriber IP traffic is routed over an IPSec tunnel from the system to a secure gateway on the packet data network (PDN) as determined by access control list (ACL) criteria.
• Mobile IP: Mobile IP control signals and subscriber data is encapsulated in IPSec tunnels that are established between foreign agents (FAs) and home agents (HAs) over the Pi interfaces.Important: Once an IPSec tunnel is established between an FA and HA for a particular subscriber, all new Mobile IP sessions using the same FA and HA are passed over the tunnel regardless of whether or not IPSec is supported for the new subscriber sessions. Data for existing Mobile IP sessions is unaffected.
• L2TP: L2TP-encapsulated packets are routed from the system to an LNS/secure gateway over an IPSec tunnel.Important: For more information on IPSec support, refer IP Security chapter in System Enhanced Feature Configuration Guide.
Important: For more information on Lawful Intercept support, refer Lawful Intercept Configuration Guide.
Important: For more information on inter-chassis session recovery support, refer Interchassis Session Recovery chapter in System Enhanced Feature Configuration Guide.
Important: MME management functionality is enabled by default for console-based access. For GUI-based management support, refer Web Element Management System.
• PDN Type: The system supports IPv4, IPv6, or IPv4v6.
• Timeout: Absolute and idle session timeout values specify the amount of time that an MS can remain connected.
• Quality of Service: Parameters pertaining to QoS feature support such as for Traffic Policing and traffic class.
• User-initiated Transparent IP: An IP EPS Bearer context request is received by the MME from the UE for a PDN. The subscriber is provided basic access to a PDN without the MME authenticating the subscriber. Either a static or dynamic IP address can be assigned to the MS in this scenario.
• User-initiated Non-transparent IP: An IP EPS Bearer context request is received by the MME from the UE for a PDN. The MME provides subscriber authentication services for the data session. Either a static or dynamic IP address can be assigned to the MS in this scenario.
• Network-initiated: An IP EPS Bearer context request is received by the MME from the PDN for a specific subscriber. If configured to support network-initiated sessions, the MME, will initiate the process of paging the MS and establishing a EPS Bearer context.
14.
2. Optional. If UE in idle or dormant mode it will initiate Random Access procedure.
10.
•
•
•
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |