The MSC/SSP contains definitions that have influence on the IN Service activation or the SSF-SCF relationship. The data contains:
PRFILE parameters:
SSN_FOR_INAP_CS1 (026:013)
The parameter defines the subsystem number (SSN) for INAP CS-1 signalling. With this parameter it is possible to configure different SSN for SCCP level Calling Party Address and SCCP level Called Party Address.
The lowest two bytes define the SSN of the SCCP level Calling Party
Address. The highest two bytes define the SSN of the SCCP level Called Party Address. If the highest two bytes are 0x00 then the lowest two bytes apply to both the SSN of the SCCP level Called Party Address and Calling Party Address.
. DEFAULT_CHRG_ZONE (001:0044)
This parameter is used when the SCF provides new e-parameters with the SendChargingInformation operation, but does not provide the zone to be used. This value is stored in the CDR as the zone value.
Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.
. INTERMEDIATE_CHARGING (001:0075)
This parameter defines whether the intermediate charging is performed in various cases.
If the intermediate CDR is generated, an
intermediateApplyChargingReport is also sent to the SCF.
If the CDR is not generated, no ACR is sent to the SCF either.
. REC_PULSE_BUFFERING (001:0076)001:076 rec_pulse_buffering
This parameter indicates when the MPM message has to be reported to the SCF by the ENC operation if the SCF has requested the report by the RNC operation. The possible values are the following:
. Value 0: Sent immediately after the reception of pulses.
. Other value: Sent after receiving the number of pulses indicated by the value and at the end of the call.
. DEFAULT_CHRG_ZONE_B (001:0077)
If the SCF provides new e-parameters with the
SendChargingInformation operation for subscriber B charging in the TBCSM, but does not provide the zone to be used, this default value is stored in the CDR as the zone value.
Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.
. DEF_CHRG_ZONE_B_ROAM (001:0078)
If the SCF provides new e-parameters with the
SendChargingInformation operation for subscriber B charging in the G-BCSM, but does not provide the zone to be used, this default value is stored in the ROAM CDR as the zone value.
Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.
. SSF_FUNCTION_ON (002:0289)
If this parameter is set to FALSE, no InitialDP operation is sent to any SCF. In this case, the calls are normal calls without an IN service. However, the ongoing IN calls are handled as IN calls, that is, ERB operations are sent.
. SSF_DP_I_PREANALYZED (002:0419)
This parameter defines whether DP2 is encountered before or after the pre-analysis.
The default value TRUE means that DP2 is encountered after the pre-analysis.
If the values are set to FALSE, DP2 is encountered before the pre-analysis.
Exception: If the SCF has sent the CollectInformation (CI) operation in DP1 and armed DP2 as EDP-R, the EDP2 encountering does not depend on the parameter at all, it is always met before the pre-analysis.
. INAP_AC_IN_USE (002:0446)
If this parameter is set to FALSE, the Application Context is not used when a dialogue is invoked towards the SCF. The default is TRUE.
. SCCP_SEGMENTATION (002:0447)
If this parameter is set to the value TRUE, the SCCP level segmentation is used with the INAP. The default is FALSE.
. CS1_LAST_OP_IN_TC_END (002:0599)
If this parameter value is TRUE (default), the last operation (the ERB-N or the ACR) is sent in the TC_END message. If the value is FALSE, the last operation is sent in the TC_CONTINUE message.
. IMPLICIT_DISARMING_CS1 (007:0106)
The parameter indicates whether or not the implicit disarming of events in the Core Intelligent Network Application Protocol
Capability Set 1 (CoreINAP CS-1) is possible (as a default, implicit disarming is not used), see Feature 739: IN: CS-1 Core INAP, Feature Description, version 3.
. SSF_MPC_ALLOWED (007:0108)
The parameter generally states whether or not the multiple point of control principle in an Intelligent Network is available. The default value is 'FALSE', which means that as long as any controlling IN service is active, no new controlling IN service can be started.
. SSF_MSDP_ALLOWED (007:0110)
The parameter generally states whether multiple controlling IN services can be served in a single DP. The default value is FALSE, which means that only one controlling IN service (the EDP-R or the TDP-R) is allowed to be served in a single DP.
. DEDICATED_IN_EVENT_CODE (007:0128)
This parameter indicates whether or not the dedicated IN Event Codes are used for Connect operations. With the parameter value TRUE, the INAP Connect operation uses Event Code 1043. With value FALSE, the default Event Code 1028 is used.
. CAMEL_ACTIVE (041:0002)
The parameter controls whether the CAMEL functionality is ON (active) or OFF (inactive) in the network element (MSC/VLR, HLR).
The parameter also indicates the CAMEL phase, either 1, 2, 3, or 4.
Fixed values for various limits:
The maximum number of service activations (InitialDP operations) in one BCSM is 10.
When the limit is reached, no new IN service is triggered, even if an armed trigger is encountered.
Trigger Data:
The trigger record contains the information for one triggering to the SCF. It includes the following data, which has an influence on the IN service activation or execution:
SKEY: The ServiceKey that is sent to the SCF in the InitialDP operation with the ServiceKey parameter.
ST: The Status of the Trigger. If the trigger is deactivated, that specific triggering does not take place and that the IN service is not initiated. It is possible that even in the same DP there is another active trigger that causes the initiation of an IN service.
PRT: The Priority of the trigger. Defining several triggers to the same DP should be avoided because the service interaction is usually not able to foresee them in the SSF. If several triggers are defined, priority decides which service is started. If a service is triggered, the other triggers no longer cause triggering in the same DP visit. But they can cause triggering if the same DP is encountered again later on in the same call.
DP: DP defines the DP in which an IN Service must be triggered. Triggering in the proper DP is essential for many IN services.
BCSM: The type of the BCSM. This parameter indicates from which model the triggering takes place. For DPs 1...10, 'OBCSM' is the default and the only allowed value. For DPs 12...18, the default is 'TBCSM' and, in this case, the triggering takes place in the TBCSM in the Visited MSC/SSP. The other choice is 'GBCSM':
the triggering then takes place in the TBCSM in the Gateway MSC/SSP. The value 'ANY' means that the triggering takes place both in the GBCSM and the TBCSM.
FOP: If the SCF-SSF communication terminates in an error, the SCF is not aware of how the call continues.
In this case, the way the call continues is determined by the SSF with the FailureOperation (FOP)
information included in the trigger.
AP: AP specifies the used Application Protocol. The default value is INAP.
ND: Number of Digits: a trigger condition. It defines the minimum number of digits that has to be collected before the triggering to the SCF takes place.
STRING: Digit String: a trigger condition. This triggering condition contains the Type of Number and 1 to 10 digits that are compared to the called party number.
The triggering can take place if the trigger condition matches the called party number.
NOT_STRING: Not Digit String: a trigger condition. This triggering condition contains the Type of Number and 1 to 10 digits, which are compared to the called party number. The triggering can take place if the trigger condition does not match the called party number.
CALLING_PARTY:
CallinG Party: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if the TON or both of the trigger conditions match the calling party number. If the TON is the only criterion, the calling party number can be anything.
NOT_CALLING_PARTY:
Not CallinG Party: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if neither the TON nor any of the trigger conditions matches the calling party number. If the TON is the only criterion, the calling party number can be anything.
VLR_ADDRESS: VLR address: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the VLR address.
The triggering can take place if the TON or both of the trigger conditions match the VLR address. If the TON is the only criterion, the VLR number can be anything.
The VLR address is always an international number.
The VLR_ADDRESS trigger condition is valid only in the Gateway terminating BCSM.
NOT_VLR_ADDRESS:
Not VLR address: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if neither the TON nor any of the trigger conditions matches the VLR address. If the TON is the only criterion, the VLR number can be anything. The VLR address is always an international number. The NOT_VLR_ADDRESS trigger condition is valid only in the Gateway
terminating BCSM.
C1...C5: Cause value: a trigger condition. The triggering can take place if any of the defined cause values matches the cause of the clear code found in the call.
TIME: Time Out value: a trigger condition. It defines the time after which the triggering can take place. It is intended to be used in the 'No_Answer' DP.
OPER: Criteria Operation. It indicates the logical operation that is used between the trigger criteria defined for a trigger. The possible values are 'AND' and 'OR'.
The following table summarises the possible uses of the Trigger Criteria listed above:
ND STRING NOT STRING
C1...C5 TIME CGP NCGP VLR NVLR
TDP1 Yes yes yes yes yes
TDP2 Yes yes yes yes yes
TDP3 Yes yes yes yes yes
TDP4 yes yes yes yes yes
TDP5 yes yes yes yes yes
TDP6 yes yes yes yes yes yes
TDP7 yes yes yes yes
TDP8 yes yes yes yes
TDP9 yes yes yes yes yes
TDP10 yes yes yes yes yes
Table 44. The possible uses of the Trigger Criteria
ND STRING NOT STRING
C1...C5 TIME CGP NCGP VLR NVLR
TDP12 yes yes yes yes yes yes
TDP13 yes yes yes yes yes yes yes
TDP14 yes yes yes yes yes yes yes yes
TDP15 yes yes yes yes yes yes
TDP16 yes yes yes yes yes yes
TDP17 yes yes yes yes yes yes yes
TDP18 yes yes yes yes yes yes yes
AL: SCP Address Location. This parameter indicates how the SCP address is determined. The possible values are 'T' = the GT address from the Trigger Data, 'A' = use the calling party address (or redirecting party address when available), and 'B' = use the called party address of the call.
Note that if in DP1 the Nature of Address of the GT address (derived from the B-number) is 'unknown', it is automatically converted to the 'subscriber' for the SCCP GT analysis.
GTI: The Global Title Indicator parameter is used to select the SCCP analysis root.
TT: The Translation Type parameter is used to select the SCCP analysis root.
GT: If the AL parameter has the value 'T', this parameter contains the SCP address. With other AL parameter values, this parameter has no meaning. The address of the SCP where the InitialDP is sent is always in the Global Title format.
NP: The Numbering Plan parameter is used to select the SCCP analysis root. This parameter can only be used if the AL value is 'T'.
NAI: The Nature of Address parameter is used to select the SCCP analysis root. This parameter can only be used if the AL value is 'T'.
AC: Use Application Context. This parameter indicates whether the Application Context is included in the TC INVOKE message when the IDP operation is sent to the SCP. By default, the AC is sent. The use of the AC can be denied by the INAP_AC_IN_USE
(002:0446) PRFILE parameter, seeMSC/SSP Core INAP configuration data.
STMR: Short Timer. This time value is used as the initial value for the Tssf when the SSF-SCF relationship is started.
MTMR: Medium Timer. This time value is used as an initial value for the Tssf when the SRF-SCF relationship is started.
OMPC: Operation in a Multiple Point of Control environment.
This parameter determines if the service can function in a multiple point of control environment.
STOC: Starting of Other Controlling services. This parameter determines if the service restricts the starting of new controlling services in the same BCSM.
OMCS: Operation of Multiple Controlling Service requests in the same DP. This parameter determines if the service can be started if another controlling service has been served in the same DP before it.
SEOC: Serving of Other Controlling service requests in the same DP. This parameter determines if the service restricts the serving of other controlling services in the same detection point after the service itself has been served.
TD: Trigger Deactivation. This parameter determines if the lifetime of the trigger can be restricted with the FIM mechanisms.
MSC software release information to SCP
The MSC software release information is packed to the TC Begin towards the SCP. This functionality allows the SCP to detect the dialogue initiator capabilities, for example, during the software upgrade phase.
The TC Begin DialoguePortition dialogueRequest user information field carries the MSC software release information coded as follows:
SwRelease ::= IA5String (SIZE(2...10)) m14 SwRelease ::= '4D3134'H