JP2016070921A - Wireless device and management method of probe information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a wireless device and management method of probe information that can appropriately supply probe information to a plurality of service providers even when the plurality of service providers individually install a roadside machine and an erasure request occurs from respective roadside machines.SOLUTION: A wireless device is configured to comprise: a communication unit that is loaded in a vehicle to communicate with a roadside machine; information acquisition means that acquires identification information capable of identifying a service provider associated with the roadside machine from information on communication with the roadside machine; a storage unit in which probe information including information about driving of a vehicle is stored; a transmission processing unit that causes the communication unit to transmit the probe information stored in the storage unit to the roadside machine; and a data management unit that causes the storage unit to store the probe information, and when an erasure request comes from the roadside machine, implements a data operation of the probe information stored in the storage unit corresponding to an identification result of the service provider based on the identification information.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a radio apparatus for transmitting probe information and a method for managing probe information.

  In recent years, a system that accumulates travel history information and other information as probe information in a vehicle and transmits the probe information from the vehicle to the roadside device when the vehicle approaches any of the roadside devices installed in various places is put into practical use. Is being considered. The probe information sent to the roadside device is collected in the data center via the communication network and can be used for traffic jam prediction.

  Conventionally, in a system for collecting probe information, it is specified that when probe information is transmitted to a roadside device, the probe information is requested to be erased and the transmitted probe information is erased from the storage unit of the in-vehicle device. (See Patent Document 1 and Non-Patent Document 1).

JP 2011-158446 A

"Radio Beacon 5.8GHz Band Road-to-Vehicle Interface Specification", Rev.1.3B, HIDO (Highway Industrial Development Organization), 2011/11, §4.3.2.1.2 "Vehicle Information Erasure Function"

  Probe information collected from a vehicle can be used for various services. Therefore, it is expected that a plurality of service providers install roadside machines and collect probe information from vehicles.

  However, when a plurality of service providers install roadside devices separately, if the conventional provision for erasing probe information is applied, a failure occurs in collecting probe information. That is, when the vehicle approaches the roadside unit of the first service provider and transmits probe information to the roadside unit, a request for deleting the transmitted probe information is generated, and the probe information is deleted from the in-vehicle device. Therefore, when the vehicle approaches the roadside machine of the second service provider and transmits the probe information of the roadside machine after the subsequent running, the probe information sent to the first service provider last time is deleted. This part is missing.

  On the other hand, the in-vehicle device stores probe information in a memory having a limited capacity. For this reason, it is necessary to appropriately erase data based on the erase request. The probe information deletion request is issued when probe information is transmitted to the roadside device, which is the simplest and most reliable method. For this reason, it is not desired to change the issuance rule of the erasure request.

  An object of the present invention is to manage a radio apparatus and probe information that can appropriately supply probe information to a plurality of service providers even when a plurality of service providers install roadside devices separately and an erasure request is generated from each. Is to provide a method.

  A wireless device according to an aspect of the present invention is a wireless device mounted on a vehicle, and a communication unit that communicates with another wireless device and communication information between the other wireless device and the other wireless device. Information acquisition means for acquiring identification information that can identify the associated service provider, a storage unit that stores probe information including information related to the travel of the vehicle, and the probe information stored in the storage unit The transmission information is transmitted to the other wireless device by the communication unit, and the probe information is accumulated in the storage unit, and when there is a request to delete the probe information from the other wireless device, the identification information And a data management unit that performs a data operation of the probe information stored in the storage unit in accordance with the result of specifying the service provider based on the above.

  A probe information management method according to an aspect of the present invention includes a communication unit that communicates with another wireless device, and a service provider associated with the other wireless device based on communication information with the other wireless device. A method of managing probe information in a wireless device comprising: information acquisition means for acquiring identifiable identification information; and a storage unit in which probe information including information related to vehicle travel is stored. The probe information is stored in the storage unit according to the identification result of the service provider based on the identification information when there is a request to delete the probe information from the other wireless device. A configuration for performing data operation of probe information is adopted.

  According to the present invention, probe information can be appropriately supplied to a plurality of service providers even when a plurality of service providers install roadside devices separately and an erasure request is generated from each.

Block diagram showing the probe information collection system of the embodiment Illustration of probe information collection system Explanatory drawing showing an installation example of a roadside machine Sequence diagram showing an example of the flow of communication between the in-vehicle device and the roadside machine The figure which shows the relationship between roadside machine ID and the service enterpriser The figure which shows the modification of the relationship between roadside machine ID and a service provider A flowchart showing data operation processing according to the first embodiment. The figure explaining the data operation processing of Embodiment 1 First part of a flowchart showing data operation processing according to the second embodiment Second part of the flowchart showing the data operation processing of the second embodiment The figure explaining the data operation processing of Embodiment 2. A flowchart showing data operation processing according to the third embodiment. The figure explaining the data operation processing of Embodiment 3. Flowchart showing data operation processing of the fourth embodiment The figure explaining the data operation process of Embodiment 4. The block diagram which shows the probe information collection system of a modification

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

  FIG. 1 is a block diagram illustrating a probe information collection system according to an embodiment. FIG. 2 is an explanatory diagram of the probe information collection system. FIG. 3 is an explanatory view showing an installation example of a roadside machine.

  The probe information collection system according to the present embodiment includes an in-vehicle device 10, a roadside device 20, and a server 30. The in-vehicle device 10 corresponds to an example of a wireless device. The roadside machine 20 corresponds to an example of another wireless device.

  The in-vehicle device 10 is mounted on the vehicle 100 as shown in FIG. The in-vehicle device 10 includes an antenna 11, a communication unit 12, a memory 13 as a storage unit, a transmission processing unit 14, a data management unit 15, and a position acquisition unit 16. In addition, the antenna 11 does not need to have the vehicle-mounted apparatus 10 as an external attachment.

  The communication unit 12 and the antenna 11 communicate with the roadside device 20 wirelessly. Although not particularly limited, the communication unit 12 and the antenna 11 perform DSRC (Dedicated Short Range Communications) bi-directional communication with the roadside device 20 using 5.8 GHz band radio waves. The communication unit 12 sends various requests received from the roadside device 20 to the data management unit 15. The communication unit 12 transmits the probe information sent from the memory 13 to the roadside device 20.

  The memory 13 stores probe information in which travel information is arranged in time series.

  The transmission processing unit 14 transfers probe information for transmission from the memory 13 to the communication unit 12 based on a transmission command from the data management unit 15.

  The data management unit 15 performs processing for accumulating probe information in the memory 13. Specifically, when the data management unit 15 sequentially receives the current location information and the time information from the position acquisition unit 16, the data management unit 15 sequentially writes the travel information that combines the current location information and the time information in the memory 13 as probe information. In addition, when there is an uplink request from the roadside device 20, the data management unit 15 issues a transmission command to the transmission processing unit 14 so that the probe information to be transmitted is transmitted. When there is an erasure request from the roadside device 20, the data management unit 15 performs predetermined data processing on the probe information in the memory 13.

  The position acquisition unit 16 measures the current position using the current position measurement sensor, and sequentially sends information on the current location to the data management unit 15. The sensor for measuring the current position may include a GPS (Global Positioning System) receiver, a direction sensor, an acceleration sensor, a vehicle speed sensor, and the like.

  As shown in FIG. 2 and FIG. 3, the plurality of roadside machines 20 are installed over a large number of districts in the vicinity of a location where the vehicle 100 passes, such as a roadside. The plurality of roadside devices 20 are classified into a plurality in association with the service providers to which they belong, such as those belonging to the operator A and those belonging to the operator B. The roadside machine 20 associated with the three service providers is indicated by the circle mark, triangle mark, and square mark in FIG.

  The roadside machine 20 includes an antenna 21, a communication unit 22, and a roadside machine ID storage unit 23.

  The antenna 21 and the communication unit 22 communicate with the in-vehicle device 10 wirelessly. Although not particularly limited, the communication unit 22 and the antenna 21 perform DSRC (Dedicated Short Range Communications) bidirectional communication with the in-vehicle device 10 using 5.8 GHz band radio waves.

  The communication unit 22 communicates with the data center server 30 via a communication network.

  The communication unit 22 is configured to execute a predetermined communication process, and when the vehicle 100 equipped with the in-vehicle device 10 approaches the roadside device 20, the communication unit 22 is connected to the communication unit 12 of the in-vehicle device 10 for a predetermined request. Send. And if probe information is received from the vehicle-mounted apparatus 10, the communication part 22 will transmit this to the server 30. FIG.

  The storage unit 23 stores a roadside machine ID (identification information) that can uniquely identify the roadside machine 20. The roadside machine ID is read by the communication unit 22 and transmitted in various requests. For example, the roadside machine ID is included in the header information of various requests. The roadside machine ID may be transmitted from the roadside machine 20 to the in-vehicle device 10 separately from various requests such as when communication is started.

  The server 30 is a computer and collects probe information. Corresponding to a plurality of service providers, a plurality of servers 30 and a plurality of data centers are provided, and the probe information received by the roadside device 20 is collected at the data center of the service provider to which the roadside device 20 is associated. Also good.

<Communication sequence>
FIG. 4 is a sequence diagram illustrating an example of a flow of communication between the in-vehicle device and the roadside device.

  When the vehicle 100 passes in the vicinity of one roadside machine 20, the communication unit 22 of the roadside machine 20 and the communication unit 12 of the in-vehicle device 10 are automatically connected for communication.

  When the communication connection is performed, the communication unit 22 of the roadside device 20 transmits an uplink request to the communication unit 12 of the in-vehicle device 10. The uplink request is a transfer command for the accumulated probe information. When there is an uplink request, the communication unit 12 of the in-vehicle device 10 performs an uplink response including the probe information.

  When the roadside device 20 normally receives the probe information, the communication unit 22 of the roadside device 20 then transmits a memory deletion request to the communication unit 12 of the in-vehicle device 10. The memory erasure request is a command for erasing transmitted probe information. When there is a memory erasure request, the data management unit 15 of the in-vehicle device 10 performs a predetermined data operation on the probe information stored in the memory 13. After the data operation, a memory erasure response is sent from the communication unit 12 of the in-vehicle device 10 to the communication unit 22 of the roadside machine 20.

  With the above uplink request and uplink response, and memory erasure request and memory erasure response, one communication process between the in-vehicle device 10 and the roadside device 20 is completed, and then the communication connection is released.

<Roadside machine ID>
FIG. 5 is a diagram showing the relationship between the roadside device ID and the service provider.

  The roadside machine ID is identification information uniquely assigned to each roadside machine 20. Each roadside machine 20 is associated with a service provider to which the roadside machine 20 belongs. Therefore, the service provider to which the roadside machine 20 is associated can be specified from the roadside machine ID.

  The example of FIG. 5 is an example in which the roadside machine ID is set with an arbitrary value. In this case, the correspondence between the roadside machine ID and the service provider is specified by the data table T1. When the roadside machine ID as shown in FIG. 5 is applied, the in-vehicle device 10 is configured to be able to refer to the data table T1. The data management unit 15 can identify the service provider associated with the roadside device 20 from the roadside device ID with reference to the data table T1.

  FIG. 6 is a diagram showing a modification of the relationship between the roadside device ID and the service provider.

  The example of FIG. 6 is an example in which the value of the predetermined bit in the roadside machine ID is a value representing the associated service provider. In the example of FIG. 6, the upper one-digit value is associated with the service provider. When the roadside machine ID as shown in FIG. 6 is applied, the data management unit 15 of the in-vehicle device 10 does not need to prepare the data table T2, and is associated with the roadside machine 20 by receiving the roadside machine ID. Service providers can be identified.

  Hereinafter, there are three operators A to C as service operators, one roadside device 20 is associated with one service operator, and the in-vehicle device 10 has three businesses as service operators to which probe information should be supplied. A case where the persons A to C are targeted will be described.

<Data manipulation processing>
(Embodiment 1)
FIG. 7 is a flowchart illustrating data operation processing according to the first embodiment. FIG. 8 is an explanatory diagram of data operation processing according to the first embodiment.

  As illustrated in FIG. 8, the data management unit 15 sets a plurality of storage areas 13 a to 13 c that correspond one-to-one with the operators A to C in the memory 13. Then, the data management unit 15 sequentially stores new probe information in each of the plurality of storage areas 13a to 13c. Thereby, common probe information is accumulated in the plurality of storage areas 13a to 13c.

  The data management unit 15 starts the data operation process of FIG. 7 based on the uplink request of FIG.

  In step S0, the data management unit 15 acquires the roadside device ID included in the uplink request.

  In the branch processing in steps S1 to S3, the data management unit 15 determines which service provider is associated with the roadside device ID.

  Step S4 is executed when the roadside device ID is associated with the operator A. In step S4, the data management unit 15 transmits the probe information accumulated in the storage area 13a of the business operator A (denoted as “memory for business operator A” in FIG. 7) to the current location. This transmission becomes an uplink response.

  Step S5 is executed in response to the subsequent memory erase request. In step S5, the data management unit 15 deletes the probe information transmitted in step S4 from the storage area 13a of the business operator A.

  Then, the data operation process ends. Thereafter, a memory erasure response is sent to the roadside device 20, and communication with the roadside device 20 is completed.

  If the roadside device ID is associated with the business operator B in the branch processing of steps S1 to S3, the same processing is executed for the storage area 13b of the business operator B in steps S6 and S7. When the roadside device ID is associated with the business operator C, the same processing is executed on the storage area 13c of the business operator C in steps S8 and S9.

  According to this data operation processing, as shown in FIG. 8, the probe information is deleted in the storage area 13a of the business operator A associated with the roadside device 20 that has issued the deletion request. Further, the probe information is not erased in the storage areas 13b and 13c associated with the other operators B and C. Therefore, after that, even when there is an uplink request from the roadside device 20 associated with the other business operator B or business operator C, the probe is sent to the roadside device 20 associated with the other business operator B or business operator C. Information can be transmitted without omission. In addition, when the uplink request is received from the operator A next time due to the deletion of the storage area 13a, the probe information can be transmitted after the previous successful transmission, and the probe information of the operator A can be continuously transmitted. Sex is preserved.

  Further, according to this data manipulation process, the transmitted probe information is erased from the corresponding storage area in response to the erase request. Therefore, the probe information stored in the memory 13 can be appropriately deleted by only performing a data operation based on the deletion request without causing a part of the probe information to remain in the memory 13.

(Embodiment 2)
9 and 10 are flowcharts showing data operation processing according to the second embodiment. FIG. 11 is an explanatory diagram for explaining data operation processing according to the second embodiment. 11A is a state diagram of the memory at the first timing, FIG. 11B is a state diagram of the memory at the second timing, and FIG. 11C is an example of the management table.

  In the second embodiment, as shown in FIGS. 11A and 11B, the probe information is sequentially stored in one storage area of the memory 13 without being divided for each business operator A to C. Further, in the second embodiment, as shown in FIG. 11C, a management table (termination storage unit) that associates service providers with information on transmission points that transmit probe information (corresponding to termination information). MT1 is used.

  Although not particularly limited, in the second embodiment, probe information is continuously accumulated along the storage address of the memory 13. The storage address may be a physical address of the memory 13 or a logical address. The information on the transmission point in the management table MT1 employs the information on the storage address at the end of the transmitted probe information. Hereinafter, the value of the storage address is represented by the symbols “0x˜”.

  Note that any information may be adopted as the information on the transmission points in the management table MT1 as long as the new and old of the plurality of transmission points are known. As the information on the transmission point, time information on the transmission point may be adopted.

  The data management unit 15 starts the data operation process of FIG. 9 based on the uplink request of FIG.

  In step S10, the data management unit 15 acquires the roadside device ID included in the uplink request.

  In the branch processing in steps S11 to S13, the data management unit 15 determines which service provider is associated with the roadside device ID.

  Step S14 is executed when the roadside device ID is associated with the operator A. In step S14, the data management unit 15 causes the probe information from the transmission point (representing the previous transmission point) of the operator A registered in the management table MT1 to the current point to be transmitted. This transmission becomes an uplink response.

  In step S15, subsequently, the data management unit 15 updates the value of the transmission point corresponding to the operator A in the management table MT1. For example, if the probe information of the storage addresses “0xaaaa to 0xcccc” is transmitted, the termination address “0xcccc” is set as the value of the transmission point.

  If the roadside device ID is associated with the business operator B in the branch processing of steps S11 to S13, the same processing is executed in association with the business operator B in steps S16 and S17. When the roadside device ID is associated with the business operator C, the same processing is executed in association with the business operator C in steps S18 and S19.

  Step S20 is executed in response to a subsequent memory erase request. In step S20, first, the oldest transmission point information is specified in the management table MT1. The oldest transmission point information may be the information indicating the transmission point where the probe information has been sent the most in the past, or the oldest remaining transmission point information in the memory 13. . In the case of a storage address, the smallest value represents the oldest point. For example, in the case of FIGS. 11B and 11C, the oldest transmission point corresponds to the address value “0xcccc” of the operator A.

  In step S20, the information on the oldest transmission point in the management table MT1 is then compared with the information on the oldest transmission point in the accumulated probe information. As a result, if the former is newer than the latter, the process proceeds to step S21. If the former is not newer than the latter, the data operation process is terminated as it is.

  In step S21, the data management unit 15 deletes the probe information from the memory 13 from the information on the oldest transmission point of the accumulated probe information to the information on the oldest transmission point in the management table MT1. Then, the data operation process ends.

  A specific example will be described. For example, as shown in FIG. 11A, it is assumed that probe information is accumulated from the address value “0xaaaa”, and the erasure request of the operator A is generated at the address value “0xcccc”. In this case, the information on the transmission points of the operators B and C in the management table MT1 is an older (smaller) value than the address value “0xaaaa”. That is, the probe information in the address range “0xaaaa-0xcccc” has not been transmitted to the roadside devices 20 of the carriers B and C. Therefore, in response to this erasure request, NO is obtained in the branch process of step S20, and the probe information is not erased.

  As shown in FIGS. 11B and 11C, after that, probe information is accumulated up to the address value “0xdddd”, and there is an uplink request and an erasure request from the roadside device 20 of the operator B. Subsequently, It is assumed that probe information is accumulated up to the address value “0xeeee” and an uplink request and an erasure request are received from the roadside device 20 of the operator C. When the business operator C deletes the request, the oldest transmission point value in the management table MT1 is the address value “0xcccc” corresponding to the business operator A. On the other hand, the value of the oldest transmission point of the accumulated probe information is the address value “0xaaaa”. Therefore, in response to the deletion request of the address value “0xeeee”, the branch information in Step S20 is Yes, and the probe information in the address range “0xaaaa-0xcccc” that has been transmitted to all of the operators A to C is deleted. Is done.

  By such data operation processing, even if there is an uplink request from any of the plurality of roadside devices 20 respectively associated with the operators A to C, it is associated with each operator A to C. Probe information can be transmitted to the roadside device 20 without omission. Further, probe information that has been transmitted to all of the operators A to C in response to the erasure request is deleted. Therefore, a part of the probe information does not continue to remain in the memory 13, and the probe information that is sequentially accumulated can be appropriately deleted only by the data operation based on the deletion request.

  Furthermore, since the data operation processing according to the second embodiment accumulates probe information in one storage area, an effect of reducing the capacity of the storage area to be used can be obtained.

(Embodiment 3)
FIG. 12 is a flowchart illustrating data operation processing according to the third embodiment. FIG. 13 is an explanatory diagram for explaining data operation processing according to the third embodiment. 13A is a state diagram of the memory at the first timing, FIG. 13B is a management table of the first timing, FIG. 13C is a state diagram of the memory at the second timing, and FIG. ) Is a state diagram of the memory at the second timing.

  In the third embodiment, as shown in FIGS. 13A and 13C, one storage area 13 h is initially set in the memory 13 and probe information is sequentially stored. Then, a plurality of storage areas 13h and 13i are set in the memory 13 according to a predetermined condition, and the same probe information is sequentially stored therein. In the third embodiment, as shown in FIGS. 13B and 13D, a management table MT2 that dynamically associates service providers and management memories is used. Here, the management memory indicates a storage area of the memory 13 in which probe information is stored for the associated service provider.

  The data management unit 15 starts the data operation process in FIG. 12 based on the uplink request from the roadside device 20.

  In step S30, the data management unit 15 acquires the roadside device ID from the uplink request.

  In step S31, the data management unit 15 specifies the service provider associated with the roadside device 20 from the roadside device ID. The service provider specified here is referred to as “applicable provider”.

  In step S32, the data management unit 15 confirms the management table MT2, and determines whether there is a management memory shared by the corresponding business operator and other service business operators. If there are, then steps S33 and S34 are executed, and the process proceeds to step S35. If not, the process proceeds to step S35.

  Step S33 is executed when there is a management memory shared by the corresponding business operator and other service business operators. In step S33, a copy of all areas of the management memory for the corresponding business operator is created in the memory 13. For example, as shown in FIGS. 13A to 13C, a storage area “0x2aaa-0x2bbb” having the same size as the storage area “0x1aaa-0x1bbb” is prepared, and all data is copied.

  In step S34, the entry row of the management table MT2 is increased by one, and among the plurality of service providers sharing the management memory, the corresponding entry and the other providers are divided into two entry lines and To do. Then, in the entry line of the other business operator, the value of the copy destination storage area is inserted into the management memory item. For example, as shown in FIG. 13 (b) to FIG. 13 (d), the businesses A to C sharing the management memory “0x1aaa-0x1bbb” are divided and copied in correspondence with the businesses B and C. Allocated management memory “0x2aaa-0x2bbb”

  Step S35 is executed subsequent to step S34 or NO in step S32. In any case, the corresponding business operator is assigned to one management memory alone.

  In step S <b> 35, the data management unit 15 causes the management memory allocated to the corresponding business operator to transmit from the start point of the accumulated probe information to the current point. This becomes the uplink response.

  In step S36, in response to the subsequent memory erasure request, the data management unit 15 erases the transmitted probe information in the management memory assigned to the corresponding business operator. Here, the area where the deleted probe information is stored may be removed from the management table MT2. For example, the management table “0x1aaa-0x1bbb” corresponding to the operator A in FIG. 13D may be updated to “0x1ccc-0x1bbb”. Thereby, the unused area of the memory 13 can be released. Then, the data operation process ends. Thereafter, an erasure response is sent to the roadside machine 20.

  According to such a data operation process, even when the transmitted probe information is deleted in response to the erasure request, the probe information is copied and remains if there is an untransmitted service provider. Accordingly, probe information can be transmitted to the roadside device 20 associated with each service provider without omission. Further, in response to the erasure request, the probe information transmitted to all the service providers is erased without remaining. Therefore, the probe information can be appropriately deleted only by data operation based on the deletion request.

(Embodiment 4)
FIG. 14 is a flowchart illustrating data operation processing according to the fourth embodiment. FIG. 15 is an explanatory diagram for explaining data operation processing according to the fourth embodiment. 15A is a state diagram of the memory at the first timing, FIG. 15B is a management table of the first timing, FIG. 15C is a state diagram of the memory at the second timing, and FIG. ) Is a state diagram of the memory at the second timing.

  In the fourth embodiment, as shown in FIGS. 15A and 15C, one storage area 13m is set in the memory 13 and probe information is sequentially stored. Further, another storage area 13n is set in the memory 13 according to a predetermined condition, and the probe information is copied. In the fourth embodiment, as shown in FIGS. 15B and 15D, a management table MT3 that dynamically associates the management memory with the service provider is used. The management memory indicates a storage area of the memory 13 in which probe information is stored.

  The data management unit 15 starts the data operation process of FIG. 14 based on the uplink request from the roadside device 20.

  In step S40, the data management unit 15 acquires the roadside device ID from the uplink request.

  In step S41, the data management unit 15 specifies a service provider associated with the roadside device 20 from the roadside device ID. The service provider specified here is referred to as “applicable provider”.

  In step S42, it is determined whether all the entry rows in the management table MT3 have been referred to. All of the entry lines mean all entry lines existing at the start of the data operation process, and do not include entry lines added during the data operation process. If all the data have been referred to, the data operation process is terminated. If not, the process proceeds to step S43.

  In step S43, the management table MT3 is referred to one entry line in which the corresponding business is registered, and it is determined whether or not the corresponding business and the other service business are sharing one management memory. To do. The reference here is performed for the entry line existing at the start of the data operation process, and is not performed for the entry line added during the data operation process.

  Step S44 is executed when the corresponding business operator and other service businesses share one management memory. In step S44, a copy of an area in which probe information from the start end to the currently transmitted portion is stored in the memory 13 in the management memory shared by the corresponding business operator and other business operators. For example, as shown in FIGS. 15A to 15C, a storage area “0x2aaa-0x2ccc” having the same size as the storage area “0x1aaa-0x1ccc” is prepared, and the probe information in this range is copied. .

  In step S45, the entry row of the management table MT3 is increased by one. Of the management memory shared by the corresponding business operator and other business operators, two entry lines are divided into a management memory that is the copy destination and an area that excludes the copy range from the original management memory. To do. Then, in the entry row where the copy destination management memory is registered, the other business operator is registered in the service business item field. For example, as shown in FIG. 15 (b) to FIG. 15 (d), as a service provider, an entry line in which the operators A to C are registered is changed to a copy destination management memory “0x2aaa-0x2ccc” and the original It is divided into the area “0x1ccc-0x1bbb” excluding the copy range from the management memory. Then, business operators B and C are assigned as service businesses corresponding to the copy destination management memory “0x2aaa-0x2ccc”. The service providers corresponding to the other management memory “0x1ccc-0x1bbb” remain the original operators A, B, and C.

  In step S46, the probe information accumulated from the beginning to the end of the management memory registered in the entry row of the management table MT3 referred to in the previous step S43 (the entry row in which the corresponding operator is registered) is terminated. Send up to.

  In step S47, the data management unit 15 deletes the probe information transmitted in step S46.

  When both the copy in step S44 and the erase in step S47 are performed, the logical address may be logically copied and deleted, and the actual copy and deletion on the physical address may be omitted.

  After erasing step S47, the data management unit 15 returns the process to step S42, and executes the same process of steps S43 to S47 for all the entry rows in the management table MT3.

  In the above-described data operation process, there are cases where the probe information is transmitted a plurality of times intermittently. However, the transmission process in step S46 is a transmission reservation process, and a plurality of transmissions are performed at the end of the data operation process. Reservation processing may be performed collectively. In this case, the collective transmission becomes an uplink response corresponding to the uplink request.

  In the above data manipulation process, there are cases where probe information is deleted a plurality of times intermittently. However, the deletion process in step S47 is a deletion reservation process, and at the end of the data manipulation process, a memory deletion request is issued. Accordingly, a plurality of deletion reservation processes may be performed together. And it is good also as a structure where a memory deletion response is transmitted after the deletion process performed collectively.

  According to the data operation processing of the fourth embodiment, even when the transmitted probe information is deleted in response to the erasure request, if there is a portion that has not been transmitted to other service providers, the probe information remains copied. Therefore, probe information can be transmitted to the roadside equipment 20 of each service provider without omission. Further, in response to the erasure request, the probe information transmitted to all the service providers is erased without remaining. Therefore, the probe information can be appropriately deleted only by data operation based on the deletion request.

  Furthermore, according to the data operation processing of the fourth embodiment, it is possible to easily determine which range of the probe information is not sent to which service provider by each entry row of the management table MT3. For example, from the management table MT3 in FIG. 15D, the range of the management memory “0x1ccc-0x1bbb” has not yet been transmitted to the operators A to C, and the range of the management memory “0x2aaa-0x2ccc” is It can be easily read from the data structure that it has not been transmitted to the operators B and C yet.

  The embodiments of the present invention have been described above.

  The present invention is not limited to the above embodiment. FIG. 16 is a block diagram illustrating a probe information collection system according to a modification. For example, in the above-described embodiment, all of the plurality of operators A to C are service providers to which the in-vehicle device 10 should supply probe information. However, you may enable it to select the service provider which should supply probe information among several provider AC. In this case, as shown in FIG. 16, the in-vehicle device is provided with a registration unit 17 that registers a service provider to which probe information should be supplied, and the data management unit 15 refers to the registration unit 17 and should not supply the service business What is necessary is just to comprise so that the process regarding a person may be abbreviate | omitted.

  In the above embodiment, the service provider associated with the roadside machine 20 is identified from the roadside machine ID. However, apart from the roadside machine ID, the identification information of the service company is provided from the roadside machine 20 to the in-vehicle device. 10 may be specified from the identification information. In addition, any method may be used for identifying the service provider as long as it can be identified by communication with the roadside device 20.

  In the above embodiment, an example is shown in which one service provider is associated with one roadside device 20, but a plurality of service providers may be associated with one roadside device 20. .

  Moreover, in the said embodiment, the information of the driving | running | working history in which the driving | running | working position and time were arranged in time series was shown as an example as probe information. However, the probe information is not particularly limited as long as it is information related to the traveling of the vehicle, such as information in which driving operation information is arranged in time series, information on a captured image outside the vehicle, and the like.

  Further, although cases have been described with the above embodiment as examples where the present invention is configured by hardware, the present invention can also be realized by software in cooperation with hardware.

  The present invention can be applied to a wireless device in a system for collecting probe information from a vehicle.

DESCRIPTION OF SYMBOLS 10 In-vehicle apparatus 11 Antenna 12 Communication part 13 Memory (memory | storage part)
13a, 13b, 13c, 13h, 13i, 13m, 13n Storage area MT1, MT2, MT3 Management table 14 Transmission processing unit 15 Data management unit 16 Location acquisition unit 17 Registration unit 20 Roadside device 21 Antenna 22 Communication unit 23 Roadside device ID Storage unit 30 Server 100 Vehicle

Claims (8)

A wireless device mounted on a vehicle,
A communication unit that communicates with other wireless devices;
Information acquisition means for acquiring identification information that can identify a service provider associated with the other wireless device from communication information with the other wireless device;
A storage unit for storing probe information including information related to travel of the vehicle;
A transmission processing unit that causes the communication unit to transmit the probe information stored in the storage unit to the other wireless device;
The probe information is stored in the storage unit, and when there is a request to delete the probe information from the other wireless device, the probe information is stored in the storage unit according to the identification result of the service provider based on the identification information A data management unit for performing data manipulation of the probe information,
A wireless device comprising: When there is a request for erasure, the data management unit does not send the probe information to a service provider that is not associated with the other wireless device among a plurality of service providers to which the probe information is to be supplied. The probe information is erased so that the transmission part remains.
The wireless device according to claim 1. It has a registration department where service provider information is registered,
The data management unit identifies one or more service providers to which the probe information should be supplied based on the information of the registration unit;
The wireless device according to claim 2. The data management unit
A plurality of storage areas corresponding to a plurality of service providers are set in the storage unit,
Storing the common probe information in the plurality of storage areas;
Erasing the probe information from the storage area corresponding to a service provider associated with the other wireless device when the other wireless device has the erasure request;
The wireless device according to claim 1. The data management unit
Having a plurality of terminal storage units corresponding to a plurality of service providers;
When the probe information is transmitted, the termination information of the transmitted probe information is stored in the termination storage unit corresponding to the service provider associated with the other wireless device of the transmission destination,
When there is an erasure request, based on the termination information of the plurality of termination storage units, erase a portion of the probe information that has been transmitted in common to the plurality of service providers,
The wireless device according to claim 1. The data management unit
A management table that dynamically associates a plurality of service providers that supply the probe information with storage areas of the storage unit,
When there is an erasure request from the other wireless device, the management table stores the storage area in which the probe information requested to be erased is stored, and the other wireless device that does not correspond to the other wireless device that has issued the erasure request. If you are associated with a service provider of
After copying the data of the storage area where the probe information requested to be erased is stored to another storage area, the probe information is erased from the storage area of the copy source,
Updating the management table so that the association of the different service provider moves from the copy source storage area to the copy destination storage area;
The wireless device according to claim 1. The data management unit
A management table that dynamically associates a storage area of the storage unit with a plurality of service providers that supply the probe information;
When there is an erasure request from the other wireless device, the management table stores a storage area in which the probe information requested to be erased is stored, and another not corresponding to the other wireless device that has issued the erasure request When the service provider is associated,
The probe information requested to be erased is copied to another storage area, then erased from the copy source storage area,
Newly registering the different storage area and the different service provider in association with the management table;
The wireless device according to claim 1. A communication unit that communicates with another wireless device, an information acquisition unit that acquires identification information that can identify a service provider associated with the other wireless device from communication information with the other wireless device, and a vehicle In a wireless device comprising a storage unit in which probe information including information related to traveling is stored, the probe information management method,
Storing the probe information in the storage unit;
When there is a request to delete the probe information from the other wireless device, the data operation of the probe information stored in the storage unit is performed according to the identification result of the service provider based on the identification information.
How to manage probe information.

Images