11 Supplementary services related services
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
11.1 MAP_REGISTER_SS service
11.1.1 Definition
This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.1./1.
11.1.2 Service primitives
Table 11.1/1: MAP_REGISTER_SS parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
Basic service |
C |
C(=) |
||
|
Forwarded-to number with subaddress |
C |
C(=) |
||
|
No reply condition time |
C |
C(=) |
||
|
EMLPP default priority |
C |
C(=) |
C |
C(=) |
|
Long FTN Supported |
C |
C(=) |
||
|
NbrUser |
C |
C(=) |
C |
C(=) |
|
Forwarding information |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.1.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
This parameter indicates the supplementary service which the mobile subscriber wants to register.
Basic service
This parameter indicates for which basic service group the supplementary service is to be registered. If it is not included, the registration request applies to all basic services.
Forwarded-to number with subaddress
This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can optionally include a sub-address.
No reply condition time
This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a superset of this service) and the mobile subscriber supplies a value for this time.
EMLPP default priority
This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at successful outcome of the service.
Long FTN Supported
This parameter indicates that the mobile station supports Long Forwarded-to Numbers.
NbrUser
This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to be used.
Forwarding information
This parameter is returned by the responder at successful outcome of the service, if the registration request concerned one or a group of Call Forwarding supplementary services.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1:
– System failure;
– Data missing;
– Unexpected data value;
– Call Barred;
– Bearer service not provisioned;
– This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
– Teleservice not provisioned;
This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
– Illegal SS operation;
– SS error status;
– SS incompatibility.
Provider error
See clause 7.6.1 for the use of this parameter.
11.2 MAP_ERASE_SS service
11.2.1 Definition
This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.2/1.
11.2.2 Service primitives
Table 11.2/1: MAP_ERASE_SS parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
Basic service |
C |
C(=) |
||
|
Forwarding information |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.2.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
This parameter indicates the supplementary service which the mobile subscriber wants to erase.
Basic service
This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, the erasure request applies to all basic services.
Forwarding information
This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or a group of Call Forwarding supplementary services.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Bearer service not provisioned;
This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
– Teleservice not provisioned;
This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
– Call Barred;
– Illegal SS operation;
– SS error status.
Provider error
See clause 7.6.1 for the use of this parameter.
11.3 MAP_ACTIVATE_SS service
11.3.1 Definition
This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.3/1.
11.3.2 Service primitives
Table 11.3/1: MAP_ACTIVATE_SS parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
Long FTN Supported |
C |
C(=) |
||
|
Basic service |
C |
C(=) |
||
|
Forwarding information |
C |
C(=) |
||
|
Call barring information |
C |
C(=) |
||
|
SS-Data |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.3.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
This parameter indicates the supplementary service which the mobile subscriber wants to activate.
Basic service
This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it is not included, the activation request applies to all basic services.
Forwarding information
This parameter is returned by the responder at successful outcome of the service, if the activation request concerned Call Forwarding.
Long FTN Supported
This parameter indicates that the mobile station supports Long Forwarded-to Numbers.
Call barring information
This parameter is returned by the responder at successful outcome of the service, if the activation request concerned Call Barring.
SS-Data
This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for example Call Waiting.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Bearer service not provisioned;
– This error is returned only if not even a subset of the requested bearer service group has been subscribed to.
– Teleservice not provisioned;
– This error is returned only if not even a subset of the requested teleservice group has been subscribed to.
– Call Barred;
– Illegal SS operation;
– SS error status;
– SS subscription violation;
– SS incompatibility;
– Negative PW check;
– Number Of PW Attempts Violation.
Provider error
See clause 7.6.1 for the use of this parameter.
11.4 MAP_DEACTIVATE_SS service
11.4.1 Definitions
This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.4/1.
11.4.2 Service primitives
Table 11.4/1: MAP_DEACTIVATE_SS parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
Basic service |
C |
C(=) |
||
|
Forwarding information |
C |
C(=) |
||
|
Call barring information |
C |
C(=) |
||
|
SS-Data |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.4.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
This parameter indicates the supplementary service which the mobile subscriber wants to deactivate.
Basic service
This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If it is not included the deactivation request applies to all basic services.
Forwarding information
This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned one or a group of Call Forwarding supplementary services.
Call barring information
This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one or a group of Call Barring supplementary services.
SS-Data
This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request concerned the Call Waiting supplementary service.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Bearer service not provisioned;
This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
– Teleservice not provisioned;
This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
– Call Barred;
– Illegal SS operation;
– SS error status;
– SS subscription violation;
– Negative PW check;
– Number Of PW Attempts Violation.
Provider error
See clause 7.6.1 for the use of this parameter.
11.5 MAP_INTERROGATE_SS service
11.5.1 Definitions
This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related to a supplementary service. The VLR will relay the message to the HLR if necessary.
The service is a confirmed service and consists of four service primitives.
11.5.2 Service primitives
The service primitives are shown in table 11.5/1.
Table 11.5/1: MAP_INTERROGATE_SS parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
Basic service |
C |
C(=) |
||
|
Long FTN Supported |
C |
C(=) |
||
|
SS-Status |
C |
C(=) |
||
|
Basic service Group LIST |
C |
C(=) |
||
|
Forwarding feature LIST |
C |
C(=) |
||
|
CLI restriction Info |
C |
C(=) |
||
|
EMLPP Info |
C |
C(=) |
||
|
MC Information |
C |
C(=) |
||
|
CCBS Feature LIST |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.5.3 Parameter use
For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications.
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
The mobile subscriber can only interrogate a single supplementary service per service request.
Basic service
This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not included, the interrogation request applies to all basic services.
SS-Status
This parameter is included by the responder if:
– the interrogated supplementary service can only be subscribed for all applicable basic services simultaneously; or
– the interrogated supplementary service is not active for any of the interrogated basic services, or
– the interrogation was for the CCBS supplementary service and no CCBS request is active or the service is not provisioned.
Basic service group LIST
This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) basic service groups, the SS-Status parameter is returned.
Long FTN Supported
This parameter indicates that the mobile station supports Long Forwarded-to Numbers.
Forwarding feature LIST
The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by the responder when the interrogation request applied to Call Forwarding supplementary service.
If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all provisioned basic services.
CLI restriction Info
The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR supplementary service.
EMLPP Info
The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation request applies to the eMLPP supplementary service.
MC Information
The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135.
CCBS Feature LIST
The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature.
User error
This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Bearer Service not provisioned;
This error is returned only if not even a subset of the interrogated bearer services are provided;
– Teleservice not provisioned;
This error is returned only if not even a subset of the interrogated teleservices are provided;
– Call Barred;
– Illegal SS operation;
– SS not available.
Provider error
See clause 7.6.1 for the use of this parameter.
11.6 Void
11.7 MAP_REGISTER_PASSWORD service
11.7.1 Definitions
This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber requests to register a new password. The VLR will relay the message to the HLR.
The service is a confirmed service and consists of four service primitives.
11.7.2 Service primitives
The service primitives are shown in table 11.7/1.
Table 11.7/1: MAP_REGISTER_PASSWORD parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
||
|
New password |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.7.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
SS-Code
This parameter indicates for which supplementary service(s) the password should be registered.
New Password
See clause 7.6.4 for the use of this parameter.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Call Barred;
– SS subscription violation;
– Password registration failure;
– Negative PW check;
– Number Of PW Attempts Violation.
Provider error
See clause 7.6.1 for the use of this parameter.
11.8 MAP_GET_PASSWORD service
11.8.1 Definitions
This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a request from the mobile subscriber for an operation on a supplementary service which requires a password from the subscriber. The VLR will relay the message to the MSC.
The service is a confirmed service and uses the service primitives shown in table 11.8/1.
11.8.2 Service primitives
Table 11.8/1: MAP_GET_PASSWORD parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
Linked id |
C |
C(=) |
||
|
Guidance info |
M |
M(=) |
||
|
Current password |
M |
M(=) |
||
|
Provider error |
O |
11.8.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
Linked Id
See clause 7.6.1 for the use of this parameter. If the MAP_GET_PASSWORD service is used in conjunction with the MAP_REGISTER_PASSWORD service, this parameter must be present; otherwise it must be absent.
Guidance info
See clause 7.6.4 for the use of this parameter.
Current password
See clause 7.6.4 for the use of this parameter.
Provider error
See clause 7.6.1 for the use of this parameter.
11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service
11.9.1 Definitions
This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation.
The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.9/1.
11.9.2 Service primitives
Table 11.9/1: MAP_PROCESS_UNSTRUCTURED_SS_REQUEST parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
USSD Data Coding Scheme |
M |
M(=) |
C |
C(=) |
|
USSD String |
M |
M(=) |
C |
C(=) |
|
MSISDN |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.9.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
USSD Data Coding Scheme
See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be present.
USSD String
See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present.
MSISDN
The subscriber’s basic MSISDN.
See definition in clause 7.6.2. For Follow Me when the service request is sent from the HLR of the A subscriber, the parameter shall contain the MSISDN of the A subscriber, see 3GPP TS 23.094 [129]. For other purposes the MSISDN may be included as an operator option, e.g. to allow addressing the subscriber’s data in the gsmSCF with the MSISDN.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1:
– System failure;
– Data missing;
– Unexpected data value;
This error is returned by the responder if it is not able to deal with the contents of the USSD string.
– Call Barred;
– Unknown Alphabet.
Provider error
See clause 7.6.1 for the use of this parameter.
11.10 MAP_UNSTRUCTURED_SS_REQUEST service
11.10.1 Definitions
This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC when the invoking entity requires information from the mobile user, in connection with unstructured supplementary service handling.
The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.
11.10.2 Service primitives
Table 11.10/1: MAP_UNSTRUCTURED_SS_REQUEST parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
USSD Data Coding Scheme |
M |
M(=) |
C |
C(=) |
|
USSD String |
M |
M(=) |
C |
C(=) |
|
Alerting Pattern |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.10.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
USSD Data Coding Scheme
See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile user’s MMI input. If this parameter is present, then the USSD String parameter has to be present.
USSD String
See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile user’s MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present.
Alerting Pattern
See clause 7.6.3 for the use of this parameter.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1:
– System failure;
– Data missing;
– Unexpected data value;
This error is returned by the responder if it is not able to deal with the contents of the USSD string;
– Absent Subscriber;
– Illegal Subscriber;
This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication;
– Illegal Equipment;
– USSD Busy;
– Unknown Alphabet.
Provider error
See clause 7.6.1 for the use of this parameter.
11.11 MAP_UNSTRUCTURED_SS_NOTIFY service
11.11.1 Definitions
This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured supplementary services handling.
The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.
11.11.2 Service primitives
Table 11.11/1: MAP_UNSTRUCTURED_SS_NOTIFY parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
USSD Data Coding Scheme |
M |
M(=) |
||
|
USSD String |
M |
M(=) |
||
|
Alerting Pattern |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.11.3 Parameter use
Invoke id
See clause 7.6.1 for the use of this parameter.
USSD Data Coding Scheme:
See clause 7.6.4 for the use of this parameter.
USSD String:
See clause 7.6.1 for the use of this parameter.
Alerting Pattern
See clause 7.6.3 for the use of this parameter.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1:
– System failure;
– Data missing;
– Unexpected data value;
This error is returned by the responder if it is not able to deal with the contents of the USSD string.
– Absent Subscriber;
– Illegal Subscriber;
This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication.
– Illegal Equipment;
– USSD Busy;
– Unknown Alphabet.
Provider error
See clause 7.6.1 for the use of this parameter.
11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition
This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY).
This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service.
11.12.2 Service primitives
The service primitives are shown in table 11.12/1.
Table 11.12/1: SS_INVOCATION_NOTIFY parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
MSISDN |
M |
M(=) |
||
|
IMSI |
M |
M(=) |
||
|
SS- event |
M |
M(=) |
||
|
SS- event data |
C |
C(=) |
||
|
B-subscriber Number |
C |
C(=) |
||
|
CCBS Request State |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.12.3 Parameter use
All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.078.
User error
This parameter is sent by the responder when an error is detected and if present, takes one of the following values:
– Data Missing;
– Unexpected Data Value;
– Unknown Subscriber.
Provider error
This is defined in clause 7.6.1.
11.13 MAP_REGISTER_CC_ENTRY service
11.13.1 Definition
This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested call completion supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.13/1.
11.13.2 Service primitives
Table 11.13/1: MAP_REGISTER_CC_ENTRY parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS Code |
M |
M(=) |
||
|
CCBS Feature |
C |
C(=) |
C |
C(=) |
|
Translated B number |
C |
C(=) |
||
|
Service Indicator |
C |
C(=) |
||
|
Call Info |
C |
C(=) |
||
|
Network Signal Info |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.13.3 Parameter use
See clause 7.6 for a definition of the parameters used, in addition to the following.
SS-Code
This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an entry.
CCBS Feature
See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature.
Translated B Number
See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence.
Service Indicator
This parameter corresponds to the parameters ‘Presentation Indicator’ and ‘CAMEL Invoked’ in 3GPP TS 23.093 [107]. It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence.
Call Info
See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence.
Network Signal Info
See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data missing;
– Unexpected data value;
– Call Barred;
– Illegal SS operation;
– SS error status;
– SS incompatibility.
– Short Term Denial;
– Long Term Denial;
– Facility Not Supported;
NOTE: This error is reserved for future use.
Private Extensions shall not be sent with these user errors for this operation.
Provider error
See clause 7.6.1 for the use of this parameter.
11.14 MAP_ERASE_CC_ENTRY service
11.14.1 Definition
This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call completion supplementary service. The VLR will relay the message to the HLR.
The service is a confirmed service and uses the service primitives shown in table 11.14/1.
11.14.2 Service primitives
Table 11.14/1: MAP_ERASE_CC_ENTRY parameters
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
SS-Code |
M |
M(=) |
C(=) |
C(=) |
|
CCBS Index |
C |
C(=) |
||
|
SS-Status |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
11.14.3 Parameter use
See clause 7.6 for a definition of the parameters used, in addition to the following.
SS-Code
This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an entry/entries.
CCBS Index
See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence.
SS-Status
Depending on the outcome of the service request this parameter may indicate either provisioned and active or not provisioned.
User error
This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values, defined in clause 7.6.1:
– System failure;
– Data Missing;
– Unexpected data value;
– Call Barred;
– Illegal SS operation;
– SS error status.
Private Extensions shall not be sent with these user errors for this operation.
Provider error
See clause 7.6.1 for the use of this parameter.