1、 TIA/EIA INTERIM STANDARD TIA/EIA/IS-847-A Roamer Database Verification TIA/EIA/IS-847-A (Revision of TIA/EIA/IS-847) July 2002(Reaffirmed-January 2007) TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunica
2、tions Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufactur
3、ers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmembe
4、r of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA members, whether the standard is to be used either domestically or internationall
5、y. Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publicatio
6、n. TIA/EIA INTERIM STANDARDS TIA/EIA Interim Standards contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of
7、the development of a TIA/EIA Standard. TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decision made on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim Standards must be cancelled by the Committee and removed from t
8、he TIA/EIA Standards Catalog before the end of their third year of existence. Publication of this TIA/EIA Interim Standard for trial use and comment has been approved by the Telecommunications Industry Association. Distribution of this TIA/EIA Interim Standard for comment shall not continue beyond 3
9、6 months from the date of publication. It is expected that following this 36 month period, this TIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards Institute for approval as an American National Standard. Suggestions for revision should be directed to
10、 Standards Telecommunications IndustryAssociation; June 1996ANSI/TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations;Telecommunications Industry Association; 1997TIA/EIA/IS-751, TIA/EIA-41-DModifications to Support IMSI; TelecommunicationsIndustry Association; February 1998TIA/EIA
11、/IS-847, Roamer Database Verification, Telecommunications IndustryAssociation; January 20014 ORGANIZATIONThis document is organized as follows: The TIA/EIA-664Modifications sections provides the modifications and additions toTIA/EIA-664“Cellular Features Description” for RDV. The TIA/EIA-41.1-DModif
12、ications section provides the modifications and additionsto TIA/EIA-41-DChapter 1 “Functional Overview” for RDV. The TIA/EIA/41.4-DModifications sections provides the modifications and additionsto TIA/EIA-41-DChapter 3 “Automatic Roaming Information Flows” for RDV. The TIA/EIA-41.5-DModifications se
13、ction provides the modifications and additionsto TIA/EIA-41-DChapter 5 “Signaling Protocol” for the RDV. The TIA/EIA-41.6-DModifications section provides the modifications and additionsto TIA/EIA-41-DChapter 6 “Signaling Procedures” for RDV.5 EDITORIAL CONVENTIONSThe following editorial conventions
14、are used for this Interim Standard: underline: additionscross 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-
15、847-Aare shown in blueCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/EIA/IS-847-A1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
16、51525354555657585960Network Capabilities 3 TIA/EIA-664 ModificationsTIA/EIA-664MODIFICATIONSThis section provides wireless features descriptions for Roamer Database Verification (RDV)according to the structure of TIA/EIA-664.Y Network CapabilitiesY.1 Roamer Database Verification (RDV)(New Section fo
17、r 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 database to verifythat subscribers wit
18、hin 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-Cor in subsequent intersystem standards, including threemessage routing databases that may be mainta
19、ined 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-based database used for routing an Ori
20、ginationRequest 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 used for routing an SMSRequest INVOKE t
21、o 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 system as well as other message routing da
22、tabase related problems.Applicability to Network ConfigurationsRDV is applicable to all network configurations.Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/EIA/IS-847-ATI
23、A/EIA-664 Modifications 4 Roamer Database Verification (RDV)123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Y.1.1 Normal OperationInvocationRDV is initiated by any of the following: An HLR query to a VLR regarding an MSID range. An MC qu
24、ery 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
25、theindicated message routing database and to verify that the data stored for the indicated MSID orMDN range enables the routing of MAP messages to the INVOKING NE. The INVOKING NEcan request that contiguous blocks of MSID or MDN entries be examined by theRESPONDING NE. For backward compatibility, HL
26、Rs querying VLRs that conform to olderversions of this standard may need to restrict the range to 10,000 numbers.RDV is initiated by an HLR query to a VLR. The HLR requests the VLR to examine its roamer databaseand to verify that the data stored for the indicated MSID range enables roaming subscribe
27、rs from therequesting service providers system to obtain wireless telecommunications service. The HLR can requestthat a range from one to 10,000 contiguous MSID entries be examined by the VLR.Normal Operation With Successful OutcomeWhen an RDV query is received, the RESPONDING NE authorizes the INVO
28、KING 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 (MSID or MDN) that has been provided for examination.The RESPONDING NE then examines that message routing database for the
29、 indicated range ofMSIDs or MDNs to determine whether the data needed to send a MAP message to theINVOKING NE is stored in the entries corresponding to that range. The RESPONDING NEresponds with a positive confirmation if every entry corresponding to that range is populated forthe INVOKING NE, or if
30、 an entry is not populated and global title addressing is used forcommunication 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 ro
31、amingsubscribers from the requesting service providers system can obtain service. The VLR responds with apositive confirmation if every MSID in the range is populated for the requesting HLR, or if an MSID entryis not populated, global title addressing is used for communication with the roaming subsc
32、ribers HLR.Call Detail RecordRDV does not require call detail information to be recorded.Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/EIA/IS-847-A123456789101112131415161
33、718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Roamer Database Verification (RDV) 5 TIA/EIA-664 ModificationsY.1.2 SecurityThe RESPONDING NE VLR authorizes the INVOKING NE HLR request to determine whetherthe requested MSID or MDN information shall be provided.
34、 Upon receipt of the RDV query,the RESPONDING NE VLR determines if the INVOKING NE HLR is associated with thereceived MSID or MDN range. A positive acknowledgment is only returned if there is nomismatch.A negative response from the RESPONDING NE VLR only indicates that the MSID or MDNrange does not
35、match the message routing roamer database entries for the INVOKING NErequesting HLR. No indication shall be sent as to whether the MSID or MDN range exists in thedatabase or not. The RESPONDING NE VLR does not provide any indication that would leadto a conclusion about MSID or MDN ranges that are no
36、t associated with the INVOKING NEHLR.Y.1.3 Exception Procedures or Unsuccessful OutcomeThe RESPONDING NE VLR provides a negative response to the INVOKING NE HLR if theINVOKING NE HLR is not authorized for the RDV query. The RESPONDING NE VLRresponds with a RETURN ERROR. The Error Code is set to indi
37、cate OperationNotSupported.The RESPONDING NE VLR provides a negative response to the INVOKING NE HLR if theMSID or MDN range (the entire range or any part of the range) is not populated for theINVOKING NEHLR. The RESPONDING NE VLR responds with a RETURN ERROR. TheError Code is set to indicate MSID/H
38、LRMismatch. Y.1.4 Alternate ProceduresNone identified.Y.1.5 Interactions With Other Network ServicesNone identified.VLR Roamer DatabaseVLR ResponseMSID or MDN range is populated Mismatch with INVOKING NE HLR mismatch not detectedPositiveMSID or MDN range is populated Mismatch with INVOKING NE HLR mi
39、smatch detectedNegativeMSID or MDN range is not populated global title addressing is usedPositiveMSID or MDN range is not populated global title addressing is not usedNegativeCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or netw
40、orking permitted without license from IHS-,-,-TIA/EIA/IS-847-ATIA/EIA-41.1-D Modifications 6 Symbols and Abbreviations123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960TIA/EIA-41.1-DMODIFICATIONSThis section provides modifications and addi
41、tions to TIA/EIA-41-DChapter 1 needed forRoamer Database Verification.4 SYMBOLS AND ABBREVIATIONSINVNE InvokingNEType parameterRANGE Range parameterRDV Roamer Database VerificationRDVREQ RoamerDatabaseVerificationRequest INVOKErdvreq RoamerDatabaseVerificationRequest RETURN RESULTRDVRT Roamer Databa
42、se Verification Request TimerCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/EIA/IS-847-A123456789101112131415161718192021222324252627282930313233343536373839404142434445464
43、748495051525354555657585960Roamer Database Verification (RDV) Scenarios 7 TIA/EIA-41.4-D ModificationsTIA/EIA-41.4-D MODIFICATIONSThis section provides new Operations, Administration, and Maintenance information flows forRoamer Database Verification according to the structure of TIA/EIA-41-D Chapter
44、 4.Y Roamer Database Verification (RDV) Scenarios(New Section for TIA/EIA-41.4-D)This section depicts the interactions between network entities in various situations related toRDV. These scenarios are for illustrative purposes only.Y.1 RDV Query: by HLR of MSID Range in VLR DatabaseThis scenario des
45、cribes an RDV query when the MSID range indicated by the HLR is loaded inthe VLR database.a. The HLR determines that an RDV query shall be initiated to a VLR. The HLR sends anRDVREQ to the VLR.b. The VLR examines its roamer database and verifies that the specified range of MSIDs isassociated with th
46、e requesting HLR. The VLR sends an rdvreq to the HLR.Figure 1 RDV Query: by HLR of MSID Range in VLR DatabaseParameters Usage TypeMSCID HLR MSCID. RMSID Starting point of the range of MSIDs to examine. RRANGE Number of MSIDs to examine (1 to 10,000). O RParameters Usage TypeTRANSCAP VLRs transaction
47、 capability. Include if applicable. OHLR VLRrdvreq TRANSCAPRDVRTabRDVREQ MSCID, MSID, RANGE Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/EIA/IS-847-ATIA/EIA-41.4-D Modifi
48、cations 8 Roamer Database Verification (RDV) Scenarios123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Y.2 RDV Query: by HLR of MSID Range Not in VLR DatabaseThis scenario describes an RDV query when the MSID range indicated by the HLR is
49、 notassociated with that HLR.a. The HLR determines that an RDV query shall be initiated to a VLR. The HLR sends anRDVREQ to the VLR.b. The VLR examines its roamer database and determines that the entire MSID range or anypart of the MSID range is not associated with the requesting HLR. The VLR sends aRETURN ERROR to the HLR with the Error Code set to ind
