Files
web.ems/wxc2_omc/omcHelp/5_2_2.htm
agtuser 16a3fd1e1b init
2024-11-11 17:56:00 +08:00

62 lines
5.2 KiB
HTML
Executable File
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!DOCTYPE HTML>
<html>
<head>
<title>NRTRDE HPMN</title>
<meta name="generator" content="Help &amp; Manual" />
<meta name="keywords" content="NRTRDE" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
body { margin: 0px; background: #FFFFFF; }
</style>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="helpman_settings.js"></script>
<script type="text/javascript" src="helpman_topicinit.js"></script>
<script type="text/javascript">
HMSyncTOC("index.html", "5_2_2.htm");
</script>
</head>
<body>
<table style="width:100%; border:none; border-spacing:0px; padding:5px; background:#649CCC">
<tr style="vertical-align:middle">
<td style="text-align:left">
<h1 class="p_Heading1"><span class="f_Heading1">NRTRDE HPMN</span></h1>
</td>
<td style="text-align:right">
<a href="0_0.htm">Top</a>&nbsp;
<a href="5_2_1.htm">Previous</a>&nbsp;
<a href="5_2_3.htm">Next</a>
</td>
</tr>
</table>
<!-- Placeholder for topic body. -->
<table style="width:100%;border:none;border-spacing:0px"><tr style="vertical-align:top"><td style="text-align:left;padding:5px">
<p style="background: #99ccff;"><span style="font-weight: bold;">Descriptions</span></p>
<p>&nbsp;</p>
<p class="p_NoramlTest" style="line-height: 1.50;"><span class="f_NoramlTest">NRTRDE (Near Real Time Roaming Data Exchange) provides a new method for monitoring the subscribers activities in the VPMN (Visited Public Mobile Network) networks, and enables the HPMN (Home Public Mobile Network) to detect unauthorized network usage and other fraud issues near real time.</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest" style="line-height: 1.50;"><span class="f_NoramlTest">One of the main purposes of NRTRDE is to reduce roaming data delivery time from the VPMN to the HPMN from up to 36 hours to 4 hours (or less), for fraud management purposes. In this solution, roaming call records will be sent independently of TAP (Transfer Account Procedure) procedures. Although a 4 hour maximum timeframe has been set as the contractual NRTRDE obligation for the VPMN to deliver roaming CDR information to the respective HPMN, it is recommended that operators set a goal to achieve NRTRDE record exchange delays of less than one hour. </span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p style="background: #99ccff;"><span style="font-weight: bold;">Functionalities</span></p>
<p>&nbsp;</p>
<p style="line-height: 1.50; margin: 0px 12px 10px 12px;">NRTRDE is for GSM mobile operators to fight roaming fraud. </p>
<p style="text-align: left; padding: 0px 0px 0px 13px; margin: 0px 12px 10px 12px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span>Replacing the existing High Usage Report (HUR) process with an industry-wide interoperable Near Real-Time Roaming Data Exchange (NRTRDE) procedure that is mandatory for all GSMA members to implement. The NRTRDE solution will have two essential functions:</p><p style="text-align: left; padding: 0px 0px 0px 13px; margin: 0px 12px 10px 12px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span>Reduce the required timeframe for delivery of fraud related roaming information from the VPMN to the HPMN from 36 hours to a maximum of 4 hours.</p><p style="text-align: left; padding: 0px 0px 0px 13px; margin: 0px 12px 10px 12px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span>Provide individual CDR information in sufficient form to allow operators to cost effectively manage roaming fraud</p><p style="text-align: left; padding: 0px 0px 0px 13px; margin: 0px 12px 10px 12px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span>Shortening the deadline from 36 hours to 4 hours for fraud loss liability from the HPMN to VPMN for any roaming fraud losses that accrue after expiration of a 4 hour deadline by which the VPMN is required to deliver roaming call records to the HPMN. At present, the VPMN is required to notify the HPMN of subscriber usage above an agreed threshold within 36 hours.</p><p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest"><span class="f_NoramlTest">&nbsp;</span></p>
<p class="p_NoramlTest" style="text-align: right;"><span style="font-size: 8pt;">5.2.2</span></p>
</td></tr></table>
</body>
</html>