ATIS 1000066-2016 Emergency Telecommunications Service (ETS) Network Element Requirements for IMS-based Next Generation Network (NGN) Phase 2.pdf

《ATIS 1000066-2016 Emergency Telecommunications Service (ETS) Network Element Requirements for IMS-based Next Generation Network (NGN) Phase 2.pdf》由会员分享，可在线阅读，更多相关《ATIS 1000066-2016 Emergency Telecommunications Service (ETS) Network Element Requirements for IMS-based Next Generation Network (NGN) Phase 2.pdf（97页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000066.2016 Emergency Telecommunications Service (ETS) Network Element Requirements for IMS-based Next Generation Network (NGN) Phase 2 As a leading technology and solutions development organization, the Alliance for Telecommunications Industr

2、y Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, 5G, network functions virtualization, big data analytics, cloud services, device soluti

3、ons, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkit

4、s, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a membe

5、r of and major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI t

6、hat the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Subst

7、antial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does n

8、ot in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances g

9、ive an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or

10、sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard

11、. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer IM call model; Stage 2 (Release 11). TS 23.228 3GPP TS 23.228, IP Multimedia Subsystem (IMS); Stage 2 (Release 11). TS 24

12、.229 3GPP TS 24.229, Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 11). TS 29.212 3GPP TS 29.212, Policy and charging control over Gx reference point (Release 11). TS 29.213 3GPP TS 29.213,

13、Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping (Release 11). TS 29.214 3GPP TS 29.214, Policy and charging control over Rx reference point (Release 11). TS 29.215 3GPP TS 29.215, Policy and Charging Control (PCC) over S9 reference point; Stage 3 (Release

14、11). TS 29.228 3GPP TS 29.228, IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents (Release 11). TS 29.229 3GPP TS 29.229, Cx and Dx interfaces based on the Diameter protocol; Protocol details (Release 11). TS 29.230 3GPP TS 29.230, Diameter applications; 3GPP sp

15、ecific codes and identifiers (Release 11). TS 29.238 3GPP TS 29.238, Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 (Release 11). 1These documents are available from the Third Generation Partnership Project (3GPP) at . ATIS-1000066.2016 2

16、 TS 29.328 3GPP TS 29.328, IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents (Release 11). TS 29.329 3GPP TS 29.329, Sh Interface based on the Diameter protocol; Protocol details (Release 11). TS 29.332 3GPP TS 29.332, Media Gateway Control Function (MGCF) IM Media Ga

17、teway; Mn Interface (Release 11). TS 29.333 3GPP TS 29.333, Multimedia Resource Function Controller (MRFC) Multimedia Resource Function Processor (MRFP) Mp Interface; Stage 3 (Release 11). ANSI/ATIS2ATIS-0100003 ATIS-0100003, User Plane Priority Levels for IP Networks and Services, November 2004. AT

18、IS-1000003 ATIS-1000003, Number Portability Databases and Global Title Translations. ATIS-1000006 ATIS-1000006, Signalling Systems No. 7 (SS7) - Emergency Telecommunications Service (ETS). ATIS-1000018.2007 ATIS-1000018.2007, NGN Architecture. ATIS-1000023.2013 ATIS-1000023.2013, ETS Phase 1 Network

19、 Element Requirements for a NGN IMS based Deployments. ATIS-1000049 ATIS-1000049, End-to-End NGN GETS Call Flows, August 2011. ATIS-1000055 ATIS-1000055, Emergency Telecommunications Service Core Network Security Requirements ATIS-1000065.2015 ATIS-1000065.2015, ETS EPC Network Element Requirements.

20、 ATIS-1000067 ATIS-1000067, IP NGN Enhanced Calling Name. ATIS-1000111.2005 ATIS-1000111.2005, Signalling System Number 7 (SS7) Message Transfer Part (MTP) (R2010). ATIS-1000112.2005 ATIS-1000112.2005, Signaling System Number 7 (SS7) Signaling Connection Control Part (R2010). ATIS-1000113.2005 ATIS-

21、1000113.2005, Signaling System No. 7 (SS7) Integrated Services Digital Network (ISDN) User Part (Revision of T1.113-2000) (R2010). ATIS-0100523.2011 ATIS-0100523.2011, ATIS Telecom Glossary 2011, http:/www.atis.org/glossary. ATIS-1000679 ATIS-1000679, Interworking between Session Initiation Protocol

22、 (SIP) and Bearer Independent Call Control or ISDN User Part. T1.114 ANSI T1.114-2004, Signaling System Number 7 (SS7) Transaction Capabilities Application Part (TCAP). IETF3RFC 2396 IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax. RFC 3261 IETF RFC 3261, SIP: Session Initiation Pr

23、otocol. RFC 3550 IETF RFC 3550, RTP: A Transport Protocol for Real-Time Applications. RFC 3725 IETF RFC 3725, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP). RFC 3966 IETF RFC 3966, The tel URI for Telephone Numbers. 2Available from ATIS at . 3The

24、se documents are available from the Internet Engineering Task Force (IETF) at: . ATIS-1000066.2016 3 RFC 4412 IETF RFC 4412, Communications Resource Priority for the Session Initiation Protocol (SIP). RFC 4733 IETF RFC 4733, RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals. RFC 586

25、5 IETF RFC 5865, A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic. RFC 6401 IETF RFC 6401, Resource ReSerVation Protocol (RSVP) Extensions for Admission Priority. IETF draft-ietf-dime-drmp IETF draft-ietf-dime-drmp-05, Diameter Routing Message Priority. ITU4H.248.1 ITU-T Rec

26、ommendation H.248.1, Gateway control protocol: Version 2. H.248.52 ITU-T Recommendation H.248.52, Gateway control protocol: QoS support packages, June 2008. H.248.81 ITU-T Recommendation H.248.81, Gateway control protocol: Gateway Control Protocol: Guidelines on the Use of the International Emergenc

27、y Preference Scheme (IEPS) Call Indicator and Priority Indicator in ITU-T H.248 Profiles, May 2011. M.3060 ITU-T Recommendation M.3060, Principles for the Management of Next Generation Networks, March 2006. M.3400 ITU-T Recommendation M.3400, TMN Management Functions, February 2000. Q.850 ITU-T Reco

28、mmendation Q.850, Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part, May 1998. Y.2171 ITU-T Recommendation Y.2171, Admission Control Priority Levels in Next Generation Networks, September 2006. 3 Definitions, Acronyms, or a s

29、ingle FE may be instantiated into two or more network elements. Only those aspects of the FEs and interfaces that are relevant for NGN GETS are specified in this Standard. ATIS-1000066.2016 9 Figure 4.1 IMS Core Network Architecture within ETS Reference Architecture NOTE 1: This Standard assumes int

30、erconnection to “Other VoIP Networks” is provided via an Interconnection Border Control Function (IBCF). NOTE 2: The interface between a Media Gateway Control Function (MGCF) and an SGW has not been specified by 3GPP. As specified in the 3GPP IMS Release 11 Architecture, the SGW functionality may be

31、 provided within the MGCF. 4.2 Functional Entities The reference architecture presented in Clause 4.1 contains FEs as described in the subclauses that follow. FE-specific requirements are provided in Clause 5.3; common requirements are provided in Clause 5.2. FE-Specific Operations, Administration,

32、Maintenance, and Provisioning (OAM common OAM and to an MGW for IP priority indication. For details, refer to TS 23.002 and TS 23.228. 4.2.11 Multimedia Resource Function Controller (MRFC) An MRFC controls the media stream resources in the MRFP under direction from an S-CSCF or AS. An MRFC interpret

33、s NGN GETS call/session information coming from an AS or S-CSCF and controls the MRFP accordingly. For NGN GETS Voice service, an MRFC applies priority treatment in NGN GETS call/session processing and signaling for GETS-AN and GETS-NT PIN collection, and for GETS-AN DN collection. For details, refe

34、r to TS 23.002 and TS 23.228. 4.2.12 Multimedia Resource Function Processor (MRFP) An MRFP provides media resources under the direction of the MRFC. It may generate media streams (e.g., multimedia announcements), mix incoming media streams for multiple parties, process media streams (e.g., audio tra

35、nscoding, media analysis), or manage access rights to shared resources in a conferencing environment. For NGN GETS Voice service, an MRFP applies priority treatment based on instruction from an MRFC, and associated GETS AS, to provide media resources as necessary for GETS-AN and GETS-NT user interac

36、tions (i.e., digit collection, announcements) and for other features or services identified for NGN GETS. For NGN GETS, the MRFP also performs the digit collection functions. For details, refer to TS 23.002 and TS 23.228. 4.2.13 Policy and Charging Rules Function (PCRF) A PCRF encompasses IP-Access

37、Network policy control decisions and data/media flow-based charging control functionalities. It provides IP-Access Network control regarding the media/data flow detection, gating (e.g., admission control), QoS, and media/data flow-based charging. The PCRF provides management of IP-Access Network QoS

38、 resources necessary to support services to network users. It communicates with the IP-Access Network FEs (e.g., Gateway GPRS Support Node GGSN, Packet Data Support Node PDSN) to provide authorization of resource allocations. It enforces policy decisions with regard to use of the IP-Access Network Q

39、oS resources, including consideration of Service Level Agreements (SLAs). For NGN GETS, a PCRF implements IP-Access Network admission control policies to give an NGN GETS call/session a high likelihood of being successful, including both establishing, maintaining, and terminating the NGN GETS call/s

40、ession in the IP-Access Network. ATIS-1000066.2016 14 This Standard assumes a PCRF either contains or can access a Subscriber Profile Repository (SPR). Within this Standard, the term PCRF also refers to a combined PCRF/SPR. For details, refer to TS 23.203. 4.2.14 Signaling Gateway (SGW) An SGW perfo

41、rms the signaling conversion (both ways) at the transport level between the SS7 based transport of signaling and the IP based transport of signaling (e.g., between SIGTRAN Stream Control Transmission Protocol SCTP/IP and SS7 Message Transfer Part MTP). For NGN GETS Voice service, an SGW recognizes G

42、ETS-related priority markings and performs the appropriate transport level interworking between the SS7-based transport of signaling and the IP-based transport of signaling to support priority treatment across both network types. For details, refer to TS 23.002 and TS 23.228. 4.2.15 Subscription Loc

43、ator Function (SLF) An SLF is: Queried by the I-CSCF during the Registration and Session Setup to get the address of the HSS containing the required subscriber-specific data. Furthermore the SLF is also queried by the S-CSCF during the Registration. Queried by an AS to get the address of the HSS con

44、taining the required subscriber-specific data. An SLF is not required if a Service Provider network only has a single HSS. An SLF may be required for NGN GETS call/session termination. For NGN GETS, the SLF recognizes queries identified as NGN GETS-related and applies priority in processing such que

45、ries and signaling the results. For details, refer to TS 23.002 and TS 23.228. 4.2.16 Transition Gateway (TrGW) A TrGW is located within the media path and controlled by an IBCF. It provides functions like network address/port translation and IPv4/IPv6 protocol translation. For NGN GETS Voice servic

46、e, a TrGW recognizes NGN GETS priority markings in bearer packets, provides priority treatment in processing, and performs the appropriate protocol interworking to preserve the priority markings. For details, refer to TS 23.002. 4.2.17 Number Portability Media/application bandwidth requirements for

47、QoS control. This interface carries NGN GETS-specific information that can be used to trigger priority treatment: P-CSCF - PCRF: Diameter AA-Request (AAR) message. The MPS-Identifier AVP indicates to the PCRF the message is related to an NGN GETS call/session. The Reservation-Priority AVP, as described in Clause 4.3.2.1.2, provides the priority level.