1、The Teleconmiunications Industry Association represents the conmiunications sector of NOTICE TIAIEIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improv
2、ement 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 TIAIEIA from manufacturing or selling products not confor
3、ming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIAIEIA members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TIAIEIA in accord
4、ance with the American National Standards Institute (ANSI) patent policy. By such action, TIAIEIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. TIA STANDARDS TIA Standards contain information deemed to b
5、e 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 TIAIEIA Standard. TIA Standards should be reviewed on an annual b
6、asis by the formulating Committee and a decision made on whether to proceed to develop a TIAIEIA Standard on this subject. TIA Standards must be cancelled by the Committee and removed from the TIAIEIA Standards Catalog before the end of their third year of existence. Publication of this TIA Standard
7、 for trial use and comment has been approved by the Telecommunications Industry Association. Distribution of this TIA Standard for comment shall not continue beyond 60 months from the date of publication. It is expected that following this 36 month period, this TIA Standard, revised as necessary, wi
8、ll be submitted to the American National Standards Institute for approval as an American National Standard. Suggestions for revision should be directed to: Standards December 1997. 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
9、 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Foreword vi TIA-756-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 EDITORIAL KEY II II Il II This section identifies the e
10、ditorial style for the use of left-hand margin vertical diffmarks, right-hand margin vertical diffmarks, single underscore lines, double underscore lines and strike through lines. The editorial style employed is: a. ANSI-41-D completely new text inserted by IS-756: I I A telephone network routing ad
11、dress for a subscriber number, often simply referred to as the telephone number. A telephone network routing address for a subscriber number, often simply referred to as the telephone number. c. ANSI-41-D new text inserted by IS-756: A telephone network routing address for a subscriber number, often
12、 simply referred to as the telephone number. A telephone network routing address for a subscriber number, often simply referred to as the telephone number. A telephone network routing ad Numbering Plan for the ISDN Era; CCITT; 1991. ANSI/TIA/EIA-41-D Cellular Radiotelecommunications Intersystem Oper
13、ations, Telecommunications Industry Association: December 1997. 2.2 INFORMATIVE REFERENCES (TIAIEIA-41-D Chapter 1, page 1-4) CTIA: CTIA Report on Wireless Number Portability; Version 2.0; Cellular Telecommunications Industry Association; July 7, 1998. :CC Docket No. 95-1 16, Second Report and Order
14、, Federal Communications Commission, 1997. 7%3Xm Telecommunications Industry Association; Nvembe? 1998. ANSI/TIA/EIA-124-B Wireless Radio Telecommunications Intersystem Non-Signaling Data Communication DMH (Data Message Handler); Telecommunications Industry Association; November 1998. Normative Refe
15、rences 2 TIAIEIA-41-D Chapter 1 Modifications TIA-756-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 II II 8751 TIA/EIA-IS- TIA/EIA-41 -D ModiJications to support IMSI; Telec
16、ommunications Industry Association; January 1998. 3.1 DEFINITIONS (TIAIEIA-41-D Chapter 1, page 1-5) Defau It Routi na Routing based on the called number, in the absence of number portability information. Directory Number (DN) A telephone network routing address for a subscriber terminal, often simp
17、ly referred to as the telephone number. Donor The switch from which a ported DN was originally ported. Location Routing Number (LRN) A network routing address (e.g., 10-digit NANP formatted number) assigned to uniquely identifj a switch that serves ported numbers. Mobile Directory Number (MDN) A dir
18、ectory number assigned to a mobile subscriber. Number Portability Database (NPDB) A network entity containing associations between ported numbers and their Location Routing Numbers (LRNs). Portable Number A Directory Number (DN) that is part of a portable range (e.g., NPA-NXX) from which one or more
19、 DNs may have been ported. A Portable Number is not necessarily a Ported Number. Ported Number A Directory Number (DN) that has been ported (e.g., moved) from one service provider to another. A Ported Number is also a Portable Number. Ported Number Translation Indicator An indicator within the ISUP
20、Forward Call Indicator (Le., the Mbit) that is set to indicate that the query to a Number Portability DataBase (NPDB) has been successfully performed, or that one is not needed (e.g., intersystem termination to a TLDN). The Ported Number Translation Indicator is used by subsequent switches to preven
21、t extraneous NPDB queries. I I I I I I I I I I I TIAIEIA-41-D Chapter 1 Modifications 3 Informative References TIA-756-A Recipient The switch to which a ported DN has been ported. 4 SYMBOLS AND ABBREVIATIONS (TIAIEIA-41-D Chapter 1, page 1-14) CCPN GAP IMSI LRN MSID NP NPDB NPREQ npreq NPT WNP Defin
22、itions Call Completion to a Portable Number Generic Address Parameter (ISUP parameter) International Mobile Station Identity Location Routing Number Mobile Station Identity (MIN or IMSI) Number Portability Number Portability DataBase NumberPortabilityRequest INVOKE NumberPortabilityRequest RETURN RE
23、SULT Number Portability Timer Wireless Number Portability 4 TIAIEIA-41-D Chapter 1 Modifications 1 4 6 7 8 :g 1 1 :I 2 1 11 1 1 14 21 2 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-756-A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1
24、9 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 5 NETWORK REFERENCE MODEL (TIAIEIA-41-D Chapter 1, page 1-24) Figure 2 presents the functional entities and the associated interface reference points that may logically compri
25、se a cellular network. The model, as defiied herein, is intended to provide a level of abstraction that may facilitate the specification of messages and protocols within ANSI-41 FA/EIA -42. As such, implementations may vary with respect to how the functional entities are distributed among various ph
26、ysical units. In cases where functional entities are combined in the same physical equipment, the interface reference points become internal, and need not adhere to interface standards. II Figure 2 Network Reference Model Note: NPDB Number Portability DataBase 5.1 FUNCTIONAL ENTITIES (TIAIEIA-41-D C
27、hapter 1, page 1-24) II 5.1.x Number Portability DataBase (NPDB) II The NPDB is an entity which manages portability information for a local set of ported Directory Numbers (DNs; e.g., in the North American Numbering Plan). The NPDB associates ported DNs with Location Routing Numbers (LRNs) for subsc
28、ribers who have ported their DNs from one service provider to another. 5.2 INTERFACE REFERENCE POINTS 5.2.x Reference Point 2 (TIAIEIA-41-D Chapter 1, page 1-26) Reference Point Z is the MSC to NPDB interface. TIAIEIA-41-D Chapter 1 Modifications 5 Network Reference Model TIA-756-A 1 2 5.3 RELEVANT
29、REFERENCE POINTS 1 (T/A/A-41-D Chapter 1, page 1-27) For purposes of ANSI-41 %!IA -42 Transactions, the reference points of interest are B, C, D, E, H, M, N, 0 and Z. e. The remaining reference points are for fwther study. 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
30、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 Reference Model 6 TIAIHA-41-D Chapter 1 Modifications TIA-756-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
31、52 53 54 55 56 57 58 59 60 3. TIAIEIA-41-D Chapter 3 “Au tomatic Roam i ng Information Flows” Modifications (T/A/A-41-D Chapter 3, Section 3) Wireless Number Portability Operations (new for TIAIHA-41-D Chapter 3) This section illustrates some typical scenarios related to Wireless Number Portability
32、(WNP) operations. II 4-x II I I 4. XI N u m be r P o r t a b i I it y Re q u e s t (new for T/A/A-4 1 -D Chapter 3) The NumberPortabilityRequest (NPREQ) operation is used to request a Location Routing Number (LRN) for a portable called Directory Number (DN). The following table lists the valid combi
33、nations of invoking and responding FES. II Table 4.x.3 FE Combinations for NPREQ I INVOKINGFE I RESPONDINGFE I MSC 1 NPDB 1 I Case i I One of several possible results is returned: 1. Routing information, containing the LRN associated with the ported called DN. 2. No parameters, indicating the called
34、 DN has not been ported. 3. A RETURN ERROR or REJECT, indicating the occurrence of an abnormal condition. TIAIHA-41-D Chapter 3 Modifications 7 Number Portability Scenarios TIA-756-A call origination Sk). 4. x .2 S u cce s sf u I N u m be r P o rt a b i I i ty Re q u est : - N u m ber Ported, Route
35、to LRN (new for TIAIEIA-41-D Chapter 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a ). . b NPREQ DGTSDIAL npreq ROUTDGTS NPT This scenario describes call setup to a portable Directory Number (DN) that has been ported. The Number Portability DataBas
36、e (NPDB) returns the Location Routing Number (LRN) to the MSC. call setup -,* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II . c . . . . . . . d 2E 25 3c 3 34 Figure 4.x.2 Successful NumberPortabilityRequest: - Number Ported, Route to LRN a. b. A call originatio
37、n with called DN is received by the MSC. In this case, the called DN is a portable number and a number portability translation has not been done. The MSC sends a NumberPortabilityRequest (NPREQ) to the NPDB. I Parameters I Usage I Type I I DGTSDIAL I Used to indicate the called DN. 171 1 MSCID 1 Use
38、d to identify the querying MSC. 171 c. The NPDB sends a npreq back to the MSC. The RoutingDigits parameter includes the LRN associated with the ported called DN. I Parameters I Usage ITypeI I ROUTDGTS I Used to indicate the LRN. 171 Number Portability Scenarios 8 TIAIEIA-41-D Chapter 3 Modifications
39、 TIA-756-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 d. Using the LRN, the MSC selects an outgoing trunk group and sets up the call. If the call is routed using ISUP signa
40、ling, the called DN is populated in the Generic Address Parameter (GAP), with the Type of Address Indicator set to PortedNumber. The LRN is populated in the Called Party Number parameter. The Ported Number Translation Indicator is set to number translated. Optionally, provisioned data may be present
41、 indicating whether the CCPN enhancements to ISUP should be used for outgoing calls on the selected ISUP trunk group. If such data is present, and if that data indicates that the CCPN enhancements should not be used, then the called DN (rather than the LRN) is signaled in the ISUP Called Party Numbe
42、r parameter, the ISUP Ported Number Translation Indicator is set to indicate number not translated and a GAP with Type of Address set to PortedNumber is not included. If the call is routed using other signaling (e.g., MF), the LRN may be used to select an outgoing trunk group. Neither the LRN nor an
43、 indication that the called number has been translated for portability are carried in the signaling. TIAIEIA-41-D Chapter 3 Modifications 9 Number Portability Scenarios TIA-756-A 3: 3 3E 3E 37 3E 35 4c 4 4. x .3 S u cce s sf u I N u m be r P o rt a b i I i ty Re q u est : - N u m ber Not Ported, Emp
44、ty RETURN RESULT (new for TIAIEIA-41-D Chapter 3) This scenario describes call setup when the called Directory Number (DN) has not been ported. The Number Portability DataBase (NPDB) returns an empty response to the MSC. II ild. NPREQ DGTSDIAL . . . . b call origination & . . . . . . . . . . . . . .
45、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a . c FT npreq 1 I cai1 setup I -,q ., . . d Figure 4.x.3 Successful NumberPortabilityRequest: - Number Not A call origination with the called DN is received by the MSC. Ported, Empty RETURN RESULT a. b. In this case, the called DN is
46、a portable number and a number portability translation has not been done. The MSC sends a NumberPortabilityRequest (NPREQ) to the NPDB. The parameters are as in Section 4.x.2 Step-b. The NPDB sends an empty npreq back to the MSC to indicate the called number has not been ported. The MSC sets up the
47、call using the called DN. If the call is routed using ISUP signaling, the called DN is populated in the Called Party Number parameter and the Ported Number Translation Indicator is set to number translated. If the call is routed using other signaling (e.g., MF), an indication that the called number
48、has been translated for portability is not carried in the signaling. c. d. Number Portability Scenarios 10 TIAIEIA-41-D Chapter 3 Modifications TIA-756-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
49、 53 54 55 56 57 58 59 60 4. x .4 U n s u c ce ss f u I N u m ber P o r t a b i I it y Re q u est - RET U R N ERROR (new for T/A/A-41-D Chapter 3) This scenario describes call setup to a portable Directory Number (DN) when the ported number translation cannot be completed due to an error. The Number Portability DataBase (NPDB) RETURN ERROR Error Code value identifies the type of error to the MSC. . b NPREQ DGTSDIAL NpT NumberPortabilityRequest RETURN ERROR error code . c I cai1 setup I -,% . . . . . . . . . . . . . . . . . . . . . . . . . . . .
