Data Collection Optimization System and Method of Using the Same

Abstract

To minimize a consumption of a processing resource by a vehicle.SOLUTION: An in-vehicle data acquisition method determines whether or not a first rule of a plurality of rules overlaps with any other rule of the plurality of rules. The method further specifies overlapping data acquisition data according to a determination that the first rule overlaps with at least one of the plurality of rules. The method moreover acquires data associated with the first rule according to detection of a trigger event. The method further stores a set of overlapping data acquisition data regardless of the number of a plurality of rules that overlap with the first rule.SELECTED DRAWING: Figure 6

Description

Background Art

[0001] Computer technology used in in-vehicle systems is becoming more sophisticated. In such computer technology, in-vehicle sensors are increasingly used to collect information related to the operation of the vehicle or information related to the vehicle's surrounding environment. This information is evaluated and analyzed to help improve the operation of the vehicle, and may also be transmitted to a central server to collect information related to the vehicle's driving environment. In some cases, third parties such as application developers, insurance companies, and government agencies may inquire about information related to the operation of the vehicle or the environment around the vehicle.

Brief Description of the Drawings

[0002] Aspects of the present disclosure will be fully understood by reading the following detailed description together with the accompanying drawings. Note that the various drawings are not drawn to scale according to industry standard practices. In fact, the dimensions of various shapes may be enlarged or reduced as appropriate for clarity of explanation.

[0003]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Modes for Carrying Out the Invention

[0004] The following disclosure provides many different embodiments or examples for implementing different features of the present subject matter. Specific examples such as the components, values, operations, materials, combinations, etc. described below are for the purpose of simplifying the present disclosure. These are of course merely examples and are not intended to be limiting. Other components, values, operations, materials, combinations, etc. are also applicable. For example, in the following description, a structure in which a first shape is on a second shape may include embodiments in which the first shape and the second shape are formed to be in direct contact, and may also include embodiments in which an additional shape is formed between the first shape and the second shape such that the first shape and the second shape are not in direct contact. Further, in some examples in the present disclosure, reference numerals may be repeatedly used. Such repetitions are for the purpose of simple and clear explanation and do not indicate the relationship between the embodiments and / or configurations in which they are used.

[0005] Furthermore, spatial relationship terms such as "beneath", "below", "lower", "above", "upper" may be used herein to briefly describe the relationship of one element or shape represented in the drawings to another element or shape. The spatial relationship terms are used with the intention of encompassing different orientations in addition to the orientation of the device or operation used in the drawings. The device may be oriented in other directions (90-degree rotation or other orientations), and the spatial relationship descriptors may be interpreted similarly according to that orientation.

[0006] Data collection based on trigger events detected in one or more vehicles can be used to fulfill rules or requirements received by third-party customers. Data collection for a certain rule or requirement is performed in response to the detected trigger event. In some embodiments, data collection includes retrieving data stored in the vehicle's memory. In some embodiments, data collection includes obtaining newly detected data from one or more sensors in the vehicle. In some embodiments, data collection includes both retrieving stored data and obtaining new data.

[0007] Rules or requirements of different users may require the collection of the same or similar data. In certain embodiments, similar data includes data with overlapping collection periods from the same sensor. In certain embodiments, the periods have the same extent. In certain embodiments, one period has an extent that exceeds other periods before or after that period. In certain embodiments, similar data includes duplicates in the required sensor data. For example, in certain embodiments, a first rule requests data from a first sensor and a second sensor during a first period, and a second rule requests data from the first sensor and a third sensor during the first period. At this time, the data collection requests for the data of the first sensor during the first period overlap. Other replacements for duplicates will be understood by those skilled in the art. The rules or requirements are inquiries regarding the operation of the vehicle or information regarding the surrounding environment of the vehicle. In certain embodiments, the rule is a fixed inquiry that is required to be fulfilled while a certain trigger event occurs multiple times. In certain embodiments, the request is a one-time inquiry that is fulfilled in response to the detection of a certain trigger event or in response to the receipt of that request. In certain embodiments, the rules and requirements are used interchangeably.

[0008] Rules that require data acquisition can request multiple types of data. The more the number of rules increases, the greater the possibility that multiple rules request the same data. When multiple rules request the same type of data, the data collection process recognizes this similarity and collects and stores the data only once to avoid duplicate consumption of processing resources and duplicate consumption of storage capacity.

[0009] In certain embodiments, when multiple rules request the same type of data, the priority of the data collection process increases. The priority of the data collection process, or its coefficient, is adjusted based on the number of rules that request that data collection process. In certain embodiments, the priority of the data collection process, or its coefficient, is defined by the sum value of the priorities of the rules that request that data collection process, or other calculation formulas.

[0010] FIG. 1 is a schematic diagram of a claim search system 100 in an embodiment. The claim search system 100 includes a user interface (UI) 110. The UI 100 is configured to receive a user request for data from the vehicle 140. The claim search system 100 further includes a server 120. The server 120 is configured to receive the user request from the UI 110, send the user request to the vehicle 140, receive data from the vehicle 140, and provide the data to the user via the accessible console 150. The server 120 includes a communication unit 130 for communicating with the UI 110 and the vehicle 140. The claim search system 100 further includes an accessible console 150 configured to convey data collected from the vehicle 140 to the user.

[0011] UI110 is configured to receive input instructions from a user. In certain embodiments, the user includes a software developer. In certain embodiments, the user includes a developer of a machine learning model. In certain embodiments, the user includes an insurance company. In certain embodiments, the user includes a law enforcement agency. In certain embodiments, the user includes a market research company. UI110 provides options for the user to select the vehicle type and data type that are the subject of the data request. In certain embodiments, UI110 can generate a data request using a form regarding vehicle identification information, the requested data type, start time, and end time. In certain embodiments, the start time and end time are absolute times, such as UNIX time representing the elapsed time since the UNIX (registered trademark) epoch. In certain embodiments, the start time and end time are relative times based on the time when the data request is received by the vehicle. In certain embodiments, the start time and end time are relative times based on a trigger event. In certain embodiments, UI110 also provides the user with options to select a trigger event and a data collection period based on the trigger event. In certain embodiments, UI110 includes information regarding the type of vehicle for which data is requested. In certain embodiments, UI110 includes a vehicle ID that can uniquely identify the vehicle that is the subject of the request. For example, the vehicle ID includes the UUID (Universally Unique Identifier) format. In certain embodiments, UI110 includes a data type that can identify the source of the data that the user wishes to collect. For example, the data type includes the sensor ID of the sensor from which sensor data is collected, and the application ID of the application from which application logs are collected. In certain embodiments, the formats of the sensor ID and application ID include the UUID format. In certain embodiments, UI110 includes a drop-down menu. In certain embodiments, UI110 includes an editable area for receiving information related to the data request. In certain embodiments, UI110 provides information regarding the types of data options available to the user. In certain embodiments, the types of data options available depend on the user.For example, in one embodiment, the law enforcement agency can select more data options than the insurance company.

[0012] In one embodiment, UI110 includes a graphical user interface (GUI). In one embodiment, UI110 includes a mobile terminal connectable to server 120, such as a mobile phone. In one embodiment, UI110 includes a web interface such as a RESTful API. In one embodiment, UI110 includes a computer connectable to server 120. In one embodiment, UI110 is capable of a wireless connection to server 120. In one embodiment, UI110 is connectable to server 120 by a wired connection. Also, UI110 can provide the user with up-to-date information regarding the status of the data request. In one embodiment, UI110 provides up-to-date information regarding the status of the data request in response to an additional inquiry by the user. In one embodiment, in one embodiment, UI110 automatically provides up-to-date information regarding the status of the data request without user intervention in response to receiving the latest information from server 120. In one embodiment, the up-to-date information regarding the status serves as a trigger for UI110 to notify the user. In one embodiment, the notification includes an auditory notification or a visual notification.

[0013] In one embodiment, UI110 includes means for accepting payment from the user. In one embodiment, UI110 includes a data entry field where the user can enter payment card information. In one embodiment, UI110 includes a reader for detecting information of a payment card, such as a magnetic stripe reader, a barcode reader, an IC chip reader, or other suitable reader.

[0014] Server 120 includes a communication unit 130 configured to communicate with UI 110 and vehicle 140. The communication unit 130 includes a receiver 131 configured to receive a data request from UI 110. In certain embodiments, the receiver 131 includes a wireless receiver. In certain embodiments, the receiver 131 is configured to receive a data request via a wired connection. In certain embodiments, the receiver 131 is further configured to perform an initial process on the received data request. In certain embodiments, the received data request includes priority level information. In certain embodiments, the receiver 131 is configured to associate a priority level with the data request based on the identity of the user who registered the data request, or the fee paid by the user who registered the data request. In certain embodiments, the receiver 131 is configured to associate a request identification number (request ID) with each received data request. In certain embodiments, the server 120 is configured to restrict access to a predetermined sensor within the vehicle 140 based on the identity of the user. For example, in certain embodiments, a third-party user cannot access sensors related to the safety functions of the vehicle 140.

[0015] The communication unit 130 further includes a storage unit 132 configured to store the data requests received by the receiver 131. In some embodiments, the storage unit 132 includes a random access memory, a semiconductor memory, or other types of memory. In some embodiments, the storage unit 132 is configured to store the data requests together with the status of the data requests. In some embodiments, the status of the data requests includes pending registration (before transmission of the data request to the vehicle 140), registered (after transmission of the data request to the vehicle 140), and completed (after reception of the requested data from the vehicle 140). In some embodiments, the storage unit 132 is accessible by the user. In some embodiments, the update of the information in the storage unit 132 triggers a notification to the user associated with the information updated in the storage unit 132. In some embodiments, the storage unit 132 stores the data requests together with timestamp information indicating the time when the data requests were received. In some embodiments, the storage unit 132 stores the data requests in association with a priority level. In some embodiments, the priority level is determined based on the identity of the user. For example, in some embodiments, a law enforcement agency has a higher priority than an insurance company, and an insurance company has a higher priority than a general user such as a software developer. In some embodiments, the user can pay a fee to raise the priority level of their requests or to obtain the requested data faster. In some embodiments, the priority level of the data requests increases as the time interval from when the data requests are first stored until they are transmitted to the vehicle increases.

[0016] The communication unit 130 further includes a transmitter 133. The transmitter 133 is configured to transmit the status of the data request to the UI 110. In certain embodiments, the status of the data request is wirelessly transmitted to the UI 110. In certain embodiments, the status of the data request is transmitted to the UI 110 via a wired connection. In certain embodiments, the transmitter 133 is configured to automatically provide the latest information on the data request in response to an update in the storage unit 132. In certain embodiments, the transmitter 133 is configured to provide the latest information on the data request in response to a latest information request received from the user. In certain embodiments, the transmitter 133 is configured to automatically transmit a request ID when the data request is first stored in the storage unit 132. In certain embodiments, the status of the data request includes the priority level of the data request. In certain embodiments, the status of the data request includes the estimated time until the data request is transmitted to the vehicle 140.

[0017] The communication unit 130 further includes an inquiry queue 134 configured to store data requests according to priority for transmission to the vehicle 140. In certain embodiments, the inquiry queue 134 is integrated with the storage unit 132. In certain embodiments, the inquiry queue 134 is separated from the storage unit 132. In certain embodiments, the inquiry queue 134 is configured to read data requests from the storage unit 132 based on priority levels and timestamp information. In certain embodiments, the inquiry queue 134 is configured to sort data requests based on priority levels, and for data requests having the same priority level, sort them according to the elapsed time since they were first stored in the storage unit 132.

[0018] The communication unit 130 further includes a transmitter 135 configured to send data requests from the query queue 134 to the vehicle 140. The transmitter 135 is configured to send data requests to the vehicle 140 based on the order of data requests in the query queue 134. In certain embodiments, the data requests are sent wirelessly to the vehicle 140. In certain embodiments, the data supply is sent to the vehicle 140 via a wired connection. The data requests sent to the vehicle 140 include trigger event information, data period information regarding how long a period before and after the trigger event for which data should be collected, and sensor information indicating the types of sensors among the sensors of the vehicle 140 that should be the target of data collection. In certain embodiments, the data requests sent to the vehicle 140 include priority level information. In certain embodiments, the transmitter 135 is configured to send data requests to the vehicle 140 when the vehicle 140 sends a request to send data requests to the vehicle 140 to the server 120. In certain embodiments, the transmitter 135 is configured to send data requests to the vehicle 140 at any time as long as the communication unit 130 has not received information indicating that the vehicle 140 cannot receive new data requests when the communication unit 130 has a sufficient connection to send data requests to and from the vehicle 140. In certain embodiments, the transmitter 135 is configured to periodically send data requests to the vehicle 140 as long as the vehicle 140 is capable of receiving new data requests and the transmitter 135 has a sufficient connection to the vehicle 140. In certain embodiments, the transmitter 135 is configured to send data requests to the vehicle 140 in batches such as five data requests, 20 data requests, or some other number of data requests. In certain embodiments, the transmitter 135 is configured to request an acknowledgment of receipt of data requests from the vehicle 140. If an acknowledgment of receipt is not received from the vehicle within a predetermined period, the transmitter 135 is configured to resend the data requests. In certain embodiments, the status of the data requests stored in the storage unit 132 is updated to indicate registered to the vehicle 140 in response to the communication unit 130 receiving an acknowledgment of receipt of the data requests from the vehicle 140.

[0019] The communication unit 130 further includes a receiver 136 configured to receive a notification of the occurrence of a trigger event from the vehicle 140. In certain embodiments, the occurrence of the trigger event is the receipt of a data request. In certain embodiments, the receiver 136 is configured to receive the notification of the trigger event wirelessly. In certain embodiments, the receiver 136 is configured to receive the notification of the trigger event via a wired connection. In certain embodiments, the receiver 136 is configured to send a signal to the storage unit 132 to update the status of the data request related to the notified trigger event.

[0020] The communication unit 130 further includes a receiver 137 configured to receive data from the vehicle 140 in response to a data request transmitted by the transmitter 135. In certain embodiments, the data is segmented by the vehicle 140 into packets, which are the units when transmitting from the vehicle 140 to the server 120, and the receiver 137 receives data packets from the vehicle 140. In certain embodiments, the receiver 137 is configured to receive the data wirelessly. In certain embodiments, the receiver 137 is configured to receive the data via a wired connection. In certain embodiments, the receiver 137 is configured to send a signal to the storage unit 132 to update the status of the data request related to the received requested data. In certain embodiments, the data corresponding to one data request is received in one packet from the vehicle 140. In certain embodiments, the data corresponding to one data request is received in multiple packets from the vehicle 140. The receiver 137 passes the received data to the pre-processor 122.

[0021] Server 120 includes a pre-processor 122 configured to receive data from receiver 137 and perform pre-processing on the data to generate collected data. In certain embodiments, the pre-processing includes reconstructing data from a plurality of packets and aggregating the data into data corresponding to a data request. In certain embodiments, the pre-processing includes deserializing and structuring from a byte array when the data is received. In certain embodiments, the pre-processing includes decompressing data that was compressed prior to transmission from vehicle 140. In certain embodiments, the pre-processing includes error correction by an error correction code (ECC) such as a Reed-Solomon (RS) code, Bose-Chaudhuri-Hocquenghem (BCH) code, Low-Density Parity-Check (LDPC) code, etc. In certain embodiments, the pre-processing includes removing outliers and smoothing the data to reduce the risk of reporting inaccurate data to the user. In certain embodiments, the pre-processing includes associating data received from receiver 137 with data request ID information, priority level information, or other appropriate information. In certain embodiments, the data is pre-processed such that it is provided to the user in a format that does not require special knowledge or equipment to understand and read easily.

[0022] Server 120 further includes a data storage 126 configured to store the collection data generated by the pre-processor 122. In some embodiments, the data storage 126 is integrated with the storage unit 132. In some embodiments, the data storage 126 is separated from the storage unit 132. In some embodiments, the data storage 126 includes a solid state drive (SSD), random access memory, or other suitable memory. In some embodiments, the data storage 126 is accessible by a user using, for example, the UI 110 or the accessible console 150. In some embodiments, the data storage 126 is configured to notify the user that data related to a data request has become available. In some embodiments, the notification includes a notification to the user. In some embodiments, the notification includes an auditory or visual notification. In some embodiments, the data storage 126 is configured to automatically display a notification about the availability of the collection data on the UI 110 or the accessible console 150. In some embodiments, the data storage 126 is accessible by a user using the accessible console 150 without the user registering a data request. In some embodiments, the data in the data storage 126 is searchable by the user via the accessible console 150. In some embodiments, the collection data is visualized on the accessible console 150.

[0023] The request search system 100 further includes a vehicle 140. The vehicle 140 includes a plurality of sensors that detect both the internal state of the vehicle 140 and the external environment around the vehicle 140. In some embodiments, the sensors include cameras, LiDAR (Light Distance And Ranging) sensors, RADAR (Radio Distance And Ranging) sensors, SONAR (Sound Navigation And Ranging) sensors, acceleration sensors, steering wheel position, vehicle speed sensors, or other suitable sensors. The vehicle 140 can receive data requests wirelessly or via a wired connection.

[0024] In one embodiment, vehicle 140 is configured to assign a data request ID to the received data request in response to receiving the data request. The data request is processed without depending on the original system or program of the data request. In other embodiments, instead of vehicle 140, communication unit 130 assigns a data request ID, and the data request ID is included in the data request that communication unit 130 sends to vehicle 140. By making the data request independent of the original system or program of the data request, vehicle 140 can receive and process data requests from a wider range of different users and systems. Vehicle 140 includes a processor that processes the data request and determines which type of data from sensors such as those available in vehicle 140 can satisfy the data request. Vehicle 140 further includes a memory that stores data from the sensors. In one embodiment, the processor accesses the memory to determine whether the stored data can satisfy the data request. Vehicle 140 can further transmit the data determined to satisfy the data request to server 120 wirelessly or via a wired connection. In one embodiment, the processor is configured to satisfy the received data requests in order of priority based on the priority level of the received data requests. In one embodiment, vehicle 140 is configured to preferentially transmit data to the server based on the priority level of the received data requests.

[0025] In one embodiment, the memory and processor of vehicle 140 are configured to store and execute software applications of the ECUs (Electronic Control Units) within vehicle 140. In one embodiment, data requests are generated by software applications stored in the ECUs. In one embodiment, data requests are generated in response to trigger events such as hard acceleration, hard braking, acquisition of sensor data including a specific object or a specific scene predetermined by the software application, stoppage (crash) of the operation of the software application, detection of an abnormality in the software application, or detection of other appropriate events. In one embodiment, vehicle 140 is configured to generate a notification to a maintenance administrator of the software application, such as a user, in response to detection of a trigger event associated with the software application. In one embodiment, the notification is transmitted directly to the user wirelessly or via a wired connection, such as via UI110. In one embodiment, the notification is transmitted to the user via server 120 wirelessly or via a wired connection. In one embodiment, the notification is configured to automatically display the notification on UI110 without user intervention.

[0026] The request search system 100 further includes an accessible console 150. The accessible console 150 enables a user to access the collected data stored in the data storage 126. In one embodiment, the accessible console 150 is integrated with the UI110. In one embodiment, the accessible console 150 is separated from the UI110. In one embodiment, the accessible console 150 includes another server separated from the server 120. In one embodiment, the accessible console 150 automatically receives the collected data related to the data request from the user when the data storage 126 receives the collected data. In one embodiment, the accessible console 150 enables the user to search the data storage 126 and determine which of the collected data stored in the data storage 126 is useful to the user even if the user has not registered a data request.

[0027] By using the request search system 100, a user can obtain information from one or more vehicles 140 in an easy-to-understand format without the need for a special device for data requests or reading. Since the request search system 100 can prioritize data requests, law enforcement agencies or other users can surely obtain data, and users who pay fees can quickly obtain data. Since the request search system 100 is thus flexible, it becomes more useful for a wide range of users.

[0028] FIG. 2 is a diagram showing GUIs (Graphical User Interfaces) 200 and 250 in the request search system of the embodiment. In one embodiment, the GUI 200 can be used as the UI 110 (FIG. 1) of the request search system 100. In one embodiment, the GUI 200 can be used to generate a data request received by the receiver 131 (FIG. 1). The GUI 200 includes a plurality of information types 210 that identify the types of information that the GUI 200 can receive from the user. The GUI 200 further includes a plurality of fields 220 configured to receive information related to the corresponding information type 210 of the GUI 200. The GUI 200 includes a registration button 230 configured to register a data request with a server, such as server 120 (FIG. 1), based on the information in the field 220. Those skilled in the art will recognize that the names and numbers of the plurality of information types 210 are merely examples, and different numbers and types of information are also within the scope of the present disclosure.

[0029] In one embodiment, column 220 includes fields for the user to input a vehicle ID, data type, start time, and end time. In one embodiment, column 220 further includes a field for the user to input a priority level of the data request. In one embodiment, GUI 200 further includes information regarding how the user can raise the priority level of the data request, such as the posting of fees associated with each applicable priority level. In one embodiment, the GUI includes column 220 where the user can input login information for identity verification. In one embodiment, GUI 200 is configured to display the priority level of the user who subsequently received the login information. In one embodiment, GUI 200 further includes column 220 for receiving payment information regarding the fees for determining the priority of the data request.

[0030] GUI 250 is configured to be displayed to the user after the user selects the registration button 230 of GUI 200. In one embodiment, GUI 250 can be used as GUI 110 (FIG. 1) in the request search system 100. GUI 250 includes information indicating that a data request has been received. GUI 250 includes a request ID label 260 and a request ID field 270. The information to be displayed in the request ID field 270 is received from a server, such as server 120 (FIG. 1), after the server receives and stores the data request. In one embodiment, GUI 250 includes information about the vehicle ID. In one embodiment, GUI 250 includes information related to the priority level of the data request. In one embodiment, GUI 250 includes information regarding the status of the data request, such as registration pending, registered, completed, etc. In one embodiment, GUI 250 includes information related to the estimated time until the data request is registered with a vehicle, such as vehicle 140 (FIG. 1). In one embodiment, GUI 250 is automatically displayed in response to receiving inquiry ID information from the server. In one embodiment, GUI 250 is displayed in response to the user's registration of the latest information request for the uploaded data request.

[0031] FIG. 3 is a diagram of a data structure 300 of a request search instruction 310 in an embodiment. In one embodiment, the request search instruction 310 is sent from the server 120 to the vehicle 140 (FIG. 1). The request search instruction 310 includes information related to the type of data that the data request requests from the vehicle, for example, the vehicle 140 (FIG. 1).

[0032] The request search command 310 includes a transfer priority parameter 311 indicating the priority level of the data request. The request search command 310 further includes a log level parameter 312 indicating the type of data (if any) to be obtained from other applications of the vehicle. For example, in one embodiment, the request search command 310 obtains data from an object detection application. The log level parameter 312 determines which type of data, such as error level or critical issue level, to obtain from other applications. In certain embodiments, the log level parameter 312 is omitted from the request search command 310, or the log level parameter 312 remains in a null state. The request search command 310 further includes a collection time range parameter 313 indicating the time range in which data should be collected before and after the trigger event. The time range corresponds to the start time and end time input by the user into the GUI 200 (Figure 2). The request search command 310 further includes a URL (Uniform Resource Locator) endpoint parameter 314 indicating the destination of the data collected in response to the data request. The request search command 310 further includes a frequency parameter 315 indicating how frequently data should be sampled assuming that data is sampled within the time range indicated by the collection time range parameter 313. For example, if the time t of the event is 100 seconds, the time range has a start time of -1 second and an end time of 2 seconds, and the frequency is 10 Hz (100 millisecond period), data at times t of 99.0 seconds, 99.1 seconds, 99.2 seconds, …, 101.9 seconds, 102.0 seconds is collected by the request search command. The request search command 310 further includes a log ID parameter 316 indicating the type of sensors and / or applications available for collecting the data requested by the data request. In certain embodiments, a unique ID (e.g., UUID (Universally Unique Identifier)) is pre-assigned to all sensors and applications, and the unique ID for which the user requests data collection is specified by the log ID parameter 316. The request search command 310 further includes a requester ID parameter 317 indicating the identity of the user who created the data request.The request search command 310 further includes an event ID parameter 318 indicating a trigger event associated with the data request. The request search command 310 further includes an allocation ID parameter 319 indicating to what extent resources of a vehicle, such as vehicle 140 (FIG. 1), are to be allocated to satisfy the data request. Those skilled in the art will also understand that the request search command 310 does not always include all the parameters shown in FIG. 3. For example, in certain embodiments, the allocation ID parameter 319 is omitted.

[0033] FIG. 4 is a block diagram of a request search system 400 of an embodiment. In certain embodiments, the request search system 400 is part of the request search system 100 (FIG. 1). In certain embodiments, the request search system 400 can be used in cooperation with the request search system 100 (FIG. 1). In certain embodiments, the request search system 400 is separable from the request search system 100 (FIG. 1).

[0034] The request search system 400 includes a detection vehicle system 410 configured to obtain information of or around a vehicle. The detection vehicle system 410 obtains information of the vehicle and its surroundings and transmits the information to a server. The request search system 400 is configured to receive the information, encode the information, and disseminate the information to the user terminal 460.

[0035] The detection vehicle system 410 includes an ECU 420 configured to receive data from a sensor 414, a GPS (Global Positioning System) 416, and a map 418. The ECU 420 includes a situation detection unit 422, a data identification unit 432, a log collection unit 434, and a log transmission unit 436. The situation detection unit 422 includes a vehicle control monitor 424, an object detection unit 426, and a scene detection unit 428.

[0036] In one embodiment, the ECU 420 further includes a localization unit configured to receive data from the GPS 416 and the map 418 to determine the position and orientation of the vehicle and the state of the vehicle relative to detected and / or known objects and / or road positions. The orientation is the direction of the vehicle relative to a reference point such as a lane. In one embodiment, the position of the vehicle is represented together with a position vector of the vehicle. The orientation and the state of the vehicle are represented by the speed and the traveling direction of the vehicle. In one embodiment, the orientation and the state of the vehicle are represented together with a velocity vector, an acceleration vector, and a jerk vector of the vehicle. In one embodiment, the position vector, the velocity vector, the acceleration vector, and the jerk vector include an angular vector. In one embodiment, the state of the vehicle is represented together with whether the engine or motor of the vehicle is operating or not.

[0037] The sensor 414 is configured to capture information about the surrounding environment of the vehicle, such as an image. In one embodiment, the sensor 414 includes a visible light camera and an infrared light camera. In one embodiment, the sensor 414 is replaced by, or further includes, a LiDAR sensor, a RADAR sensor, a SONAR sensor, or other suitable sensors. In one embodiment, the sensor 414 includes additional cameras at other positions of the vehicle. For example, in one embodiment, the additional camera is located at a lateral position of the vehicle to more widely detect the environment on the left and right of the target vehicle. Since the occupants of the vehicle can look out through the side windows of the vehicle, the detection accuracy of objects or situations around the vehicle can be improved by using an additional camera that more widely detects the surrounding environment of the vehicle. For example, in one embodiment, the additional camera is located at a rear position of the vehicle to more widely detect the environment behind the vehicle. With this information, information about the object can be captured. In one embodiment, the data from the sensor 414 includes a time stamp or other metadata to enable synchronization of the data from the sensor 414 with the data from other devices.

[0038] The GPS 416 is configured to determine the position of the vehicle. By knowing the position of the target vehicle, an object or situation can be associated with the determined position on the map 418.

[0039] The map 418 includes information related to road lanes and known objects along the road lanes. In one embodiment, the map 418 can be used in conjunction with the GPS 416 to determine the position and direction of travel of the vehicle. In one embodiment, the map 418 is received from an external device such as the server 440. In one embodiment, the map 418 is periodically updated based on information from the sensor 414 and / or the GPS 416. In one embodiment, the map 418 is periodically updated based on information received from an external device. In one embodiment, the map 418 is generated from sensor data by a SLAM (Simultaneous Localization And Mapping) algorithm. By including the map 418, it is possible to determine whether an object is a known object. By including the map 418 with known objects, the detection accuracy of new objects can be improved.

[0040] The situation detection unit 422 is configured to generate information regarding the operation of the vehicle and the in-vehicle system. The situation detection unit 422 can collect information from in-vehicle devices such as the sensor 414, the braking system, the acceleration system, and other suitable devices. Using such information, the situation detection unit 422 can determine the operation of the vehicle. In one embodiment, the situation detection unit 422 is further configured to monitor the operation of the software and network within the vehicle. For example, in one embodiment, the situation detection unit 422 is configured to receive information regarding a "crash" of software or an application within the vehicle. In one embodiment, the situation detection unit 422 is configured to collect information regarding the storage capacity of the storage device within the vehicle. In one embodiment, the situation detection unit 422 is configured to receive information regarding the processing capacity of the processor within the vehicle.

[0041] The vehicle control monitor 424 is configured to receive sensor data and a control log regarding the current operation of the vehicle. In one embodiment, the sensor data includes information regarding vehicle speed, acceleration, jerk, braking, steering, pitch, roll, yaw, hazard lamp blinking, horn, or other suitable information. The vehicle control monitor 424 is configured to determine whether any of the received sensor data indicates satisfaction of a requirement fulfillment criterion, such as satisfaction of a trigger event.

[0042] The object detection unit 426 is configured to receive sensor data from the sensor 414 and determine whether there is a foreign object in the lane. In one embodiment, the object detection unit 426 is further configured to determine whether there is an object along or near the lane. In one embodiment, the sensor data from the sensor 414 includes an image, and the object detection unit 426 is configured to perform image recognition on the received image, for example, using a trained neural network, to detect a foreign object. In one embodiment, the object detection unit 426 is configured to compare the identified object with information from the GPS 416 and the map 418 so as to be able to determine the type of the identified object. In one embodiment, the object detection unit 426 is configured to identify an object as, for example, a tire, a vehicle part, an animal, a hole, a traffic sign, an emergency vehicle, a vehicle with hazard lamps on, or other suitable objects.

[0043] The scene detection unit 428 is configured to receive sensor data from the sensor 414 and determine whether a scene that satisfies the conditions for fulfilling the request exists in the vehicle's surrounding environment. In certain embodiments, the scene detection unit 428 is configured to determine that a vehicle accident has occurred based on detecting that two or more vehicles are in contact with each other or that the vehicle is surrounded by a plurality of falling objects. In certain embodiments, the scene detection unit 428 is configured to determine that construction work is being performed when a plurality of construction vehicles are detected in extremely close proximity. In certain embodiments, the scene detection unit 428 is configured to determine that the vehicle has stopped on the shoulder based on detecting that the vehicle is near the roadway and is not moving or is moving at a significantly slower speed than other vehicles. In certain embodiments, the scene detection unit 428 is configured to determine the content of the vehicle's surrounding scene using, for example, image recognition using a trained neural network.

[0044] In certain embodiments, each of the object detection unit 426 and the scene detection unit 428 operates throughout the operation of the vehicle, for example, while the vehicle's engine or motor is operating. In certain embodiments, at least one of the object detection unit 426 and the scene detection unit 428 operates in response to a determination by the vehicle control monitor 424 of a predetermined state, such as the detection of a trigger event.

[0045] In certain embodiments, the ECU 420 further includes a duplicate filter that can identify duplicate data requests based on one or more rules stored in the detected vehicle system 410.

[0046] The data identification unit 432 is configured to receive a determination that a request has been fulfilled or that a trigger event has been detected. The data identification unit 432 analyzes the received information and is configured to determine which sensor data from the sensor 414 should be collected based on the received data. For example, in one embodiment, the data identification unit 432 is configured to determine that image data from the front camera among the sensors 414 should be captured when an abnormal steering operation by the driver is detected. Further, the data identification unit 432 is configured to determine the time interval for which data should be collected from the determined sensors based on the time of the detected situation. In one embodiment, the data identification unit 432 is configured to determine the sensor 414 to be the target of data collection based on the instructions in the request received from the user.

[0047] In one embodiment, the data identification unit 432 is configured to determine the area of the received sensor data related to the detected situation. In one embodiment, the area of the received sensor data is identified based on object recognition performed by the object detection unit 426 or the scene detection unit 428. In one embodiment, the data identification unit 432 is configured to trim the image received from the sensor or delete unnecessary data from the sensor data if the sensor data is not an image in order to reduce the amount of information in the abnormal situation log. In one embodiment, the data identification unit 432 is configured to delete personal information such as license plates and human faces from the sensor data.

[0048] The log collection unit 434 is configured to receive data from the data identification unit 432. In certain embodiments, the log collection unit 434 is configured to receive data directly from the sensor 414, the GPS 416, or the situation detection unit 422 based on the information provided by the data identification unit 432. Further, the log collection unit 434 determines which of the information, such as position information from, for example, the GPS 416 or the map 418, image information from the sensor 414, trimmed or reduced information from the data identification unit 432, timestamp information regarding the time when an object or a scene was detected, or other suitable information, can be used to identify the type and location of the object.

[0049] The log collection unit 434 generates log data based on the received and correlated data, such as trimmed images and position data. Further, the log collection unit 434 associates timestamp information with the log data to facilitate synchronization of the collected data and sorting according to priority at the server 440. In certain embodiments, the log collection unit 434 generates log data that further includes world coordinates associated with the trimmed image. In certain embodiments, the log collection unit 434 generates log data that further includes map positions associated with the trimmed image. In certain embodiments, the log collection unit 434 generates log data that includes additional information that contributes to a more accurate determination of the object or scene.

[0050] Although the above relates to the generation of log data based on image data from the sensor 414, those skilled in the art will understand that the log collection unit 434 is not limited to only generating image-based log data. In certain embodiments, the log collection unit 434 is configured to generate log data based on information from other sensors mounted on the vehicle, such as RADAR, LiDAR, or other suitable sensors. In certain embodiments, the log collection unit 434 is configured to generate log data based further on information received from smart glasses when a passenger is using them.

[0051] The log transmission unit 436 is configured to receive log data from the log collection unit 434 and transmit it to the server 440. In certain embodiments, the log transmission unit 436 is configured to transmit log data wirelessly. In certain embodiments, the log transmission unit 436 is configured to transmit log data via a wired connection. In certain embodiments, the log transmission unit 436 is configured to directly transmit log data to the user terminal 460. In certain embodiments, the log transmission unit 436 transmits log data to a portable device accessible by the user. At this time, the portable device is configured to transmit the log data to the server 440. In certain embodiments, the log transmission unit 436 is configured to transmit log data to the portable device using Bluetooth (registered trademark) or other suitable wireless technology. In certain embodiments, the ECU 420 is configured to determine whether the data transfer rate from the portable device to the server 440 is higher than the transfer rate from the log transmission unit 436 to the server 440. If it is determined that the data transfer rate from the portable device to the server 440 is higher, the log transmission unit 436 is configured to transmit the log data to the portable terminal so that the log data is transmitted to the server 440 from the portable terminal. If it is determined that the data transfer rate from the portable device to the server 440 is not higher, the log transmission unit 436 is configured to directly transmit the log data from the detection vehicle system 410 to the server 440 without transferring the log data to the portable terminal.

[0052] In one embodiment, the detection vehicle system 410 further includes a memory configured to store sensor data from sensors mounted on the vehicle. In one embodiment, the memory is further configured to store information associated with objects or scenes detected in the past. In one embodiment, when an object or scene that matches a past object or scene is detected, the data identification unit 432 is configured to provide a result based on the matching object or scene. In one embodiment, the detection vehicle system 410 is further configured to determine whether the detection vehicle has received information related to an object or scene that matches the determined object or scene from the situation detection unit 422. In one embodiment, when it is determined that the detection vehicle has already received information related to the determined object or scene, the detection vehicle system 410 is configured to suppress the transmission of log data to the server 440. By preventing duplicate information from being sent to the server 440, the data transmitted to the server 440 can be reduced, and the power consumption of the detection vehicle system 410 can be reduced. In one embodiment, the storage of past requests is referred to as a cache. Those skilled in the art will understand that the cache uses hardware or software to store data so that the data can be provided more quickly for future requests.

[0053] The server 440 includes a log data receiving unit 442 configured to receive log data from the log transmission unit 436. In one embodiment, the log data receiving unit 442 is configured to receive log data from a mobile device. The server 440 further includes a log encoding unit 444 that encodes the log data. The server 440 further includes a log transfer unit 446 that transfers the encoded log data to the user terminal 160. The server 440 further includes a request / rule receiving unit 448 configured to receive requests or rules from the user terminal 460.

[0054] The log data receiving unit 442 is configured to receive log data from the log transmitting unit 436. In certain embodiments, the log data receiving unit 442 is configured to receive log data from a mobile device. In certain embodiments, the log data receiving unit 442 is configured to receive log data wirelessly. In certain embodiments, the log data receiving unit 442 is configured to receive log data via a wired connection. In certain embodiments, the log data receiving unit 442 is configured to attach a time stamp of the time when the log data was received to the log data.

[0055] The log encoding unit 444 is configured to encode the received log data according to a predetermined encoding protocol. By encoding the log data according to the predetermined encoding protocol, when the user terminal 460 uses the log data, the user terminal 460 can surely decode the log data. In certain embodiments, the log encoding unit 444 is configured to perform compression of the log data, image encoding, generation of thumbnail images, or other appropriate encoding protocols. In certain embodiments, the log encoding unit 444 is configured to perform encryption of the log data. In certain embodiments, the log encoding unit 444 is configured to perform super-resolution processing in order to make the data easier for the user to view. Those skilled in the art will understand that super-resolution processing is a process of obtaining a high-resolution image from a low-resolution image. By improving the resolution of the log data, false detection or detection omission can be reduced.

[0056] In certain embodiments, the server 440 further includes a database for storing the received log data. In certain embodiments, the log data is stored in the database before or after encoding by the log encoding unit 444. In certain embodiments, the log data is stored in a priority queue of the database. In certain embodiments, the priority queue is determined based on an object or scene, for example, the time when a trigger event was detected, the time when the log data receiving unit 442 received the log data, the type of the object or scene, the identity of the driver of the detected vehicle, or other appropriate priority criteria.

[0057] The log transfer unit 446 is configured to receive the encoded log data from the log encoding unit 444. The log transfer unit 446 is configured to transmit the encoded log data to the user terminal 460. In certain embodiments, the log transfer unit 446 is configured to transmit the encoded log data to a portable device accessible by the user. In certain embodiments, the log transfer unit 446 is configured to wirelessly transmit the encoded log data. In certain embodiments, the log transfer unit 446 is configured to transmit the encoded log data via a wired connection. In certain embodiments, the log transfer unit 446 is configured to transmit the encoded log data together with the encoded protocol information. By transmitting the encoded protocol information of the encoded log data, the portable device or the user terminal 460 can accurately decode the encoded log data so that it can be used at the user terminal 460.

[0058] The request / rule receiving unit 448 is configured to receive new or updated rules or requests about data from the user. In certain embodiments, the request / rule receiving unit 448 is configured to wirelessly receive new or updated rules or requests. In certain embodiments, the request / rule receiving unit 448 is configured to receive new or updated rules or requests via a wired connection. In certain embodiments, the request / rule receiving unit 448 is configured to receive new or updated rules or requests from the UI 110 (FIG. 1).

[0059] In certain embodiments, the server 440 is configured to receive location information from a plurality of vehicles. In certain embodiments, the server 440 is configured to receive navigation information from a plurality of vehicles. In certain embodiments, the log transfer unit 446 is configured to limit the transmission destination of the encoded log data to vehicles within a predetermined distance from the detected trigger event.

[0060] In one embodiment, the server 440 is configured to transmit only the log data associated with the newly detected trigger event. That is, if a trigger event has been reported by the server 440, that trigger event is not reported again. By not repeatedly reporting trigger events, the server 440 can reduce the duplicate data received by the user terminal.

[0061] The user terminal 460 is a user terminal accessible to the user associated with the fulfilled request. In one embodiment, the user terminal 460 includes a GUI. In one embodiment, the user terminal 460 is configured to automatically generate a notification in response to receiving data from the server 440. In one embodiment, the notification includes an auditory or visual notification.

[0062] Those skilled in the art will understand that changes to the request search system 400 are within the scope of this disclosure. For example, in one embodiment, the detection vehicle system 410 can directly transmit log data to the user terminal 460 via a network such as a wireless network. In one embodiment, the mobile device of the occupant of the detected vehicle can directly transmit log data to the user terminal 460 via a network such as a wireless network.

[0063] By automatically identifying and disseminating data detected in the environment inside or around the vehicle in relation to the satisfaction of rules or requests, the user can structure the operation of applications or software used by a vehicle processing system such as the ECU 420. In one embodiment, the user can receive object information related to an event such as an accident.

[0064] FIG. 5 is a flowchart of a method 500 executed by the claim search system of the embodiment. In one embodiment, method 500 is executed by claim search system 100 (FIG. 1) or claim search system 400 (FIG. 4). In one embodiment, method 500 is executed by a system 700 (FIG. 7) in which the claim search system is implemented. In one embodiment, method 500 is executed by a system other than claim search system 100 (FIG. 1), claim search system 400, or system 700 (FIG. 7). The following description relates to the processing of rules or requests received from a vehicle.

[0065] In operation 505, sensor data is collected. The sensor data is collected by one or more sensors connectable to the vehicle. In one embodiment, the sensor data includes vehicle control parameters. In one embodiment, the sensor data includes information about the vehicle's surrounding environment. In one embodiment, the sensor data includes data from sensor 414 (FIG. 4) and / or other sensors of the vehicle.

[0066] In operation 510, the sensor data is processed. The sensor data is processed to identify one or more trigger events related to one or more rules stored in the vehicle's memory. In one embodiment, the sensor data is processed by a situation detection unit 422 (FIG. 4). In one embodiment, the sensor data is processed based on preprocessing instructions related to one or more rules stored in the vehicle's memory. In one embodiment, the sensor data is processed to remove privacy concerns from the sensor data. In one embodiment, the sensor data is processed to compress the sensor data for storage in the vehicle's memory.

[0067] In operation 515, a determination is made as to whether there is duplication in the rules. Duplication in the rules means that at least a part of the data collection required by the first rule coincides with at least a part of the data collection required by the second rule. For example, in one embodiment, the first rule requires the collection of data from the first sensor for a period from 5 seconds before the detected trigger event to 10 seconds after the detected trigger event, and the second rule requires the collection of data from the time the trigger event is detected to 15 seconds after the detected trigger event. These two rules have duplication in data collection for the data from the first sensor during the 10 seconds after the trigger event is detected. This duplication in data collection is determined as rule duplication in operation 515. In another example, the first rule requires the collection of data from the first sensor for 10 seconds after the trigger event is detected and data from the second sensor for 15 seconds after the trigger event is detected, and the second rule requires the collection of data from the second sensor for 10 seconds after the trigger event is detected and data from the third sensor for 5 seconds after the trigger event is detected. These two rules have duplication for the data from the second sensor during the 10 seconds after the trigger event is detected. This duplication in data collection is determined as rule duplication in operation 515. It will be understood by those skilled in the art that replacing the sensors and data collection periods with others also corresponds to the duplicate rules according to the embodiments of this specification.

[0068] The above example assumes that the trigger events for the first rule and the second rule are the same. In certain embodiments, the trigger event of the first rule is related to, but not exactly the same as, the trigger event of the second rule. For example, in one embodiment, the first trigger event of the first rule is the detection of a traffic accident involving a vehicle, and the second trigger event of the second rule is the detection of a sudden change in vehicle speed. It will be understood by those skilled in the art that while a sudden change in speed can occur in a traffic accident, a sudden change in speed does not necessarily accompany a traffic accident. In certain embodiments, operation 515 is configured to analyze the trigger events of the rules to determine whether the trigger events are related. In certain embodiments, the analysis is performed by a neural network either prior to transmitting the rule to the vehicle or after transmitting the rule to the vehicle. In certain embodiments, the analysis is performed based on a correlation database of trigger events stored in a server, such as server 440 (FIG. 4), or a vehicle system, such as detection vehicle system 410 (FIG. 4). In certain embodiments, the relationship between the trigger events is provided by the user at the time of rule generation, for example, using UI110 (FIG. 1). In response to determining that the trigger events are related, operation 515 treats the two rules as having the same trigger event when determining whether the rules overlap. This does not mean that the first rule is to be used regularly even when the first trigger event is not satisfied when the second trigger event is satisfied. Instead, this simply means that for adjusting the priority of the rules or for more efficiently using memory in the vehicle, the rules are considered to overlap.

[0069] The above example includes two examples of rules to be judged for rule duplication. Those skilled in the art will recognize that there can be more than two duplicate rules. In one embodiment, all the rules stored in the database in the vehicle are analyzed to determine whether there are no rules that duplicate at least one other rule. In one embodiment, the rule duplication determination is performed prior to sending the rules to the vehicle, and the sending of new rules to the vehicle includes information regarding duplication with the rules already stored in the vehicle. By analyzing rule duplication prior to sending the rules to the vehicle, the consumption of the vehicle's processing resources can be minimized.

[0070] By determining rule duplication, method 500 can improve the efficiency of data collection, data processing, and data storage consumption. By storing only one data set that at least partially satisfies multiple rules, the memory in the vehicle can be used more efficiently. Further, by performing data processing, such as data deletion from a privacy perspective, on one set of collected data, the processing load on the vehicle can be reduced. As a result, the vehicle can satisfy rules faster and, by improving the efficiency of the resources in the vehicle, can process more rules.

[0071] In response to a determination that there is rule duplication, method 500 proceeds to operation 517. In response to a determination that there is no rule duplication, method 500 proceeds to operation 520.

[0072] In operation 517, the priority of each of the overlapping rules is adjusted for data collection. In one embodiment, the priority of a rule is determined based on at least one of the type of the rule such as safety equipment, entertainment, the identity of the user such as a police, an insurance company, an application author, the fee paid by the user, or other suitable criteria. Operation 517 further adjusts the priority of a rule that overlaps with at least one other rule. Operation 517 adjusts the priority of all rules so as to increase the priority of the overlapping rules. By increasing the priority of the overlapping rules in operation 517, method 500 can satisfy as many rules as possible. For example, when there are insufficient resources to apply all the rules associated with the detected trigger event, the rules with higher priority are preferably applied prior to the rules with lower priority. By increasing the priority of the overlapping rules and enabling multiple rules to be satisfied without consuming resources such as the processing capacity and storage capacity of the vehicle as much as possible, more rules can be applied. By applying the overlapping rules prior to other rules, the consumed resources are reduced compared to the original assumption, and method 500 may be able to apply all the rules.

[0073] In one embodiment, the priority of the overlap is increased according to a set amount such as a certain priority level regardless of the number of overlapping rules in the group. In one embodiment, the larger the number of overlapping rules within the group, the higher the priority of the rules. For example, in one embodiment, when less than 5 rules overlap, the priority level of these rules is increased by 1, but when 5 or more rules overlap, the priority level of these rules is increased by 2. In one embodiment, the increase in the priority level is associated with the amount of resource consumption associated with the overlapping rules. For example, in one embodiment, the larger the amount of resources saved by common data collection or common data, the greater the amount of adjustment of the priority.

[0074] In one embodiment, the priority level of all overlapping rules is set to the highest priority level in the overlapping group. In one embodiment, operation 517 adjusts the priorities so that the overlapping rules maintain their individual priority levels.

[0075] In one embodiment, the priority of a rule is set based on a unique level determined by a developer of a vehicle system such as the detection vehicle system 410 (FIG. 4). For example, in one embodiment, the priority levels are set to low, medium, high, important, and essential. Those skilled in the art will understand that the names of the individual priority levels are merely examples and that this description is not limited to these levels. In one embodiment, the priority of a rule is a score in the range of, for example, 1 to 100. In one embodiment, the score of the priority level is determined based on the factors described above with respect to the consideration of priorities. Operation 517 may adjust the priority of a rule based on any priority algorithm used by the vehicle system.

[0076] In one embodiment, if the developer of the vehicle system does not request adjustment of the rule priority based on rule overlap, operation 517 is omitted. In such an embodiment, method 500 proceeds from operation 515 to operation 520 regardless of the determination in operation 515.

[0077] In operation 520, a determination is made as to which sensor information should be collected based on the rules. The rules stored in the vehicle's memory include information related to the type of sensor data and the period during which the sensor data is to be collected. In one embodiment, the collected data is trimmed or processed to reduce or eliminate unnecessary data.

[0078] In operation 525, the collected data is stored. In certain embodiments, the collected data is stored in memory. In certain embodiments, the collected data is stored in association with timestamp information regarding when the data was collected or when the trigger event occurred. In certain embodiments, the collected data is stored using the log collection unit 434 (FIG. 4).

[0079] In operation 530, the stored data is transmitted to the server 440. In certain embodiments, the stored data is transmitted wirelessly. In certain embodiments, the stored data is transmitted via a wired connection. In certain embodiments, the stored data is transmitted using the log transmission unit 436 (FIG. 4).

[0080] In operation 535, the transmitted data is received by the server 440. In certain embodiments, the data is received by the log data reception unit 442 (FIG. 4). In certain embodiments, the received data is stored in the memory of the server 440. In certain embodiments, the received data is stored in the priority queue of the server 440.

[0081] In operation 540, the received data is encoded. In certain embodiments, the received data is encoded according to a predetermined coding protocol. In certain embodiments, the received data is encoded according to criteria determined by rules associated with the received data. In certain embodiments, the received data is encoded according to the priority of the data in the priority queue. In certain embodiments, the encoded data is stored in the memory of the server 440. In certain embodiments, the encoded data is stored in the memory in the priority queue of the server 440. In certain embodiments, operation 540 is omitted and the received data is not encoded.

[0082] In operation 545, the encoded data is transmitted to the user terminal 460. In some embodiments, the encoded data is transmitted wirelessly. In some embodiments, the encoded data is transmitted via a wired connection. In some embodiments, the encoded data is transmitted according to the priority of the encoded data in the priority queue. In some embodiments, the encoded data is transmitted by the log transfer unit 446 (FIG. 4).

[0083] In operation 550, the encoded data is received. In some embodiments, the encoded data is received by the user terminal 460 (FIG. 4). In some embodiments, the received data is stored in the memory of the user terminal 460 (FIG. 4) prior to decoding. In some embodiments, the received data is stored in the priority queue of the user terminal 460 (FIG. 4).

[0084] In operation 555, the data is decoded. In some embodiments, the data is decoded according to a predetermined decoding protocol. In some embodiments, the data is decoded based on the coding protocol information received together with the data from the server 440. In some embodiments, the data is decoded according to the type of the received data. In some embodiments, the data is decoded based on the priority in the priority queue. In some embodiments, the decoded data is stored in the memory of the user terminal 460 (FIG. 4). In some embodiments, the decoded data is stored in the priority queue in the memory of the user terminal 460 (FIG. 4).

[0085] In operation 560, the decoded data is visualized. By visualizing the decoded data, a visual representation of the data is provided. In certain embodiments, the visual representation includes an image of the data from the vehicle. In certain embodiments, the visual representation includes icons representing the data from the vehicle. In certain embodiments, the visual representation includes a table of the data. In certain embodiments, the visual representation includes text such as JSON text. In certain embodiments, the visual representation includes the location on a map of the detected trigger event. In certain embodiments, the decoded data is visualized using the user terminal 460 (FIG. 4).

[0086] In operation 565, the user receives a notification about the visualized data. In certain embodiments, the user receives the notification using a UI, such as UI 110 (FIG. 1). In certain embodiments, the user receives the notification using a portable device accessible by a passenger. In certain embodiments, the notification includes an auditory or visual notification. In certain embodiments, the notification is configured to automatically generate a notification on a portable device accessible by the user.

[0087] Those skilled in the art will understand that modifications to method 500 are within the scope of this specification. In certain embodiments, at least one additional operation is included in method 500. For example, in certain embodiments, method 500 further includes receiving confirmation of a trigger event from a vehicle passenger. In certain embodiments, at least one operation is removed from method 500. For example, in certain embodiments, operation 540 is removed and the data is supplied to the user terminal 460 without being encoded. In certain embodiments, the order of operations in method 500 is changed. For example, in certain embodiments, operation 525 is performed prior to the determination as to whether a trigger event has been detected, in order to store sensor data. Those skilled in the art will understand that other modifications to method 500 are within the scope of this specification.

[0088] FIG. 6 is a flowchart of a data collection method 600 using an in-vehicle system in an embodiment. In certain embodiments, method 600 is executed as operations 515 and 520 (FIG. 5) of method 500. In certain embodiments, method 600 is executed by a situation detection unit 422 (FIG. 4). In certain embodiments, method 600 is executed using a request search system 100 (FIG. 1) or a request search system 400 (FIG. 4). In certain embodiments, method 600 is executed using a system other than the request search system 100 (FIG. 1) or the request search system 400 (FIG. 4). Method 600 can be used to determine whether rules overlap and whether to adjust the priority of overlapping rules.

[0089] In operation 605, data collection for rules stored in the in-vehicle memory is inspected. In certain embodiments, operation 605 is omitted and data collection for rules is inspected prior to transmission of the rules to the vehicle. Inspecting data collection for rules stored in the in-vehicle memory includes, for each rule, determining what rule collection is instructed in response to detection of a trigger event associated with that rule. The inspection includes identifying the type of sensor data, such as image data, vehicle operation data, vehicle position data, and the collection period of the sensor data. The collection period of the sensor data includes the time interval from the start point of data collection to the end point of data collection. In certain embodiments, the collection period includes the time prior to detection of the trigger event. In certain embodiments, data may be read from an in-vehicle temporary storage unit to collect data obtained prior to detection of the trigger event that initiates the temporary storage data request.

[0090] In operation 610, data collection information is integrated in association with the corresponding rule. By integrating data collection information in association with the corresponding rule, it becomes possible to identify the same or similar data collection requests for determining which rules overlap. In certain embodiments, the integrated data collection information is stored in the in-vehicle memory. In certain embodiments, operation 610 is integrated with operation 615.

[0091] In operation 615, a determination is made as to which rules overlap. Overlap within a rule means that at least a portion of the data collection required by the first rule coincides with at least a portion of the data collection required by the second rule. Examples of rule overlap have been described above and will not be repeated here for the sake of brevity. It will be understood by those skilled in the art that replacing the sensors and data collection periods with others would still result in overlapping rules according to the embodiments herein.

[0092] In one embodiment, the trigger event of the first rule is related to the trigger event of the second rule, but is not strictly equivalent as described above. In response to the determination that the trigger events are related, operation 615 treats the two rules as having the same trigger event when determining whether the rules overlap. This does not mean that the first rule is to be used regularly even when the first trigger event is not satisfied when the second trigger event is satisfied. Rather, this simply means that for the purpose of adjusting the rule priorities or for more efficiently using memory in the vehicle, the rules are considered to overlap.

[0093] The example above includes two rules for which overlap is determined. It will be recognized by those skilled in the art that there can be more than two overlapping rules. In one embodiment, all the rules stored in the database within the vehicle are analyzed to determine whether there are any rules that overlap with at least one other rule. In one embodiment, the rule overlap determination is made prior to transmitting the rules to the vehicle, and the transmission of new rules to the vehicle includes information regarding overlap with the rules already stored in the vehicle. By analyzing rule overlap prior to sending the rules to the vehicle, consumption of the vehicle's processing resources can be minimized.

[0094] By determining rule duplication, method 600 can improve the efficiency of data collection, data processing, and consumption of the data storage unit. By storing only one data set that at least partially satisfies multiple rules, the memory in the vehicle can be used more efficiently. Further, by performing data processing on one set of collected data, such as data deletion from a privacy perspective, the processing load on the vehicle can be reduced. As a result, the vehicle can satisfy rules faster and, by improving the efficiency of resources in the vehicle, can process more rules.

[0095] In response to determining that there is rule duplication, method 600 proceeds to operation 620. In response to determining that there is no rule duplication, method 600 proceeds to operation 625.

[0096] In operation 620, the priority of each of the duplicate rules is adjusted for data collection. In one embodiment, the rule priority is determined based on at least one of rule types such as safety equipment, entertainment, the identity of the user such as a police officer, an insurance company, an application author, the fee paid by the user, or other suitable criteria. Operation 625 further adjusts the priority of a rule that overlaps with at least one other rule. Operation 625 adjusts the priority of all rules so as to increase the priority of the overlapping rules. By increasing the priority of the overlapping rules in operation 625, method 600 can satisfy as many rules as possible. For example, when there are insufficient resources to apply all rules associated with a detected trigger event, rules with a high priority are applied preferably before rules with a low priority. By increasing the priority of overlapping rules and enabling multiple rules to be satisfied without consuming resources such as the processing capacity and storage capacity of the vehicle as much as possible, more rules can be applied. By applying overlapping rules before other rules, the consumed resources are reduced compared to what was originally assumed, and method 600 may be able to apply all rules.

[0097] Examples of rule priorities and examples of increasing rule priorities have been described above and will not be repeated here for the sake of brevity. Those skilled in the art will understand that replacing rule priorities and increasing rule priorities with others are also included in the embodiments of this specification. In certain embodiments, if the developer of the vehicle system does not require adjustment of rule priorities based on rule duplication, operation 625 is omitted. In such embodiments, method 600 proceeds from operation 615 to operation 625 regardless of the determination in operation 615.

[0098] In operation 625, one or more trigger events are detected. The trigger events are detected based on a comparison between data collected by sensors mounted on the vehicle and information stored in the vehicle's memory regarding the rules. That is, the rules include conditions for collecting data, that is, information indicating trigger events. In certain embodiments, the data is collected by sensor 414 (FIG. 4).

[0099] In operation 630, data is collected based on the rule priority levels associated with the trigger events detected in operation 625. Rules with higher priorities are applied preferably ahead of rules with lower priorities. In certain embodiments including operation 620, updated priority levels are used in determining the rules applied in operation 630. In certain embodiments, operation 630 applies multiple rules. In certain embodiments, operation 630 applies one rule. The collected data is stored at least temporarily in the memory within the vehicle. In certain embodiments, the collected data is encoded, personal information is deleted, or other appropriate processing is performed prior to storage in the memory within the vehicle.

[0100] In operation 630, data collection for duplicate rules is limited to generating one copy of the data for which the rules are determined to be duplicates. For example, if the first rule requests data from the first sensor for 10 seconds from the detection of a trigger event and the second rule requests data from the second sensor for 5 seconds from the detection of the trigger event, operation 630 saves only one copy of the data from the first sensor in the time interval of 5 seconds from the detection of the trigger event. By saving one copy for duplicate data collection requests, the vehicle can improve the efficiency of data collection or processing and can more reliably satisfy more data.

[0101] In operation 635, the collected data is transmitted to a server, such as server 440 (FIG. 4), or a user terminal, such as user terminal 460 (FIG. 4). In certain embodiments, the saved data is transmitted wirelessly. In certain embodiments, the saved data is transmitted via a wired connection. In certain embodiments, the saved data is transmitted using the log transmitter 436 (FIG. 4).

[0102] In operation 640, a new rule is received by the vehicle. The new rule is received after the integration of the data collection associated with the corresponding rule. In certain embodiments, the new rule is received wirelessly. In certain embodiments, the new rule is received via a wired connection.

[0103] In operation 645, data collection for the new rule is determined. In certain embodiments, data collection for the new rule is determined in a manner similar to that described above for operation 605. In certain embodiments, data collection for the new rule is determined based on a comparison between the new rule and the integrated data collection request. Following operation 645, method 600 proceeds to operation 610, where the integrated data collection request is updated based on the new rule.

[0104] One of ordinary skill in the art will understand that modifications to method 600 are within the scope of this specification. In certain embodiments, at least one additional operation is included in method 600. For example, in certain embodiments, method 600 further includes sending a notification to a user terminal, such as user terminal 460 (FIG. 4). In certain embodiments, at least one operation is removed from method 600. For example, in certain embodiments, operation 620 is removed if no adjustment of the priority level is required. In certain embodiments, the order of operations in method 600 is changed. For example, in certain embodiments, operation 615 is executed concurrently with operation 610. One of ordinary skill in the art will understand that other modifications to method 600 are within the scope of this specification.

[0105] FIG. 7 is a schematic diagram of a system 700 in which an embodiment of the claim search system is implemented. System 700 includes a processor 702 that is hardware, and a non-transitory computer-readable storage medium 704 that encodes computer program code 706, such as a set of executable instructions, for example including this. The computer-readable storage medium 704 also encodes instructions 707 for connecting to an external device. The processor 702 is electrically coupled to the computer-readable storage medium 704 via a bus 708. Also, the processor 702 is electrically coupled to an I / O interface 710 by the bus 708. Also, a network interface 712 is electrically coupled to the processor 702 via the bus 708. The network interface 712 is connected to a network 714, whereby the processor 702 and the computer-readable storage medium 704 can be connected to external elements via the network 714. To enable system 700 to be used to perform some or all of the operations described by claim search system 100 (FIG. 1), claim search system 400 (FIG. 4), method 500 (FIG. 5), or method 600 (FIG. 6), the processor 702 is configured to execute the computer program code 706 encoded in the computer-readable storage medium 704.

[0106] In one embodiment, the processor 702 is a CPU (Central Processing Unit), a multiprocessor, a distributed processing system, an ASIC (Application Specific Integrated Circuit), and / or a suitable processing unit.

[0107] In one embodiment, the computer-readable storage medium 704 is an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, the computer-readable storage medium 704 includes semiconductor or solid state memory, magnetic tape, removable computer diskettes, RAM (Random Access Memory), ROM (Read-Only Memory), rigid magnetic disks, and / or optical disks. In one embodiment using optical disks, the computer-readable storage medium 704 includes CD-ROM (Compact Disk - Read Only Memory), CD-R / W (Compact Disk - Read / Write), and / or DVD (Digital Versatile Disk).

[0108] In one embodiment, the storage medium 704 stores computer program code 706 configured to cause the system 700 to perform some or all of the operations described in the request search system 100 (FIG. 1), the request search system 400 (FIG. 4), the method 500 (FIG. 5), or the method 600 (FIG. 6). In one embodiment, the storage medium 704 stores information necessary for the execution of some or all of the operations described in the request search system 100 (FIG. 1), the request search system 400 (FIG. 4), the method 500 (FIG. 5), or the method 600 (FIG. 6), and information generated in the execution of some or all of the operations described in the request search system 100 (FIG. 1), the request search system 400 (FIG. 4), the method 500 (FIG. 5), or the method 600 (FIG. 6), such as sensor data parameters 716, rule parameters 718, collected data parameters 720, priority data parameters 722, and / or a set of executable instructions for performing some or all of the operations described in the request search system 100 (FIG. 1), the request search system 400 (FIG. 4), the method 500 (FIG. 5), or the method 600 (FIG. 6).

[0109] The system 700 includes an I / O interface 710. The I / O interface 710 is coupled to an external circuit. In one embodiment, the I / O interface 710 includes a keyboard, keypad, mouse, trackball, trackpad, and / or cursor direction keys for communicating information and commands to the processor 702.

[0110] System 700 also includes a network interface 712 coupled to processor 702. The network interface 712 enables System 700 to communicate with a network 714 to which one or more other computer systems are connected. The network interface 712 includes a wireless network interface such as Bluetooth, Wi-Fi, WiMAX, GPRS, or WCDMA (registered trademark), or a wired network interface such as Ethernet, USB, or IEEE 1394. In certain embodiments, some or all of the operations described in request search system 100 (FIG. 1), request search system 400 (FIG. 4), method 500 (FIG. 5), or method 600 (FIG. 6) are implemented on two or more systems 700, and information such as priority levels, query IDs, query statuses, and query data is exchanged between different systems 700 via network 714.

[0111] [Appendix 1]

[0112] The in-vehicle data collection method includes determining whether a first rule among a plurality of rules overlaps with any of the other rules among the plurality of rules. The method further includes identifying duplicate data collection data in response to a determination that the first rule overlaps with at least one of the other rules among the plurality of rules. The method further includes collecting data related to the first rule in response to detection of a trigger event. The method further includes storing a set of duplicate data collection data regardless of the number of rules that overlap with the first rule.

[0113] [Appendix 2]

[0114] The method according to Appendix 1, wherein the determination of whether the first rule overlaps with at least one of the other rules among the plurality of rules includes identifying data collection information of the first rule, the data collection information including a first sensor and a first period, and determining that the first rule overlaps with at least one of the other rules among the plurality of rules in response to a determination that at least one of the plurality of rules includes a period that at least partially matches the first sensor and the first period.

[0115] [Appendix 3]

[0116] The first period is a period set based on a trigger event, by the method described in Appendix 2.

[0117] [Appendix 4]

[0118] Further including adjusting the priority level of the first rule in response to a determination that the first rule overlaps with at least one of the other multiple rules, and the collection of data related to the first rule includes the collection of data associated with the first rule based on the priority level of the first rule, by the method described in any one of Appendices 1-3.

[0119] [Appendix 5]

[0120] The adjustment of the priority of the first rule includes the adjustment of the priority of the first rule based on the number of multiple rules that overlap with the first rule, by the method described in Appendix 4.

[0121] [Appendix 6]

[0122] Further including adjusting the priority level of each of the multiple rules that overlap with the first rule in response to a determination that the first rule overlaps with at least one of the other multiple rules, and the collection of data associated with each of the multiple rules that overlap with the first rule includes the collection of data associated with the corresponding rule based on the priority level of the corresponding rule among the multiple rules that overlap with the first rule, by the method described in any one of Appendices 1-5.

[0123] [Appendix 7]

[0124] The adjustment of the priority level of each of the multiple rules that overlap with the first rule includes making the priority level of the first rule the same as the priority level of each of the multiple rules that overlap with the first rule, by the method described in Appendix 6.

[0125] [Appendix 8]

[0126] The in-vehicle data collection system includes a non-transitory computer-readable medium configured to store instructions and a processor connected to the non-transitory computer-readable medium. The processor is configured to execute instructions for determining whether a first rule among a plurality of rules overlaps with any other of the plurality of rules. The processor is configured to execute instructions for identifying duplicate data collection data in response to a determination that the first rule overlaps with at least one other of the plurality of rules. The processor is configured to execute instructions for collecting data related to the first rule in response to the detection of a trigger event. The processor is configured to execute instructions for storing a set of duplicate data collection data in the non-transitory computer-readable medium regardless of the number of rules that overlap with the first rule.

[0127] [Appendix 9]

[0128] The processor further executes instructions for identifying data collection information of the first rule, the data collection information including a first sensor and a first period, and determining that the first rule overlaps with at least one other of the plurality of rules in response to a determination that at least one of the plurality of rules includes a period that at least partially matches the first sensor and the first period, for the system according to Appendix 8.

[0129] [Appendix 10]

[0130] The system according to Appendix 9, wherein the first period is a period set based on a trigger event.

[0131] [Appendix 11]

[0132] The processor is further configured to execute instructions for adjusting the priority level of the first rule in response to a determination that the first rule overlaps with at least one of the other plurality of rules, and the collection of data related to the first rule includes the collection of data associated with the first rule based on the priority level of the first rule, the system according to any one of Appendices 8-10.

[0133] [Appendix 12]

[0134] The processor is further configured to execute instructions for adjusting the priority of the first rule based on the number of rules that overlap with the first rule, the system according to Appendix 11.

[0135] [Appendix 13]

[0136] The processor is further configured to execute instructions for adjusting the priority level of each of the plurality of rules that overlap with the first rule in response to a determination that the first rule overlaps with at least one of the other plurality of rules, and the collection of data associated with each of the plurality of rules that overlap with the first rule includes the collection of data associated with the corresponding rule based on the priority level of the corresponding rule among the plurality of rules that overlap with the first rule, the system according to any one of Appendices 8-12.

[0137] [Appendix 14]

[0138] The processor is further configured to execute instructions for making the priority level of the first rule the same as the priority level of each of the plurality of rules that overlap with the first rule, the system according to Appendix 13.

[0139] [Appendix 15]

[0140] A non-transitory computer-readable medium configured to store instructions for causing a processor to perform an operation including determining whether a first rule among a plurality of rules overlaps with any other of the plurality of rules. The operation further includes identifying duplicate data collection data in response to a determination that the first rule overlaps with at least one other of the plurality of rules. The operation further includes collecting data related to the first rule in response to detection of a trigger event. The operation further includes storing a set of the duplicate data collection data regardless of the number of rules that overlap with the first rule.

[0141] [Appendix 16]

[0142] The determination of whether the first rule overlaps with at least one other of the plurality of rules includes identifying data collection information of the first rule, the data collection information including a first sensor and a first period, and determining that the first rule overlaps with at least one other of the plurality of rules in response to a determination that at least one of the plurality of rules includes a period that at least partially matches the first sensor and the first period. The non-transitory computer-readable medium according to Appendix 15 includes this.

[0143] [Appendix 17]

[0144] The instructions further cause the processor to perform an operation of adjusting a priority level of the first rule in response to a determination that the first rule overlaps with at least one other of the plurality of rules, and the collection of data related to the first rule includes the collection of data associated with the first rule based on the priority level of the first rule. The non-transitory computer-readable medium according to Appendix 15 or 16 includes this.

[0145] [Appendix 18]

[0146] The adjustment of the priority of the first rule includes the adjustment of the priority of the first rule based on the number of rules that overlap with the first rule. The non-transitory computer-readable medium according to Appendix 17 includes this.

[0147] [Appendix 19]

[0148] The command further causes the processor to execute an operation that adjusts the priority level of each of a plurality of rules that overlap with the first rule in response to a determination that the first rule overlaps with at least one of the other plurality of rules, and the collection of data associated with each of the plurality of rules that overlap with the first rule includes the collection of data associated with the corresponding rule based on the priority level of the corresponding rule among the plurality of rules that overlap with the first rule, a non-transitory computer-readable medium described in any one of Appendices 15-18.

[0149] [Appendix 20]

[0150] The adjustment of the priority level of each of the plurality of rules that overlap with the first rule includes making the priority level of the first rule the same as the priority level of each of the plurality of rules that overlap with the first rule, a non-transitory computer-readable medium described in Appendix 19.

[0151] The above outlines the features of several embodiments so that those skilled in the art can better understand the aspects of the present disclosure. Those skilled in the art should understand that the present disclosure can be easily utilized for the purpose of designing or improving other processes or structures to achieve the same objectives and / or the same advantages as the embodiments introduced herein. Also, those skilled in the art should recognize that such equivalent components do not depart from the spirit and scope of the present disclosure and that changes, substitutions, and modifications can be made to the present disclosure without departing from the spirit and scope of the present disclosure.

Claims

Claim 1. A first rule among a plurality of rules that are set in response to a trigger event detected in a vehicle and that each specify collected data to be collected from among data of at least one sensor mounted on the vehicle determines whether it overlaps with at least one other of the plurality of rules by including overlapping collected data in which the first collected data specified by the first rule overlaps with other collected data specified by at least one other of the plurality of rules. When it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to detection of the trigger event, collecting the first collected data and storing a set of the overlapping collected data. The determination as to whether the first rule overlaps with at least one other of the plurality of rules is made in response to a determination that the first collected data includes data of a first sensor in a first period and the other collected data includes data of the first sensor in a period that at least partially coincides with the first period, and the first rule is determined to overlap with at least one other of the plurality of rules. In-vehicle data collection method. Claim 2. The method according to claim 1, wherein the first period is a period set based on the trigger event. Claim 3. A first rule among a plurality of rules that are set in response to a trigger event detected in a vehicle and that each specify collected data to be collected from among data of at least one sensor mounted on the vehicle determines whether it overlaps with at least one other of the plurality of rules by including overlapping collected data in which the first collected data specified by the first rule overlaps with other collected data specified by at least one other of the plurality of rules. When it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to detection of the trigger event, collecting the first collected data and storing a set of the overlapping collected data. Including adjusting a priority level of the first rule in response to a determination that the first rule overlaps with at least one other of the plurality of rules. The collection of the first collected data includes collection of data associated with the first rule based on the priority level of the first rule. In-vehicle data collection method. Claim 4. The adjustment of the priority level of the first rule according to claim 3 includes the adjustment of the priority level of the first rule based on the number of the plurality of rules overlapping with the first rule.

5. The method further includes adjusting the priority level of each of the plurality of rules overlapping with the first rule in response to a determination that the first rule overlaps with at least one other of the plurality of rules, and the collection of data associated with each of the plurality of rules overlapping with the first rule includes the collection of data associated with a corresponding rule based on the priority level of the corresponding rule among the plurality of rules overlapping with the first rule. The method according to claim 3.

6. The adjustment of the priority level of each of the plurality of rules overlapping with the first rule according to claim 5 includes making the priority level of the first rule the same as the priority level of each of the plurality of rules overlapping with the first rule.

7. A non-transitory computer-readable medium configured to store instructions, A processor connected to the non-transitory computer-readable medium, The processor, Among a plurality of rules that are set corresponding to a trigger event detected in a vehicle and respectively identify collected data to be collected among data of at least one sensor mounted on the vehicle, a first rule determines whether the first rule overlaps with at least one other of the plurality of rules by including duplicate collected data in which first collected data specified by the first rule overlaps with other collected data specified by at least one other of the plurality of rules. When it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to the detection of the trigger event, the processor is configured to execute instructions for collecting the first collected data and storing a set of the duplicate collected data in a non-transitory computer-readable medium. The determination as to whether the first rule overlaps with at least one other of the plurality of rules includes determining that the first rule overlaps with at least one other of the plurality of rules in response to a determination that the first collected data includes data of a first sensor in a first period and the other collected data includes data of the first sensor in a period that at least partially coincides with the first period. In-vehicle data collection system.

8. The system according to claim 7, wherein the first period is a period set based on the trigger event.

9. A non-transitory computer-readable medium configured to store instructions, and a processor connected to the non-transitory computer-readable medium, wherein the processor is set in response to a trigger event detected in the vehicle, and determines whether a first rule among a plurality of rules that respectively identify collected data to be collected from among the data of at least one sensor mounted on the vehicle overlaps with at least one other of the plurality of rules by including duplicate collected data in which the first collected data identified by the first rule overlaps with other collected data identified by at least one other of the plurality of rules, when it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to the detection of the trigger event, collects the first collected data and stores a set of the duplicate collected data in a non-transitory computer-readable medium, and is configured to execute instructions for adjusting a priority level of the first rule in response to a determination that the first rule overlaps with at least one other of the plurality of rules, wherein the collection of the first collected data includes the collection of data associated with the first rule based on the priority level of the first rule, In-vehicle data collection system.

10. The system according to claim 9, wherein the processor is further configured to execute instructions for adjusting the priority level of the first rule based on the number of the plurality of rules that overlap with the first rule.

11. The processor is further configured to execute instructions for adjusting the priority level of each of the plurality of rules that overlap with the first rule in response to a determination that the first rule overlaps with at least one other of the plurality of rules, and the collection of data associated with each of the plurality of rules that overlap with the first rule includes the collection of data associated with a corresponding rule based on the priority level of the corresponding rule among the plurality of rules that overlap with the first rule, The system according to claim 9.

12. ​ The system according to claim 11, wherein the processor is further configured to execute instructions for making the priority level of the first rule the same as the priority level of each of the plurality of rules overlapping with the first rule.

13. Among a plurality of rules that are set corresponding to a trigger event detected in a vehicle and that respectively specify collected data to be collected among data of at least one sensor mounted on the vehicle, a first rule determines whether or not it overlaps with at least one other of the plurality of rules by including overlapping collected data in which first collected data specified by the first rule overlaps with other collected data specified by at least one other of the plurality of rules. When it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to detection of the trigger event, the first collected data is collected and a set of the overlapping collected data is saved. configured to save instructions for causing a processor to execute operations including this. The determination as to whether or not the first rule overlaps with at least one other of the plurality of rules includes determining that the first rule overlaps with at least one other of the plurality of rules in response to a determination that the first collected data includes data of a first sensor in a first period and the other collected data includes data of the first sensor in a period that at least partially matches the first period. Non-transitory computer-readable medium.

14. Among a plurality of rules that are set corresponding to a trigger event detected in a vehicle and that respectively specify collected data to be collected among data of at least one sensor mounted on the vehicle, a first rule determines whether or not it overlaps with at least one other of the plurality of rules by including overlapping collected data in which first collected data specified by the first rule overlaps with other collected data specified by at least one other of the plurality of rules. When it is determined that the first rule overlaps with at least one other of the plurality of rules, in response to detection of the trigger event, the first collected data is collected and a set of the overlapping collected data is saved. In response to a determination that the first rule overlaps with at least one other of the plurality of rules, adjust the priority level of the first rule. configured to store instructions for causing a processor to execute operations including collecting the first collected data including collecting data associated with the first rule based on the priority level of the first rule, a non-transitory computer-readable medium. **Claim 15** The non-transitory computer-readable medium according to claim 14, wherein adjusting the priority level of the first rule includes adjusting the priority level of the first rule based on the number of the plurality of rules overlapping with the first rule. **Claim 16** The instructions further include causing the processor to execute operations of adjusting the priority level of each of the plurality of rules overlapping with the first rule in response to a determination that the first rule overlaps with at least one of the other plurality of rules, and collecting data associated with each of the plurality of rules overlapping with the first rule includes collecting data associated with a corresponding rule based on the priority level of the corresponding rule among the plurality of rules overlapping with the first rule. The non-transitory computer-readable medium according to claim 14. **Claim 17** The non-transitory computer-readable medium according to claim 16, wherein adjusting the priority level of each of the plurality of rules overlapping with the first rule includes making the priority level of the first rule the same as the priority level of each of the plurality of rules overlapping with the first rule.

Images