1、 International Telecommunication Union ITU-T H.460.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2013) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Supplementary services for multimedia Number portability interworking between ITU-T H.323 and switched circ
2、uit networks Recommendation ITU-T H.460.2 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H.229 Systems aspects H.230H
3、.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359 Quality of service architecture for audi
4、ovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile multimedia
5、 collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559 Mobile multimedia collaboration inter-working procedures H.
6、560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor network applications and Internet of Things H.640H.649 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV Gen
7、eral aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to consumption H.770H.779 Digital Signage H.780H.789 For further details
8、, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.460.2 (03/2013) i Recommendation ITU-T H.460.2 Number portability interworking between ITU-T H.323 and switched circuit networks Summary Recommendation ITU-T H.460.2 describes the procedures and the signalling protocol for Service Pro
9、vider and Location Portability, while interworking with SCN (using SS No. 7 signalling) interfaces in an ITU-T H.323 network. Service Provider Portability allows subscribers to keep their existing phone numbers/addressing scheme even when changing from one service provider to another without changin
10、g their location, and without changing the nature of the service offered. Location Portability allows subscribers to retain their existing phone numbers/addressing scheme even when moving from one location to another. This Recommendation makes use of the “Generic extensibility Framework“ specified i
11、n Recommendation ITU-T H.323 version 4. This revision introduces a number of corrections and clarifications by incorporating technical and editorial corrections from the ITU-T H.323-series Implementers Guide (03/2011). History Edition Recommendation Approval Study Group 1.0 ITU-T H.460.2 2001-07-29
12、16 2.0 ITU-T H.460.2 2013-03-16 16 ii Rec. ITU-T H.460.2 (03/2013) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector
13、 (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every f
14、our years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, t
15、he necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary.
16、 However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the neg
17、ative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the
18、use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendati
19、on, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/
20、www.itu.int/ITU-T/ipr/. ITU 2013 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.460.2 (03/2013) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Abbreviations and acronyms 1 4 Interworking d
21、escription . 2 4.1 Messages and signalling . 2 4.2 ISUP-to-H.225 ingress interworking 3 4.3 ITU-T H.225-to-ISUP egress interworking 4 5 ITU-T H.225.0 generic data usage . 4 6 Description of ASN.1 types and fields . 5 Annex A ITU-T H.460.2 message syntax (ASN.1) 7 Appendix I Number portability within
22、 the United States . 9 I.1 Introduction 9 I.2 Coding the RegionalParameters Sequence . 9 Bibliography. 10 Rec. ITU-T H.460.2 (03/2013) 1 Recommendation ITU-T H.460.2 Number portability interworking between ITU-T H.323 and switched circuit networks 1 Scope This Recommendation specifies the Number Por
23、tability interworking procedures between ITU-T H.323 and SCN networks. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were
24、 valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendat
25、ions is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.225.0 Recommendation ITU-T H.225.0 (2009), Call signalling protocols and media stream packetization for packet-based multimedia com
26、munication systems. ITU-T H.323 Recommendation ITU-T H.323 version 4 (2009), Packet-based multimedia communications systems. ITU-T Q.769.1 Recommendation ITU-T Q.769.1 (1999), Signalling System No. 7 ISDN user part enhancements for the support of number portability. ITU-T Q.850Add.1 Recommendation I
27、TU-T Q.850 (1998), Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part, Addendum 1 (2000). ITU-T T.35 Recommendation ITU-T T.35 (2000), Procedure for the allocation of ITU-T defined codes for non-standard facilities. ITU-T X.68
28、0 Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.681 Recommendation ITU-T X.681 (2008) | ISO/IEC 8824-2:2008, Information technology Abstract Syntax Notation One (ASN.1): Information objec
29、t specification. ITU-T X.691 Recommendation ITU-T X.691 (2008) | ISO/IEC 8825-2:2008, Information technology ASN.1 encoding rules Specification of Packed Encoding Rules (PER). 3 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ARJ RAS Admission Reject ARQ
30、 RAS Admission Request ASN.1 Abstract Syntax Notation one 2 Rec. ITU-T H.460.2 (03/2013) DN Directory (or Dialled) Number IAM Initial Address Message ISUP Integrated Services Digital Network User Part LRJ RAS Location Reject LRQ RAS Location Request NoA Nature of Address indicator NP Number Portabil
31、ity NPSI Number Portability Status Indicator NRN Network Routing Number PSTN Public Switched Telephone Network RAS Registration, Admission, and Status SCN Switched Circuit Network TON Type Of Number 4 Interworking description Number Portability in the SCN is specified in ITU-T Q.769.1. There are sev
32、eral schemes used for transporting the parameter. Separate Directory Number Addressing Method: clause 6.1 of ITU-T Q.769.1. Separate Network Routing Number Addressing Method: Annex B of ITU-T Q.769.1. Concatenated Addressing Method: Annex A of ITU-T Q.769.1. If the query returns no NRN, then the Cal
33、led Party Number parameter in the IAM message contains the Directory Number (dialled-digits). The IAM may contain the Number Portability Forward Information parameter (see Annex E of ITU-T Q.769.1). The following information needs to be conveyed across ITU-T H.323 network to support Number Portabili
34、ty. 1) Network Routing Number (NRN). 2) Directory Number (DN). 3) NP Status indicator (NPSI). 4) Regional Parameters (This parameter may be used to carry national specific or Regional Number Portability standards specific information). 4.1 Messages and signalling It is proposed that the NP parameter
35、s listed above be transported as follows in the ITU-T H.225.0/RAS messages using the generic extensibility framework: 1) The genericData parameter (containing the NumberPortabilityInfo sequence) should be used in the ITU-T H.225.0 Call Signalling (Setup) or RAS (ARQ and LRQ) messages. The genericDat
36、a parameter identifies Number Portability feature and contains the NumberPortabilityData. The NumberPortabilityInfo of the NumberPortabilityData contains the appropriate fields populated. 2) The ISUP NRN is always carried in the ITU-T H.225 Called Party Number IE with its TypeOfNumber (TON) set to N
37、ational (significant) Number. Rec. ITU-T H.460.2 (03/2013) 3 3) A new NumberPortabilityInfo ASN.1 definition is introduced to transport the directory number (DN), NPSI, NRN and regionalParams parameters. 4) A concatenated ISUP NRN and DN are carried concatenated in the Called Party Number IE and the
38、 NumberPortabilityInfo parameter. 5) When a Gatekeeper receives an ARQ or LRQ and determines that the destination number is ported out of the network and it may wish to invoke number portability Query on Release (QoR) procedures (as specified in Annex C of ITU-T Q.769.1). In such cases, the Gatekeep
39、er must respond with ARJ or LRJ that contains a reject reason of genericDataReason. The Gatekeeper should include the genericData of the ARJ/LRJ that contains the NumberPortabilityGenericData with the numberPortabilityRejectReason. The numberPortabilityRejectReason now will have a value of qorPorted
40、Number (=1). This maps to the ISUP release cause value = #14 (QoR: ported number) as specified in ITU-T Q.850Add.1. 4.2 ISUP-to-H.225 ingress interworking NP Parameters in ISUP ITU-T H.225 and NumberPortabilityInfo (inside genericData) Parameters in Setup, ARQ, LRQ NPSI NumberPortabilityInfo.numberP
41、ortabilityData.addressTranslated (if NPSI = query not done, it is not necessary to create a NumberPortabilityInfo parameter; it will be necessary for some downstream switch to do a query) (if NPSI = query done, set addressTranslated = TRUE) Network Routing Number (NRN) in Network Routing Number para
42、meter, DN in Called Party Number parameter a) The NRN is mapped as follows: Called Party Number (Setup) or destinationAddress (ARQ, LRQ messages) (TON=National(significant)Number) and NumberPortabilityInfo.numberPortabilityData.routingAddress (Setup, ARQ, LRQ messages). (portabilityTypeOfNumber = ro
43、utingNumber) b) The DN is mapped as follows: NumberPortabilityInfo.numberPortabilityData.portedAddress Directory number (DN) in Called Directory Number parameter, NRN in Called Party Number parameter a) The NRN is mapped as follows: Called Party Number (Setup) or destinationAddress (ARQ, LRQ message
44、s) (TON=National(significant)Number) and NumberPortabilityInfo.numberPortabilityData.routingAddress (Setup, ARQ, LRQ messages). (portabilityTypeOfNumber = routingNumber) b) The DN is mapped as follows: NumberPortabilityInfo.numberPortabilityData.portedAddress Concatenated NRN + DN in Called Party Nu
45、mber parameter Called Party Number (Setup) or destinationAddress (ARQ,LRQ) (TON = National(significant)Number) and NumberPortabilityInfo.numberPortabilityData.routingAddress (Setup, ARQ, LRQ). (portabilityTypeOfNumber = concatenatedNumber) Regional Parameters NumberPortabilityInfo.numberPortabilityD
46、ata.regionalParams 4 Rec. ITU-T H.460.2 (03/2013) If an NPSI indicating that a query has been done is present in the IAM, or if an NRN is present in the IAM, the genericData parameter (containing the NumberPortabilityInfo sequence) should be used in the ITU-T H.225.0 Call Signalling (Setup) or RAS (
47、ARQ and LRQ) messages. The genericData parameter identifies Number Portability feature and contains the NumberPortabilityData. The NumberPortabilityInfo of the NumberPortabilityData contains the appropriate fields populated as shown in the table above. The portabilityTypeOfNumber field indicates the
48、 TypeOfNumber (TON) of the NRN or DN present in the IAM message. If the NoA of the Routing Number in the IAM message is set to either Routing Number or Concatenated Number, then the routingAddress in NumberPortabilityInfo shall be populated with the Routing Number and its typeOfAddress is set to rou
49、tingNumber or concatenatedNumber respectively. If the NoA of the Routing Number in the IAM message is set to National(significant)Number, then the interworking function may not populate the routingAddress in NumberPortabilityInfo. If the Gatekeeper performs an NP query, it shall provide the NumberPortabilityInfo as a genericData parameter in ACF and LCF messages as specified above. The ingress interworking function, receiving this info in ACF shall send it in Setup message and the egress interworki
