Parking fee setting system

Abstract

To provide a parking fee setting system capable of simply and reliably performing an appropriate fee setting of a parking lot.SOLUTION: A parking fee setting system 100 includes: a data extraction unit DE that extracts parking fee data TD from a fee display image FI on the basis of a creation format of a parking fee signboard SG; and a parking fee setting unit FS that performs a fee setting of a parking lot based on the parking fee data TD extracted by the data extraction unit DE. Accordingly, when the fee setting of the parking lot is performed in the parking fee setting unit FS, the parking fee data TD extracted on the basis of the creation format of the parking fee signboard is used to maintain a state matching with contents shown in the fee display image FI.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a parking fee setting system that sets parking fees by utilizing information related to parking fee signs installed in parking lots. [Background technology]

[0002] Generally, there is known a technology for extracting various character strings such as addresses from an image obtained by a scanner or the like (see, for example, Patent Document 1, etc.). On the other hand, there is known a fee display system for displaying parking fees that changes the fee per unit time (see Patent Document 2).

[0003] However, in recent years, as fee systems have become more complex, problems have arisen such as the time it takes to set up a fare adjustment machine, and incorrect settings resulting in the fare differing from that shown on a sign, resulting in trouble. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-60474 A [Patent Document 2] Utility Model Registration No. 3151090 Summary of the Invention

[0005] The present invention has been made in consideration of the above-mentioned points, and has an object to provide a parking fee setting system that can easily and reliably set appropriate fees for a parking lot.

[0006] To achieve the above objective, the parking fee setting system includes a data extraction unit that extracts parking fee data from a fee display image based on a creation format of a parking fee sign, and a parking fee setting unit that sets parking fees based on the parking fee data extracted by the data extraction unit.

[0007] In the above parking fee setting system, the parking fee can be set in the parking fee setting unit based on the parking fee data extracted from the fee display image by the data extraction unit, and in particular, accurate reading is achieved by extracting the parking fee data based on the creation format of the parking fee sign, so that even if the fee system is complex, parking fees can be easily and reliably set in a manner that is consistent with the content shown in the fee display image.

[0008] In a specific aspect of the present invention, the data extraction unit determines the type of each data constituting the extracted parking fee data according to the display position in the fee display image. Here, the format for creating parking fee signs is determined to some extent in the parking lot rental industry in terms of the display position and size of each item on the sign. Therefore, in this case, by extracting data based on the above-mentioned creation format, it is possible to collect accurate information on the fee system.

[0009] In another aspect of the present invention, the data extraction unit extracts parking lot identification information included in the fee display image, and transmits the extracted parking lot identification information to the parking fee setting unit in association with the parking fee data. In this case, matching with the parking lot for which the parking fee is to be set can be performed based on the parking lot identification information extracted from the fee display image.

[0010] In yet another aspect of the present invention, the fee display image includes a captured image of a signboard installed in a parking lot. In this case, the parking fee can be set based on the captured image of the signboard captured at the site where the parking lot is located.

[0011] In yet another aspect of the present invention, a portable terminal is provided that captures an image using an imaging unit to generate a fee display image, and the portable terminal associates location information at the time of capturing the image using the imaging unit with the fee display image. In this case, the location information at the time of capturing the image can be used as information indicating the location of the parking lot.

[0012] In yet another aspect of the present invention, the portable terminal includes a data extraction unit, and links the location information to the parking fee data and transmits the linked location information to the parking fee setting unit. In this case, by extracting the necessary data in the portable terminal, rapid processing is possible.

[0013] In yet another aspect of the present invention, the data extraction unit is provided in a parking lot management server, the parking fee setting unit is provided in a payment machine installed at the site, and the parking lot management server extracts parking fee data from a fee display image transmitted from outside and transmits it to the corresponding payment machine. In this case, payment processing can be performed in the payment machine installed at the site based on the parking fee data extracted by the parking lot management server.

[0014] In yet another aspect of the present invention, the fee display image includes a copy image for signboard production, and the parking fee setting unit starts setting the parking fee after confirming the installation of the signboard corresponding to the copy image. In this case, the parking fee can be set based on the copy image for signboard production. [Brief description of the drawings]

[0015] [Figure 1] 1 is a conceptual diagram for explaining an overview of a parking fee setting system according to a first embodiment. FIG. [Diagram 2] FIG. 1 is a diagram showing an overview of data extraction for setting parking fees. [Diagram 3] 13A and 13B are image diagrams showing an example of a signboard as an image capturing target that is to become a price display image or a fee display image. [Figure 4] 11 is a data table showing an example of information on character data extracted from a price display image. [Diagram 5] 10 is a data table showing an example of parking fee data created based on information of extracted character data. [Figure 6] 1 is a block diagram for explaining a configuration example of a parking fee setting system. [Figure 7] FIG. 13 is a conceptual diagram for explaining an overview of a modified example of a parking fee setting system. [Figure 8] FIG. 11 is a conceptual diagram for explaining an overview of a parking fee setting system according to a second embodiment. [Figure 9] FIG. 13 is a conceptual diagram for explaining an overview of a modified example of a parking fee setting system. [Figure 10] FIG. 11 is a conceptual diagram for explaining an overview of a parking fee setting system according to a third embodiment. [Figure 11] FIG. 13 is a conceptual diagram for explaining an overview of a parking fee setting system according to a fourth embodiment. [Figure 12] FIG. 13 is a conceptual diagram for explaining an overview of a parking fee setting system according to a fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] [First embodiment] An example of a parking fee setting system according to the first embodiment will be described below with reference to Fig. 1 etc. As shown in Fig. 1 etc., a parking fee setting system 100 according to this embodiment includes a mobile terminal 10 that generates a fee display image, a parking lot management server 50 that manages various information about the parking lot, and an on-site terminal 70 that is installed at the parking lot, such as a payment machine.

[0017] The portable terminal 10 is, for example, a smartphone, includes a camera CA constituting an imaging unit, is capable of communicating with the parking lot management server 50, and transmits various data including image data captured by the camera CA. In this example, the portable terminal 10 is provided with a data extraction unit DE that extracts various data from the captured image data by installing a dedicated application in advance, for example.

[0018] The parking lot management server 50 can be in various forms such as a physical server or a cloud-type server, and handles various information related to the parking lot, such as information from the mobile terminal 10. Here, it is assumed that the server 50 particularly manages information related to parking fees transmitted from the mobile terminal 10.

[0019] As described above, the on-site terminal 70 is composed of, for example, an adjustment machine or the like installed in the parking lot, which is the site, and is responsible for various processes for on-site parking management, such as the settlement of parking fees. In this example, the on-site terminal 70 is capable of communicating with the parking lot management server 50, and sets the parking fee system based on the parking fee data transmitted from the parking lot management server 50. For this reason, the on-site terminal 70 is provided with a parking fee setting unit FS.

[0020] The procedure for setting parking fees in the parking fee setting system 100 having the above configuration will now be outlined.

[0021] In the illustrated example, in the parking fee setting system 100, first, the camera CA captures an image of a parking fee signboard SG installed at the site in the mobile terminal 10 to generate a fee display image FI (see, for example, FIG. 2, FIG. 3, etc.). In this case, the captured image of the parking fee signboard SG installed in the parking lot becomes the fee display image FI. The data extraction unit DE of the mobile terminal 10 extracts character strings from the acquired fee display image FI, and finally generates parking fee data TD (see, for example, FIG. 5, etc.) that is data that enables the setting of parking fees in the parking lot. The parking fee data TD is data that enables the calculation of parking fees corresponding to the fee system written on the parking fee signboard SG, and is configured in, for example, a CSV format so as to be applicable when performing settlement processing. As described above, in the mobile terminal 10, the data extraction unit DE extracts parking fee data TD that is applicable to the settlement processing of parking fees from the fee display image FI captured by the parking fee signboard SG. In other words, the data extraction unit DE converts the fee display image FI into parking fee data TD. The mobile terminal 10 transmits (sends) the generated parking fee data TD to the parking lot management server 50. At this time, a fee display image FI and the like may also be sent.

[0022] Next, when the parking lot management server 50 receives information such as the parking fee data TD from the portable terminal 10, it stores and manages this information, and also transmits it to the on-site terminal 70 corresponding to the parking fee data TD.

[0023] When the on-site terminal 70 receives the parking fee data TD transmitted from the parking lot management server 50, the parking fee setting unit FS sets the parking fee based on the received parking fee data TD. That is, the on-site terminal 70, as a payment machine installed on-site, performs payment processing based on the parking fee data TD.

[0024] In this manner, parking fees are set in the parking fee setting system 100, and settlement processing is carried out in the parking lot based on the fee setting that matches the information written on the parking fee signboard SG installed at the site.

[0025] Hereinafter, an overview of data extraction for setting parking fees will be described with reference to FIG. 2. FIG. 2 conceptually illustrates an example of the configuration of the data extraction unit DE, particularly, of the parking fee setting system 100, in the form of a block diagram. The data extraction unit DE is composed of, for example, an electronic circuit, or a CPU or a storage device, and is capable of information processing based on various programs and data. In the illustrated example, the data extraction unit DE includes, as program parts, a character string extraction program LE, a type determination program TJ, and a parking fee data creation program FC. The data extraction unit DE also includes, as storage units for storing various data, a parking fee signboard creation format storage unit FD and a parking fee data storage unit PD. Here, as shown in the region BL of the balloon indicated by the dashed line, processing is performed in each unit constituting the data extraction unit DE, whereby character strings are extracted from the fee display image FI acquired by imaging the parking fee signboard SG, and finally, parking fee data TD that is digitized as text data or the like is generated.

[0026] Among the program parts constituting the data extraction unit DE, the character string extraction program LE extracts a character image object from the fee display image FI and determines (matches) a character or a number corresponding to the extracted character image object. That is, the character string extraction program LE performs OCR processing to convert character image data into text data. In addition, at this time, the position in the image of the character or character string (hereinafter also referred to as character data) that has been read and converted into data, the relative ratio (size) to the entire image, and, if necessary, information such as font and color are also extracted. The character string extraction program LE may perform conversion processing specialized for characters and numbers used when creating a parking fee signboard. For example, when two or more candidates are presented in the above matching, it is possible to preferentially adopt those that are often used on parking fee signs, or to exclude characters that are unlikely to be used on parking fee signs from the candidates in advance.

[0027] The type determination program TJ in the data extraction unit DE determines the type of the character string (character data) extracted by the character string extraction program LE. For example, the type determination program TJ determines the type of each data constituting the extracted parking fee data according to the display position in the fee display image FI. More specifically, the type determination program TJ determines the type of information contained in the extracted character string, such as whether it indicates the numerical value of the fee, the date and time, or the location of the parking lot, based on the position and size on the sign. At this time, the type determination program TJ determines the above type based on the principles for creating a parking fee sign by referring to the information stored in the parking fee sign creation format storage unit FD. Specifically, it determines what the characteristics of the information contained in the character string to be determined should be, taking into account the points of the creation format, based on whether the character data is composed of numbers or letters, the size and font of the letters, and the contents of other adjacent letters.

[0028] The parking fee data creation program FC creates parking fee data TD from information on each character string whose type has been determined by the type determination program TJ, the relative positional relationship of each character string, etc. More specifically, the parking fee data creation program FC creates, as the parking fee data TD, data corresponding to a parking fee conversion formula according to the fee system shown on the parking fee signboard SG (see FIG. 1).

[0029] Among the storage units constituting the data extraction unit DE, the parking fee signboard creation format storage unit FD stores various data related to the principles for creating parking fee signs, as described above. That is, the parking fee signboard creation format storage unit FD stores various data related to general rules and principles for the placement, size, and relative positional relationship in creating parking fee signs for days of the week, time periods, maximum fees, fees per unit time, and character strings that enable the location of the parking lot to be identified, or guidelines in the parking lot rental industry. The type determination program TJ determines the attribute, i.e., type, of the character string extracted by the character string extraction program LE by comparing its position, size, and character content with the data stored in the parking fee signboard creation format storage unit FD. In addition, when the data extraction unit DE matches characters, it may select (adopt) a corresponding character string from the character strings contained in the parking fee signboard creation format storage unit FD, for example.

[0030] The parking fee data storage unit PD is a data storage area for storing the parking fee data TD created by the parking fee data creation program FC.

[0031] The data extraction unit DE outputs the parking fee data TD generated from the fee display image FI to the parking fee setting unit FS, as each component of the data extraction unit DE functions as described above. In the example shown in Fig. 1, the parking fee data TD is generated in the portable terminal 10 including the data extraction unit DE, and is transmitted to an on-site terminal 70 (payment machine) including the parking fee setting unit FS via the parking lot management server 50. The on-site terminal 70 sets the parking fee based on the parking fee data TD, so that the on-site terminal 70 functions as a payment machine capable of processing the settlement of parking fees.

[0032] 3(A) and 3(B) are image diagrams showing an example of a fee display image FI or a signboard (parking fee signboard SG) as an imaging target to become the fee display image FI. Each example shown in the figure is created in a format corresponding to, for example, guidelines in the parking lot rental industry.

[0033] FIG. 3(A) shows an example of a case where a day-of-week fee is applied and the maximum fee is repeatedly applied. On the other hand, FIG. 3(B) shows an example of a case where a day-of-week fee is applied but the maximum fee is not repeatedly applied. As shown in the figure, for example, the maximum fee amount display is displayed large in the center of the fee display image FI (parking fee signboard SG). It is also displayed in a bold and red color, making it conspicuous. For the days of the week, for example, weekdays (Monday to Friday) and Saturdays, Sundays, and holidays are provided on the left and right, and a color different from the maximum fee is used in the upper left position of the amount display indicating the maximum fee, and the size of the characters is also smaller than that of the amount display indicating the maximum fee. In addition, for example, for the repeated application of the maximum fee, in the example of FIG. 3(A), a word indicating that the maximum fee is applied is displayed near the amount display indicating the maximum fee. On the other hand, in the example of FIG. 3(B), a word indicating that the maximum fee is not applied is displayed near the amount display. The fee display image FI (parking fee signboard SG) also includes parking lot identification information that enables identification of the parking lot where the parking fee signboard SG is to be installed. Specifically, in the fee display image FI shown in FIG. 3(A) and FIG. 3(B), the address and parking lot name are reflected toward the center of the lower side, and the parking lot identification information included in the fee display image FI is read by extracting a character string from this. Although not shown in the figures, the parking lot identification information included in the fee display image FI may also include character data (code number) dedicated for identification in addition to the above. The read parking lot identification information also functions as a signboard ID that identifies the parking fee signboard SG.

[0034] An example of the data to be handled will be described below with reference to Fig. 4 etc. Fig. 4 is a data table showing an example of character data information extracted from the fee display image FI exemplified in Fig. 3(A) etc. by the data extraction unit DE. Fig. 5 is a data table showing an example of parking fee data TD created based on the extracted character data information shown in Fig. 4, for example.

[0035] The extraction result data LD shown as a data table in FIG. 4 is created based on a character string extraction program LE that converts image data into text data (character data) and a type determination program TJ that performs type determination on the converted character data, both of which are included in the data extraction unit DE. In the illustrated example, the extraction result data LD first includes a fee display image FI or a parking fee signboard SG, and further includes parking lot identification information (signboard ID) SS1 that identifies the parking lot where the fee display image FI should be installed. That is, the data extraction unit DE illustrated in FIG. 2 extracts the parking lot identification information SS1 included in the fee display image FI, and transmits the extracted parking lot identification information SS1 to the parking fee setting unit FS in association with the parking fee data TD. In addition, it is assumed that the location data DDp at the time of capturing the parking fee signboard SG, i.e., at the time of generating the fee display image FI, is added to the parking lot identification information SS1 by the GPS function (described later with reference to FIG. 6) of the smartphone as the mobile terminal 10. Furthermore, the main data DD of the extraction result data LD are extracted as the character data DD1 extracted by the character string extraction program LE, the font and color data DD2 as the data associated with the character data, and the in-image position and relative ratio (size) data DD3. Furthermore, the type determination program TJ extracts content type data DD4 as the result of type determination obtained by comparing each of the data DD1 to DD3 with the data stored in the parking fee sign creation format storage unit FD.

[0036] Based on the extraction result data LD in Fig. 4, the parking fee data creation program FC of the data extraction unit DE creates parking fee data TD, for example, shown as a data table (table data) in Fig. 5. In the example in Fig. 5, in addition to the parking lot identification information SS1 and the location data DDp, a list LS of entry times and exit times for each day of the week created based on the main data DD in Fig. 4 and the parking fee sign creation format storage unit FD is shown as an example of the parking fee data TD, but it is not limited to this as long as it is valid as data necessary for setting the parking fee, and various forms are possible, such as data on a conversion formula that uses entry and exit time data as input and calculates the parking fee as output.

[0037] Hereinafter, a configuration example of the parking fee setting system 100 will be described with reference to a block diagram shown in FIG.

[0038] First, as described above, the parking fee setting system 100 comprises a portable terminal 10, a parking lot management server 50, and an on-site terminal 70, of which the portable terminal 10 is composed of a smartphone or the like, and the on-site terminal 70 is composed of a parking lot payment machine.

[0039] The portable terminal 10 includes a control unit 11, a touch panel 12 as an input receiving unit, a display unit 13 configured with a display or the like, an imaging unit 14 configured with a camera CA, a GPS receiving unit 15, and a communication unit 16. The control unit 11 is configured with, for example, an electronic circuit, or a CPU or a storage device, and functions as a data extraction unit DE. The portable terminal 10 can be configured by installing a dedicated application for functioning as the data extraction unit DE, for example, on an existing smartphone equipped with a camera and GPS function. In the portable terminal 10, when an image is captured by the camera CA, the GPS receiving unit 15 receives location information, so that location data DDp (see FIG. 4) can be attached to the fare display image FI.

[0040] The control unit 11 receives various operation commands (input signals) via the touch panel 12, outputs various data including the imaging results (image data) by the imaging unit 14 (camera CA) to the display unit 13, and performs various processes as a data extraction unit DE to generate extraction result data LD and further parking fee data TD, and transmits the various processing result data such as the parking fee data TD from the communication unit 16 to the parking lot management server 50. At this time, the extraction result data LD and the fee display image FI may be transmitted together with the transmission of the parking fee data TD.

[0041] As described above, the parking lot management server 50 can be configured with various types of servers, and in this embodiment, the parking lot management server 50 includes a control unit 51 and a communication unit 52. The control unit 51 includes a parking management database 51d that stores various data related to parking management, such as parking fee data TD. In other words, the parking fee data TD, etc. transmitted from the mobile terminal 10 are stored and managed in the parking management database 51d.

[0042] Furthermore, the control unit 51 transmits data via the communication unit 52 to the on-site terminal 70 installed in the corresponding parking lot, based on the parking lot specification information SS1 and the position data DDp attached to the parking fee data TD.

[0043] As described above, the on-site terminal 70 is composed of, for example, an adjustment machine AM installed in the parking lot (on-site), and includes a control unit 71 and a communication unit 72. The control unit 71 is composed of, for example, an electronic circuit, or a CPU, a storage device, etc., and functions as a parking fee setting unit FS and a settlement processing unit PT. That is, the control unit 71 functions as a parking fee setting unit FS by setting a parking fee based on the parking fee data TD received from the parking lot management server 50 via the communication unit 72. Also, the control unit 71 functions as a settlement processing unit PT by performing settlement processing at the time of leaving the parking lot according to the parking fee system set as the parking fee setting unit FS. That is, the on-site terminal 70 functions as an adjustment machine AM. Also, for example, the on-site terminal 70 (adjustment machine AM) may transmit the result of the settlement processing to the parking lot management server 50 each time, thereby managing the fees in the parking lot management server 50.

[0044] With regard to information reception using the communication unit 72 of the on-site terminal 70, as long as it is possible to receive the necessary information, i.e., the parking fee data TD, it is not limited to being via wireless communication, etc., and may be configured to enable reception of information such as the parking fee data TD by an information reception unit RE that can accept physically existing storage devices such as a USB memory stick or SD card.

[0045] With the above-mentioned configuration, the parking fee setting system 100 can set the parking fee.

[0046] Hereinafter, an overview of one modified example of the parking fee setting system 100 will be described with reference to Fig. 7. Fig. 7 corresponds to Fig. 1, and differs from the example shown in Fig. 1 etc. in that the data extraction unit DE is provided in the parking lot management server 50.

[0047] That is, in the case of the modified example shown in Fig. 7, the portable terminal 10 does not perform extraction processing (OCR processing) of character data related to the parking fee, and transmits the fee display image FI, which is image data captured by the imaging unit 14 (camera CA), from the portable terminal 10 to the parking lot management server 50. In this case, the portable terminal 10 does not require, for example, a dedicated app, and can be considered as an external device that only transmits image data to the parking lot management server 50, etc. However, the position data DDp when the parking fee signboard SG is captured, i.e., when the fee display image FI is generated, may be transmitted from the portable terminal 10, which is an external device, together with the fee display image FI.

[0048] The parking lot management server 50 extracts various data from the fee display image FI from the mobile terminal 10 using the data extraction unit DE, and transmits the extracted parking fee data TD to the corresponding on-site terminal 70. This enables the parking fee setting system 100 to set the parking fee. In this case, the parking lot management server 50 can be considered to extract the parking fee data TD from the fee display image FI transmitted from the outside (mobile terminal 10) and transmit it to the on-site terminal 70 as the corresponding payment machine.

[0049] As described above, the parking fee setting system 100 in this embodiment includes a data extraction unit DE that extracts parking fee data TD from the fee display image FI based on the creation format of the parking fee signboard SG, and a parking fee setting unit FS that sets the parking fee based on the parking fee data TD extracted by the data extraction unit DE. In this case, when the parking fee setting unit FS sets the parking fee based on the parking fee data TD extracted from the fee display image FI by the data extraction unit DE, the parking fee data TD is extracted based on the creation format of the parking fee signboard, so that accurate reading can be performed, and the parking fee can be easily and reliably set in a state that matches the contents shown in the fee display image FI, even if the fee system is complicated.

[0050] Second Embodiment An example of the parking fee setting system 100 according to the second embodiment will be described below with reference to FIG. 8 and other figures. This embodiment is different from the first embodiment in that parking fee data TD is transmitted (sent) from the parking lot management server 50 to a user terminal TI of the parking lot, and the user terminal TI functions as a payment machine including a parking fee setting unit FS. Note that the overall configuration of the parking fee setting system 100 other than the above viewpoint is the same as that of the first embodiment, and therefore detailed description of each component of the overall configuration denoted by the same reference numeral will be omitted.

[0051] Fig. 8 is a conceptual diagram for explaining an overview of the parking fee setting system 100 according to this embodiment, and corresponds to Fig. 1. In this embodiment, as shown in the figure and as described above, the parking fee data TD is transmitted (transmitted) from the parking lot management server 50 to the user terminal TI.

[0052] Here, the user terminal TI is, for example, a smartphone or the like owned by a parking lot user, and is pre-registered for payment or the like, and the contents of the pre-registration are managed by the parking lot management server 50. A parking lot user can pay parking fees on the user terminal TI owned by the user. That is, the user terminal TI functions as a payment machine that performs payment processing. The user terminal TI may be configured, for example, such that a dedicated app is installed on a smartphone owned by the user so that the smartphone itself functions as a payment machine, or such that a payment process is performed by accessing a payment website on the smartphone owned by the user. For example, when the smartphone itself becomes a user terminal TI that functions as a payment machine, the parking fee data TD is transmitted from the parking lot management server 50 in conjunction with the installation of a dedicated app, and the user terminal TI includes a parking fee setting unit FS, and the payment of the parking fee based on the fee system set by the parking fee setting unit FS in response to the parking fee data TD is made on the user terminal TI.

[0053] Incidentally, as shown in FIG. 9, which is a diagram corresponding to FIG. 7, even when the data extraction unit DE is provided in the parking lot management server 50, the data can be similarly transmitted (transmitted) from the parking lot management server 50 to the parking lot user terminal TI.

[0054] In addition, in the embodiment described with reference to Figures 8 and 9, the on-site terminal 70 described with reference to Figure 1, etc. may be installed in parallel with the user terminal TI, and settlement via the on-site terminal 70 may also be available.

[0055] As described above, in this embodiment, when the parking fee setting unit FS sets the parking fee based on the parking fee data TD extracted from the fee display image FI by the data extraction unit DE, the parking fee data TD is extracted based on the format of the parking fee sign, so that accurate reading can be performed, and even if the fee system is complicated, the parking fee can be easily and reliably set in accordance with the contents shown in the fee display image FI. Particularly, in the case of this embodiment, the parking fee can be set and settlement processing (payment of parking fee) can be performed on the user terminal TI.

[0056] Third Embodiment Hereinafter, an example of the parking fee setting system 100 according to the third embodiment will be described with reference to FIG. 10. This embodiment is different from the first embodiment in that the parking fee data TD is transmitted (sent) from the mobile terminal 10 to the on-site terminal 70, as compared with the parking fee setting system 100 described as an example of the first embodiment. In this case, the parking lot management server 50 may not exist, and the on-site terminal 70 may perform parking management in a stand-alone manner. The overall configuration of the parking fee setting system 100 other than the above viewpoint is the same as that of the first embodiment, and therefore detailed description of each component denoted by the same reference numeral in the overall configuration will be omitted.

[0057] FIG. 10 is a conceptual diagram for explaining an overview of the parking fee setting system 100 according to this embodiment, and corresponds to FIG. 1. In this embodiment, as shown in the figure and as described above, the parking fee data TD is directly transmitted (transmitted) from the mobile terminal 10 to the on-site terminal 70. In this case, it is considered that both the mobile terminal 10 and the on-site terminal 70 are present in the on-site parking lot, and for example, a short-distance wireless communication may be performed between them to transmit necessary information such as the parking fee data TD. Furthermore, the on-site terminal 70 may be configured to have no communication unit, and to receive information such as the parking fee data TD by an information receiving unit that can receive a physically existing storage device such as a USB memory or an SD card.

[0058] As shown in the figure, when the parking lot management server 50 is present, for example, as indicated by the dashed arrow, it is possible to consider a mode in which the parking fee data TD is transmitted (transmitted) from the mobile terminal 10 to the parking lot management server 50 after the fact. Alternatively, after transmitting the parking fee data TD to the parking lot management server 50, the on-site terminal 70 may wait for a response from the parking lot management server 50 and then start settlement processing based on the parking fee data TD.

[0059] As described above, in this embodiment, when the parking fee setting unit FS sets the parking fee based on the parking fee data TD extracted from the fee display image FI by the data extraction unit DE, the parking fee data TD is extracted based on the format used to create the parking fee sign, so that accurate reading can be performed, and parking fee setting that is maintained in accordance with the contents shown in the fee display image FI can be easily and reliably performed even if the fee system is complicated. Particularly, in this embodiment, the data extraction unit DE is provided in the mobile terminal 10, while the parking fee setting unit FS is installed in the parking lot, which is the site.

[0060] [Fourth embodiment] Hereinafter, an example of the parking fee setting system 100 according to the fourth embodiment will be described with reference to Fig. 11. This embodiment is a modified example of the first embodiment and the like.

[0061] Fig. 11 is a conceptual diagram for explaining an overview of the parking fee setting system 100 according to this embodiment, and corresponds to Fig. 10 etc., which are referred to as an example of the third embodiment. This embodiment is different from the third embodiment in that, compared with the parking fee setting system 100 described with reference to Fig. 10, a fee display image FI is transmitted (sent) from the mobile terminal 10 to an on-site terminal 70, and conversion from the fee display image FI to parking fee data TD is performed in the on-site terminal 70. That is, in this embodiment, a data extraction unit DE is provided in the on-site terminal 70.

[0062] In the present embodiment, first, the portable terminal 10 does not perform extraction processing (OCR processing) of character data related to the parking fee, but transmits the fee display image FI, which is image data captured by the camera CA, directly to the on-site terminal 70. The on-site terminal 70 extracts various data from the fee display image FI from the portable terminal 10 using a data extraction unit DE, and generates parking fee data TD as the extraction result. That is, the fee display image FI is converted into parking fee data TD. Furthermore, the parking fee is set in the parking fee setting unit FS of the on-site terminal 70 based on the parking fee data TD.

[0063] As indicated by the dashed arrow, the parking fee data TD is subsequently transmitted (sent) from the on-site terminal 70 to the parking lot management server 50. Alternatively, after transmitting the parking fee data TD to the parking lot management server 50, the on-site terminal 70 may wait for a response from the parking lot management server 50 and then start settlement processing based on the parking fee data TD.

[0064] As described above, in this embodiment, when the parking fee setting unit FS sets the parking fee based on the parking fee data TD extracted from the fee display image FI by the data extraction unit DE, the parking fee data TD is extracted based on the format of the parking fee sign, so that accurate reading is possible, and even if the fee system is complicated, the parking fee can be easily and reliably set in accordance with the contents shown in the fee display image FI. Particularly, in this embodiment, the data extraction unit DE and the parking fee setting unit FS are installed at the site, that is, the parking lot.

[0065] Fifth embodiment Hereinafter, an example of the parking fee setting system 100 according to the fifth embodiment will be described with reference to Fig. 12. This embodiment is a modified example of the first embodiment and the like.

[0066] Fig. 12 is a conceptual diagram for explaining an overview of the parking fee setting system 100 according to this embodiment, and corresponds to Fig. 1 etc. As shown in the figure, this embodiment differs from other embodiments in that a block copy image BI for signboard production is used as a fee display image FI.

[0067] In the production of a parking fee sign SG, as a preliminary step, a sign maker or sign designer may create a draft image BI as a PDF file, for example, using drawing software built into a PC, as a preliminary step to producing and installing the sign.

[0068] In this embodiment, the image data of such a block copy image BI is treated as a fee display image FI, and the parking fee is set in the same manner as in the other embodiments. That is, the block copy image BI as the fee display image FI is converted into parking fee data TD.

[0069] In the illustrated example, when a fee display image FI (block image BI) is transmitted (sent) to a parking lot management server 50 equipped with a data extraction unit DE, the block image BI is converted to parking fee data TD in the parking lot management server 50, and the parking fee data TD is transmitted (sent) to an on-site terminal 70 equipped with a parking fee setting unit FS or a user terminal TI. Furthermore, based on the parking fee data TD, the parking fee is set in the on-site terminal 70 or the parking fee setting unit FS of the user terminal TI. In the above case, the parking lot management server 50 can be considered to be configured such that a block image BI as a fee display image FI is transmitted from an external PC, the parking lot management server 50 extracts the parking fee data TD from the transmitted block image BI, and transmits it to the on-site terminal 70 as a corresponding payment machine.

[0070] In the above, for example, a camera CAα may be provided in the on-site terminal 70 at a position where the parking fee signboard SG installed in the parking lot can be imaged, and image data of the parking fee signboard SG captured by the camera CAα may be analyzed to extract information corresponding to the parking lot identification information SS1 (see FIG. 5, etc.), for example, and the parking fee setting unit FS may compare the extracted information with the parking fee data TD. By performing the above comparison, it is possible to determine whether the parking fee data TD acquired via the parking lot management server 50 matches the contents of the parking fee signboard SG actually installed. In this case, the above comparison may be used, for example, to start setting the parking fee after the parking fee setting unit FS confirms that the parking fee signboard SG corresponding to the block copy image BI has been installed. The above confirmation using the camera CAα may be performed automatically, i.e., unmanned, or remotely at the site. Also, a configuration may be adopted in which the camera CAα as described above is not provided, and the above confirmation may be performed by a method other than the camera CAα.

[0071] As described above, in this embodiment, when the parking fee setting unit FS sets the parking fee based on the parking fee data TD extracted from the fee display image FI by the data extraction unit DE, the parking fee data TD is extracted based on the creation format of the parking fee sign, so that accurate reading is performed, and even if the fee system is complicated, the parking fee can be easily and reliably set in accordance with the contents shown in the fee display image FI. In particular, in this embodiment, a block copy image BI for sign production can be used as the fee display image FI.

[0072] 〔others〕 The present invention is not limited to the above-described embodiment, and can be embodied in various forms without departing from the spirit and scope of the present invention.

[0073] First, various aspects of the data extraction unit DE have been described above, but the present invention is not limited to these and may be further modified. For example, a processing part for extracting the extraction result data LD from the fee display image FI and a processing part for generating the parking fee data TD from the extraction result data LD may be performed in separate locations.

[0074] In addition, among the above, various aspects are possible regarding the method of creating the parking fee data TD by the data extraction unit DE. For example, it is possible to perform deep learning on a typical known fee display image (parking fee sign), that is, to prepare artificial intelligence that enables analysis of what the partial images in each part of the fee display image FI indicate, and to use this to generate the parking fee data TD from the fee display image FI. [Explanation of symbols]

[0075] 10...portable terminal, 11...control unit, 12...touch panel, 13...display unit, 14...imaging unit, 15...GPS receiving unit, 16...communication unit, 50...parking lot management server, 51...control unit, 51d...parking management database, 52...communication unit, 70...on-site terminal, 71...control unit, 72...communication unit, 100...parking fee setting system, AM...payment machine, BI...plate image, BL...area, CA...camera, CA...imaging unit 14 (camera, CAα...camera, DD...main data, DD1 to DD D4...data, DDp...location data, DE...data extraction section, FC...parking fee data creation program, FD...creation format storage section, FI...fee display image, FS...parking fee setting section, LD...extraction result data, LE...character string extraction program, LS...list, PD...parking fee data storage section, PT...payment processing section, RE...information reception section, SG...parking fee signboard, SS1...parking lot specific information, TD...parking fee data, TI...user terminal, TJ...type determination program

Claims

1. a data extraction unit that extracts parking fee data from the fee display image based on a creation format of the parking fee sign; a parking fee setting unit that is provided in the payment machine and sets a fee for payment processing that matches the information written on a signboard of the parking lot based on the parking fee data extracted by the data extraction unit; A parking fee setting system comprising:

2. The parking fee setting system according to claim 1 , wherein the data extraction unit determines a type of each piece of data constituting the parking fee data to be extracted depending on a display position in the fee display image.

3. 3. The parking fee setting system according to claim 1, wherein the data extraction unit extracts parking lot identification information included in the fee display image, links the extracted parking lot identification information to the parking fee data, and transmits the information to the parking fee setting unit.

4. 4. The parking fee setting system according to claim 1, wherein the fee display image includes a captured image of a signboard installed in the parking lot.

5. A portable terminal that captures an image by an imaging unit and generates the fee display image, The parking fee setting system according to any one of claims 1 to 4, wherein the portable terminal associates position information at the time of capturing an image by the imaging unit with the fee display image.

6. The parking fee setting system according to claim 5 , wherein the portable terminal includes the data extraction unit, and links the location information to the parking fee data and transmits the data to the parking fee setting unit.

7. The data extraction unit is provided in a parking lot management server, The payment machine having the parking fee setting unit is installed at a site, The parking fee setting system according to any one of claims 1 to 5, wherein the parking lot management server extracts the parking fee data from the fee display image transmitted from outside and transmits it to the corresponding payment machine.

8. The price display image includes a copy image for signboard production, 8. The parking fee setting system according to claim 1, wherein the parking fee setting unit starts setting fees for the parking lot after confirming that a sign corresponding to the block copy image has been installed.

Images