DOCSLIB.ORG

Experimenting with Srv6: a Tunneling Protocol Supporting Network Slicing in 5G and Beyond

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. the underlay network. In this paper, we analyse the use of an While this effort usually focuses on the control plane and alternative tunnelling protocol to transport user data, namely, management functions, most of the network-slicing-related Segment Routing IPv6 (SRv6). More specifically, we discuss its researches from the user plane perspective are targeting issues qualitative advantages, present a prototype implementation, and carry out an experimental comparison vs. GTP, confirming that at the RAN level. Indeed, achieving flexible network slicing in it constitutes a valid alternative as tunnelling protocol. the network access is fundamental to correctly route “sliced” network flows and to transport service-related (and isolated) I. INTRODUCTION information to the intended core instance in an efficient The success of the upcoming 5th generation of mobile manner. network (5G) and beyond is heavily tied with the implementa- In this context, the GPRS Tunnelling Protocol (GTP) cur- tion of a novel paradigm: network slicing. Strongly supported rently used in mobile networks might not result the best fit by the virtualization and programmability concepts, network to support sliced networks. The reasons are as follows. GTP slicing represents a turning point that allows network operators consists of control-plane (C-plane) and user-plane (U-plane) (NOPs) to acquire and self-manage a virtual instance of a sections, where the former signals movements of a user and mobile network to deliver diverse network services while establishes user-plane data paths by means of tunnels between increasing the overall resource utilization. the end user and an anchor-node (over IP-based backhaul However, higher flexibility and augmented revenues might network). This reduces the complexity as the control-plane come at a price. Technical challenges have to be solved while does not require communication with the underlay networks installing network slicing along all network domains, such as (such as MPLS label-switched paths, VLANs, L3-VPNs and (Radio) Access Network (R)AN, Transport and Core. Such so on). However, when network slices are in place, the orches- a domains need a simultaneous and efficient interaction to tration solution should be aware of the underlay networks, to properly provide service-level agreement (SLA) guarantees: guarantee the expected SLAs from the U-plane perspective. this is accomplished by a novel architectural block, dubbed To solve the above problem while keeping the network de- as Management and Orchestration (MANO), able to control, ployment simple, it would be recommendable to integrate the monitor and trigger actions onto each network (virtual) func- U-plane into a layer that forwards packets through requested tion. As a result, networks supporting slicing require advanced data-paths (note that GTP do not support such operation). orchestration solutions that have attracted interest from both The most appropriate network layer able to integrate all the industry and academia showing advantages and drawbacks in required functions is the end-to-end IP layer. More specifically, current deployments. an IPv6-enabled layer might play a relevant role in this con- Interestingly, the main standardization bodies (ISGs) have text, given the “limitless” amount of available address space also listed network slicing in their priority activities. Recently, that can be used for multiplexing mobile sessions between 3GPP has released the first official guidelines for 5G net- tunnel endpoints of the user-plane. works (Rel-15) wherein the network slicing concept has been The IPv6 layer might also integrate network functions into unveiled associated with novel use cases and new standard- it—as specified by the IETF work on Segment Routing IPv6 ization blocks. In particular, four different main classes have (SRv6) [2]—thereby enabling that forwarding functions are been defined: extreme/enhanced Mobile Broadband (x/eMBB), represented as IPv6 addresses. SRv6 network programming Ultra Low Latency and Reliable Communications (URLLC), might also define different forwarding functions, such as, e.g., massive Machine Type Communications (mMTC) and (re- encapsulation or decapsulation and routing while comprising cently) Vehicular-to-Infrastructure communication (V2X) [1]. VPNs, traffic engineering, and service chaining aspects. Ad- ditionally, SRv6 might also compose data paths in the end-to- end IPv6 address layer by means of network programmability. This adds flexibility as mobile applications only need a single IPv6 layer to run on, for e.g. network resources and optimized paths for low-latency (and high-reliability) may be represented as an IPv6 address. Once they have been abstracted as IPv6 IDs, the C-plane could comprise of slices with them as nodes of the U-plane function (UPF), and deploy required data-paths for mobile applications on them [3]. In this paper, we make the case for the use of SRv6 as a transport protocol in network slicing environments, which include 5G and beyond networks. More specifically, we make Fig. 1. Key components of the data plane in a 5G network. the following contributions: • In Section II, we summarize and compare GTP and SRv6, discussing the qualitative advantages of the latter over the B. GTP-U encapsulation former. The existing encapsulation process is called GTP encapsu- • In Section III, after an overview of the existing alterna- lation and is the one currently used in mobile networks (e.g., tives to implement SRv6, we present our implementation Gn and Gp interfaces in GPRS, Iu, Gn, and Gp interfaces in based on the P4 programming language. UMTS). It has been proposed for 5G Systems as well, i.e., • In Section IV, we present a quantitative performance for the interfaces described above and the Xn interface (i.e., evaluation of SRv6, comparing its performance vs. GTP the one between RAN nodes, which is not considered in this in a number of scenarios. paper). According to its specification [5], the encapsulation Finally, we summarize the main results and sketch new lines consists of adding a GTP-U header to the IP datagram (i.e., for future research in Section V. the T-PDU) and using UDP/IP as transport layer. Both IPv4 II. TUNNELING PROTOCOLS FOR USER DATA TRAFFIC IN and IPv6 traffic types are supported. 5G NETWORKS The GTP-U header, as illustrated in Fig. 2, has a variable length, depending on the number of optional fields. The The tunnelling protocol design is of paramount importance minimum length is 8 bytes and includes the Tunnel End- to properly run network slices. Hereafter, we overview the point Identifier (TEID), which is the key variable towards overall Rel-15 architecture to illustrate the main interfaces forwarding as this element is used by the receiving end of the that have been disclosed by the recently published standard packet to identify the PDP context of the T-PDU. As already guidelines. We then summarize the existing GTP properties discussed in Section I, this protocol does not provide native while shedding the light on the main novelties introduced by path differentiation, and it is already falling short for some of the Segment Routing IPv6 (SRv6) protocol. the use cases envisioned by 5G (we note that the first version A. 3GPP UPF reference points of GTP-U was standardized in [5], more than a decade ago). We summarize in Fig. 1 the 3GPP-related reference points of the User Plane Function (UPF), which are illustrated along C. Segment Routing v6 with other elements of the 5G architecture [4]. The User Segment Routing for IPv6 uses an IPv6 Routing Header Equipment (UE) establishes a data session and gets assigned Extension, the Segment Routing Header (SRH), defined in [6]. the corresponding User Plane Function (UPF) in the core Its structure is depicted in Fig. 2 and consists on the Segment network, responsible of routing and forwarding the traffic back Lists (SL), in which each segment is identified with an IPv6 and forth between the UE and a Data Network (DN). The address, i.e., the SegmentID (SID). The current active segment UPF selects the appropriate transport network for the user is the destination address of the packet, while the next address traffic by means of N4 reference point, which provides an is indicated by the Segments Left field of SRH. interface with the Session Management Function (SMF).
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]
  • 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]
  • Atis 3Gpp Specification
    ATIS 3GPP SPECIFICATION ATIS.3GPP.38.424.V1520 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn data transport (Release 15) Approved by WTSC Wireless Technologies and Systems Committee 3GPP ATIS is committed to providing leadership for, and the rapid development and promotion of, worldwide technical and operations standards for information, entertainment and communications technologies using a pragmatic, flexible and open approach. < http://www.atis.org/ > The text in this ATIS Specification is identical to 3GPP TS 38.424 V15.2.0 (2019-07). Please note that ATIS.3GPP.38.424.V1520 was developed within the Third Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP™. The contents of ATIS.3GPP.38.424.V1520 are subject to continuing work within the 3GPP™ and may change following formal 3GPP™ approval. Should the 3GPP™ modify the contents of ATIS.3GPP.38.424.V1520 it will be re-released by the 3GPP™ with an identifying change of release date and an increase in version number. The user of this Specification is advised to check for the latest version of 3GPP TS 38.424 V15.2.0 (2019-07) at the following address: ftp://ftp.3gpp.org/Specs/ (sorted by release date) The user is further advised to verify the changes over the version listed as the approved basis for this Specification and to utilize discretion after identifying any changes. 3GPP Support Office 650 Route des Lucioles -- Sophia Antipolis Valbonne - FRANCE tel: +33 4 92 94 42 00 fax: +33 4 93 65 47 16 web: http://www.3gpp.org "3GPP" is a registered trademark of ETSI in France and other jurisdictions on behalf of the 3rd Generation Partnership Project Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
    [Show full text]