1、 TIA-847-B August 2004 (r 7/2009) Roamer Database Verification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assi
2、sting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards a
3、nd Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By
4、 such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the
5、responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-4785-RV2, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Docum
6、ent will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rig
7、hts (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is reque
8、sted, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the pa
9、rties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. TIA do
10、es not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMI
11、TATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY
12、 OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TI
13、A SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATIO
14、N, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENT
15、S WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-847-B123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960i ContentsTIA-41 ENHANCEMENTS FOR ROAMER DATABASE VERIFICATIONCONTENTSList of Figures iiiList of TablesivRevision History
16、vIntroduction . 11 General 12 Objective. 13 References. 24 Organization 25 Editorial Conventions . 3TIA/EIA-664Modifications. 4Y Network Capabilities 4Y.1 Roamer Database Verification (RDV) . 4Y.1.1 Normal Operation 5Y.1.2 Security 5Y.1.3 Exception Procedures or Unsuccessful Outcome 6Y.1.4 Alternate
17、 Procedures 6Y.1.5 Interactions With Other Network Services 6TIA/EIA-41.1-DModifications 74 Symbols and Abbreviations 7TIA/EIA-41.3-D Modifications 8Y Roamer Database Verification (RDV) Scenarios . 8Y.1 RDV Query by HLR of MSID Range in VLR Database . 8Y.2 RDV Query by HLR of MSID Range Not in VLR D
18、atabase 9Y.3 RDV Query by MC of MSID Range in MSC Database. 10Y.4 RDV Query by MC of MSID Range Not in MSC Database 11Y.5 RDV Query by HLR of MSID Range in MSC Database. 12Y.6 RDV Query by HLR of MSID Range Not in MSC Database 13Y.7 RDV Query by MC of MDN Range in MSC Database . 14Y.8 RDV Query by M
19、C of MDN Range Not in MSC Database 15Y.9 RDV Query by HLR of MDN Range in MC Database 16Y.10 RDV Query by HLR of MDN Range Not in MC Database. 17Y.11 RDV Query by MC of MDN Range in MC Database 18TIA-847-BContents ii 12345678910111213141516171819202122232425262728293031323334353637383940414243444546
20、4748495051525354555657585960Y.12 RDV Query by MC of MDN Range Not in MC Database.19TIA/EIA-41.5-D Modifications.205 Data Transfer Services 205.1 SS7-BASED DATA TRANSFER SERVICES 205.1.1 Message Transfer Part 206 Application Services .206.4 Map Operations.206.4.1 General .206.4.1.2 Operation Specifie
21、rs .206.4.2 Operation Definitions .206.4.2.aq RoamerDatabaseVerificationRequest.216.5 Map Parameters 236.5.1 General .236.5.1.2 Parameter Identifiers 236.5.2 Parameter Definitions.246.5.2.gj Range246.5.2.gt InvokingNEType 25TIA/EIA-41.6-D Modifications264 Intersystem Procedures .264.ZZ Roamer Databa
22、se Verification Request264.ZZ.1 HLR Initiating a Roamer Database Verification Request to a VLR 264.ZZ.2 VLR Receiving RoamerDatabaseVerificationRequest INVOKE264.ZZ.3 HLR Initiating a Roamer Database Verification Request to an MSC274.ZZ.4 MC Initiating a Roamer Database Verification Request to an MS
23、C284.ZZ.5 MSC Receiving RoamerDatabaseVerificationRequest INVOKE294.ZZ.6 HLR Initiating a Roamer Database Verification Request to an MC304.ZZ.7 MC Initiating a Roamer Database Verification Request to an MC314.ZZ.8 MC Receiving RoamerDatabaseVerificationRequest INVOKE315 Operation Timer Values 33TIA-
24、847-B123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960iii List of FiguresLIST OF FIGURESIntroductionTIA/EIA-664 ModificationsTIA/EIA-41.1-D ModificationsTIA/EIA-41.3-D ModificationsFigure 1 RDV Query by HLR of MSID Range in VLR Database.
25、. . . . . . . . . . . . . . . . . . . . . . 8Figure 2 RDV Query by HLR of MSID Range Not in VLR Database . . . . . . . . . . . . . . . . . . . 9Figure 3 RDV Query by MC of MSID Range in MSC Database . . . . . . . . . . . . . . . . . . . . . . 10Figure 4 RDV Query by MC of MSID Range Not in MSC Datab
26、ase . . . . . . . . . . . . . . . . . . . 11Figure 5 RDV Query by HLR of MSID Range in MSC Database . . . . . . . . . . . . . . . . . . . . . 12Figure 6 RDV Query by HLR of MSID Range Not in MSC Database . . . . . . . . . . . . . . . . . . 13Figure 7 RDV Query by MC of MDN Range in MSC Database. . .
27、 . . . . . . . . . . . . . . . . . . . . 14Figure 8 RDV Query by MC of MDN Range Not in MSC Database . . . . . . . . . . . . . . . . . . . 15Figure 9 RDV Query by HLR of MDN Range in MC Database . . . . . . . . . . . . . . . . . . . . . . . 16Figure 10 RDV Query by HLR of MDN Range Not in MC Databas
28、e . . . . . . . . . . . . . . . . . . . 17Figure 11 RDV Query by MC of MDN Range in MC Database . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 12 RDV Query by MC of MDN Range Not in MC Database . . . . . . . . . . . . . . . . . . . . 19TIA/EIA-41.5-D ModificationsTIA/EIA-41.6-D Modificatio
29、nsTIA-847-BList of Tables iv 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960LIST OF TABLESIntroductionTIA/EIA-664 ModificationsTIA/EIA-41.1-D ModificationsTIA/EIA-41.3-D ModificationsTIA/EIA-41.5-D ModificationsTable 1 MTP Message Prior
30、ity Values for TIA/EIA-41 Operations 20Table 8 TIA/EIA-41 MAP Operation Specifiers 20Table 10 Summary of MAP Operations20Table 112 TIA/EIA-41 MAP Parameter Identifiers23TIA/EIA-41.6-D ModificationsTable 1 VLR RoamerDatabaseVerificationRequest Response.27Table 2 MSC RoamerDatabaseVerificationRequest
31、Response 30Table 3 MC RoamerDatabaseVerificationRequest Response.32Table 63 Operation Timer Values.33TIA-847-B123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960v Revision HistoryREVISION HISTORYFOREWORDThis specification is for use in conj
32、unction with TIA-41-D Chapters 1, 3 and 6 and withTIA-41-E Parts 000 and 5xx.Version Date0 January 2001 Initial PublicationA June 2002 Enhancement for HLR TelecommunicationsIndustry Association; June 1996.2 3GPP2: N.S0005, Cellular Radiotelecommunications Intersystem OperationsCCSA: YD/T-1031-1999;
33、Cellular Radiotelecommunications Intersystem OperationsTIA: ANSI/TIA/EIA-41-D, Cellular Radiotelecommunications IntersystemOperations; Telecommunications Industry Association; December 1997TTA: TTAE.3G-N.S0005; Radiotelecommunications Intersystem Operations3 3GPP2: N.S0009, TIA/EIA-41-D Modification
34、s to Support IMSICCSA: CWTS-MC-N.S0009-0; YD/T-1031-1999; TIA/EIA-41-D Modifications toSupport IMSITIA: TIA/EIA/IS-751, TIA/EIA-41-D Modifications to Support IMSI;Telecommunication Industry Association; February 1998TTA: TTAE.3G-N.S0009; TIA/EIA-41-D Modifications to Support IMSITTC: JP-3GB-N.S0009;
35、 TIA/EIA-41-D Modifications to Support IMSI4 3GPP2: N.S0025-A, Roamer Database VerificationTIA: TIA/EIA/IS-847-A, Roamer Database Verification; TelecommunicationsIndustry Association; June 20024 ORGANIZATIONThis document is organized as follows: The TIA/EIA-664 Modifications sections provides the mo
36、difications and additions toTIA/EIA-664 “Cellular Features Description” for RDV. The TIA/EIA-41.1-D Modifications section provides the modifications and additionsto TIA/EIA-41-D Chapter 1 “Functional Overview” for RDV. The TIA/EIA/41.3-D Modifications sections provides the modifications and addition
37、sto TIA/EIA-41-D Chapter 3 “Automatic Roaming Information Flows” for RDV. The TIA/EIA-41.5-D Modifications section provides the modifications and additionsto TIA/EIA-41-D Chapter 5 “Signaling Protocol” for the RDV.TIA-847-B12345678910111213141516171819202122232425262728293031323334353637383940414243
38、4445464748495051525354555657585960Editorial Conventions 3 Introduction The TIA/EIA-41.6-D Modifications section provides the modifications and additionsto TIA/EIA-41-D Chapter 6 “Signaling Procedures” for RDV.5 EDITORIAL CONVENTIONSThe following editorial conventions are used for this Interim Standa
39、rd: 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 underlinedTIA-847-B123456789101112131415161718192021222324252627282930313
40、233343536373839404142434445464748495051525354555657585960TIA/EIA-664 Modifications 4 Network CapabilitiesTIA/EIA-664 MODIFICATIONSThis section provides wireless features descriptions for Roamer Database Verification (RDV)according to the structure of TIA/EIA-664.Y Network CapabilitiesY.1 Roamer Data
41、base Verification (RDV)(New Section for TIA/EIA-664)Roamer Database Verification (RDV) enables a home system to verify that a roaming partnersVLR database is correctly loaded for the MSID number ranges that “belong” to the homeservice provider. At the request of the HLR, the VLR examines its roamer
42、database to verifythat 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 supportnewer capabilities introduced in IS-41-C or in subsequent intersystem standards, including threemessa
43、ge routing databases that may be maintained at an MSC and two message routingdatabases 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 messageto the originating MSs MC. An MSID
44、-based database used for routing an OriginationRequest INVOKE or aFeatureRequest INVOKE to the appropriate HLR. An MDN-based database used for directly routing an MS-originated SMS message tothe destinations MC.The message routing databases that may be maintained at an MC are: An MDN-based database
45、used for routing an SMSRequest INVOKE to the MSs HLR. An MDN-based database that it uses in its role as originating MC to route MS-originated SMS messages to the destinations MC. RDV provides a tool to assist in resolving problems experienced by home system subscriberswhen roaming in the visited sys
46、tem as well as other message routing database related problems.Applicability to Network ConfigurationsRDV is applicable to all network configurations.TIA-847-BRoamer Database Verification (RDV) 5 TIA/EIA-664 Modifications1234567891011121314151617181920212223242526272829303132333435363738394041424344
47、45464748495051525354555657585960Y.1.1 Normal OperationInvocationRDV 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
48、 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 theindicated message routing database and to verify that the data stored for the indicated MSID orMDN range enables the routing of MAP mess
49、ages to the INVOKING NE. The INVOKING NEcan request that contiguous blocks of MSID or MDN entries be examined by theRESPONDING NE. For backward compatibility, HLRs querying VLRs that conform to olderversions of this standard may need to restrict the range to 10,000 numbers.Normal Operation With Successful OutcomeWhen an RDV query is received, the RESPONDING NE authorizes the INVOKING NErequest. If the INVOKING NE is authorized, the RESPONDING NE determines whichmessage routing database to examine based on the type of the INVOKING NE and the type ofrange (MSI
