IP Library Granted Patent US 12682696
Granted Patent B2
US 12682696 · App. 18/384,227 · Granted Jul 14, 2026

Electronic device and method for managing event in vehicle communication system

Inventor: Taekyu Han (Seongnam-si, KR)
Assignee: THINKWARE CORPORATION
G07C5/02G06F21/602
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12682696
App. No.
18/384,227
Granted
Jul 14, 2026
Kind
B2
Abstract

In embodiments, a device of a vehicle includes at least one transceiver, memory configured to store instructions, and at least one processor operably coupled to the memory and the at least one transceiver. The at least one processor is, when the instructions are executed, configured to receive an event message related to an event of a source vehicle. The event message includes identification information on a serving road side unit (RSU) of the source vehicle and direction information indicating a driving direction of the source vehicle. The at least one processor is, when the instructions are executed, configured to identify whether the serving RSU of the source vehicle is included in a driving list of the vehicle.

Claims (65)

1 . A device of a vehicle, the device comprising:

at least one transceiver;

memory configured to store instructions; and

at least one processor operably coupled to the memory and the at least one transceiver, wherein the at least one processor is, when the instructions are executed, configured to:

obtain an expected driving path and a driving list of the vehicle including a plurality of road side units (RSUs) along with the expected driving path; and

receive, from a source vehicle, an event message related to an event of the source vehicle, wherein the event message includes identification information on a serving RSU of the source vehicle and direction information indicating a driving direction of the source vehicle,

identify whether the serving RSU of the source vehicle is included in the plurality of RSUs of the driving list of the vehicle,

identify whether the driving direction of the source vehicle matches a driving direction of the vehicle,

upon identifying that the driving direction of the source vehicle matches the driving direction of the vehicle and the serving RSU of the source vehicle is included in the plurality of RSUs of the driving list of the vehicle, perform driving according to the event message, and

upon identifying that the driving direction of the source vehicle does not match the driving direction of the vehicle or the serving RSU of the source vehicle is not included in the plurality of RSUs of the driving list of the vehicle, perform driving without the event message.

2 . The device of claim 1 ,

wherein the driving direction indicates one of a first lane direction and a second lane direction opposite to the first lane direction.

3 . The device of claim 1 , wherein the at least one processor is, when the instructions are executed to receive the event message, further configured to:

obtain pre-encryption information including encryption information for each RSU included in the plurality of RSUs of the driving list of the vehicle; and

decrypt the event message of the source vehicle based on encryption information for the serving RSU included in the pre-encryption information, to obtain the identification information for the serving RSU of the source vehicle and the direction information.

4 . The device of claim 3 , wherein the at least one processor is, when the instructions are executed, further configured to:

transmit a service request message to a service provider server through a RSU before receiving the event message, and

receive a service response message corresponding to the service request message from the service provider server through the RSU, and

wherein the service response message includes driving plan information for indicating the expected driving path of the vehicle, the driving list of the vehicle, and

the pre-encryption information.

5 . The device of claim 1 , wherein the at least one processor is, when the instructions are executed, further configured to receive a broadcast message from the serving RSU before receiving the event message of the source vehicle, and

wherein the broadcast message includes identification information for the serving RSU and encryption information for the serving RSU.

6 . The device of claim 1 , wherein the at least one processor is, when the instructions are executed to perform the driving according to the event message, configured to change driving-related setting of the vehicle based on the event message, and

wherein the driving-related setting includes at least one of a driving path of the vehicle, a driving lane of the vehicle, a driving speed of the vehicle, a lane of the vehicle, or braking of the vehicle.

7 . The device of claim 1 , wherein the at least one processor is, when the instructions are executed to perform the driving according to the event message, configured to:

generate a delivery event message based on the event message,

encrypt the delivery event message based on encryption information on a RSU servicing the vehicle, and

transmit the encrypted delivery event message to the RSU or to another vehicle.

8 . The device of claim 1 , wherein the at least one processor is, when the instructions are executed to perform the driving according to the event message, configured to:

transmit an update request message to a service provider server through a RSU servicing the vehicle, and

receive an update message from the service provider server through the RSU,

wherein the update request message includes information related to the event of the source vehicle, and

wherein the update message includes information indicating an updated driving path of the vehicle.

9 . A method performed by a vehicle, the method comprising:

obtaining an expected driving path and a driving list of the vehicle including a plurality of road side units (RSUs) along with the expected driving path; and

receiving, from a source vehicle, an event message related to an event of the source vehicle, wherein the event message includes identification information on a serving RSU of the source vehicle and direction information indicating a driving direction of the source vehicle;

identifying whether the serving RSU of the source vehicle is included in the plurality of RSUs of the driving list of the vehicle;

identifying whether the driving direction of the source vehicle matches a driving direction of the vehicle;

upon identifying that the driving direction of the source vehicle matches the driving direction of the vehicle and the serving RSU of the source vehicle is included in the plurality of RSUs of the driving list of the vehicle, performing driving according to the event message, and

upon identifying that the driving direction of the source vehicle does not match the driving direction of the vehicle or the serving RSU of the source vehicle is not included in the plurality of RSUs of the driving list of the vehicle, performing driving without the event message.

10 . The method of claim 9 ,

wherein the driving direction indicates one of a first lane direction and a second lane direction opposite to the first lane direction.

11 . The method of claim 9 , wherein the receiving the event message comprises:

obtaining pre-encryption information including encryption information for each RSU included in the plurality of RSUs of the driving list of the vehicle; and

decrypting the event message of the source vehicle based on the encryption information for the serving RSU included in the pre-encryption information, to obtain the identification information for the serving RSU of the source vehicle and the direction information.

12 . The method of claim 11 , further comprising:

transmitting a service request message to a service provider server through a RSU before receiving the event message, and

receiving a service response message corresponding to the service request message from the service provider server through the RSU,

wherein the service response message includes driving plan information for indicating the expected driving path of the vehicle,

the driving list of the vehicle, and the pre-encryption information.

13 . The method of claim 9 , further comprising:

receiving a broadcast message from the serving RSU before receiving the event message of the source vehicle, and

wherein the broadcast message includes identification information for the serving RSU and encryption information for the serving RSU.

14 . The method of claim 9 , wherein the performing of the driving according to the event message comprises:

changing driving-related setting of the vehicle based on the event message, and

wherein the driving-related setting includes at least one of a driving path of the vehicle, a driving lane of the vehicle, a driving speed of the vehicle, a lane of the vehicle, or braking of the vehicle.

15 . The method of claim 9 , wherein the performing of the driving according to the event message comprises:

generating a delivery event message based on the event message,

encrypting the delivery event message based on encryption information on a RSU servicing the vehicle, and

transmitting the encrypted delivery event message to the RSU or to another vehicle.

16 . The method of claim 9 , wherein the performing of the driving according to the event message comprises:

transmitting an update request message to a service provider server through a RSU servicing the vehicle, and

receiving an update message from the service provider server through the RSU,

wherein the update request message includes information related to the event of the source vehicle, and

wherein the update message includes information indicating an updated driving path of the vehicle.