This chapter provides upgrade impacts information for Portal™ Release 7.3 to Oracle Communications Billing and Revenue Management (BRM) Release 7.3.1. It describes the feature changes that affect your Portal system, and what you must consider when you upgrade from 7.3 to 7.3.1.
For information on planning your upgrade implementation, such as setting up your development and test environments, see "About Upgrading BRM Releases".
This section discusses the changes made to the AAA Gateway Manager from Portal release 7.3 to BRM 7.3.1.
AAA Gateway Manager now supports the new versions of the message-based interface (MBI) protocol: HP-MBI protocol version 1.29 and HP-OCSAC CDR version 1.19. New message types are supported and changes have been made to the existing grammar to support the new versions of the MBI protocol.
The GSM requests are now mapped to the Services Framework AAA opcodes instead of to the GSM AAA opcodes as shown in Table 13-1. GSM-specific data are included in the EXTENDED_INFO block of the Services Framework AAA block.
Table 13-1 GSM Requests to Services Framework AAA Opcode Mapping
| GSM Request | Opcode Called |
|---|---|
|
Authorize_req Authorize_conf Authorize_reject |
PCM_OP_TCF_AAA_AUTHORIZE |
|
Reauthorize_req |
PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE |
|
End_req End_ack |
PCM_OP_TCF_AAA_STOP_ACCOUNTING If the reason for terminating the call is DESTINATION_BUSY, NO_ANSWER, CALLER_ABANDON, or SMS_FAILURE, PCM_OP_TCF_AAA_CANCEL_AUTHORIZATION is called. |
The MBI administrative messages shown in Table 13-2 are mapped to Services Framework AAA opcodes with the service type set to /service/telco to close all open sessions irrespective of the service sub-type:
The existing grammar and mapping files in the Pipeline_Home/formatDesc/Formats/MBI directory have been renamed as shown in Table 13-3:
The existing grammar and mapping files in the Pipeline_Home/formatDesc/Formats/MBI_CDR directory have been renamed as shown in Table 13-4:
To map MBI requests to the Services Framework AAA opcodes, the AAA EDR container has been changed as follows:
Input and output blocks for the following Services Framework AAA opcodes have been added:
PCM_OP_TCF_AAA_AUTHORIZE
PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE
PCM_OP_TCF_AAA_STOP_ACCOUNTING
PCM_OP_TCF_AAA_CANCEL_AUTHORIZATION
PCM_OP_TCF_AAA_ACCOUNTING_ON
PCM_OP_TCF_AAA_ACCOUNTING_OFF
GSM-specific data has been added in the EXTENDED_INFO.GSM_INFO block.
GPRS-specific data has been added in the EXTENDED_INFO.GPRS_INFO block.
Note:
The AAA EDR container includes input and output blocks for GSM AAA opcodes to support GSM requests in Diameter protocol and flist format, which are mapped to GSM AAA opcodes.The ASS_MBI_INFO and ASS_OCSAC_INFO blocks have been enhanced to support additional fields defined in the MBI v1.29 specification and the OCSAC CDR v1.19 specification respectively.
By default, the ServicesSupported entry in the mbi.reg file is commented. By default, all telco services (/service/telco) are supported. If you want to support only a specific service, for example GSM service, you can uncomment the ServicesSupported entry and specify a service, for example /service/telco/gsm.
The following iScripts and iRules used by the Timeout and Replay pipelines have been modified to map requests to Services Framework AAA opcodes:
ISC_GenericPostOpcode
ISC_TimeoutDefaultResponse
ISC_TimeoutPreZone
ISC_TimeoutProcessedResponse
ISC_ReplayPostOpcode
IRL_ReplayRouter
IRL_TimeoutRouter
IRL_Router
Note:
These iScripts and iRules map also to GSM AAA opcodes to support requests in Diameter protocol and flist format.This section discusses the changes made to the Pipeline Manager from Portal release 7.3 to BRM 7.3.1.
Pipeline Manager now uses business parameter settings (/config/business_params) from the BRM database rather than pipeline registry entries to determine whether optional BRM features and functionality are enabled. The DAT_PortalConfig module has been enhanced to retrieve business parameter settings from the BRM database at pipeline initialization and store them in internal memory. Other data modules that require business parameter settings retrieve them directly from the DAT_PortalConfig module's memory. For more information, see ”Using Business Parameter Settings from the BRM Database” in BRM System Administrator's Guide.
BRM no longer supports Vertex CommTax21. Vertex Communications Tax Q Series is now supported. Vertex plans to discontinue support for CommTax21 soon.
Communications Tax Q Series does not support the customization of DM Vertex to collect extra data. If you added or uncommented the extra_tax_data entry in the Vertex DM configuration file (BRM_Home/sys/dm_vertex/pin.conf), you should remove that entry.
In addition, Vertex Quantum is now called Vertex Sales Tax Q Series.
The names of the two BRM Vertex managers are unchanged:
Vertex Manager: Supports Vertex Sales Tax Q Series and Vertex Communications Tax Q Series.
Vertex Quantum Manager: Supports Vertex Sales Tax Q Series. This manager does not support Vertex Communications Tax Q Series.
Configuration file (pin.conf) entries and package names related to Sales Tax Q Series continue to include ”Quantum.”
This section discusses the changes made to the Telco Framework (Services Framework) from Portal release 7.3 to BRM 7.3.1.
Telco Framework (TCF) has been renamed to Services Framework. Likewise, TCF Manager has been renamed to Services Framework Manager, and TCF AAA Manager has been renamed Services Framework AAA Manager.
Note:
The Services Framework opcodes, objects, and utilities still continue to have ”TCF” in their names.