Information system, management device, and edge device

Abstract

To provide a technique which reduces anxiety of a user about his or her vehicle which may be used by others.SOLUTION: An information system comprises a first management unit, a second management unit, and an edge device. The edge device comprises a data providing unit and an event transmission unit. The event transmission unit detects the occurrence of a preliminarily set event and transmits an event notification to the second management unit. The second management unit comprises a data acquisition unit, a receiving unit, a geofence setting unit, a position identification unit, a determination unit, and a notification transmission unit. In response to receiving the event notification, the geofence setting unit sets a geofence including a current position of a registered vehicle. The determination unit determines movement of the registered vehicle to the outside of the geofence. When it is determined that the registered vehicle has moved to the outside of the geofence, the notification transmission unit transmits a notification to a terminal device.SELECTED DRAWING: Figure 18

Description

[Technical Field]

[0001] The present disclosure relates to a technology for effectively utilizing resources possessed by a connected car. [Background technology]

[0002] 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. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-200123 Summary of the Invention [Problem to be solved by the invention]

[0004] The technology described in Patent Document 1 is used for fleet services, etc. Fleet services are provided using connected technology for commercial vehicles and include services such as vehicle tracking, business management, driver management, regulatory compliance, and cost reduction.

[0005] Some fleet services are based on the premise that the vehicle will be used by others, and users may have various concerns regarding the use of their vehicle by others.

[0006] One aspect of the present disclosure provides techniques that alleviate users' concerns about others using their vehicles. [Means for solving the problem]

[0007] An information system according to one aspect of the present disclosure includes a management device and an edge device (2). The management device includes a first management unit (3) and a second management unit (5). The edge device is mounted on a registered vehicle (8) registered in the second management unit. The edge device includes a data providing unit (261) and an event transmitting unit (S20, S60). The data providing unit is configured to repeatedly collect vehicle data including location information and status information of the registered vehicle and provide the collected data to the first management unit. The event transmitting unit is configured to detect the occurrence of a preset event and transmit an event notification indicating the occurrence of the event to the second management unit. The first management unit includes a memory unit (113) configured to store the vehicle data repeatedly provided from the edge device in association with the registered vehicle. The second management unit includes a data acquisition unit (61), a receiving unit (S110, S130, S210, S230), a geofence setting unit (S120, S220), a position identification unit (S100, S140, S200, S240), a determination unit (S150), and a notification sending unit (S160). The data acquisition unit is configured to acquire vehicle data stored in the storage unit. The receiving unit is configured to receive an event notification transmitted from the event sending unit. The geofence setting unit is configured to set a geofence including a current position of the registered vehicle in response to reception of the event notification by the receiving unit. The position identification unit is configured to repeatedly identify the current position of the registered vehicle based on the vehicle data acquired by the data acquisition unit. The determination unit is configured to determine movement outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit. The notification sending unit is configured to send a notification indicating that the registered vehicle has moved outside the geofence to a terminal device linked to the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence.

[0008] In an information system according to one aspect of the present disclosure, when a preset event occurs and it is determined that a registered vehicle has moved outside a geofence, a notification is sent to a terminal device associated with the registered vehicle. Thus, even if the vehicle is used by a third party, the user can immediately recognize the use of the vehicle by a third party. Therefore, the user's concerns about the use of the vehicle by a third party can be alleviated.

[0009] An information system according to another aspect of the present disclosure includes a management device and an edge device (2). The management device includes a first management unit (3) and a second management unit (5). The edge device is mounted on a registered vehicle (8) registered in the second management unit. The edge device also includes a data providing unit (261) and an event transmitting unit (S20, S60). The data providing unit is configured to repeatedly collect vehicle data, including location information and status information of the registered vehicle, and provide the collected data to the first management unit. The event transmitting unit is configured to detect the occurrence of a preset event and transmit an event notification indicating the occurrence of the event to the second management unit. The first management unit includes a memory unit (113) and a vehicle control unit (130). The memory unit is configured to store the vehicle data repeatedly provided from the edge device in association with the registered vehicle. The vehicle control unit is configured to cause the registered vehicle to perform instructed vehicle control. The second management unit includes a data acquisition unit (61), a receiving unit (S110, S130, S210, S230), a geofence setting unit (S120, S220), a position identification unit (S100, S140, S200, S240), a determination unit (S150), and a control instruction unit (62). The data acquisition unit is configured to acquire vehicle data stored in the storage unit. The receiving unit is configured to receive an event notification transmitted from the event transmission unit. The geofence setting unit is configured to set a geofence including a current position of the registered vehicle in response to reception of the event notification by the receiving unit. The position identification unit is configured to repeatedly identify the current position of the registered vehicle based on the vehicle data acquired by the data acquisition unit. The determination unit is configured to determine movement of the registered vehicle outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit. The control instruction unit is configured to instruct the vehicle control unit to perform predetermined vehicle control on the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence.

[0010] In another aspect of the present disclosure, an information system instructs a predetermined vehicle control on a registered vehicle when a predetermined event occurs and the registered vehicle is determined to have moved outside a geofence. This allows the user to keep control of the vehicle even if the vehicle is used by another person. This alleviates the user's concerns about the vehicle being used by another person.

[0011] A management device according to one aspect of the present disclosure includes a first management unit (3) and a second management unit (5), and together with an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, constitutes an information system (1). The first management unit includes a storage unit (113) configured to store vehicle data including location information repeatedly provided from the edge device, in association with the registered vehicle. The second management unit includes a data acquisition unit (61), a receiving unit (S110, S130, S210, S230), a geofence setting unit (S120, S220), a location identification unit (S100, S140, S200, S240), a determination unit (S150), and a notification transmission unit (S160). The data acquisition unit is configured to acquire the vehicle data stored in the storage unit. The receiving unit is configured to receive an event notification transmitted from the edge device indicating the occurrence of a preset event. The geofence setting unit is configured to set a geofence including a current position of the registered vehicle in response to reception of the event notification by the receiving unit. The position identification unit is configured to repeatedly identify the current position of the registered vehicle based on the vehicle data acquired by the data acquisition unit. The determination unit is configured to determine movement of the registered vehicle outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit. The notification sending unit is configured to send a notification indicating movement of the registered vehicle outside the geofence to a terminal device linked to the registered vehicle when movement outside the geofence is determined by the determination unit.

[0012] According to the management device of one aspect of the present disclosure, the same effects as those of the information system of one aspect of the present disclosure are achieved.

[0013] A management device according to another aspect of the present disclosure includes a first management unit (3) and a second management unit (5), and together with an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, constitutes an information system (1). The first management unit includes a storage unit (113) and a vehicle control unit (130). The storage unit is configured to store vehicle data including location information repeatedly provided from the edge device, in association with the registered vehicle. The vehicle control unit is configured to cause the registered vehicle to execute instructed vehicle control. The second management unit includes a data acquisition unit (61), receiving units (S110, S130, S210, S230), a geofence setting unit (S120, S220), a position identification unit (S100, S140, S200, S240), a determination unit, and a control instruction unit (62). The data acquisition unit is configured to acquire the vehicle data stored in the storage unit. The receiving unit is configured to receive an event notification transmitted from the edge device, the event notification indicating the occurrence of a preset event. The geofence setting unit is configured to set a geofence including a current position of the registered vehicle in response to the receiving unit receiving the event notification. The position identifying unit is configured to repeatedly identify the current position of the registered vehicle based on the vehicle data acquired by the data acquiring unit. The determining unit is configured to determine whether the registered vehicle has moved outside the geofence set by the geofence setting unit based on the current position identified by the position identifying unit. The control instructing unit is configured to instruct the vehicle control unit to perform predetermined vehicle control on the registered vehicle when the determining unit determines that the registered vehicle has moved outside the geofence.

[0014] According to the management device of another aspect of the present disclosure, the same effects as those of the information system of another aspect of the present disclosure are achieved.

[0015] An edge device according to one aspect of the present disclosure configures an information system (1) together with a management device having a first management unit (3) and a second management unit (5), and is mounted on a registered vehicle (8) registered in the second management unit. The edge device includes a data providing unit (261), a first event transmitting unit (S20), and a second event transmitting unit (S60). The data providing unit is configured to repeatedly collect vehicle data, including location information and status information of the registered vehicle, and provide the collected data to the first management unit. The first event transmitting unit transmits a first event notification to the second management unit in response to detecting the occurrence of a preset event. The second event transmitting unit is configured to transmit a second event notification to the second management unit in response to the vehicle speed of the registered vehicle reaching or exceeding a threshold after the first event transmitting unit transmits the first event notification.

[0016] By the edge device according to one aspect of the present disclosure transmitting the second event notification in addition to the first event notification, the second management unit can detect use of the vehicle by another person with higher accuracy.

[0017] An information notification method according to one aspect of the present disclosure is executed by an information system (1) including a management device having a first management unit (3) and a second management unit (5), and an edge device (2) mounted on a registered vehicle (8) registered in the second management unit. In the information notification method, the edge device repeatedly collects vehicle data including location information and status information of the registered vehicle and provides it to the first management unit, detects the occurrence of a preset event, and transmits an event notification indicating the occurrence of the event to the second management unit. In the information notification method, the first management unit stores the vehicle data repeatedly provided by the edge device in a memory unit, linking it to the registered vehicle. In the above information notification method, the second management unit acquires vehicle data stored in the memory unit, and in response to receiving an event notification, sets a geofence including the current location of the registered vehicle, repeatedly identifies the current location of the registered vehicle based on the acquired vehicle data, determines whether the registered vehicle has moved outside the set geofence based on the identified current location, and if it determines that the registered vehicle has moved outside the geofence, sends a notification to the terminal device linked to the registered vehicle indicating that the registered vehicle has moved outside the geofence.

[0018] According to the information notification method of one aspect of the present disclosure, the same effects as those of the information system of one aspect of the present disclosure are achieved.

[0019] A vehicle control method according to one aspect of the present disclosure is executed by an information system (1) including a management device having a first management unit (3) and a second management unit (5), and an edge device (2) mounted on a registered vehicle (8) registered in the second management unit. In the vehicle control method, the edge device repeatedly collects and provides vehicle data, including location information and status information of the registered vehicle, to the first management unit. The edge device detects the occurrence of a preset event and transmits an event notification indicating the occurrence of the event to the second management unit. In the vehicle control method, the first management unit associates the vehicle data repeatedly provided from the edge device with the registered vehicle and stores it in a memory unit. In the vehicle control method, the second management unit acquires the vehicle data stored in the memory unit, and, in response to receiving the event notification, sets a geofence including the current location of the registered vehicle, repeatedly identifies the current location of the registered vehicle based on the acquired vehicle data, determines whether the registered vehicle has moved outside the set geofence based on the identified current location, and, if it determines that the registered vehicle has moved outside the geofence, instructs the first management unit to perform predetermined vehicle control on the registered vehicle. In the vehicle control method, the first management unit causes the registered vehicle to execute the predetermined vehicle control in response to an instruction for the predetermined vehicle control from the second management unit.

[0020] According to the vehicle control method of one aspect of the present disclosure, the same effects as those of the information system of another aspect of the present disclosure are achieved.

[0021] A program according to one aspect of the present disclosure forms an information system (1) together with a management device having a first management unit (3) and a second management unit (5), and causes a processing device (211) of an edge device (2) mounted on a registered vehicle (8) registered in the second management unit to repeatedly collect vehicle data including the location information and status of the registered vehicle and provide it to the first management unit, send a first event notification to the second management unit in response to detecting the occurrence of a predetermined event, and send a second event notification to the second management unit in response to the vehicle speed of the registered vehicle becoming equal to or greater than a threshold after the first event notification has been sent.

[0022] When the program according to one aspect of the present disclosure is executed by a processing device of the edge device, the same effect as that of the edge device according to one aspect of the present disclosure is achieved. [Brief explanation of the drawings]

[0023] [Figure 1] FIG. 1 is a schematic diagram showing the configuration of a mobility IoT system. [Figure 2] FIG. 2 is a block diagram showing a hardware configuration of an edge device. [Figure 3] FIG. 2 is a functional block diagram showing the functional configuration of an edge device. [Figure 4] FIG. 2 is a diagram showing the first layer and data format of standardized vehicle data. [Figure 5] FIG. 2 is a diagram showing the configuration of standardized vehicle data. [Figure 6] 10 is a flowchart showing a border crossing detection process of a border crossing detection application. [Figure 7] FIG. 2 is a block diagram showing a hardware configuration of a management server. [Figure 8] FIG. 2 is a functional block diagram showing the functional configuration of a management server. [Figure 9] FIG. 2 is a functional block diagram showing the functional configuration of a mobility gateway and a data management unit. [Figure 10] FIG. 10 is a diagram illustrating a configuration of a shadow. [Figure 11] FIG. 10 is a diagram illustrating the configuration of the latest index. [Figure 12] FIG. 10 is a diagram illustrating the structure of an index. [Figure 13] FIG. 2 is a block diagram showing a hardware configuration of a service server. [Figure 14] FIG. 2 is a functional block diagram showing the functional configuration of a service server. [Figure 15] 10 is a flowchart showing a first embodiment of event processing executed by an event management unit of a service server. [Figure 16]10 is a flowchart showing a second embodiment of the event processing executed by the event management unit of the service server. [Figure 17] FIG. 1 is a sequence diagram showing the operation of the mobility IoT system under normal circumstances. [Figure 18] FIG. 10 is a sequence diagram showing the operation of the mobility IoT system when an event is detected in an edge device. [Figure 19] FIG. 1 is an explanatory diagram illustrating an overview of services provided by a border crossing detection app. DETAILED DESCRIPTION OF THE INVENTION

[0024] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. <1-1. Overall structure> The mobility IoT system 1 shown in Fig. 1 includes multiple edge devices 2, a management server 3, a service server 5, and multiple terminal devices 7. IoT stands for Internet of Things. The management server 3 and the service server 5 may be configured as cloud servers.

[0025] Each of the edge devices 2 is mounted on a different registered vehicle 8. Each of the edge devices 2 collects vehicle data of the registered vehicle 8 in which it is mounted and uploads the collected vehicle data to the management server 3. Each of the edge devices 2 executes vehicle control according to instructions from the management server 3. Each of the edge devices 2 executes various application programs that are arbitrarily installed. The multiple edge devices 2 are registered with the service server 5. Note that the mobility IoT system 1 may include at least one edge device in addition to the multiple edge devices 2. Each of the at least one edge device collects vehicle data of the registered vehicle 8 in which it is mounted and uploads the collected vehicle data to the management server 3, but is not registered with the service server 5. In other words, the at least one edge device does not receive services from the service server 5.

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

[0027] The service server 5 uses the interface provided by the management server 3 to collect vehicle data corresponding to the registered vehicle 8 and to perform vehicle control of the registered vehicle 8. In this way, the service server 5 provides various services to the user of the registered vehicle 8. The user of the registered vehicle 8 includes the owner, driver, passengers, and owner of the registered vehicle 8.

[0028] The multiple terminal devices 7 are mobile terminals such as smartphones and tablets. Each of the terminal devices 7 is owned by a user of a registered vehicle 8 and is linked to the registered vehicle 8. Each of the terminal devices 7 communicates with the service server 5. Each of the terminal devices 7 executes various application programs that are arbitrarily installed.

[0029] In this embodiment, the service server 5 is provided separately from the management server 3, but may be provided integrally with the management server 3. In addition to the service server 5, the mobility IoT system 1 may include one or more service servers that provide services different from those of the service server 5.

[0030] <2. Edge devices> <2-1. Hardware configuration> As shown in FIG. 2, 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.

[0031] The control unit 21 includes a CPU 211, a ROM 212, and a RAM 213. Various functions of the control unit 21 are realized by the CPU 211 executing a program stored in a non-transitory tangible recording medium. In this embodiment, the ROM 212 corresponds to the non-transitory tangible recording medium storing the program. Furthermore, by executing this program, a method corresponding to the program is performed.

[0032] The vehicle IF unit 22 is connected to various on-board devices via an on-board network of the registered vehicle 8, etc., and acquires various information from the on-board devices. The on-board network may include CAN and Ethernet. CAN is an abbreviation for Controller Area Network. CAN is a registered trademark. Ethernet is a registered trademark. The on-board devices connected to the vehicle IF unit 22 may include devices that are originally installed in the registered vehicle 8, as well as exterior devices that are added later. The exterior devices may include sensors, cameras, audio devices, display devices, etc.

[0033] The communication unit 23 performs data communication with the management server 3 and the service server 5 via wireless communication over the wide area communication network NW. The storage unit 24 stores 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.

[0034] <2-2. Functional configuration> 3, the edge device 2 includes the functions of systemware 25, a core function execution unit 26, and an application execution unit 27. The functions of these units 25 to 27 are realized by the CPU 211 executing a program stored in the ROM 212.

[0035] The systemware 25 abstracts hardware and includes basic software that provides various services necessary for executing application programs, and drivers for supporting special processes that cannot be standardized. The basic software includes an operating system (hereinafter referred to as OS) and a hardware abstraction layer (hereinafter referred to as HAL). The hardware that is the target of abstraction by the systemware 25 includes not only the hardware provided in the edge device 2, but also in-vehicle equipment and exterior devices connected to the edge device 2 via the vehicle IF unit 22.

[0036] The core function execution unit 26 and the application execution unit 27 are realized by software that runs on the systemware 25 .

[0037] <2-2-1. Core Function Execution Unit> The core function execution unit 26 has the form of an edge computer that mediates between the management server 3 and the registered vehicles 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 vehicles 8 and uploads it to the management server 3. The vehicle control unit 262 controls the registered vehicles 8 in accordance with instructions from the management server 3. The controls executed by the vehicle control unit 262 include a first control, a second control, and a third control. The first control is a control to sound the horn in a specified pattern. The second control is a control to flash specified lighting devices in a specified pattern. The third control is a control to limit the upper limit of the travel speed.

[0038] Here, the vehicle data that the basic upload unit 261 provides to the management server 3 will be described. The basic upload unit 261 repeatedly collects vehicle data from registered vehicles 8 via the vehicle IF unit 22. The basic upload unit 261 converts the collected vehicle data into a standard format, associates it with hierarchical classifications, and stores it in the storage unit 24. Hereinafter, the hierarchical vehicle data will be referred to as standardized vehicle data.

[0039] As shown in FIG. 4, the standard format of vehicle data may include the following items: "unique label," "ECU," "data type," "data size," "data value," and "data unit."

[0040] The "unique label" is information for identifying each physical quantity. For example, "ETHA" indicates the intake air temperature, and "NE1" indicates the engine speed. "ECU" is information indicating the electronic control unit (hereinafter referred to as ECU) that generated the vehicle data. For example, "ENG" indicates that the data was generated by the engine ECU.

[0041] A "data type" is information for defining the properties of a "data value." A "data type" may include, for example, an integer type, a floating-point type, a logical type, a character type, and the like. "Data size" is information indicating how many bytes a "data value" is expressed in.

[0042] The "data value" is information indicating the value of the physical quantity identified by the "unique label." "Data unit" is information indicating the unit of the data value. The "data values" are normalized so that the same physical quantities are expressed in the same units regardless of the vehicle model and vehicle manufacturer.

[0043] Furthermore, the "unique label" may include information that identifies "processed data" in addition to identifying "raw data" obtained from the registered vehicle 8. "Processed data" refers to data that has been converted into a format that is easier for users to understand by performing a predetermined calculation on one or more pieces of "raw data."

[0044] The standardized vehicle data has a multi-layer structure. For example, as shown in FIG. 4, the standardized vehicle data includes the following items set in the top first layer: "Attribute Information," "Powertrain," "Energy," "ADAS / AD," "Body," "Multimedia," and "Other." ADAS stands for Advanced Driver Assistance System. AD ​​stands for Autonomous Driving. Each item in the first layer represents a category of vehicle data.

[0045] As shown in Fig. 5, the standardized vehicle data may have a second and third hierarchies in addition to the first hierarchies. The second hierarchies are immediately below the first hierarchies, and the third hierarchies are immediately below the second hierarchies.

[0046] For example, "Attribute Information," an item in the first layer, includes items in the second layer such as "Vehicle Identification Information," "Vehicle Attributes," "Transmission Configuration," and "Firmware Version." "Powertrain," an item in the first layer, includes items in the second layer such as "Accelerator Pedal," "Engine," and "Engine Oil." "Energy," an item in the first layer, includes items in the second layer such as "Battery Status," "Battery Configuration," and "Fuel." Each of these items in the second layer also represents a category of vehicle data.

[0047] For example, the second-level item "Vehicle Identification Information" includes third-level items such as "Vehicle Identification Number," "Vehicle Identification Number," and "License Plate." The second-level item "Vehicle Attributes" includes third-level items such as "Brand Name," "Model," and "Year of Manufacture." The second-level item "Transmission Configuration" includes third-level items such as "Transmission Type." Although not shown, the second-level item "Accelerator Pedal" includes third-level items such as "Accelerator Pedal Status" and "Accelerator Pedal Opening Degree." The second-level item "Engine" includes third-level items such as "Engine Status" and "RPM." Each of these third-level items corresponds to a "unique label" in the standard format. In other words, each piece of vehicle data is stored in association with each third-level item. Each piece of vehicle data belonging to the standardized vehicle data is also referred to as an item.

[0048] In this way, each item in the first layer includes one or more items in the second layer, and each item in the second layer includes one or more items in the third layer, i.e., vehicle data. For example, vehicle data whose "unique label" is "vehicle identification information" is stored in a storage area in the standardized vehicle data where the first layer is "attribute information," the second layer is "vehicle identification information," and the third layer is "vehicle identification number."

[0049] The first-level item "Other" may include, for example, location information, that is, latitude, longitude, and altitude, acquired from a GPS device mounted on the registered vehicle 8 via the vehicle IF unit 22.

[0050] Next, a procedure in which the basic upload unit 261 uploads vehicle data to the management server 3 will be described. A transmission cycle for transmitting data to the management server 3 is set for each vehicle data belonging to the standardized vehicle data. The transmission cycle is set according to the degree of change of the data, the importance of the data, etc., so that the more frequently the data changes or the more important the data, the shorter the transmission cycle. In other words, each vehicle data is transmitted at a frequency according to its characteristics. The transmission cycle is, for example, 500 ms, 2 s, 4 s, 30 s, 300 s, 12 hours, etc.

[0051] The transmission timing is set to, for example, a 250 ms cycle. Each vehicle data is uploaded at a predetermined transmission timing according to a schedule. The schedule is set so that transmission of a large amount of vehicle data is not concentrated at the same transmission timing.

[0052] <2-2-2. Application execution section> 3, the application execution unit 27 provides a function to execute application programs (hereinafter referred to as external applications) A1, A2, . . . that are arbitrarily installed later. The application execution unit 27 includes a virtual environment platform 271 and a library 272.

[0053] 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 systemware 25. The external applications Ai are executed on the virtual environment platform 271. The external applications Ai include a border crossing detection application A1.

[0054] The library 272 is a group of programs for providing standard functions commonly used by the external applications Ai. The library 272 includes an event notification program P1 and a video upload program P2. The event notification program P1 provides a function of sending an event notification to the service server 5 in accordance with instructions from the external application Ai. The video upload program P2 provides a function of uploading video captured by a video camera in the vehicle cabin to the service server 5 in accordance with instructions from the external application Ai.

[0055] <2-2-3. Border crossing detection app> The processing procedure of the border crossing detection application A1 executed by the CPU 211 of the edge device 2 will be described with reference to the flowchart of Fig. 6. The border crossing detection application A1 is one of external applications. When the border crossing detection application A1 is installed in the edge device 2, the CPU 211 repeatedly executes the border crossing detection application A1.

[0056] One of the services provided by the service server 5 is a cleaning request service. In the cleaning request service, when a user (i.e., the owner) requests cleaning of a registered vehicle 8, a cleaning company comes to the parking lot and cleans the parked registered vehicle 8. The user grants the cleaning company the authority to open and close the doors of the registered vehicle 8 within a limited time so that the user does not have to be present during cleaning. However, the user may be concerned that the cleaning company, who has been granted the authority to open and close the doors, may get into the registered vehicle 8 and run away, and may hesitate to use the cleaning request service.

[0057] Therefore, to alleviate the user's concerns, the edge device 2 executes the border crossing detection application A1. By executing the border crossing detection application A1, the edge device 2 detects that the registered vehicle 8 may have crossed the border within a set range (i.e., that the vehicle may have been stolen), and notifies the service server 5.

[0058] In S10, it is determined whether the target vehicle has been unlocked with a guest authority key. The guest authority key is a key given by the user of the target vehicle to another person (i.e., a temporary user), and is, for example, a digital key. The guest authority key includes information indicating the type and / or level of authority given to other vehicles by the user of the target vehicle. For example, the greater the guest authority, the wider the range in which the target vehicle can move. The target vehicle is a registered vehicle 8 that is running the border crossing detection app A1.

[0059] The digital key can be realized, for example, by a smartphone app. When a user (e.g., the owner) of the target vehicle requests cleaning of the target vehicle, the user provides the guest authority key to the cleaning company. Also, when a user of the registered vehicle 8 lends the registered vehicle 8 to someone, the user provides the guest authority key to that person.

[0060] If it is determined in S10 that the door has been unlocked with the guest authority key, the process proceeds to S20, and if it is determined that the door has not been unlocked, the process of S10 is repeated. In S20, the service server 5 is notified via the communication unit 23 that the vehicle has been unlocked with the guest authority key. The unlocking notification corresponds to the first event notification of the present disclosure. The unlocking notification may also include the current location of the registered vehicle 8.

[0061] In S30, a video camera inside the vehicle interior is activated. In S40, it is determined whether the vehicle speed of the target vehicle is equal to or greater than a preset threshold. If it is determined that the vehicle speed is equal to or greater than the threshold, the process proceeds to S50. If it is determined that the vehicle speed is less than the threshold, the process of S40 is repeatedly executed.

[0062] In S50, the service server 5 is notified via the communication unit 23 that the target vehicle may have crossed the border. The border crossing possibility notification corresponds to the second event notification of the present disclosure. When a service provider provides a service, the service provider may want to move the target vehicle slightly from a parking lot or the like. In such a case, if a border crossing is falsely detected, the service provider may not be able to provide sufficient service. By determining the occurrence of a border crossing when the vehicle speed exceeds a threshold, the occurrence of a border crossing can be detected with high accuracy. The threshold is approximately the speed limit in the parking lot, for example, 10 km / h.

[0063] Next, in S60, the video of the interior of the vehicle captured by the video camera is uploaded to the service server 5 via the communication unit 23, and the process ends.

[0064] <3. Management Server> <3-1. Hardware configuration> 7, the management server 3 includes a control unit 31, a communication unit 32, and a storage unit 33. The management server 3 corresponds to a first management unit of the present disclosure.

[0065] 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-transitory physical recording medium. In this example, the ROM 312 corresponds to the non-transitory physical recording medium storing the program. Furthermore, by executing this program, a method corresponding to the program is performed.

[0066] The communication unit 32 performs data communication between the edge devices 2 and the service server 5 via the wide area communication network NW. For communication with the edge devices 2, for example, MQTT, a simple and lightweight publish / subscribe protocol, may be used. MQTT stands for Message Queue Telemetry Transport.

[0067] The storage unit 33 is a storage device for storing vehicle data and the like provided by the edge device 2.

[0068] <3-2. Functional configuration> As shown in FIG. 9, the management server 3 includes the functions of a vehicle-side unit 110 and a service-side unit 120.

[0069] The method for realizing these functions of the management server 3 is not limited to software, and some or all of the elements may be realized using one or more pieces of hardware. For example, if the above functions are realized by electronic circuits that are hardware, the electronic circuits may be realized by digital circuits including multiple logic circuits, analog circuits, or a combination of these.

[0070] The vehicle-side unit 110 includes a mobility gateway (hereinafter referred to as mobility GW) 111. The mobility gateway 111 includes a shadow management unit 112 and a vehicle control unit 130. The shadow management unit 112 has a function of managing a shadow 114 provided for each vehicle equipped with an edge device 2. The shadow 114 is generated based on standardized vehicle data transmitted from the edge device 2. The vehicle control unit 130 has a function of controlling the vehicle equipped with the edge device 2 in accordance with instructions from the service server 5.

[0071] The service side unit 120 includes a data management unit 121 and an API providing unit 122. API is an abbreviation for Application Programming Interface. The data management unit 121 has a function of managing a digital twin 123, which is a virtual space for providing vehicle access independent of changes in the vehicle connection status. The digital twin 123 is one of the databases constructed on the storage unit 33.

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

[0073] <3-2-1. Data accumulation function> As shown in Figure 9, 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 components that realize the function of accumulating vehicle data obtained from the edge device 2.

[0074] The shadow creation unit 115 updates the standardized vehicle data by overwriting the transmitted vehicle data in 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 provided for each vehicle and is updated asynchronously.

[0075] The shadow creation unit 115 uses the updated standardized vehicle data to simultaneously create new shadows 114 for all vehicles at regular intervals. The shadow creation unit 115 stores the created shadows 114 in the shadow storage unit 113. As a result, the shadow storage unit 113 stores multiple shadows 114 created in chronological order for each vehicle. In other words, the shadows 114 can be considered to be copies of the state of the edge-equipped vehicle at a certain time.

[0076] As shown in FIG. 10, the shadow 114 includes a vehicle data storage unit 114a and a device data storage unit 114b. The vehicle data storage unit 114a stores "object-id", "Shadow_version", and "mobility-data" as data related to the edge-equipped vehicle.

[0077] "Object-id" is a character string that identifies the vehicle in which the edge device 2 is installed, and functions as a partition key. "Shadow_version" is a numerical value indicating the version of the shadow 114, and a timestamp indicating the time of creation is set each time the shadow 114 is created.

[0078] "mobility-data" is the value of the normalized vehicle data at the time represented by the timestamp. The device data storage unit 114b stores the following data as data relating to the hardware, software, and status installed in the edge device 2: "object-id", "update_time", "version", "power_status", "power_status_timestamp", and "notify_reason".

[0079] "Object-id" is a character string that identifies the vehicle in which the edge device 2 is installed, and functions as a partition key. "update_time" is a numerical value indicating the time when the hardware and software were updated.

[0080] "Version" is a string that indicates the version of the hardware and software. "power_status" is a character string indicating the system status of the edge device 2. Specifically, there is a "power on" state in which all functions are available, and a "power off" state in which some functions are stopped and low power consumption is achieved.

[0081] "power_status_timestamp" is a number indicating the time when the system status was notified. "notify_reason" is a string indicating the reason for the notification.

[0082] When a change occurs in the "version", "power_status", "notify_reason" and the like stored in the device data storage unit 114b, the edge device 2 notifies the change separately from the standardized vehicle data.

[0083] 9, the latest index creation unit 116 acquires the latest shadow 114 for each vehicle from the shadow storage unit 113, and creates a latest index 118 using the acquired shadow 114. The latest index creation unit 116 then stores the created latest index 118 in the latest index storage unit 117. The latest index storage unit 117 stores one latest index 118 for each vehicle (i.e., for each object-id).

[0084] As shown in FIG. 11, the latest index 118 stores "gateway-id", "object-id", "shadow-version", "vin", "location-lon", "location-lat", and "location-alt".

[0085] The “object-id” and “shadow-version” are the same as those explained in the shadow 114 . The "gateway-id" is information for identifying the mobility GW 111. When there are multiple management servers 3, for example, each of which is provided for a different country, the "gateway-id" is information for identifying these management servers.

[0086] "VIN" is the unique registration number assigned to your Edge-equipped vehicle. "location-lon" is information indicating the latitude at which the Edge-equipped vehicle is located. "location-lat" is information indicating the longitude at which the Edge-equipped vehicle is located.

[0087] "location-alt" is information indicating the altitude at which the Edge-equipped vehicle is located. Returning to FIG. 9, the data management unit 121 includes an index creation unit 124 and an index storage unit 125 as components for realizing the function of storing the latest index 118 acquired from the shadow management unit 112 as an index 126 .

[0088] The index creation unit 124 acquires the latest indexes 118 from the latest index storage unit 117 according to a preset acquisition schedule, and creates indexes 126 for the digital twin 123 using the acquired latest indexes 118. The index creation unit 124 then sequentially stores the created indexes 126 in the index storage unit 125. As a result, the index storage unit 125 stores multiple indexes 126 created in chronological order for each vehicle. In other words, each of the indexes 126 stored in the index storage unit 125 represents a vehicle that exists in the digital twin 123, which is a virtual space-time.

[0089] As shown in FIG. 12, the index 126 stores "timestamp", "schedule-type", "gateway-id", "object-id", "shadow-version", "vin", "location", and "alt".

[0090] "timestamp" is a timestamp indicating the time in milliseconds when the index 126 was created. "schedule-type" indicates whether the scheduler that created the data is periodic or event. If it is periodic, "schedule-type" is set to "Repeat", and if it is event, "schedule-type" is set to "Event".

[0091] “gateway-id”, “object-id”, “shadow-version”, and “vin” are information inherited from the latest index 118. "Location" is information inherited from "location-lon" and "location-lat" of the latest index 118, and "alt" is information inherited from "location-alt" of the latest index 118.

[0092] <3-2-2. Service provision functions> 8 and 9, the service side unit 120 includes an API providing unit 122. The API providing unit 122 is an interface provided to allow an external service provider such as the service server 5 to use the functions of the management server 3. Hereinafter, a user of the mobility IoT system 1 who uses the API providing unit 122 or the like is referred to as a service user. A service user is, for example, a service provider that delivers goods to the trunk of a vehicle.

[0093] 9, 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, the API providing unit 122 includes a login API 145, a data acquisition API 146, and a vehicle control API 148 as types of APIs provided to the service user.

[0094] The authentication information storage unit 141 stores "authentication information" in association with a "service user ID." The "service user ID" is identification information that uniquely identifies a service user. The "authentication information" is a preset password.

[0095] The authorization information storage unit 142 stores "authorization information" in association with "service user ID." The "authorization information" is information that specifies, for each service user, the range of available services among all the services provided by the management server 3.

[0096] The vehicle identification information storage unit 143 stores table information that associates an "object-id" uniquely assigned to an edge-equipped vehicle with the "vin" of that edge-equipped vehicle. 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.

[0097] The login API 145 is used when logging in to the management server 3. When the login API 145 receives an authentication request from a service user, the authentication processing unit 144 executes authentication processing. In the authentication processing, the "service user ID" and "authentication information" input by the login API 145 are compared with the registered contents of the authentication information storage unit 141. If the information matches as a result of the comparison, that is, if authentication is successful, access to the management server 3 is permitted.

[0098] 8, the data acquisition API 146 is an API used to access vehicle data (i.e., the index 126 and the shadow 114) accumulated in the management server 3. The vehicle control API 148 is an API used to access an edge-equipped vehicle, as shown in L2 in FIG.

[0099] The data acquisition API 146 and the vehicle control API 148 may perform authorization processing when receiving an access request from a service user. The authorization processing is processing for permitting or denying the access request in accordance with the authority previously granted to the service user.

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

[0101] <3-2-3. Data acquisition function> As shown in FIG. 9, the management server 3 includes an index acquisition unit 127 and a data acquisition unit 119 as components for processing an access request (hereinafter, a data acquisition request) via the data acquisition API 146.

[0102] The data acquisition process executed by the index acquisition unit 127 and the data acquisition unit 119 when the data acquisition API 146 receives a data acquisition request from a service user will be described below.

[0103] The data acquisition request includes vehicle designation information, time designation information, and data designation information. The vehicle designation information is information for designating the vehicle (hereinafter referred to as the target vehicle) that is the source of the vehicle data. The vehicle designation information can be provided in two ways: by listing the vehicle IDs (i.e., object-id or vin) of the target vehicles in a list format, or by designating the geographical area where the target vehicles are located (hereinafter referred to as area designation).

[0104] The time designation information is information that designates the timing at which data was generated. The time designation information is expressed by a starting time and a range. The range is, for example, a value that expresses a time width as an integer equal to or greater than 1, with the generation cycle of the latest index 118 as the unit time.

[0105] The data designation information is information that designates the data to be acquired. The data designation information may be expressed in list form as the item names of the data indicated in the standardized vehicle data, or may be expressed by designating the category names indicated in the standardized vehicle data. When a category name is designated, it is equivalent to designating all items belonging to that category. Furthermore, when neither an item name nor a category name is designated, it is equivalent to designating all items.

[0106] The method of setting the vehicle specification information, time specification information, and data specification information shown here is an example, and the present invention is not limited to the above method. The index acquisition unit 127 extracts all indexes 126 having a "timestamp" within the time range indicated in the time specification information for all vehicles identified from the vehicle specification information indicated in the data acquisition request.

[0107] For each of the extracted indexes 126, the index acquisition unit 127 generates shadow identification information by combining the "object-id" and "shadow-version" indicated in the index 126. In this way, a shadow list is generated that lists the shadow identification information.

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

[0109] That is, the index acquisition unit 127 generates a shadow list according to the acquisition conditions, which are the vehicle specification information and time specification information indicated in the data acquisition request from the data acquisition API 146. The index acquisition unit 127 also outputs a shadow access request that combines the generated shadow list with the data specification information to the data acquisition unit 119.

[0110] When the data acquisition unit 119 receives a shadow access request from the index acquisition unit 127, it references the shadow storage unit 113 and extracts the shadows 114 corresponding to each piece of shadow identification information indicated in the shadow list of the shadow access request. Furthermore, the data acquisition unit 119 extracts, from each of the extracted shadows 114, designated data that is data indicated in the data designation information of the shadow access request, and returns the extracted designated data as an access result to the data acquisition API 146 that originated the request.

[0111] <3-2-4. Vehicle control functions> As shown in FIG. 9, the management server 3 includes a vehicle control unit 130 as a component for processing an access request via the vehicle control API 148 (hereinafter referred to as a vehicle control request).

[0112] The vehicle control process executed by the vehicle control unit 130 when the vehicle control API 148 receives a vehicle control request from a service user will be described. The vehicle control request includes vehicle designation information, execution target information, and control designation information. The vehicle control request may further include priority information, time limit information, and vehicle authentication information.

[0113] The vehicle designation information indicates one vehicle ID. The vehicle identified by the vehicle ID is the target vehicle to be controlled. The execution target information is information that specifies which application installed in the registered vehicle 8 is to execute the control content indicated in the control specification information, and indicates an application ID that identifies the application.

[0114] The control designation information indicates the specific content of the control to be executed by the registered vehicle 8. For example, it may include the operation of the keys of various doors such as the passenger doors and the trunk door, the operation of audio devices such as a horn and a buzzer, the operation of various lamps such as headlights and hazard lights, and the operation of various sensors such as a camera and radar. The control designation information may indicate one control, or may indicate in list form a plurality of controls to be executed consecutively. Note that the controls indicated in list form are executed in the order listed.

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

[0116] The time limit information indicates the latest time that control of the registered vehicle 8 is permitted. The time limit information is set, for example, to a limit of 10 minutes from the time the vehicle control request is input. As with the priority information, the time limit information may be set by the service user who makes the request, or may be set automatically depending on the content of the control requested of the vehicle.

[0117] The vehicle authentication information is information used to determine whether the target vehicle is permitted to accept a control instruction, and may consist of an owner ID and password that identify the owner of the target vehicle. The vehicle authentication information is held in the registered vehicle 8 and also held by a service user who is permitted to access the vehicle.

[0118] 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. When the edge device 2 receives a control instruction from the management server 3, it performs authentication by comparing the vehicle authentication information indicated in the control instruction with the vehicle authentication information possessed by the vehicle itself.

[0119] If the authentication is successful, the edge device 2 causes the application identified from the implementation specification information to execute the control indicated in the control specification information, and also transmits a response including the execution result of the control to the management server 3. Upon receiving the response, the vehicle control unit 130 returns the response content to the vehicle control API 148.

[0120] <4. Service Server> <4-1. Hardware configuration> 13, 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 unit of the present disclosure.

[0121] 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-transitory physical recording medium. In this example, the ROM 512 corresponds to the non-transitory physical recording medium storing the program. Furthermore, by executing this program, a method corresponding to the program is performed.

[0122] 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. Note that a network different from the network used for communication with the management server 3 may be used for communication with the terminal device 7. The storage unit 53 stores various information necessary for providing the service.

[0123] <4-2. Functional configuration> 14, the service server 5 includes a data collection unit 61, a remote control unit 62, and an event management unit 63. The service server 5 also includes a plurality of databases (hereinafter, DBs), specifically, a vehicle DB 531, a video DB 532, a user DB 533, a map DB 534, and a geofence DB 535.

[0124] The vehicle DB 531 stores vehicle data acquired by the data collection unit 61 from the management server 3. The video DB 532 stores video data uploaded from the edge device 2. The user DB 533 stores driver information, which is information relating to the driver of the registered vehicle 8. The driver information includes the vehicle ID of the registered vehicle 8 associated with the driver and a contact method for the terminal device 7 (for example, a telephone number, an email address, etc.). The map DB 534 stores map information used for navigation, etc. The geofence DB 535 stores geofences that are set based on the positions of the registered vehicles 8 stored in the vehicle DB 531 and the map information stored in the map DB 534. A geofence is an area surrounded by virtual geographical boundaries.

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

[0126] The remote control unit 62 executes vehicle control of the designated registered vehicle 8 according to instructions from the terminal device 7 and using the vehicle control API 148 provided by the management server 3 . When the event management unit 63 receives an event notification from the edge device 2, it executes processing according to the contents of the event notification.

[0127] <4-3. Event Processing> <4-3-1. First Example> A first example of the event processing executed by the CPU 511 of the service server 5 will be described with reference to the flowchart of Fig. 15. In the first example, the CPU 511 transmits a border crossing notification to the terminal device 7 linked to the edge device 2.

[0128] In S100, the CPU 511 identifies the current location of the target vehicle by searching the vehicle DB 531. Next, in S110, it is determined whether or not an unlocking notification has been received from the edge device 2 via the communication unit 52. If it is determined that an unlocking notification has been received, the process proceeds to S120, and if it is determined that an unlocking notification has not been received, the process of S110 is repeatedly executed.

[0129] In S120, a geofence is set that includes the current location identified in S100. At this time, the shape and / or size of the geofence may be changed depending on the authority of the occupant of the registered vehicle 8. For example, if the occupant is a guest, the size of the geofence is set smaller than if the occupant is the owner of the registered vehicle 8. If the occupant is the owner of the registered vehicle 8, the size of the geofence may be set to be infinite.

[0130] Furthermore, if the occupant is a guest, the shape and / or size of the geofence may be changed depending on the type and / or size of the guest authority acquired from the guest authority key. For example, if the guest authority is authority given to a cleaning company, the range of the geofence may be limited to the parking lot, and the shape of the geofence may be set to a rectangle. Also, if the guest authority is authority given to a family member of the user of the registered vehicle 8, the range of the geofence may be limited to the prefecture, and the shape of the geofence may be set to a circle.

[0131] In addition, multiple geofences of different sizes may be set in multiple stages. A first geofence among the multiple geofences may contain a second geofence that is smaller than the first geofence. In other words, multiple geofences may be set in a nested state.

[0132] Next, in S130, it is determined whether or not a border crossing possibility notification has been received from the edge device 2 via the communication unit 52. If it is determined that a border crossing possibility notification has been received, the process proceeds to S140, and if it is determined that a border crossing possibility notification has not been received, the process of S130 is repeatedly executed.

[0133] In S140, the vehicle DB 531 is searched to identify the current location of the target vehicle. In S150, it is determined whether the current location determined in S140 has moved outside the geofence set in S120. If multiple geofences are set in S120, it is determined whether the current location has moved outside each of the multiple geofences.

[0134] If it is determined that the current location has moved outside the geofence, the process proceeds to S160, and if it is determined that the current location is inside the geofence, the process repeats S150. If multiple geofences are set in S120, if it is determined that the current location has moved outside the smallest geofence, the process proceeds to S160, and if it is determined that the current location is inside the smallest geofence, the process repeats S150.

[0135] In S160, a border crossing notification is sent to the terminal device 7 linked to the target vehicle via the communication unit 52. This allows the user to check the vehicle interior video uploaded to the service server 5 via the terminal device 7. Furthermore, the user can instruct vehicle control of the target vehicle via the terminal device 7. Vehicle control includes, for example, sounding the horn of the target vehicle or flashing the lights of the target vehicle. Vehicle control may also include braking control and steering control.

[0136] In addition, when multiple geofences are set, the border crossing notification may be changed depending on the current location. For example, each time the current location moves outside a larger geofence, the border crossing notification warning level sent to the terminal device 7 may be increased.

[0137] Note that if the edge device 2 transmits the unlocking notification including the current location of the registered vehicle 8, the CPU 511 may not execute the processing of S100. Also, in S150, instead of determining whether the current location identified in S140 has moved outside the geofence set in S120, the CPU 511 may determine whether there is a possibility that the registered vehicle 80 will move outside the geofence based on the current location and the trajectory of the registered vehicle 80. The trajectory of the registered vehicle 80 corresponds to a line connecting the current locations identified in the current and previous processing cycles. If the CPU 511 determines that there is a high possibility that the registered vehicle 80 will move outside the geofence, even before the registered vehicle 80 has moved outside the geofence, the CPU 511 may transmit a border crossing notification to the terminal device 7.

[0138] Furthermore, the use of border crossing detection is not limited to detecting theft of registered vehicles 8. The service server 5 may use border crossing detection of registered vehicles 8 to provide a monitoring service for novice drivers who have just obtained their driver's license or elderly people. When the service server 5 provides a monitoring service, for example, the owner may set a geofence within a prefecture for guests who are novice drivers, and set a geofence extending to hospitals or supermarkets for elderly guests. If the owner receives a border crossing notification after detecting an event that a novice driver or elderly person has boarded the registered vehicle 8, the owner can recognize that trouble may have occurred. Consequently, the owner can take action assuming that trouble will occur.

[0139] <4-3-2. Second Example> A second embodiment of the event processing executed by the CPU 511 of the service server 5 will be described with reference to the flowchart of Fig. 16. In the second embodiment, the CPU 511 commands the management server 3 to control the vehicle of the target vehicle.

[0140] In S200 to S250, the same processing as in S100 to S150 is executed. In S250, the management server 3 is instructed to perform predetermined vehicle control of the target vehicle. That is, in the second embodiment, the management server 3 is instructed to perform predetermined vehicle control of the target vehicle directly, without going through the terminal device 7. The predetermined vehicle control includes sounding the horn of the target vehicle and flashing the lamps of the target vehicle. The predetermined vehicle control may also include braking control and steering control.

[0141] Furthermore, when multiple geofences are set, vehicle control may be changed depending on the current location. For example, if the current location moves outside the smallest geofence, the horn may be sounded. If the current location moves outside the second smallest geofence, the horn may be sounded and the lamp may be flashed. If the current location moves outside the largest geofence, braking control may also be performed.

[0142] <5. Terminal Device> A terminal application is installed in the terminal device 7. The terminal application uses a graphic user interface (hereinafter referred to as GUI) and has functions to display notifications from the service server 5, play in-vehicle videos, and instruct the service server 5 to control the vehicle.

[0143] The GUI of the terminal app displays a video viewing screen, menu buttons, etc. The menu buttons include a video playback button and vehicle control buttons. When the terminal app receives a border crossing notification, it may not only display an icon or the like on the display screen of the terminal device 7 indicating that a border crossing notification has been received, but may also alert the user by sound or vibration using audio equipment or the like installed on the terminal device 7.

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

[0145] When the vehicle interior video is played back, the terminal application enables the vehicle control button. When the enabled vehicle control button is operated, the terminal application instructs the service server 5 to control the vehicle. If there are multiple vehicle controls that can be performed, a vehicle control button may be provided for each type of vehicle control.

[0146] <6. Operation> The overall operation of the mobility IoT system 1 will be described with reference to the sequence diagrams of FIGS.

[0147] <6-1. Normal operation> As shown in FIG. 17, under normal circumstances, the edge device 2 repeatedly transmits vehicle data of the edge-equipped vehicle to the management server 3 according to a schedule.

[0148] The mobility GW 111 of the management server 3 stores the received vehicle data as a shadow 114 and generates an updated index 118. The data management unit 121 of the management server 3 stores the updated index 118 as a digital twin 123. The digital twin 123 includes at least the identification information and location information of all edge-equipped vehicles.

[0149] That is, as shown in the upper part of Figure 19, the management server 3 on the cloud stores vehicle data of all vehicles equipped with edge devices 2, which are updated sequentially as shadows 114 and digital twins 123.

[0150] The data collection unit 61 of the service server 5 uses the data acquisition API 146 provided by the management server 3 to repeatedly acquire location information of the registered vehicle 8 that is running the border crossing detection application A1, and stores the latest location information in the vehicle DB 531.

[0151] The data acquisition request input to the data acquisition API 146 may have, for example, a service provision area set as location specification information, a current time set as time specification information, and location information set as acquisition information. The data management unit 121 then generates an object list that specifies the object IDs and current time of all registered vehicles 8 present within the service specification area. The mobility gateway 111 then extracts the latest location information from the shadow 114 according to the object list and returns it to the service server 5.

[0152] <6-2. Operation when an event is detected> 18, when the edge device 2 detects unlocking with the guest authority key, it transmits an unlocking notification to the service server 5 and activates the video camera inside the vehicle. That is, when a person other than the user (i.e., the owner) of the target vehicle unlocks the target vehicle, the video camera starts recording the inside of the vehicle.

[0153] 19, in response to receiving the unlocking notification, the service server 5 sets a geofence including the current position of the target vehicle. For example, the service server 5 sets a rectangular geofence centered on the current position.

[0154] After detecting unlocking, if the edge device 2 detects that the vehicle speed of the target vehicle has exceeded a threshold, it sends a border crossing possibility notification to the service server 5 and uploads a video of the inside of the vehicle to the service server 5.

[0155] In response to receiving the border crossing possibility notification, the service server 5 determines whether the current location of the target vehicle has moved outside the geofence. That is, in response to receiving the unlocking notification, the service server 5 generates a geofence and prepares to execute a movement determination of the target vehicle. Then, in response to receiving the border crossing possibility notification, the service server 5 actually executes a movement determination of the target vehicle.

[0156] In response to determining that the current position of the target vehicle has moved outside the geofence, the service server 5 transmits a border crossing notification to the terminal device 7 linked to the target vehicle. The user of the target vehicle receives a border crossing notification via their own terminal device 7. In response to receiving the border crossing notification, the user's terminal device 7 instructs the service server 5 to carry out a predetermined vehicle control. If the service server 5 has set multiple geofences, the user selects vehicle control according to the current location of the target vehicle via the terminal device 7 and instructs the service server 5 to carry out the selected vehicle control. Before instructing vehicle control, the user can access the service server 5 from the terminal device 7 and check the in-vehicle video, if necessary.

[0157] When the terminal device 7 instructs the service server 5 to control the vehicle, the service server 5 accesses the edge device 2 of the target vehicle via the vehicle control API 148 of the management server 3, and causes the target vehicle to execute predetermined vehicle control.

[0158] The operation of the service server 5 when an event is detected as described above corresponds to the operation when the first embodiment of the event processing is executed. The operation of the service server 5 when an event is detected may be the operation when the second embodiment of the event processing is executed.

[0159] <8. Effects> According to the present embodiment described above in detail, the following effects are achieved. (1) In the first embodiment of the mobility IoT system 1, when a preset event occurs and the target vehicle moves outside the geofence, a border crossing notification is sent to the terminal device 7 linked to the target vehicle. Therefore, even if the vehicle is stolen, the user can immediately recognize the theft. This can alleviate the user's concerns about the vehicle being used by others.

[0160] (2) Furthermore, in the first embodiment, in response to the user receiving the border crossing notification via the terminal device 7, the user can instruct the target vehicle to perform a predetermined vehicle control via the terminal device 7. This can further alleviate the user's concerns about the use of the vehicle by others.

[0161] (3) In the second embodiment of the mobility IoT system 1, when a preset event occurs and the vehicle moves outside the geofence, a predetermined vehicle control is instructed for the registered vehicle 8. Therefore, even if the vehicle crosses the border, the thief is prevented from escaping with the vehicle. This can alleviate the user's concerns about the vehicle being used by others.

[0162] (4) When the service server 5 changes the shape and / or size of the geofence according to the user's authority, the owner can limit the movement range of the target vehicle according to the authority given to the user.

[0163] (5) In response to the target vehicle's speed being equal to or greater than a threshold, a border crossing possibility notification is transmitted from the edge device 2 to the service server 5. In response to receiving the border crossing possibility notification, the service server 5 determines whether the target vehicle has moved outside the geofence. That is, in response to the target vehicle's speed being equal to or greater than a threshold, the service server 5 determines whether a border crossing has occurred. Therefore, it is possible to suppress false detection of a border crossing.

[0164] (Other embodiments) Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0165] (a) In the above embodiment, the service server 5 determines whether the current location of the target vehicle has moved outside the geofence in response to receiving an unlocking notification and a border crossing possibility notification from the edge device 2, but the present disclosure is not limited to this. The service server 5 may set a geofence and determine whether the current location of the target vehicle has moved outside the geofence in response to receiving an unlocking notification from the edge device 2. In this case, the edge device 2 may not need to determine whether the vehicle speed is greater than or equal to a threshold. Consequently, the edge device 2 may not need to send a border crossing possibility notification to the service server 5.

[0166] (b) In the above embodiment, the edge device 2 detects unlocking with guest privileges and activates the video camera inside the vehicle cabin. However, the video camera does not have to be activated. In other words, the edge device 2 does not have to upload the video of the inside of the vehicle cabin to the service server 5.

[0167] (c) The service server 5 may set a geofence of a fixed shape and size without changing the shape and / or size of the geofence depending on the type and / or size of the guest authority.

[0168] (d) The control units 21, 31, and 51 and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to execute one or more functions embodied in a computer program. Alternatively, the control units 21, 31, and 51 and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control units 21, 31, and 51 and the methods described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to execute one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible recording medium. The methods for implementing the functions of each unit included in the control units 21, 31, and 51 do not necessarily need to include software; all of the functions may be implemented using one or more hardware devices.

[0169] (e) In addition to the mobility IoT system, management device, and edge device as the information notification system described above, the present disclosure can also be realized in various forms, such as a program for causing a computer to function as the management device and edge device, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and an information notification method. [Explanation of symbols]

[0170] 1... Mobility IoT system, 2... Edge device, 3... Management server, 5... Service server, 7... Terminal device, 8... Registered vehicle, 21, 31, 51... Control unit, 22... Vehicle IF unit, 23, 32, 52... Communication unit, 24, 33, 53... Memory unit

Claims

1. a management device having a first management unit (3) and a second management unit (5); an edge device (2) mounted on a registered vehicle (8) registered in the second management unit; The edge device a data providing unit (261) configured to repeatedly collect vehicle data including location information of the registered vehicle and a state of the registered vehicle and provide the collected data to the first management unit; an event transmission unit (S20, S60) configured to detect the occurrence of a preset event and transmit an event notification indicating the occurrence of the event to the second management unit; The first management unit a storage unit (113) configured to store the vehicle data repeatedly provided from the edge device in association with the registered vehicle; The second management unit a data acquisition unit (61) configured to acquire the vehicle data stored in the storage unit; a receiving unit (S110, S130, S210, S230) configured to receive the event notification transmitted from the event transmitting unit; a geofence setting unit (S120, S220) configured to set a geofence including a current position of the registered vehicle in response to the event notification being received by the receiving unit; a location identification unit (S100, S140, S200, S240) configured to repeatedly identify a current location of the registered vehicle based on the vehicle data acquired by the data acquisition unit; a determination unit (S150) configured to determine whether the registered vehicle has moved outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit; and a notification sending unit (S160) configured to send a notification indicating that the registered vehicle has moved outside the geofence to a terminal device linked to the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence. Information systems.

2. a management device having a first management unit (3) and a second management unit (5); an edge device (2) mounted on a registered vehicle (8) registered in the second management unit; The edge device a data providing unit (261) configured to repeatedly collect vehicle data including location information of the registered vehicle and a state of the registered vehicle and provide the collected data to the first management unit; an event transmission unit (S20, S60) configured to detect the occurrence of a preset event and transmit an event notification indicating the occurrence of the event to the second management unit; The first management unit a storage unit (113) configured to store the vehicle data repeatedly provided from the edge device in association with the registered vehicle; a vehicle control unit (130) configured to cause the registered vehicle to execute the instructed vehicle control; The second management unit a data acquisition unit (61) configured to acquire the vehicle data stored in the storage unit; a receiving unit (S110, S130, S210, S230) configured to receive the event notification transmitted from the event transmitting unit; a geofence setting unit (S120, S220) configured to set a geofence including a current position of the registered vehicle in response to the event notification being received by the receiving unit; a location identification unit (S100, S140, S200, S240) configured to repeatedly identify a current location of the registered vehicle based on the vehicle data acquired by the data acquisition unit; a determination unit (S150) configured to determine whether the registered vehicle has moved outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit; and a control instruction unit (62) configured to instruct the vehicle control unit to perform predetermined vehicle control on the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence. Information systems.

3. the terminal device is configured to instruct the second management unit to perform predetermined vehicle control of the registered vehicle in response to receiving the notification from the notification sending unit, The first management unit a vehicle control unit (130) configured to cause the registered vehicle to execute the instructed vehicle control; The second management unit The vehicle control system further includes a control instruction unit (62) configured to instruct the vehicle control unit to perform the predetermined vehicle control for the registered vehicle determined to be outside the geofence in response to the predetermined vehicle control being instructed by the terminal device. The information system of claim 1 .

4. The geofence setting unit is configured to change the shape and / or size of the geofence depending on the authority of an occupant of the registered vehicle. The information system according to any one of claims 1 to 3.

5. the event notification includes a first event notification and a second event notification; the event transmission unit is configured to transmit the first event notification to the second management unit in response to detecting the occurrence of the event, and to transmit the second event notification to the second management unit in response to a vehicle speed of the registered vehicle becoming equal to or greater than a threshold after transmitting the first event notification, the geofence setting unit is configured to set the geofence in response to the first event notification being received by the receiving unit; The determination unit is configured to determine, in response to the reception of the second event notification by the receiving unit, that the registered vehicle has moved outside the geofence. The information system according to any one of claims 1 to 4.

6. The geofence setting unit is configured to set a plurality of geofences having different sizes, and a first geofence among the plurality of geofences includes a second geofence that is smaller than the first geofence. The information system according to any one of claims 1 to 5.

7. A management device comprising a first management unit (3) and a second management unit (5), and constituting an information system (1) together with an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, The first management unit a storage unit (113) configured to store vehicle data including location information repeatedly provided from the edge device in association with the registered vehicle; The second management unit a data acquisition unit (61) configured to acquire the vehicle data stored in the storage unit; a receiving unit (S110, S130, S210, S230) configured to receive an event notification indicating the occurrence of a preset event transmitted from the edge device; a geofence setting unit (S120, S220) configured to set a geofence including a current position of the registered vehicle in response to the event notification being received by the receiving unit; a location identification unit (S100, S140, S200, S240) configured to repeatedly identify a current location of the registered vehicle based on the vehicle data acquired by the data acquisition unit; a determination unit (S150) configured to determine whether the registered vehicle has moved outside the geofence set by the geofence setting unit based on the current position identified by the position identification unit; and a notification sending unit (S160) configured to send a notification indicating that the registered vehicle has moved outside the geofence to a terminal device linked to the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence. Management device.

8. A management device comprising a first management unit (3) and a second management unit (5), and constituting an information system (1) together with an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, The first management unit a storage unit (113) configured to store vehicle data including location information repeatedly provided from the edge device in association with the registered vehicle; a vehicle control unit (130) configured to cause the registered vehicle to execute the instructed vehicle control; The second management unit a data acquisition unit (61) configured to acquire the vehicle data stored in the storage unit; a receiving unit (S110, S130, S210, S230) configured to receive an event notification indicating the occurrence of a preset event transmitted from the edge device; a geofence setting unit (S120, S220) configured to set a geofence including a current position of the registered vehicle in response to the event notification being received by the receiving unit; a location identification unit (S100, S140, S200, S240) configured to repeatedly identify a current location of the registered vehicle based on the vehicle data acquired by the data acquisition unit; a determination unit configured to determine whether the registered vehicle has moved outside the geofence set by the geofence setting unit, based on the current position identified by the position identification unit; and and a control instruction unit (62) configured to instruct the vehicle control unit to perform predetermined vehicle control on the registered vehicle when the determination unit determines that the registered vehicle has moved outside the geofence. Management device.

9. An information notification method executed by an information system (1) comprising a management device having a first management unit (3) and a second management unit (5) and an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, The edge device repeatedly collecting vehicle data including location information of the registered vehicle and a state of the registered vehicle and providing the same to the first management unit; Detecting the occurrence of a preset event and transmitting an event notification indicating the occurrence of the event to the second management unit; The first management unit The vehicle data repeatedly provided from the edge device is stored in a storage unit in association with the registered vehicle; The second management unit Acquire the vehicle data stored in the storage unit; In response to receiving the event notification, a geofence including a current position of the registered vehicle is set; repeatedly determining the current location of the registered vehicle based on the acquired vehicle data; determining whether the registered vehicle has moved outside the established geofence based on the identified current location; When it is determined that the registered vehicle has moved outside the geofence, a notification indicating that the registered vehicle has moved outside the geofence is sent to a terminal device linked to the registered vehicle. Information notification method.

10. A vehicle control method executed by an information system (1) comprising a management device having a first management unit (3) and a second management unit (5), and an edge device (2) mounted on a registered vehicle (8) registered in the second management unit, comprising: The edge device repeatedly collecting vehicle data including location information of the registered vehicle and a state of the registered vehicle and providing the same to the first management unit; Detecting the occurrence of a preset event and transmitting an event notification indicating the occurrence of the event to the second management unit; The first management unit The vehicle data repeatedly provided from the edge device is stored in a storage unit in association with the registered vehicle; The second management unit Acquire the vehicle data stored in the storage unit; In response to receiving the event notification, a geofence is set that includes a current position of the registered vehicle; repeatedly determining the current location of the registered vehicle based on the acquired vehicle data; determining whether the registered vehicle has moved outside the established geofence based on the identified current location; When determining that the registered vehicle has moved outside the geofence, instruct the first management unit to perform a predetermined vehicle control on the registered vehicle; The first management unit causing the registered vehicle to execute the predetermined vehicle control in response to the instruction for the predetermined vehicle control from the second management unit; Vehicle control method.

Images