JP2010238203A - Roadside device, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a roadside device 15 to concretely select an exact parking lot where distribution information is useful to a user of an ITS (Intelligent Transport System) onboard unit 17 while using DSRC (Dedicated Short Range Communication) standard of road/vehicle communication. <P>SOLUTION: The roadside device 15 receives uplink information including information of the past stopovers from the ITS onboard unit 17 (S55Yes) and detects the position of a user's house on the basis of the uplink information (S60). A square frame, the one side of which includes a predetermined length is set centering on three-dimensional meshes at which the position of the house is located, and each three-dimensional mesh existing on the square frame is selected (S61). Downlink information wherein information of a parking lot included in the selected three-dimensional mesh is designated to IDs=50 and 51 of an information group is generated, and distributed (S62 and S63). <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a roadside apparatus, method, and program using road-to-vehicle communication such as DSRC (Dedicated Short Range Communication).

  Patent Document 1 acquires map data from a CD-ROM or DVD-ROM of a DVD-ROM drive (paragraph 0017 of Patent Document 1), and provides parking information (see FIG. 4 of Patent Document 1) to the user based on the map data. A navigation device presenting b)) is disclosed. In the structure of the map data, the facility name, latitude / longitude, parking lot information, etc. are associated with each point information (FIG. 2 of Patent Document 1), and when the user selects a predetermined facility, the facility The presence or absence of a dedicated or affiliated parking lot is checked based on the map data, and if found, the parking lot list is displayed (S102 YES →... → S105 in FIG. 3 of Patent Document 1).

  Patent Document 2 discloses a DSRC vehicle-mounted device that receives information from a roadside device by DSRC (paragraph 0008 and FIG. 1 of Patent Document 2). The DSRC on-vehicle device compares the amount of data received from a roadside device with the amount of memory that can be stored in the memory, and stores it if it can be stored in the memory. The oldest information is deleted and then stored in the memory (S105 to S110 in FIG. 2 of Patent Document 1).

JP 2002-323332 A JP 2007-109032 A

  Data in a predetermined road-to-vehicle data transmission format is basically distributed by a push-type information distribution method by individual communication in the 5.8 GHz band DSRC, whereby the roadside device is equipped with an ITS (Intelligent Transport System) in the communication area. Road traffic system) It is possible to distribute various contents according to the characteristics of the ITS on-board device and the preference of the user (occupant) to the on-board device.

  In order to realize rational information distribution from the roadside device to the ITS on-board unit in the predetermined road-to-vehicle data transmission format, the preference data table information is included in the downlink information, and the preference data is included in the uplink information. It is considered that preference data as user responses to the table is included, and the roadside device narrows down to information reflecting the preference data and distributes the information to the in-vehicle device. In the predetermined road-to-vehicle data transmission format, when the roadside device enters the DSRC area, the roadside device can obtain information on the past stop-off location from the in-vehicle device along with the preference data. .

  In the information distribution using the preference data from the in-vehicle device, it is possible to include the information associated with the user's preference, the parking lot and the associated parking lot in the downlink information, and the parking lot and the alliance of the facility. Dynamic information and static information of a parking lot unrelated to the parking lot can be arbitrarily included in the downlink information. Therefore, it is desirable to specifically and accurately select a parking lot that is irrelevant to the facility related to the user preference and is useful to the user, and to distribute the dynamic information and static information.

  Patent Document 1 discloses that a navigation device is used to distribute information on a dedicated or affiliated parking lot to a user-selected facility, but is independent of the facility and useful to the user of the information. There is no suggestion on how to select an appropriate parking lot for information distribution. Further, in the navigation device of Patent Document 1, the parking lot information is not distributed from the roadside device, but is searched from the self-equipped parking lot database.

  Patent Document 2 discloses information distribution from a roadside device to an in-vehicle device using DSRC, but is a parking lot information, and a specific selection of a parking lot in which the information is useful for a user of the in-vehicle device It does not suggest how.

  An object of the present invention is to provide a roadside device, a method, and a program for specifically selecting and distributing an accurate parking lot in which distribution information is beneficial for a user of an in-vehicle device while using a standard for road-to-vehicle communication. That is.

  According to the present invention, a regional section is selected based on past stopover information of the in-vehicle device received wirelessly from the in-vehicle device that has entered the wireless communication area. For example, the number of times of stoppage and the date and time of stoppage of each past stopover are grasped from the past stopover information, and a reference point such as a home position is detected based on the information. Then, for example, an area section having a parking lot for delivering information to the user of the in-vehicle device is selected based on the distance to the home position and the required time.

The roadside apparatus of the present invention includes the following.
Receiving means for wirelessly receiving past stopover information from an in-vehicle device that has entered the wireless communication area,
A regional section selecting means for selecting a regional section based on the received past stop-off area information, and a distribution means for wirelessly distributing information on the parking lot included in the selected regional section to the in-vehicle device in the wireless communication area.

The roadside apparatus control method of the present invention includes the following steps.
A reception step of receiving the past stop-by location information wirelessly from the in-vehicle device that has entered the wireless communication area,
A regional partition selection step of selecting a regional partition based on the received past stop-off location information, and a distribution step of wirelessly distributing the parking lot information included in the selected regional partition to the in-vehicle device in the wireless communication area.

  The program of the present invention functions as each means of the roadside device of the present invention described above.

  According to the present invention, the roadside device selects an appropriate area block based on the information group obtained from the in-vehicle device, distributes the parking lot information existing in the area block to the in-vehicle device, and provides the vehicle-mounted device user with the information. Useful parking information can be given.

1 is a schematic diagram of a road-to-vehicle DSRC system based on data in a predetermined road-to-vehicle data transmission format. It is explanatory drawing of the data transmission aspect in a predetermined road-to-vehicle data transmission format. It is a figure which shows whether each ID is essential or arbitrary about the structure of an information group. It is a 1st part of the classification table allocated to each ID used by downlink. It is a 2nd part of the classification table allocated to each ID used by a downlink. It is a 3rd part of the classification table allocated to each ID used by a downlink. It is a 4th part of the classification table allocated to each ID used by a downlink. It is a figure which shows the communication and process between each apparatus implemented by the transaction between a roadside apparatus roadside apparatus and ITS onboard equipment.

It is data explanatory drawing of the uplink information sent to an roadside apparatus from an ITS onboard equipment. It is explanatory drawing which expressed table example of preference data. It is an example of the screen of the check which the ITS onboard equipment which received preference data from the roadside apparatus roadside apparatus displays on the display part of a navigation part. It is a flowchart of a parking lot information delivery method. It is a figure which illustrates the distribution of the past drop-in place of the ITS onboard equipment which the roadside apparatus acquired from the uplink information from ITS onboard equipment. It is a figure which shows the position of the tertiary mesh of an area range including a home position, and a parking lot. It is the distribution map of the tertiary mesh which selected another tertiary mesh, and a parking lot. It is a flowchart of the onboard equipment side transmission / reception method. It is a block diagram of a road-to-vehicle wireless communication system. It is a flowchart of a roadside device control method.

  FIG. 1 is a schematic diagram of a road-to-vehicle DSRC system 10 based on data in a predetermined road-to-vehicle data transmission format. The roadside machine 11 constitutes a roadside device 15 together with the server 12, and is connected to the server 12 by wire or wirelessly. Further, the server 12 can exchange data with another server via a network such as the Internet. The roadside device 11 transmits and receives data to and from the ITS vehicle-mounted device 17 mounted on the automobile 13 existing in an area having a diameter of about several m to 30 m by using 5.8 GHz band radio waves. The ITS vehicle-mounted device 17 includes a DSRC unit 18 and a navigation unit 19.

  FIG. 2 is an explanatory diagram of a data transmission mode in a predetermined road-to-vehicle data transmission format. In the downlink of the multi-content format, data is classified according to its type, and ID codes “00”, “01”, “02”,. In multi-content format data transmission, data is grouped in units of information groups, and each information group has classification data with ID = “00” at the head. The classification data of ID = “00” is configuration information indicating what kind of ID is included in the information group.

  FIG. 3 is a diagram showing whether each ID is essential or optional for the configuration of the information group. ID = 00, 01, 02 must be included in each information group. ID = 03, 04, and 05 do not need to be included in the information group when providing information only with ID = 60, but must be included in the information group when providing other information. Whether or not other IDs are included in the information group is arbitrary.

  4 to 7 are classification tables assigned to each ID used in the downlink. ID = 00 is a classification of configuration ID information (an area describing what ID each information group stores). ID = 01 is a classification of a business operator, a service business code (a business code that can identify a service business), a service business display text (a service business name (service name) text information for navigation display), And a service provider phonetic character string (service company name (service name) phonetic character string information for navigation utterance).

  ID = 02 is a content classification, and is a company code (a code that can identify the information provider of the content), a company display text (information providing company name text information for navigation display), a company phonetic character string (for navigation utterances) Information providing company name phonetic character string information), information code (information code that can identify the content), information display text (content content text information for navigation display), information phonetic character string (content content phonetic character string information for navigation utterances) ), And a preference data category (category code indicating an information category to which the information corresponds).

  Similar to ID = 02, ID = 03 is a content classification, and an immediate playback / storage code (a code representing a content playback operation after reception) and a playback condition code (content playback conditions in the information provision area) Code).

  ID = 04 is a classification of an expiration date, and includes a start year / month / day / hour / minute / second (content expiration date) and an end year / month / day / hour / minute / second (content expiration date). ID = 05 is a classification of provision time, and includes business hours (business hours of content provider) and information provision time (content provision time).

  ID = 10 is the classification of the target point, the target point coordinates (latitude and longitude information of the point where the service can be provided), the target point display text (service name (store name, etc.)), partner parking information (target Partner parking lot information other than location), icon display image data (icon data representing a place where service can be provided), display character data (text information for service description), display image data (still image information representing service) , Phonetic character string data (phonetic character string information indicating service), compressed voice data (compressed voice data information), voice playback order (representing the playback order of phonetic string and compressed voice), video data (video data) Information) and a URL (URL information representing a service).

  ID = 20 is a classification of information provision points. For a total of five information provision points, information provision center coordinates (latitude and longitude information for reproducing pop-up information) and information provision areas (areas for reproducing pop-up information) are provided. Radius information from central coordinates to be defined), information provision direction code (information provision direction information for reproducing pop-up information), information provision road type (road type information for reproducing pop-up information), display image data (still image for pop-up reproduction) Data), phonetic character string data (phonetic character string information for pop-up playback, compressed voice data for compressed voice data for pop-up playback), and voice playback order (a code representing the playback order of voice data for pop-up playback). .

  ID = 30 is a category of transition information, and includes a total of eight next reproduction information codes (screen transition information). ID = 40 is a classification of detailed information, and for each of the total 8 pieces of detailed information, display character data (navigation display detailed information text information) and utterance phonetic character string (navigation utterance detailed information) Phonetic character string information). For ID = 40 in FIG. 5, for the line described as “detailed information 1”, “detailed information 1” is changed to “detailed information 1 display character data” and the content of the information is changed to “displayed characters”. When the "detailed information text information for data navigation display" is changed to "detailed information text information for navigation display", the lines of "detailed information 1 utterance character string for utterance" and "detailed information phonogram string information for navigation utterance" Can also be used.

  ID = 50 is a classification of parking lot information. For each of the 15 parking lots, a parking lot ID (ID that can identify the parking lot), detailed information (dynamic detailed information on parking lots), and special notes (Special notes for parking lots).

  ID = 51 can update the static information of the parking lot stored in the navigation unit 19 for a maximum of 4 meshes in units of tertiary meshes. ID = 51 is the number of tertiary meshes (notifying the number of tertiary meshes including updated parking lot static information), and the tertiary mesh code (updating parking lot static information for each mesh of 1-4). 3rd mesh code included), 3rd mesh version information (3rd mesh version information including updated parking lot static information), 3rd mesh parking lot number (number of parking static information included in updated mesh) Includes tertiary mesh parking lot static information (static information of parking lot to be updated).

  ID = 52 is deleted parking lot ID information. This information is not used when updating all parking information (new / deleted) in mesh units. ID = 52 is the number of the tertiary mesh (notifying the number of the tertiary mesh including the parking lot ID information to be deleted), the tertiary mesh code (the tertiary mesh code including the parking lot ID information to be deleted), the tertiary mesh Version information (version information of the tertiary mesh including the parking lot ID information to be deleted; the same as the version of the static information notified simultaneously with ID = 51), the number of the tertiary mesh deletion parking lot ID (update Deleted parking lot information ID number included in the mesh to be performed) and tertiary mesh deleted parking lot ID information (parking lot ID information to be deleted).

  ID = 60 is classification of driving support, driving support image data (driving support image information), driving support phonetic character string data (driving support phonetic character string information), driving support compressed voice data (driving support compressed voice data). Information) and voice playback order (representing the playback order of the phonetic character string and the compressed voice).

  ID = 80 is a classification of preference data. For a total of 127 pieces of preference data, preference data version (version information of preference data table), preference data (preference data display text information), phonogram string (Speech character string information for utterance of preference data) and detailed information (detailed information of preference data) are included.

  FIG. 8 shows communication and processing between the devices performed in the transaction between the roadside device 15 and the ITS vehicle-mounted device 17. The roadside machine 11 and the server 12 constitute a roadside apparatus 15. The ITS vehicle-mounted device 17 includes a DSRC unit 18 and a navigation unit 19. Explain in chronological order. Communication between the roadside device 11 and the DSRC unit 18 is performed by DSRC radio waves, and communication between the roadside device 11 and the server 12 and between the DSRC unit 18 and the navigation unit 19 is usually performed by a cable.

  As the ITS vehicle-mounted device 17 is turned on, client information data is written from the navigation unit 19 to the DSRC unit 18 in S10. In S11, the DSRC connection is established between the roadside device 11 and the DSRC unit 18 as the automobile 13 equipped with the ITS on-vehicle device 17 enters the radio wave arrival area at a distance (eg, about 30 m) where communication with the roadside device 11 is possible. Processing is performed.

  When the DSRC connection process in S11 is completed, a DSRC connection notification is made in S12 and S13. The connection notification in S12 is from the roadside device 11 to the server 12, and the connection notification in S13 is from the DSRC unit 18 to the navigation unit 19. In S <b> 14, client information is notified from the DSRC unit 18 to the server 12 via the roadside device 11.

  The server 12 determines whether the user of the ITS vehicle-mounted device 17 is a member or a non-member based on the client information notification from the DSRC unit 18, and the hardware of the ITS vehicle-mounted device 17 for appropriately reproducing the content by the ITS vehicle-mounted device 17. Know the wear information. In S <b> 18, content such as a Welcom screen is transmitted from the server 12 to the navigation unit 19 via the roadside device 11 and the DSRC unit 18. The content is organized in a multi-content format. The navigation unit 19 determines a service provider from the multi-content format.

  After S18, the server 12 periodically polls the DSRC unit 18 in S19 until the navigation unit 19 writes the uplink information in the DSRC unit 18. In S20, the navigation unit 19 writes the uplink information to the DSRC unit 18 if it is a member of the service provider, but does nothing if it is not a member.

  In S <b> 24, the server 12 sends default content (e.g., a welcome screen) to the navigation unit 19 via the roadside device 11 and the DSRC unit 18. In S <b> 29, the server 12 performs memory access polling for the DSRC unit 18. On the other hand, in S30, if the user is a member, the DSRC unit 18 notifies the server 12 of uplink information.

  In S33, the server 12 organizes the storage-type content suitable for the member preference based on the member information acquired from the uplink information in the multi-content format (FIG. 2) and distributes it to the ITS in-vehicle device 17. As will be described later, the roadside device 15 interrupts the distribution of the accumulation type content one or more times during the period of S33 and interrupts the distribution of the immediate reproduction type content. In S34, the end of distribution of the storage type content is notified. The automobile 13 equipped with the ITS vehicle-mounted device 17 leaves the communication area with the roadside device 11 with the end of distribution.

  FIG. 9 is a data explanatory diagram of uplink information sent from the ITS vehicle-mounted device 17 to the roadside device 15. Uplink information is sent in multiple tags. The tag 1 includes a service provider code, a destination (latitude and longitude), a waypoint (latitude and longitude) 1 to 5, a cumulative travel distance, a preference genre data version, preference genre data, and member information 1 to 8. The tag 2 includes a service provider code and past stopover locations (latitude and longitude) 1 to 41. The tag 3 includes a service provider code and past stopover places (latitude and longitude) 42 to 82.

  The tag 4 includes a service provider code and reception / reproduction history (reception information code and reproduction identification flag) 1 to 123. The tag 5 includes a service provider code and reception / reproduction history (reception information code and reproduction identification flag) 124 to 246.

  FIG. 10 is an explanatory diagram showing an example of preference data with ID = 80 as a table. The preference data includes a preference data number, preference data display text, preference data display nest, preference data target identifier, preference data default value, and phonogram string. There are a total of 128 preference data numbers ranging from 0 to 127, and the service provider can freely set items for each data number. Of the 128 items, a maximum of 96 items are notified as uplink information from the ITS in-vehicle device 17 to the roadside device 15 in S30 (FIG. 8).

  Of the 96 items notified as uplink information, 12 items are used for public information provision service purposes and are information items distributed by default when providing information in DSRC communication. In the preference data table of FIG. 10, the display nest means a hierarchy of each item (corresponding to the data number of FIG. 10), and a larger numerical value means a lower hierarchy. The target identifier means that an item whose value is “0” is not a check target on the preference data check screen (FIG. 11 described later) in the navigation unit 19, and is “1”. This means that the item is a check target on the check screen. The default value means that an item with “0” is displayed on the initial check screen without checking, and an item with “1” is displayed on the initial check screen. It means to display with check.

  FIG. 11 is an example of a check screen that the ITS vehicle-mounted device 17 that has received the preference data from the roadside device 15 displays on the display unit of the navigation unit 19. The user can scroll the screen up and down by dragging the scroll bar 23. In FIG. 11, when the user clicks the on button, the check is added, and when the user clicks the off button, the check is removed. In each item, it means that the user has selected the one in which “on” and “off” are italicized.

  Distribution of parking lot information from the roadside device 15 to the ITS vehicle-mounted device 17 in the road-to-vehicle DSRC system 10 uses ID = 10 (FIG. 4) and ID = 50, 51 and / or 52 (FIGS. 6 and 5). 7) may be used. The designation of the parking lot information with ID = 10 is used for the distribution of the information on the parking lot of the facility associated with the preference data and the information of the partner parking lot. In detail, the following (a1) and (a2) It is as follows.

(A1) When using the target point coordinates of the target point information classification of ID = 10: If the facility as the target point does not have a parking lot, the latitude of the center position of the facility is used as the target point coordinate・ Longitude is designated, but when the facility has a parking lot, the latitude / longitude of the entrance of the parking lot is designated in the column of the target point coordinates.

(A2) When using affiliated parking lot information of classification of target point information of ID = 10; In the affiliated parking lot information, the ID of the affiliated parking lot of the facility at the target point is entered. The roadside device 15 holds a parking lot database for target points nationwide, and grasps information information (location, name, fee, business hours, etc.) about the corresponding parking lot from the parking lot ID based on the parking lot database. Be able to. The parking lot ID is the prefecture / city / town / city code (JIS compliant): 5 digits + district code (added when the city / town / village is required): 1 digit + parking lot type code: 1 digit + company code: 3 digits + Sequential code: 6 digits + branch number: 1 digit, consisting of 17 digits in total, making it unique nationwide.

  In the designation of the parking lot information in ID = 50, 51 and / or 52 (FIGS. 6 and 7), information on any parking lot unrelated to the parking lot of the facility associated with the preference data and the partner parking lot is obtained. Can be specified. The roadside device 15 uses ID = 50, 51 and / or 52 to repeatedly distribute information on a predetermined parking lot every time the ITS onboard unit 17 enters the DSRC area. The distribution of parking lot information by these IDs will be described in detail below.

  In the classification of the parking lot information with ID = 50 (FIG. 6), the roadside device 15 has dynamic information about the maximum of 15 parking lots (full information on the vehicle type by entrance, opening hours, initial charges, additional charges, etc.). Can be specified.

  In the classification of the parking lot additional update information with ID = 51 (FIG. 6), the roadside device 15 can designate a maximum of four tertiary meshes. Each tertiary mesh has static information on the maximum 511 parking lots (latitude / longitude of the entrance, name of parking lot, number of vehicles accommodated, vehicle restrictions (vehicle height restriction, vehicle width restriction, vehicle length restriction), warehousing. It is possible to specify a possible time, a leaving time, a regular holiday, etc.

  In the classification of the deleted parking lot ID information with ID = 52 (FIG. 7), the roadside device 15 can specify a maximum of four tertiary meshes. In each tertiary mesh, the IDs of up to 63 parking lots to be deleted can be designated. ID = 52 is used in combination with ID = 51. That is, when the parking lot information in the predetermined tertiary mesh is completely changed in the parking lot database in the ITS in-vehicle device 17, only ID = 51 is used and ID = 52 is not used. On the other hand, in the parking lot database in the ITS vehicle-mounted device 17, when updating the parking lot information in the predetermined third mesh with the difference information, ID = 51 designates additional parking lot information, and ID = 52 designates the ID of the information of the deleted parking lot. In addition, a flag indicating whether the parking lot information is a full change or a difference change can be prepared in the information group.

  Not only ID = 50 but also the distribution of parking lot information by ID = 51 or the distribution of parking lot information by both ID = 51 and ID = 52 is used in combination. Because the data in the parking lot database of the ITS on-board device 17 may be out of date, that is, the parking lot may be newly established, abolished, or changed, etc. = 51 etc., the parking lot information is distributed, and the ITS vehicle-mounted device 17 updates the parking lot information in the parking lot database, and then gives the dynamic information of ID = 50 to the user based on the updated parking lot database. This is in order to guarantee the accuracy of the presentation information.

  FIG. 12 is a flowchart of the parking lot information distribution method 50. The parking lot information distribution method 50 is executed in the server 12 of the roadside device 15. The parking lot information distribution method 50 is executed at regular intervals, for example. In S51, it is determined whether the ITS vehicle-mounted device 17 has entered the DSRC area. If the determination is positive, the process proceeds to S52, and if not, the parking lot information distribution method 50 is terminated. The fact that the ITS vehicle-mounted device 17 has entered the DSRC area can be detected by the roadside device 15 receiving a predetermined data-containing radio wave from the ITS vehicle-mounted device 17.

  In S52, connection processing with the ITS vehicle-mounted device 17 is performed. In S53, it is determined whether the user of the ITS vehicle-mounted device 17 is a member or non-member of the information provider of the roadside device 15 (eg, the service provider at ID = 01 or the information provider company at ID = 02 in FIG. 4). If it is determined that the member is a member, the process proceeds to S54. If the member is a non-member, the parking lot information distribution method 50 is terminated.

  In S54, the ITS on-board device 17 is requested to transmit uplink information. In S55, it is determined whether uplink information has been received, and the process proceeds to S60 as soon as it is received. The specific contents of the uplink information to be received are as shown in FIG. 9, and the user of the ITS in-vehicle device 17 has a past drop-in place (the past drop-off places 1 to 82 of the tags 2 and 3) and the preference data (the tag 1). Preference genre data). In addition, since the information on the past stop points of the tags 2 and 3 in FIG. 9 includes not only the latitude and longitude of the past stop points, but also the stop date and time, the information on the number of stops and the frequency of the stop at the same point is also grasped. be able to.

  In S60, the information on the past drop-in place, that is, the points (specifically latitude and longitude) of the past drop-off places 1 to 82 of the tags 2 and 3 are extracted from the uplink information, and the home position of the user is detected.

  FIG. 13 is a diagram illustrating a distribution of past drop-off places of the ITS in-vehicle device 17 obtained from the uplink information from the ITS on-vehicle device 17 by the roadside device 15. In FIG. 13, “X” indicates a past stop-in place. The roadside device 15 can obtain a maximum of 84 past stopovers from the uplink information from the ITS onboard equipment 17. The past drop-in place of the ITS vehicle-mounted device 17 indicates a point where the vehicle 13 on which the ITS vehicle-mounted device 17 is mounted has turned off the engine (a point where power supply from the battery to the ITS vehicle-mounted device 17 is cut off by turning off the engine key). The ITS vehicle-mounted device 17 clears the past stopover information of the storage device after transmitting the uplink information, and records the past stopover information in order from the past stopover 1 again. ing.

  In the distribution map of past stopovers in FIG. 13, R1 indicates the maximum number of past stopover points, and R2 is recognized to be the number that is smaller than R1, but next to R1, and sufficient. It is a point that can be done. In consideration of an error of about several meters with respect to the point, R1 and R2 are shown not as points but as a circular range with a predetermined radius. R1 is understood to be the home position of the user of the ITS on-vehicle device 17. If the user is used for commuting or attending school, R2 is recognized as the user's workplace (including school).

  As described above, since the information on the past stop points of the tags 2 and 3 in FIG. 9 includes not only the latitude and longitude of the past stop points but also the stop date and time, the past stop points as shown in FIG. For example, it is also possible to detect the home position or the work place from the stop date and time instead of the distribution map. For example, a past stopover at a predetermined time zone every night or every evening can be a home position, and a past stopover at a predetermined time zone every morning can be a work place.

  Returning to FIG. 12, in S61, a tertiary mesh is selected that surrounds the tertiary mesh at the home position with a square frame centered on it and having a predetermined length on one side. FIG. 14 shows the position of the tertiary mesh and the parking lot in the area including the home position. In FIG. 14, each cell corresponds to each tertiary mesh, and the selection mesh 3 in which the tertiary mesh that is hatched with the right shoulder is surrounded by the square frame of S61 (hereinafter referred to as “selected square frame”). Means the next mesh. A tertiary mesh that is hatched downward is a tertiary mesh having a home position.

  In FIG. 14, “◯” indicates a home position, and “●” indicates a parking position. For convenience of explanation, a parking lot existing in the selected tertiary mesh (each square with hatching in FIG. 14) will be referred to as a “selected parking lot”.

  In FIG. 14, the selected tertiary mesh is a tertiary mesh on the selected square frame, but another tertiary mesh can be set as the selected tertiary mesh. FIG. 15 is a distribution diagram of a tertiary mesh and a parking lot in which a tertiary mesh different from that in FIG. 14 is selected. Also in FIG. 15, as in FIG. 14, a tertiary mesh that is hatched with a rising shoulder means a selected tertiary mesh. Examples of how to determine the selected tertiary mesh are listed as follows (c1) to (c4).

  In addition, in the following (c1) to (c4), the third mesh with the home position is excluded from the selected third mesh because the user is familiar with the third mesh in the vicinity of the home. This is because parking information is not required. In the following, it is assumed that the home position and work place (including school) are not the home position itself or the work place itself but a tertiary mesh having the home position and work place. Since the vicinity of the work place is an area familiar to the user as well as the vicinity of the home position, even if the third mesh corresponding to the selected third mesh in the following (c1) to (c4), the work place If it is a certain cubic mesh, it may be excluded. Further, in the following (c1) to (c4), it is assumed that the home position may be replaced with the work place, or the home position may be replaced with the home position and the work place.

(C1) A tertiary mesh having a radius range of a predetermined distance range and / or a predetermined required time range from the home position other than the tertiary mesh having the home position. This determination method overlaps with the determination method in FIG. 13, but it is not necessary to make all the corresponding tertiary meshes as tertiary meshes as shown in FIG. 13, and a predetermined tertiary mesh (eg, connecting home and work place). The case where a 3rd-order mesh with a route) is excluded is included.
(C2) A third-order mesh having a past stopover place other than the home position with a large number of stopovers.
(C3) A tertiary mesh that includes a relatively large number of past stopovers in a time zone where the parking lot is relatively crowded on holidays other than the home position.

(C4) A tertiary mesh related to preference data (preference genre data of tag 1 in FIG. 9). For example, if it is determined that the user's preference determined from the preference data is favorable for movies, sports, music, or paintings, a tertiary mesh including a movie theater, a baseball field, a concert hall, or a museum is selected. At that time, the movie theaters and the like are limited to those within a predetermined distance range and / or required time range from the home position.

  Returning to FIG. 12, in S <b> 62, downlink information in which the information on the selected parking lot is designated as the information group ID = 50, 51 is generated. As described above, the parking lot information specified for the information group ID = 50 is dynamic information (full information, charges, etc.), and the parking lot information specified for the information group ID = 51 is static. Information (latitude / longitude of each entrance, name, capacity, etc.). In S63, downlink information is transmitted.

  FIG. 16 is a flowchart of the vehicle-mounted device side transmission / reception method 70. The method 70 is executed in the ITS vehicle-mounted device 17. The method 70 is executed at regular intervals, for example. In S71, it is determined whether the ITS vehicle-mounted device 17 has entered the DSRC area. If the determination is positive, the process proceeds to S72, and if not, the method 70 is terminated. The entry of the ITS vehicle-mounted device 17 into the DSRC area can be detected by the ITS vehicle-mounted device 17 receiving a predetermined data-containing radio wave from the roadside device 15.

  In S72, connection processing with the roadside device 15 is performed. In S73, it is determined whether the own device (ITS vehicle-mounted device 17) is authenticated as a member of the information provider by the roadside device 15 or not authenticated. If it is authenticated, the process proceeds to S74. The method 70 ends.

  In S74, it is determined whether a request for uplink information has been received from the roadside device 15, and the process proceeds to S75 as soon as it is received. In S75, uplink information is transmitted. The specific contents of the uplink information transmitted in S75 are as shown in FIG. 9, and the user's preference data (tag 1 preference genre data) of the ITS in-vehicle device 17 and past stopover locations (tags 2 and 3). User information such as past stopovers 1 to 82).

  In S76, it is determined whether downlink information has been received, and the process proceeds to S77 as soon as it is received. The downlink information is also an information group.

  In S77, the downlink information is stored in the reproduction and storage device. Typically, the content with ID = 10 in the downlink information is immediately played. The parking lot information with ID = 50 and 51 is normally temporarily stored in the storage device of the ITS vehicle-mounted device 17 in the storage device, and is reproduced on the monitor or speaker of the navigation unit 19 when a direct or indirect reproduction instruction is given from the user. The

  FIG. 17 is a block diagram of the road-vehicle wireless communication system 85. The road-to-vehicle DSRC system 10 (FIG. 1) is a specific example of the road-to-vehicle wireless communication system 85. The road-to-vehicle wireless communication system 85 includes a roadside device 86 and an in-vehicle device 95 that are connected to each other by wireless communication (for example, DSRC). Specific examples of the roadside device 86 and the vehicle-mounted device 95 are the roadside device 15 and the ITS vehicle-mounted device 17, respectively.

  The roadside device 86 includes a receiving unit 87, a regional section (for example, tertiary mesh) selecting unit 88, and a distributing unit 89. The receiving unit 87 wirelessly receives the past stop-by place information from the in-vehicle device 95 that has entered the wireless communication area. The regional section selecting means 88 selects a regional section based on the received past stop-by place information. The distribution unit 89 wirelessly distributes the parking lot information included in the selected area section to the in-vehicle device 95 in the wireless communication area.

  A specific example of the selected area section is a grid that is hatched with a right shoulder in FIGS. 14 and 15. A specific example of past stopover information is information on past stopovers 1 to 82 of tags 2 and 3 in FIG.

  Typically, the regional section selecting means 88 detects a reference point based on past stopover information and selects a regional section based on the reference point. Preferably, the regional section selecting means 88 selects the regional section based on the distance from the reference point and / or the required time. The area division selection means 88 can select an area area based on, for example, a radius range of a predetermined distance range from the reference point and / or a radius range of a predetermined required time range. A specific example of this is each of the regional sections of the selected square frame in FIG. 14 (cells that are hatched upward). Instead of a square frame, another annular surrounding frame such as a circular frame may be used.

  Typically, the regional section selecting means 88 detects the reference point based on the number of times of stoppage and / or the date and time of stoppage of the same past stopover place in the past stopover place information. The reference point is, for example, the home and / or work place of the user of the in-vehicle device 95.

  The receiving means 87 receives the user's preference data together with the past stopover information, and the regional section selection means 88 selects the regional section based on the past stopover information and the preference data. This specific example has been described in the above (c4), and grasps the user's preference such as movies and sports from the user's preference data, and selects a regional section including facilities such as a movie theater related to the preference. .

  FIG. 18 is a flowchart of the roadside device control method 100. The roadside device control method 100 is applied to the road-to-vehicle wireless communication system 85. In S101, the past stop location information is wirelessly received from the in-vehicle device 95 that has entered the wireless communication area. In S102, a regional section is selected based on the received past stopover information. In S103, the parking lot information included in the selected area section is wirelessly distributed to the in-vehicle device 95 in the wireless communication area.

  The processes of S101 to S103 correspond to the functions of the receiving unit 87, the regional section selecting unit 88, and the distributing unit 89 of the roadside device 86, respectively. Therefore, the specific modes described for the functions of the reception unit 87, the regional section selection unit 88, and the distribution unit 89 of the roadside device 86 can also be applied as specific modes for the processing of S101 to S103.

  The program to which the present invention is applied causes a computer to function as each unit of the roadside device 86. Another program to which the present invention is applied causes a computer to execute each step of the roadside apparatus control method 100.

  This specification discloses various ranges and levels of the invention. In addition to various devices and methods of various technical scopes and specific levels described in the present specification, the present invention has operations and effects independent of each device and each method within the scope of expansion or generalization. Extracting one or more elements, changing one or more elements within the scope of expansion or generalization, and combining one or more elements between devices and methods Includes replacements.

85: Road-to-vehicle wireless communication system, 86: Roadside device, 87: Receiving means, 88: Tertiary mesh selection means, 89: Distribution means, 95: In-vehicle device, 100: Roadside device control method.

Claims (9)

Receiving means for wirelessly receiving past stopover information from an in-vehicle device that has entered the wireless communication area,
A regional section selecting means for selecting a local section based on the received past stopover information, and a distribution means for wirelessly distributing information on the parking lot included in the selected regional section to the in-vehicle device in the wireless communication area;
A roadside device comprising:   The roadside device according to claim 2, wherein the area division selecting means detects a reference point based on past stopover information and selects an area block based on the reference point.   The roadside device according to claim 2, wherein the regional section selecting means selects a regional section based on a distance from the reference point and / or a required time.   4. The roadside apparatus according to claim 3, wherein the area division selecting means selects an area area based on a radius range of a predetermined distance range from the reference point and / or a radius range of a predetermined required time range.   The roadside device according to any one of claims 2 to 4, wherein the regional section selecting means detects the reference point based on the number of times of stoppage and / or the stop date and time of the same past stopover in the past stopover information. .   The roadside device according to any one of claims 2 to 5, wherein the reference point is a home and / or work place of a user of the in-vehicle device. The receiving means receives user preference data together with past stopover information,
The roadside device according to any one of claims 1 to 6, wherein the regional section selection unit selects a regional section based on the past stop-by place information and the preference data. A reception step of receiving the past stop-by location information wirelessly from the in-vehicle device that has entered the wireless communication area,
A regional partition selection step of selecting a regional partition based on the received past stop-off location information, and a distribution step of wirelessly distributing the parking lot information included in the selected regional partition to the in-vehicle device in the wireless communication area;
A roadside device control method comprising:   The program which makes a computer function as each means of the roadside apparatus in any one of Claims 1-7.

Images