Patent Description:
A vehicle is an apparatus which moves a passenger from one place to another place. A representative example is a car. A vehicle-to-everything (V2X) communication technology, which means vehicle-to-object communication, refers to a technology in which the vehicle communicates with other vehicles, pedestrians, road infrastructures, servers, and the like to provide a series of services.

For the V2X, standardization organizations such as Institute of Electrical and Electronics Engineers (IEEE), 3rd Generation Partnership Project (3GPP), etc. provide various communication specifications. Dedicated Short Range Communications (DSRC) is the communication standard protocol based on IEEE <NUM>. Cellular-V2X (C-V2X) is the communication standard protocol based on cellular communication protocol of 3GPP. In general, V2X has focused on vehicle safety through direct communication between vehicles, but recently V2X includes vehicle-to-infrastructure communication for communicating with peripheral devices via a network. From <CIT>, an information push method is known where a server pushes a terminal device with information of a subscribed service in a subscribed service area.

Attempts are being made to extend V2X technology to be applied to pedestrians and other electronic devices, rather than simply being used for vehicle safety, such as vehicle-to-vehicle and vehicle-to-peripheral devices.

The present disclosure provides a road side unit (RSU) for vehicle-to-everything (V2X) service, a method performed by the same and a non-transitory computer-readable medium having computer-readable instructions stored thereon which are defined in the independent claims. Further, optional features are defined in the dependent claims.

It is possible to provide V2X services to more diverse users as well as vehicles.

Hereinafter, the embodiments disclosed in the present specification will be described in detail with reference to the accompanying drawings, but the same or similar components are assigned the same reference numbers regardless of reference numerals, and redundant description thereof will be omitted. The suffixes "module" and "unit" for the components used in the following description are given or mixed in consideration of only the ease of writing the specification, and do not have distinct meanings or roles by themselves. In addition, in describing the embodiments disclosed in the present specification, if it is determined that detailed descriptions of related known technologies may obscure the gist of the embodiments disclosed in the present specification, the detailed description thereof will be omitted. In addition, the accompanying drawings are only for easy understanding of the embodiments disclosed in the present specification, and the technical ideas disclosed in the present specification are not limited by the accompanying drawings.

Terms including an ordinal number, such as first, second, etc., may be used to describe various elements, but the elements are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

When an element is referred to as being "connected" or "coupled" to another element, it is understood that it may be directly connected or coupled to the other element, but other elements may exist in between. On the other hand, when it is mentioned that a certain element is "directly connected" or "directly coupled" to another element, it should be understood that no other element is present in the middle.

The singular expression includes the plural expression unless the context clearly dictates otherwise.

In the present application, terms such as "comprises" or "have" are intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, but it is to be understood that this does not preclude the possibility of addition or existence of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

A vehicle according to an embodiment of the present specification can be defined as a means of transport traveling on a road or track. Vehicles may include automobiles, ships, aircraft, trains, motorcycles, bicycles, and the like. The vehicle may include an internal combustion engine vehicle having an engine as a power source, a hybrid vehicle having an engine and an electric motor as a power source, an electric vehicle having an electric motor as a power source, and combinations thereof.

A vehicle-to-everything (V2X) device according to an embodiment of the present specification refers to a device that provides V2X functions and V2X services to users based on software, and is also referred to as a SoftV2X device. The V2X device may be implemented based on hardware and/or software in an electronic device operated by a user such as User Equipment (UE), mobile station (MS), mobile terminal (MT), user terminal (UT), cellular phone, laptop, handheld device, tablet, drone, consumer electronics, and the like. The V2X device may be mounted on a vehicle or electronic device as an on-board unit (OBU) to provide V2X functions and services to the vehicle. A V2X device disposed inside or outside the vehicle may be connected to the vehicle through a wireless interface to provide V2X functions and V2X services to the vehicle.

<FIG> shows a system to which an embodiment of the present specification is applied.

A system includes a V2X device <NUM> and a V2X server <NUM>. The V2X device <NUM> may communicate with the V2X server <NUM> through the base station <NUM> or a Road Side Unit (RSU) <NUM>. The V2X device <NUM> may communicate with the base station <NUM>, the RSU <NUM>, a neighbor vehicle <NUM> and/or a neighbor V2X device using a wireless communication protocol. There is no limitation on the wireless communication protocol. The wireless communication protocol may include Dedicated Short Range Communications (DSRC), Cellular-V2X (C-V2X), WiFi, BLUETOOTH and/or cellular communication protocols based on 3rd Generation Partnership Project (3GPP) (e.g. Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), etc.).

The V2X server <NUM> receives one or more V2X messages from the V2X device <NUM> within a managed area. The V2X server <NUM> may forward the one or more collected V2X messages to the subscribing V2X device <NUM>.

The V2X message may periodically or aperiodically be transmitted to the V2X server <NUM> by the V2X device <NUM> (or RSU <NUM>), and is a message providing status information of the V2X device <NUM> (or device managed by the RSU <NUM>). For example, the V2X device <NUM> may transmit <NUM> V2X messages per second. The V2X server <NUM> collects V2X messages from multiple V2X devices, and forwards the V2X messages to subscribing V2X devices.

The following table shows examples of information elements included in the V2X message. Not all information elements are required, and names are examples only. Information elements may be added/changed/deleted according to policies or circumstances.

The V2X message transmitted by the V2X device <NUM> to the V2X server <NUM> is called an uplink (UL) V2X message, and the V2X message transmitted by the V2X server <NUM> to the V2X device <NUM> is called a downlink (DL) V2X message.

The V2X device <NUM> may include a processor <NUM> and a memory <NUM>. The processor <NUM> implements the functions of the V2X device <NUM> and may include one or more software modules. The V2X device <NUM> may further include various additional devices according to functions such as a display, a user interface, and a wireless modem.

The V2X server <NUM> is connected to one or more base stations <NUM> and/or RSU <NUM> and includes computing hardware that provides V2X functions and V2X services to the V2X device <NUM>. The V2X server <NUM> may be a Mobile/Mutli-access Edge Computing (MEC)-based server or a centralized-based server. The V2X server <NUM> may be called another name, such as a Geocast server or a SoftV2X server. The V2X server <NUM> may include a processor <NUM> and a memory <NUM>. The processor <NUM> implements the function of the V2X server <NUM>, and may include one or more software modules.

The processors <NUM> and <NUM> may include Application-Specific Integrated Circuits (ASICs), Central Processing Unit (CPU), Application Processor (AP), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), micro-controller, chipset, logic circuits, data processing device and/or combinations thereof. In the software implementation for the following embodiments, the software code for performing the functions described herein may be stored in the memories <NUM> and <NUM> and executed by the processors <NUM> and <NUM>.

Memories <NUM> and <NUM> may store information accessible by processors <NUM> and <NUM>. The information may include instructions executable by the processors <NUM> and <NUM> and/or data processed by the processor. Memories <NUM> and <NUM> may include any form of computer-readable medium operable to store information. For example, the memories <NUM> and <NUM> include read only memory (ROM), random access memory (RAM), digital video disc (DVD), optical disc, flash memory, solid state drive (SSD), hard drive and combinations thereof.

Message Queuing Telemetry Transport (MQTT) is used as a message queuing protocol between the V2X device <NUM> and the V2X server <NUM>, but this is only an example. Advanced Message Queuing Protocol (AMQP), HyperText Transfer Protocol (HTTP), and/or vendor specific protocols may be used.

Now, setting an area for V2X service will be described in more detail. Hereinafter, a tile refers to a geographic basic unit for setting a subscription area. Hereinafter, a rectangle is shown in the form of a tile, but it is only an example. There are no restrictions on the shape of the tile, such as polygons or circles.

<FIG> shows an example of a tile using a quadtree.

The quadtree represents a partition of space in two dimensions by decomposing a map (i.e. world map) into four equal quadrants, subquadrants, and so on. The size of a quadrant varies according to a zoom level, and each quadrant corresponds to a tile. Here, the case where the levels are <NUM>, <NUM>, and <NUM> is shown. The larger the level, the smaller the size of the tile. At each level, a unique ID is assigned to a tile. The tile ID may have the number of bits corresponding to the level.

The V2X device may acquire the ID of the tile in which the V2X device is located based on location information of the V2X device (e.g., latitude and longitude). The V2X device and/or the V2X server may adjust the size of the area by adjusting the level according to the situation.

In the following embodiment, the area for the V2X service is defined as follows.

- Management area: The area managed by the V2X server. The management area includes one or more tiles.

- Subscription area: The area where the V2X device requests a subscription to the V2X server. The subscription area may be referred to as another name, such as a concerned area, an impact area, or a geocast area. The subscription area contains one or more tiles. The subscription area may be included in one management area, and may be defined across a plurality of management areas managed by a plurality of V2X servers.

- Publishing area: The area where the V2X device publishes V2X messages to the V2X server. The publishing area may include one tile in each level. The publishing area may indicate a tile where the V2X device is currently located. Some or all of the publishing area may overlap with the subscription area.

<FIG> shows an example in which a subscription area is set.

A first subscription area is set to the first V2X device <NUM>, and a second subscription area is set to the second V2X device <NUM>. Each V2X device can set/change/delete the subscription area periodically or aperiodically (e.g. when its location is changed). Each V2X device can request setting/change/deletion of the subscription area to the V2X server.

The number of tiles included in the first subscription area is <NUM> and the number of tiles included in the second subscription area is <NUM>, but the number of tiles included in the subscription area or the shape of the subscription area is not limited thereto. The subscription area may include a tile in which the V2X device is located. Alternatively, the subscription area may include one or more tiles other than a tile in which the V2X device is located.

The first V2X device <NUM> may generate a first V2X message and periodically send the first V2X message to the V2X server. The second V2X device <NUM> may generate a second V2X message and periodically send the second V2X message to the V2X server.

The V2X server may forward one or more V2X messages received in or around a subscription area to the V2X device related to the subscription area.

A device that sets a subscription area may be referred to as a "subscriber device". A device that transmits a V2X message to a V2X server can be referred to as a "provider device". A V2X device may be a subscriber device, a provider device, or both a subscriber device and a provider device. The V2X server may forward the V2X messages transmitted by the provider devices in the management area to the subscriber device.

The V2X server may deliver the V2X message of a provider device "associated" to the subscription area of a subscriber device to the subscriber device. A provider device associated with a subscription area of a subscriber device may be referred to as a "subscribed provider device". The provider device associated with the subscription area of the subscriber device may satisfy at least one of the following conditions (i) to (iii): (i) part or all of the publishing area of the provider device overlaps with the subscription area of the subscriber device; (ii) some or all of the subscription area of the provider device overlaps the subscription area of the subscriber device; and/or (iii) the location where the provider device transmits the V2X message is within the subscription area of the subscriber device.

According to condition (i) or (iii), the V2X server delivers V2X messages received in the first subscription area to the first V2X device <NUM>. The V2X server delivers V2X messages received in the second subscription area to the second V2X device <NUM>.

Since the first V2X device <NUM> is located in the second subscription area, the V2X server may forward the first V2X message to the second V2X device <NUM>. The second V2X device <NUM> is a subscriber device, and the first V2X device <NUM> is a subscribed provider device.

Since the second V2X device <NUM> is not located in the first subscription area (which means that condition (i) or condition (iii) is not satisfied), the V2X server does not forward the second V2X message to the first V2X device <NUM>. The second V2X device <NUM> is not a provider device of the first V2X device <NUM>. If condition (ii) is considered, the second V2X device <NUM> may be a provider device of the first V2X device <NUM>.

<FIG> is a flowchart illustrating a method for a V2X service.

In step S510, a V2X device sends a subscription request for requesting subscription of the V2X service to a V2X server. The subscription request may include information about the identifier, location, etc. of the V2X device. The V2X server may transmit a subscription response for granting or rejecting subscription to the V2X device in response to the subscription request.

In step S520, the V2X device may send the area configuration related to the V2X service to the V2X server. The area configuration may be included in a separate message or included in the subscription request. The area configuration includes information about configuration and/or modification of the subscription area.

In step S530, the V2X server may collect V2X messages from V2X devices in the management area, and perform message filtering.

The V2X server receives the first V2X message from the second V2X device (step S541), and receives the second V2X message from the third V2X device (step S542). Assume that the second V2X device belongs to the subscription area of the first V2X device, but the third V2X device does not belong to the subscription area of the first V2X device.

In step S550, the V2X server publishes the first V2X message belonging to the subscription area of the first V2X device to the first V2X device. The first V2X device is a subscriber device and the second V2X device is a provider device. Since a V2X message of the third V2X device is not delivered to the first V2X device, the third V2X device is not a provider device of the first V2X device.

If there are a plurality of V2X messages to be sent to the first V2X device, the plurality of V2X messages may be published separately or as a single message.

Message filtering is that V2X server filters the V2X messages to be transmitted to V2X devices that have completed the subscription request. Message filtering may be referred to as a process of selecting a subscribed provider device associated with a subscriber device among a plurality of provider devices. Filtering conditions may be defined differently depending on the subscription area and/or the state of the V2X device. For example, if the number of V2X devices in the subscription area is large, the filtering conditions may be modified so that more messages are filtered out. Filtering condition may be related to the degree of risk of the V2X device.

While a vehicle travels at high speed, it is necessary to minimize the period at which the V2X message is transmitted so that it can be prepared for a dangerous situation. When the V2X server is connected through an IP network, the time required to transmit a message may be extended, and the transmission delay may increase.

<FIG> shows a system for a V2X service which may be used in connection with an embodiment of the present specification.

To implement a V2X server, local V2X servers <NUM> and <NUM> are used as edge computing devices, and a global V2X server <NUM> is used as a cloud server. Although it is shown that the two local V2X servers <NUM> and <NUM> are connected to the global V2X server <NUM> through an IP network, but there is no limit to the number of connected local V2X servers.

The global V2X server <NUM> manages the local V2X servers <NUM> and <NUM>. The local V2X servers <NUM> and <NUM> may communicate directly with each other, or may communicate through the global V2X server <NUM>. The global V2X server <NUM> may provide each V2X device with local server information on the local V2X server and information on the validity period of the local server information.

Each of the local V2X servers <NUM> and <NUM> has a management area, and provides V2X services to V2X devices in each management area. Each local V2X server may receive a V2X message from a V2X device in the management area. The first local V2X server may deliver the received V2X message to a first V2X device in its management area. The first local V2X server may forward the received V2X message to the second local V2X server. The first local V2X server may deliver the received V2X message to a second V2X device in the management area of the second local V2X server through the global V2X server <NUM>.

The local V2X servers <NUM> and <NUM> may be deployed at the edge of the network, and here an example is shown that they are deployed around base stations <NUM> and <NUM>. The <NUM>:<NUM> connection between the local V2X server and the base station is only an example. A plurality of local V2X servers may be deployed in one base station, or a single local V2X server may be deployed in a plurality of base stations.

The V2X device may receive information about local V2X servers from the global V2X server based on its current location. The V2X device may send a subscription request to the local V2X server and may register a subscription area. The V2X device may transmit its own V2X message to the local V2X server. The V2X device may receive the V2X message of surrounding V2X devices associated with the subscription area from the local V2X server.

<FIG> shows an example in which a boundary area between two local V2X servers is defined.

A first local V2X server <NUM> has a first management area <NUM>, and a second local V2X server <NUM> has a second management area <NUM>. A boundary <NUM> may be set between the two management areas <NUM> and <NUM>. Here, it is shown that there is a rectangular management area and the boundary <NUM> is formed along one side, but the shape of the management area or the boundary is not limited.

A boundary area <NUM> is defined along the boundary <NUM>. The boundary area <NUM> includes a first boundary area 650a belonging to the first management area <NUM> of the first local V2X server <NUM> and a second boundary area 650b belong to the second management area <NUM> of the second local V2X server <NUM>. It is shown that each of the first boundary area 650a and the second boundary area 650b includes tiles which are adjacent to the boundary <NUM> and area arranged along the boundary <NUM>, but this is only an example. Each of the first boundary area 650a and the second boundary area 650b may include tiles adjacent to the boundary <NUM>.

All or part of the subscription area of the V2X device <NUM> may overlap with the boundary area <NUM>. At least one of the first local V2X server <NUM> and the second local V2X server <NUM> may transmit the V2X message to the V2X device <NUM>.

The V2X device <NUM> may be located in the boundary area <NUM>. This may mean that the publishing area of the V2X device <NUM> overlaps the boundary area <NUM>. The V2X device <NUM> transmits the V2X message to at least one of the first local V2X server <NUM> and the second local V2X server <NUM>.

The V2X device may receive local server information about the first and second local V2X servers and validity period information from the global V2X server. The local server information may include information about the ID of the local V2X server, the management area and/or the boundary area of the local V2X server. The validity period information indicates a period during which the local V2X server information is valid. When the validity period expires, the V2X device may try to receive the local server information again from the global V2X server.

<FIG> shows a connection between an RSU and a local V2X server.

An RSU is deployed around the road and can communicate with V2X devices such as vehicles or pedestrians through a wireless medium based on a direct communication protocol (for example, DSRC, C-V2X, etc.). A V2X device that supports only communication with the RSU and/or device-to-device direct communication is called a legacy V2X device. The legacy V2X device can only communicate with the RSU, not directly with the V2X server. A V2X device communicating with the V2X server is not connected to the RSU, and can only receive a V2X message transmitted by the RSU.

A first RSU <NUM> is connected to a local V2X server <NUM> through a wired and/or wireless network. The local V2X server <NUM> is connected to a global V2X server <NUM> through an IP network. A second RSU <NUM> is also connected to the local V2X server <NUM> through a wired and/or wireless network. Although it shows that the local V2X server <NUM> is connected to two RSUs <NUM> and <NUM>, one or more RSUs may be connected to the local V2X server <NUM>.

The RSUs <NUM> and <NUM> may be connected to the local V2X server <NUM> and/or the V2X device based on various wireless/wired communication protocols such as DSRC, C-V2X, cellular communication, a dedicated link, etc. The RSUs <NUM> and <NUM> receive a message from the local V2X server <NUM> through a wireless link or a wired link such as Ethernet, IP network, etc., and transmit a radio signal to the V2X device through a wireless link such as DSRC, C-V2X, etc. The RSUs <NUM> and <NUM> may receive a message from the V2X device via a wireless link, and deliver this message to the local V2X server <NUM> via a wireless link or a wired link.

Although the RSUs <NUM> and <NUM> and the local V2X server <NUM> are shown to be separated, this is only an example. The RSUs <NUM> and <NUM> and the local V2X server <NUM> may be integrally implemented, or the RSUs <NUM> and <NUM> may perform some of the functions of the local V2X server <NUM>.

Each of the RSUs <NUM> and <NUM> may include a memory and a processor. The memory may store information accessible by the processor. The information may include instructions executable by the processor and/or data processed by the processor. The RSUs <NUM> and <NUM> may further include a wireless modem for wireless link communication and a wired modem for wired link communication.

An RSU management area refers to a geographic area managed by an RSU. The RSU management area may include an area to which a radio frequency (RF) signal of the RSU arrives. A V2X device located in the RSU management area may receive a message transmitted by the RSU.

An RSU subscription area is the area where the RSU requests a subscription to the V2X server. The RSU subscription area may include one or more tiles. The RSU subscription area is defined by the RSU and may be set simultaneously with or separately from a subscription request. The RSU subscription area may be configured for each RSU by the V2X server. The RSU subscription area may overlap with the RSU management area, and there is no limitation in setting these areas.

The V2X server may deliver the V2X message of the V2X device 'associated' with the RSU subscription area to the RSU. A V2X device associated with the RSU subscription area may satisfy at least one of the following conditions (i) to (iii): (i) some or all of the announcement area of the V2X device overlaps the RSU subscription area; (ii) a part or all of the subscription area of the V2X device overlaps the RSU subscription area; and (iii) the location where the V2X device transmits the V2X message is within the RSU subscription area.

<FIG> shows an example in which a message is delivered from a V2X device to a legacy V2X device.

A V2X device <NUM> transmits a V2X message to a local V2X server <NUM> (S810). When the V2X device <NUM> is associated with the RSU subscription area of an RSU <NUM>, the local V2X server <NUM> transmits the V2X message to the RSU <NUM> (S820). The RSU <NUM> converts the received V2X message into a format that the legacy V2X device <NUM> is able to receive, and transmits the converted message to the legacy V2X device <NUM> (S830).

<FIG> shows an example in which a message is delivered from a legacy V2X device to a V2X device.

A legacy V2X device <NUM> transmits a legacy V2X message to an RSU <NUM> (S910). The RSU <NUM> converts the legacy V2X message into a V2X message that the V2X device <NUM> can receive. For example, the V2X message may further include information about the publishing area of the legacy V2X device <NUM>. The RSU <NUM> transmits the V2X message to a local V2X server <NUM> (S920). When the legacy V2X device <NUM> is associated with the subscription area of a V2X device <NUM>, the local V2X server <NUM> transmits the V2X message to the V2X device <NUM> (S930).

The legacy V2X device is based on direct communication, and does not support the aforementioned areas (e.g., subscription area, announcement area, etc.) for the V2X server. In order to support the V2X server, the RSU may set a virtual subscription area and/or publishing area to the legacy V2X device.

The virtual subscription area refers to the subscription area of the legacy V2X device set by the RSU. The virtual publishing area refers to the publishing area of the legacy V2X device set by the RSU. The RSU can register the virtual subscription area with the local V2X server and complete the subscription request. A V2X device in which the virtual publishing area and/or the virtual subscription area is set is called a virtual V2X device. The RSU may add the virtual publishing area to a V2X message received from the virtual V2X device, and deliver the added V2X message to the local V2X server.

The local V2X server (and/or RSU) may allocate a virtual V2X ID to each virtual V2X device. The virtual V2X ID may be used to identify the virtual V2X device for communication between the local V2X server and the RSU. Because the legacy V2X device cannot make a request for subscription on its own, the local V2X server may consider that the legacy V2X device with virtual V2X IDs have completed a subscription request. The local V2X server (and/or RSU) may add a virtual V2X ID to a V2X message received from a legacy V2X device (or replace a V2X ID with a virtual V2X ID), and transmit the added V2X message to other V2X devices. If the virtual V2X ID is included in the V2X message received from the V2X device, the local V2X server or RSU may generate a V2X message from which the virtual V2X ID is removed, and may transmit the generated V2X message to the legacy V2X device.

<FIG> shows an example according to the present invention in which a message is transmitted to a virtual V2X device.

An RSU <NUM> sets an RSU subscription area 1030a and a virtual subscription area 1040a for a legacy V2X device <NUM>.

A V2X device <NUM> transmits a V2X message to a local V2X server <NUM> (S1010). The V2X device <NUM> is not associated with the RSU subscription area 1030a of the RSU <NUM>, but is associated with the virtual subscription area 1040a. Therefore, the local V2X server <NUM> transmits the V2X message to the RSU <NUM> that manages the virtual V2X device <NUM> (S1020). The RSU <NUM> converts the received V2X message into a format that the virtual V2X device <NUM> is able to receive, and transmits the converted message to the virtual V2X device <NUM> (S1030).

<FIG> shows an example for a V2X service at the boundary between a plurality of RSUs.

A local V2X server <NUM> manages a first RSU <NUM> and a second RSU <NUM>. The first RSU <NUM> sets the first RSU subscription area 1120a, and the second RSU <NUM> sets the second RSU subscription area 1130a. The first RSU subscription area 1120a and the second RSU subscription area 1130a are adjacent to each other, but do not overlap. A V2X device <NUM> is located in the first RSU subscription area 1120a of the first RSU <NUM>, and is moving toward a legacy V2X device <NUM>. The legacy V2X device <NUM> is located in the second RSU subscription area 1130a of the second RSU <NUM>, and is moving toward the V2X device <NUM>.

The V2X device <NUM> sends a V2X message to the local V2X server <NUM>. Despite the risk of collision between the V2X device <NUM> and the legacy V2X device <NUM>, the V2X message of the V2X device <NUM> is not delivered to the legacy V2X device <NUM>. This is because the V2X device <NUM> is not associated with the second RSU subscription area 1130a yet.

To solve this problem, the following scheme is proposed.

In the first scheme, a virtual subscription area 1150a may be set to the legacy V2X device <NUM>. The virtual subscription area 1150a may be set by the local V2X server <NUM> or the second RSU <NUM>. Since the V2X device <NUM> is associated with the virtual subscription area 1150a, the V2X message of the V2X device <NUM> can be delivered to the legacy V2X device <NUM> through the local V2X server <NUM> and the second RSU <NUM>.

In the second scheme, an overlapped area may be set between a plurality of adjacent RSU subscription areas (and/or a plurality of RSU management areas). The local V2X server <NUM> may set the overlapped area 1160a around the boundary between the first RSU subscription area 1120a and the second RSU subscription area 1130a. The overlapped area 1160a may include one or more tiles, but is not limited in size or shape. The local V2X server <NUM> may transmit a V2X message received from the V2X device <NUM> in the overlapped area 1160a to the second RSU <NUM> associated with the overlapped area 1160a. The second RSU <NUM> may transmit the V2X message to the legacy V2X device <NUM>.

<FIG> shows an example of overlapped virtual subscription area between a plurality of local V2X servers.

A first local V2X server <NUM> has a first management area 1220a, and a second local V2X server <NUM> has a second management area 1240a. A boundary area <NUM> is defined along a boundary between the two management areas 1220a and 1240a. The boundary area <NUM> includes a first boundary area 1250a belonging to the first management area 1220a of the first local V2X server <NUM> and a second boundary region 1250b belonging to the second management area 1240a of the second local V2X server <NUM>. Each of the first boundary area 1250a and the second boundary area 1250b includes tiles arranged in a line along the boundary, but this is only an example.

A legacy V2X device <NUM> is located in an RSU management area of an RSU <NUM>. The RSU <NUM> may set a virtual subscription area 1210a for the legacy V2X device <NUM>. When a part or all of the virtual subscription area 1210a overlaps with the boundary area <NUM>, it is proposed which local V2X server registers the virtual subscription area 1210a.

A part of the virtual subscription areas that do not overlap with the boundary area is registered in the corresponding local V2X server, and a remaining part is registered in all local V2X servers related to the boundary area. The virtual subscription area 1210a may include a first part 1210b that does not overlap with the boundary area <NUM> and a second part 1210c that overlaps with the boundary area <NUM>. The RSU <NUM> registers the first part 1210b to the first local V2X server <NUM>, and registers the second part 1210c to both the first local V2X server <NUM> and the second local V2X server <NUM>. When a V2X message is received from the V2X device associated with the first part 1210b or the second part 1210c, the first local V2X server <NUM> transmits the V2X message to the RSU <NUM>. When the second local V2X server <NUM> receives a V2X message from the V2X device associated with the second apart 1210c, the second local V2X server <NUM> transmits the V2X message to the RSU <NUM>.

<FIG> shows an example of overlapped RSU subscription area between a plurality of local V2X servers.

A first local V2X server <NUM> has a first management area 1320a, and a second local V2X server <NUM> has a second management area 1340a. A boundary area <NUM> is defined along the boundary between the two management areas 1320a and 1340a.

An RSU subscription area 1330a is configured for the RSU <NUM>. When some or all of the RSU subscription area 1330a overlaps with the boundary area <NUM>, it is proposed which local V2X server registers the RSU subscription area 1330a.

A part of an RSU subscription area that does not overlap with the boundary area is registered in the corresponding local V2X server, and a remaining part is registered in all local V2X servers related to the boundary area. The RSU subscription area 1330a include a first part 1330b belonging to the management area of the first local V2X server <NUM> that does not overlap with the boundary area <NUM>, a second part 1330c that overlaps with the boundary area <NUM>, and a third part 1330d belonging to the management area of the second local V2X server <NUM> that does not overlap with the boundary area <NUM>. The RSU <NUM> registers the first part 1330b to the first local V2X server <NUM>, registers the second part 1330c to both the first local V2X server <NUM> and the second local V2X server <NUM>, and registers the third part 1330d to the second local V2X server <NUM>. When the first local V2X server <NUM> receives a V2X message from the V2X device associated with the first part 1330b or the second part 1330c, the first local V2X server <NUM> transmits the received V2X message to the RSU <NUM>. When a V2X message is received from the V2X device associated with the second part 1330c or the third part 1330d, the second local V2X server <NUM> transmits the received V2X message to the RSU <NUM>.

<FIG> shows an example in which an RSU publishes a V2X message between a plurality of local V2X servers.

A first local V2X server <NUM> has a first management area 1420a, and a second local V2X server <NUM> has a second management area 1440a. A boundary area <NUM> is defined along the boundary between the two management areas 1420a and 1440a.

A first legacy V2X device <NUM> and a second legacy V2X device <NUM> are located within a management area of an RSU <NUM>. The RSU <NUM> belongs to the second management area 1440a. When the first legacy V2X device <NUM> belongs to the first management area 1420a and the second legacy V2X device <NUM> belongs to the boundary area <NUM>, it is proposed to which local V2X server the RSU <NUM> transmits V2X messages received from each legacy V2X device.

When the V2X message is received from the legacy V2X device, the RSU <NUM> calculates a publishing area (and/or virtual publishing area) based on the location of the legacy V2X device. The RSU <NUM> adds the publishing area to the V2X message, and transmits the added V2X message to the local V2X server. The RSU <NUM> may determine a local V2X server based on the publishing area (and/or virtual presentation area) of the legacy V2X device that has transmitted the V2X message.

Claim 1:
A road side unit, RSU, (<NUM>) for a vehicle-to-everything, V2X, service, the RSU (<NUM>) comprising:
a processor; and
a memory operatively coupled with the processor and configured to store instructions that, when executed by the processor, cause the RSU (<NUM>) to perform functions comprising:
setting a virtual subscription area (1040a) for a legacy V2X device (<NUM>) which supports communication with the RSU (<NUM>) with device-to-device direct communication protocol but does not support communication with a V2X server (<NUM>), wherein the virtual subscription area (1040a) assigned by the RSU (<NUM>) is registered to the V2X server (<NUM>) as a subscription area (1040a) of the legacy V2X device (<NUM>) and the V2X server (<NUM>) delivers to the RSU (<NUM>, <NUM>, <NUM>, <NUM>) any V2X message of a V2X device (<NUM>) which is connected to the V2X server (<NUM>) and is associated to the subscription area (1040a) of the legacy V2X device (<NUM>);
transmitting, to the V2X server (<NUM>), information on the virtual subscription area (1040a);
receiving, from the V2X server (<NUM>), a first V2X message for a first V2X device (<NUM>) associated with the virtual subscription area (1040a);
generating a second V2X message based on the first V2X message; and
transmitting, to the legacy V2X device (<NUM>), the second V2X message.