| Oracle® Communications Service Broker Concepts Guide Release 5.0 Part Number E15180-01 |
|
|
View PDF |
| Oracle® Communications Service Broker Concepts Guide Release 5.0 Part Number E15180-01 |
|
|
View PDF |
Oracle Communications Service Broker Signaling Server Units (SSUs) manage Service Broker connectivity to external networks. For each network domain, a specific implementation of SSU handles the network connectivity functions. Service Broker includes the following SSUs:
The Signaling System #7 (SS7) Signaling Server Unit (SSU) enables Service Broker to access legacy SS7 network entities (for example, MSC and SCP).
The SS7 SSU is the Service Broker connectivity point to the network Signaling Gateways (SGs) or Signaling Transfer Points (STPs). Serving as the Service Broker frontend o the SS7 network, the SS7 SSU provides Service Broker with a point code, presenting it to the network as an SS7 signaling entity. Service Broker IMs that require an interface to the SS7 network (for example, IM-SCF and IM-SSF), use the SS7 SSU to send and receive SS7 messages to and from the SS7 network.
While the SS7 SSU supports the SS7 SCCP and lower protocol layers, the Service Broker IMs that interact with the SS7 SSU handle TCAP and higher SS7 protocol layers (for example, CAP and INAP).
Towards the SS7 network, the SS7 SSU presents a possibly redundant logical interface (one or more point codes) that has redundant physical interfaces. Redundancy is accomplished by deploying the SSUs in pairs (1+1 architecture). The redundancy model for the SSU is Active/Active with no single point of failure.
The SSU's role is to process low SS7 stack layers (up to SCCP) and distribute the traffic to the Service Broker IMs for processing.
To facilitate access to an underlying SS7 stack, Service Broker wraps the SS7 stack in an SS7 process, which is available to the SSU through a TCP connection.
SS7 SSU is available for two types of SS7 network connectivity, described in the following sections:
SS7 SSU over TDM provides Service Broker with connectivity to the legacy SS7 network over Time Division Multiplexing (TDM) physical infrastructure (i.e. PCMs) through the use of dedicated TDM signaling boards. Usually, SS7 SSUs are physically connected to STPs, but they can also be directly connected to MSCs, HLRs, etc.
SS7 SSU over TDM supports the following key functionality:
Support for MTP1, MTP2, MTP3 and SCCP SS7 protocol layers, as shown in Figure 4-1.
Alias-based addressing—An alias is assigned to every SS7 network entity. Applications use Service Broker to interact with legacy SS7 network entities by specifying the alias of the destination entities. The SS7 SSU converts the alias to an appropriate SCCP address that is used to route traffic in the SS7 network.
Global Titling (GT)—Supports GT address format.
SS7 SSU over SIGTRAN M3UA provides Service Broker with connectivity to the legacy SS7 network over an IP-based physical infrastructure, using the MTP3 User Adaptation Layer (M3UA). SS7 SSUs are physically connected to an IP network through Signaling Gateways (SGs).
SS7 SSU over SIGTRAN M3UA supports the following key functionality:
Support for IP, SCTP, M3UA and SCCP SS7 protocol layers.
Alias-based addressing—An alias is assigned to every SS7 network entity. Applications use Service Broker to interact with legacy SS7 network entities by specifying the alias of the destination entities. The SS7 SSU converts the alias to an appropriate SCCP address that is used to route traffic in the SS7 network.
Global Titling (GT) - Supports GT address format.
The SIP Signaling Server Unit (SSU) is a SIP frontend for Service Broker that provides access to SIP-based networks (for example, IMS) and the various SIP/IMS network elements (for example, CSCF, AS). Every Service Broker IM that requires a SIP interface (i.e. IM-ASF SIP, R-IM-ASF SIP) uses the SIP SSU as a sole route to send/receive SIP messages.
Redundancy of the SIP SSU is accomplished by deploying the SSUs in pairs (1+1 architecture).
The SIP SSU supports the following key functionality:
Alias-based addressing—An alias is assigned to every SIP network entity. Applications use Service Broker to interact with SIP network entities by specifying the alias of the destination entities. The SIP SSU converts the alias to an appropriate destination address that is used to route traffic in the SIP network. The same alias can be assigned to one or more SIP addresses, enabling alternative routing if one of the destinations is unreachable.
Heartbeat—The SIP SSU is actively checking SIP entities in the network using the SIP OPTIONS request to check their availability status. The status information is used when routing SIP traffic from Service Broker to the network.
Load balancing—When SIP traffic is designated to a certain address alias, the SIP SSU can divide traffic between more than one SIP address, providing load balancing between several SIP entities. Traffic is load balanced only between SIP entities that are known to be available, based on the heartbeat functionality.
The Diameter Signaling Server Unit (SSU) is a Diameter frontend for Service Broker, which provides access to remote Diameter entities (for example, OCS, HSS) in the IMS network. Every Service Broker IM that requires a Diameter interface (i.e IM-OCF), uses the Diameter SSU as a sole route to send and receive Diameter messages.
Redundancy of the Diameter SSU is accomplished by deploying the SSUs in pairs (1+1 architecture).
The Diameter SSU supports the following key functionality:
Alias-based addressing—An alias can be assigned to every Diameter network entity. Applications use Service Broker to interact with Diameter network entities by specifying the alias of the destination entities. The Diameter SSU converts the alias to an appropriate destination address that is used to route traffic in the network. The same alias is assigned more than one Diameter destination to enable alternative routing if one of the destinations is unreachable.
Heartbeat—The Diameter SSU holds a list of established Diameter transport connections and updates their status periodically. The status of connections is used when routing Diameter traffic from Service Broker to the network.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
