TIA-756-A-1-2002 TIA EIA-41-D Enhancements for Wireless Number Portability C Phase II Addendum 1《补遗1-TIA EIA-41-D 无线便携性增强 第II阶段》.pdf

《TIA-756-A-1-2002 TIA EIA-41-D Enhancements for Wireless Number Portability C Phase II Addendum 1《补遗1-TIA EIA-41-D 无线便携性增强 第II阶段》.pdf》由会员分享，可在线阅读，更多相关《TIA-756-A-1-2002 TIA EIA-41-D Enhancements for Wireless Number Portability C Phase II Addendum 1《补遗1-TIA EIA-41-D 无线便携性增强 第II阶段》.pdf（10页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA DOCUMENT TIA/EIA-41-D Enhancements for Wireless Number Portability Phase II Addendum 1 TIA-756-A-1 (Addendum No. 1 to TIA-756-A) SEPTEMBER 2002 (Reaffirmed January 2008) TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of N

2、OTICE 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 assisting the purchaser in selecting and obtaining with minimum dela

3、y the proper product for their particular need. The existence of such Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use

4、by non-TIA members, either domestically or internationally. TIA DOCUMENTS TIA Documents 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 commen

5、ts which is a procedural part of the development of a American National Standard (ANS). TIA documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise, withdraw, or proceed to develop an American National Standard on this subject.

6、 Suggestions for revision should be directed to: Standards & Technology Department, Telecommunications Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201 U.S.A. (From Project No. 3-4186-AD1, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Wireless Intersystem Technol

7、ogy.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2002 Standards & Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering D

8、ocuments, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/standards/search_n_order.cfm All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Or

9、ganizations may obtain permission to reproduce a limited number of copies through entering into a license agreement. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 U.S.A. or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 NOT

10、ICE OF DISCLAIMER AND LIMITATION OF LIABILITY The document to which this Notice is affixed has been prepared by one or more Engineering Committees of the Telecommunications Industry Association (“TIA”). TIA is not the author of the document contents, but publishes and claims copyright to the documen

11、t pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees are expected to conduct their affairs in accordance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are available at http:/www.tiaonline.org/standards/sf

12、g/engineering_manual.cfm. TIAs function is to administer the process, but not the content, of document preparation in accordance with the Manual and, when appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). THE USE OR PRACTICE OF CONTENTS OF THIS DOCUMENT

13、MAY INVOLVE THE USE OF INTELLECTUAL PROPERTY RIGHTS (“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 PATENT APPLICATIONS ARE CLAIMED AND CALLED TO TIAS ATTENTION, A ST

14、ATEMENT FROM THE HOLDER THEREOF IS REQUESTED, 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. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIM

15、ITATION, 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 ACCURAC

16、Y OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION. TIA 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

17、 LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED O

18、F THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Wireless Number Portability TIA-756-A-1123456789101112131415161718192021222324252627282930313233

19、343536373839404142434445464748495051525354555657585960i ContentsCONTENTSRevision History iiChanges to Assumptions.1Assumptions.1TIA-756-A-1 Wireless Number PortabilityRevision History ii123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960REV

20、ISIONHISTORYRevision Date Remarks0 March 1998 Initial Publication (WNP Phase I)A December 1998 (WNP Phase II)Addendum 1 September 2002 NP Queries for Emergency Services CallsWireless Number Portability TIA-756-A-1123456789101112131415161718192021222324252627282930313233343536373839404142434445464748

21、495051525354555657585960Assumptions 1 Changes to AssumptionsCHANGESTOASSUMPTIONSThis Addendum identifies the changes to the TIA/EIA/IS-756-AAssumptions section thatare needed to support Number Portability (NP) Query for emergency services calls thathave portable called numbers.ASSUMPTIONS(See TIA/EI

22、A/IS-756-A, page viii)The following items are basic understandings used during the development of thisdocument:a. MobileDirectoryNumbers MDNs are the only wireless service providers E.164numbering resource that may be ported (e.g., Temporary Local DirectoryNumbers TLDNs, Remote Feature Control RFC p

23、orts, Roamer Ports are notported).b. This Number Portability document considers only “circuit mode calls.”c. Automatic Code Gapping (ACG) has not been addressed in this document.d. Short Message Service (SMS) has not been addressed in this document.e. Feature interaction support (e.g., Calling Name

24、Presentation CNAP) has notbeen addressed in this document.f. WNP impacts on message accounting (e.g., TIA/EIA-124) recommendations havenot been addressed in this document. g. WNP impacts to interface standards (e.g., TIA/EIA-93) have not been addressedsupported in this document. h. Only limited loca

25、tion portability is supported consistent with ANSI.T1.660. Thedesignation of portable numbers1may vary between systems. Establishing thegeographical areas within which Number Portability (NP) must be supported isbeyond the scope of this document.i. Number Portability DataBases (NPDBs) do not maintai

26、n records for numberswhich are not ported.j. NP queries are performed by an MSC for all calls to numbers recognized asportable numbers, except for calls to portable numbers that are assumed to be notported (see “a” above). NP queries are not performed for calls to operator servicesincluding calls di

27、aled as “0+” calls.NP queries are not performed for emergencyservices (e.g., 9-1-1) calls.k.TIA/EIA/IS-751MobileStationIdentity (MSID)(i.e., InternationalMobileStationIdentity IMSI or MobileIdentificationNumberMIN) is not portable.l. Public Switched Telephone Network (PSTN) directory numbers may be

28、portable.m. The HLR operations (i.e., messages) have not been modified to support WNP. Nonew parameters, new parameter fields or new parameter values have been addedto existing HLR operations and no support is provided for HLR initiated NumberPortability queries.1See Section 3.1 (page 3) for definit

29、ion of terms.TIA-756-A-1 Wireless Number Portability)Changes to Assumptions 2 Assumptions123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960n. An MSC which is Number Portability capable and has ISUP facilities supportsANSI.T1.660on those fa

30、cilities.o. Call looping should be avoided. However, no mechanism is provided by thisstandard to accomplish that objective.p. Roamer ports allow calls only to MSs known to be present in that system. NPqueries are not performed for Roamer Port calls unless the called MSs HLRredirects the call from th

31、e MS to a portable number.q. ANSI ISUP Release Cause value 26, Misrouted call to ported number, issupported to identify mismatches between the NPDB and HLR. Refinements tothe use of Cause value 26 are for further study.r. An MSC knows which DN ranges are portable, but an MSC does not necessarilyknow

32、 which individual MDNs have been ported.s. When the MSC is not able to obtain portability information from the NPDB, theMSC will default route the call.t. When a call is default routed to the donor MSC, and that MSC attempts to deliverthe call, the MSC performs a NumberPortabilityRequest (NPREQ) que

33、ry to do so.u. In a Number Portability environment the MobileIdentificationNumber (MIN) andMobileDirectoryNumber (MDN) may be different.v. Only the MDN shall be used by the Serving MSC in call services to identify thesubscriber externally (e.g., Emergency Services call back number, AutomaticNumber I

34、dentification). The Serving MSC shall not, in the absence of a successfulHLR response, make any assumption as to the equivalence of an MDN and a MIN.w. As this standard does not require the HLR to distinguish vacant numbers fromnumbers which have ported out, implementation specific HLR operations (e

35、.g.,signaling optimizations, forwarding number validation) may need to be modifiedso that service is not impacted. The required modifications are not addressed inthis document.x. An NP capable MSC may support an ISUP trunk group option for signaling theported number instead of the LRN as the called party number for outgoing callssent on that trunk group.y. Transit call handling (e.g., tandem calls) has not been addressed in this document.z. “Aging” and “Number Pooling” of MDNs have not been addressed in thisdocument, including their implications on the use of ANSI Cause value 26.