Escolar Documentos
Profissional Documentos
Cultura Documentos
www.pt.com
Introduction
In todays Signaling architecture, SIGTRAN capabilities are being used to overcome bandwidth constraints, reduce signaling transport cost, and to position the network for migration to the Next-Generation Network (NGN). A full understanding of the utilization and implementation of SIGTRAN is required to efficiently design a network suitable for the transport of SS7 Signaling over IP. The major stumbling block to fully understanding SIGTRAN is that all available explanations relate to next-generation architecture, including Media Gateway Controllers (MGC), Media Gateways (MG), and Signaling Gateways (SG), with very little information regarding the traditional network elements or network topology. This paper will focus on the SIGTRAN Adaptation Layers. A cursory overview of SCTP is provided in this paper; however detailed SCTP information will be covered in a subsequent white paper. Included in this paper will be detailed discussions on network topology, impact on existing infrastructure, and the benefits of each adaptation layer.
As traffic, messaging, and services are increasing, carriers are being tasked with reducing cost. The Insight Research Corporation study finds that Traditional carriers are seeing increased operating expenses cutting into margins and revenue growth. With network and network development costs typically accounting for more than 35 percent of fixed-line operating costs, telecom service providers are under pressure to reduce their network-related expenses to sustain margins. 3 A recent study conducted by Venture Development Corporation, SS7 Market Opportunities and Requirements: Global Market Demand Analysis, shows shipments of SIGTRAN stacks to rise 22% between 2006 and 2012.4 This increase is from USD15.9 Million in 2006 to USD 53.1 Million in 2012. This represents a shift away from legacy SS7 protocol stack shipments leading to the conclusion that SS7 networks are rapidly migrating to SIGTRAN.
History
The SIGTRAN working group of the Internet Engineering Task Force (IETF) was formed in 1999 and tasked with defining the architecture for transporting real-time signaling information over an Internet Protocol (IP) network. The working groups effort yielded three key results: 1) A new network architecture. 2) New transport protocol. 3) Numerous adaptation layers. This architecture framework centered on a restructuring of the circuit switch into distinct parts: Media Gateway Controllers (MGCs), Media Gateways (MGs), and Signaling Gateways (SGs).
The second characteristic of the new switching architecture is a total separation of signaling from the media and the media control plane. This three-layer split in network switching functionality was originally defined in IETF RFC 2719 Framework Architecture for Signaling Transport. RFC 2719 provided the following definitions for the MGC, MG and SG. Media Gateway (MG) A MG terminates switched circuit network (SCN) media streams, packetizes the media data, if it is not already packetized, and delivers packetized traffic to the packet network.5 Media Gateway Controller (MGC) A MGC handles the registration and management of resources at the MG. The MGC may have the ability to authorize resource usage based on local policy. For signaling transport purposes, the MGC serves as a possible termination and origination point for SCN application protocols.6 Signaling Gateway (SG) An SG is a signaling agent that receives/sends SCN native signaling at the edge of the IP network. The SG function may relay, translate, or terminate SS7 signaling in an SS7-Internet Gateway. The SG function may also be co-resident with the MG function to process SCN signaling associated with line or trunk terminations controlled by the MG.7 RFC 2719 also states that each of these functions can be deployed as separate entities or the MG and MGC, or the SG and MG may be combined. The IETF provided a high degree of network flexibility with these definitions. However, there is no mention in RFC2719 about: legacy networks, legacy network elements, or hybrid networks where both new and old network elements coexist. This concept will be clarified as we increase our understanding of the SIGTRAN protocol including transport and adaptation layers.
5 Internet Engineering Task Force (IETF) RFC 2719 October 1999 6 Internet Engineering Task Force (IETF) RFC 2719 October 1999 7 Internet Engineering Task Force (IETF) RFC 2719 October 1999
Reliable Data Transfer. Multiple streams to help avoid head-of-line blocking. Ordered and unordered data delivery on a per-stream basis. Bundling and fragmentation of user data. Congestion and flow control. Support for continuous monitoring of reachability. Graceful termination of association. Support of multi-homing for added reliability. Protection against blind denial-of-service attacks. Protection against blind masquerade attacks.
These requirements and more were addressed (or resolved) by the SIGTRAN working group in RFC 2960, Stream Control Transmission Protocol, and further updated by RFC 3309, Stream Control Transmission Protocol (SCTP) Checksum Change. SCTP can be used for the transmission of any real-time sensitive, sequenced delivery protocol, and as such is not limited to SS7 related data. The relationship of SS7 levels and IP/SIGTRAN layers is shown in Figure 1.
SS7
MTP 3 MTP 2 MTP 1
SIGTRAN
ISUP MTP 3 M2PA M2UA IP
M3UA SCTP
Adaptation Layers
The general function of adaptation layers is to encapsulate upper levels of the SS7 protocol and transport them over IP utilizing the services of SCTP.8 Because each adaptation layer is based on the SS7 level being transported or replaced, there are common capabilities across all adaptation layers. Each adaptation layer must provide:
u u
A seamless operation of SS7 level peers over an IP network. A primitive interface boundary that the corresponding SS7 level had with its underlying SS7 level. Management of SCTP transport associations and traffic between Signaling Gateways (SGs) and IP Signaling Endpoints (ISEPs) or two ISEPs. Asynchronous reporting of status changes to management functions.
The goal of each of the adaptation layers is to replace an existing SS7 level with an adaptation layer which utilizes the services of SCTP/IP. This replacement should be accomplished without any modification to the SS7 level being transported by
8 Internet Engineering Task Force (IETF) RFC 4166 February 2006
the adaptation layer. To accomplish this function, the adaptation layer must communicate with the carried SS7 level in exactly the same manner as SS7 would, i.e. through using the same primitives.
Data retrieval to support the MTP3 changeover procedure. Reporting of link status changes to MTP3. Processor outage procedure. Link alignment procedure.
As indicated by the functions of M2PA, the SCTP associations in an M2PA environment are treated as SS7 links over IP.
MTP Level 2, and the MGC will terminate MTP Level 3 and above. In other words, the SG will transport MTP Level 3 messages over an IP network to an MGC.10 M2UA employs a client server concept. The client side of M2UA has the resident MTP3 with its SS7 Point Code. The server functionality provides the SS7 physical termination and communicates with the client side using SCTP over IP. There are two main functions of M2UA. First, it provides a mechanism for the transport of SS7 MTP2 user signaling (e.g., MTP3 messages) over IP using SCTP. Second, it allows remote termination of SS7 links for the backhaul of traffic to a centralized node in the network. Functions provided by M2UA are:
u u u u
Flow Control. SCTP Stream Management. Seamless SS7 Network Management Interworking. Active Association Control.
Transfer of SCCP user part messages (TCAP, MAP, RANAP, etc.). SCCP Connectionless Services. SCCP Connection Oriented Services. SCCP management services Remote Destinations Subsystems Distributed IP-based Signaling Nodes.
Routing
Implementation Complexity
10
SSP
Edge STP
M2PA
Core STP
MSC
IP Network
M2PA
SSP
M2PA
11
SSP
Edge Device
Core STP
MSC
IP Network
M2UA
SSP
M2UA
Link alignment (normal and Emergency). Changeover and Changeback. Processor outage. Congestion, etc.
Core STP to Soft Switch M3UA was chosen for communication between the Core STP and the Soft Switch based on the efficiency of the protocol stack and the types of traffic generated by the switch. ISUP and TCAP over SCCP are generated by switching elements whether they are MSCs, Tandem switches, wireline offices, or Soft
12
Switches. These traffic patterns limit the choice of SIGTRAN connectivity to M2PA, M2UA, or M3UA. M3UA was chosen because it transports both ISUP and SCCP with the added benefit of being more efficient than M2PA due to the absence of a protocol stack level. Core STP to SCP SUA was the selected adaptation layer going from the Core STP to the SCP for the following reasons: It will transport TCAP traffic. It has lower overhead than M3UA. It requires less configuration than M3UA.
u u u
Core STP to Edge Device When aggregating network element connectivity based on topology or geography, M2UA is the adaptation layer of choice based on the following benefits: No valuable Point Code resources required. Easy to implement, i.e. few switch or STP translations to change. Transparent to the network. SS7 routing centralized in Core STP.
u u u u
The driving factor in this network implementation is to achieve signaling transport with significant cost savings, through aggregation and transport over IP. Core STP to Edge STP M2PA is implemented between the Core STP and the Edge STP because local routing is desired at the Edge STP. Local routing is desired because it adds an extra level of network survivability. If the Core STP or the connectivity between the Edge STP and the Core STP fails, intra Edge STP calls can then be completed based on local routing within the Edge STP.
13
SSP
MSC
SSP
SSP
Edge Device
M2PA
SUA
Core STP
IP Network
MSC
M2UA
SSP
M3UA
Softswitch
Core STP
Figure 4. Network Interconnectivity What to look for in SIGTRAN-enabled devices (Signaling Transfer Point, Signaling Gateway, and IP Edge) When looking for a source to provide SIGTRAN-enabled equipment for network deployment, consider the following requirements: Designed and architected for IP deployment: The revolution in the Signaling Network demands that more and more signaling traffic is placed on the IP network. It is critical to select equipment that is designed from the ground up as IP-centric. These capabilities should include, but not be limited to, the following: embedded IP capabilities (Back plane, Ethernet switches, high bandwidth, etc.), ease of IP connectivity, and ease of IP configuration.
14
High processing capabilities: With the ever increasing traffic on the Signaling Network due to Number Portability, SMS, Location Updates, etc., it is extremely important to select equipment that will process todays traffic loads and be extensible for future traffic requirements. SIGTRANs ability to efficiently relieve bandwidth bottle necks in the network makes it the ideal choice. Most cost-effective (initial purchase and life cycle): When selecting network equipment, it is extremely important to consider not only the initial purchase price, but also the ongoing support and maintenance of the equipment. The most economical combination of these two should be selected, assuming that all of the other requirements are met. Standards-based: Ensure that selected systems are designed to the latest protocol standards and have the widest breadth of protocols available. These protocols should include, but not be limited to the following: SS7 both ITU and ANSI SIGTRAN (M2PA, M2UA, M3UA & SUA) SIP
u u u
Most environmentally friendly: With todays focus on cost and environmental concerns, another important consideration is whether or not new equipment is the environmentally friendly. Two factors that should be taken into consideration are: 1. Least amount of power consumed. 2. Least amount of heat generated. Extensive Support Services: Explore companies that will partner with you for the long term. The company should provide network planning, network engineering, installation, training, and support services. These services should be on an a la carte basis, so only the required services need be selected.
15
16
international and domestic applications in wireless and wireline configurations all over the world, including the United States, Canada, France, United Kingdom, Netherlands, Brazil, Mexico, Japan, China, Africa and many others. A vast array of standards-based protocols are supported including: SCTP, M2PA, M2UA, M3UA and SUA. Also supported are traditional TDM, ATM and Annex A. For more information on PT and the SEGway signaling solutions or to schedule a demonstration, please contact sales@pt.com.
17
About PT (www.pt.com)
PT (NASDAQ: PTIX) is a global supplier of advanced network communications solutions to carrier, government, and OEM markets. PTs portfolio includes IP-centric network elements and applications designed for high availability, scalability, and long life-cycle deployments. The companys entire line of offerings is anchored by IPnexus, PTs own IP-native, highly integrated platforms and element management systems. OEMs and application developers, including PT itself, leverage the robust carrier grade Linux development environment and rich suite of communications protocols (PTs NexusWare) of IPnexus ApplicationReady Systems as a cornerstone component of their end product value proposition. PTs SEGway Signaling Solutions provide low cost, high density signaling, advanced routing, IP migration, gateway capabilities, SIP bridge, and core-to-edge distributed intelligence. The companys Xpress NGN applications enable evolving Mobile 2.0, Multimedia, and IMS based revenue generating services. PT is headquartered in Rochester, NY and maintains sales and engineering offices around the world.
PT is a trademark of Performance Technologies, Inc. The names of other companies, products, or services may be the trademarks, registered trademarks, or service marks of their respective owners in the United States and/or other countries.
18