Roamer Database Verification. Revision: A COPYRIGHT. 3GPP2 N.S0025-A Version Version Date: June 2002

Transcription

1 GPP N.S00-A Version.0.0 Version Date: June 00 Roamer Database Verification Revision: A COPYRIGHT GPP and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2 Revision History Revision Date Rev. 0 Initial Publication January 00 Rev. A Version Update June 00 Note This specification is an extract of TIA TR-. IS--A.

3 N.S00-A v CONTENTS ROAMER DATABASE VERIFICATION List of Figures...iii List of Tables... iv Revision History... v Introduction... General... Objective... References... Organization... Editorial Conventions... TIA/EIA- Modifications... Y Network Capabilities... Y. Roamer Database Verification (RDV)... Y.. Normal Operation... Y.. Security... Y.. Exception Procedures or Unsuccessful Outcome... Y.. Alternate Procedures... Y.. Interactions With Other Network Services... TIA/EIA-.-D Modifications... Symbols and Abbreviations... TIA/EIA-.-D Modifications... Y Roamer Database Verification (RDV) Scenarios... Y. RDV Query: by HLR of MSID Range in VLR Database... Y. RDV Query: by HLR of MSID Range Not in VLR Database... Y. RDV Query by MC of MSID Range in MSC Database... Y. RDV Query by MC of MSID Range Not in MSC Database... 0 Y. RDV Query by HLR of MSID Range in MSC Database... Y. RDV Query by HLR of MSID Range Not in MSC Database... Y. RDV Query by MC of MDN Range in MSC Database... Y. RDV Query by MC of MDN Range Not in MSC Database... Y. RDV Query by HLR of MDN Range in MC Database... Y.0 RDV Query by HLR of MDN Range Not in MC Database... Y. RDV Query by MC of MDN Range in MC Database... i Contents

4 N.S00-A v.0 Y. RDV Query by MC of MDN Range Not in MC Database... TIA/EIA-.-D Modifications... Data Transfer Services.... SS-BASED DATA TRANSFER SERVICES..... Message Transfer Part... Application Services.... Map Operations..... General Operation Specifiers..... Operation Definitions......aq RoamerDatabaseVerificationRequest Map Parameters..... General Parameter Identifiers..... Parameter Definitions......gj Range......gt InvokingNEType... TIA/EIA-.-D Modifications... Intersystem Procedures....ZZ Roamer Database Verification Request....ZZ. HLR Initiating a Roamer Database Verification Request to a VLR....ZZ..ZZ. VLR Receiving RoamerDatabaseVerificationRequest INVOKE... HLR Initiating a Roamer Database Verification Request to an MSC....ZZ. MC Initiating a Roamer Database Verification Request to an MSC....ZZ. MSC Receiving RoamerDatabaseVerificationRequest INVOKE....ZZ. HLR Initiating a Roamer Database Verification Request to an MC....ZZ. MC Initiating a Roamer Database Verification Request to an MC....ZZ. MC Receiving RoamerDatabaseVerificationRequest INVOKE... Operation Timer Values Contents ii

5 N.S00-A v LIST OF FIGURES Introduction TIA/EIA- Modifications TIA/EIA-.-D Modifications TIA/EIA-.-D Modifications Figure RDV Query: by HLR of MSID Range in VLR Database Figure RDV Query: by HLR of MSID Range Not in VLR Database Figure RDV Query by MC of MSID Range in MSC Database Figure RDV Query by MC of MSID Range Not in MSC Database Figure RDV Query by HLR of MSID Range in MSC Database Figure RDV Query by HLR of MSID Range Not in MSC Database Figure RDV Query by MC of MDN Range in MSC Database Figure RDV Query by MC of MDN Range Not in MSC Database Figure RDV Query by HLR of MDN Range in MC Database Figure 0 RDV Query by HLR of MDN Range Not in MC Database Figure RDV Query by MC of MDN Range in MC Database Figure RDV Query by MC of MDN Range Not in MC Database TIA/EIA-.-D Modifications TIA/EIA-.-D Modifications iii List of Figures

6 N.S00-A v.0 LIST OF TABLES Introduction TIA/EIA- Modifications TIA/EIA-.-D Modifications TIA/EIA-.-D Modifications TIA/EIA-.-D Modifications Table MTP Message Priority Values for TIA/EIA- Operations... Table TIA/EIA- MAP Operation Specifiers... Table 0 Summary of MAP Operations... Table TIA/EIA- MAP Parameter Identifiers... TIA/EIA-.-D Modifications Table VLR RoamerDatabaseVerificationRequest Response... Table MSC RoamerDatabaseVerificationRequest Response... Table MC RoamerDatabaseVerificationRequest Response... Table Operation Timer Values List of Tables iv

7 N.S00-A v REVISION HISTORY Version Date 0 January 00 Initial Publication A June 00 Enhancement for HLR & MC v Revision History

8 N.S00-A v.0 (This page intentionally left blank.) 0 0 Revision History vi

9 N.S00-A v INTRODUCTION GENERAL OBJECTIVE 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--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. This document describes the RDV network capability and the intersystem operations to enable a wireless system to use RDV. The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. General Introduction

10 N.S00-A v.0 REFERENCES This Interim Standard builds on the following standards: ORGANIZATION ANSI/TIA/EIA-, Cellular Features Description; Telecommunications Industry Association; June ANSI/TIA/EIA--D, Cellular Radiotelecommunications Intersystem Operations; Telecommunications Industry Association; TIA/EIA/IS-, TIA/EIA--D Modifications to Support IMSI; Telecommunications Industry Association; February TIA/EIA/IS-, Roamer Database Verification, Telecommunications Industry Association; January 00 This document is organized as follows: The TIA/EIA- Modifications sections provides the modifications and additions to TIA/EIA- Cellular Features Description for RDV. The TIA/EIA-.-D Modifications section provides the modifications and additions to TIA/EIA--D Chapter Functional Overview for RDV. The TIA/EIA/.-D Modifications sections provides the modifications and additions to TIA/EIA--D Chapter Automatic Roaming Information Flows for RDV. The TIA/EIA-.-D Modifications section provides the modifications and additions to TIA/EIA--D Chapter Signaling Protocol for the RDV. The TIA/EIA-.-D Modifications section provides the modifications and additions to TIA/EIA--D Chapter Signaling Procedures for RDV. EDITORIAL CONVENTIONS The following editorial conventions are used for this Interim Standard: underline: additions cross out: deletion change bar: indicates additions or deletions new sub-sections are identified in the sub-section heading for clarity, new sub-sections are shown with vertical change bars but are not underlined additions and deletions for IS--A are shown in blue 0 0 Introduction References

11 N.S00-A v TIA/EIA- MODIFICATIONS Y This section provides wireless features descriptions for Roamer Database Verification (RDV) according to the structure of TIA/EIA-. Network Capabilities Y. Roamer Database Verification (RDV) (New Section for TIA/EIA-) Roamer Database Verification (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--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. Applicability to Network Configurations RDV is applicable to all network configurations. Network Capabilities TIA/EIA- Modifications

12 N.S00-A v.0 Y.. Normal Operation Invocation RDV is initiated by any of the following: An HLR query to a VLR regarding an MSID range. An MC query to an MSC regarding an MSID range. An HLR query to an MSC regarding an MSID range. An MC query to an MSC regarding an MDN range. An HLR query to an MC regarding an MDN range. An MC query to an MC regarding an MDN range. In any of these cases, the INVOKING NE requests the RESPONDING NE to examine the indicated message routing database and to verify that the data stored for the indicated MSID or MDN range enables the routing of MAP messages to the INVOKING NE. The INVOKING NE can request that contiguous blocks of MSID or MDN entries be examined by the RESPONDING NE. For backward compatibility, HLRs querying VLRs that conform to older versions of this standard may need to restrict the range to 0,000 numbers. RDV is initiated by an HLR query to a VLR. The HLR requests the VLR to examine its roamer database and to verify that the data stored for the indicated MSID range enables roaming subscribers from the requesting service provider s system to obtain wireless telecommunications service. The HLR can request that a range from one to 0,000 contiguous MSID entries be examined by the VLR. Normal Operation With Successful Outcome When an RDV query is received, the RESPONDING NE authorizes the INVOKING NE request. If the INVOKING NE is authorized, the RESPONDING NE determines which message routing database to examine based on the type of the INVOKING NE and the type of range (MSID or MDN) that has been provided for examination. The RESPONDING NE then examines that message routing database for the indicated range of MSIDs or MDNs to determine whether the data needed to send a MAP message to the INVOKING NE is stored in the entries corresponding to that range. The RESPONDING NE responds with a positive confirmation if every entry corresponding to that range is populated for the INVOKING NE, or if an entry is not populated and global title addressing is used for communication with the INVOKING NE. When an RDV query is received by a VLR, the VLR authorizes the HLR request. If the HLR is authorized, the VLR examines its roamer database for MSIDs in the range indicated by the HLR to verify that roaming subscribers from the requesting service provider s system can obtain service. The VLR responds with a positive confirmation if every MSID in the range is populated for the requesting HLR, or if an MSID entry is not populated, global title addressing is used for communication with the roaming subscriber s HLR. Call Detail Record RDV does not require call detail information to be recorded. 0 0 TIA/EIA- Modifications Roamer Database Verification (RDV)

13 N.S00-A v Y.. Y.. Y.. Y.. Security The RESPONDING NE VLR authorizes the INVOKING NE HLR request to determine whether the requested MSID or MDN information shall be provided. Upon receipt of the RDV query, the RESPONDING NE VLR determines if the INVOKING NE HLR is associated with the received MSID or MDN range. A positive acknowledgment is only returned if there is no mismatch. A negative response from the RESPONDING NE VLR only indicates that the MSID or MDN range does not match the message routing roamer database entries for the INVOKING NE requesting HLR. No indication shall be sent as to whether the MSID or MDN range exists in the database or not. The RESPONDING NE VLR does not provide any indication that would lead to a conclusion about MSID or MDN ranges that are not associated with the INVOKING NE HLR. MSID or MDN range is populated MSID or MDN range is populated Exception Procedures or Unsuccessful Outcome The RESPONDING NE VLR provides a negative response to the INVOKING NE HLR if the INVOKING NE HLR is not authorized for the RDV query. The RESPONDING NE VLR responds with a RETURN ERROR. The Error Code is set to indicate OperationNotSupported. The RESPONDING NE VLR provides a negative response to the INVOKING NE HLR if the MSID or MDN range (the entire range or any part of the range) is not populated for the INVOKING NE HLR. The RESPONDING NE VLR responds with a RETURN ERROR. The Error Code is set to indicate MSID/HLRMismatch. Alternate Procedures None identified. Interactions With Other Network Services None identified. VLR Roamer Database MSID or MDN range is not populated global title addressing is used MSID or MDN range is not populated global title addressing is not used Mismatch with INVOKING NE HLR mismatch not detected Mismatch with INVOKING NE HLR mismatch detected VLR Response Positive Negative Positive Negative Roamer Database Verification (RDV) TIA/EIA- Modifications

14 N.S00-A v.0 TIA/EIA-.-D MODIFICATIONS This section provides modifications and additions to TIA/EIA--D Chapter needed for Roamer Database Verification. SYMBOLS AND ABBREVIATIONS INVNE RANGE RDV RDVREQ rdvreq RDVRT InvokingNEType parameter Range parameter Roamer Database Verification RoamerDatabaseVerificationRequest INVOKE RoamerDatabaseVerificationRequest RETURN RESULT Roamer Database Verification Request Timer 0 0 TIA/EIA-.-D Modifications Symbols and Abbreviations

15 N.S00-A v TIA/EIA-.-D MODIFICATIONS Y This section provides new Operations, Administration, and Maintenance information flows for Roamer Database Verification according to the structure of TIA/EIA--D Chapter. Roamer Database Verification (RDV) Scenarios (New Section for TIA/EIA-.-D) This section depicts the interactions between network entities in various situations related to RDV. These scenarios are for illustrative purposes only. Y. RDV Query: by HLR of MSID Range in VLR Database This scenario describes an RDV query when the MSID range indicated by the HLR is loaded in the VLR database. HLR Figure RDVREQ [MSCID, MSID, RANGE] RDVRT rdvreq [TRANSCAP] RDV Query: by HLR of MSID Range in VLR Database a. The HLR determines that an RDV query shall be initiated to a VLR. The HLR sends an RDVREQ to the VLR. Parameters Usage Type MSCID HLR MSCID. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine ( to 0,000). O R b. The VLR examines its roamer database and verifies that the specified range of MSIDs is associated with the requesting HLR. The VLR sends an rdvreq to the HLR. Parameters Usage Type TRANSCAP VLR s transaction capability. Include if applicable. O VLR a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

16 N.S00-A v.0 Y. RDV Query: by HLR of MSID Range Not in VLR Database This scenario describes an RDV query when the MSID range indicated by the HLR is not associated with that HLR. HLR Figure RDVREQ [MSCID, MSID, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query: by HLR of MSID Range Not in VLR Database a. The HLR determines that an RDV query shall be initiated to a VLR. The HLR sends an RDVREQ to the VLR. Parameters Usage Type MSCID HLR MSCID. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine ( to 0,000). O R b. The VLR examines its roamer database and determines that the entire MSID range or any part of the MSID range is not associated with the requesting HLR. The VLR sends a RETURN ERROR to the HLR with the Error Code set to indicate MSID/HLRMismatch. VLR a b 0 0 TIA/EIA-.-D Modifications Roamer Database Verification (RDV) Scenarios

17 N.S00-A v Y. RDV Query by MC of MSID Range in MSC Database This scenario describes an RDV query when the MSID range indicated by the MC is loaded in the MSC database. MC Figure RDVREQ [INVFE, MSID, RANGE] RDVRT rdvreq [] RDV Query by MC of MSID Range in MSC Database a. The MC determines that an RDV query shall be initiated to an MSC to verify the database used by the MSC to indirectly route MS-originated SMS messages. The MC sends an RDVREQ to the MSC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine. O b. The MSC examines the message routing database used for indirect routing of MS-originated SMS messages to the originating MS s MC and verifies that the specified range of MSIDs is associated with the requesting MC. The MSC sends an empty rdvreq to the MC. MSC a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

18 N.S00-A v.0 Y. RDV Query by MC of MSID Range Not in MSC Database This scenario describes an RDV query when the MSID range indicated by the MC is not associated with that MC. MC Figure RDVREQ [INVFE, MSID, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query by MC of MSID Range Not in MSC Database a. The MC determines that an RDV query shall be initiated to an MSC to verify the database used by the MSC to indirectly route MS-originated SMS messages. The MC sends an RDVREQ to the MSC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine. O b. The MSC examines the message routing database used for indirect routing of MS-originated SMS messages to the originating MS s MC and determines that the entire MSID range or any part of the MSID range is not associated with the requesting MC. The MSC sends a RETURN ERROR to the MC with the Error Code set to indicate MSID/HLRMismatch. MSC a b 0 0 TIA/EIA-.-D Modifications 0 Roamer Database Verification (RDV) Scenarios

19 N.S00-A v Y. RDV Query by HLR of MSID Range in MSC Database This scenario describes an RDV query when the MSID range indicated by the HLR is loaded in the MSC database. HLR Figure RDVREQ [MSCID, MSID, RANGE] RDVRT rdvreq [TRANSCAP] RDV Query by HLR of MSID Range in MSC Database a. The HLR determines that an RDV query shall be initiated to an MSC. The HLR sends an RDVREQ to the MSC. Parameters Usage Type MSCID HLR MSCID. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine. O b. The MSC examines the message routing database that it uses to route FEATREQs and ORREQs to HLRs and verifies that the specified range of MSIDs is associated with the requesting HLR. The MSC sends an rdvreq to the HLR. MSC Parameters Usage Type TRANSCAP MSC s transaction capability. Include if applicable. O a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

20 N.S00-A v.0 Y. RDV Query by HLR of MSID Range Not in MSC Database This scenario describes an RDV query when the MSID range indicated by the HLR is not associated with that HLR. HLR Figure RDVREQ [MSCID, MSID, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query by HLR of MSID Range Not in MSC Database a. The HLR determines that an RDV query shall be initiated to a MSC. The HLR sends an RDVREQ to the MSC. Parameters Usage Type MSCID HLR MSCID. R MSID Starting point of the range of MSIDs to examine. R RANGE Number of MSIDs to examine. O b. The MSC examines the message routing database that it uses to route FEATREQs and ORREQs to HLRs and determines that the entire MSID range or any part of the MSID range is not associated with the requesting HLR. The MSC sends a RETURN ERROR to the HLR with the Error Code set to indicate MSID/HLRMismatch. MSC a b 0 0 TIA/EIA-.-D Modifications Roamer Database Verification (RDV) Scenarios

21 N.S00-A v Y. RDV Query by MC of MDN Range in MSC Database This scenario describes an RDV query when the MDN range indicated by the MC is loaded in the MSC database. MC Figure RDVREQ [INVFE, MDN, RANGE] RDVRT rdvreq [] RDV Query by MC of MDN Range in MSC Database a. The MC determines that an RDV query shall be initiated to an MSC to verify the database used by the MSC for direct routing of MS-originated SMS messages. The MC sends an RDVREQ to the MSC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The MSC examines the message routing database used for direct routing of MS-originated SMS messages to the destination MS s MC and verifies that the specified range of MDNs is associated with the requesting MC. The MSC sends an empty rdvreq to the MC. MSC a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

22 N.S00-A v.0 Y. RDV Query by MC of MDN Range Not in MSC Database This scenario describes an RDV query when the MDN range indicated by the MC is not associated with that MC. MC Figure RDVREQ [INVFE, MSID, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query by MC of MDN Range Not in MSC Database a. The MC determines that an RDV query shall be initiated to an MSC to verify the database used by the MSC for direct routing of MS-originated SMS messages. The MC sends an RDVREQ to the MSC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The MSC examines the message routing database used for direct routing of MS-originated SMS messages to the destination MS s MC and determines that the entire MDN range or any part of the MDN range is not associated with the requesting MC. The MSC sends a RETURN ERROR to the MC with the Error Code set to indicate MSID/HLRMismatch. MSC a b 0 0 TIA/EIA-.-D Modifications Roamer Database Verification (RDV) Scenarios

23 N.S00-A v Y. RDV Query by HLR of MDN Range in MC Database This scenario describes an RDV query when the MDN range indicated by the HLR is loaded in the MC database. HLR Figure RDVREQ [MSCID, MDN, RANGE] RDVRT rdvreq [] RDV Query by HLR of MDN Range in MC Database a. The HLR determines that an RDV query shall be initiated to an MC. The HLR sends an RDVREQ to the MC. Parameters Usage Type MSCID HLR MSCID. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The MC examines the message routing database that it uses to route SMSREQs to HLRs and verifies that the specified range of MDNs is associated with the requesting HLR. The MC sends an empty rdvreq to the HLR. MC a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

24 N.S00-A v.0 Y.0 RDV Query by HLR of MDN Range Not in MC Database This scenario describes an RDV query when the MDN range indicated by the HLR is not associated with that HLR. HLR Figure 0 RDVREQ [MSCID, MDN, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query by HLR of MDN Range Not in MC Database a. The HLR determines that an RDV query shall be initiated to a MC. The HLR sends an RDVREQ to the MC. Parameters Usage Type MSCID HLR MSCID. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The MC examines the message routing database that it uses to route SMSREQs to HLRs and determines that the entire MDN range or any part of the MDN range is not associated with the requesting HLR. The MC sends a RETURN ERROR to the HLR with the Error Code set to indicate MSID/HLRMismatch. MC a b 0 0 TIA/EIA-.-D Modifications Roamer Database Verification (RDV) Scenarios

25 N.S00-A v Y. RDV Query by MC of MDN Range in MC Database This scenario describes an RDV query when the MDN range indicated by the MC is loaded in the queried MC database. MC Figure RDVREQ [INVFE, MDN, RANGE] RDVRT rdvreq [] RDV Query by MC of MDN Range in MC Database a. The MC determines that an RDV query shall be initiated to another MC to verify the database used by that MC to relay indirectly routed MS-originated SMS messages to the destination MS s MC. The MC sends an RDVREQ to the MC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The queried MC examines the message routing database used to relay indirectly routed MSoriginated SMS messages to the destination MS s MC and verifies that the specified range of MDNs is associated with the requesting MC. The queried MC sends an empty rdvreq to the requesting MC. MC a b Roamer Database Verification (RDV) Scenarios TIA/EIA-.-D Modifications

26 N.S00-A v.0 Y. RDV Query by MC of MDN Range Not in MC Database This scenario describes an RDV query when the MDN range indicated by the MC is not associated with that MC. MC Figure RDVREQ [INVFE, MDN, RANGE] RDVRT RETURN ERROR [Error Code] RDV Query by MC of MDN Range Not in MC Database a. The MC determines that an RDV query shall be initiated to another MC to verify the database used by that MC to relay indirectly routed MS-originated SMS messages to the destination MS s MC. The MC sends an RDVREQ to the MC. Parameters Usage Type INVNE Indicates that the query was initiated by an MC. R MDN Starting point of the range of MDNs to examine. R RANGE Number of MDNs to examine. O b. The queried MC examines the message routing database used to relay indirectly routed MSoriginated SMS messages to the destination MS s MC and determines that the entire MDN range or any part of the MDN range is not associated with the requesting MC. The queried MC sends a RETURN ERROR to the requesting MC with the Error Code set to indicate MSID/HLRMismatch. MC a b 0 0 TIA/EIA-.-D Modifications Roamer Database Verification (RDV) Scenarios

27 N.S00-A v TIA/EIA-.-D MODIFICATIONS This section provides modifications and additions to TIA/EIA--D Chapter needed for Roamer Database Verification. Data Transfer Services. SS-BASED DATA TRANSFER SERVICES.. Message Transfer Part Table Application Services. Map Operations.. General... Operation Specifiers Table.. Operation Definitions (TIA/EIA-.-D, page -) MTP Message Priority Values for TIA/EIA- Operations TIA/EIA- Operation MTP Message Priority RoamerDatabaseVerificationRequest 0 TIA/EIA- MAP Operation Specifiers Operation Name (TIA/EIA-.-D, page -) Operation Specifier H G F E D C B A Decimal RoamerDatabaseVerificationRequest Table 0 Summary of MAP Operations Operation RoamerDatabaseVerificationRequest (TIA/EIA-.-D, page -) Reference...aq Data Transfer Services TIA/EIA-.-D Modifications

28 N.S00-A v.0...aq RoamerDatabaseVerificationRequest (New for TIA/EIA-.-D Section..) The RoamerDatabaseVerificationRequest (RDVREQ) operation is used by an HLR to verify that a message routing roaming partner s VLR database at the RESPONDING NE is correctly loaded for the MSID or MobileDirectoryNumber number range associated with the INVOKING NE. The database to be verified is identified by the RESPONDING NE based on the NE type of the INVOKING NE and the type of number range (MSID or MobileDirectoryNumber) to be examined home service provider. The following table lists the valid combinations of invoking and responding NEs. The RoamerDatabaseVerificationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Notes: INVOKING NE RESPONDING NE Case HLR VLR Case MC MSC Case HLR MSC Case HLR MC Case MC MC RoamerDatabaseVerificationRequest INVOKE Parameters a. Include to indicate HLR s MSCID, if the INVOKING NE is an HLR. Timer: RDVRT Field Value Type Reference Notes Identifier SET [NATIONAL ] M... Length variable octets M... Comments InvokingNEType O...gt e MobileDirectoryNumber O...0 f, g MSCID (HLR) O... a MSID O...bv b, g Range O...gj c, d b. Include to indicate the starting point of the range of MSIDs to examine if the message routing database to be examined is MSID-based. c. Include to indicate the number of MSIDs or MobileDirectoryNumbers to examine ( to 0,000). For backward compatibility, HLRs querying VLRs that conform to older versions of this standard may need to restrict the range to 0,000 numbers. d. If this parameter is not included, one MSID or MobileDirectoryNumber number shall be examined. e. Include if the INVOKING NE is not an HLR to indicate the NE type of the INVOKING NE. 0 0 TIA/EIA-.-D Modifications 0 Map Operations

29 N.S00-A v f. Include to indicate the starting point of the range of MobileDirectoryNumbers to examine if the message routing database to be examined is MobileDirectoryNumberbased. g. One and only one of these parameters should be included. The RoamerDatabaseVerificationRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: RoamerDatabaseVerificationRequest RETURN RESULT Parameters Notes: Field Value Type Reference Notes Identifier SET [NATIONAL ] M... Length variable octets M... Comments TransactionCapability O... a a. Included when this response is sent to an HLR by a VLR or MSC if the TransactionCapability parameter is included in all the RegistrationNotification INVOKE operations sent for MSIDs in the specified Range. (The parameter value shall be set to the value used for all the RegistrationNotification INVOKE operations.) Map Operations TIA/EIA-.-D Modifications

30 N.S00-A v.0. Map Parameters.. General... Parameter Identifiers (TIA/EIA-.-D, page -) Table TIA/EIA- MAP Parameter Identifiers Parameter Identifier Name Parameter Identifier Code Reference H G F E D C B A Range gj InvokingNEType gt TIA/EIA-.-D Modifications Map Parameters

31 N.S00-A v Parameter Definitions...gj Range (New for TIA/EIA-.-D Section..) The Range (RANGE) parameter is used to specify the length of a range of consecutive numbers. Identifier Comments Notes: Field Value Type Reference Notes Range IMPLICIT Unsigned Integer a. The length of the range is the value indicated. M... variable octets M... H G F E D C B A Octet Notes MSB Range LSB n a Map Parameters TIA/EIA-.-D Modifications

32 N.S00-A v.0...gt InvokingNEType The InvokingNEType (INVNE) parameter may be used to specify the type of network entity invoking an operation. Identifier Comments Notes: Field Value Type Reference Notes InvokingNEType IMPLICIT Unsigned Integer M... variable octets M... H G F E D C B A Octet Notes a. Ignore extra octets, if received. Send only defined (or significant) octets. NE Type (octet ) Value 0 Not used. HLR. MC. values through through NE Type n a Meaning Reserved. Treat the same as value 0, Not used. Reserved for TIA/EIA- protocol extension. If unknown, treat the same as value 0, Not used. 0 0 TIA/EIA-.-D Modifications Map Parameters

33 N.S00-A v TIA/EIA-.-D MODIFICATIONS This section provides the additions to TIA/EIA--D Chapter needed for Roamer Database Verification. Intersystem Procedures.ZZ.ZZ..ZZ. Roamer Database Verification Request (new for TIA/EIA-.-D Section ) HLR Initiating a Roamer Database Verification Request to a VLR When an HLR determines that an MSID range at a VLR database shall be verified, it shall perform the following: Include the MSCID parameter set to the HLR identity. Include the MSID parameter set to the starting point of the range of MSIDs to examine. Include the Range parameter set to the number of MSIDs in the range to be examined, if applicable. Send a RoamerDatabaseVerificationRequest INVOKE to the VLR. Start the Roamer Database Verification Request Timer (RDVRT). WAIT for a Roamer Database Verification Request response. WHEN a RETURN RESULT is received: - Stop the timer (RDVRT). - IF the message cannot be processed: -- Execute the Local Recovery Procedures task (see..). - ENDIF. WHEN a RETURN ERROR or REJECT is received - Stop the timer (RDVRT). - Execute the Local Recovery Procedures task (see..). WHEN the timer (RDVRT) expires: - Execute the Local Recovery Procedures task (see..). 0 ENDWAIT. Exit this task. VLR Receiving RoamerDatabaseVerificationRequest INVOKE When a VLR receives a RoamerDatabaseVerificationRequest INVOKE, it shall perform the following: IF the received message can be processed: - IF any part of the received MSID range is not associated with the requesting HLR: -- Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting HLR. Intersystem Procedures TIA/EIA-.-D Modifications

34 N.S00-A v.0.zz. - ELSE: -- Include applicable parameters. -- Send a RETURN RESULT to the requesting HLR. - ENDIF. ELSE (the received message cannot be processed): - Send a RETURN ERROR with a proper Error Code value (see the following table) to the requesting HLR. ENDIF. Exit this task. Table RETURN ERROR Error Code MSID/HLRMismatch ResourceShortage OperationNotSupported ParameterError SystemFailure UnrecognizedParameterValue HLR Initiating a Roamer Database Verification Request to an MSC When an MC determines that the message routing database used by an MSC to route FeatureRequest INVOKEs and OriginationRequest INVOKEs to HLRs shall be verified, it shall perform the following: Include the MSCID parameter set to the HLR identity. Include the MSID parameter set to the starting point of the range of MSIDs to examine. Include the Range parameter set to the number of MSIDs in the range to be examined, if applicable. Send a RoamerDatabaseVerificationRequest INVOKE to the MSC. Start the Roamer Database Verification Request Timer (RDVRT). WAIT for a Roamer Database Verification Request response. WHEN a RETURN RESULT is received: - Stop the timer (RDVRT). - IF the message cannot be processed: -- Execute the Local Recovery Procedures task (see..). - ENDIF. VLR RoamerDatabaseVerificationRequest Response Problem Detection and Recommended Response from VLR to HLR Problem Definition All or part of the received MSID range is not associated with the requesting HLR. A required VLR resource (e.g., internal memory record, VLR is fully occupied) is temporarily not available (e.g., congestion). The requested MAP operation is recognized, but not supported, by the receiving VLR, or the requesting HLR is not authorized. A supplied parameter has an encoding problem. A required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution. A supplied parameter value is unrecognized or has nonstandard values (e.g., Range=0, Range>0,000 for some older VLRs). WHEN a RETURN ERROR or REJECT is received 0 0 TIA/EIA-.-D Modifications Roamer Database Verification Request

35 N.S00-A v ZZ. - Stop the timer (RDVRT). - Execute the Local Recovery Procedures task (see..). WHEN the timer (RDVRT) expires: - Execute the Local Recovery Procedures task (see..). 0 ENDWAIT. Exit this task. MC Initiating a Roamer Database Verification Request to an MSC When an MC determines that one of the message routing database used by an MSC to route MSoriginated SMS messages shall be verified, it shall perform the following: Include the InvokingNEType parameter set to indicate that the INVOKING NE is an MC. IF the database to be verified is the database used for indirect routing of MS-originated SMS messages to the originating MS s MC: - Include the MSID parameter set to the starting point of the range of MSIDs to examine. - Include the Range parameter set to the number of MSIDs in the range to be examined, if applicable. ELSE (the database to be verified is the database used for direct routing of MS-originated SMS messages to the destination MS s MC): - Include the MobileDirectoryNumber parameter set to the starting point of the range of MobileDirectoryNumbers to examine. - Include the Range parameter set to the number of MobileDirectoryNumbers in the range to be examined, if applicable. ENDIF. Send a RoamerDatabaseVerificationRequest INVOKE to the MSC. Start the Roamer Database Verification Request Timer (RDVRT). WAIT for a Roamer Database Verification Request response. WHEN a RETURN RESULT is received: - Stop the timer (RDVRT). - IF the message cannot be processed: -- Execute the Local Recovery Procedures task (see..). - ENDIF. WHEN a RETURN ERROR or REJECT is received - Stop the timer (RDVRT). - Execute the Local Recovery Procedures task (see..). 0 WHEN the timer (RDVRT) expires: 0- Execute the Local Recovery Procedures task (see..). ENDWAIT. Exit this task. Roamer Database Verification Request TIA/EIA-.-D Modifications

36 N.S00-A v.0.zz. MSC Receiving RoamerDatabaseVerificationRequest INVOKE When an MSC receives a RoamerDatabaseVerificationRequest INVOKE, it shall perform the following: IF the received message can be processed: - IF the message was received from an HLR: -- IF any part of the received MSID range is not associated with the requesting HLR: --- Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting HLR. -- ELSE: --- Include applicable parameters. --- Send a RETURN RESULT to the requesting HLR. -- ENDIF. - ELSE (the message was received from an MC): -- IF an MSID range was received AND IF any part of that range is not associated with the requesting MC in the message routing database used for indirect routing of MS-originated SMS messages: --- Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting MC. -- ELSEIF a MobileDirectoryNumber range was received AND IF any part of that range is not associated with the requesting MC in the message routing database used for direct routing of MS-originated SMS messages: --- Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting MC. -- ELSE: --- Send a RETURN RESULT to the requesting MC. -- ENDIF. ELSE (the received message cannot be processed): - Send a RETURN ERROR with a proper Error Code value (see the following table) to the requesting NE. ENDIF. 0 0 TIA/EIA-.-D Modifications Roamer Database Verification Request

37 N.S00-A v ZZ. Exit this task. Table RETURN ERROR Error Code MSID/HLRMismatch ResourceShortage OperationNotSupported ParameterError SystemFailure UnrecognizedParameterValue HLR Initiating a Roamer Database Verification Request to an MC When an HLR determines that the message routing database used by an MC to route SMSRequest INVOKEs to HLRs shall be verified, it shall perform the following: Include the MSCID parameter set to the HLR identity. Include the MobileDirectoryNumber parameter set to the starting point of the range of MobileDirectoryNumbers to examine. Include the Range parameter set to the number of MobileDirectoryNumbes in the range to be examined, if applicable. Send a RoamerDatabaseVerificationRequest INVOKE to the MC. Start the Roamer Database Verification Request Timer (RDVRT). WAIT for a Roamer Database Verification Request response. WHEN a RETURN RESULT is received: - Stop the timer (RDVRT). - IF the message cannot be processed: -- Execute the Local Recovery Procedures task (see..). - ENDIF. WHEN a RETURN ERROR or REJECT is received - Stop the timer (RDVRT). - Execute the Local Recovery Procedures task (see..). WHEN the timer (RDVRT) expires: - Execute the Local Recovery Procedures task (see..). 0 ENDWAIT. Exit this task. MSC RoamerDatabaseVerificationRequest Response Problem Detection and Recommended Response from VLR to HLR Problem Definition All or part of the received MSID or MobileDirectoryNumber range is not associated with the requesting NE. A required MSC resource (e.g., internal memory record, MSC is fully occupied) is temporarily not available (e.g., congestion). The requested MAP operation is recognized, but not supported, by the receiving MSC, or the requesting NE is not authorized. A supplied parameter has an encoding problem. A required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution. A supplied parameter value is unrecognized or has nonstandard values (e.g., Range=0). Roamer Database Verification Request TIA/EIA-.-D Modifications

38 N.S00-A v.0.zz..zz. MC Initiating a Roamer Database Verification Request to an MC When an MC determines that the message routing database used by another MC to relay indirectly routed MS-originated SMS messages to the destination MS s MC shall be verified, it shall perform the following: Include the InvokingNEType parameter set to indicate that the INVOKING NE is an MC. Include the MobileDirectoryNumber parameter set to the starting point of the range of MobileDirectoryNumbers to examine. Include the Range parameter set to the number of MobileDirectoryNumbers in the range to be examined, if applicable. Send a RoamerDatabaseVerificationRequest INVOKE to the MC. Start the Roamer Database Verification Request Timer (RDVRT). WAIT for a Roamer Database Verification Request response. WHEN a RETURN RESULT is received: - Stop the timer (RDVRT). - IF the message cannot be processed: -- Execute the Local Recovery Procedures task (see..). - ENDIF. WHEN a RETURN ERROR or REJECT is received - Stop the timer (RDVRT). - Execute the Local Recovery Procedures task (see..). WHEN the timer (RDVRT) expires: - Execute the Local Recovery Procedures task (see..). 0 ENDWAIT. Exit this task. MC Receiving RoamerDatabaseVerificationRequest INVOKE When an MC receives a RoamerDatabaseVerificationRequest INVOKE, it shall perform the following: IF the received message can be processed: - IF the message was received from an HLR: -- IF any part of the received MobileDirectoryNumber range is not associated with the requesting HLR: --- Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting HLR. -- ELSE: --- Send a RETURN RESULT to the requesting HLR. -- ENDIF. - ELSE (the message was received from an MC): -- IF any part of the received MobileDirectoryNumber range is not associated with the requesting MC: 0 0 TIA/EIA-.-D Modifications Roamer Database Verification Request

39 N.S00-A v Send a RETURN ERROR with the Error Code set to indicate MSID/HLRmismatch to the requesting MC. -- ELSE: --- Send a RETURN RESULT to the requesting MC. -- ENDIF. ELSE (the received message cannot be processed): - Send a RETURN ERROR with a proper Error Code value (see the following table) to the requesting NE. ENDIF. Exit this task. Table RETURN ERROR Error Code MSID/HLRMismatch ResourceShortage OperationNotSupported ParameterError SystemFailure UnrecognizedParameterValue MC RoamerDatabaseVerificationRequest Response Problem Detection and Recommended Response from VLR to HLR Problem Definition All or part of the received MSID or MobileDirectoryNumber range is not associated with the requesting NE. A required MSC resource (e.g., internal memory record, MSC is fully occupied) is temporarily not available (e.g., congestion). The requested MAP operation is recognized, but not supported, by the receiving MSC, or the requesting NE is not authorized. A supplied parameter has an encoding problem. A required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution. A supplied parameter value is unrecognized or has nonstandard values (e.g., Range=0). Roamer Database Verification Request TIA/EIA-.-D Modifications

40 N.S00-A v.0 Operation Timer Values Timer RDVRT Roamer Database Verification Request Timer Table Default (sec.) Operation Timer Values RoamerDatabase- VerificationRequest INVOKE is sent (see TIA/EIA-.-D, page -0) Started when Normally stopped when Action when timer expires RoamerDatabase- VerificationRequest RETURN RESULT or RETURN ERROR is received Execute recovery procedures 0 0 TIA/EIA-.-D Modifications Operation Timer Values