ITU-T H 550-2017 Architecture and functional entities of vehicle gateway platforms (Study Group 16).pdf

《ITU-T H 550-2017 Architecture and functional entities of vehicle gateway platforms (Study Group 16).pdf》由会员分享，可在线阅读，更多相关《ITU-T H 550-2017 Architecture and functional entities of vehicle gateway platforms (Study Group 16).pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T H.550 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2017) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Vehicular gateways and intelligent transportation systems (ITS) Architecture for vehicular gateways Architecture and functional entities of vehicl

2、e gateway platforms Recommendation ITU-T H.550 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H.229 Systems aspects H

3、.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359 Quality of service architecture for

4、 audiovisual and multimedia services H.360H.369 Telepresence H.420H.429 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and service

5、s H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 VEHICULAR GATEWAYS AND INTELLIGENT TRANSPORTATION SYSTEMS (ITS) Architect

6、ure for vehicular gateways H.550H.559 Vehicular gateway interfaces H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor network applications and Internet of Thi

7、ngs H.640H.649 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to

8、consumption H.770H.779 Digital Signage H.780H.789 E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS Personal health systems H.810H.819 Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) H.820H.859 Multimedia e-health data exchange services H.860H.869 For further

9、details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.550 (12/2017) i Recommendation ITU-T H.550 Architecture and functional entities of vehicle gateway platforms Summary Recommendation ITU-T H.550 describes the architecture, functional architecture framework and functional entiti

10、es of vehicle gateway platforms (VGPs). Some signalling flows of VGP are also described in Appendix I. History Edition Recommendation Approval Study Group Unique ID*1.0 ITU-T H.550 2017-12-14 16 11.1002/1000/13434 Keywords Architecture, functional architecture framework, functional entities, signall

11、ing flow, vehicle gateway platforms, VGP. *To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T H.550 (12/2017) FOREWORD The Interna

12、tional Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, oper

13、ating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, p

14、roduce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In

15、this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g.,

16、 interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not sugg

17、est that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evid

18、ence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which m

19、ay be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2018 All rights reserved. No part of this publication may b

20、e reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.550 (12/2017) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventio

21、ns 3 6 Introduction . 3 7 Architecture of VGP . 4 7.1 Functional architecture framework . 6 8 Functional entities of VGP . 8 8.1 Vehicle gateway . 8 8.2 Service functionalities 11 8.3 Services . 14 8.4 Management . 17 Appendix I Signalling flows of VGP 19 I.1 Signalling flows for emergency informati

22、on display in V2V scenario 19 I.2 Signalling flows for traffic data download in V2I scenario . 20 I.3 Signalling flows of remote UI scenario 21 I.4 Signalling flows of emergency call scenario 22 I.5 Signalling flows of anti-stolen scenario . 23 I.6 Signalling flows of remote software update scenario

23、 . 24 I.7 Signalling flows of navigation scenario . 25 Bibliography. 26 Rec. ITU-T H.550 (12/2017) 1 Recommendation ITU-T H.550 Architecture and functional entities of vehicle gateway platforms 1 Scope This Recommendation specifies the architecture, functional architecture framework and functional e

24、ntities for vehicle gateway platforms (VGPs). Some signalling flows of VGP are also described in Appendix I. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of pu

25、blication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of

26、 the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T F.749.1 Recommendation ITU-T F.749.1 (2015), Functional requirements for vehicle gateways. ITU-

27、T F.749.2 Recommendation ITU-T F.749.2 (2017), Service requirements for vehicle gateway platforms. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 driver-vehicle interface (DVI) ITU-T F.749.2: The integrated user interface for the vehic

28、le. It includes visual displays, loudspeakers, microphones, manual input controls, etc. 3.1.2 functional entity b-ITU-T Y.2012: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe pra

29、ctical, physical implementations. 3.1.3 intelligent transport systems (ITS) b-ITU-R handbook: ITS can be defined as systems utilizing the combination of computers, communications, positioning and automation technologies to improve the safety, management and efficiency of terrestrial transport system

30、s. 3.1.4 nomadic devices ITU-T F.749.1: Nomadic devices include all types of information and communication as well as entertainment devices that can be brought into the vehicle by the driver and/or passengers to be used while driving. Examples include mobile phones, portable computers, tablets, mobi

31、le navigation devices, portable media players and multi-functional smart phones. 3.1.5 remote user interface (UI) ITU-T F.749.2: An approach to realize the interaction between applications in nomadic devices and the driver-vehicle interface (DVI). The UI of applications in nomadic devices can be dis

32、played in the vehicles touch screen and drivers are able to control the applications through DVIs (touch screen, buttons etc.). A remote UI can help drivers avoid distraction from applications and thus reduce the probability of accidents. 3.1.6 telematics b-ISO 15638-16: Telematics is the use of wir

33、eless media to obtain and transmit (data) from a distant source. 2 Rec. ITU-T H.550 (12/2017) 3.1.7 vehicle gateway (VG) ITU-T F.749.1: A VG is a device in a vehicle that enables communications between a device in the vehicle and another device which may be physically located either inside the vehic

34、le or outside the vehicle (e.g., roadside station, cloud-based server, etc.). A VG provides standardized interfaces and protocols, communications across heterogeneous networks, optimized network selection based on application needs and network QoS, arbitration and integration of network communicatio

35、ns, security and switching network connections to maintain service continuity. 3.1.8 vehicle gateway platform (VGP) ITU-T F.749.1: A VGP is the collection of ICT hardware and software in a vehicle operating as an open platform to provide an integrated runtime environment for delivering the communica

36、tions services of a VG. A VGP may also provide higher layer communications services such as interaction with the driver through the driver-vehicle access services and so on. Subsystems dedicated solely to vehicle operation are not considered part of the VGP. Supported applications/services include I

37、TS and infotainment. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: API Application Programming Interface CAN Controller Area Network CI Communication Interface DLL Data Link Layer DVA Driver Vehicle Acce

38、ss EAP Extensible Authentication Protocol ECU Electronic Control Unit ETC Electronic Toll Collection GPS Global Positioning System GRE Generic Routing Encapsulation HUD Head Up Display ICT Information and Communications Technology IP Internet Protocol ITS Intelligent Transport System L2TP Layer 2 Tu

39、nnelling Protocol MAC Medium Access Control MAN Metropolitan Area Network MIB Management Information Base NAT Network Address Translation OSI Open System Interconnection POI Point Of Interest PPTP Point to Point Tunnelling Protocol Rec. ITU-T H.550 (12/2017) 3 PSAP Public Service Answering Point QoS

40、 Quality of Service RSU Roadside Unit SAM Situational Awareness Management SIM Subscriber Identification Module SSL Secure Sockets Layer TCP Transmission Control Protocol TLS Transport Layer Security Protocol TSP Telematics Service Provider UDP User Datagram Protocol UI User Interface V2I Vehicle-to

41、-Infrastructure V2V Vehicle-to-Vehicle VG Vehicle Gateway VGP Vehicle Gateway Platform VPN Virtual Private Network WLAN Wireless Local Area Network WPAN Wireless Personal Area Network WWAN Wireless Wide Area Network 5 Conventions In this Recommendation: The keywords “shall“ indicate a requirement wh

42、ich must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. The keywords “should“ indicate an optional requirement which is permissible. This term is not intended to imply that the vendors implementation must provide the option, and the fe

43、ature can be optionally enabled by the vendor. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. 6 Introduction Figure 1 shows VGP positioning in the intelligent transport system (ITS) reference model: there are six major scenarios, i.

44、e., vehicle to vehicle, vehicle to infrastructure, vehicle to cloud-based server, vehicle to nomadic device, vehicle to pedestrian/bicycle and interaction with in-vehicle network scenarios. The vehicle to vehicle (V2V) scenario mainly describes the safety and auto-driving scenarios in which vehicles

45、 communicate with each other. The vehicle to infrastructure (V2I) scenario mainly describes the safety, electronic toll collection (ETC) and traffic information exchange scenarios in which vehicles communicate with roadside infrastructures. The vehicle to cloud-based server scenario mainly describes

46、 the emergency call and telematics scenarios in which vehicles communicate with cloud-based services. 4 Rec. ITU-T H.550 (12/2017) The vehicle to nomadic device scenario mainly describes the telecommunication and remote user interface (UI) scenarios in which vehicles connect to nomadic devices. The

47、vehicle to pedestrian/bicycle scenario mainly describes the safety warning scenarios in which vehicles communicate with the devices carried by pedestrian/bicycles. Interaction with the in-vehicle network scenario mainly describes the vehicle diagnostics, remote data collection and vehicle remote con

48、trol scenarios in which a VGP communicates with the proprietary in-vehicle network. Figure 1 Location of VGP in the ITS reference model 7 Architecture of VGP Figure 2 presents the high-layer architecture of VGPs. The functionalities in the various subsystems of a VGP include: vehicle gateway service

49、s service functionalities management. Rec. ITU-T H.550 (12/2017) 5 Figure 2 High-level architecture of a VGP The VGP services include software and an application data management service, driver-vehicle access service, and other services (see block (1) in Figure 2). Service functionalities include session management and in-vehicle resource access management (see block (2) in Figure 2). Management includes device management; security management and wired and wireless access management (see blo