Notification service apparaus for vehicle and control method thereof, relay vehicle

Abstract

The present invention relates to C-V2X (Cellular Vehicle to Everything) and to a vehicle notification service device and a method of operation of the vehicle notification service device for effectively delivering notification messages regarding event situations occurring on the road by extending the target of the vehicle notification service to all vehicles (terminals) that have installed an API provided by a service provider.

Description

Technology Field

[0001] The present invention relates to C-V2X (Cellular Vehicle to Everything) and to a method for effectively delivering notification messages regarding event situations occurring on the road by extending the target of a vehicle notification service to all vehicles (terminals) that have installed an API provided by a service provider. Background Technology

[0002] Major companies in the automotive and mobile industries have launched the 5G Automotive Association (5GAA), and the 5GAA has set C-V2X (Cellular Vehicle to Everything) technology as one of its core goals.

[0003] C-V2X refers to a communication technology designed to lay the foundation for safe and interconnected vehicles of the future by exchanging information, such as traffic data, with other vehicles and infrastructure-equipped objects, including roads, via wired or wireless networks while driving.

[0004] Such C-V2X can be understood as encompassing all communication technologies applicable to vehicles on the road, such as V2V (Vehicle to Vehicle), V2I (Vehicle to Infra), and V2N (Vehicle to Nomadic Devices), in order to lay the foundation for safe and interconnected vehicles of the future.

[0005] Accordingly, in a C-V2X environment, moving away from the methods used in V2V and V2I that utilize existing Wave terminals, terminals can adopt a format where they receive services through network connections, and based on this, a vehicle notification service can be implemented to deliver road event situations in the form of messages.

[0006] However, in order to implement the aforementioned vehicle notification service in an existing C-V2X environment, it is necessary for a specific application (e.g., T-map application) to be installed identically on the vehicle (terminal) intending to use the service; consequently, there is a problem in that service usage may be restricted on vehicles (terminals) that do not have the application installed.

[0007] Accordingly, the present invention proposes a method for delivering notification messages by expanding the range of vehicles (terminals) capable of providing vehicle notification services. Meanwhile, the technology forming the background of the present invention is disclosed in 'Korean Patent Publication No. 10-2011-0071494 (June 29, 2011)'. The problem to be solved

[0008] The present invention was created in consideration of the above circumstances, and the objective of the present invention is to effectively deliver notification messages regarding event situations occurring on the road by extending the target of the vehicle notification service in a C-V2X (Cellular Vehicle to Everything) environment to all vehicles (terminals) that have installed the API provided by the service provider. means of solving the problem

[0009] A vehicle notification service device according to an embodiment of the present invention for achieving the above objective comprises: a management unit that manages vehicle-specific location information received from each vehicle that has been issued a service ID for a vehicle notification service; and a notification unit that, when a notification area is determined according to the occurrence of an event, selects a vehicle located in the notification area based on the vehicle-specific location information and delivers a notification message to each selected vehicle.

[0010] Specifically, the management unit can manage location information received from each vehicle issued the service ID by matching it to a location on a link corresponding to a road section on a map.

[0011] Specifically, the vehicle notification service device may further include a determination unit that determines the notification area by matching the point where the event occurred to a location on a link corresponding to a road section on a map.

[0012] Specifically, the determination unit may determine the area between the start position and the end position on the link, which is designated as at least one of the forward and behind regions with respect to the vehicle's direction of travel according to the type of event based on the location on the link corresponding to the point where the event occurred, as the notification area.

[0013] Specifically, the notification unit can select a vehicle located on a link that matches the notification area based on the location on the managed link for each vehicle to which the service ID was issued.

[0014] Specifically, when a vehicle located in the notification area is selected, the notification unit may generate and transmit the notification message for each selected vehicle, the message including at least one of the type of the event, the location where the event occurred, and the distance from the location where the event occurred.

[0015] A method of operation of a vehicle notification service device according to an embodiment of the present invention for achieving the above objective comprises: a management step of managing vehicle-specific location information received from each vehicle that has been issued a service ID for a vehicle notification service; and a notification step of, when a notification area is determined according to the occurrence of an event, selecting a vehicle located in the notification area based on the vehicle-specific location information and delivering a notification message to each selected vehicle.

[0016] Specifically, the above management step can manage location information received from each vehicle issued the above service ID by matching it to a location on a link corresponding to a road section on a map.

[0017] Specifically, the above method may further include a determination step of determining the notification area by matching the point where the event occurred to a location on a link corresponding to a road section on a map.

[0018] Specifically, the above determination step may determine the area between the start position and the end position on the link, which is designated as at least one of the forward and behind regions with respect to the vehicle's direction of travel according to the type of event based on the location on the link corresponding to the point where the event occurred, as the notification area.

[0019] Specifically, the notification step may select a vehicle located on a link that matches the notification area, based on the location on the managed link for each vehicle issued the service ID.

[0020] Specifically, the notification step may generate and transmit the notification message for each selected vehicle when a vehicle located in the notification area is selected, the notification message may include at least one of the type of the event, the point where the event occurred, and the distance from the point where the event occurred. Effects of the invention

[0021] Accordingly, according to the vehicle notification service device and the method of operation of the vehicle notification service device of the present invention, it is possible to effectively deliver notification messages regarding event situations occurring on the road by expanding the range of vehicles (terminals) capable of vehicle notification services, thereby allowing for improved user satisfaction with vehicle notification services and expansion of the service area. Brief explanation of the drawing

[0022] FIG. 1 is an example diagram illustrating a network configuration in a conventional C-V2X environment. FIG. 2 is an exemplary diagram illustrating a vehicle notification service environment according to an embodiment of the present invention. FIG. 3 is a schematic diagram illustrating a vehicle notification service device according to an embodiment of the present invention. FIGS. 4 and FIGS. 5 are exemplary diagrams for explaining a method of managing location data per vehicle according to an embodiment of the present invention. FIG. 6 is an illustrative diagram for explaining a method of calculating a position on a link according to an embodiment of the present invention. FIG. 7 is an illustrative diagram for explaining whether a link moves according to an embodiment of the present invention. FIG. 8 is an exemplary diagram showing a service flow according to an embodiment of the present invention. FIG. 9 is an exemplary diagram illustrating a notification area determination method according to an embodiment of the present invention. FIGS. 10 and 11 are flowcharts for explaining the operation method of a vehicle notification service device according to an embodiment of the present invention. Specific details for implementing the invention

[0023] Hereinafter, preferred embodiments of the present invention will be described with reference to the attached drawings.

[0024] In one embodiment of the present invention, a vehicle notification service is implemented to transmit event situations occurring on the road to a vehicle in the form of a notification message by using C-V2X (Cellular Vehicle to Everything), a communication technology that exchanges information such as traffic information with other vehicles and objects with infrastructure such as roads through a wired / wireless network while driving.

[0025] The network configuration of C-V2X can include all communication technologies applicable to vehicles on the road, such as V2V (Vehicle to Vehicle), V2I (Vehicle to Infra), and V2N (Vehicle to Nomadic Devices), for example, as shown in Fig. 1.

[0026] For example, traffic or environmental information can be transmitted via existing LTE / 5G networks, while V2V can be used for vehicle-to-vehicle communication requiring low latency, such as collision avoidance.

[0027] In this case, the performance is the same as the coverage of the existing LTE network, and the service can be provided with a maximum of 75 Mbps (typically several hundred kbps to several Mbps), latency of 100 ms for V2N (typically 50 ms) and within 20 ms for V2V, and it has the advantage of low investment costs as it mostly uses existing communication networks and enables interoperability between communication operators through V2N.

[0028] However, there is a limitation in that delays may occur in traffic-dense areas, requiring technology for separate QoS management for regions where traffic is momentarily concentrated, and thus necessitating the optional installation of Road Side Units (RSUs).

[0029] In this regard, a vehicle notification service according to one embodiment of the present invention can be implemented based on the T-map V2X service.

[0030] The T-map V2X service can be understood as a location-based service that provides appropriate services and notifications based on the location of a terminal (T-map user) using a navigation application (e.g., T-map application) within a terminal (e.g., a smartphone) corresponding to (V) of V2N.

[0031] In this T-map V2X service, since the terminal's navigation application (e.g., T-map application) basically supports the function of mapping location information to map information for processing, there is an advantage in that the server corresponding to (N) in V2N can be configured much more simply; however, there is also a limitation in that the installation of a navigation application on the terminal is required to use the service.

[0032] Accordingly, in order to overcome the above limitations of the T-map V2X service, a service method is adopted that is similar to the aforementioned T-map V2X service, but the terminal corresponding to (V) of V2X is not limited to a navigation application (e.g., T-map application), but is extended to all terminals that have installed an API provided by a service provider.

[0033] That is, in a vehicle notification service according to one embodiment of the present invention, the target of the vehicle notification service can be extended from a terminal with a navigation application installed to any terminal capable of connecting to a GPS and network, such as a black box or an in-vehicle navigation system.

[0034] In this regard, FIG. 2 schematically shows a vehicle notification service environment according to one embodiment of the present invention.

[0035] As illustrated in FIG. 2, a vehicle notification service environment according to one embodiment of the present invention may include a vehicle notification service device (20) that transmits a notification message about an event occurring on the road to a vehicle (VD).

[0036] The vehicle notification service device (20) can be implemented as part of a platform built in a C-V2X environment, for example, in the form of a server accessible via a wired or wireless communication network.

[0037] In this way, when the vehicle notification service device (20) is implemented in the form of a server, it may be implemented in the form of, for example, a cloud server, a web server, a database server, a proxy server, etc., and one or more of various software that enables a network load balancing mechanism or service device to operate on the internet or another network may be installed, and through this, it may also be implemented as a computerized system.

[0038] This vehicle notification service device (20) communicates with each vehicle (VD) based on V2N (Vehicle to Nomadic Devices) communication technology and supports a map matching function that matches location information received from each vehicle (VD) at intervals (e.g., 1 second) to a location on a link corresponding to a road section on a map through a connection with a map matching server (30).

[0039] Meanwhile, in this regard, each vehicle (VD) that communicates with the vehicle notification service device (20) via V2N may be equipped with a terminal that supports network connection functions, and it is assumed that such a terminal can support GPS functions and periodically transmit its own location information.

[0040] Here, for V2N communication technology, for example, the MQTT (MQ Telemetry Transport) protocol can be applied.

[0041] Accordingly, in a vehicle notification service environment according to one embodiment of the present invention, a message broker (10: MB, Message Broker) configured for message transmission between a vehicle notification service device (20) and a vehicle (VD) may be further included by applying the MQTT (MQ Telemetry Transport) protocol.

[0042] In the vehicle notification service environment according to one embodiment of the present invention, through the above configuration, event situations occurring on the road can be transmitted to the vehicle (VD) in the form of a notification message. Below, the configuration of the vehicle notification service device (20) for realizing this will be explained in more detail.

[0043] FIG. 3 schematically shows the configuration of a vehicle notification service device (20) according to one embodiment of the present invention.

[0044] As illustrated in FIG. 3, a vehicle notification service device (20) according to one embodiment of the present invention may include a management unit (21) that manages location information for each vehicle, a determination unit (22) that determines a notification area, and a notification unit (23) that transmits a notification message.

[0045] The entire configuration or at least part of the configuration of the vehicle notification service device (20) may be implemented in the form of a hardware module or a software module, or in a combined form of a hardware module and a software module.

[0046] Here, a software module can be understood as an instruction executed by a processor that processes operations within a vehicle notification service device (20), for example, and such instruction may be in the form of being loaded in a separate memory within the vehicle notification service device (20).

[0047] Meanwhile, a vehicle notification service device (20) according to one embodiment of the present invention may have a configuration that further includes a communication unit (24), which is an RF module responsible for actual communication functions with each component within the service environment, in addition to the configuration described above.

[0048] Here, the communication unit (24) includes, but is not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, and a memory, and may include all known circuits that perform this function.

[0049] The vehicle notification service device (20) according to one embodiment of the present invention can transmit event situations occurring on the road to a vehicle (VD) in the form of a notification message through the above-described configuration. Below, each configuration within the vehicle notification service device (20) for realizing this will be described in more detail.

[0050] The management department (21) performs the function of managing location information for each vehicle (VD).

[0051] More specifically, the management unit (21) receives and manages vehicle-specific location information from each vehicle (VD) that has been issued a service ID for the vehicle notification service.

[0052] At this time, the management unit (21) matches the location information (e.g., GPS information - spherical coordinate system) received from each vehicle (VD) at intervals (e.g., 1 second) through a connection with the map matching server (30) to the position on the link (POL, Position On the Link) corresponding to the road section on the map (e.g., navigation map), and can update and manage the location data for each vehicle (VD) including the map matching results on the DB (Redis).

[0053] In this regard, [Table 1] below shows an example of the form of location information received from each vehicle (VD) that has been issued a service ID, and [Table 2] also shows an example of the form of management of location data per vehicle (VD) including map matching results of such location information.

[0054] Field Type Description DevType String Device types Time String Message creation time DevId String Device ID DevSpeed Int speed DevLocation Location Device location (WGS84-Latitude,Longitude,Altitude)

[0055] Field Type Description Level 1 Level 2 DevId String V2X Device ID DevType String V2X Device type LastmapmachingTimestamp Integer Time of generating the most recent map matching result LastReceivedLocationTimestamp Integer Recent VD location information reception time LinkLength Integer The length of the link where VD is located Pol Integer VD's link location value Locationlist Object VD Location Information lat Double VD Location-Latitude Ion Double VD position-longitude mapmachingResult Object Map matching results idxName String Mesh ID linkid String Link ID roadCategory Integer Road class speed Integer Road speed limit point List Shape information of the link

[0056] Meanwhile, in one embodiment of the present invention, a situation in which N vehicles (VD) are simultaneously connected may be considered, and in such a situation of simultaneous connection, the design of the location data processing logic for each vehicle may have a significant impact on the performance of the system. In this regard, one embodiment of the invention proposes a location data processing logic that considers a situation in which N vehicles (VD) are simultaneously connected as follows.

[0057] That is, when the management unit (21) receives location information from the vehicle (VD), it calls the location data of the vehicle in DB (Redis), and determines the validity of the location data by comparing the time-stamp information on the called location data with the current time.

[0058] At this time, the management unit (21) can determine that the called location data is valid if the difference between the time-stamp information and the current time is less than the threshold time.

[0059] As such, the fact that the difference between the time-stamp information and the current time point is less than a threshold time can be interpreted as the location data being updated and stored in the previous cycle adjacent to the current cycle in which the location information was received from the vehicle (VD).

[0060] Furthermore, the management unit (21) checks whether there is a map matching result in the called location data (Redis), and if there is a map matching result, calculates the location (POL) on the link that matches the location information of the vehicle (VD).

[0061] At this time, the position (POL) on the link that matches the position information of the vehicle (VD) can be calculated as a range value corresponding to 0 up to the length of the target link.

[0062] In this regard, the management unit (21), for example as illustrated in FIG. 4, when the calculated position (POL) on the link is the same as the length of the link (Link A) corresponding to the previous position, matches the position information of the vehicle (VD) to the position (POL) on the new link (Link B) through a connection (map matching API) with the map matching server (30), and from the map matching result value, retrieves new information (e.g., attribute information, shape information) of the link (Link B) and updates the position data of the vehicle (VD) on the DB (Redis).

[0063] However, in order to match the position information of the vehicle (VD) to the position (POL) on the new link (Link B) in this way, the position (POL) on the new link (Link B) calculated for the vehicle (VD) must be at least 0 and at most less than the length of the new link (Link B).

[0064] Here, the above process of updating the location data of the vehicle (VD) by matching the location information of the vehicle (VD) to the location (POL) on the link through a connection (map matching API) with the map matching server (30) can be performed in the same way even if there is no map matching result in the called location data.

[0065] On the other hand, the management unit (21) can update and store the previous position (POL) on the link (Link A) in the vehicle (VD) position data (Redis) as the new position (POL) on the link (Link A) calculated, for example, as shown in FIG. 5, when the calculated position (POL) on the link (Link A) is shorter than the length of the previous position (Link A).

[0066] To aid in understanding the explanation, let us briefly examine the specific method for calculating the position (POL) on the aforementioned link.

[0067] In one embodiment of the present invention, regarding a road network consisting of links representing roads and nodes which are vertices connecting these links, it can be assumed that map data consisting of attribute information (metadata) and shape information (geometry) of nodes and links is managed.

[0068] Here, the shape information can be composed of a polyline that represents the shape of the road as a continuous series of points.

[0069] Accordingly, in one embodiment of the present invention, the input values ​​given to calculate the position (POL) on the link may be the position of the target vehicle (point, WGS84 coordinate system) and the shape of the link (line - Polyline, WGS84 coordinate system), and for example, the position (POL) on the link for the target vehicle may be calculated from the shape of the link based on parameters such as those in [Table 3] below.

[0070] Step(i) i 1 10 meters 2 1 meter 3 0.1 meter

[0071] Here, Step(i) represents the number of steps required to calculate the position (POL) on the link, and the value is a unit used for calculating the distance from the shape of the link, which can be defined as shown in [Equation 1] below. [Equation 1]

[0072] i = * 10 3-i

[0073] ( = 0.1 meter -> The minimum unit of a position (POL) value on a link)

[0074] Below, with reference to Fig. 6, we will explain the process of calculating the position (POL) on the link for each Step (i) according to the parameter definitions as in [Table 3] above.

[0075] First, in Step 1, as shown in Fig. 6(a), the distance from the location of the target vehicle (Ego vehicle) to each point (Pi) was calculated in units of 1, resulting in the distance (*LI i P1, which is the point on the shortest link, can be selected, and in the subsequent step, Step 2, the position of the target vehicle (Ego vehicle) is calculated in increments of 2 for the P0~P2 section.

[0076] Next, in Step 2, as shown in Fig. 6(b), the distance from the location of the target vehicle (Ego vehicle) to each point (Pi) is calculated in units of 2, and the distance (*LI i P6, which is the point on the shortest link, can be selected, and in the subsequent final step, Step 3, the position of the target vehicle (Ego vehicle) is calculated in units of 3 for the P5~P7 section.

[0077] Finally, in Step 3, as shown in Fig. 6(c), the distance from the location of the target vehicle (Ego vehicle) to each point (Pi) was calculated in units of 3, resulting in the distance (*LI i P2, which is the point on the shortest link, can be selected, and the position (POL) on the link for the target vehicle (Ego vehicle) can be finally calculated as “l = 5·2+ 2·3” with reference to [Table 4] below.

[0078] Point l i P0 5·2 P1 5·2+ 1·3 P2 5·2+ 2·3 P3 5·2+ 3·3 P4 5·2+ 4·3 P5 5·2+ 5·3 P6 5·2+ 6·3

[0079] Meanwhile, in relation to the description referring to FIGS. 4 and 5 above, in one embodiment of the present invention, the current position on the link calculated for the target vehicle (POL, t = t i To check whether the link has moved for ), the previous position on the link (POL, t = t i -1) can be used. To explain this, in one embodiment of the present invention, it can be assumed that a target vehicle is located on a road network where two links (LO1, LO2) are consecutive, for example, as shown in FIG. 7.

[0080] Here, the position (POL) on the link calculated for the target vehicle is always greater than 0 and less than or equal to the length of the link.

[0081] In this regard, Figure 7 (a) shows a case where there is no movement of the link.

[0082] That is, for the target vehicle, currently (t = t i ) Calculated position on the link (POL i ) is the transfer of the target vehicle (t = t i -1 ) Location(POL i - It can be confirmed that it is shorter than the total length (L) of link L01 corresponding to 1), and in this case, for the target vehicle, the current (t = t i ) Calculated position on the link (POL i It is possible to determine that there is no movement of the link from ).

[0083] On the other hand, FIG. 7 (b) represents the case where there is movement of the link, and for the target vehicle, the current (t = t i +1 ) Calculated position on the link (POL i + 1) The transfer of the target vehicle (t = t i ) Location(POL i It can be confirmed that it is identical to the total length (L) of link L01 corresponding to ), and in this case, for the target vehicle, the current (t = t i +1 ) Calculated position on the link (POL i + It can be determined from 1) that there is movement of the link.

[0084] However, as such, the location on the link (POL i + 1) If it is determined that there is a movement of the link, the position (POL) on the link is recalculated for LO2 connected to link L01.

[0085] After concluding the additional explanation regarding the calculation of the position (POL) on the above link and the determination of whether the link is moving, we will continue with the explanation of the position information management function of the management unit (21).

[0086] When the management department (21) completes updating the location data by matching the location information of the vehicle (VD) to the location (POL) on the link, it manages the updated location data of the vehicle (VD) on the DB (Redis) in the following structure to distinguish the link unit through the hash below.

[0087] - Key: "ROAD:{RoadID}"

[0088] - Field: "DEV:{DeviceID}"

[0089] - Value: Refer to [Table 5] below

[0090] Here, the Road ID represents a link corresponding to a road section on a map, and through this, in one embodiment of the present invention, it is possible to select target vehicles receiving notification messages on a link basis when an event occurs on the road, thereby reducing the load in selecting notification targets.

[0091] Field Type Description Level 1 Level 2 DevId String V2X Device ID Time String Update time information road_ID String Road ID IdxName String Mesh ID LinkId String Link ID Pol String VD's Position On Link Pfl String VD's Position From Link

[0092] For reference, the aforementioned processes up to the point of updating and managing location data by matching location information received from each vehicle (VD) to a location (POL) on the link can be understood as, for example, the procedures 'd' to 'h' in the service flow of FIG. 8, which involve matching the location information of each vehicle (VD1, VD2) that has been issued a service ID to a location (POL) on the link to update and manage location data. Here, in order to update and manage location data for each vehicle (VD1, VD2), the procedures include: procedure 'a', in which each vehicle (VD1, VD2) connects to the message broker (10), undergoes an authentication process, and completes the connection with the vehicle notification service device (20); procedure 'b', in which the vehicle notification service device (20) applies for a subscription to the message broker (10) to receive location information and event reports from each vehicle (VD1, VD2); and each vehicle (VD1, VD2) connects to the message broker (10) to receive notification messages. 'c' and 'd' applying for a subscription must precede.

[0093] The decision unit (22) performs the function of determining the notification area according to the occurrence of an event.

[0094] More specifically, when the event occurrence is detected according to the event information reported from the vehicle (VD), the decision unit (22) determines a notification area for delivering a notification message corresponding to the detected event.

[0095] For reference, the event information reported from the vehicle (VD) in this manner may include, for example, information on the time of occurrence (time of occurrence, time of end) and information on the location of occurrence (location or area of ​​occurrence).

[0096] At this time, the decision unit (22) can match the location where the event occurred to a location on a link corresponding to a road section on the map based on the detection of the event occurrence, and then determine a notification area for delivering a notification message according to the type of event.

[0097] That is, the decision unit (22) checks whether there is information stored in DB (Redis) by referencing the event ID reported from the vehicle (VD), and if there is no stored information, the event occurrence point is matched and converted to a position on the link (POL, Position On the Link) corresponding to a road section on the map (e.g., navigation map) through linkage with the map matching server (30).

[0098] Next, when the matching conversion for the event occurrence point is completed, the decision unit (22) can determine the area between the start position and the end position on the link, which is designated as at least one of the forward and behind areas for the vehicle's direction of travel according to the type of event, as the notification area.

[0099] For example, referring to FIG. 9, if the type of event is a contact accident, the area 'a' located behind the vehicle's direction of travel relative to the point where the event occurred (o) can be set as the notification area.

[0100] Here, the notification area 'a' can be understood as an area that is located a certain distance away from the point where the event occurred (o) so that the contact accident cannot be visually recognized and a secondary accident may be caused by the sudden braking of the vehicle in front.

[0101] If the type of event is the approach of an emergency vehicle (e.g., ambulance, fire truck), contrary to the example above, the area 'b' located forward relative to the vehicle's direction of travel, based on the event occurrence point (o), can be set as the notification area.

[0102] Here, the notification area 'b' is located at a certain distance from the event occurrence point (o) so that the rear approach of an emergency vehicle cannot be perceived visually or audibly, and can be understood as an area where prior actions such as stopping on the shoulder are required to support the smooth passage of the emergency vehicle.

[0103] The notification unit (23) performs the function of delivering notification messages.

[0104] More specifically, when the notification unit (23) determines the notification area for the occurrence of an event, it selects a vehicle (VD) located in the notification area based on the location information of each vehicle and delivers a notification message regarding the event situation to each selected vehicle (VD).

[0105] At this time, the notification unit (23) can select a vehicle (VD) located on a link that matches the notification area based on the location data of each vehicle (VD) managed by link unit on the DB (Redis), and select each selected vehicle (VD) as a vehicle (VD) that will receive the notification message.

[0106] That is, the notification unit (23) can select a vehicle for receiving a notification message by checking the Road ID from the map information for the link determined as the notification area and obtaining a list of each vehicle (VD) that is managed with location data separated based on the Road ID in the DB (Redis).

[0107] However, based on the Road ID, only all vehicles on the link included in the notification area can be initially selected, and in order to finally select the vehicle receiving the notification message, it is necessary to refer to the detailed location on the managed link for each vehicle selected in this initial manner.

[0108] Furthermore, when a vehicle located in the notification area is selected, the notification unit (23) generates and transmits a notification message for each selected vehicle that includes at least one of the following information: the type of event, the location where the event occurred, and the distance from the location where the event occurred, as shown in [Table 6] below.

[0109] Field Type Description EventID String Event ID EventType String Event types DisToEvent String Distance from the event occurrence point EventLocation Location Event location (WGS84-Latitude,Longitude,Altitude)

[0110] For reference, the aforementioned processes of selecting a vehicle located in the notification area and delivering a notification message in accordance with the occurrence of an event can be understood as the procedure of ‘i’ to ‘n’ in the service flow of FIG. 8 previously exemplified, in which event information is reported from a vehicle (VD1) through the message broker (10), the notification area is determined according to the type of event, and then a vehicle (VD2) located in the notification area is selected and a notification message is delivered again through the message broker (10). As seen above, according to the configuration of the vehicle notification service device (20) according to one embodiment of the present invention, the target of the vehicle notification service can be extended to all vehicles (terminals) that have installed the API provided by the service provider. In particular, by managing the location information of each vehicle (terminal) by matching it to a location on a link corresponding to a road section on a map, it becomes possible to effectively deliver a notification message regarding an event situation occurring on the road, thereby allowing for the expectation of increased user satisfaction with the notification service and expansion of the service area.

[0111] Hereinafter, with reference to FIG. 10, the operation method of a vehicle notification service device (20) according to an embodiment of the present invention will be described.

[0112] First, the management department (21) receives and manages vehicle-specific location information from each vehicle (VD) that has been issued a service ID for the vehicle notification service (S10-S20).

[0113] At this time, the management unit (21) matches the location information (e.g., GPS information - spherical coordinate system) received from each vehicle (VD) that has been issued a service ID at a period (e.g., 1 second) to the location (POL, Position On the Link) on the Link corresponding to the road section on the map (e.g., navigation map) through linkage with the map matching server (30), and can update and manage the location data for each vehicle (VD) including the map matching results on the DB (Redis).

[0114] Meanwhile, in one embodiment of the present invention, a situation in which N vehicles (VD) are simultaneously connected may be considered, and in such a simultaneous connection situation, the design of the location data processing logic for each vehicle may have a significant impact on the performance of the system.

[0115] Accordingly, below, we will briefly examine the operation method according to the position data processing logic according to one embodiment of the present invention with reference to FIG. 11.

[0116] First, when the management unit (21) receives location information from the vehicle (VD), it calls the location data of the vehicle in DB (Redis) and determines the validity of the location data by comparing the time-stamp information on the called location data with the current time (S21-S22).

[0117] At this time, the management unit (21) can determine that the called location data is valid if the difference between the time-stamp information and the current time is less than the threshold time.

[0118] As such, the fact that the difference between the time-stamp information and the current time point is less than a threshold time can be interpreted as the location data being updated and stored in the previous cycle adjacent to the current cycle in which the location information was received from the vehicle (VD).

[0119] Furthermore, the management unit (21) checks whether there is a map matching result in the called location data (Redis), and if there is a map matching result, calculates the location (POL) on the link that matches the location information of the vehicle (VD) (S23-S24).

[0120] At this time, the management unit (21), as illustrated in FIG. 4 previously, matches the location information of the vehicle (VD) to the location (POL) on the new link (Link B) through a connection (map matching API) with the map matching server (30) when the calculated location (POL) on the link (Link A) corresponding to the previous location is the same as the length of the link (Link A) corresponding to the previous location. From the map matching result value, the information of the link (Link B) (e.g., attribute information, shape information) is newly retrieved and the location data of the vehicle (VD) on the DB (Redis) is updated (S25-S27).

[0121] However, in order to match the position information of the vehicle (VD) to the position (POL) on the new link (Link B) in this way, the position (POL) on the new link (Link B) calculated for the vehicle (VD) must be at least 0 and at most less than the length of the new link (Link B).

[0122] Here, the process of steps S26-S27, which updates the location data of the vehicle (VD) by matching the location information of the vehicle (VD) to the location (POL) on the link through a connection (map matching API) with the map matching server (30), can be performed in the same way even if, as a result of verification in the preceding step S23, there is no map matching result in the called location data.

[0123] On the other hand, if the position (POL) on the link calculated as shown in FIG. 5, as previously exemplified, is shorter than the length of the link (Link A) corresponding to the previous position, the management unit (21) can update and store the previous position (POL) on the link (Link A) in the position data (Redis) of the vehicle (VD) as the new position (POL) on the calculated link (Link A) as a result of verification in step S25 (S28).

[0124] Afterwards, when the management department (21) completes updating the location data by matching the location information of the vehicle (VD) to the location (POL) on the link, it manages the updated location data of the vehicle (VD) by link unit on the DB (Redis) through hashing as previously mentioned with reference to [Table 3] (S29).

[0125] Having finished the description of the operation method according to the position data processing logic of one embodiment of the present invention, we will continue with the description referring to FIG. 10.

[0126] Meanwhile, the decision unit (22) determines a notification area to deliver a notification message corresponding to the detected event when an event is detected based on event information reported from the vehicle (VD) (S40).

[0127] For reference, the event information reported from the vehicle (VD) in this manner may include, for example, information on the time of occurrence (time of occurrence, time of end) and information on the location of occurrence (location or area of ​​occurrence).

[0128] At this time, the decision unit (22) can match the location where the event occurred to a location on a link corresponding to a road section on the map based on the detection of the event occurrence, and then determine a notification area for delivering a notification message according to the type of event.

[0129] That is, the decision unit (22) checks whether there is information stored in DB (Redis) by referencing the event ID reported from the vehicle (VD), and if there is no stored information, the event occurrence point is matched and converted to a position on the link (POL, Position On the Link) corresponding to a road section on the map (e.g., navigation map) through linkage with the map matching server (30).

[0130] Next, when the matching conversion for the event occurrence point is completed, the decision unit (22) can determine the area between the start position and the end position on the link, which is designated as at least one of the forward and behind areas for the vehicle's direction of travel according to the type of event, as the notification area.

[0131] Referring to Fig. 9, which was previously exemplified, if the type of event is a contact accident, the area 'a' located behind the vehicle's direction of travel relative to the point where the event occurred (o) can be set as the notification area.

[0132] Here, the notification area 'a' can be understood as an area that is located a certain distance away from the point where the event occurred (o) so that the contact accident cannot be visually recognized and a secondary accident may be caused by the sudden braking of the vehicle in front.

[0133] If the type of event is the approach of an emergency vehicle (e.g., ambulance, fire truck), contrary to the example above, the area 'b' located forward relative to the vehicle's direction of travel, based on the event occurrence point (o), can be set as the notification area.

[0134] Here, the notification area 'b' is located at a certain distance from the event occurrence point (o) so that the rear approach of an emergency vehicle cannot be perceived visually or audibly, and can be understood as an area where prior actions such as stopping on the shoulder are required to support the smooth passage of the emergency vehicle.

[0135] Afterwards, when the notification unit (23) determines the notification area for the occurrence of an event, it selects the vehicle (VD) located in the notification area based on the location information of each vehicle and delivers a notification message about the event situation to each selected vehicle (VD) (S70).

[0136] At this time, the notification unit (23) can select a vehicle (VD) located on a link that matches the notification area based on the location data of each vehicle (VD) managed by link unit on the DB (Redis), and select each selected vehicle (VD) as a vehicle (VD) that will receive the notification message.

[0137] That is, the notification unit (23) can select a vehicle for receiving a notification message by checking the Road ID from the map information for the link determined as the notification area and obtaining a list of each vehicle (VD) that is managed with location data separated based on the Road ID in the DB (Redis).

[0138] However, based on the Road ID, only all vehicles on the link included in the notification area can be initially selected, and in order to finally select the vehicle receiving the notification message, it is necessary to refer to the detailed location on the managed link for each vehicle selected in this initial manner.

[0139] Furthermore, when a vehicle located in the notification area is selected, the notification unit (23) generates and transmits a notification message for each selected vehicle that includes at least one of the information of the type of event, the location where the event occurred, and the distance from the location where the event occurred, as shown in [Table 4] previously exemplified.

[0140] As described above, according to the operation method of the vehicle notification service device (20) according to one embodiment of the present invention, the target of the vehicle notification service can be extended to all vehicles (terminals) that have installed the API provided by the service provider, and in particular, by managing the location information of each vehicle (terminal) by matching it to a location on a link corresponding to a road section on a map, it becomes possible to effectively deliver notification messages regarding event situations occurring on the road, thereby allowing for improved user satisfaction with the notification service and expansion of the service area.

[0141] Meanwhile, the operation method of the vehicle notification service device (20) according to one embodiment of the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., either individually or in combination. The program instructions recorded on the medium may be those specifically designed and configured for the present invention, or may be those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The above-described hardware device may be configured to operate as one or more software modules to perform the operation of the present invention, and vice versa.

[0142] Although the present invention has been described in detail with reference to preferred embodiments, the present invention is not limited to the above-described embodiments, and the technical concept of the present invention extends to the scope in which various modifications or alterations are possible by anyone with ordinary knowledge in the technical field to which the present invention belongs, without departing from the gist of the present invention as claimed in the following claims. Industrial applicability

[0143] According to the vehicle notification service device and the method of operation of the vehicle notification service device according to the present invention, the target of the vehicle notification service in a C-V2X (Cellular Vehicle to Everything) environment is extended to all vehicles (terminals) that have installed the API provided by the service provider, and notification messages regarding event situations occurring on the road can be effectively delivered. In this respect, the invention overcomes the limitations of existing technology, and thus, not only is there sufficient possibility for the commercialization or business of the applied device rather than just the use of the related technology, but it is also an invention that is clearly and realistically implementable, and therefore has industrial applicability. Explanation of the symbols

[0144] 10: Message Broker 20: Vehicle notification service device 21: Management Department 22: Decision Department 23: Notification Department 30: Map Matching Server

Claims

Claim 1 A vehicle notification service device comprises: a management unit that manages vehicle-specific location information received from each vehicle that has been issued a service ID for the vehicle notification service; When a notification area is determined following the occurrence of an event, the system includes a notification unit that selects a vehicle located within the notification area based on the vehicle-specific location information and delivers a notification message to each selected vehicle. The vehicle-specific location information and the notification message are transmitted via the message broker between the vehicle notification service device, which has subscribed to the message broker (MB) to receive vehicle location information and event reports, and the vehicle, which has subscribed to the message broker to receive the notification message. The management unit manages location information received from each vehicle issued the service ID by matching it to a location on a link corresponding to a road section on a map, and calculates the point on the link closest to the vehicle as the vehicle's location for each step required to calculate the vehicle's location on the link. It implements points along the shape of the link at shorter distance intervals compared to adjacent previous steps as the steps progress starting from a specific distance unit interval. When location information is received from a vehicle, it retrieves the location data of the vehicle from the DB (Redis), and the difference between the time-stamp information on the location data and the current time point A vehicle notification service device characterized by determining that location data is valid only when the time is less than a threshold time, matching location information received from a vehicle to a location on a link based on a Road ID for each link corresponding to a road section on a map in order to update the location data recognized as valid, and the notification unit confirming a specific Road ID of a link matching the notification area and selecting a vehicle receiving a notification message using a list of vehicles managing location data based on the specific Road ID on the DB (Redis). Claim 2 delete Claim 3 A vehicle notification service device according to claim 1, characterized in that the vehicle notification service device further includes a determination unit that determines the notification area by matching the point where the event occurred to a location on a link corresponding to a road section on a map. Claim 4 A vehicle notification service device according to claim 3, wherein the determining unit determines the area between the starting position and the ending position on the link, which is designated as at least one of the forward and behind regions with respect to the vehicle's direction of travel according to the type of event based on the position on the link corresponding to the point where the event occurred, as the notification area. Claim 5 delete Claim 6 A vehicle notification service device according to claim 1, wherein the notification unit, when a vehicle located in the notification area is selected, generates and transmits the notification message for each selected vehicle, the message including at least one of the type of the event, the point where the event occurred, and the distance from the point where the event occurred. Claim 7 A method of operation of a vehicle notification service device, comprising: a management step for managing vehicle-specific location information received from each vehicle that has been issued a service ID for the vehicle notification service;The method includes a notification step in which, once a notification area is determined following the occurrence of an event, a vehicle located within the notification area is selected based on the vehicle-specific location information, and a notification message is delivered to each selected vehicle. The vehicle-specific location information and the notification message are transmitted via the message broker between the vehicle notification service device that has subscribed to the message broker (MB) to receive vehicle location information and event reports, and the vehicle that has subscribed to the message broker to receive the notification message. The management step manages location information received from each vehicle issued the service ID by matching it to a location on a link corresponding to a road section on a map, and calculates the point on the link closest to the vehicle as the vehicle's location for each step required to calculate the vehicle's location on the link. It implements points along the shape of the link at shorter distance intervals by comparing them with adjacent previous steps as the steps progress starting from a specific distance unit interval. When location information is received from a vehicle, the location data of the vehicle from which the location information was received is retrieved from the DB (Redis), and the time-stamp information on the location data and the current time point A method of operation of a vehicle notification service device, wherein location data is determined to be valid only when the difference is less than a threshold time, and to update the valid location data, location information received from a vehicle is matched to a location on a link based on a Road ID for each link corresponding to a road section on a map, and the notification step is characterized by confirming a specific Road ID of a link matching the notification area and selecting a vehicle receiving a notification message using a list of vehicles managing location data based on the specific Road ID in the DB (Redis). Claim 8 delete Claim 9 A method of operation of a vehicle notification service device according to claim 7, wherein the method further includes a determination step of determining the notification area by matching the point where the event occurred to a location on a link corresponding to a road section on a map. Claim 10 A method of operation of a vehicle notification service device according to claim 9, wherein the determination step determines the area between the start position and the end position on the link, which is designated as at least one of the forward and behind regions with respect to the direction of travel of the vehicle according to the type of event based on the location on the link corresponding to the point where the event occurred, as the notification region. Claim 11 delete Claim 12 A method of operation of a vehicle notification service device according to claim 7, wherein the notification step is characterized by generating and transmitting a notification message for each selected vehicle, the notification message including at least one of the type of the event, the point where the event occurred, and the distance from the point where the event occurred, when a vehicle located in the notification area is selected.

Images