DOCSLIB.ORG

MEC for Automotive in Multi-Operator Scenarios

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
MEC for Automotive in Multi-Operator Scenarios MEC for Automotive in Multi-Operator Scenarios 5GAA Automotive Association Technical Report CONTACT INFORMATION: Copyright © 2021 5GAA. All Rights Reserved. Lead Coordinator – Thomas Linget Email: [email protected] No part of this White Paper may be reproduced without written permission. MAILING ADDRESS: 5GAA c/o MCI Munich Neumarkter Str. 21 81673 München, Germany www.5gaa.org VERSION: 1.0 DATE OF PUBLICATION: 03.03.2021 DOCUMENT TYPE: Technical Report CONFIDENTIALITY CLASS: P (Public use) REFERENCE 5GAA WORKING GROUP: Working Group 2 DATE OF APPROVAL BY 5GAA BOARD: 11.01.2021 MEC for Automotive in Multi-Operator Scenarios 2 3 5GAA A-200150 Contents Foreword............................................................................................................................................................. 5 1 Scope ........................................................................................................................................................ 6 2 References ................................................................................................................................................ 7 3 Abbreviations ........................................................................................................................................... 9 4 Definition of Edge Computing ............................................................................................................... 11 4.1 The application perspective (three-tier paradigm) ........................................................................................... 11 5 Overview of Edge Computing architecture principles for V2X (SoA) .................................................. 13 5.1 Relation to 5GAA V2X Application Architecture ........................................................................................... 13 5.2 ETSI MEC architecture and deployment options ............................................................................................ 13 5.2.1 ETSI MEC architecture .............................................................................................................................. 13 5.2.2 ETSI MEC architecture in NFV ................................................................................................................. 15 5.2.3 ETSI MEC deployment options ................................................................................................................. 17 5.2.4 Multi-MNO MEC deployment options ...................................................................................................... 18 5.3 AECC architecture ........................................................................................................................................... 19 5.4 Edge Computing support in 3GPP systems ..................................................................................................... 21 5.4.1 Edge Computing in 3GPP SA5 .................................................................................................................. 22 5.4.2 Edge Computing in 3GPP SA6 .................................................................................................................. 24 5.5 Cloud Native Computing Foundation ............................................................................................................. 26 6 High-level architectural considerations on MEC in multi-MNO scenarios ........................................... 27 6.1 Reference architecture for MEC4AUTO scenarios ......................................................................................... 27 6.2 Introduction to multi-MNO scenarios and assumptions .................................................................................. 27 6.3 Single OEM use case for 3 main scenarios ...................................................................................................... 28 6.3.1 Scenario 1: Both MNO A and MNO B have MEC platform and MEC application X ............................... 28 6.3.2 Scenario 2: Both MNO A and MNO B have MEC platforms, but MEC application X is available only in MNO A .......................................................................................................................................... 28 6.3.3 Scenario 3: Only MNO A has a MEC platform and MEC application X is available only in MNO A ..... 29 6.3.3.1 Scenario 3A: Inter-domain connectivity by means of N9 tunnelling ................................................... 29 6.3.3.2 Scenario 3B: Inter-domain connectivity by means of controlled IP network ....................................... 30 6.4 Multiple OEMs vehicle use case for three main scenarios .............................................................................. 30 6.4.1 Scenario 1: Both MNO A and MNO B have MEC platforms and MEC application Y ............................. 30 6.4.2 Scenario 2: Both MNO A and MNO B have MEC platforms, but MEC application Y is available only in MNO A .......................................................................................................................................... 31 6.4.3 Scenario 3: Only MNO A has a MEC platform and MEC application Y is available only in MNO A ..... 31 6.4.3.1 Scenario 3A: Inter-domain connectivity by means of N9 tunnelling ................................................... 31 6.4.3.2 Scenario 3B: Inter-domain connectivity by means of controlled IP network ....................................... 32 6.5 Open issues ...................................................................................................................................................... 32 6.6 Summary on multi-MNO scenarios on MEC .................................................................................................. 33 7 Deployments for use cases ..................................................................................................................... 34 7.1 Examples of Edge Computing architectures .................................................................................................... 34 7.2 Application layer deployments for MEC4AUTO use cases ............................................................................ 36 7.2.1 UC1: See Through ...................................................................................................................................... 37 7.2.2 UC2: In-Vehicle Entertainment (IVE) ....................................................................................................... 38 7.2.3 UC3: Intersection Movement Assist (IMA) ............................................................................................... 38 7.2.4 UC4: Vulnerable Road User (VRU) .......................................................................................................... 39 7.2.4.1 Deployment according to Scenario 1 .................................................................................................... 39 7.2.4.2 Deployment according to Scenario 2 .................................................................................................... 40 7.2.4.3 Deployment according to Scenario 3 .................................................................................................... 40 7.2.5 UC5: Vehicle Platooning ........................................................................................................................... 41 7.2.5.1 Deployment example (vehicle joining/leaving the platoon) ................................................................. 41 7.2.5.2 Deployment example (changing the platoon head vehicle) .................................................................. 42 7.3 Examples of demonstration/trial implementations ........................................................................................... 42 8 Interoperability and service continuity for Edge Computing ................................................................. 45 8.1 State of requirement ......................................................................................................................................... 45 8.2 MEC service continuity based on N9 forwarding tunnel ................................................................................. 45 4 5GAA A-200150 8.2.1 Network domain solution ........................................................................................................................... 45 8.2.2 Application domain solution ...................................................................................................................... 47 8.2.2.1 Application service retention ................................................................................................................ 48 8.2.2.2 Application instantiation and data migration ........................................................................................ 48 8.2.2.3 Application service redirection ............................................................................................................. 49 8.3 Summary on MEC service continuity .............................................................................................................. 50 9 MEC security guidance .......................................................................................................................... 51 9.1 Security scope .................................................................................................................................................. 51 9.2 MEC4AUTO Shared Responsibility
Load more

Recommended publications
  • The Design of the EMPS Multiprocessor Executive for Distributed Computing
    The design of the EMPS multiprocessor executive for distributed computing Citation for published version (APA): van Dijk, G. J. W. (1993). The design of the EMPS multiprocessor executive for distributed computing. Technische Universiteit Eindhoven. https://doi.org/10.6100/IR393185 DOI: 10.6100/IR393185 Document status and date: Published: 01/01/1993 Document Version: Publisher’s PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication: • A submitted manuscript is the version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website. • The final author version and the galley proof are versions of the publication after peer review. • The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.
    [Show full text]
  • FGVM-02 Architecture of Vehicle Multimedia Systems
    International Telecommunication U n i o n ITU-T Technical Report TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (13 April 2021) Focus Group on Vehicular Multimedia (FG-VM) FGVM-02 Architecture of Vehicle Multimedia Systems - 2 - Acknowledgement This Technical Report was prepared under the leadership of Mr. Jun Li, Chair of ITU-T FG-VM (TIAA, China) and Yajun Kou, Chair of ITU-T FG-VM Working Group 2 (Global Fusion Media Technology and Development Co. Ltd, China). It is based on the contributions of numerous authors who participated in the Focus Group activities. Due credit is given to the following Focus Group participants: Srinivasagan Ayyappan, Yansong Guo (Great Wall Motors, Co, LTD, China); Yajun Kou, Jun Li (Global Fusion Media Technology and Development Co. Ltd, China); Koji Nakao (National Institute of Information and Communications Technology, Japan); Stiepan A. Kovac (QRCrypto SA; CEuniX.eu Project); Paolo Volpato, Francois Fischer (Huawei Technologies); Latif Ladid (IPv6 Forum); Jonas Walter (Technical University of Darmstadt Institute of Ergonomics & Human Factors); Gaëlle Martin-Cocher (InterDigital Canada, Lte, Canada); Prakash Ranganathan (University of North Dakota); Sébastien Ziegler, Anna Brékine, Cédric Crettaz (Mandat International); and Pradipta Biswas (Indian Institute of Science). Srinivasagan Ayyappan (Great Wall Motors, Co, LTD, China) served as the main Editor of this Technical Report. Stefano Polidori (Advisor), Mythili Menon (Project Officer), and Carolina Lima (Assistant) served as the FG-VM Secretariat. -
    [Show full text]
  • Computer Demos—What Makes Them Tick?
    AALTO UNIVERSITY School of Science and Technology Faculty of Information and Natural Sciences Department of Media Technology Markku Reunanen Computer Demos—What Makes Them Tick? Licentiate Thesis Helsinki, April 23, 2010 Supervisor: Professor Tapio Takala AALTO UNIVERSITY ABSTRACT OF LICENTIATE THESIS School of Science and Technology Faculty of Information and Natural Sciences Department of Media Technology Author Date Markku Reunanen April 23, 2010 Pages 134 Title of thesis Computer Demos—What Makes Them Tick? Professorship Professorship code Contents Production T013Z Supervisor Professor Tapio Takala Instructor - This licentiate thesis deals with a worldwide community of hobbyists called the demoscene. The activities of the community in question revolve around real-time multimedia demonstrations known as demos. The historical frame of the study spans from the late 1970s, and the advent of affordable home computers, up to 2009. So far little academic research has been conducted on the topic and the number of other publications is almost equally low. The work done by other researchers is discussed and additional connections are made to other related fields of study such as computer history and media research. The material of the study consists principally of demos, contemporary disk magazines and online sources such as community websites and archives. A general overview of the demoscene and its practices is provided to the reader as a foundation for understanding the more in-depth topics. One chapter is dedicated to the analysis of the artifacts produced by the community and another to the discussion of the computer hardware in relation to the creative aspirations of the community members.
    [Show full text]
  • Open Source Democracy How Online Com M U N I C Ation Is Changing Offline Pol I T I C S
    Pol i t ical struc tur es ne ed to cha n g e. The y wil l eme rg e fr om peopl e acting and comm un i c a t in g in the pres e nt , not talking abou t a fictio nal futur e Open Source Democracy How online com m u n i c ation is changing offline pol i t i c s Douglas Rushkoff About Demos Demos is a greenhouse for new ideas which can improve the quality of our lives.As an independent think tank, we aim to create an open resource of knowledge and learning that operates beyond traditional party politics. We connect researchers, thinkers and practitioners to an international network of people changing politics.Our ideas regularly influence government policy, but we also work with companies, NGOs, colleges and professional bodies. Demos knowledge is organised around five themes, which combine to create new perspectives.The themes are democracy, learning, enterprise, quality of life and global change. But we also understand that thinking by itself is not enough. Demos has helped to initiate a number of practical projects which are delivering real social benefit through the redesign of public services. For Demos, the process is as important as the final product. We bring together people from a wide range of backgrounds to cross-fertilise ideas and experience. By working with Demos, our partners help us to develop sharper insight into the way ideas shape society. www.demos.co.uk © Douglas Rushkoff 2003 Open access. Some rights reserved. As the publisher of this work, Demos has an open access policy which enables anyone to access our content electronically without charge.
    [Show full text]
  • Open Networking & the Security of Open Source Software Deployment
    Open Networking & the Security of Open Source Software Deployment A white paper presenting security considerations for practical deployment January 2021 Table of Contents Executive Summary ......................................................................................................... 5 Welcome ........................................................................................................................... 7 Introduction ...................................................................................................................... 8 Open Source in Virtualised Open Networks ................................................................... 9 The Software Development Process ............................................................................. 11 Shades of Open Source ................................................................................................. 13 Open Interfaces and Open Source Software Are Different .......................................... 15 Two Perspectives: Systems and Component ............................................................... 16 Systems-level Approach ................................................................................................... 17 Component-level approach............................................................................................... 19 Deployment Considerations .......................................................................................... 20 Layered Security Defence ...............................................................................................
    [Show full text]
  • Illuminating the Higher Layers of Mobile Networks
    Beyond the Radio: Illuminating the Higher Layers of Mobile Networks Narseo Vallina-Rodriguez§, Srikanth Sundaresan§, Christian Kreibich§*, Nicholas Weaver§ⱡ, and Vern Paxson§ⱡ TR-14-003 December 2014 Abstract Cellular network performance is often viewed as primarily dominated by the radio technology. However, reality proves more complex: mobile operators deploy and configure their networks in different ways, and sometimes establish network sharing agreements with other mobile carriers. Moreover, regulators have encouraged newer operational models such as Mobile Virtual Network Operators (MVNOs) to promote competition. In this paper we draw upon data collected by the ICSI Netalyzr app for Android to develop a characterization of how operational decisions, such as network configurations, business models, and relationships between operators introduce diversity in service quality and affect user security and privacy. We delve in detail beyond the radio link and into network configuration and business relationships in six countries. We identify the widespread use of transparent middleboxes such as HTTP and DNS proxies, analyzing how they actively modify user traffic, compromise user privacy, and potentially undermine user security. In addition, we identify network sharing agreements between operators, highlighting the implications of roaming and characterizing the properties of MVNOs, including that a majority are simply rebranded versions of major operators. More broadly, our findings highlight the importance of considering higher-layer relationships
    [Show full text]
  • Man Pages Section 6: Demos
    man pages section 6: Demos Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 816–5222–10 December 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Edge Computing for 5G Networks
    5G PPP Technology Board Edge Computing for 5G Networks 5GPPP Technology Board Working Group 5G-IA’s Trials Working Group Edge Computing for 5G Networks Version 1.0 Date: 29-01-2021 Version: 1.0 DOI 10.5281/zenodo.3698117 URL https://doi.org/10.5281/zenodo.3698117 Dissemination level: Public Page 1 / 96 5G PPP Technology Board Edge Computing for 5G Networks Table of Contents Executive Summary ........................................................................................................ 4 1. Introduction - Why Edge Computing is key for 5G and beyond............................ 6 1.1 What is Edge Computing ............................................................................... 6 1.2 Why is Edge Computing critical for 5G ....................................................... 7 1.3 Where is the Edge of the Network ................................................................ 9 1.4 How does the Edge look like? ...................................................................... 12 1.5 Introduction to the 5G Edge Cloud Ecosystem.......................................... 13 2. Key Technologies for 5G on Edge Computing ..................................................... 15 2.1 Resources Virtualization framework .......................................................... 15 2.1.1 Virtual Machines and Containerization ................................................................................... 15 2.1.2 Lightweight virtualization ......................................................................................................
    [Show full text]
  • Clironica Da Semana
    N. 59 - 38 de Fevereiro de 1893 s=» Anno XVIII Rio de Janoiro Domingo ASSIMftTUÍWS PARA OS ESTADOS * 10S000 , MIIWATUIM MW mUl- SiímWTIU ¦i,,,,,1,mu .?5"99i Xn«J;,.:....*• i..^»"-•••;:::;:;;;:iop» PAGAMENTO ADIANTADO TACAMUNTO AIMANTADO TYPOORAPMIA ESCRIPTORIO 70 uva hhth im: m_ . _> ..unuo 7» .o «"A "»» ouviwon *<> NUMERO AVULSO 60 RS. NUMERO AVULSO 60 RS. Sterootypada e impressa nas machinas rotativas de Marinoni, na typographia da ((Gazeta de Noticias » Al auignaluru icwcrmii rio qualquer dia o Irrmiuam nu Iim de março, junli», .piunbro ou ilazemVro Oi ttli.ii cn\ÍAdp* 5 rtdacjlo nio «crio rcsliluiilti ainda que olt pejam publicados sociedade anonyma --rTrarynAifrrrr-mnggr^"'"-" "-"W«ia»iu»:i.riiairi_r,iri ._»»¦«¦«¦»_ E volvou do novo n bcu posto, quedou recomecei oa mona estudos do daiyde novo Interrompe-sei npproxlma- poderiam prosentomonto fuvorecor com paisagem, SPERO DRACOS largo espaço, linmovel, na mesma con- CARTAS DA AUM1A HISTORIAS A VAPOR convencido do quo Jamais apanharia um 110.000 exemplares ao agora um outro carro, o unico. novos recursos o movimento da locallsn- coNsut, n.v tomplnçaooxtatlea. lira ao tempo om quo rou Tiragem touro & unha. (AO SU. OTIIOS I.KON.MIDOS, Esto traz A balda doua rapados farda- çllo d'catos innumoros papeis; faltar- PECADOR POR NECESSIDADE exercito turco, a rampa do Pois apanhei 1 UIIIXIA) o galgando MAU TJOftDAU doa. I" um coupb. A.' illmrgn galopam Ihoa-hla dinheiro o confiança para o desllladeiro, chegava abaixo da torro do cinco nnnos Estava ou uma tardo com Thomaz ds uo soculo, doua soldados. fazer. O govorno, pela sua parte, nocos- Depois do haver residido Kol nos primeiros mezo» Kiapha, aob IvnungI, o cimo coroado dn Duni.iM, 4 do fovcrolro onde cm Dublin, aprendi a Anniinciaç&o, nas terras da Mtilpiqtic, Começara Semana ²E' um ministro.,» slla ser om extremo canto.
    [Show full text]
  • Case No COMP/M.6381 - GOOGLE/ MOTOROLA MOBILITY
    EN Case No COMP/M.6381 - GOOGLE/ MOTOROLA MOBILITY Only the English text is available and authentic. REGULATION (EC) No 139/2004 MERGER PROCEDURE Article 6(1)(b) NON-OPPOSITION Date: 13/02/2012 In electronic form on the EUR-Lex website under document number 32012M6381 Office for Publications of the European Union L-2985 Luxembourg EUROPEAN COMMISSION Brussels, 13/02/2012 C(2012) 1068 In the published version of this decision, some MERGER PROCEDURE information has been omitted pursuant to Article 17(2) of Council Regulation (EC) No 139/2004 ARTICLE 6(1)(b) DECISION concerning non-disclosure of business secrets and other confidential information. The omissions are shown thus […]. Where possible the information PUBLIC VERSION omitted has been replaced by ranges of figures or a general description. PUBLIC VERSION To the notifying party: Dear Sir/Madam, Subject: Case No COMP/M.6381 – Google/Motorola Mobility Commission decision pursuant to Article 6(1)(b) of Council Regulation No 139/2004 1. On 25 November 2011, the European Commission received notification of a proposed concentration pursuant to Article 4 of Council Regulation No 139/20041 by which Google Inc. ("Google", USA), acquires, within the meaning of Article 3(1)(b) of the Merger Regulation, sole control over Motorola Mobility Holdings, Inc. (“Motorola Mobility”, USA)2 by way of purchase of shares.3 Google is designated hereinafter as the "notifying party" whereas Google and Motorola Mobility are referred to as the "parties to the proposed transaction". 2. On 9 December 2011, the Commission adopted two decisions pursuant to Article 11(3) of the Merger Regulation in order to obtain from Google documents which the Commission considered necessary for its assessment of the case.
    [Show full text]
  • 1 Where to Start
    Where to Start Where to Start 1 Where to Start We set out to write a book that could be a system administrator’s trusty companion, providing the practical advice, comfort, and basic system administration theory that you can’t get from reading manual pages. As a result, this book is designed to com- plement—not replace—your system’s documentation. We think this book will help you in five ways: • It will give you an overview of the major administrative systems, identify- ing the different pieces of each and explaining how they work together. • It will introduce general administrative techniques that we have found, through experience, to be worthwhile. • It will help you choose solutions that continue to work well as your site grows in size and complexity. • It will help you sort good ideas from bad and educate you about various atrocities of taste committed by operating system developers. • It will summarize common procedures so that you don’t have to dig through the excessive detail of the manuals to accomplish simple tasks. It’s impossible to perform these functions with perfect objectivity, but we think we’ve made our biases fairly clear throughout the text. One of the interesting things about system administration is the fact that reasonable people can have dramatically dif- ferent notions of what constitute the most appropriate policies and procedures. We 1 2 UNIX System Administration Handbook offer our subjective opinions to you as raw data. You’ll have to decide for yourself how much to accept and to what extent our comments apply to your environment.
    [Show full text]
  • No Slide Title
    Lecture 1: “a small yet powerful operating system” Unix History and Fundamentals Introduction • “Technically, Unix is a simple, coherent system which pushes a few good ideas to the limit.”—Sunil Das • “The greatest virtues of Unix, in my opinion, are those that emerged as a result of the way that it developed.”—Peter Salus • “The growth and development of Unix is an exciting sociological tale. The nature of the individuals and their interactions is what made Unix vital.”—Peter Salus • “UNIX is simple and coherent, but it takes a genius (or at any rate, a programmer) to understand and appreciate its simplicity.”—Dennis Ritchie • The history of Unix is a story of intrigue, adaptability, desire, cunning, intellectual honesty, and the pursuit of freedom and happiness.—Mark Shacklette “it was the summer of ‘69” •The Multics (Multiplexed Information and Computing Service) operating system was being developed jointly by the Computer Research Group at BTL and Fernando Corbato’s MAC (Multiple Access Computers) project at MIT and GE which provided the hardware. Multics: – Was based on CTSS (Compatible Time Sharing System) at MIT – Was to deliver multi-user multitasking support for 300 simultaneous users in an interactive (non-batch) system – Ran on a powerful machine: a GE 645, a 36-bit machine that executed at about .435 MIPS • This was about 30% faster than the original IBM PC (808[6,8]), and a 1000 Mhz Pentium III today is about 2000 times faster than the GE 645 • The GE645 took about an hour to boot Multics Space Travel and New Ideas • Ken
    [Show full text]