ATIS 1000065-2015 Emergency Telecommunications Service (ETS) Evolved Packet Core (EPC) Network Element Requirement.pdf

《ATIS 1000065-2015 Emergency Telecommunications Service (ETS) Evolved Packet Core (EPC) Network Element Requirement.pdf》由会员分享，可在线阅读，更多相关《ATIS 1000065-2015 Emergency Telecommunications Service (ETS) Evolved Packet Core (EPC) Network Element Requirement.pdf（85页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000065.2015 Emergency Telecommunications Service (ETS) Evolved Packet Core (EPC) Network Element Requirements As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings

2、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, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M,

3、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 toolkits, open source solutions, and

4、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 member of and major U.S. contributo

5、r 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 that the requirements for due p

6、rocess, 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. Substantial agreement means much mo

7、re 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 not in any respect preclude any

8、one, 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 give an interpretation of any A

9、merican 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 sponsor whose name appears on

10、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. Purchasers of American Natio

11、nal Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer Advance Priority-SPR and Advance Priority-HSS; Congestion control; Circuit Switched Fallback (CSFB) to UTRAN/GERAN; CSFB to 1xRTT; Intra-RAT E-UTRAN ha

12、ndover; Inter-RAT (IRAT) handover to/from the UMTS PS domain; and IRAT handover to/from eHRPD. This standard assumes a 3GPP Release 10 system. 2 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time

13、of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. 3GPP1TS 22.011 TS 22.011, Service accessibil

14、ity (Release 8). TS 23.203 TS 23.203, Policy and Charging Control Architecture (Release 10). 1These documents are available from the Third Generation Partnership Project (3GPP) at . ATIS-1000065.2015 2 TS 23.272 TS 23.272, Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 (Relea

15、se 10). TS 23.401 TS 23.401, General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 11). TS 24.008 TS 24.008, Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 10). TS 24.301 TS 24.301, No

16、n-Access Stratum (NAS) protocol for Evolved Packet System (EPS) Stage 3 (Release 11). TS 25.331 TS 25.331, Radio Resource Control (RRC); Protocol specification (Release 10). TS 25.413 TS 25.413, UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling (Release 10). TS 29.018 TS 29

17、.018, General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification (Release 8). TS 29.060 TS 29.060, GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface (Release 8). TS 29.118 TS 29.118, Mobility Management Ent

18、ity (MME) - Visitor Location Register (VLR) SGs interface specification (Release 8). TS 29.212 TS 29.212, Policy and charging control over Gx reference point (Release 8). TS 29.214 TS 29.214, Policy and charging control over Rx reference point (Release 10). TS 29.215 TS 29.215, Policy and Charging C

19、ontrol (PCC) over S9 reference point Stage 3 (Release 8). TS 29.272 TS 29.272, Mobile Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol (Release 10). TS 29.273 TS 29.273, Evolved Packet System (EPS); 3GPP EPS AAA interfaces (Release 8). TS 29.

20、274 TS 29.274, Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C) Stage 3 (Release 10). TS 29.275 TS 29.275, Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols Stage 3 (Release 8). TS 29.277 TS 29.277, Optimised handover procedures and protoco

21、l between EUTRAN access and non-3GPP accesses (S102); Stage 3 (Release 10). TS 29.281 TS 29.281, General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) (Release 8). TS 36.213 TS 36.213, Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 8). T

22、S 36.300 TS 36.300, Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8). TS 36.321 TS 36.321, Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specifica

23、tion (Release 8). TS 36.331 TS 36.331, Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 10). TS 36.413 TS 36.413, Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 10). TS 36.422 TS

24、36.422, Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling transport (Release 8). TS 36.423 TS 36.423, X2 application protocol (X2AP) (Release 8). ATIS-1000065.2015 3 3GPP22A.S0008 3GPP2 A.S0008-D v1.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Ra

25、dio Access Network Interfaces with Session Control in the Access Network, TBD. A.S0014 3GPP2 A.S0014-D v4.0, Interoperability Specification (IOS) for cdma2000 Access Network Interfaces - Part 4 (A1, A1p, A4, and A5 Interfaces), August 2012. X.S0057 3GPP2 X.S0057-B v1.0, E-UTRAN eHRPD Connectivity an

26、d Interworking Core Network Aspects, October 2012. ETSI3ETSI TS 183 017 ETSI TS 183 017, DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol Specification, February 2010. IETF4RFC 3588

27、IETF RFC 3588, Diameter Base Protocol. RFC 4005 IETF RFC 4005, Diameter Network Access Server Application. RFC 4006 IETF RFC 4006, Diameter Credit-Control Application. RFC 4831 IETF RFC 4831, Goals for Network-Based Localized Mobility Management (NETLMM). RFC 5213 IETF RFC 5213, Proxy Mobile IPv6. I

28、TU5M.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. OTHER6GSMA IR.92 IMS Profile for Voice and SMS, Version 6.0, May 2012. GSMA IR.94 IMS Profile for Conversational

29、Video Service, Version 3.0, July 2012. 3 Definitions, Acronyms, common requirements are provided in Sections 5.1 and 5.2. FE-Specific OAM common OAM and Paging procedures. ATIS-1000065.2015 23 4.5.1.4 Paging Priority Beginning with 3GPP Release 10, as part of the Paging procedure, priority marking o

30、f the S1-AP “Paging” message by including the “Paging Priority” IE results in the priority handling of the “Paging” message in times of congestion at the MME and eNodeB. NGN GETS priority is achieved by setting the “Paging Priority” IE to the “PrioLevel1” value. 4.5.1.5 MPS EPS Priority Beginning wi

31、th 3GPP Release 10, the “MPS EPS Priority” is stored in the HSS and in the SPR and is used to indicate that the user is subscribed to MPS (NGN GETS) in the EPS domain. The HSS delivers the “MPS EPS Priority” indicator to the MME at the time of Attach in the S6a “Update-Location-Answer” command. The

32、PCRF receives the “MPS EPS Priority” from the SPR at the time of Attach via the unspecified Sp Interface. 4.5.1.6 MPS Priority Level Beginning with 3GPP Release 10, the “MPS Priority Level” is stored in the SPR and is used to indicate the priority level associated with Service Users MPS. It provides

33、 the priority level of NGN GETS service and is used when the user invokes NGN GETS service. The PCRF receives the “MPS Priority Level” from the SPR at the time of Attach via the unspecified Sp Interface. 4.5.1.7 IMS Signalling Priority Beginning with 3GPP Release 10, the “IMS Signalling Priority” is

34、 stored in the SPR and is used to indicate that the user is subscribed to Advance Priority-SPR. The PCRF receives the “IMS Signalling Priority” from the SPR at the time of Attach via the unspecified Sp Interface. 4.5.1.8 Relationship of Service Users Priority Level & Access Classes For every value o

35、f the Service Users priority level, an NGN GETS subscribed UE is assigned to AC 14 in addition to other access classes. See TS 22.011. AC 14 is used for all Service Users priority levels. 4.5.1.9 Sample Mapping of Service Users Priority Level, Reservation-Priority AVP, & ARP Priority Level Table 4-3

36、 shows a sample mapping of the Service Users priority level to the session level “Reservation-Priority” AVP over the Rx Interface, and to the ARP Priority Level. For NGN GETS subscribers, the Default Bearer and IMS Signaling Bearer get the highest priority ARP from the set allocated by the Service P

37、rovider for NGN GETS use, in this example a value of 2. The Media Bearer ARP is determined based on the session-level “Reservation-Priority” AVP received over the Rx interface. An example of ARP values assigned for voice media bearer as a function of the “Reservation-Priority” AVP received over the Rx interface is also shown in Table 4-3.