No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Voice Feature Guide 01

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Malicious Call Identification

Malicious Call Identification

A user who registers this callee-side service can identify the calling number if the user receives a malicious call or unsolicited call, such as a prank call or a phishing call.

Malicious Call Identification

This topic describes the definition and benefits of the malicious call identification (MCID) service.

Definition

The MCID service enables a user to identify the calling number when the user receives a malicious call or unsolicited call.

Benefit
Beneficiary Benefits

Carrier

The MCID service enhances carriers' competitiveness and provides new revenue streams.

User

In the following cases, the called party can obtain the calling number of the calling party through the MCID service:
  • The called party has not subscribed to the originating identification presentation (OIP) service.
  • The calling party has subscribed to the originating identification restriction (OIR) service.
  • After the phone rings, the calling number is not displayed but the calling party hangs up.

In addition, when a user answers a malicious call (for example, blackmail or extortion), the user can notify the police through the MCID service.

Standards Compliance

EN300 130

ETSI TS 300 130

ETSI TS 124 516

ETSI TS 183 016

ETSI TS 183 036

ETSI TS 183 043

Service Flow of Malicious Call Identification

This topic takes the service user A and common user B as an example to describe the malicious call identification (MCID) service flows.

MCID Service Flow for POTS Users

The MCID service of a POTS user can be implemented in two ways: During a call, the user can dial the service access code to obtain the malicious call information by pressing the hookflash or dialing the service access code after the call ends (or after refusing the call), as shown in Figure 1-86 and Figure 1-87.

Figure 1-86 MCID service flow for POTS users during a call

User A is a service user. User A presses hookflash, and user B is placed on hold. The MCID service flow for POTS users is as follows:
  1. AG1 plays the special dial tone to user A.
  2. User A calls the SCC number.
  3. AG1 sends an unsolicited Invite message to the IMS.
  4. The IMS allocates MRF resources and returns a 183 response. User A hears an announcement indicating that the MCID service is successful.
  5. User A presses hookflash.
  6. AG1 sends a Cancel message to cancel the previous unsolicited Invite request.
  7. The IMS responds with a 200 OK message.
  8. The IMS responds with an Ack message. The call between users A and B is resumed.
Figure 1-87 MCID service flow for POTS users after a call

User A is a service user. User A ends a call with user B. The MCID service flow for a POTS user is as follows:
  1. User A picks up the phone.
  2. AG1 plays the special dial tone to user A.
  3. User A calls the SCC number.
  4. AG1 sends an unsolicited Invite message to the IMS.
  5. The IMS allocates MRF resources and returns a 183 response. User A hears an announcement indicating that the MCID service is successful.
  6. User A hangs up the phone.
  7. AG1 sends a Cancel message to cancel the previous unsolicited Invite request.
  8. The IMS responds with a 200 OK message.
  9. The IMS responds with an Ack message. User A releases the call.
MCID Service Flow for ISDN Users

Figure 1-88 shows the service flow of the MCID service for ISDN users.

Figure 1-88 MCID service for ISDN users

Users A and B enter the conversation state through a call flow. User A is the service party (called party). The MCID service flow for ISDN users is as follows:
  1. User A performs operations on the ISDN terminal and starts the MCID. The terminal sends a Facility message carrying the FIE message unit, indicating that the message is an MCID request.
  2. AG1 maps the FIE to the XML message body and initiates media renegotiation to the IMS.
  3. The IMS determines that A has the MCID service permission, and then notifies AG1 of the phone number of malicious caller through the SDP in media renegotiation.
  4. After receiving the SDP message from the IMS, AG1 sends an Ack message.
  5. AG1 sends a Facility message carrying the FIE message unit to user A, indicating the MCID result. User A hears user B's number through the terminal announcement.
Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 12905

Downloads: 120

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next