1. Release Notes
  2. Feature Descriptions

2 Feature Descriptions

This chapter provides a summary of each feature released in DSR release 8.5.1.0.0.

Release 8.5.1.0.0

This sections summarizes all the new and enhanced features in DSR, vSTP, VNFM, and SCEF.

DSR

The following DSR features are implemented in release 8.5.1.0.0:
  • FABR with UDR: The Full Address Based Resolution (FABR) application supports sending ComAgent stack events to User Data Repository (UDR), Network OAM (NOAM). FABR with UDR supports bundling and non-bundling cases. DSR can select Subscriber Database Server (SDS) or UDR as the database type for FABR queries. For more information about FABR, see the following guides:
    • Oracle Communications Diameter Signaling Router Diameter User Guide
    • Oracle Communications Diameter Signaling Router Full Address Based Resolution User Guide
    • Oracle Communications Diameter Signaling Router Operations, Administration, and Maintenance Guide.
    • Oracle Communications Diameter Signaling Router Measurement Reference Guide
  • Increase the number of Route Groups per Route List from 3 to 5: The number of Route Groups per Route List has increased from 3 to 5. The user can configure 5 Route Groups per Route List. This configuration is supported from both GUI and MMI. For more information, see the following guides:
    • Oracle Communications Diameter Signaling Router Diameter User Guide
    • Oracle Communications Diameter Signaling Router Operations, Administration, and Maintenance Guide.
  • Support more than 20 applications in CER-CEA messages: Earlier DSR was supporting only 10 Application IDs in CER/CEA. The user could configure only 10 Application IDs per CEX configuration set. By implementing this feature, DSR now supports 20 Application IDs in CER/CEA. For more information, see the following guides:
    • Oracle Communications Diameter Signaling Router Diameter User Guide
    • Oracle Communications Diameter Signaling Router Operations, Administration, and Maintenance Guide.

VNFM

The following VNFM feature is implemented in release 5.3.1:

  • Segregation of OAM and Replication Traffic Support: This feature supports the following:
    • Separate network for OAM and Replication traffic
    • Supports DSR NOAM, DSR DR NOAM, and Signaling VNFs
    Replication traffic is optional for a user where it can be used as Inter-NE network (xmiRepl), Intra-NE network (imiRepl), or both or None. xmiRepl/imiRepl and xmi/imi supports single, dual, and mix mode subnet, where both OAM and Replication service network can be on IPV4 or IPV6. For more information, see VNFM Installation and User Guide.
The following VNFM features are implemented in release 5.3.0:
  • VNFM Get Operation Status: VNFM supports the SOL003 operation Get Operation Status. The NFVO invokes Get Operation Status from VNF Life cycle management operations towards VNFM. VNFM queries the VNF for all life cycle management operation occurence. For more information, see VNFM Installation and User Guide.
  • VNFM to support vSTP Service MP deployment: By implementing this feature, VNFM deploys the Service MP along with vSTP-MP only and Service MP deployment is optional. vSTP-MP can be independently deployed without service MP. For more information, see VNFM Installation and User Guide.

vSTP

The following vSTP feature is implemented in release 8.5.1.0.0:
  • Support for eLYNX PCIe Card: Starting with this release, vSTP supports Time Division Multiplexing (TDM) through eLYNX PCIe Card. vSTP allows the eLYNX configurations through the vSTP Graphical User Interface (GUI).

    Note:

    The following points must be considered while configuring the eLYNX Card:

    • The eLYNX card supports only E1 traffic.
    • eLYNX is supported when installed in Oracle X8-2 and X8-2L servers.
    • A maximum of 4 eLYNX cards per server are supported.
    • PCI slots 5 and 6 are not supported for eLYNX on the Oracle X8-2L servers.
    • Only 1 eLYNX card per Message Processor (MP) is supported.
    • The eLYNX card is rated to process a maximum of 10K messages per second. If the ingress message rate crosses the 10K per second limit, the eLYNX card gets locally congested, causing all the links on the eLYNX card to go out of service until the congestion condition abates. After the congestion condition clears, the eLYNX card starts the link alignment process again.
    If the congestion persists for too long, the eLYNX card can be impacted severely. Some links may not recover automatically. If this happens, then the eLYNX card musr be reset or reloaded to recover.

    For more information about the eLYNX configurations, see vSTP User Guide.

    For more information about eLYNX installation, see vSTP eLYNX Installation Guide

  • vSTP GTT Throttling Enhancements: The vSTP SS7 security firewall is enhanced to support a new GTT Action for Egress throttling of individual GTT messages. The Indv_Throt action is added to provide support for Egress throttling of individual messages in a group. For more information, see vSTP SS7 Security User Guide.

  • vSTP CAP/INAP Filtering: Starting with this release, vSTP supports the GTT translations based on CDPN, BCD CDPN, and SK+BCSM with the CAP/INAP filtering feature. It provides the following Opcodes to support CAP/INAP filtering:

    • Initial DP
    • IDPSMS
    • IDPGPRS
    For more information about the feature configurations, see vSTP User Guide.

  • vSTP UDTS Routing: vSTP supports the routing of vSTP generated UDTS messages, based on Originating Point Code (OPC) of the incoming SCCP request or message. This provides an additional capability to the existing vSTP functionality wherein UDTS response messages generated by vSTP can be routed to originator, based on OPC of incoming UDT Message.

    For more information about the feature configurations, see vSTP User Guide.

  • ENUM Support: DSR 8.5.1 is enhanced to support the ENUM functionality to access Unified Data Repository (UDR) using the ENUM protocol. The newly added ENUM application in DSR supports the ENUM interface on UDP with the bind9 software. For more information about the DSR ENUM Application, see DSR ENUM User Guide.

SCEF

The following SCEF features are implemented in release 8.5.1.0.0:
  • SCEF Reliable Data Transfer: The Reliable Data Service is used by the UE and SCEF when using PDN Connection of PDN Type Non-IP. This service provides a mechanism for the SCEF to determine if the data was successfully delivered to the UE and vice-versa. For more information, see SCEF User Guide.