A SPECTOS ÉTICOS

5.3.1 IN supplementary service management procedures

One DP has been inserted into the supplementary service management procedures. One request-type trigger DP (TDP-R) is supported. When the TDP is met, the SSF contacts the SCF, and suspends the processing of the supplementary service management request.

The DPs can be located with the help of a state model. The state model for the supplementary service management procedure is defined in the HLR.

Figure 9. SS-DP1: SS management

5.3.2 Support of Core INAP operations in IN supplementary service management

The SCF-SSF operations defined by the Core INAP specification are presented in TableMobility Management state model in the VLR for the inter-VLR location registration. For further information, see ETS 300 374-1 . The indication whether the implementation of the SSP supports the operation in the Supplementary Service DP in the HLR is marked with:

O_Null & Receive_SS_Request

SS-DP1 SS-Management

Complete_SS_Request

S supported

NS not supported

Table 56. Support for SSF - SCF Core INAP operations in the Supplementary Service State Model

Core INAP Operation Nokia Siemens Networks' support in

Supplementary Service Management

state model

Note

Connect S

Continue S

InitialDP S 1

ReleaseCall S

1 Extensions have been specified for the operation.

The SSF is not capable of sending an unsupported operation to the SCF. If a not supported operation is received from the SCF, the SSF ignores the operation and aborts the conversation. If an operation outside the Core INAP application context is received, the operation is rejected.

5.3.3 Support of Core INAP parameters in IN supplementary service management

This section describes support for parameters of Core INAP operations, including the restrictions and inconsistencies relating to ETS 300 374-1.

Operation: Connect (CON)

Direction: SCF → SSF

Usage: The SCF changes the forwarded-to-number.

Associated operations:

None.

Comments: The SCF sends this operation as a final response operation.

About the use of this operation:

With this operation, the SCP changes the forwarded-to-number which the subscriber tries to register.

Parameters:

Table 57. Support for the Connect operation parameter

Parameter Nokia Siemens

Networks' support

Note

destinationRoutingAddress S

About the use of the parameters:

. destinationRoutingAddress

It indicates the changed forwarded-to-number, which is stored in the HLR database.

Operation: Continue (CUE)

Direction: SCF → SSF

Usage: The SCF requests the SSF to continue the processing from the DP where it was suspended because of the SCF inquiry.

Associated operations:

None.

Comments: The SCF sends this operation as a final response operation.

About the use of this operation:

With this operation, the SCP allows the supplementary service management procedure to continue normally.

Parameters: None.

Operation: InitialDP (IDP)

Direction: SSF → SCF

Usage: The SSF requests service from the SCF when it detects an active trigger in a TDP.

Associated operations:

None.

Comments: The supplementary service management procedure is stopped until the final response from the SCF is received.

About the use of this operation:

For the coding of the extension, see ASN.1 definitions for extensions in Section Interface description: ASN definitions.

The InitialDP is sent to the SCF, when:

. The SSF functionality is active in the HLR/SSF.

. An armed TDP is encountered.

. The INAP protocol handler is able to deliver the operation through the TC.

Note

When the SSF leaves the TDP, it is disarmed regardless of whether the triggering took place or not.

Parameters:

Table 58. Support for InitialDP operation parameters

Parameter Nokia Siemens

Networks' support

Note

serviceKey S

callingPartyNumber S

extensions iMSI sS-Code

ext-BasicServiveCode mAPOperationCode forwardedToNumber mM-EventType

S

About the use of the parameters:

. serviceKey

This parameter contains the value of the SKey in the subscriber data.

. callingPartyNumber

It contains the Primary MSISDN of the subscriber making the supplementary service management request from the HLR

database. It identifies the service requested from the SCP together with the SKey.

Extensions:

The criticality of every extension is IGNORE.

. Extension: iMSI

The IMSI of the subscriber making the supplementary service management attempt is received from the MS.

. Extension: sS-Code

It specifies the supplementary service related to the SS management request. It is received from the MS.

. Extension: ext-BasicServiceCode

It specifies the basic service related to the supplementary service. It is received from the MS.

. Extension: mAPOperationCode

It specifies the request type, that is, the SS operation. It is received from the MS.

. Extension: forwardedToNumber

It specifies the forwarded-to-number the subscriber tries to register.

It is received from the MS.

. Extension: mM-EventType

It identifies the DP at which the triggering was done. The following value has been reserved:

. value 7 indicated in the SS-DP1 Operation: ReleaseCall (RC)

Direction: SCF → SSF

Usage: The SCF requests the SSF to reject the location-updating attempt. A reject cause is sent to the SSF, which is then forwarded to the MS.

Associated operations:

None.

Comments: The SCF sends this operation as a final response operation.

About the use of this operation:

This operation is used to reject the supplementary service management transaction.

Parameters:

Table 59. Support for the ReleaseCall operation parameter

Parameter Nokia Siemens

Networks' support

Note

cause S

About the use of the parameters:

. cause

Value 7C is reserved for the call-unrelated functionalities. The additional cause value in the diagnostics field of the parameter is not used.