DOCSLIB.ORG

Previously Inter- Service Provider IP Backbone Guidelines) Version 13.0 17 October 2016

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Previously Inter- Service Provider IP Backbone Guidelines) Version 13.0 17 October 2016 GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) Guidelines for IPX Provider networks (Previously Inter- Service Provider IP Backbone Guidelines) Version 13.0 17 October 2016 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2016 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V13.0 Page 1 of 50 GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) Table of Contents 1. Introduction 3 1.1 Overview 3 1.1.1 Purpose 3 1.1.2 Background 3 1.1.3 About this Document 4 1.2 Scope 4 1.2.1 In Scope 4 1.2.2 Out of Scope 4 1.3 Definition of Terms 5 1.4 Document Cross-References 7 2 The Need for IP Interconnect 8 2.1 General 8 2.2 IPX 9 3 IPX Network Architecture 9 3.1 IPX Network Connection 9 3.2 IPX Architecture 10 3.3 IPX Connectivity Options 11 3.3.1 IPX Transport 11 3.3.2 IPX Service Transit 11 3.3.3 IP Service Hub 11 3.4 IPX Proxy Services 11 3.5 Types of Service Provider and Interconnectivity Allowed 12 4 Requirements of the IPX Networks 12 4.1 General 12 4.2 Separation of IPX Services on IPX Networks 13 4.3 Number of IPX Providers used to Transit Packets between Service Providers 13 4.4 Connections between IPX Provider and Service Provider 14 4.5 Peering Interface 14 4.6 Technical Specification of the IPX Network 15 4.6.1 IP Routing 15 4.6.2 BGP-4 Advertisement Rules 16 4.6.3 IPX Service to VLAN/VPN Mapping and Advertisement 16 4.6.4 IP Addressing and Routing 18 4.6.5 DNS 19 4.6.6 Security and Screening 19 4.6.7 QoS 19 4.6.8 Generic IPX Proxy Requirements 20 5 Technical Requirements for Service Providers 20 5.1 General Service Provider Requirements 20 5.1.1 Service Provider IP Routing 21 5.1.2 Service Provider IP Addressing 21 5.1.3 Service Provider DNS 21 5.1.4 Service Provider Security and Screening 21 V13.0 Page 1 of 50 GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) 5.2 BGP Advertisement Rules 22 5.2.1 General Rules 22 5.3 Service Provider and IPX Network Connectivity 23 6 QoS 24 6.1 SLA for IPX Network 24 6.1.1 Service Guarantees 24 6.1.2 Responsibilities 24 6.2 Traffic classification 25 6.2.1 UMTS QoS parameters 25 6.2.2 EPS QoS Class Identifiers 25 6.2.3 Diffserv Per Hop Behaviour 25 6.2.4 IPX traffic classes 26 6.2.5 Differentiated Services Code Point 26 6.2.6 2G/3G and EPS traffic marking 26 6.2.7 Application traffic marking 27 6.2.8 Packet marking rules 27 6.3 IP QoS Definitions for IPX Network 28 6.3.1 Availability 28 6.3.2 Delay 29 6.3.3 Jitter 32 6.3.4 Packet Loss Rate 34 7 Traffic Applications 34 7.1 GPRS/3G Data Roaming 34 7.2 Service Provider Bilateral Services 35 7.3 WLAN Roaming 35 7.4 MMS Interworking 36 7.5 IMS 36 Annex A Considerations for implementation 38 A.1 A.1 Double IPX Provider network problem 38 A.1.1 Short term solution: Network configuration 38 A.1.2 Short-term solution disadvantages 39 A.1.3 Long-term solution: Network design in Service Provider network 39 Annex B IPX Proxy Requirements 42 B.1 Introduction 42 B.2 Requirements for IPX Proxy 42 B.2.1 General 42 Annex C Document Management 47 C.1 Document History 47 Other Information 49 V13.0 Page 2 of 50 GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) 1. Introduction 1.1 Overview 1.1.1 Purpose The internet Protocol (IP) Packet eXchange (IPX) Network is an inter-Service Provider IP backbone which comprises the interconnected networks of IPX Providers and General Packet Radio Service (GPRS) Roaming eXchange (GRX) Providers. The IPX network supports multiple IPX services. The purpose of this document is to provide guidelines and technical information on how these networks are set-up and interconnect, and how Service Providers will connect to the IPX Provider networks. The services supported on IPX are out of scope for this document and are currently listed in GSMA PRD AA.51. An IPX service is a service that is part of the IPX releases and that requires the IPX network for either isolation from the Internet and/or for quality of service and experience. The terms IPX and IPX network are better defined in AA.51. Contrary to previous versions of IR.34, GRX is now considered an IPX service which is offered on an IPX Network. The term GRX network is no longer used; however, an entity which only offers the GRX service may refer to itself as a GRX Provider. IPX Provider IPX Provider network Peering for IPX services network including GRX IPX Network Peering for Peering for GRX service only GRX service only GRX Provider network Figure 1: IPX Network comprising interconnected networks of GRX and IPX providers This document also defines high level security requirements for the Inter-Service Provider IP network. Detailed complementary requirements can be found in the Permanent Reference Document (PRD): “Inter-Operator IP backbone Security Requirements for Service Providers and Inter-operator IP Backbone Providers” IR.77 [19]. 1.1.2 Background The IPX Network was originally conceived as an inter-Service Provider IP backbone created to carry GTP-tunnels (GPRS Tunnelling Protocol) via the Gp interface between the GPRS Support Nodes (GSNs) in different GSM Operators that is, data roaming. The Gp interface allowed V13.0 Page 3 of 50 GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) mobile end-users to make use of the GPRS/3G services of their home network while roaming in a visited network. Later, Multimedia Messaging Service (MMS) interworking and Wireless Local Area Network (WLAN) authentication data roaming were added as supported services. This original inter-Service Provider IP backbone is in fact an Inter-PLMN (Public Land Mobile Network) IP Backbone and was termed the GRX. The GRX model is used to interconnect in excess of 300 networks and has proven highly successful. With the development of IP-based services, interworking of such services has become an industry wide challenge. The GRX model is applicable as an IP interworking solution; however the GRX specification does not meet all the requirements. It has been recognised that by adding interworking specific functionality to the GRX model and offering it to the industry, a common interconnect platform could be established for IP interworking. The enhanced GRX network is called the IPX network and is designed to support a variety of types of Service Providers in a secure and business sustainable way. The core enhancements to the GRX are end-to-end Quality of Service and the introduction of the service awareness which facilitates interconnect cascade billing and multi-lateral interconnect agreements. 1.1.3 About this Document The document provides a brief introduction to the requirement for IP interworking and the IPX network. The technical architectures of the IPX network are described followed by the technical implementation guidelines for IPX (and GRX) Providers and connecting Service Providers. Technical guidelines for Security, Quality of Service and Traffic applications are also given. Appendices provide details on known issues in the IPX Network and on the requirements for IPX proxies. 1.2 Scope 1.2.1 In Scope IPX Network: an inter-Service Provider IP backbone network architecture which connects Mobile Network Operators (MNOs), Fixed Network Operators (FNOs) Internet Service Providers (ISPs) and Application Service Providers (ASPs), from here on in referred to collectively as "Service Providers". Where there is specific reference to a Service Provider type they shall be directly referred to in each case. Technical guidance to Service Providers for connecting their IP based networks and services together to achieve roaming and/or inter-working services between them. Recommendations for IP addressing. (Applies to inter- and intra-Service Provider nodes only). Host name recommendations remain within the scope of the present document but are further defined in PRD IR.67. 1.2.2 Out of Scope IP addressing and host names of GPRS user plane (that is, mobile stations) and service elements (for example, Wireless Application Protocol (WAP) Gateway) located beyond the Gi reference point.
Load more

Recommended publications
  • Gs Mec 011 V1.1.1 (2017-07)
    ETSI GS MEC 011 V1.1.1 (2017-07) GROUP SPECIFICATION Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement Disclaimer The present document has been produced and approved by the Mobile Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. 2 ETSI GS MEC 011 V1.1.1 (2017-07) Reference DGS/MEC-0011Plat.App.Enablemen Keywords API, MEC ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]
  • Experimenting with Srv6: a Tunneling Protocol Supporting Network Slicing in 5G and Beyond
    This is a postprint version of the following published document: Gramaglia, M., et al. Experimenting with SRv6: a tunneling protocol supporting network slicing in 5G and beyond. In, 2020 IEEE 25th International Workshop on Computer Aided Modeling and Design of Communication Links and Networks (CAMAD), 14-16 September 2020 (Virtual Conference). IEEE, 2020, 6 Pp. DOI: https://doi.org/10.1109/CAMAD50429.2020.9209260 © 2020 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. Experimenting with SRv6: a Tunneling Protocol supporting Network Slicing in 5G and beyond Marco Gramaglia∗, Vincenzo Sciancalepore†, Francisco J. Fernandez-Maestro‡, Ramon Perez∗§, Pablo Serrano∗, Albert Banchs∗¶ ∗Universidad Carlos III de Madrid, Spain †NEC Laboratories Europe, Germany ‡Ericsson Spain §Telcaria Ideas, Spain ¶IMDEA Networks Institute, Spain Abstract—With network slicing, operators can acquire and Additionally, specific core network functions and procedures manage virtual instances of a mobile network, tailored to a have been introduced to correctly manage network slice life- given service, in this way maximizing flexibility while increasing cycle management operations, such as Network Slice Selection the overall resource utilization. However, the currently used tunnelling protocol, i.e., GTP, might not be the most appropriate Function (NSSF), Network Slice Selection Assistance Infor- choice for the envisioned scenarios, given its unawareness of mation (NSSAI), and so on.
    [Show full text]
  • Release Notes Release 10.3.0.2 E98788-01
    Oracle® Communications Performance Intelligence Center Oracle Communications Performance Intelligence Center Release Notes Release 10.3.0.2 E98788-01 November 2019 Oracle® Communications Performance Intelligence Center Oracle Communications Performance Intelligence Center Release Notes, Release 10.3.0.2 Copyright © 2003, 2019 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notices are applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Development Guide
    DEVELOPMENT GUIDE FOR INDUSTRIAL USING NB-IoT ABOUT THE GSMA ABOUT THE GSMA INTERNET OF THINGS The GSMA represents the interests of mobile PROGRAMME operators worldwide, uniting more than 750 operators with over 350 companies in the broader The GSMA’s Internet of Things Programme is an mobile ecosystem, including handset and device industry initiative focused on: makers, software companies, equipment providers and internet companies, as well as organisations in COVERAGE of machine friendly, cost effective adjacent industry sectors. The GSMA also produces networks to deliver global and universal benefits industry-leading events such as Mobile World Congress, Mobile World Congress Shanghai, Mobile CAPABILITY to capture higher value services World Congress Americas and the Mobile 360 beyond connectivity, at scale Series of conferences. CYBERSECURITY to enable a trusted IoT where For more information, please visit the GSMA security is embedded from the beginning, at every corporate website at www.gsma.com. stage of the IoT value chainBy developing key enablers, facilitating industry collaboration and Follow the GSMA on Twitter: @GSMA. supporting network optimisation, the Internet of Things Programme is enabling consumers and businesses to harness a host of rich new services, connected by intelligent and secure mobile networks. Visit gsma.com/iot or follow gsma.at/iot to find out more about the GSMA IoT Programme. 02 DEVELOPMENT GUIDE FOR INDUSTRIAL USING NB-IOT Contents 1. Introduction 04 2. Examples of Industrial Applications 04 2.1. Smart Industrial Factory Monitoring 04 2.2. Industrial Goods Tracker 04 3. NB-IoT in the Industrial Application Lifecycle 05 3.1. Smart Industrial Factory Monitoring 08 3.2.
    [Show full text]
  • Security for the Core Network of Third Generation Mobile Systems
    Security for the core network of third generation mobile systems GUNTER HORN, DIRK KROSELBERG Siemens AG, Corporate Technology, D-81730 Muenchen, Germany STEFANPUTZ T-Mobil, P.O. Box 300463, D-53184 Bonn, Germany ROLAND SCHMITZ T-Nova Technology Centre, D-64307 Darmstadt, Germany Keywords: UMTS, MAP Security, Multimedia domain, SIP, IPSec, IKE, Key Management Abstract: This contribution gives a survey of the present standardisation activities by 3GPP (3'd Generation Partnership Project1) in the area of security for signalling in the core network of third generation mobile systems. We give an overview of the protocols that need to be secured, present the basic principles behind the overall security architecture and describe the key management and format of secured messages, as far as they have already been finalised. In particular, we address core network security aspects of the 3GPP multimedia domain. 1 3GPP was formed by regional standards organisations from Europe, Asia and North America to produce specifications for a third generation mobile system named UMTS which is designed to evolve from GSM core network. There is a competing effort known as 3GPP2 with partners from North America and Asia. The original version of this chapter was revised: The copyright line was incorrect. This has been corrected. The Erratum to this chapter is available at DOI: 10.1007/978-0-387-35413-2_36 R. Steinmetz et al. (eds.), Communications and Multimedia Security Issues of the New Century © IFIP International Federation for Information Processing 2001 298 1. THREATS TO CORE NETWORK SECURITY FOR MOBILE RADIO NETWORKS The core network of mobile radio systems is the part of the network which is independent of the radio interface technology of the mobile terminal.
    [Show full text]
  • Ts 129 274 V10.9.0 (2013-01)
    ETSI TS 129 274 V10.9.0 (2013-01) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 (3GPP TS 29.274 version 10.9.0 Release 10) 3GPP TS 29.274 version 10.9.0 Release 10 1 ETSI TS 129 274 V10.9.0 (2013-01) Reference RTS/TSGC-0429274va90 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • ETSI TR 101 338 V1.1.6 (2000-07) Technical Report
    ETSI TR 101 338 V1.1.6 (2000-07) Technical Report Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Analysis of existing roaming techniques applicable to TIPHON mobility services 2 ETSI TR 101 338 V1.1.6 (2000-07) Reference DTR/TIPHON-07001 Keywords internet, network, protocol, roaming, telephony ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:+33492944200 Fax:+33493654716 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/ If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards
    [Show full text]
  • Master's Thesis Template
    DEGREE PROGRAMME IN WIRELESS COMMUNICATIONS ENGINEERING MASTER’S THESIS INTEGRATION OF LORA WIDE AREA NETWORK WITH THE 5G TEST NETWORK Author Rumana Yasmin Supervisor Prof. Ari Pouttu Second Examiner Dr. Heikki Karvonen Technical Advisor M.Sc. Juha Petäjäjärvi, M.Sc. Konstantin Mikhaylov April 2017 Yasmin R. (2017) Integration of LoRa Wide Area Network with the 5G Test Network. University of Oulu, Degree Programme in Wireless Communications Engineering. Master’s Thesis, 63 p. ABSTRACT The global communication network is going through major transformation from conventional to more versatile and diversified network approaches. With the advent of virtualization and cloud technology, information technology (IT) is merging with telecommunications to alter the conventional approaches of traditional proprietary networking techniques. From radio to network and applications, the existing infrastructure lacks several features that we wished to be part of 5th Generation Mobile Networks (5G). Having a support for large number of applications, Internet of Things (IoT) will bring a major evolution by creating a comfortable, flexible and an automated environment for end users. A network having the capability to support radio protocols on top of basic networking protocols, when blended with a platform which can generate IoT use cases, can make the expectations of 5G a reality. Low Power Wide Area Network (LPWAN) technologies can be utilized with other emerging and suitable technologies for IoT applications. To implement a network where all the technologies can be deployed virtually to serve their applications within a single cloud, Network Functions Virtualization (NFV) and Software Defined Network (SDN) is introduced to implement such a networking possibility for upcoming technologies.
    [Show full text]
  • Ts 129 060 V12.6.0 (2014-10)
    ETSI TS 129 060 V12.6.0 (2014-10) TECHNICAL SPECIFICATION Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface (3GPP TS 29.060 version 12.6.0 Release 12) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS 3GPP TS 29.060 version 12.6.0 Release 12 1 ETSI TS 129 060 V12.6.0 (2014-10) Reference RTS/TSGC-0429060vc60 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]
  • MEC(18)000003R1
    MEC(18)000003r1 Title*: Way Forward On Terminology Acronyms from Source*: Virtuosys Limited Contact: Mark Cannon input for Committee*: MEC Contribution For*: Decision X Discussion Information Submission date*: 2018-01-09 Meeting & Allocation: MEC#88-Tech - Relevant WI(s), or RGS/MEC-0001v211Terms deliverable(s): Decision/action requested: Please approve ABSTRACT: This contribution discusses some alternative approaches for defining MEC acronyms in the Phase 2 specification documents. Some specific proposals are made that are intended to promote a consistent approach. 1/7 MEC(18)000003r1 1 Introduction There was some discussion at the last face-to-face meeting in Chandler (MEC#12) about the best approach for defining MEC acronyms in the specification documents. This document describes some alternative approaches that could be adopted and makes some specific proposals that are intended to promote a consistent approach across all the Phase 2 specifications and to reduce the burden on anyone making a change to the documents. The MEC-specific and non-MEC specific acronyms are treated separately in clauses 2 and 3. A summary of all the acronyms from all the currently active specifications is shown in the Annex. The changes in Revision r1 reflect the decisions agreed during MEC#88-Tech. 2 MEC-specific acronyms The most problematic definitions are those that MEC is defining for its own use. Some MEC acronyms are defined identically in multiple Phase 1 documents and this is potentially causing inconsistency and could cause maintenance problems if the same approach is used in Phase 2. Hence the first proposal is that all MEC-specific acronyms are only defined in one place.
    [Show full text]
  • View on 5G Architecture
    5G PPP Architecture Working Group View on 5G Architecture Version 3.0, June 2019 Date: 2019-06-19 Version: 3.0 Dissemination level: Public Consultation Abstract The 5G Architecture Working Group as part of the 5G PPP Initiative is looking at capturing novel trends and key technological enablers for the realization of the 5G architecture. It also targets at presenting in a harmonized way the architectural concepts developed in various projects and initiatives (not limited to 5G PPP projects only) so as to provide a consolidated view on the technical directions for the architecture design in the 5G era. The first version of the white paper was released in July 2016, which captured novel trends and key technological enablers for the realization of the 5G architecture vision along with harmonized architectural concepts from 5G PPP Phase 1 projects and initiatives. Capitalizing on the architectural vision and framework set by the first version of the white paper, the Version 2.0 of the white paper was released in January 2018 and presented the latest findings and analyses of 5G PPP Phase I projects along with the concept evaluations. The work has continued with the 5G PPP Phase II and Phase III projects with special focus on understanding the requirements from vertical industries involved in the projects and then driving the required enhancements of the 5G Architecture able to meet their requirements. The results of the Working Group are now captured in this Version 3.0, which presents the consolidated European view on the architecture design. Dissemination level: Public Consultation Table of Contents 1 Introduction........................................................................................................................
    [Show full text]
  • Guidelines for IPX Provider Networks (Previously Inter- Service Provider IP Backbone Guidelines) Version 14.0 01 August 2018
    GSM Association Non-confidential Official Document IR.34 - Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) Guidelines for IPX Provider networks (Previously Inter- Service Provider IP Backbone Guidelines) Version 14.0 01 August 2018 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2018 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V14.0 Page 1 of 52 GSM Association Non-confidential Official Document IR.34 - Guidelines
    [Show full text]