1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.4456 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2018) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things and s
2、mart cities and communities Frameworks, architectures and protocols Requirements and functional architecture for smart parking lots in smart cities Recommendation ITU-T Y.4456 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTER
3、NET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Securit
4、y Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.150
5、0Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabil
6、ities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.279
7、9 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infras
8、tructure, connectivity and networks Y.4250Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999
9、For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.4456 (03/2018) i Recommendation ITU-T Y.4456 Requirements and functional architecture for smart parking lots in smart cities Summary Smart parking lots can provide various parking services for different parking lot
10、scenarios, including parking guidance, parking space reservation, vehicle reverse search, vehicle automatic access control and self-service payment. Recommendation ITU-T Y.4456 specifies the requirements and functional architecture for smart parking lots. History Edition Recommendation Approval Stud
11、y Group Unique ID* 1.0 ITU-T Y.4456 2018-03-01 20 11.1002/1000/13498 Keywords Architecture, requirement, smart parking lot, use case. * 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, h
12、ttp:/handle.itu.int/11.1002/1000/ 11830-en. ii Rec. ITU-T Y.4456 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardizatio
13、n Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating 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
14、 every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce 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 pu
15、rview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In 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 vo
16、luntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., 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
17、 the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may invol
18、ve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, 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 Recom
19、mendation, ITU had not received notice of intellectual property, protected by patents, which may 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
20、 http:/www.itu.int/ITU-T/ipr/. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4456 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined else
21、where 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Introduction to SPL . 2 7 Requirements for SPLs . 3 7.1 Parking guidance 3 7.2 Parking space reservation . 3 7.3 Vehicle automatic access control . 4 7.4 Self-service payment 4 7.5 Vehicle reverse s
22、earch 4 7.6 Information management 4 8 Functional architecture of SPLs 4 8.1 Functional architecture overview . 4 8.2 Off-street and on-street parking lots (OOPL) . 5 8.3 Smart parking networking platform (SPNP) 5 Appendix I Use cases of SPL 7 I.1 Parking guidance 7 I.2 Parking space reservation . 7
23、 I.3 Vehicle automatic access control . 8 I.4 Self-service payment 8 I.5 Vehicle reverse search 8 Rec. ITU-T Y.4456 (03/2018) 1 Recommendation ITU-T Y4456 Requirements and functional architecture for smart parking lots in smart cities 1 Scope Smart parking lots (SPLs) integrate parking information t
24、o enable the coordination of parking facilities within smart cities. SPLs work with other systems to provide various parking services. This Recommendation specifies the requirements and functional architecture for SPLs. The scope of this Recommendation includes: introduction of SPLs requirements for
25、 SPL Functional architecture of SPL NOTE For use cases of SPL see 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 publication, the editions indicat
26、ed 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 the currently valid ITU-T Reco
27、mmendations 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 Y.101 Recommendation ITU-T Y.101 (2000), Global Information Infrastructure terminology: Terms and definitions. ITU-T Y.2012 IT
28、U-T Recommendation Y.2012 (2010), Functional requirements and architecture of next generation networks. ITU-T Y.2261 ITU-T Recommendation Y.2261 (2006), PSTN/ISDN evolution to NGN. ITU-T Y.4000 ITU-T Recommendation Y.4000/Y.2060 (2012), Overview of the Internet of things. 3 Definitions 3.1 Terms def
29、ined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application ITU-T Y.2261: A structured set of capabilities, which provide value-added functionality supported by one or more services, which may be supported by an API interface. 3.1.2 functional entity ITU-T Y.2012
30、: An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. 3.1.3 service ITU-T Y.101: A structure set of capabilities intended to support applications.
31、 2 Rec. ITU-T Y.4456 (03/2018) 3.2 Terms defined in this Recommendation This Recommendation defines the following term: 3.2.1 smart parking lot: An application that integrates citywide parking information and provides various parking services to produce an enhanced parking experience. 4 Abbreviation
32、s and acronyms This Recommendation uses the following abbreviations and acronyms: APP Application AAFE Access and Authentication Functional Entity DAFE Data Analytics Functional Entity FE Functional Entity OOPL Off-street and On-street Parking Lots PGFE Parking Guidance Functional Entity POMFE Platf
33、orm Operation and Management Functional Entity SCMFE SPL Ctrl. and Mgmt. Functional Entity SPL Smart Parking Lot SPNP Smart Parking Networking Platform VAACFE Vehicle Automatic Access Control Functional Entity WEB World Wide Web 5 Conventions In this Recommendation: The keywords “is required to“ ind
34、icate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to
35、claim conformance. The keywords “can optionally“ and “may“ indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendors implementation must provide the option and the feature can be optionally enabled b
36、y the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. 6 Introduction to SPL The number of vehicles in cities has increased sharply and finding parking spaces has become increasingly difficult. Fur
37、thermore, the lack of parking guidance and parking space booking services makes it difficult for drivers to find parking spaces. A smart parking lot (SPL) brings the efficient integration of parking resources and coordinated parking facilities together with other systems (e.g., external payment syst
38、ems, WEB/APP-parking systems, urban parking guidance systems, traffic systems, etc.). SPLs can provide various parking services to meet the particular requirements of different scenarios. Typical services may include parking guidance, parking space reservation, vehicle reverse search, vehicle automa
39、tic access control and self-service payment. Rec. ITU-T Y.4456 (03/2018) 3 Parking guidance: An SPL publishes information about unoccupied parking spaces with parking guidance information. Parking space reservation: An SPL can help search for available parking spaces and reserve parking spaces in ad
40、vance. Vehicle automatic access control: An SPL may support vehicle parking without the need for stopping at entries and exits. Self-service payment: An SPL supports payment through self-service terminals, hand-held devices, WEB/APP-based parking systems or fully-automatic charging, etc. Vehicle rev
41、erse search: An SPL could help vehicle users to identify where their vehicles are parked, should they forget where they have left them. The overview of the SPL environment is depicted in Figure 1. Off-street parking lots may have controlled entries and exits and on-street parking lots usually do not
42、 have controlled entries and exits. Both off-street and on-street parking lots (OOPL) may use sensors and actuators to monitor and control the use of parking spaces. Communication networks provide communication capabilities between off-street and on-street parking lots, smart parking network platfor
43、ms (SPNPs) and external systems. An SPL platform provides capabilities (operation and management, access and authentication, data analytics, etc.) for the integration of parking information via interfaces. External systems are relatively independent of the SPL. They include WEB/APP-based parking sys
44、tems, urban parking guidance systems, external payment systems and traffic systems. The SPL supports external interfaces for external systems to provide various parking services. Figure 1 Overview of the SPL environment 7 Requirements for SPLs 7.1 Parking guidance OOPL are required to collect parkin
45、g space information and report it to the SPNP. The SPNP is required to provide interfaces to external systems to support parking guidance. OOPL are recommended to use parking space lights, electronic guide screens to indicate parking space information to drivers. 7.2 Parking space reservation The SP
46、NP is recommended to receive requests for parking space reservations from external systems. 4 Rec. ITU-T Y.4456 (03/2018) OOPL may reserve parking spaces according to requests from the SPNP. The SPNP is recommended to provide interfaces to external systems to support parking space reservations. 7.3
47、Vehicle automatic access control OOPL may control vehicle automatic access. The SPNP is recommended to update vehicle information from OOPL. 7.4 Self-service payment OOPL are required to support a method of self-service payment. NOTE Self-service payment can be supported through self-service termina
48、ls, hand-held terminals, WEB/APP-based parking systems and fully-automatic collection. OOPL are required to collect payment information and may report the information to the SPNP. The SPNP may support interfaces to external systems for self-service payment. NOTE Payment information is required to en
49、able self-service payment. The payment information may include vehicle identification (licence plate number, e-tag, RFID, etc.), payment amount, payment time and payment status (paid, unpaid) and rate. 7.5 Vehicle reverse search An SPNP may check vehicle identification and request the parking space location of the vehicle with the corresponding parking lot. OOPL may provide a response of the parking space location to the SPNP. The SPNP may provide the interface to external systems f
