JP7333293B2 - Data delivery system and data delivery method - Google Patents

Description

The present invention relates to a data distribution system and a data distribution method, and is applied to a data distribution system and a data distribution method for vehicles that distribute necessary data owned by a plurality of companies to a distribution server that distributes data to vehicles. It is suitable for

Currently, as services using the IoT (Internet of Things) permeate the world, the technological progress of "connected services" for vehicles that connect automobiles to the Internet is particularly rapid. When automobile manufacturers provide connected services, the data that can be input to applications are OEMs (Original Equipment Manufacturers) and probe data collected from vehicles (map data, location information, presence or absence of failures in vehicle parts, mileage, mileage, etc.). speed, etc.) is currently being used.

In the future, it is expected that connected services for vehicles will further diversify and user needs will become more complex. It is thought that there will also be a scene in which new services are provided. In order to realize these usage scenes in the future, it will be necessary to develop a technology to process the data collected from third-party organizations into the appropriate data required by automobile manufacturers and provide it.

As a conventional technology that can be utilized when realizing such a usage scene, for example, Patent Document 1 describes a filter condition file and 1 A data distribution system is disclosed that has a mechanism for distributing data associated with a pair to a vehicle.

JP 2019-165444 A

According to the technique disclosed in Patent Literature 1, in realizing the above-described usage scene, it is possible to control the distribution of data to vehicles by utilizing the mechanism of filter conditions. However, in order to realize the above-mentioned usage scenes in connected services for vehicles, there is a mechanism to acquire multiple data from a third party in response to a vehicle data request, and to aggregate the acquired multiple data into one data. A mechanism for processing the data into the data format requested by the vehicle is required, and Patent Document 1 does not disclose these mechanisms.

The present invention has been made in consideration of the above points. Data that can be obtained by acquiring a plurality of data provided by a third party, processed into data in any format required by automobile manufacturers, and distributed. It is intended to propose a distribution system and a data distribution method.

In order to solve this problem, in the present invention, data is acquired from one or more third parties and distributed to a distribution server capable of distributing data to each of a plurality of vehicles that receive connected services for vehicles. In a data distribution system, when use of an application installed in the vehicle is requested to the distribution server from any one of the plurality of vehicles, one or more data required when using the application receiving a data collection request for target data from the distribution server, and first requirement information indicating requirements related to a third-party organization as an acquisition source for each of the target data to be acquired in the data collection request; , a second requirement information indicating requirements related to a data format required when distributing the target data to the distribution server; A data acquisition unit that acquires each of the target data set as the above from the third party organization that is the acquisition source in the first requirement information, and for each of the target data acquired by the data acquisition unit, a data processing unit for converting a data format based on the second requirement information; and transmitting the target data after the data format conversion by the data processing unit to the distribution server. a data format indicated in the second requirement information is a data format required for the target data when the application is used in the vehicle, and is an arbitrary data format required by the manufacturer of the vehicle. A data delivery system is provided that is a data format of

In addition, in order to solve such a problem, in the present invention, data is acquired from one or more third parties to a distribution server capable of distributing data to each of a plurality of vehicles that receive connected services for vehicles. A data distribution method using a data distribution system for distribution, wherein when one of the plurality of vehicles requests the distribution server to use an application installed in the vehicle, the data distribution system A third party that receives a data collection request for one or more target data required when using the application from the distribution server, and selects each of the target data to be acquired by the data collection request as the acquisition destination. a command receiving step for receiving first requirement information indicating requirements relating to an institution and second requirement information indicating requirements relating to a data format required when distributing the target data to the distribution server; a data acquisition step in which the distribution system acquires each of the target data to be acquired in the data collection request received in the command receiving step from the third-party organization specified as the acquisition destination in the first requirement information; a data processing step in which the data delivery system converts a data format of each of the target data acquired in the data acquisition step based on the second requirement information; and the data delivery. a delivery step of transmitting the target data after the conversion of the data format in the data processing step to the delivery server, wherein the data format indicated in the second requirement information is the A data distribution method is provided that is a data format required for the target data when the application is used in a vehicle, and is an arbitrary data format required by the manufacturer of the vehicle.

According to the present invention, it is possible to acquire a plurality of data provided by a third party, process them into data in any format required by automobile manufacturers, and distribute the data.

BRIEF DESCRIPTION OF THE DRAWINGS It is a figure which shows the schematic structural example of the connected service 1 for vehicles using the data distribution system 10 which concerns on one Embodiment of this invention. 2 is a block diagram showing a configuration example of a common base 10; FIG. It is a figure which shows an example of the data acquisition requirement table|surface 17 for ECU. FIG. 3 is a sequence diagram showing an example of a procedure of overall processing in the connected service for vehicles 1; FIG. 10 is a sequence diagram showing a detailed procedure example of data acquisition processing; FIG. 4 is a diagram for explaining an image of how various data are handled in the data acquisition process; FIG. 10 is a sequence diagram showing a detailed procedure example of data processing; FIG. 4 is a diagram for explaining an image of data conversion by data processing; It is a figure which shows an example of the data acquisition requirement table|surface 27 for navigation.

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

FIG. 1 is a diagram showing a schematic configuration example of a vehicle-oriented connected service 1 using a data distribution system 10 according to an embodiment of the present invention. A connected service 1 for vehicles shown in FIG. 1 is a next-generation connected service that is expected to be realized in several years.

The data distribution system 10 according to the present embodiment distributes the data provided by the OEM server 20 to the vehicle 30 in providing the service to the vehicle 30 to the companies A to D, which are third parties 40 . This data distribution system collects data from servers 41 to 44 and distributes (provides) it to OEM server 20, and is hereinafter referred to as common base 10. FIG. The common platform 10 may consist of a physical server and database, or may consist of a cloud.

The OEM server 20 is a distribution server owned by a service provider (mainly an automobile manufacturer) that provides services to the vehicle 30 and is configured to be able to communicate with the vehicle 30 and the common base 10 . The OEM server 20 receives data necessary for the application from the company servers 41 to 44 of the third party organization 40 via the common infrastructure 10 in response to a request from the vehicle 30 to activate or use the application, and transmits the data to the vehicle 30. have a role to play. The above-mentioned "application" is, for example, an application installed in the vehicle 30, and "data necessary for the application" is, for example, an ECU (Electronic Control Unit) or the like when starting and using the application. corresponds to the data required by the vehicle-mounted equipment of the vehicle 30 of . Further, the OEM server 20 combines not only the data of the third party organization 40 received from the common platform 10 but also the existing data held by the OEM server 20 or the like to add added value and provide services. good too.

In this example, the third party organization 40 is composed of companies A to D, and the company servers 41 to 44 (which may be considered as databases) of each company are required by the applications used by the vehicle 30. , and provides these data to the common platform 10 in response to requests from the common platform 10 . The “data” provided by the third-party organization 40 is data necessary for launching and using applications, and specifically includes security patches, images, sounds, videos, climate data, traffic information, or map data. etc.

Referring to FIG. 1, the general behavior of the vehicle-oriented connected service 1 will be described. be done. The OEM server 20 that has received the application use request requests the common platform 10 to collect the data requested in the application use request (hereinafter referred to as data collection request). Upon receiving the data collection request, the common platform acquires and processes data in response to the data collection request from multiple third-party organizations 40 (more precisely, company servers 41 to 44), and then provides it to the OEM server 20. . Then, the OEM server 20 distributes the data of the third party provided from the common platform 10 to the vehicle 30 to respond to the application use request from the vehicle 30 .

FIG. 2 is a block diagram showing a configuration example of the common base 10. As shown in FIG. As shown in FIG. 2 , the common base 10 includes a command reception unit 11 , a data acquisition unit 12 , a data processing unit 13 , a distribution unit 14 and a data storage unit 15 .

Of the configuration of the common base 10, each functional unit of the command reception unit 11, the data acquisition unit 12, the data processing unit 13, and the distribution unit 14 is a processor such as a server on which the common base 10 is mounted (for example, CPU (Central Processing Unit)). Unit)) reads out a predetermined program into memory and executes it, thereby realizing the functions possessed by each unit, and transmits and receives data to and from external devices (OEM server 20 and corporate servers 41 to 44 of third party organization 40). In some cases, a network I/F (not shown) is used. Details of each functional unit will be described later in the description of processing.

The data storage unit 15 of the common base 10 is implemented by storage means such as a database. As shown in FIG. 2, the data storage unit 15 specifically stores a company ID master 16 and a data acquisition requirement table 17. FIG.

The company ID master 16 is master data for managing company IDs uniquely assigned to each company (including the company of the OEM server 20 and companies A to D of the third party organization 40). It is data managed by More specifically, the company ID master 16 manages the company IDs of the OEM servers 20 that can use the data collection service provided by the common platform 10, and also manages the company IDs of the OEM servers 20 that can use the common platform 10 as data acquisition destinations. The company ID of the public institution 40 is managed. Note that the company ID may not be assigned on a company-by-company basis, but may be assigned on a company-by-company information processing system basis (specifically, for example, for each OEM server 20 or each company server 41 to 44). In that case, the company ID master 16 serves as master data for managing company IDs assigned to the information processing systems of each company.

The data acquisition requirement table 17 defines information on data that the common platform 10 needs to acquire from the third party organization 40 in response to a data collection request from the OEM server 20, and information on the data conversion method after acquisition. It is a requirement table, and is realized by, for example, table format data. The format of the data acquisition requirement table 17 is configured so that the format can be flexibly converted by negotiating the specifications between the user who uses the common platform 10 and the vendor who builds the common platform 10. is preferred. The contents of the data acquisition requirement table 17 are usually negotiated between the common platform 10 and the OEM server 20 and held by both the common platform 10 and the OEM server 20 . In addition, when the data required to respond to the application usage request changes due to changes in the specifications of the application (specifically, for example, when it is necessary to acquire specific data or not), The data format requirements of the data acquisition requirement table 17 are customized in the OEM server 20, and the customized data acquisition requirement table 17 is transmitted to the common platform 10 and stored in the data storage unit 15, whereby the common platform 10 and the OEM The same data acquisition requirement table 17 can be held with the server 20 .

FIG. 3 is a diagram showing an example of the data acquisition requirement table 17 for ECU. As shown in FIG. 3, the data acquisition requirement table 17 includes data necessary for starting or using a certain application (application) for each module 171 (for example, ECU1, ECU2) in the vehicle 30 that mainly uses the data. furthermore, these data requirements are information (request data 172) including requirements related to the data to be acquired by the common platform 10 and its acquisition destination, and the data acquired by the common platform 10 can be roughly divided into information (data conversion method 173) including requirements regarding the data format required when distributing to the OEM server 20.

In the data acquisition requirement table 17 shown in FIG. 3, the request data 172 is composed of data name 1721, data content 1722, flag 1723, acquirer company code 1724, and label 1725 items.

Among them, the data name 1721 holds information indicating the name of the target data of the record. As the name of the data held in the data name 1721, a data name agreed in advance between the company of the third party organization 40 from which the target data is acquired and the user of the common platform 10 or the OEM server 20 is used. be done. Further, in the data contents 1722, when the target data is provided from the third party organization 40 by the data acquisition request, the actual data is embedded.

The flag 1723 holds flag information indicating whether or not the target data of the record is data desired to be obtained by the OEM server 20, which is the source of data acquisition (that is, whether or not data acquisition is necessary). . Specifically, for example, if the data is data to be acquired, a flag of "1" is set, and if the data is not to be acquired, a flag of "0" is set. Although details will be described later, the flag 1723 is used for control by the data acquisition unit 12 .

The acquisition source company code 1724 holds information indicating the company code of the third party organization 40 (company A to company D) from which the target data of the record is acquired. In this example, the company code of company A is "aaaa", the company code of company B is "bbbb", the company code of company C is "cccc", and the company code of company D is "dddd". As in the above example, the company code is assigned a unique code for each company (more precisely, for each company server 41 to 44 owned by each company). 40 (strictly speaking, company servers 41 to 44) can be specified. Although the details will be described later, the acquisition company code 1724 is used for control by the data acquisition unit 12 .

The label 1725 holds label information used as key information for retrieving the target data of the record from the database managed by the third party organization 40 (company servers 41 to 44) from which the data is obtained. . The label information is not limited to a specific form, but may be, for example, information such as the name of the target data or a search word related to the content of the data. It may be address information or the like that can be specified/narrowed down. Although the details will be described later, at the time of the data acquisition request, the data acquisition unit 12 is stored in the label 1725 in the acquisition source third-party organization 40 (company servers 41 to 44) indicated by the acquisition source company code 1724. By sending the label information together, the third party organization 40 (for example, the company server 41) that receives the data acquisition request can search for the target data.

Also, in the data acquisition requirement table 17 shown in FIG. As described above, the data conversion method 173 is performed by the data processing unit 13 of the common platform 10 on the data (acquired data) acquired from the third party organization 40 (company servers 41 to 44) in response to a data acquisition request. It defines requirements for data conversion (data processing), and in the case of FIG. 3, a configuration example assuming character data as acquired data is shown.

The data name 1731 holds information indicating the name of acquired data, which is the same as the data name 1721 of the corresponding record of the request data 172 . The data format 1732, the number of data digits 1733, the character code 1734, and the encryption format 1735 are formats for data conversion performed by the data processing unit 13 on the acquired data (data format, number of data digits, data character code, encryption format applied to the data) are held respectively.

Although the details will be described later, the data processing unit 13 processes the acquired data into a format that conforms to the requirements of the data conversion method 173, so that the data is formatted from a plurality of third-party organizations 40 (company servers 41 to 44). Even if different acquisition data are acquired, the formats of the plurality of acquisition data can be uniformed through data conversion for each acquisition data.

In the common platform 10 according to this embodiment, the data (acquired data) input from the third party organization 40 is not limited to character data as in the above example, and may be image data, voice data, or the like. is assumed. Therefore, it is preferable that the data acquisition requirement table 17 can be converted by a conversion method that conforms to various data formats. In addition, the registration contents (holding information) of each requirement in the data acquisition requirement table 17 can be flexibly customized according to the requirements of the user.

FIG. 4 is a sequence diagram showing a procedure example of overall processing in the connected service 1 for vehicles. In FIG. 4, as an example, an overall processing procedure for obtaining data from the company server 41 of company A and the company server 42 of company B is shown.

According to FIG. 4, first, the vehicle 30 transmits a request to activate or use a predetermined application (application use request) to the OEM server 20 (step S101). The OEM server 20 that has received the application use request independently communicates with the vehicle 30, authenticates the vehicle 30 and the vehicle user (step S102), and notifies the vehicle 30 of the results of authentication and authorization (step S103). After the notification, the OEM server 20 transmits a collection request for necessary data (data collection request) to the common base 10 (step S104). More specifically, in step S104, the OEM server 20 sends the company ID of its own server and the data acquisition requirement table 17 to the common platform 10 together with (or included in) the data collection request command. The command reception unit 11 of receives these. Note that the command receiving unit 11 stores the new data acquisition requirement table 17 in the data storage unit 15 when receiving the new data acquisition requirement table 17 in step S104.

Next, the command receiving unit 11 of the common platform 10 authenticates the OEM server 20 using the company ID of the OEM server 20 received in step S104 (step S105), and notifies the OEM server 20 of the authentication and authorization results. (step S106). More specifically, in step S105, the command receiving unit 11 matches the company ID of the OEM server 20 received in step S104 with the company ID master 16 held in the data storage unit 15 of the common platform 10. authenticates whether the OEM server 20 can use the service provided by the common platform 10. Then, when the use of the OEM server 20 is authorized by the authentication in step S105, the command receiving unit 11 notifies the OEM server 20 of the authentication and authorization results in step S106, and also the data acquisition requirement table received in step S104. 17 to the data acquisition unit 12 .

Next, in the common platform 10, the data acquisition unit 12, based on the data acquisition requirements table 17 received from the command reception unit 11, A data acquisition request (data acquisition request) is made to the company server 42) (steps S107 and S108). The corporate servers 41 and 42 of the third-party organization 40 that have received the data acquisition request in steps S107 and S108 acquire the data according to the request from the database managed by themselves and send it to the data acquisition unit 12 of the common platform 10. provided (steps S109, S110).

Next, the data acquisition unit 12 of the common platform 10 aggregates (groups) the data provided from the company servers 41 and 42 of the third party organization 40 (step S111). Aggregation of data in step S111 is performed by aggregating a plurality of data provided by the third-party organization 40 for each group ( grouping). The "group based on the service provided to the vehicle 30 by the service provider" means, for example, a group for each application. Specifically, in the case of the data acquisition requirement table 17 shown in FIG. It corresponds to "ECU1" and "ECU2". Therefore, in detail with reference to FIG. 3, in step S111, the data acquisition unit 12 stores each data provided by the third party organization 40 for each module 171 of the data acquisition requirements table 17, and the third party organization 40 The data is aggregated (grouped) by registering each data provided from the data contents 1722 . After that, the data acquisition unit 12 sends the data acquisition requirement table 17 after data aggregation to the data processing unit 13 . Note that the processing (data acquisition processing) of steps S107 to S111 executed mainly by the data acquisition unit 12 and the third party organization 40 (company servers 41 and 42) described above will be described with reference to FIGS. Details will be described later.

Next, the data processing unit 13 of the common platform 10 performs format conversion (data processing) on the aggregated data based on the data acquisition requirement table 17 received from the data acquisition unit 12 (step S112). Then, the distribution unit 14 of the common base 10 provides the data processed by the data processing unit 13 to the OEM server 20 as a response to the data collection request in step S104 (step S113). Details of the processing (data processing) of step S112 performed by the data processing unit 13 will be described later with reference to FIGS. 7 and 8. FIG.

After receiving the data provided from the common platform 10 in step S113, the OEM server 20 packages the data based on its own specifications and then distributes the data to the vehicle 30 (step S114). As a result, the vehicle 30 can start and use the application using the distributed data (step S115).

FIG. 5 is a sequence diagram showing a detailed procedure example of data acquisition processing. The data acquisition process shown in FIG. 5 shows in detail the processes of steps S107 to S111 in FIG. executed. FIG. 6 is a diagram for explaining an image of how various data are handled in the data acquisition process. In FIG. 6, in addition to the common platform 10 (strictly speaking, the data acquisition unit 12), the data acquisition requirement table 17 detailed in FIG. Data are represented.

A detailed procedure of the data acquisition process will be described below with reference to FIGS. 5 and 6. FIG. In the description of FIG. 5, for the sake of simplification, the processing on the side of the third-party organization 40 will be focused on the company server 41 of company A, but other third-party organizations 40 (company servers 42 to 44) will be described. can be considered to be the same as the processing in the company server 41 .

In the data acquisition process shown in FIG. 5, in step S106 of FIG. Started after sending.

According to FIG. 5, first, the data acquisition unit 12 of the common platform 10 receives the data acquisition requirement table 17 transmitted from the command reception unit 11 (step S201), and refers to the received data acquisition requirement table 17 (step S202).

Next, the data acquisition unit 12 requests the third party organization 40 (for example, the company server 41) from which the data read from the data acquisition requirement table 17 is acquired to acquire the data (step S203).

The processing of step S203 will be described in detail. First, the data acquisition unit 12 checks the flag 1723 of the request data 172 of the data acquisition requirement table 17, and if the value of the flag 1723 is "1", the data indicated by the data name 1721 of the record is It is determined that it is the data to be acquired. In this case, the data acquisition unit 12 further confirms the company code held in the acquisition company code 1724 of the record, thereby confirming the data acquisition destination third-party organization 40 (for example, the company server 41 held by company A, The company server 42 held by company B) can be identified (see step S203-1 in FIG. 6). Then, the data acquisition unit 12 sends a data acquisition request to the specified data acquisition destination along with the label information held in the label 1725 of the record (see step S203-2 in FIG. 6). The label information is information that can be used as a search key for obtaining information from the database internally managed by the third-party organization 40. By sending a data acquisition request with such label information, On the side of the third party institution 40, it becomes possible to search for the data to be acquired. On the other hand, when the value of the flag 1723 in the request data 172 of the data acquisition requirement table 17 is "0", it can be determined that the data indicated by the data name 1721 of the record is not to be acquired. No data acquisition request will be sent for this data.

Next, the third-party organization 40 (for example, the company server 41 of company A) of the data acquisition destination receives the data acquisition request and label information sent from the data acquisition unit 12 in step S203, and accepts the data acquisition request ( step S204). Next, the third-party organization 40 (for example, the company server 41) utilizes the received label information as a search key, selects necessary data (acquired data) from an internally managed database, and obtains the data. It is provided to the unit 12 (step S205). It should be noted that the number of label information data used as a search key can be flexibly changed.

It is also assumed that general security measures are taken for data exchange in steps S203 to S205. Further, in step S203, if a data acquisition request is also sent from the data acquisition unit 12 to another third-party organization 40 (for example, the company server 42 of company B), the third-party organization 40 similarly , filtering and provision of acquired data.

Next, in step S205, the data acquisition unit 12 receives acquired data from one or more third party organizations 40 (company server 41 and company server 42), aggregates the received acquired data, and sends it to the data processing unit 13. Send (step S206).

The processing of step S206 will be described in detail. First, as aggregation of the acquired data, the data acquisition unit 12 embeds the actual data of the acquired data in the data content 1722 of the record corresponding to the acquired data in the data acquisition requirement table 17 . At this time, the obtained data may be embedded in the data contents 1722 according to a predetermined format. In the data acquisition requirement table 17, the data content 1722 of the record corresponding to the data not subject to the data acquisition request (in other words, the record whose flag 1723 value is "0") is set to a "null" value, for example. It may be embedded (see also S206 in FIG. 6). After the embedding of the data contents 1722 of each record is completed, the data acquisition unit 12 sends the data acquisition requirements table 17 after embedding to the data processing unit 13 .

By performing the data acquisition processing of steps S201 to S206 in this manner, the data acquisition unit 12 of the common platform 10 acquires the data from the OEM server 20 based on the data acquisition requirement table 17 (more specifically, the request data 172). Data desired by the collection request (step S104 in FIG. 4) can be acquired from the third party organization 40 and sent to the data processing unit 13. FIG.

FIG. 7 is a sequence diagram showing a detailed procedure example of data processing. The data processing shown in FIG. 7 shows in detail the processing of step S112 in FIG.

The data processing shown in FIG. 7 aggregates (groups) the data acquired by the data acquisition unit 12 from the third party organization 40 in step S111 of FIG. It is started after sending to .

According to FIG. 7, the data processing unit 13 first receives the data acquisition requirement table 17 transmitted from the data acquisition unit 12 (step S301), and refers to the received data acquisition requirement table 17 (step S302).

Next, the data processing unit 13 converts (processes) the data acquired by the data acquisition unit 12 from the third party organization 40 (company servers 41 to 44) according to the data conversion method read from the data acquisition requirement table 17 ( step S303). In the data acquisition requirement table 17 exemplified in FIG. 1735), a different data conversion method may be registered for each target data, or the same data conversion method may be registered for each module 171 (e.g., ECU1 or ECU2). may be

FIG. 8 is a diagram for explaining an image of data conversion by data processing. FIG. 8 shows the data acquisition requirement table 17A before data conversion (data processing) in step S303 of FIG. Specifically, the data content 1722) in which the actual data is embedded is shown. The data acquisition requirement tables 17A and 17B shown in FIG. 8 have the same configuration as the data acquisition requirement table 17 illustrated in FIGS. Also, the data acquisition requirement table 17A corresponds to part of the data acquisition requirement table 17 aggregated (grouped) through the process of S206 in FIG.

Comparing the data acquisition requirement table 17A before data conversion and the data acquisition requirement table 17B after data conversion shown in FIG. It can be seen that the data content 1722 in the record (holding information other than null) changes before and after the data conversion. Specifically, for example, in the case of “data A” of “ECU2”, the data content 1722 in the data acquisition requirement table 17A before data conversion is “○○○○”, but data acquisition after data conversion The data content 1722 in the requirement table 17B is "□□□□". This is because data conversion (data processing) was performed in accordance with the registration contents of the data conversion method 173 in the record corresponding to data A, and the actual data of data A changed from "○○○○" to "□□□ □” means that it has been converted (processed). On the other hand, if the data content 1722 in the data acquisition requirement table 17A is "null", which means data not to be acquired, such as "data A" of "ECU1", the data in the data acquisition requirement table 17B The content 1722 of the is still "null". That is, data not to be acquired may not be subjected to special data conversion. Thus, the data acquisition requirement table 17B shown in FIG. 8 aggregates a plurality of pieces of acquired data acquired from the third-party organization 40 in units of modules 171 such as "ECU1" and "ECU2", and further performs data conversion. The results can be held, in other words, data obtained by integrating a plurality of acquired data can be held.

Returning to the description of FIG. After performing the data conversion in step S303 as described above, the data processing unit 13 sends the data acquisition requirement table 17 (corresponding to the data acquisition requirement table 17B in FIG. 8) in which the actual data after data conversion is embedded to the distribution unit 14. (step S304).

By performing the data processing of steps S301 to S304 in this way, the data processing unit 13 of the common platform 10 can perform the third-party institution The data acquired from 40 can be converted (processed) and sent to the distribution unit 14 . That is, even if data with different formats are obtained from a plurality of third-party organizations 40 (company servers 41 to 44) through the data acquisition process described above, the data processing process is performed to obtain, for example, "ECU1". , and "ECU2" for each module 171, and the acquired data can be converted into a suitable format when an application uses the acquired data. As a result, the distribution unit 14 can distribute the acquired data to the OEM server 20 in a format suitable for the application (or the OEM server 20).

In this description, in the data acquisition process, the data acquisition unit 12 embeds data (acquired data) acquired from the third-party organization 40 into the data contents 1722 of the data acquisition requirements table 17, and then the data processing unit 13 , and in the data processing, the data processing unit 13 converts the acquired data embedded in the data content 1722 of the data acquisition requirement table 17. The method of handling acquired data in the common platform 10 according to the embodiment is not limited to the above method. Specifically, for example, if the data acquisition requirement table 17 does not have the data contents 1722, the data acquisition unit 12 acquires the acquired data from the third-party organization 40 in the data acquisition process, and the data acquisition requirements It may be sent to the data processing unit 13 together with the table 17, and the data processing unit 13 may perform data conversion on the separately sent acquisition data based on the data acquisition requirements table 17 in the data processing process.

As described above, the common base 10 (data distribution system 10) according to the present embodiment, in response to a request for data required by the vehicle 30, receives the request data of the data acquisition requirement table 17 from the OEM server 20. 172 (a flag indicating whether or not data acquisition is necessary, the company ID of the third-party organization 40 from which the data is acquired, and label information that serves as a search key at the data acquisition source). By acquiring each from the third-party organization 40 (company servers 41 to 44), it is possible to realize a mechanism for acquiring a plurality of data from the third-party organization 40. FIG. As a result, the common platform 10 can acquire one or more pieces of data from one or more third-party organizations 40, respectively. becomes possible.

Furthermore, the common platform 10 (data distribution system 10) according to the present embodiment aggregates each data acquired from the third party organization 40, and converts the data of the data acquisition requirement table 17 to each aggregated data. Based on the information (data format, number of data digits, character code, encryption format) described in Method 173, data conversion (data processing) is performed to aggregate the acquired multiple data into one data. It is possible to realize a mechanism for processing data into a data format requested by the vehicle. As a result, when the data collected by the common platform 10 is delivered to the OEM server 20, the effect of reducing the processing load on the OEM server 20 can be obtained.

Thus, according to the common platform 10 (data distribution system 10) according to the present embodiment, a plurality of data provided by the third-party organization 40 (company servers 41 to 44) are acquired, and the data are delivered in any format required by the automobile manufacturer. data, and delivers it to the OEM server 20.

In the above description of the present embodiment, the data distribution system 10 (common base 10) acquires data required by the ECU or the like from the third party organization 40 when starting or using an application on the vehicle 30 side. However, the applicable range of the data distribution system 10 (common base 10) according to the present embodiment is not limited to the above examples such as the ECU. In addition, the common platform 10 according to the present embodiment, for example, uses a human machine interface (HMI) device mounted on the vehicle 30 to allow the user to provide content information ( It is also applicable when trying to acquire an application independently developed by a third party.

Data acquisition using the above HMI will be explained using, for example, a car navigation system (navigation) installed in a vehicle as an example. , the OEM server 20 is requested to acquire the data of the selected content information. At this time, the vehicle-oriented connected service 1 replaces the "application use request" in step S101 of FIG. 4 with a "content information data acquisition request" to proceed with the subsequent overall processing according to the sequence diagram of FIG. can be done.

Then, the OEM server 20 that has received the content information data acquisition request (step S104 in FIG. 2), upon receiving the data collection request (step S104 in FIG. 2), creates a data acquisition requirement table 27 for navigation that describes the requirements for acquiring the content information. is sent to the common base 10. FIG. 9 is a diagram showing an example of the data acquisition requirement table 27 for navigation. Since the data acquisition requirement table 27 illustrated in FIG. 9 has the same data configuration as the data acquisition requirement table 17 for ECU illustrated in FIG. 3, detailed description thereof will be omitted.

Then, based on the data acquisition requirement table 27 received from the OEM server 20, the common platform 10 acquires content information data from the third party organization 40 (data acquisition processing), and performs data conversion on the acquired content information. After performing (data processing), the content information can be distributed to the OEM server 20 . Note that the sequence diagram of FIG. 5 can be used for the data acquisition process, and the sequence diagram of FIG. 7 can be applied to the data processing process.

As described above, according to the vehicle connected service 1 using the data distribution system 10 (common platform 10) according to the present embodiment, it is possible to realize a mechanism for distributing content information in HMI.

In addition, the present invention is not limited to the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described. Moreover, it is possible to add, delete, or replace a part of the configuration of the embodiment with another configuration.

Further, each of the above configurations, functions, processing units, processing means, and the like may be realized by hardware, for example, by designing them in an integrated circuit. Moreover, each of the above configurations, functions, etc. may be realized by software by a processor interpreting and executing a program for realizing each function. Information such as programs, tables, and files that implement each function can be stored in recording devices such as memories, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.

Further, in the drawings, control lines and information lines are shown as necessary for explanation, and not all control lines and information lines are necessarily shown on the product. It may be considered that almost all configurations are interconnected in practice.

1 Connected service for vehicles 10 Data distribution system (common platform)
11 command reception unit 12 data acquisition unit 13 data processing unit 14 distribution unit 15 data storage unit 16 company ID master 17 (17A, 17B), 27 data acquisition requirement table 20 OEM server 30 vehicle 40 third party organization 41-44 company server

Claims (8)

A data distribution system that acquires and distributes data from one or more third parties to a distribution server capable of distributing data to each of a plurality of vehicles that receive connected services for vehicles,
When one of the plurality of vehicles requests the distribution server to use an application installed in the vehicle, a data collection request for one or more target data required when using the application is made. For each of the target data received from the distribution server and to be acquired by the data collection request, first requirement information indicating requirements related to a third-party institution from which the target data is acquired, and the target data to be delivered a command receiving unit that receives second requirement information indicating requirements related to the data format required when delivering to the server;
a data acquisition unit configured to acquire each of the target data to be acquired in the data collection request received by the command reception unit from the third-party organization specified as an acquisition destination in the first requirement information;
a data processing unit that converts a data format based on the second requirement information for each of the target data acquired by the data acquisition unit;
a distribution unit configured to transmit the target data after conversion of the data format by the data processing unit to the distribution server;
with
The data format indicated in the second requirement information is a data format required for the target data when using the application in the vehicle, and is an arbitrary data format required by the manufacturer of the vehicle.
A data delivery system characterized by: The first requirement information further includes label information that serves as a search key that can be used when extracting the target data to be acquired at a third-party institution from which it is acquired,
2. The data according to claim 1, wherein the data acquisition unit also sends the label information of the target data when requesting the acquisition destination third-party organization to acquire the target data. delivery system. In the first requirement information, the plurality of target data to be acquired by the data collection request are managed by being divided into groups based on the services provided by the connected service ,
The data acquisition unit aggregates the plurality of target data acquired from the third-party organization for each group,
2. The data distribution system according to claim 1, wherein the data processing unit converts the data format for each of the plurality of target data aggregated by the data acquisition unit. further comprising a data storage unit holding master data of a company identifier pre-assigned to a service provider of the connected service ;
The command receiving unit receives the data collection request to which the company identifier of the service provider is attached from the distribution server, and authenticates the service provider by comparing the company identifier with the master data. 2. The data distribution system according to claim 1, characterized by: The master data further includes a company identifier pre-assigned to each company constituting the third-party organization,
The first requirement information includes flag information for controlling whether or not a plurality of candidate data to be acquired by the data collection request is to be acquired, and the first requirement information holding each of the candidate data. the third party company identifier; and
The data acquisition unit determines the target data to be acquired by the data collection request based on the flag information of the first requirement information, and corresponds to the target data in the first requirement information. 5. The data delivery system according to claim 4, wherein the acquisition source of the target data is determined by comparing the company identifier with the master data. The first requirement information and the second requirement information are managed by requirement table data in a table format,
In the requirement table data, the target data acquired from the third-party organization by the data acquisition unit or the target data after the data format conversion by the data processing unit can be embedded. 2. The data distribution system according to claim 1, characterized by: When use of the application is requested by the vehicle - mounted device of the vehicle, or when use of content information provided by the third-party organization is requested in response to a user operation on a human-machine interface mounted on the vehicle. 2. The data distribution system according to claim 1, wherein said command reception unit receives said data collection request from said distribution server. A data distribution method by a data distribution system that acquires and distributes data from one or more third parties to a distribution server capable of distributing data to each of a plurality of vehicles that receive connected services for vehicles,
When one of the plurality of vehicles requests the distribution server to use an application installed in the vehicle, the data distribution system provides one or more targets required when using the application. receiving a data collection request for data from the distribution server, and for each of the target data to be acquired by the data collection request, first requirement information indicating requirements related to a third-party organization as an acquisition destination; a command receiving step of receiving second requirement information indicating requirements regarding a data format required when distributing the target data to the distribution server;
data obtained by said data distribution system from said third party organization designated as an acquisition destination in said first requirement information for each of said target data obtained in said data collection request received in said instruction receiving step; an acquisition step;
a data processing step in which the data delivery system converts the data format of each of the target data acquired in the data acquisition step based on the second requirement information;
a distribution step in which the data distribution system transmits the target data after the conversion of the data format in the data processing step to the distribution server;
with
The data format indicated in the second requirement information is a data format required for the target data when using the application in the vehicle, and is an arbitrary data format required by the manufacturer of the vehicle.
A data distribution method characterized by:

Images