EAGLE

The EAGLE is a robust SS7-over-IP solution that delivers centralized signaling routing and bridges legacy circuit-switched and packet networks. EAGLE provides seamless interworking between TDM resources such as Service Control Points and IP-enabled elements such as Media Gateway Controllers and next-generation databases. With its packet-based technology, the EAGLE can handle signaling requirements of the most complex networks, delivering dynamic bandwidth sharing to support increases in signaling traffic without adding new nodes. The same platform delivers full Signal Transfer Point (STP) capabilities and a complete portfolio of integrated applications.

Using the EAGLE to structure the network provides a predictable and reliable architecture with all required interfaces. It is easily scalable to cover huge core networks, with an independent control layer that allows expansion on different parts of the network independent of each other.

The EAGLE provides ease of database management for the SS7-over-IP architecture. Key benefits of using the SS7-over-IP solution include:

• Decreased network congestion:. Oracle’s packet-switched technology delivers dynamic bandwidth sharing to enable carriers to effectively expand their signaling network and reduce network bottlenecks. By replacing TDM links with an IP interface, service providers can significantly increase signaling capacity to Service Control Points.
• Reduced transport costs: Replacing long-haul, point-to-point SS7 links between network elements with IP connectivity can reduce recurring signaling transport costs by 40% to 70%.
• More efficient networks: Transitioning to SS7-over-IP signaling does not require expensive equipment replacement or costly software upgrades for existing end nodes. With Oracle solutions, carriers can streamline their networks while reducing administration, without service interruption during installation.
• Migration to next-generation architecture: The EAGLE can appear as an end office to the SS7 network by sharing its point code with the IP endpoints. This allows carriers to migrate to a packet-based architecture without adding a new point code or reconfiguring the network. Oracle’s open, multi-protocol architecture (SS7, SCTP, M2PA, M3UA, and SUA) provides carriers the capability to grow and migrate their network with the independence to choose best-in-class products.

IPLIMx, IPGWx and IPSG applications

The EAGLE implements SIGTRAN with three applications:

• IPLIMx, which represents IPLIM for ANSI networks and IPLIMi for ITU-N and ITU-I networks
• IPGWx, which represents IPGWx for ANSI networks and IPGWi for ITU-N and ITU-I networks
• IPSG, which represents a unified application for both ANSI and ITU links on a single association

The IPLIMx application uses SCTP with M2PA protocols to support B-, C-, and D- links; but it can also be used for A-links to connect to SEPs on other vendor equipment that has M2PA SIGTRAN specifications implemented. IPLIMx is fully compliant with RFC 4165.

IPLIMx is installed on an E5-ENET, or E5-ENET-B card. Based on the card type, IPLIMx allows up to 16 links per E5-ENET or E5-ENET-B card, each with one SCTP association per link. IPLIMx can be implemented with just one card and expanded to 250 cards per system, as long as it does not exceed System TPS limitations (500k or 750k).

The IPGWx application uses SCTP with M3UA and SUA protocols to provide user part support such as SCCP and ISUP over A-links to IP-resident network elements such as Service Switching Points, Mobile Switching Centers, Service Control Points and Home Location Registers using SIGTRAN. Since IPGWx applications use M3UA/SUA to replace MTP3 functions, it cannot be used in mixed linksets of both M3UA/SUA and MTP3, as the application will not participate in any changeover/changeback procedure. IPGWx supports statically provisioned routing keys by selecting IP connections based on DPC/OPC/SI/CIC/SSN. The application also supports the End Office mode where the EAGLE shares its point codes with IP-remote applications. However, A-links for nodes requiring in-sequence delivery of messages should be configured on the IPLIMx application using M2PA; M3UA/SUA does not have sequence numbers to support lossless changeover/changeback procedures.

IPGWx is installed on an E5-ENET or E5-ENET-B card. IPGWx allows one link per card and up to 50 SCTP associations.The link terminates at a private adjacent point code. IPGWx is installed with just one card, and can be expanded to 250 cards per system, as long as it does not exceed System TPS limitations (500k or 750k).

The IPSG application uses SCTP with the M2PA protocol to support A-, B-, C-, D-links as previously mentioned for IPLIMx. It also uses SCTP with the M3UA protocol to support user part as IPGWx above. IPSG supports routing keys in the form of SS7 Routes referencing IPSG M3UA linksets, rather than as distinct ‘routing key’ managed elements or End Office capability as IPGWx does. IPSG is installed on an E5-ENET or E5-ENET-B card. IPSG can be implemented with just one card and expanded to 250 cards per system, as long as it does not exceed System TPS limitations (500k or 750k).

The IPSG feature provides conforming M3UA functionality that behaves more like other LIMs, providing the following benefits:

• The IPSG-application M3UA operational model equates Linkset (LS) and Application Server (AS). It equates a Signaling Link (SLK) with an AS-ASP (Routing Context + Association) instance. This allows each AS-ASP instance to be administered as a signaling link.
• A new signaling link type, IPSG-M3UA, can be assigned to linksets having up to 16 signaling links. This doubles the 8-link (and card) limitation of the current IPGWx linkset.
• Each IPSG card will host up to 128 signaling links.
• Each IPSG card will host up to 128 SCTP associations. A maximum of 16 IPSG-M3UA signaling links can be assigned to a single association.
• The adjacent point code (APC) of the IPSG-M3UA linkset is the point code assigned to the Application Server serviced by the linkset. The IPSG-M3UA linkset does not require a fake adjacent point code as the current IPGWx application does.
• Each IPSG-M3UA signaling link can have a single IP connection, unlike the current IPGWx signaling link which can have up to 50 IP connections.
• The state of the IPSG-M3UA signaling link will be based on the states of the assigned IP connection and AS-ASP instance. If the IP connection is unavailable for traffic, then the IPSG-M3UA signaling link will also be unavailable. If the AS-ASP instance is not available, then the IPSG-M3UA signaling link will also be unavailable.
• Multiple IPSG-M3UA signaling links (up to 16) can share one IP connection, as long as all of the IPSG-M3UA signaling links and corresponding IP connection are hosted by the same card. This enables multiple SS7 variant support across a single IP connection.