Page Chapter Point

6 Assemptions Post upgrade thorough testing will be performed by

Orange or aligned testing team by Orange
6 Pre-requistes Prerequisites 3 & 4
7 Existing artchitecture 3PP Integration

8 Proposed solution Interfaces file

15 3.4 General Impacts in SSH is used for MML communication for security
CS18.1 R25A purposes.
16 Changed interfaces when Atomic is set to true in Service Configuration, then
while sending Final-Unit-Indication, SDP sends the CC-
Total-Octets, CC-Input-Octets, and CC-Output-Octets
Diameter AVPs based on the Unit field configured for a
service under Service Configuration. Earlier these
Diameter AVPs were always sent.

17 Discontinued functions The following functions are not visible in the Function
Manager window:
• LicenseUsageAlarm
• UsageStatisticLogging
• UsageStatisticAlarm

21 3PP Version ESA upgrade from 4.0.5.2375 to 17.0.0.100

enhancements
21 Java upgrade from 1.7.0_95 to 1.8.0_131

22 Security As the part of security hardening on RHEL, world writable

directories (permission 777) will now have sticky bit set
on them. Only the user or the group users who own the
directory will be able to modify (move/delete) the
directory contents. Tools or applications that use these
directories or its contents using OS user will be impacted.
For example, Signaling Manager (SM) GUI, which uses OS
user to update the configuration, will be impacted.

24 Impact on existing Active SDP function file

functions

26 Detailed DRPL Level General

changes

Global Global

Global Global
Comment Comment holder
the UAT need to be applied with support of supplier SI Yacine

Change AIR by SDP Yacine

Update need to be done for the below points: Yacine
1-The provisioning is done through AIR UCIP/ACIP
interface, MINSAT CCAPI is no more used.
2-XML IVR is not part of OTN CS architecture
3-SDP has a MAP integration with VAS USSD-GW as well
as HLR.
4-There is no direct CDR FTP to mediation from CCN &
OCC, the CDR goes first to NGCRS then NGCRS distribute
it to mediation through custom scripts
5-NGCRS is not receiving CDRs from mediation
6-NGCRS has two UAH API integration: 1-with MINSAT 2-
with API history Gateway (3PP node)

the comments is on the dedicated file Yacine

what is the impact on the current MML interface Yacine

IS there any impact on diameter interface with 3PP for Yacine

the Atomic service volume unit

the LicenseUsageAlarm & UsageStatisticAlarm are not Yacine

activated on current version so what is the impact of
those features

is there any impact on NAGIOS interface due to this Yacine

upgrade
is it possible to distibute RMA trees from SDPTB once Yacine
upgraded to SDP prod before upgrade (this situation
happens once the SDPTB is upgraded and SDP prod not
yet upgraded)

what is the real impact on Signaling Manager GUI and Yacine

what is your recommendation

*the function UsageStatisticLogging is still available and Yacine

it activated by default
*what is the impact of the non-availability of
BalanceAfterCall feature ?

The CDR impact from the current DRPL version to the Yacine
target DRPL version need to be grouped in one table,
and only the standard parameters with the activated
feature/PC parameters need to be included in the table.

In the document there is no recomendation or action Yacine

plan related to a highlighted impact, only the impact is
highlighted, the document should highlight the impact
with its related action plan to manage the impact

A dimensioning excercice need to be included Yacine

Page Chapter Point
7 Assemptions Post upgrade thorough testing will be performed by
Orange or aligned testing team by Orange
7 Pre-requisites There should not be any other activities planned on
AIR/AF during upgrade. All new product
configurations should be kept under hold till the time
all AIRs are upgraded.

8 Existing 3PP Integration

artchitecture

15 Licenses Expired licenses are not granted any grace period.

Earlier such licenses were granted a 15 days grace
period after expiry.
16 Java upgrade to 1.8.0_131

Function
Updates in
Charging
16 System 18 ESA upgrade to 17.0
16 SS7 Upgrade
22 Capacity and On the HPE ProLiant DL360 Gen9 physical server, a
performance drop of around 7% is observed. Deployment Variants
(DV) instances must be re-evaluated before the
upgrade.

34 Impact on Existing function file

existing
functions
59 AIR Output General
CDR changes
Comment Comment holder
The UAT need to be applied with support of supplier SI Yacine

Is the business configuration should be in freez during all Yacine

upgrade period ?if yes, this need to be discussed

Update need to be done for the below points: Yacine

1-The provisioning is done through AIR UCIP/ACIP interface,
MINSAT CCAPI is no more used.
2-XML IVR is not part of OTN CS architecture
3-SDP has a MAP integration with VAS USSD-GW as well as HLR.
4-There is no direct CDR FTP to mediation from CCN & OCC, the
CDR goes first to NGCRS then NGCRS distribute it to mediation
through custom scripts
5-NGCRS is not receiving CDRs from mediation
6-NGCRS has two UAH API integration: 1-with MINSAT 2-with
API history Gateway (3PP node)

is there any alarms raised before license expiry to prevent such Yacine
situation ?

is it possible to distibute RMA trees from AIRTB once upgraded Yacine

to AIR prod before upgrade (this situation happens once the
AIRTB is upgraded and AIR prod not yet upgraded)

is there any impact on NAGIOS interface due to this upgrade ? Yacine

Any impact on the 3PP integration ? Yacine
A dimensioning excercise need to be performed to get the AIR Yacine
capacity

What is the impact of the non-availability of the activated Yacine

feature after upgrade ? Is there any evaluation in this sens ?

The CDR impact from the current DRPL version to the target Yacine
DRPL version need to be grouped in one table, and only the
standard parameters with the activated feature/PC parameters
need to be included in the table.