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.

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.

Prior art is found in "Intelligent Transport Systems; Framework for public mobile networks in cooperative ITS (C-ITS)", F-<NUM>.

The present disclosure provides relates to a method for vehicle-to-everything (V2X) and a device using the same.

According to a first aspect, we describe a server (<NUM>) for a vehicle-to-everything, V2X, service, the server (<NUM>) comprising: a processor (<NUM>); and a memory (<NUM>) operatively coupled with the processor (<NUM>) and configured to store instructions that, when executed by the processor (<NUM>), cause the server (<NUM>) to perform functions comprising: receiving (S810), from a first V2X device (<NUM>), a message for configuring a subscription area, wherein the server (<NUM>) delivers a V2X message of a V2X device associated with the subscription area of the first V2X device (<NUM>) to the first V2X device (<NUM>); receiving (S820), from a second V2X device, a V2X message, the V2X message including a V2X ID identifying the second V2X device and driving information of the second V2X device; determining (S830) that the second V2X device affects the first V2X device (<NUM>) based on the V2X message of the second V2X device if the second V2X device is not associated with the subscription area; and transmitting (S840), to the first V2X device (<NUM>), a reconfiguration message for requesting a reconfiguration of the subscription area of the first V2X device (<NUM>) when the second V2X device affects the first V2X device (<NUM>).

According to a second aspect, we describe a method for a vehicle-to-everything, V2X, service, the method performed by a server and comprising: receiving (S810), from a first V2X device, a message for configuring a subscription area, wherein the server delivers a V2X message of a V2X device associated with the subscription area of the first V2X device to the first V2X device; receiving (S820), from a second V2X device, a V2X message, the V2X message including a V2X ID identifying the second V2X device and driving information of the second V2X device; determining (S830) that the second V2X device affects the first V2X device based on the V2X message of the second V2X device if the second V2X device is not associated with the subscription area; and transmitting (S840), to the first device, a reconfiguration message for requesting a reconfiguration of the subscription area of the first V2X device when the second V2X device affects the first V2X device.

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 it 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.

<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 device 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" with 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 the subscription area of the subscriber device. (ii) some or all of the subscription area of the provider device overlaps with 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 according to an embodiment of the present specification.

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.

Now, how to modify a subscription area will be described.

As described above, in order for a V2X device to receive a V2X message from a V2X server, a subscription area is configured and registered with the V2X server. The V2X device can configure the size and/or shape of the subscription area based on its own driving information (e.g., speed/location/heading, etc.). For example, when driving or moving at high speed, the V2X device can configure a wider or larger subscription area, than compared to low-speed driving.

Outside the subscription area, a neighbor V2X device can come closer to a V2X device at high speed. Before the neighbor V2X device enters the subscription area, the V2X device cannot receive the message of the surrounding V2X device, there may be a delay in awareness and the V2X may be unprepared for the upcoming risk.

<FIG> shows an example of a scenario due to a neighbor V2X device.

A first V2X device <NUM> sets a subscription area 510a and is running at a relatively low speed. A second V2X device <NUM> is running toward the first V2X device <NUM> at high speed. The V2X server is receiving V2X messages from each of the first V2X device <NUM> and the second V2X device <NUM>. Although not shown in the drawing, the second V2X device <NUM> may also configure a subscription area.

At time T, the second V2X device <NUM> is far away from the first V2X device <NUM> and is not located within the subscription area 510a. Therefore, the V2X server does not deliver the V2X message of the second V2X device <NUM> to the first V2X device <NUM>.

At time T+t, the second V2X device <NUM> is now adjacent to the subscription area 510a, but the V2X server still does not deliver the V2X message of the second V2X device <NUM> to the first V2X device <NUM>.

The first V2X device <NUM> may not set the subscription area 510a large enough as the first V2X device <NUM> travels at a low speed. Therefore, the first V2X device <NUM> may not know the existence of the second V2X device <NUM> approaching at high speed, and it may be difficult for the first V2X device <NUM> to prepare for the upcoming risk of a fast approaching vehicle in advance.

<FIG> shows an example of reconfiguring a subscription area.

The V2X server may know the speed/direction of the first V2X device <NUM> and the speed/direction of the second V2X device <NUM> through the received V2X messages. Accordingly, if the V2X server determines that the possibility of collision between the first V2X device <NUM> and the second V2X device <NUM> is high enough, the V2X server may request the first V2X device <NUM> to configure an additional subscription area 510b.

The V2X server can know the driving information (e.g., speed/direction, etc.) of each V2X device based on the received V2X messages. Based on the driving information, the V2X server can determine the estimated risk area of each V2X device. The V2X server selects a V2X device whose subscription area does not overlap with the estimated risk area among V2X devices within the estimated risk area. The V2X server may request the selected V2X device to add/modify its subscription area. The V2X server may deliver the V2X message of the V2X device related to the estimated risk area to the selected V2X device. The selected V2X device can add/modify its subscription area according to the request of the V2X server. The selected V2X device may determine whether to add/modify the subscription area according to whether the dangerous situation satisfies a specific condition.

<FIG> shows an example of the system architecture of the V2X device and the V2X server. Each module may be implemented in software, stored in a memory, and executed by a processor. Not all modules are required. Some modules may be omitted or modified, and more modules may be added. The name of each module is merely an example, not a limitation.

A V2X device <NUM> includes a user interface (UI) module <NUM>, an application module <NUM>, a message layer module <NUM>, a client module <NUM>, and a network stack module <NUM>.

The UI module <NUM> may provide the user with a status of the V2X service, a warning, and the like, and receive a user input. The application module <NUM> may perform risk assessment and the like using the received message. The message layer module <NUM> handles the sending/receiving of messages.

The client module <NUM> performs a client function to support the V2X service. The client module <NUM> includes an information collector <NUM>, an area calculator <NUM>, and a Message Queuing Telemetry Transport (MQTT) client protocol <NUM>. The information collector <NUM> collects the location, sensor, and/or external information of the V2X device <NUM>. The area calculator <NUM> determines the subscription area. The area calculator <NUM> may determine whether to modify/add the subscription area according to the request of the V2X server. The area calculator <NUM> may determine whether to modify/add the subscription area according to the state/risk level of the V2X device <NUM>. The MQTT client protocol <NUM> implements the MQTT client protocol.

A V2X server <NUM> includes a server module <NUM> and a network stack module <NUM>. The server module <NUM> performs a server function to support the V2X function. The server module <NUM> includes a client manager <NUM>, a message queue <NUM>, and an MQTT server protocol <NUM>. The client manager <NUM> manages a client connected to the V2X server <NUM>. The message queue <NUM> includes a queue for storing messages to be relayed to clients, and manages messages. The MQTT server protocol <NUM> implements the MQTT server protocol.

The network stack modules <NUM> and <NUM> implement IP network interfaces such as transmission control protocol/internet protocol (TCP/IP), user datagram protocol/internet protocol (UDP/IP), etc..

MQTT is used as a message protocol, but this is only an example. Advanced Message Queuing Protocol (AMQP), HyperText Transfer Protocol (HTTP), and/or vendor specific protocols may be used.

<FIG> is a flowchart illustrating a method for a V2X service according to another embodiment of the present specification.

In step S810, a first V2X device sets a subscription area, and transmits a message having information about the subscription area to a V2X server. The subscription area may be set separately or together with the subscription request. The first V2X device may be called a subscriber device.

In step S820, a second V2X device transmits a V2X message to the V2X server. The V2X message may be arbitrarily or periodically transmitted regardless of the subscription request of the first V2X device. The V2X message may include at least one information element shown in Table <NUM>, but there is no limitation. The V2X message may include a device ID of the second V2X device and driving information of the second V2X device. The driving information includes the location, velocity, and direction of the second V2X device. The second V2X device may transmit the V2X message according to a specific condition.

Condition (<NUM>): When driving at a speed above a certain value for a specific time, the second V2X device may transmit a V2X message. Condition (<NUM>): When a sudden change in speed is detected for a specific time, the second V2X device may transmit a V2X message. Condition (<NUM>): When a sudden change in the heading direction is detected for a specific time, the second V2X device may transmit a V2X message.

One or more of the above conditions (<NUM>) to (<NUM>) may be used. One or more of the above conditions (<NUM>) to (<NUM>) may be combined. For example, it is defined as D=w1*V+w2*A+w3*D. V is the speed of the second V2X device, A is the speed change (acceleration) of the second V2X device, D is the direction change of the second V2X device, and w1, w2, and w3 are weights. If D is greater than a specific value, the second V2X device may transmit a V2X message.

In step S830, if the second V2X device is not associated with the subscription area, the V2X server determines whether the second V2X device will affect the first V2X device based on the collected V2X message, and determines whether the subscription area is needed to be reconfigured or not.

When the second V2X device is associated with the subscription area, the V2X server forwards the V2X message to the first V2X device. That the second V2X device is associated with the subscription area means that (i) the second V2X device is located in the subscription area, (ii) the publishing area of the second V2X device overlaps with the subscription area, or (iii) the subscription area of the second V2X device overlaps with the subscription area.

If the second V2X device is not associated with the subscription area, the V2X server may determine whether to reconfigure the subscription area of the first V2X device according to the degree of risk that the second V2X device affects the first V2X device. The server determines the estimated risk area of the second V2X device based on the V2X message. When the estimated risk area partially or completely overlaps the subscription area, it may be determined that the second V2X device affects the first V2X device.

The estimated risk area may be determined based on driving information of the second V2X device. The estimated risk area may include at least one or more tiles on an expected path on which the second V2X device drives.

<FIG> shows an example of calculating an estimated risk area.

A first V2X device <NUM> configures a subscription area 910a. At time "T", a second V2X device <NUM> travels toward the first V2X device <NUM> at a higher speed than the first V2X device <NUM>. At time T + t, a V2X server can calculate the estimated positions of the first V2X device <NUM> and the second V2X device <NUM> based on the speed/direction of the first V2X device <NUM> and the second V2X device <NUM>. The value of "t" may be determined by the V2X server in consideration of driving information of V2X devices. In addition, the V2X server may calculate the estimated risk area 920a in consideration of the moving direction and speed of the second V2X device <NUM> at time T+t. For example, the V2X server may determine the estimated risk area 920a having one or more tiles in consideration of the distance and the driving route reached by the second V2X device <NUM> at time T+t+k.

When a part or all of the estimated risk area 920a overlaps with the subscription area 910a, the V2X server may determine that the second V2X device <NUM> affects the risk of the first V2X device <NUM>.

Referring back to <FIG>, in step S840, if it is determined that the subscription area needs to be reconfigured, the V2X server transmits a reconfiguration message for requesting the reconfiguration of the subscription area to the first V2X device. If it is determined that the second V2X device affects the first V2X device, the V2X server may transmit the reconfiguration message for requesting reconfiguration of the subscription area to the first V2X device.

The reconfiguration message may include information on a subscription area recommended to be reconfigured by the first V2X device. The reconfiguration message may include information on an additional area recommended to be added in the subscription area.

The reconfiguration message may include the driving information of the second V2X device. The reconfiguration message may include driving information of one or more V2X devices having one or more estimated risk areas overlapping the subscription area.

In step S850, the first V2X device may determine whether to reconfigure the subscription area based on the reconfiguration message. Reconfiguration of the subscription area may mean addition and/or modification of the subscription area. When the subscription area is reconfigured, the first V2X device may notify the reconfigured subscription area to the V2X server.

When the first V2X device receives information about the modified/added subscription area from the V2X server, the first V2X device can reconfigure the subscription area without further decision.

The first V2X device may determine whether to reconfigure the subscription area based on its own driving information and the driving information of the second V2X device. The first V2X device may predict the estimated location of the second V2X device for a specific time, and check whether the estimated location is included in the subscription area. If the estimated location is included in the subscription area, the subscription area may be reconfigured.

Claim 1:
A server (<NUM>) for a vehicle-to-everything, V2X, service, the server (<NUM>) comprising:
a processor (<NUM>); and
a memory (<NUM>) operatively coupled with the processor (<NUM>) and configured to store instructions that, when executed by the processor (<NUM>), cause the server (<NUM>) to perform functions comprising:
receiving (S810), from a first V2X device (<NUM>), a message for configuring a subscription area, wherein the server (<NUM>) delivers a V2X message of a V2X device associated with the subscription area of the first V2X device (<NUM>) to the first V2X device (<NUM>);
receiving (S820), from a second V2X device, a V2X message, the V2X message including a V2X ID identifying the second V2X device and driving information of the second V2X device;
determining (S830) that the second V2X device affects the first V2X device (<NUM>) based on the V2X message of the second V2X device if the second V2X device is not associated with the subscription area; and
transmitting (S840), to the first V2X device (<NUM>), a reconfiguration message for requesting a reconfiguration of the subscription area of the first V2X device (<NUM>) when the second V2X device affects the first V2X device (<NUM>).