Dynamic Car Parking Negotiation And Guidance Using An Agent-Based Platform
Published on Dec 05, 2016
Modern prosperous cities strongly need advanced parking assistant systems, intelligent transportation systems providing drivers with parking information. Existing parking information systems usually ignore the parking price factor and do not automatically provide optimal car parks matching drivers' demand. Currently, the parking price has no negotiable space; consumers lose their bargaining position to obtain better and cheaper parking.
This study uses an intelligent aent system, and
considering negotiable parking prices, selects the optimal car park for the driver. The autonomous coordination activities challenge traditional.
This System is divided into three Different models:
1. User interface Command
2. Information Station
3. CAR Parking Agent
A. User interface Command
User command through to search the agent by SMS
1. Nearest car park Location( Current Location Name + DCAR)
2. Cost per hour
3. Available of slot to park in which Floor
B. Information Station
1. Info station for Service Agent control
2. Interface GSM Unit Control
3. Info station for Profile Agent control
a. Info station for Service Agent control
This is divided into two Services,
a. Service control and Execution for data Agent
b. Service Catalogue for Search Engine
b. Interface GSM Unit Control
This is divided into two interfaces
a. GSM Protocol Development in Software and Hardware
b. Serial interface to PC
c. Info station for Profile Agent control
This is divided into two Services,
a. Master profile storage Agent to Database
b. Master profile Retrieve Agent from Database
Intelligent Parking Locator Service:
A multi-agent approach is adopted as most suitable approach to structuring our system. In order to facilitate flexible and adaptable service provision, intelligent agents, residing within each of the three tiers of the system architecture must interact so as to satisfy, in the „best‟ possible way, any user requests they might encounter. The following description outlines the entity interactions that take place during the Intelligent Parking Locator service provision. In the delivery of this service, the content must be adapted and customized according to the capabilities of the user device and the user prefereces.
For example if the user has access to a resource any mobile device. If however the user only has access to a device with unlimited capabilities (e.g. a mobile phone), then the details of the available parking spaces would be specified in a simple format which„best‟ suits the device (e.g. SMS). This trimming (adaptation) of the services is one way to address the shortcomings of some mobile devices, while still delivering the service.
The “Composite Capabilities / Preference Profile” (CC/PP) is used as the uniform format for the implementation of the user profiles. The master profile repository in the InfoStation Center contains descriptions of all registered user devices, i.e. their capabilities and technical characteristics. During the initial AAA request, the user‟s Personal Assistant sends as parameters the make and the model of the user device.
An agent working on the InfoStation (or the InfoStation Center) reads the corresponding device‟s description from the repository and according to this, selects and forwards the best format of the service content. However a problem arises when a user uses a non-registered device as s/he might receive the service content in unsuitable format.
Thus the user needs first to register any new mobile device s/he wants to use within the system. In this case, during the initial AAA request the Personal Assistant sends a full description of the user device‟s capabilities towards the InfoStation Center. As the user enters the campus area in a vehicle, s/he enters the coverage area of an InfoStation, positioned at the entrance to the campus.
The Personal Assistant, installed in the user mobile device, and the InfoStation mutually discover each other. The Personal Assistant sends a request to the InfoStation for user‟s Authorization, Authentication and Accounting (AAA). During this initial AAA request, the user‟s Personal Assistant sends also the make and the model parameters of the user device, and any updates of user profile and user service profile.