KR102040061B1 - Management system of resident priority parking area - Google Patents

Abstract

The present invention relates to a management system for a resident priority parking lot, which allows users to use and share a resident priority parking area managed by a local government. To this end, the present system comprises: a resident priority parking server storing information with respect to a parking lot provider having an authority to use a resident priority parking area after having submitted a request to use the same to a local government; a resident priority parking sharing server which can check the information with respect to the parking lot provider from the resident priority parking server, and is provided to share the resident priority parking area whose authority to use the same is possessed by the parking lot provider such that another person may use the same, and to manage the use of the other person with respect to the parking area shared by the parking lot provider; a parking lot provider application which is installed at a mobile device, and is configured such that the parking lot provider may register and request to share the resident priority parking area whose authority to use the same is possessed by the parking lot provider; and a user application which is installed at a mobile device, and is configured such that the other person may request to use the resident priority parking area which is shared by the parking lot provider.

Description

MANAGEMENT SYSTEM OF RESIDENT PRIORITY PARKING AREA}

The present invention relates to a resident-first parking lot management system, and more specifically, to enable the resident-first parking area, which is managed and operated by local governments, to be shared and used by a plurality of people. It relates to a resident-first parking lot management system that can solve the parking shortage.

In order to solve the parking shortage in the city, local governments have set up parking zones on the back roads of residential areas, and have implemented a resident-first parking system that allows them to park at a low fee from nearby residents.

The resident-first parking lot is operated by each local government, and the parking lot is provided to local residents every two years.

However, only those vehicles that have previously applied for and obtained permission to use such occupant-first parking zones can park other vehicles. Therefore, even if the parking area is empty, other vehicles cannot park, and as a result, the parking area is not effectively utilized.

In addition, the parking area where the current occupant-first parking lot is shared is divided into available types for day, night and all day for each parking area through the system operated by each local government. The sharing information of the residents' priority parking lot among residents used is not communicated smoothly, and the sharing residents and the using residents do not match.

In addition, even if the resident-first parking zone is shared with the resident-first parking lot, there is a problem of cracking down on illegal parking because it is not possible to know whether the currently parked vehicle is a legal or illegal vehicle. .

Korean Patent Registration No. 10-1045690

The present invention is to solve the above problems, by providing a shared service plan for the resident-first parking area to more efficiently use the resident-first parking area to solve the parking shortage, but to share the parking area It aims to provide a resident-first parking management system that enables providers to generate income from parking fees so that sharing of parking areas can be made more active.

In another aspect, the present invention provides a resident-first parking management system that can determine whether the resident-first parking zone is shared in real time on the basis of the above-described problems, and also makes it easy to visually check the information of the unique resident parking zone to other users. It aims to do it.

In addition, an object of the present invention is to provide a resident-first parking management system that can easily provide whether the parking or illegal parking of the vehicle parked in the resident-first parking zone based on the above-mentioned problems.

In order to solve the above-mentioned problems, according to an aspect of the present invention, there is provided a resident-first parking lot management system that can share and use the resident-first parking area managed by the local government, the system of the present invention Resident priority parking server, which has completed the application for use by the local government and stores information on the parking lot provider who has the authority to use the resident-first parking area; Information about the parking lot provider can be checked from the resident priority parking server, and the sharing of the resident-first parking area so that others can use the resident-first parking area to which the parking provider has permission to use Resident-first parking sharing server for managing the use of others in the parking area shared by the parking provider; An application for a parking lot provider installed in a mobile device and configured to apply for registration and sharing of the resident-first parking area for which the parking lot provider has a use authority; And a user application installed on the mobile device and configured to apply for the use of the resident-first parking area shared by the parking lot provider.

In the above-described aspect, the resident-first parking sharing server further includes a database for storing the unique number of the resident-first parking zone and the vehicle number of the parking-park provider as shared information for the resident-first parking zone registered by the parking lot provider.

In addition, in the above-described aspect, the resident-first parking sharing server further adds a QR code linked to the sharing information including the unique number information of the resident-first parking area and the vehicle number information of the parking lot provider for the resident-first parking area registered by the parking lot provider. Configured to generate.

In addition, in the above-described aspect, the database further stores QR code information that is linked to the shared information including the unique number information of the resident-first parking area for the resident-first parking area registered by the parking lot provider and the vehicle number information of the parking lot provider. The resident-first parking server is connected to the database.

In addition, in the above-described aspect, if another person has applied for the use of the resident-first parking area shared by the parking lot provider, the resident-first parking sharing server adds the information requested by the other person to the shared information stored in the database. The updated sharing information is configured to further include sharing time information requested by another person and vehicle number information of another person.

In the above-described aspect, the occupant-first parking sharing server is configured to generate map mashup information for the occupant-first parking area shared by the parking lot provider.

In addition, in the above-described aspect, the resident-first parking lot management system includes an application for an inspector, which functions to determine fraudulent parking for the resident-first parking lot, and the application for the chopper functions to read the QR code to determine whether the parking is illegal.

According to the resident-first parking management system according to the present invention, by using the application installed on the mobile device, the user can simply register the sharing information for the resident-first parking area in real time on the server, and the user of the resident-first parking area also uses the application. Through this, you can check the information on the resident-first parking area and apply for parking.

In addition, according to the present invention, when a user applies for sharing of a resident-first parking area using an application installed on a mobile device, the resident-first parking area may be conveniently used as the mashup is displayed in real time and displayed on a map.

In addition, according to the present invention, a QR code is issued to the resident-first parking area managed by the city or ward office, and the enforcement officer can easily determine whether the vehicle is currently parked in the resident-first parking area by reading the QR code.

In addition, if the provider shares the resident-first parking area, the income from the parking fee can be raised during the parking area sharing process, thereby inducing more active sharing of the parking area.

In addition, since the provider or the user can simply and clearly report to the local government through unauthorized use of the application, there is an advantage that the unauthorized parking can be neglected and the sharing of the resident-first parking area can be carried out more efficiently.

1 is a block diagram schematically showing the configuration of a resident-first parking lot management system according to the present invention;
2 is an explanatory diagram showing functions of an application according to the present invention;
3 is a diagram illustrating parking lot sharing settings in an application according to the present invention;
4A and 4B schematically illustrate map information screens of a resident-first parking lot displayed in an application through a mash-up service of a shared-resident-first parking lot according to an embodiment of the present invention;
FIG. 5 is a diagram for exemplarily illustrating a fraudulent parking report function provided to an application of a provider or a user; FIG.
6 is a flowchart illustrating a flow of a sharing operation performed in a sharing server in a resident-first parking lot management system according to the present invention;
7 is a flowchart illustrating a method of providing shared resident-first parking lot information to a user in real time according to an embodiment of the present invention.

Advantages and features of the present invention, and methods for achieving them will be apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below but may be implemented in various different forms.

In this specification, the embodiments are provided so that the disclosure of the present invention may be completed and the scope of the present invention may be completely provided to those skilled in the art. And the present invention is only defined by the scope of the claims. Thus, in some embodiments, well known components, well known operations and well known techniques are not described in detail in order to avoid obscuring the present invention.

Like reference numerals refer to like elements throughout. In addition, the terms used (discussed) herein are for the purpose of describing particular embodiments only and are not intended to be limiting of the invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase. In addition, components and operations referred to as 'includes (or includes)' do not exclude the presence or addition of one or more other components and operations.

Unless otherwise defined, all terms (including technical and scientific terms) used in the present specification may be used in a sense that can be commonly understood by those skilled in the art. In addition, the terms defined in the commonly used dictionary are not ideally or excessively interpreted unless they are defined.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

1 is a block diagram showing the configuration of the resident-first parking lot management system according to the present invention. As shown in FIG. 1, the parking lot management system 100 according to the present invention includes a resident-first parking server 10, a resident-first parking lot sharing server 2, and a parking application (App) 30.

The resident-first parking server 10 according to the present invention is a resident-first parking area that is the subject of a resident-first parking system. The municipality receives an application for use of the resident-first parking area and grants the use permit according to certain criteria. A person who is licensed for a resident-first parking area will be the parking lot provider who will provide the parking area for which he / she is authorized as a shared parking area. Anyone who wants to use a resident-first parking area shared by a parking lot provider for use by another person becomes a parking lot user.

The resident-first parking server 10 includes software or hardware for the local government to manage the status of users who are permitted to use the resident-first parking area, and data such as address, contact information and vehicle information of the licensed users. It may further include a parking management database (not shown) is stored. The parking lot management system according to the present invention may provide a resident-first parking management service by interworking with the parking management database of the resident-first parking server 10 operated by the local government.

The resident-first parking sharing server 20 may share the resident-first parking area sharing process and others for the parking area shared by the parking provider so that the parking lot provider may use the resident-first parking area for which the parking lot provider has permission to use. Means software or hardware for managing the use process.

The parking lot provider and the parking lot user may download and install the parking management application 3 on the mobile device, and perform access to the resident-first parking sharing server 20 through the parking application 3.

Resident priority parking sharing server 20 is a resident-first parking management module 210, map call module 220, content calling module 230, mashup information generation module 240, QR code generation module 250 and shared database 260 is further included.

The resident-first parking lot management module 210 receives the information about the resident-first parking area owned by the provider 110 through the application 30 and receives it and stores it in the database 260 and also the resident-first parking lot management module. (210) updates the shared information of the resident priority parking lot shared by the provider and stores it in the database.

The map call module 220 of the resident priority parking sharing server 20 functions to call a map corresponding to the GPS location information from the user or a map corresponding to the request place when the user's place search request is made. The map to be called may be called from a server (eg, Google map, Naver map, next map) stored in the database 260 or providing an open API type map service.

When the shared server 20 receives the GPS location information or the search request of the user, the content calling module 230 calls the resident-first parking lot information having the address included in the called map from the database. At this time, the resident-first parking lot information to be called includes location information and parking fee information for the resident-first parking lot stored in the database at the time of the call.

The mashup information generation module 240 generates a parking mashup information for providing the user by mixing or overlapping the map called by the map calling module 220 and the parking information called by the content calling module 230 and sharing the server. 200 transmits the generated parking lot mashup information to the driver's application.

Although the above-described embodiment has described the generation of parking mashup information by mapping the map and the content information of the requested place and delivering it to the driver's application, the present invention is not limited thereto, and the place requested by the user on the server side is described. It may be implemented to deliver to each driver application along with respective GPS coordinates of occupant-first parking lot information for and display the parking lot information on a map in the driver application.

For example, when the user requests the parking lot information for a specific place, it is preferable to generate the resident-first parking lot mashup information as described above on the server side and deliver the same to the driver's application. However, when the user requests the parking lot information at the current location of the user, Based on the GPS information of the user, it is preferable that the neighbor-first parking lot information is searched from the database, and the retrieved parking lot information is transmitted along with the GPS coordinates to the driver application to be displayed on the map in the driver application.

The QR code generation unit 250 generates a QR code for the resident-first parking area shared by the provider and stores it in the database 260. The issued QR code has a reduced URL (Bintum URL) including information about the corresponding resident-first parking area (serial number) and registered vehicle number to prevent excessive information exposure. Save the original URL that is linked in the database.

The QR code stored in the database 260 is shared with the resident priority parking server 10 managed by the city or county through the API, and is printed by the city or county and attached to each resident priority parking area.

* Application for Provider

2 is a diagram illustrating main functions of an application (provider application and user application). As shown in FIG. 2, the provider application includes a provider registration module, a parking lot sharing module, a usage status inquiry module, and a fraudulent parking report module.

In the provider application, the provider registration module is a module that functions for membership registration. The provider registers vehicle information and unique resident-first parking lot information to the server 20 through the provider registration module.

Specifically, the resident-first parking lot sharing provider must first perform a membership through the application (30). On first use of the application, the provider fills in the driver's ID, driver's name, vehicle number 1 (or more than one), and the resident-first parking lot serial number to be registered via the screen interface.

Information input through the application of the provider is transmitted to the shared server 20, the shared server 20 generates an ID for the corresponding user and stores the input information in the database 300.

Since the provider may use the resident-first parking lot using a plurality of vehicles, a plurality of vehicle numbers may be input. The occupant-first parking lot management module 210 of the shared server 20 manages the input vehicle number and the provider by matching the serial number of the corresponding occupant-first parking lot.

When the provider completes the service subscription through the application, the resident-first parking lot management module 210 of the server 20 delivers it to the QR code generation module 250 and generates a unique QR code for the resident-first parking lot area. The generated QR code is stored in the database in association with the unique number of the resident-first parking lot.

In addition, in addition to the vehicle number and the serial number of the resident-first parking lot during the membership registration process as described above, account information for receiving a deposit of the shared parking fee generated during the sharing process of the parking lot may be input if necessary, but is proportional to the shared time. For example, it may be operated in such a way that the rent is deducted at the time of renting the next occupant-first parking lot as much as the paid points.

In addition, if it is necessary to prove the right to use the resident-first parking zone during the membership registration process described above, documents (receipts) etc. to prove that the user is a legitimate user of the resident-first parking zone are uploaded to the server using the upload function provided to the application. You can also upload.

The parking lot unique module allows the provider to set a time zone for sharing. FIG. 3 is a screen illustrating an example of sharing a resident-first parking area using an application of a resident-first parking lot. As shown in FIG. 3, the provider may select a sharing period, sharing time, price, etc. through a screen provided by the application.

For example, providers can only share a specific time zone on a specific date, and can be specified by day, week, day, or month. In addition, the sharing screen may be configured to enable sharing by providing an option of one time and repetition by displaying 24 hours from 0 o'clock per day.

The usage status inquiry module allows the provider to inquire the usage status of the resident-first parking area shared by the provider. The usage status inquiry module displays the usage history of the shared parking area for each provider to the provider, and the provider can check the usage history of the parking lot.

In the case of a fraudulent parking report module, a provider is provided to report a fraudulent vehicle directly in his preferred parking area. The fraudulent parking report module may be implemented in a form of directly transmitting the unauthorized parking position and unauthorized parking time information to the local government using an application together with a picture of the unauthorized parking state as shown in FIG. 5. .

* Application for users

The user application includes a user registration module, a shared parking search module, a shared parking reservation module, and a fraudulent parking report module.

The user registration module functions to receive necessary information related to membership registration. The user inputs information such as a driver ID, a driver's name, a vehicle number (multiple), and a telephone number through a provided screen interface. In the case of a user member, the user's ID and vehicle number are stored in a database.

Next, the user application includes a shared parking lot search module. 4A and 4B schematically illustrate a screen interface of a driver application provided by a shared parking lot search module as described above. First, FIG. 4A illustrates an example of a screen of a surrounding search interface provided to a user. If the shared parking lot search module uses the surrounding search interface on the application, the shared parking lot search module displays the parking information on the map based on the current driver's position based on the current GPS position of the user. This screen may be, for example, an initial screen or a default main screen provided after a user subscribes to an application. In this state, the server 200 retrieves GPS information from the user's application and displays a resident-first parking area that can be parked in real time on a map including the user's current location. In FIG. 4A, the resident-first parking lot that is shared and available is displayed in blue in the case of the unavailable parking lot.

When the user clicks on the available parking or non-parking indication icon provided on the map, the information window provided in any part of the screen further displays the location of the resident-first parking lot, the hourly parking fee of the resident-first parking lot, and the link to the shared parking reservation window. do. In addition, the information window may further include link information such as a navigation guide link to a corresponding parking lot or a link for linking to a navigation application installed in a smartphone.

4B is a diagram illustrating a user searching for parking lot information around a place to go using a search menu provided on an application. As shown in FIG. 4B, when a user searches for a place in a search window provided after clicking a search menu, the server 200 provides real-time information on neighboring residents' parking lots on the map in real time.

In addition, as described in FIG. 4A, when the user clicks on the parkable or non-parking indication icon provided on the map, the location of the parking lot, the hourly parking fee of the parking lot, the parking reservation link, etc. are displayed through the information window provided on any part of the screen. Is displayed. In addition, the information window may further include link information such as a navigation guide link to a corresponding parking lot or a link for linking to a navigation application installed in a smartphone.

The shared parking reservation module functions to allow users to make reservations for shared resident-first parking areas. The user can reserve the desired occupant-first parking area through the reservation function provided through the screen interface.

The user may share only a specific time zone of a specific date with respect to the shared parking lot, and is configured to make a reservation within a range specified by the provider on a daily, weekly, weekly or monthly basis.

For example, if the provider has set a shared parking lot for the resident-first car park repeatedly from 6 pm to 8 am, Monday through Friday, the user will be able to use the unit on a daily basis until 6 pm to 8 am It is possible to apply for reservations on a weekly or monthly basis. In addition, the user may apply for a reservation on a daily, weekly or monthly basis only every Monday from 6 to 10 o'clock. In addition, the user may apply for a reservation only at a specific time on a specific date.

In the case of a fraudulent parking report module, if a fraudulent car is parked in the preferred parking area reserved by the user, the user is provided to report it. The fraudulent parking report module is basically the same as the fraudulent parking report module previously provided in the provider application. That is, as shown in FIG. 5, with the photograph of the unauthorized parking state, the unauthorized parking position and the unauthorized parking time information may be directly transmitted to the local government using an application.

In addition, the user application may include a shared parking period expiration notification function. That is, before the expiration of the use period for the reserved occupant-first parking area, the parking lot user can be notified that the expiration of the period is imminent so that a notification can be provided for moving the vehicle or applying for an extension of the use period.

For example, 10 minutes before the expiration of the usage period, an application is provided to the user so that the parking lot user can know that the parking lot reservation has expired in advance. The notification time is configured to be freely selected by the user through a menu such as application setting.

In addition, users who are notified that their expiration date is imminent may request an extension through the application. If the parking lot user requests the extension by inputting the desired period of extension, the extension request is delivered to the sharing server 20, and the sharing server 2 checks whether the extension period is within the sharing period requested by the parking lot provider. Check whether or not. If the extension period is within the sharing period, an additional parking fee will be requested. If the parking lot user pays the additional parking fee, the extension will be approved. If the extension period exceeds the sharing period, the extension request will be denied. In this case, the user may be guided again to another available parking area.

In the above description, the application for the provider and the application for the user are described as separate, but for the purpose of understanding the present invention, the actual application is provided as a single integrated application, and the provider and the user may use each user mode. The necessary functions can be used through.

* Application for chopper

A chopper application is provided to crack down on fraudulent parking. The application for the enforcement officer may control whether illegal parking is performed through the resident priority parking server 10 when the database 260 of the present invention is configured to interoperate with a resident priority parking server 10 operated by a city or a ward through an API. In addition, the resident priority parking sharing server 20 according to the present invention may be directly connected to the operation. The application for the enforcement officer uses a QR code reader provided to the application to read a QR code provided for each resident-first parking area to control illegal parking.

The database 260 stores the identification information and the vehicle information of the resident-first parking lot corresponding to the QR code registered by the provider of the resident-first parking area, and the user who reserved the parking lot when the provider applied for the parking lot sharing through the application. Since the usage time and the vehicle number are updated and stored, the chopper can check whether the parking lot is parked in the resident-first parking area by reading the QR code.

6 is a flowchart illustrating a sharing operation of the residential priority parking lot in the resident priority parking sharing server 20 of the residential priority parking management system according to the present invention. As shown in FIG. 6, in step S100, the resident-first parking sharing server 20 first receives a unique number and a vehicle number of a parking lot of a provider through an application and stores it in a database 260, followed by resident-first in step S110. Generate a QR code for the parking area. In this case, the generated QR code link may include a unique number of a resident-first parking area and a vehicle number of a provider.

In the subsequent step S120, the resident-first parking sharing server 20 checks whether there is a parking lot sharing request from the application of the provider. If the provider applies for parking lot sharing through the application in step S120, the process proceeds to step S130, and if there is no parking lot sharing application, the process proceeds to step S170 and ends.

Meanwhile, in step S130, the shared information requested by the provider is generated and stored in the database. The shared information requested by the provider includes the location information of the resident-first parking area and the time information that can be shared, and the user who wants to use the resident-first parking area can use the application to obtain the location information and the sharing time of the resident-first parking area through the application. You will be able to confirm and proceed with your reservation.

In step S140, the shared server 20 checks whether there is a reservation request. If the reservation is requested in step S140, the step proceeds to step S150, and the sharing server 20 stores the reservation information in the database and updates the link information of the QR code. The updated information further includes a reservation time of the reserved user and vehicle information of the user. Therefore, whenever the usage information or reservation information for the resident-first parking area shared by the provider is updated, the link information of the QR code is updated, so that the cracker can easily perform the illegal parking control by reading the QR code.

Thereafter, in step S160, the sharing server 20 determines whether additional reservation is possible based on the sharing information input by the provider and the reservation information reserved by the user. If it is determined in step S160 that the additional reservation is possible, the step proceeds to step S140 and repeats until step S160. If it is determined in step S160 that the additional reservation is impossible, the step proceeds to step S170 and ends.

7 is a flowchart including two operations of generating map information (mashup information) for the shared resident-first parking lot described above. As shown in FIG. 7, first, in step S200, a user starts a process by requesting mashup information for a resident-first parking lot shared with the shared server 20 through the application.

In step S210, the sharing server 20 receives the mashup information request, and then in step S220, the sharing server 20 determines whether the user's request is a request for a specific place. That is, when the user performs a search for a specific place using a search box provided on the application as described with reference to FIG. 4B, in step S230, the server is connected to a server (Google, Naver, Next) that provides an open API map service. Invoke the map for a specific place.

After calling the map for a specific place (search place) in S230, the server searches for the shared resident-first parking lot included in the map from the information of the shared resident-first parking lot stored in the database 300 in step S240, and the corresponding parking lot. Call the content information (parking lot location, parking lot price, reservation link, etc.)

In a subsequent step S250, the server matches (mapping) the location of the shared occupant priority parking lot corresponding to the called map to generate a shared parking lot information map, and the shared server uses the shared parking lot information map generated in step S260 to Send to the application. Meanwhile, the sharing server may store a parking information map in which the map and the shared resident-first parking lot information are matched on the server, and transmit the link address where the parking information map is stored to the user's application.

In operation S270, the user application receives the shared parking lot information map from the sharing server, and the received shared parking lot information map is displayed on the screen through the user application. The generated shared parking lot information map is displayed with the fare information or the resident-first parking lot number along with a marker indicating the parking position as shown in FIG. 4B, and the user wants to view more detailed information about the specific resident-first parking lot or make a reservation. When the marker of the corresponding parking lot displayed on the map is clicked, information such as shared parking fee, shared time information, parking lot address, and reservation link may be displayed on the display through the information window of the screen.

If the user requests shared occupant-first parking lot information for the current location of the user instead of the specific place in step S220, the step proceeds to S235. In step S235, the user application transmits its local GPS location information to the server, and the server receives the GPS location information of the user.

In step S245, the server searches for the shared resident-first parking lot with the GPS information based on the current user's location from the information of the shared resident-first parking lots stored in the database 300, and the contents information (sharing parking cost, sharing) for the corresponding parking lots. Time, parking address, reservation link, etc.). Here, the shared occupant-first parking lot search information searched based on the user location may be parking lot information within the same administrative area (for example, town, town, or east) or parking lot information within a certain radius of the user's location. have.

In step S255, the server transmits the information of the searchable shareable resident-first parking lots together with the GPS information of each of the parking lots to the user application.

In operation S265, the user application receives the parking lot information associated with the location information of the shared occupant-first parking lot transmitted from the server, and generates a parking lot information map to the driver based on the received location information of the parking lot. In this case, the call of the open API map and the mapping of the parking lot information received from the server are performed in the driver's application.

The generated parking lot information map is displayed with a fare information or a resident-first parking lot number along with a marker indicating a parking location as shown in FIG. 4A, and when the user wants more detailed information about a specific resident-first parking lot, the marker of the corresponding parking lot displayed on the map. If you click, information such as shared parking fee, sharing time, parking lot address, etc. may be displayed on the display through the information window of the screen.

In addition, information based on the user's current GPS location is automatically performed at predetermined time intervals, so that the driver's parking convenience can be improved because the server continuously displays updated information in real time while driving the vehicle. have.

According to the present invention, even if the user is located in a remote location, the location information of the shared occupant-first parking lot of the corresponding area, the sharing cost information of the parking lot, the parking availability of the shared parking lot can be searched, and it is easier to park the vehicle It will be able to provide real-time parking information to help.

In the resident-first parking lot management system according to the present invention, a resident-owned provider or a user who owns a mobile device can easily share his resident-first parking area by running an application and also can check the resident-first parking area that can be parked. First of all, the utilization efficiency of the parking area can be greatly improved.

10: Resident First Parking Server
20: resident-first parking sharing server
30: Application
210: resident-first parking management module
220: map call module
230: content calling module
240: mashup information generation module
250: QR code generation module
260: database

Claims (7)

As a resident-first parking lot management system that allows residents to share and use resident-first parking areas,
Resident priority parking server that has completed the application for use by the local government and stores information on the parking lot provider who has the authority to use the resident-first parking area;
Information about the parking lot provider can be checked from the resident priority parking server, and the sharing of the resident-first parking area so that others can use the resident-first parking area to which the parking provider has permission to use Resident-first parking sharing server for managing the use of others in the parking area shared by the parking provider;
An application for a parking lot provider installed in a mobile device and configured to apply for registration and sharing of the resident-first parking area for which the parking lot provider has a use authority; And
Installed on the mobile device, the other includes a user application configured to apply for the use of the resident-first parking area shared by the parking lot provider,
The resident-first parking sharing server includes a database for storing the unique number of the resident-first parking zone for the resident-first parking zone registered by the parking lot provider and the vehicle number of the parking lot provider as sharing information.
The database further stores QR code information linked to the shared information including the unique number information of the resident-first parking area for the resident-first parking area registered by the parking lot provider and the vehicle number information of the parking lot provider, and the resident-first parking server. Is connected to the database,
When the other person applies for the use of the resident-first parking area shared by the parking lot provider, the resident-first parking sharing server adds the information requested by the other person to the shared information stored in the database and links information of the QR code. And renewed, the updated information further includes the reservation time and vehicle information of the other person applying for use,
The resident-first parking lot management system includes an application for an intermittent that functions to determine fraudulent parking for the resident-first parking lot, and the chopper for application reads the QR code to determine whether or not illegal parking.
Resident-first parking management system.
delete The method of claim 1,
The resident-first parking sharing server is configured to further generate a QR code linked to the sharing information including the unique number information of the resident-first parking zone for the resident-first parking zone registered by the parking lot provider and the vehicle number information of the parking lot provider. Resident-first parking management system characterized in that.
delete delete The method of claim 3,
The resident priority parking sharing server is a resident-first parking management system, characterized in that configured to generate map mashup information for the resident-first parking area shared by the parking lot provider.
delete

Images