INTRODUCTION

This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service.

Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities.

RDV enables a home system to verify that a roaming partner's VLR database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system.

RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in IS-41-C or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC.

The message routing databases that may be maintained at an MSC are:

•An MSID-based database used for indirectly routing an MS-originated SMS message to the originating MS's MC.

• An MSID-based database used for routing an OriginationRequest INVOKE or a FeatureRequest INVOKE to the appropriate HLR.

• An MDN-based database used for directly routing an MS-originated SMS message to the destination's MC.

The message routing databases that may be maintained at an MC are:

• An MDN-based database used for routing an SMSRequest INVOKE to the MS's HLR.

• An MDN-based database that it uses in its role as originating MC to route MSoriginated SMS messages to the destination's MC.

RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system as well as other message routing database related problems.