Mobility service system and method for reducing data volume

Abstract

A mobility service system according to one aspect of the present disclosure is provided with an in-vehicle device and a management server. An in-vehicle device is provided with an execution unit, an event detection unit, an in-vehicle device-side reduction unit, and an upload unit. When an event is detected, the in-vehicle device-side reduction unit reduces the amount of data of the acquired content on the basis of an in-vehicle device reduction reference, and generates in-vehicle device partial content. The management server is provided with a server-side reduction unit and a terminal transmission unit. The server-side reduction unit reduces the amount of data of the uploaded in-vehicle device partial content on the basis of a server reduction standard, and generates server partial content.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This international application claims the priority of Japanese Patent Application No. 2022-089071 filed with the Japan Patent Office on May 31, 2022, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] The present disclosure relates to a technology for reducing the amount of data in a mobility service system. Background Art

[0004] Patent Document 1 listed below describes a technology for connecting a vehicle to a cloud server or the like on a network and uploading and downloading various data between the vehicle and the cloud.

[0005] Patent Document 1: Japanese Patent Application Publication No. 2020-200123

[0006] By uploading various data from the vehicle to the cloud, service providers can use the data stored in the cloud to provide various services to end users. However, the inventors' detailed research has found that when uploading a large amount of data from the vehicle to the cloud and storing a large amount of data in the cloud, the operation fees such as communication fees and database maintenance fees are too high, and the service usage fees of the end users may increase. Summary of the invention

[0007] One aspect of the present disclosure is to reduce the amount of data communicated and / or stored while providing appropriate services to end users in a mobility service system.

[0008] The mobility service system of one aspect of the present disclosure includes an on-board device and a management server, wherein the on-board device includes an acquisition device for acquiring content including images or sounds and is mounted on a vehicle, and the management server is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the vehicle. The on-board device includes an execution unit, an event detection unit, an on-board device side reduction unit, and an upload unit. The execution unit executes an application. The event detection unit detects an event related to the application while the execution unit executes the application. When the event is detected by the event detection unit, the on-board device side reduction unit reduces the data volume of the content acquired by the acquisition device according to the on-board device reduction standard corresponding to the application, and generates on-board device partial content. The upload unit uploads the on-board device partial content generated by the on-board device reduction unit to the management server. The management server includes a server side reduction unit and a terminal transmission unit. The server side reduction unit reduces the data volume of the on-board device partial content uploaded by the upload unit according to the server reduction standard corresponding to the information related to the on-board device, and generates the server partial content. The terminal transmission unit transmits the terminal content to the terminal device of the end user who uses the service corresponding to the application based on the server partial content generated by the server side reduction unit.

[0009] In a mobility service system of one aspect of the present disclosure, a vehicle-mounted device reduces the data volume of content using a vehicle-mounted device reduction benchmark, and uploads the reduced data volume content to a management server. In addition, in the above-mentioned mobility service system, the management server reduces the data volume of the uploaded content using a benchmark corresponding to the server reduction benchmark, and based on the reduced data volume content, sends terminal content to the terminal device of the end user. The vehicle-mounted reduction benchmark corresponds to the application, and the server reduction benchmark corresponds to information related to the vehicle-mounted device. Therefore, the above-mentioned mobility service system can provide appropriate services to the end user via the terminal device, and can reduce the communication volume between the vehicle-mounted device and the management server.

[0010] Another aspect of the present disclosure is a method for reducing the amount of data performed by a mobility service system having an on-board device and a management server, wherein the on-board device has an acquisition device for acquiring content including images or sounds and is mounted on a vehicle, and the management server is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the vehicle. The on-board device executes an application, and during the execution of the application, detects an event related to the application, and based on the detected event, reduces the data amount of the content acquired by the acquisition device using an on-board device reduction benchmark corresponding to the application, generates on-board device partial content, and uploads the generated on-board device partial content to the management server. The management server reduces the data amount of the uploaded on-board device partial content using a server reduction benchmark corresponding to the information related to the on-board device, generates server partial content, and based on the server partial content, sends terminal content to a terminal device of an end user who uses a service corresponding to the application.

[0011] The above method is executed by the mobility service system, achieving the same effect as the above mobility system. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 This is a schematic diagram showing the configuration of a mobile IoT system.

[0013] Figure 2 This is a block diagram showing the hardware configuration of an edge device.

[0014] Figure 3 This is a functional block diagram showing the functional configuration of an edge device.

[0015] Figure 4 is a diagram representing the first layer and data format of standardized vehicle data.

[0016] Figure 5 It is a diagram showing the structure of standardized vehicle data.

[0017] Figure 6 : is a flowchart showing the content upload process executed by the vehicle-mounted device.

[0018] Figure 7 This is a diagram schematically showing the gradual reduction in the amount of data in the mobile IoT system.

[0019] Figure 8 This is a block diagram showing the hardware configuration of the management server.

[0020] Fig. 9 This is a functional block diagram showing the functional configuration of the management server.

[0021] Fig.10 This is a functional block diagram showing the functional structure of the mobility GW and the data management unit.

[0022] Fig.11 This is a diagram showing the composition of a shadow.

[0023] Fig.12 This is a diagram showing the structure of the latest index.

[0024] Fig.13 It is a diagram showing the structure of an index.

[0025] Fig.14 This is a flowchart showing the content storage process executed by the management server.

[0026] Fig.15 This is a block diagram showing the hardware configuration of the service server.

[0027] Fig.16 This is a block diagram showing the functional structure of the service server.

[0028] Fig.17 : is a flowchart showing the content acquisition processing executed by the service server.

[0029] Fig.18 This is a sequence diagram showing normal operations in a mobile IoT system.

[0030] Fig.19 It is a sequence diagram for event detection in mobile IoT systems. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0032] <1-1. Overall structure>

[0033] Figure 1 The mobility IoT system 100 shown has edge devices 2A, 2B, a management server 3, service servers 5A, 5B, and terminal devices 7A, 7B. IoT is an abbreviation of Internet of Things. The management server 3 and the service server 5 can also be configured as cloud servers. Hereinafter, the edge devices 2A, 2B are collectively referred to as edge devices 2, and the service servers 5A, 5B are collectively referred to as service servers 5. In addition, the terminal devices 7A, 7B are collectively referred to as terminal devices 7. In addition, the mobility IoT system 100 is equivalent to the mobility service system of the present disclosure, and the edge devices 2A, 2B are equivalent to the vehicle-mounted devices of the present disclosure. In addition, the management server 3 is equivalent to the first management unit of the present disclosure, and the service servers 5A, 5B are equivalent to the second management unit of the present disclosure.

[0034] The edge devices 2A and 2B are mounted on different registered vehicles 8A and 8B. Hereinafter, the registered vehicles 8A and 8B are collectively referred to as registered vehicles 8. The edge device 2 collects vehicle data of the registered vehicle 8 on which it is mounted, and uploads the collected vehicle data to the management server 3. The edge device 2 performs vehicle control according to instructions from the management server 3.

[0035] The edge device 2 downloads and installs an application program (hereinafter referred to as an application) from the service server 5 and executes the application. The identification information of the edge device 2 (specifically, the edge device ID) is registered in the service server 5 storing the application downloaded by the edge device 2.

[0036] The management server 3 communicates with each edge device 2 and each service server 5 via the wide area communication network NW. The management server 3 stores vehicle data uploaded from each edge device 2 in a database. The management server 3 provides each service server 5 with an interface for accessing the database of the management server 3 and registering vehicles 8.

[0037] The service server 5 uses the interface provided by the management server 3 to perform the collection of vehicle data corresponding to the registered vehicle 8 and the vehicle control of the registered vehicle 8. The service server 5 is owned or managed by the service user. The service user provides various services to the end user through the service server 5 using various data of the management server 3. The service user is, for example, a fleet operator or a car sharing operator. The fleet operator provides fleet services to end users such as transport operators. The car sharing service provides car sharing services to end users such as general drivers.

[0038] The terminal device 7 is a smartphone, a tablet terminal, a PC, a smart watch, etc. Each terminal device 7 is held by an end user. Each terminal device 7 communicates with a predetermined service server 5 and receives services from the service server 5. Each terminal device 7 executes an application installed in the edge device 2 and an application corresponding to the installed application. The edge device 2 associates a registered vehicle 8 equipped with the edge device 2, a vehicle user of the registered vehicle 8, and an end user who receives services related to the registered vehicle 8.

[0039] The application installed in the edge device 2 is related to the service provided by the service user. The end user signs a contract with the service user who provides the desired service and downloads one or more applications from the service server 5 of the signed service user. There may be two or more applications corresponding to one service.

[0040] For example, when the end user receives a fleet service from a fleet service operator, the end user downloads the suspicious person detection application A1 and the smoking detection application A2 related to the fleet service from the service server 5 of the fleet service operator (refer to Figure 7 ).

[0041] In addition, the mobility IoT system 100 may also include one or more other edge devices 200 in addition to the edge device 2. The other edge devices 200 collect vehicle data of the vehicle on which they are mounted, and upload the collected vehicle data to the management server 3. However, the other edge devices 200 are not registered in the service server 5, and do not download applications from the service server 5. That is, users associated with the other edge devices 200 do not receive services from the service server 5.

[0042] In the present embodiment, the service server 5 is provided independently from the management server 3, but may be provided integrally with the management server 3. In addition, the mobile IoT system 100 may include three or more service servers 5, and may include three or more edge devices 2.

[0043] <2. Edge devices>

[0044] <2-1. Hardware configuration>

[0045] like Figure 2 As shown, the edge device 2 includes a control unit 21 , a vehicle interface (hereinafter referred to as vehicle I / F) 22 , a communication unit 23 , and a storage unit 24 .

[0046] The control unit 21 includes a CPU 211, a ROM 212, and a RAM 213. The various functions of the control unit 21 are realized by the CPU 211 executing a program stored in a non-migrating physical recording medium. In this embodiment, the ROM 212 is equivalent to a non-migrating physical recording medium storing a program. In addition, by executing the program, a method corresponding to the program is executed.

[0047] The vehicle IF unit 22 is connected to various vehicle-mounted devices via the vehicle-mounted network of the registered vehicle 8, etc., and obtains various information from the vehicle-mounted devices. The vehicle-mounted network may include CAN (Controller Area Network) and Ethernet. CAN is a registered trademark. Ethernet is a registered trademark. In addition to the devices originally installed on the registered vehicle 8, the vehicle-mounted devices connected to the vehicle IF unit 22 may also include post-installed external devices. The vehicle-mounted devices include one or more acquisition devices 222 and one or more surrounding monitoring sensors 223. The acquisition device 222 is a camera that captures the interior of the vehicle and / or a microphone that collects sound, and acquires digital content containing images and / or sounds. The surrounding monitoring sensor 223 is, for example, a sonar, lidar, radar, etc. that detects obstacles within a detection range of 3m or less around the registered vehicle 8. In addition, the vehicle-mounted equipment may also include sensors, acoustic devices, and display devices.

[0048] The communication unit 23 performs data communication with the management server 3 and the service server 5 via the wide area communication network NW by wireless communication.

[0049] The storage unit 24 stores the vehicle data and the like acquired via the vehicle IF unit 22 . The vehicle data accumulated in the storage unit 24 is uploaded to the management server 3 via the communication unit 23 .

[0050] <2-2. Functional structure>

[0051] like Figure 3 As shown, the edge device 2 includes functions of a system ware 25, a core function execution unit 26, and an application execution unit 27. The functions of the units 25 to 27 are realized by the CPU 211 executing a program stored in the ROM 212.

[0052] The system ware 25 includes basic software that abstracts the hardware and provides various services required to execute applications, and drivers for supporting special processing that cannot be standardized. The basic software includes an operating system (hereinafter referred to as an OS), a hardware abstraction layer (hereinafter referred to as a HAL), etc. The hardware that becomes the abstraction object of the system ware 25 includes not only the hardware of the edge device 2, but also vehicle-mounted devices and external devices connected to the edge device 2 via the vehicle IF unit 22.

[0053] The core function execution unit 26 and the application execution unit 27 are implemented by software running on the system component 25 .

[0054] <2-2-1. Core Function Execution Department>

[0055] The core function execution unit 26 is in the form of an edge computer that mediates between the management server 3 and the registered vehicle 8. Specifically, the core function execution unit 26 includes a basic upload unit 261 and a vehicle control unit 262. The basic upload unit 261 collects vehicle data of the registered vehicle 8 and uploads it to the management server 3. The vehicle control unit 262 controls the registered vehicle 8 according to instructions from the management server 3.

[0056] Here, the vehicle data provided by the basic uploading unit 261 to the management server 3 will be described.

[0057] The basic upload unit 261 repeatedly collects vehicle data from the registered vehicles 8 via the vehicle IF unit 22. The basic upload unit 261 converts the collected vehicle data into a standard format and stores it in correspondence with the hierarchical categories in the storage unit 24. Hereinafter, the hierarchical vehicle data is referred to as standardized vehicle data.

[0058] like Figure 4As shown, the standard format of vehicle data may include "unique tag", "ECU", "data type", "data size", "data value", and "data unit" as items.

[0059] The "unique tag" is information used to identify each physical quantity. For example, "ETHA" indicates the intake air temperature, and "NE1" indicates the engine speed.

[0060] "ECU" is information indicating an electronic control unit (hereinafter referred to as ECU) that is a source of generating vehicle data. For example, "ENG" indicates that data is generated by the engine ECU.

[0061] The "data type" is information for defining the nature of a "data value." The "data type" may include, for example, integer type, floating point type, logical type, character type, and the like.

[0062] The "data size" is information indicating how many bytes are used to express the "data value".

[0063] The “data value” is information indicating the value of a physical quantity identified by the “unique label”.

[0064] The "data unit" is information indicating the unit of a data value.

[0065] Furthermore, the “data value” is standardized so as to represent the same physical quantity in the same unit regardless of the vehicle type and vehicle manufacturer.

[0066] Furthermore, the “unique tag” may include information identifying “processed data” in addition to “raw data” obtained from the registered vehicle 8. “Processed data” is data converted into a format more easily understood by the user by performing a predetermined operation on one or more “raw data”.

[0067] Standardized vehicle data has a multi-layer structure. For example, Figure 4 As shown, the standardized vehicle data has "attribute information", "powertrain", "energy", "ADAS / AD", "body", "multimedia" and "others" as items set as the top first layer. ADAS is an abbreviation of Advanced Driver Assistance System. AD ​​is an abbreviation of Autonomous Driving. Each item belonging to the first layer represents the category of vehicle data.

[0068] like Figure 5 As shown, the standardized vehicle data may include a second layer and a third layer in addition to the first layer. The second layer is a layer directly below the first layer, and the third layer is a layer directly below the second layer.

[0069] For example, "attribute information" as an item of the first layer has "vehicle identification information", "vehicle attributes", "transmission configuration", and "firmware version" as items of the second layer. "Powertrain" as an item of the first layer has "accelerator pedal", "engine", and "engine oil" as items of the second layer. "Energy" as an item of the first layer has "battery status", "battery configuration", and "fuel" as items of the second layer. Each of these items belonging to the second layer also indicates the category of vehicle data.

[0070] For example, "vehicle identification information" as a second-layer item has "vehicle identification number", "body number" and "license plate number" as third-layer items. "Vehicle attributes" as a second-layer item have "brand name", "model" and "manufacturing year" as third-layer items. "Transmission configuration" as a second-layer item has "transmission type" as a third-layer item. Although omitted in the figure, "accelerator pedal" as a second-layer item has "accelerator pedal status", "accelerator pedal opening" and other items as third-layer items. "Engine" as a second-layer item has "engine status", "speed" and other items as third-layer items. Each of these third-layer items corresponds to a "unique label" in a standard format. In other words, each vehicle data is stored in correspondence with each item of the third layer. Each vehicle data belonging to standardized vehicle data is also referred to as an entry.

[0071] In this way, each item in the first layer contains one or more items in the second layer, and each item in the second layer contains one or more items in the third layer, that is, vehicle data.

[0072] For example, vehicle data whose "unique tag" is "vehicle identification information" is stored in a storage area in which the first layer is "attribute information", the second layer is "vehicle identification information", and the third layer is "vehicle identification number" in the standardized vehicle data.

[0073] The “others” as the first-level item may include, for example, position information acquired from a GPS device mounted on the registered vehicle 8 via the vehicle IF unit 22 , that is, latitude, longitude, and altitude.

[0074] Next, a description will be given of a procedure for the basic uploading unit 261 to upload vehicle data to the management server 3 .

[0075] For each vehicle data belonging to the standardized vehicle data, a transmission cycle for transmitting data to the management server 3 is set. The transmission cycle is set such that the more frequently changing data has a shorter transmission cycle, and / or the more important data has a shorter transmission cycle, based on the degree of data change and / or the importance of the data. In other words, each vehicle data is transmitted at a frequency corresponding to its characteristics. The transmission cycle is, for example, a 500 ms cycle, a 2 s cycle, a 4 s cycle, a 30 s cycle, a 300 s cycle, a 12 hour cycle, etc.

[0076] In addition, the transmission timing is set to a 250 ms cycle, for example. Each vehicle data is uploaded at the transmission timing determined according to the schedule. The schedule is set so that the transmission of a large number of vehicle data will not be concentrated at the same transmission timing.

[0077] <2-2-2. Application execution unit>

[0078] Return to Figure 3 Next, the application execution unit 27 will be described. The application execution unit 27 provides a function of executing application programs (hereinafter referred to as external applications) A1, A2, ... installed arbitrarily after installation. The application execution unit 27 includes a virtual environment platform 271 and a program library 272.

[0079] The virtual environment platform 271 has a function of simplifying the execution and management of containerized external applications Ai by virtualizing the OS of the system 25. The external applications Ai are executed on the virtual environment platform 271. The external applications Ai include a suspicious person detection application A1 and a smoking detection application A2.

[0080] The program library 272 is a program group for providing standardized functions commonly used by the external application Ai. The program library 272 includes an event notification program P1 and an image upload program P2. The event notification program P1 provides a function of sending an event notification to the service server 5 according to an instruction from the external application Ai. The image upload program P2 provides a function of uploading the image acquired by the acquisition device 222 to the service server 5 according to an instruction from the external application Ai.

[0081] <2-3. Content upload processing>

[0082] Reference Figure 6 The flowchart of FIG. 1 illustrates the content data upload process executed by the CPU 211 of the edge device 2. In the present embodiment, the content data upload process while the CPU 211 executes the suspicious person detection application A1 is described.

[0083] In addition, the CPU 211 may also perform the content data upload process while executing an external application Ai other than the suspicious person detection application A1. Other external applications Ai may include, for example, the smoking detection application A2. The CPU 211 may also execute the smoking detection application A2 and perform the above-mentioned upload process when smoking is detected.

[0084] In S10, the CPU 211 determines whether a suspicious person is detected. When the CPU 211 starts executing the suspicious person detection application A1, it determines whether the registered vehicle 8 is in a parked state. If the registered vehicle 8 is in a parked state, the CPU 211 activates the surrounding monitoring sensor 223 via the vehicle IF unit 22. When a moving object is detected by the surrounding monitoring sensor 223, the CPU 211 activates the acquisition device 222 via the vehicle IF unit 22 to start acquiring content. Then, the CPU 211 determines whether a suspicious person is detected based on the image included in the content acquired by the acquisition device 222.

[0085] Specifically, the CPU 211 detects a suspicious person when (i) the moving object is determined to be a person based on the image, and (ii) the moving object determined to be a person is present for a certain period of time or longer within the detection range of the surrounding monitoring sensor 223. The suspicious person here is a person other than a vehicle user who has been registered in advance as a user of the registered vehicle 8 equipped with the edge device 2.

[0086] When the CPU 211 determines in S10 that a suspicious person has not been detected, the process of S10 is repeatedly executed. When the CPU 211 determines that a suspicious person has been detected, the process proceeds to S20.

[0087] In S20, the CPU 211 reduces the data volume of the content acquired by the acquisition device 222 with the vehicle-mounted device reduction standard. In this embodiment, the acquired content is an image. The vehicle-mounted device reduction standard is equivalent to the reduction rate, reduction amount, or reduced data volume of the content data volume. That is, the CPU 211 reduces the data volume of the content from the start of the acquisition device 222 to the current time.

[0088] In the present embodiment, reduction is to reduce the amount of information of the content itself, in other words, to irreversibly reduce the amount of information of the content. That is, in the present embodiment, reduction does not include compression of the content that can return the amount of information to the original amount of information. Specifically, in the present embodiment, reduction is equivalent to cutting out a part of the information of the content, or thinning out the information of the content. Cutting out a part of the information of the content includes cutting out (or extracting) a part of the image, deleting the initial and final extracted middle parts of the image. Thinning out the information includes reducing the resolution / image quality, thinning out the frames of the image (for example, extracting one frame every five frames) to make it a continuous still picture.

[0089] In addition, in the present embodiment, the reduction criterion indicates the amount of reduction of the information of the content (i.e., the amount to be reduced), and / or the method of cutting out the amount of information, the method of thinning out the method. For example, the reduction criterion indicates the amount of reduction of the information of the content, such as 00 bytes, XX minutes, □□ frames. In addition, the reduction criterion indicates the method of reduction, such as deleting the first minute and the last minute, or reducing the full high definition (HD) image quality to the standard (SD) image quality.

[0090] In this embodiment, increasing the reduction standard is equivalent to increasing the amount of reduction of the content information, and further equivalent to increasing the reduction rate or reduction amount of the content. In addition, decreasing the reduction standard is equivalent to decreasing the amount of reduction of the content information, and further equivalent to decreasing the reduction rate or reduction amount of the content.

[0091] When the content is an image, the data volume of the content depends on the time, number of frames, and image quality (or resolution) of the image. When the content is an image, CPU211 reduces the data volume of the image by (i) shortening the image time, (ii) reducing the image quality, or (iii) culling the frames of the image based on the onboard machine reduction benchmark. The onboard machine reduction benchmark corresponds to the external application Ai being executed by CPU211. When the edge device 2 downloads the external application Ai from the service server 5, the onboard machine reduction benchmark is downloaded to the edge device 2 together with the external application Ai and the application ID of the external application Ai. The application ID and the onboard machine reduction benchmark are stored in the storage unit 24 of the edge device 2.

[0092] The amount of data required to implement the service varies depending on the service content provided by the service user. The service provided by the service user corresponds to the application executed by the CPU 211. Therefore, the CPU 211 changes the reduction rate, reduction amount, or reduced data amount of the content data associated with the application according to the application being executed.

[0093] For example, Figure 7 As shown, during the execution of the suspicious person detection application A1, the CPU 211 reduces the data volume of the content (specifically, the image) and generates a one-minute vehicle-mounted device partial content. The one-minute is centered on the time when the suspicious person is detected. In addition, during the execution of the smoking detection application A2, the CPU 211 reduces the data volume of the content and generates a ten-second vehicle-mounted device partial content. The ten seconds are centered on the time when the smoking is detected.

[0094] Next, in S30 , the CPU 211 associates the vehicle-mounted device partial content generated in S20 with the application ID and the edge device ID, uploads the content to the management server 3 , and ends the present process.

[0095] <3. Management Server>

[0096] <3-1. Hardware configuration>

[0097] like Figure 8 As shown, the management server 3 includes a control unit 31, a communication unit 32, and a storage unit 33. The management server 3 corresponds to the first management means of the present disclosure.

[0098] The control unit 31 includes a CPU 311, a ROM 312, and a RAM 313. The various functions of the control unit 31 are realized by the CPU 311 executing a program stored in a non-migrating physical recording medium. In this example, the ROM 312 corresponds to a non-migrating physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed.

[0099] The communication unit 32 performs data communication with the plurality of edge devices 2 and the service server 5 via the wide area communication network NW. The communication with the edge device 2 may use, for example, MQTT (Message Queue Telemetry Transport), a simple and lightweight publish / subscribe protocol.

[0100] The storage unit 33 is a database that stores vehicle data, content data, and the like provided from the edge device 2 .

[0101] <3-2. Functional structure>

[0102] like Fig. 9 As shown, the management server 3 has the functions of a vehicle-side unit 110 and a service-side unit 120 .

[0103] The method of realizing these functions of the management server 3 is not limited to software, and some or all of the elements may be realized by using one or more hardware. For example, when the above functions are realized by an electronic circuit as hardware, the electronic circuit may be realized by a digital circuit including a plurality of logic circuits, or an analog circuit, or a combination thereof.

[0104] The vehicle-side unit 110 includes a mobility gateway (hereinafter referred to as mobility GW) 111 .

[0105] Furthermore, the mobility GW 111 includes a shadow management unit 112 and a vehicle control unit 130. The shadow management unit 112 includes a function of managing a shadow 114 provided for each vehicle equipped with the edge device 2. The shadow 114 is generated based on standardized vehicle data transmitted from the edge device 2. The vehicle control unit 130 includes a function of controlling a registered vehicle 8 equipped with the edge device 2 according to an instruction from the service server 5.

[0106] The service-side unit 120 includes a data management unit 121 and an API providing unit 122. API is an abbreviation of Application Programming Interface: application program interface.

[0107] The data management unit 121 has a function of managing a digital twin 123 which is a virtual space for providing vehicle access that is not dependent on changes in the connection state of the vehicle. The digital twin 123 is one of the databases constructed on the storage unit 33 .

[0108] The API providing unit 122 is an interface for the service server 5 to access the mobility GW 111 and the data management unit 121 .

[0109] <3-2-1. Data storage function>

[0110] like Fig.10 As shown, the shadow management unit 112 includes a shadow creation unit 115 , a shadow storage unit 113 , a latest index creation unit 116 , and a latest index storage unit 117 as a configuration for realizing a function of accumulating vehicle data acquired from the edge device 2 .

[0111] The shadow generator 115 updates the standardized vehicle data by overlaying the transmitted vehicle data on the corresponding area of ​​the structured standardized vehicle data every time the vehicle data is transmitted from the edge device 2. In other words, the standardized vehicle data is set for each vehicle and updated asynchronously.

[0112] The shadow generator 115 uses the updated standardized vehicle data to generate new shadows 114 for all vehicles at the same time at a constant cycle. The shadow generator 115 stores the generated shadows 114 in the shadow storage 113. Thus, the shadow storage 113 stores multiple shadows 114 generated in time series for each vehicle. In other words, the shadow 114 can be regarded as a shadow that replicates the state of the vehicle equipped with the edge device 2, 200 at a certain moment.

[0113] like Fig.11 As shown, the shadow 114 includes a vehicle data storage unit 114a and a device data storage unit 114b.

[0114] The vehicle data storage unit 114 a stores “object-id”, “Shadow_version”, and “mobility-data” as data related to a vehicle on which the edge device 2 or 200 is mounted (hereinafter referred to as a mounted vehicle).

[0115] "object-id" is a character string that identifies the vehicle being loaded and functions as a partition key.

[0116] “Shadow_version” is a numerical value indicating the version of the shadow 114 , and a timestamp indicating the time of creation is set every time the shadow 114 is created.

[0117] “Mobility-data” is the value of the standardized vehicle data at the time indicated by the timestamp.

[0118] The device data storage unit 114 b stores “object-id”, “update_time”, “version”, “power_status”, “power_status_timestamp”, and “notify_reason” as data related to hardware, software, and status mounted in the edge device 2 .

[0119] "object-id" is a character string that identifies the vehicle being loaded and functions as a partition key.

[0120] “update_time” is a numerical value indicating the update time of hardware and software.

[0121] "version" is a character string indicating the version of hardware and software.

[0122] “power_status” is a character string indicating the system status of the edge device 2. Specifically, there are a “power-on” state in which all functions can be used, and a low-power “power-off” state in which some functions are stopped.

[0123] "power_status_timestamp" is a numerical value indicating the time of notification of the system status.

[0124] "notify_reason" is a character string indicating the reason for notification.

[0125] When the “version”, “power_status”, “notify_reason” and the like stored in the device data storage unit 114 b are changed, the edge device 2 notifies the change separately from the standardized vehicle data.

[0126] Back to Fig.10 , the latest index creation unit 116 is described. The latest index creation unit 116 obtains the latest shadow 114 by vehicle from the shadow storage unit 113, and creates the latest index 118 using the acquired shadow 114. Then, the latest index creation unit 116 stores the created latest index 118 in the latest index storage unit 117. In the latest index storage unit 117, one latest index 118 is stored by vehicle (i.e., for each object-id).

[0127] like Fig.12 As shown, the latest index 118 stores “gateway-id”, “object-id”, “shadow-version”, “vin”, “location-lon”, “location-lat”, and “location-alt”.

[0128] “Object-id” and “shadow-version” are the same as the data described in the shadow 114 .

[0129] "gateway-id" is information for identifying the mobility GW 111. When there are a plurality of management servers 3, for example, provided for each country, this is information for identifying these management servers.

[0130] "vin" is a unique registration number assigned to the vehicle on which the vehicle is mounted.

[0131] "Location-lon" is information indicating the latitude of the vehicle on board.

[0132] “Location-lat” is information indicating the longitude of the vehicle on board.

[0133] "location-alt" is information indicating the height at which the mounted vehicle is located.

[0134] Back to Fig.10 Next, the data management unit 121 is described. The data management unit 121 includes an index creation unit 124 and an index storage unit 125. The index creation unit 124 and the index storage unit 125 correspond to a configuration that realizes a function of storing the latest index 118 acquired from the shadow management unit 112 as an index 126.

[0135] The index generating unit 124 obtains the latest index 118 from the latest index storage unit 117 according to a preset acquisition schedule, and uses the obtained latest index 118 to generate an index 126 for the digital twin 123. Then, the index generating unit 124 stores the generated indexes 126 in the index storage unit 125 in sequence. Thus, in the index storage unit 125, a plurality of indexes 126 generated in a time series are stored for each vehicle. In other words, the indexes 126 stored in the index storage unit 125 respectively represent vehicles existing in the virtual space-time, i.e., the digital twin 123.

[0136] like Fig.13As shown, the index 126 stores “timestamp”, “schedule-type”, “gateway-id”, “object-id”, “shadow-version”, “vin”, “location”, and “alt”.

[0137] “timestamp” is a timestamp indicating the time when the index 126 was created in milliseconds.

[0138] "Schedule-type" indicates whether the scheduler of the data creation source is periodic or event. In the case of periodicity, "schedule-type" is set to "Repeat", and in the case of event, "schedule-type" is set to "Event".

[0139] “gateway-id”, “object-id”, “shadow-version”, and “vin” are information transferred from the latest index 118 .

[0140] “location” is information taken over from “location-lon” and “location-lat” of the latest index 118 , and “alt” is information taken over from “location-alt” of the latest index 118 .

[0141] <3-2-2. Data provision function>

[0142] like Fig. 9 as well as Fig.10 As shown, the service-side unit 120 includes an API providing unit 122. The API providing unit 122 is an interface prepared to allow an external service user to use the functions and / or data of the management server 3 via the service server 5 or the like.

[0143] like Fig.10 As shown, the API providing unit 122 includes an authentication information storage unit 141, an authorization information storage unit 142, a vehicle identification information storage unit 143, and an authentication processing unit 144. In addition, as types of APIs provided to service users, a login API 145, a data acquisition API 146, and a vehicle control API 148 are provided.

[0144] The authentication information storage unit 141 stores the "authentication information" in association with the "service user ID." The "service user ID" is identification information for uniquely identifying a service user. The "authentication information" is a preset password.

[0145] The authorization information storage unit 142 stores “authorization information” in association with the “service user ID.” The “authorization information” is information that specifies, for each service user, a range of services that can be used among all services provided by the management server 3 .

[0146] The vehicle identification information storage unit 143 stores table information in which “object-id” uniquely assigned to a mounted vehicle and “vin” of the mounted vehicle are associated with each other.

[0147] The authentication processing unit 144 executes authentication processing when an authentication request is made via the login API 145 , and executes authorization processing when an access request is made via the data acquisition API 146 and the vehicle control API 148 .

[0148] The login API 145 is used when logging into the management server 3. When the login API 145 accepts an authentication request from the service user, the authentication processing unit 144 performs authentication processing. In the authentication processing, the "service user ID" and "authentication information" input through the login API 145 are compared with the registration content of the authentication information storage unit 141. If the comparison result shows that the information is consistent, that is, if the authentication is successful, access to the management server 3 is permitted.

[0149] Data acquisition API 146 Fig. 9 As shown in L1 in FIG. 1 , this is an API used to access the vehicle data (i.e., the index 126 and the shadow 114) stored in the management server 3. The vehicle control API 148 is as shown in FIG. Fig. 9 L2 in FIG. 1 is an API used to access the mounted vehicle.

[0150] The data acquisition API 146 and the vehicle control API 148 may also perform authorization processing when receiving an access request from a service user. The authorization processing is a process of permitting or rejecting an access request based on the authority previously granted to the service user.

[0151] In addition, in the data acquisition API 146 and the vehicle control API 148, either "object-id" or "vin" can be used as information for identifying a vehicle. When "vin" is used as information for identifying a vehicle, the information for identifying a vehicle can be converted from "vin" to "object-id" by referring to the vehicle identification information storage unit 143.

[0152] <3-2-3. Data acquisition function>

[0153] like Fig.10As shown, the management server 3 includes an index acquisition unit 127 and a data acquisition unit 119 as a configuration for processing an access request (hereinafter referred to as a data acquisition request) via the data acquisition API 146 .

[0154] The following describes a data acquisition process performed by the index acquisition unit 127 and the data acquisition unit 119 when the data acquisition API 146 accepts a data acquisition request from a service user.

[0155] The data acquisition request includes vehicle specifying information, time specifying information, and data specifying information.

[0156] The vehicle specifying information is information for specifying a vehicle that is a source of vehicle data (hereinafter referred to as a target vehicle). The vehicle specifying information includes a method of listing the vehicle IDs (i.e., object-id or vin) of the target vehicles in a list format and a method of specifying a geographical area (hereinafter referred to as area specification) where the target vehicle exists.

[0157] The time specification information is information that specifies the timing of generating data. The time specification information is represented by a time point that becomes a starting point and a range. For example, the range is a value that represents the time width by an integer greater than 1, with the generation cycle of the latest index 118 as a unit time.

[0158] The data designation information is information that designates the acquired data. The data designation information can be expressed by showing the item names of the data shown in the standardized vehicle data in a list form, or by specifying the category name shown in the standardized vehicle data. Specifying a category name is equivalent to specifying all items belonging to the category. In addition, not specifying either the item name or the category name is equivalent to specifying all items.

[0159] In addition, the method of setting the vehicle specifying information, the time specifying information, and the data specifying information shown here is an example, and is not limited to the above method.

[0160] The index acquisition unit 127 extracts all the indexes 126 having a “timestamp” within the time range indicated by the time specifying information for all the vehicles specified by the vehicle specifying information indicated by the data acquisition request.

[0161] The index acquisition unit 127 generates shadow identification information by combining “object-id” and “shadow-version” indicated by the index 126 for each extracted index 126. Thus, a shadow list listing shadow identification information is generated.

[0162] The index acquisition unit 127 outputs a shadow access request in which the data specifying information indicated by the data acquisition request is added to the generated shadow list to the data acquisition unit 119 of the shadow management unit 112 .

[0163] In other words, the index acquisition unit 127 generates a shadow list based on the vehicle specified information and time specified information shown in the data acquisition request from the data acquisition API 146 as acquisition conditions. In addition, the index acquisition unit 127 outputs a shadow access request combining the generated shadow list and the data specified information to the data acquisition unit 119.

[0164] When the data acquisition unit 119 receives the shadow access request from the index acquisition unit 127, it extracts the shadows 114 corresponding to the shadow identification information shown in the shadow list of the shadow access request with reference to the shadow storage unit 113. Furthermore, the data acquisition unit 119 extracts the data shown in the data designation information of the shadow access request, i.e., the designated data, from each extracted shadow 114, and returns the extracted designated data to the data acquisition API 146 that is the request source as the access result.

[0165] <3-2-4. Vehicle control function>

[0166] like Fig.10 As shown, the management server 3 includes a vehicle control unit 130 as a configuration for processing an access request (hereinafter referred to as a vehicle control request) via a vehicle control API 148 .

[0167] The following describes the vehicle control process performed by the vehicle control unit 130 when the vehicle control API 148 accepts a vehicle control request from a service user.

[0168] The vehicle control request includes vehicle specifying information, execution target information, and control specifying information. The vehicle control request may further include priority information, time limit information, and vehicle authentication information.

[0169] The vehicle specifying information includes one vehicle ID. The vehicle specified by the vehicle ID is the target vehicle to be controlled.

[0170] The execution target information specifies which application installed in the registered vehicle 8 is to execute the control content indicated by the control designation information. The execution target information includes an application ID for identifying the application.

[0171] The control designation information includes the content of the specific control to be executed by the registered vehicle 8. For example, the control designation information may include key operations of various doors such as the doors of each seat and the trunk door, operations of acoustic devices such as horns and buzzers, operations of various lights such as headlights and hazard lights, operations of the acquisition device 222 and various sensors such as radars. The control designation information may include one control or may include multiple controls to be executed continuously in a list format. In addition, multiple controls in a list format are executed sequentially according to the list.

[0172] The priority information indicates the priority when a control instruction generated based on the vehicle control request is transmitted to the registered vehicle 8. The priority information may be set by a service user who is the request source, or may be automatically set according to the content of the control indicated by the control designation information.

[0173] The time limit information indicates the final time at which control in the registered vehicle 8 is permitted. For example, the time limit information is set as the time when the vehicle control request is input + 10 minutes. The time limit information, like the priority information, can be set by the service user who is the request source or automatically set according to the content of the control requested for the vehicle.

[0174] The vehicle authentication information is information for determining whether the target vehicle can accept the control instruction, and may include an owner ID and a password for identifying the owner of the target vehicle. The vehicle authentication information is held in the registered vehicle 8 and also in the service user who is allowed to access the vehicle.

[0175] When a vehicle control request is input from the vehicle control API 148 , the vehicle control unit 130 transmits one or more control instructions generated based on the vehicle control request to the target vehicle.

[0176] When receiving the control instruction from the management server 3 , the edge device 2 compares the vehicle authentication information indicated by the control instruction with the vehicle authentication information of the own vehicle to perform authentication.

[0177] When the edge device 2 is successfully authenticated, the edge device 2 causes the application program specified by the execution designation information to execute the control included in the control designation information. In addition, the edge device 2 sends a response including the execution result of the control to the management server 3.

[0178] The vehicle control unit 130 that has received the response returns the response content to the vehicle control API 148 .

[0179] <3-3. Data storage processing>

[0180] Reference Fig.14The flowchart of FIG. 1 illustrates the content storage process executed by the CPU 311 of the management server 3. The CPU 311 repeatedly executes the content storage process in a predetermined cycle.

[0181] In S100, the CPU 311 determines whether the vehicle-mounted device partial content is uploaded from the edge device 2 to the management server 3. That is, the CPU 311 determines whether the vehicle-mounted device partial content is received from the edge device 2. If the CPU 311 determines that the vehicle-mounted device partial content is uploaded, it proceeds to the processing of S110, and if it determines that the vehicle-mounted device partial content is not uploaded, it repeatedly executes the processing of S100.

[0182] In S110 , the CPU 311 checks the service user type corresponding to the uploaded vehicle-mounted device partial content, specifically, the service user ID. The service user type corresponds to a group divided by grouping related to a plurality of vehicle-mounted devices, and a plurality of end users provided with services by a service operator via the service server 5 belong to the group.

[0183] The service user provides a predetermined service to one or more end users associated with the plurality of edge devices 2. The end user receives the predetermined service by executing one or more applications on one or more edge devices 2, respectively.

[0184] For example, Figure 7 As shown, service user AAA provides fleet service a, which is bundled with a first edge device group, a first vehicle group, or a first vehicle user group related to fleet service a. Service user BBB provides car sharing service b, which is bundled with a second edge device group, a second vehicle group, or a second vehicle user group related to car sharing service b. The first edge device group is equivalent to a plurality of edge devices 2 having a plurality of edge device IDs including "XXX" and "YYY". The first vehicle group is equivalent to a plurality of registered vehicles 8 equipped with the first edge device group. The first vehicle user group is equivalent to one or more vehicle users of the first vehicle group. The second edge device group is equivalent to a plurality of edge devices 2 having a plurality of edge device IDs including "ZZZ". The second vehicle group is equivalent to a plurality of registered vehicles 8 equipped with the second edge device group. The second vehicle user group is equivalent to one or more vehicle users of the second vehicle group.

[0185] Furthermore, a group corresponding to a service user may also be divided into multiple subgroups according to a specified feature. The specified feature may be, for example, the type of vehicle, and a group corresponding to a service user may also be divided into a light vehicle group, an ordinary vehicle group, and a truck group. That is, a service user may also divide a group providing the same type of service into multiple subgroups, and set differences in the content of the service by subgroup. For example, a service user AAA may also change the content of the fleet service provided to the ordinary vehicle group to the content of the fleet service provided to the truck group.

[0186] like Figure 7 As shown, the management server 3 associates the application ID, service user ID, first management unit reduction standard, and edge device ID with each other and stores them in the storage unit 33. The management server 3 refers to the storage unit 33 to obtain the service user ID corresponding to the edge device ID associated with the vehicle-mounted device partial content.

[0187] In S120, CPU311 reduces the vehicle-mounted machine partial content uploaded to the management server 3 using the first management unit reduction benchmark to generate the first management unit partial content. The first management unit reduction benchmark is equivalent to the reduction rate, reduction amount, or reduced data amount of the vehicle-mounted machine partial content. The first management unit reduction benchmark varies according to the identification information of the group that bundles multiple edge devices 2, multiple registered vehicles 8, or multiple vehicle users, such as the service user ID. For example, the management server 3 sets the first management unit reduction benchmark for each service user according to the contract content, and stores it in the storage unit 33 in association with the service user ID. CPU311 uses the first management unit reduction benchmark corresponding to the service user type confirmed in S110.

[0188] CPU311 reduces the data volume of the vehicle-mounted device content by (i) shortening the image time of the vehicle-mounted device content, (ii) reducing the image quality of the vehicle-mounted device content, or (iii) eliminating frames of the vehicle-mounted device content based on the first management unit reduction benchmark corresponding to the service user ID confirmed in S110.

[0189] The amount of data required for the content varies depending on the service content provided by the service user. Therefore, the contract related to the amount of data stored in the management server 3 varies according to the service user. For example, Figure 7 As shown, the service user AAA signs a one-minute content preservation agreement with the management server 3 regarding the suspicious person detection application A1. Therefore, the management server 3 reduces the first vehicle-mounted machine partial content and generates a first management unit partial content of one minute. The first vehicle-mounted machine partial content is content uploaded from the edge device 2 having an edge device ID of "XXX" or "YYY". In addition, the service user BBB reduces the second vehicle-mounted machine partial content and generates a first management unit partial content of thirty seconds. The second vehicle-mounted machine partial content is content uploaded from the edge device 2 having an edge device ID of "ZZZ".

[0190] In addition, when a group corresponding to one service user includes a plurality of subgroups, a first management unit reduction standard is set for each subgroup. Therefore, the CPU 311 changes the reduction amount of the data volume for each subgroup. The CPU 311 reduces the vehicle-mounted device partial content by the corresponding first management unit reduction standard for each subgroup to generate the first management unit partial content.

[0191] In addition, the data volume of the first management unit partial content does not necessarily need to be reduced compared to the data volume of the vehicle-mounted device partial content, and may be the same as the data volume of the vehicle-mounted device partial content. For example, when both the vehicle-mounted device reduction criterion and the first management unit reduction criterion are one minute of video time, the first management unit partial content is not reduced from the vehicle-mounted device partial content, but becomes the same as the vehicle-mounted device partial content.

[0192] Next, in S130 , the CPU 311 associates the first management unit partial content generated in S120 with the application ID, the edge device ID, and the service user ID, and stores the association in the storage unit 33 .

[0193] Next, in S140, the CPU 311 determines whether there is any content request from the service server 5. If the CPU 311 determines that there is a content request, it proceeds to S150, and if it determines that there is no content request, it repeatedly executes the process of S140.

[0194] In S150, CPU 311 confirms the service user who requested the content. That is, CPU 311 confirms the service user ID associated with service server 5 (i.e., service user) who requested the content. Then, CPU 311 sends the first management unit partial content used by the service user to the service server 5 of the confirmed service user.

[0195] Next, in S160, CPU 311 determines whether the storage period of each of the stored first management unit partial contents exceeds the prescribed period. When the storage period of all the first management unit partial contents is less than the prescribed period, CPU 311 repeatedly executes the processing of S160. When the storage period of any one of the first management unit partial contents exceeds the prescribed period, CPU 311 proceeds to the processing of S170.

[0196] In S170, the CPU 311 deletes the first management unit partial content whose storage period exceeds the prescribed period from the storage unit 33, and ends the present process. In addition, in S160, the CPU 311 may determine whether the number of transmissions of each of the stored first management unit partial contents exceeds the set number of times instead of determining whether the storage period exceeds the prescribed period. The number of transmissions is the number of times the first management unit partial content is transmitted from the management server 3 to the service server 5. Furthermore, in S170, the CPU 311 may delete the first management unit partial content whose number of transmissions exceeds the set number of times from the storage unit 33.

[0197] <4. Service Server>

[0198] <4-1. Hardware configuration>

[0199] like Fig.15 As shown, the service server 5 includes a control unit 51, a communication unit 52, and a storage unit 53. The service server 5 corresponds to the second management means of the present disclosure.

[0200] The control unit 51 includes a CPU 511, a ROM 512, and a RAM 513. The various functions of the control unit 51 are realized by the CPU 511 executing a program stored in a non-migrating physical recording medium. In this example, the ROM 512 corresponds to a non-migrating physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed.

[0201] The communication unit 52 communicates with the edge device 2, the management server 3, and the terminal device 7 via the wide area communication network NW. In addition, the communication with the terminal device 7 may use a network different from the network used for communication with the management server 3.

[0202] The storage unit 53 stores various information required for providing services.

[0203] <4-2. Functional structure>

[0204] like Fig.16 As shown, the service server 5 includes a data collection unit 61, a remote operation unit 62, and an event management unit 63. In addition, the service server 5 includes a plurality of databases (hereinafter referred to as DBs), specifically, a vehicle DB 531, an image DB 532, a user DB 533, a map DB 534, and a geo-fence DB 535.

[0205] The vehicle DB531 stores the vehicle data acquired by the data collection unit 61 from the management server 3. The image DB532 stores the image data uploaded from the edge device 2. The user DB533 stores information related to the driver of the registered vehicle 8, that is, the driver information. The driver information includes the vehicle ID of the registered vehicle 8 corresponding to the driver, and the contact method to the terminal device 7 (for example, a telephone number, an email address, etc.). The map DB534 stores the map information used for navigation, etc. The geo-fence DB535 stores the geo-fence set based on the position of the registered vehicle 8 stored in the vehicle DB531 and the map information stored in the map DB534. The geo-fence is an area surrounded by a virtual geographic boundary line.

[0206] The data collection unit 61 repeatedly acquires the position information of all registered vehicles 8 using the data acquisition API provided by the management server 3 , and stores the latest position information of each registered vehicle 8 in the vehicle DB 531 .

[0207] The remote operation unit 62 executes vehicle control of the designated registered vehicle 8 using the vehicle control API 148 provided by the management server 3 in accordance with an instruction from the terminal device 7 .

[0208] Upon receiving an event notification from the edge device 2 , the event management unit 63 executes a process corresponding to the content of the event notification.

[0209] <4-3. Content acquisition processing>

[0210] Reference Fig.17 The flowchart of FIG. 5 illustrates the content acquisition process executed by the CPU 511 of the service server 5. The CPU 511 repeatedly executes the content acquisition process in a predetermined cycle.

[0211] In S200 , the CPU 511 requests the management server 3 to which the service user has contracted for content corresponding to the contracted content.

[0212] In S210 , the CPU 511 acquires the first management unit partial content transmitted from the management server 3 .

[0213] In S220, the CPU 511 confirms the end user type corresponding to the first management unit partial content obtained in S210, specifically, confirms the end user ID. Figure 7 As shown, the service server 5 of the service user AAA associates the application ID, the end user ID, the edge device ID, the membership level and the second management unit reduction standard with each other and stores them in the storage unit 53. The CPU 511 obtains the end user ID corresponding to the edge device ID associated with the first management unit part content. The end user type is equivalent to the identification information of the end user or the vehicle-mounted device or the vehicle user who uses the service disclosed in the present invention.

[0214] Next, in S230, the CPU 511 reduces the received first management unit partial content with the second management unit reduction standard to generate the second management unit partial content. The second management unit reduction standard is equivalent to the reduction rate, reduction amount, or reduced data amount of the data volume of the first management unit partial content. The second management unit reduction standard changes according to the end user ID, etc. That is, the second management unit reduction standard changes according to the identification information of the end user, edge device 2, registered vehicle 8, or vehicle user corresponding to the service provided by the service server 5.

[0215] The service user assigns membership levels to the end users respectively, and associates the end user ID with the membership level. Furthermore, the service user changes the content of the services provided according to the membership level. For example, the service user provides more substantial services to the end users with higher membership levels than to the end users with lower membership levels. Therefore, the service reduction standard is changed according to the membership level, and the CPU 511 reduces the reduction amount of the data volume as the membership level corresponding to the end user ID becomes higher.

[0216] CPU511 reduces the data volume of the partial content of the first management unit by (i) shortening the image time of the partial content of the first management unit, (ii) reducing the image quality of the partial content of the first management unit, or (iii) eliminating frames of the partial content of the first management unit, based on the second management unit reduction benchmark corresponding to the end user ID confirmed in S220.

[0217] For example, Figure 7 As shown, in order to provide services to the end user MMM who is a premium member, the CPU 511 reduces the data volume of the first management unit partial content and generates a second management unit partial content of one minute. That is, the CPU 511 generates a second management unit partial content of one minute based on the first management unit partial content based on the content uploaded from the edge device 2 having the edge device ID "XXX". The edge device ID "XXX" is associated with the end user MMM.

[0218] In addition, in order to provide a service to the end user NNN who is a trial member, the CPU 511 reduces the data volume of the first management unit partial content and generates a second management unit partial content of ten seconds. That is, the CPU 511 generates the second management unit partial content of ten seconds based on the first management unit partial content based on the content uploaded from the edge device 2 having the edge device ID "YYY".

[0219] Furthermore, the data volume of the second management unit partial content does not necessarily need to be reduced compared to the data volume of the first management unit partial content, and may be the same as the data volume of the first management unit partial content. When both the second management unit reduction criterion and the first management unit reduction criterion are one minute of video time, the second management unit partial content is not reduced from the first management unit partial content, but becomes the same as the first management unit partial content.

[0220] Next, in S240 , the CPU 511 stores the second management unit partial content generated in S230 in the storage unit 53 .

[0221] Next, in S250, the CPU 511 determines whether there is access to data from the end user's terminal device 7. If the CPU 511 determines that there is access, it proceeds to the process of S260, and if it determines that there is no access, it repeatedly executes the process of S250.

[0222] In S260, the CPU 511 determines the end user who has accessed the data based on the end user ID assigned to the access. Furthermore, the CPU 511 sends the terminal content to the corresponding terminal device 7 based on the second management unit partial content corresponding to the end user who has accessed the data. The terminal content can be the same as the second management unit partial content or it can be the content processed from the second management unit partial content. In addition, in this embodiment, the second management unit partial content is equivalent to the service partial content of the present disclosure.

[0223] <5. Terminal device>

[0224] The terminal device 7 is installed with a terminal application. The terminal application includes a graphical user interface (hereinafter referred to as GUI), and has functions of displaying notifications from the service server 5, playing images in the vehicle cabin, and instructing the service server 5 to control the vehicle.

[0225] The GUI of the terminal application displays a video viewing screen, menu buttons, etc. The menu buttons include a video playback button and a vehicle control button.

[0226] If the terminal application receives a suspicious person detection notification, a smoking detection notification, etc., in addition to displaying an icon indicating that the detection notification has been received on the display screen of the terminal device 7, an acoustic device installed in the terminal device 7 can also be used to make a report based on sound or vibration.

[0227] When the terminal device 7 receives the video upload notification from the service server 5, the terminal application enables the video playback button. When the enabled video playback button is operated, the terminal application plays the in-vehicle video on the video viewing screen.

[0228] If the in-vehicle image is played, the terminal application enables the vehicle control button. If the vehicle control button that becomes effective is operated, the terminal application instructs the service server 5 to perform vehicle control. When there are multiple vehicle controls that can be implemented, vehicle control buttons can also be prepared according to the type of vehicle control.

[0229] <6. Action>

[0230] Reference Fig.18 as well as Fig.19 The sequence diagram illustrates the overall operation of the mobility IoT system 100.

[0231] <6-1. Normal operation>

[0232] like Fig.17 As shown, in normal times, the edge device 2 repeatedly transmits the vehicle data of the registered vehicle 8 equipped with the edge device 2 to the management server 3 according to a schedule.

[0233] The mobility GW 111 of the management server 3 accumulates the received vehicle data as a shadow 114 and generates a latest index 118. The data management unit 121 of the management server 3 accumulates the latest index 118 as a digital twin 123. The digital twin 123 includes at least identification information and location information of all mounted vehicles.

[0234] In other words, on the management server 3 on the cloud, the vehicle data of all vehicles equipped with the edge device 2 are sequentially updated and accumulated as shadows 114 and digital twins 123 .

[0235] The data collection unit 61 of the service server 5 repeatedly acquires the position information of the registered vehicle 8 during the execution of the suspicious person detection application A1 using the data acquisition API 146 provided by the management server 3 , and stores the latest position information in the vehicle DB 531 .

[0236] In addition, the data acquisition request input to the data acquisition API 146 sets, for example, the service provision range as the location specifying information, the current time as the time specifying information, and the location information as the acquisition information. Then, the data management unit 121 generates an object list specifying the object IDs of all registered vehicles 8 existing in the service provision range and the current time. Then, the mobility GW 111 extracts the latest location information from the shadow 114 based on the object list and sends it back to the service server 5.

[0237] <6-2. Actions when an event is detected>

[0238] like Fig.19 As shown, when the edge device 2 starts executing the suspicious person detection application A1, it starts acquiring content based on the acquisition device 222. When the edge device 2 detects a suspicious person based on the content acquired by the acquisition device 222, it reduces the data volume of the content based on the vehicle-mounted device reduction standard and generates vehicle-mounted device partial content. The edge device 2 uploads the generated vehicle-mounted device partial content to the management server 3.

[0239] The management server 3 confirms the type of service user corresponding to the uploaded vehicle-mounted device partial content, reduces the data volume of the vehicle-mounted device partial content by the first management unit reduction standard corresponding to the confirmed service user type, generates the first management unit partial content, and stores it in the storage unit 33.

[0240] In order to use the content of the management server 3, the service server 5 requests authentication from the management server 3. The management server 3 performs authentication processing of the service server 5, and if the authentication is successful, sends an authentication OK to the service server 5. If the service server 5 receives the authentication OK, it requests the content from the management server 3. The management server 3 confirms the service user corresponding to the service server 5. The management server 3 sends the first management unit partial content corresponding to the confirmed service user to the service server 5.

[0241] The service server 5 confirms the type of the end user corresponding to the received first management unit content, reduces the data size of the first management unit content by a second management unit reduction criterion corresponding to the confirmed type of the end user, generates a second management unit content, and stores it in the storage unit 53.

[0242] The terminal device 7 accesses data of the service server 5 to receive services from the service server 5. The service server 5 transmits terminal content based on the second management unit partial content corresponding to the end user of the terminal device 7 to the terminal device 7.

[0243] <7. Effect>

[0244] According to the present embodiment described in detail above, the following effects are achieved.

[0245] (1) The edge device 2 reduces the data volume of the content based on the vehicle-mounted device reduction standard, thereby reducing the communication volume between the edge device 2 and the management server 3. In addition, the management server 3 reduces the data volume of the uploaded vehicle-mounted device portion of the content based on the first management unit reduction standard and stores it, thereby reducing the amount of data stored in the management server 3, and reducing the communication volume between the management server 3 and the service server 5. The service server 5 reduces the data volume of the received first management unit portion of the content based on the second management unit reduction standard and stores it, thereby reducing the amount of data stored in the service server 5.

[0246] (2) The service server 5 increases the amount of data of the second management unit portion used for providing services to end users as the level of the end users increases. This allows the service server 5 to provide higher quality services to end users with higher levels.

[0247] (3) The management server 3 can change the reduction degree of the first management unit partial content according to the service user who provides the first management unit partial content. That is, the management server 3 can change the reduction degree of the first management unit partial content according to the service provided to the end user. Therefore, the end user can receive appropriate services from the service user.

[0248] (4) By dividing the group of end users who receive the same type of service into a plurality of subgroups, the management server 3 can change the reduction degree of the first management unit content for each subgroup. As a result, the service provider can provide more appropriate services to the end users.

[0249] (5) When the content includes video, the data volume of the content can be reduced by shortening the video time, reducing the image quality, or thinning out the frames.

[0250] (6) The management server 3 can suppress the amount of data stored in the storage unit 33 by deleting from the database the first management unit partial content whose storage period exceeds the set period.

[0251] (7) The management server 3 can suppress the amount of data stored in the storage unit 33 by deleting from the database the first management unit partial content that has been sent to the service server 5 more than a set number of times.

[0252] (Other Embodiments)

[0253] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, Various deformation|transformation can be made and it can be implemented.

[0254] (a) In the above embodiment, the management server 3 reduces the data volume of the vehicle-mounted device partial content, but the management server 3 may not reduce the data volume of the vehicle-mounted device partial content. That is, the management server 3 may also save the vehicle-mounted device partial content as the first management unit partial content and send it to the service server 5.

[0255] (b) In the above embodiment, the service server 5 reduces the data size of the first management unit partial content, but the service server 5 may not reduce the data size of the first management unit partial content. That is, the service server 5 may save the first management unit partial content as the second management unit partial content and send it to the terminal device 7.

[0256] (c) In the above embodiment, the CPU 311 of the management server 3 deletes the first management unit partial content whose storage period exceeds the set period or the first management unit partial content whose transmission frequency exceeds the set number of times from the storage unit 33, but the CPU 511 of the service server 5 may also delete the second management unit partial content from the storage unit 53 in the same manner. That is, the CPU 511 may also delete the second management unit partial content whose storage period exceeds the set period or the second management unit partial content whose transmission frequency exceeds the set number of times from the storage unit 53.

[0257] (d) The control units 21, 31, 51 and methods described in the present disclosure may also be implemented by a dedicated computer provided by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the control units 21, 31, 51 and methods described in the present disclosure may also be implemented by a dedicated computer provided by a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control units 21, 31, 51 and methods described in the present disclosure may also be implemented by one or more dedicated computers composed of a combination of a processor and a memory programmed to execute one or more functions and a processor composed of one or more hardware logic circuits. In addition, a computer program may also be stored as an instruction executed by a computer in a non-migratable tangible recording medium that can be read by a computer. The method for implementing the functions of each unit included in the control unit 21, 31, 51 does not necessarily need to include software, and all of its functions may be implemented using one or more hardware.

[0258] (e) It is also possible to realize multiple functions of one component in the above-mentioned embodiment by multiple components, or realize one function of one component by multiple components. In addition, it is also possible to realize multiple functions of multiple components by one component, or realize one function realized by multiple components by one component. In addition, it is also possible to omit part of the structure of the above-mentioned embodiment. In addition, it is also possible to add or replace at least part of the structure of the above-mentioned embodiment with the structure of other above-mentioned embodiments.

[0259] (f) In addition to the above-mentioned mobility system, the present disclosure can also be implemented in various ways, such as various programs for enabling the vehicle-mounted device, management server, and service server included in the mobility system to function respectively, and non-migrating physical recording media such as semiconductor memories that record these programs.

[0260] [Technical ideas disclosed in this specification]

[0261] [Project 1]

[0262] A mobility service system comprises an on-board device (2A, 2B) and a management server (3, 5A, 5B), wherein the on-board device (2A, 2B) comprises an acquisition device (222) for acquiring content including images or sounds and is mounted on a vehicle (8A, 8B), and the management server (3, 5A, 5B) is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the above-mentioned vehicle. In the mobility service system (100),

[0263] The above-mentioned vehicle-mounted device has:

[0264] an execution unit (211, 27) configured to execute an application program;

[0265] an event detection unit (211, S10) configured to detect an event related to the application program while the execution unit is executing the application program;

[0266] a vehicle-mounted device-side reduction unit (211, S20) configured to reduce the data volume of the content acquired by the acquisition device according to a vehicle-mounted device reduction standard corresponding to the application program when the event is detected by the event detection unit, and generate vehicle-mounted device partial content; and

[0267] The uploading unit (211, S30) is configured to upload the vehicle-mounted device partial content generated by the vehicle-mounted device side reduction unit to the management server,

[0268] The above management server has:

[0269] A server-side reduction unit (311, 511, S120, S230) configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit according to a server reduction standard corresponding to the information related to the vehicle-mounted device, and generate a server partial content; and

[0270] The terminal sending unit (511, S260) is configured to send terminal content to a terminal device (7A, 7B) of an end user who uses a service corresponding to the application based on the server partial content generated by the server-side reduction unit.

[0271] [Item 2] A mobility service system according to Item 1, wherein:

[0272] The management server (3, 5A, 5B) comprises a first management unit (3) and a second management unit (5A, 5B),

[0273] The server reduction criteria include a first management unit reduction criteria determined based on grouping related to a plurality of vehicle-mounted devices.

[0274] The first management unit comprises:

[0275] A first management unit reduction unit (311, S120), included in the server-side reduction unit, and configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit (211, S30) based on the first management unit reduction standard to generate the first management unit partial content;

[0276] A storage unit (33) configured to store the first management unit partial content generated by the first management unit reduction unit; and

[0277] The first sending unit (311, S150) is configured to send the first management unit partial content corresponding to the request among the first management unit partial content stored in the storage unit to the second management unit according to the request from the second management unit.

[0278] The second management unit comprises:

[0279] A receiving unit (511, S210) configured to receive the partial content of the first management unit sent by the first sending unit; and

[0280] The terminal sending unit (511, S260),

[0281] The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the first management unit partial content.

[0282] [Item 3] A mobility service system according to Item 1, wherein:

[0283] The management server (3, 5A, 5B) comprises a first management unit (3) and a second management unit (5A, 5B),

[0284] The server reduction criteria include a second management unit criteria determined based on identification information related to the vehicle-mounted device.

[0285] The first management unit comprises:

[0286] A storage unit (33) configured to store the first management unit partial content based on the vehicle-mounted device partial content uploaded by the upload unit (211, S130); and

[0287] The first sending unit (311, S150) is configured to send the first management unit partial content corresponding to the request among the first management unit partial content stored in the storage unit to the second management unit according to the request from the second management unit.

[0288] The second management unit comprises:

[0289] A receiving unit (511, S210), configured to receive the partial content of the first management unit sent by the first sending unit;

[0290] A second management unit reduction unit (511, S230), included in the server-side reduction unit, and configured to reduce the data volume of the first management unit partial content received by the receiving unit based on the second management unit to generate a second management unit partial content; and

[0291] The terminal sending unit (511, S260),

[0292] The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the second management unit partial content.

[0293] [Item 4] A mobility service system according to Item 2, wherein:

[0294] The server reduction criterion includes a second management unit reduction criterion determined based on identification information related to the vehicle-mounted device.

[0295] The second management unit (5A, 5B) further comprises:

[0296] The second management unit reduction unit (511, S230) is included in the server-side reduction unit and is configured to reduce the data volume of the first management unit partial content received by the receiving unit (511, S210) based on the second management unit reduction standard to generate the second management unit partial content.

[0297] The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the second management unit partial content.

[0298] [Item 5] A mobility service system according to Item 3, wherein:

[0299] The server reduction criteria include a first management unit reduction criteria determined based on grouping related to a plurality of vehicle-mounted devices.

[0300] The first management unit (3) further comprises:

[0301] The first management unit reduction unit (311, S120) is included in the server side reduction unit and is configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit (211, S130) based on the first management unit reduction standard to generate the first management unit partial content.

[0302] [Item 6] A mobility service system according to any one of Items 1 to 5, wherein:

[0303] The second management unit reduction unit (511, S230) is configured to reduce the reduction amount of the data when the identification information of the end user or the vehicle-mounted device or the user of the vehicle corresponds to a high level, compared with a case where the identification information of the end user or the vehicle-mounted device or the user of the vehicle corresponds to a low level.

[0304] [Item 7] A mobility service system according to any one of items 2, 4, 5, and 6, wherein:

[0305] A plurality of end users provided with services by a service operator via the second management unit (5A, 5B) belong to a group based on the grouping.

[0306] [Item 8] A mobility service system according to any one of items 2, 4, 5, and 6, wherein:

[0307] A group based on the above grouping contains multiple subgroups.

[0308] The first management unit reduction unit (311, S120) is configured to change the amount of reduction of the data amount for each of the plurality of sub-groups.

[0309] [Item 9] A mobility service system according to any one of Items 1 to 8, wherein:

[0310] The above content contains images,

[0311] The reduction in the data amount described above corresponds to any one of shortening the video time, reducing the image quality, and thinning out the frames.

[0312] [Item 10] A mobility service system according to any one of Items 1 to 9, wherein:

[0313] The first management unit (3) further comprises:

[0314] The deleting unit (311, S170) is configured to delete the first management unit partial content from the storage unit (33) when a set period has passed since the first management unit partial content was stored in the storage unit (33).

[0315] [Item 11] A mobility service system according to any one of Items 1 to 10, wherein:

[0316] The first management unit (3) further comprises:

[0317] The deleting unit (311) is configured to delete the first management unit partial content from the storage unit when the number of times the first sending unit sends the first management unit partial content to the second management unit exceeds a set number of times.

[0318] [Item 12]

[0319] A method for reducing the amount of data is a method for reducing the amount of data performed by a mobility service system having an on-board device (2A, 2B) and a management server (3, 5A, 5B), wherein the on-board device (2A, 2B) has an acquisition device (222) for acquiring content including images or sounds and is mounted on a vehicle (8A, 8B), and the management server (3, 5A, 5B) is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the above-mentioned vehicle.

[0320] The above-mentioned vehicle-mounted device is composed of:

[0321] Execute the application;

[0322] During the execution of the application, detecting an event related to the application;

[0323] In response to the detection of the event, the data volume of the content acquired by the acquisition means is reduced by a vehicle-mounted device reduction standard corresponding to the application program to generate vehicle-mounted device partial content; and

[0324] Upload the generated content of the above vehicle-mounted machine to the above management server,

[0325] The above management server is composed of:

[0326] Reducing the data volume of the uploaded vehicle-mounted device partial content by using a server reduction standard corresponding to the information related to the vehicle-mounted device to generate a server partial content; and

[0327] The server portion of the content is transmitted to a terminal device (7) of an end user who utilizes a service corresponding to the application.

Claims

1. A mobility service system comprising an on-board device (2A, 2B) and a management server (3, 5A, 5B), wherein the on-board device comprises an acquisition device (222) for acquiring content including images or sounds and is mounted on a vehicle (8A, 8B), and the management server is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the above-mentioned vehicle. In the mobility service system (100), The above-mentioned vehicle-mounted device has: an execution unit (211, 27) configured to execute an application program; an event detection unit (211, S10) configured to detect an event related to the application program while the execution unit is executing the application program; a vehicle-mounted device-side reduction unit (211, S20) configured to reduce the data volume of the content acquired by the acquisition device according to a vehicle-mounted device reduction standard corresponding to the application program when the event is detected by the event detection unit, and generate vehicle-mounted device partial content; and The uploading unit (211, S30) is configured to upload the vehicle-mounted device partial content generated by the vehicle-mounted device side reduction unit to the management server, The above management server has: A server-side reduction unit (311, 511, S120, S230) configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit according to a server reduction standard corresponding to the information related to the vehicle-mounted device, and generate a server partial content; and The terminal sending unit (511, S260) is configured to send terminal content to a terminal device (7A, 7B) of an end user who uses a service corresponding to the application based on the server partial content generated by the server-side reduction unit.

2. The mobility service system according to claim 1, wherein: The management server (3, 5A, 5B) comprises a first management unit (3) and a second management unit (5A, 5B), The server reduction criteria include a first management unit reduction criteria determined based on grouping related to a plurality of vehicle-mounted devices. The first management unit has: The first management unit reduction unit (311, S120) is included in the server side reduction unit and is configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit (211, S30) based on the first management unit reduction standard to generate the first management unit partial content. The first management unit comprises: A storage unit (33) configured to store the first management unit partial content generated by the first management unit reduction unit; and The first sending unit (311, S150) is configured to send the first management unit partial content corresponding to the request among the first management unit partial content stored in the storage unit to the second management unit according to the request from the second management unit. The second management unit comprises: A receiving unit (511, S210) configured to receive the partial content of the first management unit sent by the first sending unit; and The terminal sending unit (511, S260), The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the first management unit partial content.

3. The mobility service system according to claim 1, wherein: The management server (3, 5A, 5B) comprises a first management unit (3) and a second management unit (5A, 5B), The server reduction criteria include a second management unit criteria determined based on identification information related to the vehicle-mounted device. The first management unit comprises: A storage unit (33) configured to store the first management unit partial content based on the vehicle-mounted device partial content uploaded by the upload unit (211, S30); as well as The first sending unit (311, S150) is configured to send the first management unit partial content corresponding to the request among the first management unit partial content stored in the storage unit to the second management unit according to the request from the second management unit. The second management unit comprises: A receiving unit (511, S210), configured to receive the partial content of the first management unit sent by the first sending unit; A second management unit reduction unit (511, S230), included in the server-side reduction unit, and configured to reduce the data volume of the first management unit partial content received by the receiving unit based on the second management unit to generate the second management unit partial content; and The terminal sending unit (511, S260), The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the second management unit partial content.

4. The mobility service system according to claim 2, wherein: The server reduction criterion includes a second management unit reduction criterion determined based on identification information related to the vehicle-mounted device. The second management unit (5A, 5B) further comprises: The second management unit reduction unit (511, S230) is included in the server-side reduction unit and is configured to reduce the data volume of the first management unit partial content received by the receiving unit (511, S210) based on the second management unit reduction standard to generate the second management unit partial content. The terminal transmission unit is configured to transmit the terminal content to the terminal device based on the second management unit partial content.

5. The mobility service system according to claim 3, wherein: The server reduction criteria include a first management unit reduction criteria determined based on grouping related to a plurality of vehicle-mounted devices. The first management unit (3) further comprises: The first management unit reduction unit (311, S120) is included in the server side reduction unit and is configured to reduce the data volume of the vehicle-mounted device partial content uploaded by the upload unit (211, S30) based on the first management unit reduction standard to generate the first management unit partial content.

6. The mobility service system according to claim 4 or 5, wherein: The second management unit reduction unit (511, S230) is configured to reduce the reduction amount of the data when the identification information of the end user or the vehicle-mounted device or the user of the vehicle corresponds to a high level, compared with a case where the identification information of the end user or the vehicle-mounted device or the user of the vehicle corresponds to a low level.

7. The mobility service system according to claim 4 or 5, wherein: A plurality of end users provided with services by a service operator via the second management unit (5A, 5B) belong to a group based on the grouping.

8. The mobility service system according to claim 4 or 5, wherein: A group based on the above grouping contains multiple subgroups. The first management unit reduction unit (311, S120) is configured to change the amount of reduction of the data amount for each of the plurality of sub-groups.

9. The mobility service system according to any one of claims 1 to 5, wherein: The above content contains images, The reduction in the data amount described above corresponds to any one of shortening the video time, reducing the image quality, and thinning out the frames.

10. The mobility service system according to any one of claims 2 to 5, wherein: The first management unit (3) further comprises: The deleting unit (311, S170) is configured to delete the first management unit partial content from the storage unit (33) when a set period has passed since the first management unit partial content was stored in the storage unit (33).

11. The mobility service system according to any one of claims 2 to 5, wherein: The first management unit (3) further comprises: The deleting unit (311) is configured to delete the first management unit partial content from the storage unit when the number of times the first sending unit sends the first management unit partial content to the second management unit exceeds a set number of times.

12. A method for reducing the amount of data, the method being performed by a mobility service system having an on-board device (2A, 2B) and a management server (3, 5A, 5B), wherein the on-board device has an acquisition device (222) for acquiring content including images or sounds and is mounted on a vehicle (8A, 8B), and the management server is configured to collect and store data from a plurality of on-board devices mounted on a plurality of vehicles including the above-mentioned vehicle, wherein: The above-mentioned vehicle-mounted device is composed of: Execute the application; During the execution of the application, detecting an event related to the application; In response to the detection of the event, the data volume of the content acquired by the acquisition means is reduced by a vehicle-mounted device reduction standard corresponding to the application program to generate vehicle-mounted device partial content; and Upload the generated content of the above vehicle-mounted machine to the above management server, The above management server is composed of: Reducing the data volume of the uploaded vehicle-mounted device partial content by using a server reduction standard corresponding to the information related to the vehicle-mounted device to generate a server partial content; and Based on the server partial content, terminal content is transmitted to a terminal device (7) of an end user who utilizes a service corresponding to the application.

Images