TIA-EIA-IS-847-A-2002-R2007.pdf

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 telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno 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 manufacturers 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 nonmember 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 internationally. 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 publication. 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 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 the 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 36 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: standards telecommunications industry association; june 1996 ansi/tia/eia-41-d , cellular radiotelecommunications intersystem operations; telecommunications industry association; 1997 tia/eia/is-751 , tia/eia-41-d modifications to support imsi; telecommunications industry association; february 1998 tia/eia/is-847 , roamer database verification, telecommunications industry association; january 2001 4organization this document is organized as follows: the tia/eia-664 modifications sections provides the modifications and additions to tia/eia-664 “cellular features description” for rdv. the tia/eia-41.1-d modifications section provides the modifications and additions to tia/eia-41-d chapter 1 “functional overview” for rdv. the tia/eia/41.4-d modifications sections provides the modifications and additions to tia/eia-41-d chapter 3 “automatic roaming information flows” for rdv. the tia/eia-41.5-d modifications section provides the modifications and additions to tia/eia-41-d chapter 5 “signaling protocol” for the rdv. the tia/eia-41.6-d modifications section provides the modifications and additions to tia/eia-41-d chapter 6 “signaling procedures” for rdv. 5editorial 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-847-a are shown in blue copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 network capabilities3 tia/eia-664 modifi cations tia/eia-664 modifications this section provides wireless features descriptions for roamer database verification (rdv) according to the structure of tia/eia-664 . ynetwork capabilities y.1roamer database verification (rdv) (new section for tia/eia-664) roamer database verification (rdv) enables a home system to verify that a roaming partners 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 mss 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 destinations 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 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 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. copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a tia/eia-664 modifi cations4 roamer database verifi cation (rdv) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 y.1.1normal 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 10,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 providers system to obtain wireless telecommunications service. the hlr can request that a range from one to 10,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 providers 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 subscribers hlr. call detail record rdv does not require call detail information to be recorded. copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 roamer database verifi cation (rdv)5 tia/eia-664 modifi cations y.1.2security 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 . y.1.3exception 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 . y.1.4alternate procedures none identified. y.1.5interactions with other network services none identified. vlr roamer database vlr response msid or mdn range is populatedmismatch with invoking ne hlr mismatch not detected positive msid or mdn range is populatedmismatch with invoking ne hlr mismatch detected negative msid or mdn range is not populated global title addressing is used positive msid or mdn range is not populated global title addressing is not used negative copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a tia/eia-41.1-d modifi cations6symbols and abbreviations 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 tia/eia-41.1-d modifications this section provides modifications and additions to tia/eia-41-d chapter 1 needed for roamer database verification. 4symbols and abbreviations invneinvokingnetype parameter rangerange parameter rdvroamer database verification rdvreqroamerdatabaseverificationrequest invoke rdvreqroamerdatabaseverificationrequest return result rdvrtroamer database verification request timer copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 roamer database verifi cation (rdv) scenarios7 tia/eia-41.4-d modifi cations tia/eia-41.4-d modifications this section provides new operations, administration, and maintenance information flows for roamer database verification according to the structure of tia/eia-41-d chapter 4. yroamer database verification (rdv) scenarios (new section for tia/eia-41.4-d) this section depicts the interactions between network entities in various situations related to rdv. these scenarios are for illustrative purposes only. y.1rdv 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. a.the hlr determines that an rdv query shall be initiated to a vlr. the hlr sends an rdvreq to the vlr. 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. figure 1rdv query: by hlr of msid range in vlr database parametersusagetype mscidhlr mscid.r msidstarting point of the range of msids to examine.r rangenumber of msids to examine (1 to 10,000).o r parametersusagetype transcapvlrs transaction capability. include if applicable.o hlrvlr rdvreq transcap rdvrt a b rdvreq mscid, msid, range copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a tia/eia-41.4-d modifi cations8 roamer database verifi cation (rdv) scenarios 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 y.2rdv 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. a.the hlr determines that an rdv query shall be initiated to a vlr. the hlr sends an rdvreq to the vlr. 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. figure 2rdv query: by hlr of msid range not in vlr database parametersusagetype mscidhlr mscid.r msidstarting point of the range of msids to examine.r rangenumber of msids to examine (1 to 10,000).o r hlrvlr return error error code rdvrt a b rdvreq mscid, msid, range copyright telecommunications industry association provided by ihs under license with eialicensee=ihs employees/1111111001, user=leee, leee not for resale, 11/22/2007 19:22:10 mstno reproduction or networking permitted without license from ihs -,-,- tia/eia/is-847-a 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 roamer database verifi cation (rdv) scenarios9 tia/eia-41.4-d modifi cations y.3rdv 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. 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. b.the msc examines the message routing database used for indirect routing of ms-originated sms messages to the originating mss mc and verifies that the specified range of msids is associated with the requesting mc. the msc sends an empty rdvreq to the mc. figure 3rdv query by mc of msid range in msc database parametersusagetype invneindicates that the query was initiated by an mc.r msidstarting point of the range of msids to examine.r rangenumber of msids to examine.o mcmsc rdvreq rdvrt a b rdvreq invfe, msid, range copyright telecommunications industry association provided