EP3729405A1

EP3729405A1 - Method for determining a communications scenario and associated terminal

Info

Publication number: EP3729405A1
Application number: EP18833273.8A
Authority: EP
Inventors: Ghislain Moncomble
Original assignee: Orange SA
Current assignee: Orange SA
Priority date: 2017-12-22
Filing date: 2018-12-07
Publication date: 2020-10-28
Also published as: US11710405B2; FR3076046A1; WO2019122579A1; US20200342759A1

Abstract

The invention concerns a method for determining a communications scenario corresponding to an action for producing, by a first movable element situated in a traffic lane, a response to an event, characterised in that it comprises the following steps: · determining (E320) an event in a vicinity of the first movable element, depending on at least one neighbouring element from a list of neighbouring elements positioned in said vicinity, · determining (E330) a series of actions able to be performed in response to said event, by consulting a lookup table between at least one event and at least one series of actions, · for at least one action of said series of actions, determining (E340) a communications scenario associated with said action, the step (E340) of determining a scenario comprising a sub-step (E342) of selecting, in said list of elements, for at least one communications scenario message, at least one neighbouring element receiving said message.

Description

Method for determining a communications scenario and associated terminal

Background of the invention

The present invention relates to the field of autonomous vehicles and assistance in driving a vehicle or the movement of a living being, and more particularly relates to a technique for determining a communications scenario corresponding to an action that can be performed by a movable element, such as a vehicle or a living being.

As is known, certain motor vehicles are equipped with systems making it possible to assist the drivers of these vehicles when they drive these vehicles, or to replace the drivers.

A vehicle equipped with such a system is able to determine an event on the taxiway, for example by analyzing images obtained by a camera positioned on the vehicle, and to determine and perform an action in response to the detected event. .

The determination of the action to be performed is thus performed at the level of the vehicle, from data obtained by means specific to the vehicle, including information on the traffic lane, as well as indications on the presence and possibly the behavior of the vehicle. other vehicles on the taxiway.

In addition, the vehicle may possibly transmit information to another nearby vehicle.

In order to determine the identifier of this other vehicle to send a message including this information, the vehicle analyzes an image obtained by the camera to determine the license plate number of the other vehicle, then sends the plate number registration to a remote server. The remote server can then consult a database using the license plate number to determine the identifier of the other vehicle.

However, it is not always possible for the vehicle to determine the license plate number, for example when the weather conditions are bad, when the ambient light is low or when the distance between the two vehicles is large. The other vehicle may also not be visible from the vehicle, for example because it is hidden by an element of the environment such as an obstacle, a hedge or a wall.

In addition, this determination technique is not easy to implement in countries where license plates are not standardized, such as the United States. United States, where fonts vary by state and where the front and back plates may be different and include custom inscriptions.

The vehicle can further send geolocated information to a remote server which then stores this information. Other vehicles can then consult the server to retrieve information. This indirect communication technique is for example useful for signaling an obstacle.

However, this indirect communication technique consumes a lot of energy and clogs the telecommunications networks concerned, because all vehicles must consult the remote server periodically, without knowing if this is necessary.

The response time of the remote server is thus quite important, which implies that this indirect communication technique is not suitable for situations requiring a rapid reaction and not affecting all the vehicles traveling on the channel concerned (for example a situation or a vehicle passes another vehicle or an arrival situation of two vehicles at an intersection), which poses a safety problem for the users of the vehicles.

Obiet and summary of the invention

The present invention relates to a method for determining a communications scenario corresponding to at least one action that can be performed by a first mobile element located at a traffic lane, in response to at least one event, implemented by a first terminal associated with the first mobile element, characterized in that it comprises the following steps:

Determining at least one event in a neighborhood of the first mobile element, as a function of at least one neighboring element of a list of neighboring elements positioned in said neighborhood, said list of neighboring elements comprising at least one neighboring element ,

• determination of at least one series of actions, which can be carried out in response to at least one event, by consulting a correspondence table between at least one event and at least one series of actions, said series of actions determined comprising at least one action,

For at least one action of said at least one series of actions, determining a communications scenario associated with said at least one action, said scenario comprising at least one message,

the step of determining a communications scenario comprising a sub-step of selecting, in said list, for at least one message of the communications scenario, at least one neighbor element recipient of said message. Thus, the first movable element can directly and certainly prevent the neighboring elements concerned by the action that should be performed in response to the event, the neighboring elements concerned by the action being the elements on which the action could have an impact if it were performed, or those that because of their response could prevent the triggering of said action.

This direct communication makes it possible to preserve the network resources and to quickly prevent the neighboring elements concerned by the action that can be performed. The comfort and safety of the users are thus improved.

In a particular embodiment, the determination step comprises, for the said at least one action of the said at least one series of actions, the determination of a starting instant for carrying out the action and a duration of performing the action, so that said at least one neighboring element recipient of said message is selected according to said start time of completion of the action and said duration of completion of the action.

In a particular embodiment, the correspondence table comprises at least two events, each event being associated with a series of actions that can be performed.

In a particular embodiment, the step of determining a communications scenario comprises obtaining a MSISDN number of a terminal associated with said at least one neighbor element to which the message is addressed.

In a particular embodiment, at least one neighboring element of said list of neighboring elements is determined according to:

• a geolocation position, and / or

• a speed, and / or

• a direction of travel, and / or

• a direction of movement,

of the first mobile element and the neighboring element, at a first instant corresponding to the implementation of the determination of the list of neighboring elements, and at least a second instant corresponding to the first instant to which is added a predicted duration of completion of one or more shares of the series of shares.

In a particular embodiment, the step of determining said at least one event comprises a substep of confirming the geolocation position of the at least one neighboring element of the list of neighboring elements, by means of a measurement. performed by the first terminal.

The confirmation sub-step may allow updating of the geolocation position of the at least one neighboring element, which allows a more precise determination of the event and thus improves the security of the users. In a particular embodiment, a content of the at least one message of the scenario is standardized and comprises at least one of the following information list:

• the scenario,

• the action corresponding to the message,

A contextual data element of the first mobile element depending on said at least one action corresponding to the message,

• a message number in the scenario,

An identifier of the first terminal,

A temporal indication concerning said at least one action corresponding to the message,

• a time indication of at least one other share in the series of shares

BAG,

• an indication of what to do with the message,

• a list of possible answers including at least one answer.

The invention further relates to a communication method comprising the determination method described above, comprising a step of sending, by the first terminal and via a telecommunication network, the at least one message of the scenario to the Neighboring recipient element.

In a particular embodiment, the sending is performed according to a SCR protocol, and said at least one message is a SIP-options message.

The invention further relates to a terminal adapted to implement a determination method as described above.

In a particular embodiment, the various steps of the determination method and / or the communication method according to the invention are determined by instructions of computer programs.

Accordingly, the invention also relates to a computer program, on an information medium, this program comprising instructions adapted to the implementation of the steps of a determination method and / or a communication method according to the invention.

This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other form desirable shape.

The invention also relates to a computer-readable information medium, comprising instructions of a computer program as mentioned above.

The information carrier may be any entity or device capable of storing the program. For example, the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording means, for example a hard disk.

On the other hand, the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention can be downloaded in particular on an Internet type network.

Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.

Brief description of the drawings

Other features and advantages of the present invention will emerge from the description given below, with reference to the accompanying drawings which illustrate an embodiment having no limiting character. In the figures:

FIG. 1 schematically represents a system able to implement a method for determining a communications scenario according to an exemplary embodiment of the invention;

- Figure 2 shows schematically a first terminal of the system of Figure 1;

FIGS. 3 and 4 represent, in the form of flowcharts, the main steps of methods for determining a communications scenario, according to exemplary embodiments of the invention;

FIG. 5 represents a first mobile element associated with a first terminal of a system able to implement a method according to an exemplary embodiment of the invention;

FIG. 6 represents, in flowchart form, the main steps of a communication method, according to an exemplary embodiment of the invention.

Detailed description of embodiments

FIG. 1 schematically represents a system 100 able to implement a method for determining a communications scenario according to an exemplary embodiment of the invention.

The system 100 includes a first terminal 110 and a main remote server 120. The system may further include a second terminal 130. In addition, the system may include a plurality of secondary remote servers 140, each secondary remote server 140 being associated with a predetermined geographical area 150.

The geographical zone 150 corresponds in one example to a predetermined portion of taxiway VC, or a geographical area of several kilometers in diameter, typically 20 kilometers. As can be seen in FIG. 1, two adjacent geographical zones 150 can overlap.

The first terminal 110, the main remote server 120 and possibly the second terminal 130 and / or the secondary remote servers 140 may be connected to a telecommunications network 160 in order to communicate with each other. No limitation is attached to the nature of the telecommunications network. It can be for example an Internet network (for example Wifi), or a mobile network (3G, 4G etc.).

The first terminal 110 may be a mobile terminal such as a mobile phone, for example of the "smartphone" type, a digital tablet, or a personal computer.

The first terminal 110 is associated with a first mobile element 170, the first mobile element 170 being typically a vehicle or a living being.

The first movable member 170 is for example located at a traffic lane VC. The first movable member 170 for example circulates on the driving lane or beside it (typically when the first movable element is a living being).

The first terminal 110 can thus be positioned at a first vehicle 170, typically inside the first vehicle 170, or incorporated in the first vehicle 170.

Alternatively, the first terminal 110 may be carried by a living being, such as a human being or an animal, typically a dog.

The second terminal 130 may be a mobile terminal such as a mobile phone, for example of the "smartphone" type, a digital tablet, or a personal computer.

In addition, the second terminal 130 is associated with a second element 180, this second element 180 typically being a moving element such as a vehicle or a living being, or a fixed element, such as a display panel.

The second element 180 is for example located at a traffic lane VC. When the second element 180 is movable, it circulates for example on the traffic lane or beside it (typically when the first movable element is a living being). When the second member 180 is stationary, it can be positioned at the taxiway VC, typically sideways or upwards.

The second terminal 130 can thus be positioned at a second vehicle 180, typically inside the second vehicle 180, or incorporated in the second vehicle 180. Alternatively, the second terminal 130 may be carried by a living being, such as a human being or an animal, typically a dog.

The first vehicle 170 and / or the second vehicle 180 may be a self-driving vehicle, and may take the form of a motorized vehicle such as a motor car, a truck, a bus or a two-wheeled vehicle, a bicycle, a train, a tram or even a boat.

The system 100 may further comprise one or more other terminals, each terminal being associated with a mobile element such as a vehicle or a living being, or a fixed element, such as a billboard positioned at the level of the track. VC circulation.

In addition, the system 100 may include one or more other remote servers, for example dedicated to long-term storage.

As shown in FIG. 2, the first terminal 110 presents the conventional architecture of a computer. The first terminal 110 comprises in particular a processor 200, a read-only memory 202 (of the "ROM" type), a non-volatile rewritable memory 204 (of the "EEPROM" or "Flash NAND" type for example), a rewritable volatile memory 206 (of type "RAM"), and a communication interface 208.

The read-only memory 202 of the first terminal 110 constitutes a recording medium in accordance with an exemplary embodiment of the invention, readable by the processor 200 and on which is recorded a computer program PI conforming to an exemplary mode of operation. embodiment of the invention. In a variant, the computer program PI is stored in the rewritable non-volatile memory 204.

The computer program may allow the first terminal 110 to implement the notification or communication method according to an exemplary embodiment of the invention.

In addition, the first terminal 110 may comprise an onboard camera, a radar, a microphone, a laser scanner and / or GPS or Galileo guidance means.

As a variant, the first mobile element 170 may comprise an on-board camera, a radar, a microphone and / or a GPS or Galileo guidance means to which the first terminal 110 can access.

The onboard camera is then positioned on the windshield and / or the rear window of the first movable member 170.

The main remote server 120, the second terminal 130 and / or each secondary remote server 140 may also present the conventional architecture of a computer, and may each then comprise in particular a processor, a ROM (ROM type), a non-volatile memory rewritable (type "EEPROM" or "Flash NAND" for example), a volatile memory rewritable (type "RAM"), and a communication interface. Each read-only memory may constitute a recording medium according to an exemplary embodiment of the invention, readable by the associated processor and on which is recorded a computer program according to an exemplary embodiment of the invention. . Alternatively, the computer program is stored in the associated non-volatile rewritable memory. The computer program may allow the implementation of at least a part of the notification or communication method according to an exemplary embodiment of the invention.

FIG. 3 represents a method 300 for determining a communications scenario corresponding to at least one action that can be performed by a first mobile element 170 located at a VC taxiway, in response to at least one event.

The method may be implemented by a first terminal associated with the first mobile element 170, such as the first terminal 110 described with reference to FIGS. 1 and 2.

In a step E320, at least one event EV in a neighborhood of the first movable element 170 is determined, as a function of at least one neighboring element of a list of neighboring elements positioned in this neighborhood, the list of neighboring elements comprising at least one neighboring element.

In a step E330, at least one series of SAC actions that can be performed in response to said at least one EV event is determined, by consulting a correspondence table between at least one event and at least one series of actions, the determined SAC share series comprising at least one share.

In a step E340, for at least one action of said at least one series of SAC actions, a communication SC scenario associated with said at least one action is determined, the scenario comprising at least one message.

The determination step E340 of a communications scenario SC comprises a substep E342 for selecting, from the list, for at least one message of the communications scenario, at least one neighboring destination element ED of said message.

FIG. 4 represents a method 400 for determining a communications scenario corresponding to at least one action that can be performed by a first mobile element 170 located at a traffic lane VC, in response to an event, according to another exemplary embodiment of the invention.

The method is implemented by a system such as the system 100 of FIG.

In a step E401, the first terminal 110 obtains a DID identification data or DC characterization of the first mobile element 170.

The identification data that can be obtained is typically the MSISDN number (acronym for "Mobile Integrated Services Digital Network Station") of the first terminal 110 associated with the first mobile element 170. In a variant, the identification data may be the license plate number of the first mobile element 170.

In addition, the characterization data that can be obtained can indicate the general category to which the first element 170 belongs, that is to say whether the first element 170 is fixed or mobile, or more precisely if the first element 170 is a car, a truck, a bus, a two-wheeler, a bicycle, a train, a tram, a boat, a human being, an animal, or a billboard.

As a variant, the characterization data item that can be obtained can indicate a subcategory of the general category to which the first item 170 belongs. For example, if the first element 170 is a vehicle, this data relates to the type of vehicle, the vehicle mark, the model of the vehicle, the color of the vehicle.

As a variant, the characterization data item that can be obtained indicates the weight of the first mobile element 170, the maximum speed of the first mobile element 170, the action capacities of the first mobile element 170, the degree of autonomy of the first mobile element 170, an apparatus link between the first terminal 110 and the first mobile element 170, or the priority of the first mobile element 170, typically in a country and / or with respect to a given event.

As a variant, the characterization data item that can be obtained can relate to the communication capabilities of the first element 170.

"Action capabilities" include, for example, the ability to change direction, or the ability to accelerate or decelerate. For example, a train or tram does not have the ability to overtake an element positioned on its taxiway, or does not have the ability to leave the tracks of its taxiway.

The capability of action may be a function of various parameters, such as the speed and / or weight of the movable member, the length, width and / or curvature of the taxiway available to perform the action, and possibly the speed and / or the weight of other moving parts traveling on the same lane.

In addition, "autonomy" here refers to the ability of the mobile element to follow and / or respond to a suggestion regarding the action to be taken in response to an event. For example, a fully autonomous vehicle can automatically take into account the suggestion and thus carry out the suggested action, a vehicle having a driving assistance may require an acquittal on the part of the driver so that the element having issued the suggestion know that this suggestion is taken into account, and a vehicle that does not have driver assistance does not respond to suggestions. In addition, an animal such as a dog does not respond to suggestions and may not perform the suggested action.

"Priority" indicates whether the moving element has priority when managing a given event. The priority may depend on the country where the event occurs. An example priority vehicles of general interest, typically ambulances, which have priority in France during their interventions.

"Communication capabilities" refer, for example, to the ability of the element to send a message via the telecommunications network 160 or to display the message.

A display module such as a screen, can indeed be positioned at the rear of a truck so as to be visible by other elements positioned at the rear of the truck. Similarly, a display panel may include a display module such as a screen. Such display modules can thus transmit messages to other elements, which is particularly useful when these elements are not able to receive the message via the telecommunications network 160 and / or to analyze it.

In a step E402, the first terminal 110 sends to the main remote server 120, via the telecommunications network 160, the identification data DID or DC characterization obtained in step E401.

In one example, the first terminal 110 implements the step E402 during an enrollment of the first terminal 110 to an application implementing the method or during registration of the first mobile element 170.

In another example, the first terminal 110 implements the step E402 during an assembly of the first terminal 110 to the first mobile element 170, or during a start of travel on the taxiway VC.

The first terminal 110 can then retain all or part of the data, and send it to the main remote server 120 after having been authenticated with the main remote server 120, which makes it possible to preserve the anonymity of the data when the method is not put in place. implemented. Alternatively, in order to avoid too much data transfer volume, the first terminal 110 can send a link to a storage space of another remote server, typically after authentication of the first terminal 110 with the main remote server 120 and possibly from the other remote server.

Step E401 and optionally step E402 may be repeated one or more times by the first terminal 110 in order to obtain and send one or more additional identification data DID and / or DC characterization data of the first mobile element 170. (Multiple data can be sent at the same time to step E402).

Steps E401 and E402 can also be repeated to update one or more data.

Indeed, certain data such as the weight of the first element, the fitting link or the priority of the first element 170 may vary over time.

For example, the weight of a vehicle varies according to the loading of that vehicle. In addition, a vehicle may be a priority during an intervention and not a priority outside these interventions. In addition, the switchgear link between the first terminal 110 and the first element 170 can be effective when moving the first member 170 and be canceled when the first member 170 is not moving.

The steps E401 and E402 may also be implemented one or more times by one or more terminals associated with elements relating to the taxiway VC other than the first mobile element 170. The data obtained are then relative to the element associated with the terminal implementing these steps.

The steps E401 and E402 can thus be implemented one or more times by the second terminal 130 associated with the second mobile element 180.

After receiving a data item (step F402), the main remote server 120 stores the data in order to store it (step F406), typically in a secure manner, after having optionally certified it (step F404).

The data received at this step F402 may be stable, that is, not vary in time. The duration of storage of the data can thus be important.

The identification data DID or DC characterization for the same element are stored in association by the main remote server 120. In one example, each data sent to step E402 by the same terminal associated with an element is accompanied by a same identification data, the identification data enabling the main remote server 120 to link the data concerning the same element.

The main remote server 120 may further receive, certify and / or store environmental data, such as:

• data relating to the weather conditions of one or more geolocalised zones 150 traversed by the taxiway VC (typically the temperature and the rainfall which influence the braking distances), and / or

• forecast or observed traffic data on taxiway VC, and / or

• technical and / or statistical data on geolocated portions of the taxiway VC (type of lane, predefined traffic rules, traffic statistics, etc.).

The type of track is, for example, a track comprising several sub-tracks on which the elements are traveling in the same direction, a track comprising two sub-tracks on which the elements are traveling in opposite directions, a track leading to an intersection with another track, a track parking, parking place, etc.

The predefined traffic rules include the usual rules of the highway code and / or predefined rules relating to the VC channel on which the first mobile element 170 (for example the maximum authorized speed) circulates.

In addition, the main remote server 120 may receive, certify and / or store one or more data relating to a particular use of a mobile element, typically the first mobile element 170 and / or the second mobile element. The "particular use of the mobile element" refers, for example, to the behavior of the element with respect to the road code (observed habits of speed, safety distance, etc.), or the behavior of the element by relative to a suggestion of behavior (for example if the moving element has the habit of slowing down when it receives a suggestion of braking). Data on the particular use of the mobile element is thus useful for evaluating safety distances.

The "particular use of the mobile element" may also designate one or more usual paths of the mobile element, typically the path from the place of residence to the workplace of the element or the user. This type of data can make it possible to automatically recognize a path in progress made subsequently, even for a mobile element that does not include a terminal according to the invention.

Each usual trip can be determined based on trip history, which can be provided by telecom operators.

In a step E408, the first terminal 110 obtains a contextual DCO data from the first mobile element 170.

The contextual DCO data obtained can be:

A position of geolocation of the first mobile element 170,

A predictive trajectory of the first mobile element 170,

A predicted path of the first mobile element 170, the path comprising a succession of predicted trajectories,

The speed of the first movable element 170,

A speed evolution of the first mobile element 170,

A data item concerning the level of attention of the user of the first mobile element 170 or of the first mobile element 170 itself when the element is a living being, this datum being determined by detecting whether the user or the element is performing an action, such as speaking, listening to music or reading a message).

The first terminal 110 can obtain the geolocation position, the trajectory and / or the path by accessing the GPS or Galileo guidance means of the first terminal 110 or the first mobile element 170.

In addition, the first terminal 110 can obtain the speed and / or the evolution of the speed as a function of successive GPS coordinates first mobile element 170, obtained by accessing the GPS or Galileo guidance means of the first terminal 110 or the first mobile element 170. The first terminal 110 can also obtain the speed and / or the speed evolution by accessing speed data of the speed counter of the first movable member 170.

In addition, the first terminal 110 can obtain the level of attention data by accessing the microphone of the first terminal 110 or the first movable element. 170 and analyzing the data from the microphone, or determining if a call is in progress.

The first terminal 110 can also obtain the data concerning the level of attention by accessing a sensor positioned on the user's seat, or a camera able to obtain images from the user (the terminal can then detect a lower attention of the user by monitoring the evolution of the user's face, especially at the level of the eye sphere).

In a step E410, the first terminal 110 sends the main remote server 120, via the telecommunications network 160, the contextual data DCO, as well as an identification data DID of the first mobile element 170.

Sending can be done in real time, after obtaining the contextual data made in step E408.

After receiving the contextual data (step F410), the remote server 120 or the secondary remote server or 140s record the data in order to store it (step F414), typically in a secure manner, possibly after having certified it (step F412) .

More specifically, the contextual data item COD is stored in association with the identification data item (s) DID and / or characterization item DC relating to the first item 170. The identification item DID of the first item 170 sent to step E410 allows the main remote server 260 to make the link between the received DCO contextual data and the DID identification and / or characterization data concerning the first mobile element 170, previously recorded by the main remote server 120.

As a variant, the contextual data item COD and the identification datum DID of the first mobile element 170 are sent to the secondary remote server 140 corresponding to the geographical area 150 in which the first mobile element 170 is positioned.

The secondary remote server 140 then stores the contextual data DCO in association with the identification data DID (step F414), typically in a secure manner, possibly after certifying the contextual data DCO (step F412).

The secondary remote server 140 can then consult the main remote server 120 by sending the identification data DID in order to retrieve and then store in association with the contextual data DCO, one or more identification data DID and / or DC characterization concerning the first movable member 170.

The storage duration of the data may be limited, typically a few minutes after the first mobile element 170 has left the geographical zone 150. Thus, the secondary remote server 140 associated with the geographical zone in which the first mobile element 170 is positioned. can store at a given moment, the geolocation position of the element at the given instant, one or more geolocation positions of the element to one or more instants preceding the given moment, and forecast trajectories at one or more moments following the given moment.

As a variant, the storage duration of the data may be greater than a few minutes, so that the secondary remote server 140 can provide this data for legal purposes (in order, for example, to determine liability in the event of an accident), or again so that the secondary remote server 140 can provide a path history, for example to the main remote server 120, so that the main remote server 120 can determine a particular usage datum of the element, or predicted traffic data. .

The contextual data can also be sent to a remote server dedicated to long-term storage, so that this data can be used for the aforementioned purposes.

When the first mobile element 170 is overlapping two adjacent zones 150, the first mobile element 170 sends the contextual data to the two secondary remote servers 140 corresponding to the two adjacent zones 150.

The division of the geographical areas 150 between several secondary remote servers 140 makes it possible to reduce the processing time of the data at the level of each server.

In addition, when the predicted path of the first mobile element 170 is known, the secondary remote server 140 corresponding to the geographical zone 150 in which the first mobile element 170 is positioned can send the contextual data to the secondary remote server 140 corresponding to the next zone. geographical 150 which passes the estimated path, so as to limit the polling time of the latter secondary server 140 when passing from one zone to another.

Step E408 and possibly step E410 can be repeated one or more times by the first terminal 110 in order to obtain and send one or more additional contextual data of the first mobile element 170 (several contextual data can be sent at the same time). time at step E410).

The steps E408 and E410 may also be implemented one or more times by one or more terminals associated with elements relating to the taxiway VC other than the first mobile element 170. The data obtained are then relative to the element associated with the terminal implementing these steps.

The steps E408 and E410 can thus be implemented one or more times by the second terminal 130 associated with the second mobile element 180.

The reiteration of the steps E408 and E410 can be performed when the forecast trajectory, the estimated path, the speed, the speed evolution and / or the level of attention is modified. The repetition of steps E408 and E410 can be periodic. The reiteration period may be of the order of one second, which allows an almost real-time updating of the contextual data concerning the first mobile element 170.

The reiteration period may be higher so as not to saturate the telecommunication network 160, for example when the first mobile element 170 follows a predictive path at a stable speed.

The reiteration period may furthermore be adapted as a function of the observed traffic density, the speed of the first mobile element 170, or as a function of the level of attention of the user of the first mobile element 170.

In a step E420, an EV event in a neighborhood of the first movable member 170 is set is determined.

The step E420 can be implemented at the same time as the steps E408 and E410, for example when the event EV detected corresponds to the departure of a path of the first mobile element 170. In addition, the step E420 can be set implemented by the first terminal 110.

As described in more detail below, the neighborhood of the first element may correspond to a geographical area of neighborhood around the first movable element 170. The event can thus occur at the VC circulation path of the first movable element 170, or at another traffic lane located near the taxiway of the first movable member 170, for example crossing the taxiway VC of the first movable member 170 at an intersection.

The step E420 may comprise a substep E422 for determining a series of data SDEV corresponding to the event EV, the data set comprising at least one datum, typically several data.

Each data in the SDEV data series can be:

A characterization data DC of the first mobile element 170 as obtained in step E401,

A contextual DCO data element of the first mobile element 170 as obtained in step E408, and / or

An environmental data item as received in step F402.

In one example, the SDEV dataset includes:

A type of taxiway VC at which the first movable element 170 is positioned,

• a modification of the type of taxiway (typically the presence of a nearby intersection between taxiway VC and another taxiway),

The predicted trajectory of the first mobile element 170, and / or • at least one predefined traffic rule.

Each piece of data can be obtained by the first terminal 110 by consulting the main remote server 120 or the secondary remote server 140 associated with the geographical area 150 in which the first mobile element 170 is positioned, or be detected by the first terminal 110.

In addition, the step E420 may comprise a substep E424 in which a first list of neighboring elements positioned in a neighborhood of the first mobile element 170 is determined, said first list of elements comprising at least one mobile or fixed neighboring element. For each neighboring element of the first list, this first list comprises in one example an identification data item and / or the geolocation position of this neighboring item.

Each neighboring element of the first list can be determined according to DCO contextual data of the first mobile element 170 and / or of said neighboring element, at a first moment corresponding to the implementation of the substep E424 for determining the first list of the first list. neighboring elements, for example:

• a geolocation position, and / or

• a speed,

• a direction of movement,

• a direction of movement.

At least one element of the first list may further be determined from a message concerning the behavior of said neighboring element (acceleration or deceleration, change of direction, etc.), or a detection of such behavior.

A geographical area of neighborhood around the first mobile element 170 can be determined, each element positioned in the geographical area being first added to the first list.

The area of the geographical area around the first movable element 170 depends on the geolocation position of the first movable element 170.

The area of the geographical area around the first movable member 170 may further depend on the speed of the first movable member 170. Specifically, the higher the speed of the first movable member 170, the larger the area.

In addition, the geographical area around the first movable member 170 may depend on the direction of movement of the first movable member 170. For example, the zone extends in the direction of flow of the first movable member 170 in proportion to the speed of the first movable member 170, and decreases in the opposite direction of movement of the first movable member 170 in proportion to the speed of the first movable member 170.

In addition, a movable member positioned in the geographical area around the first movable member 170 can be removed from the first list according to the speed of said element, the distance between said element and the first movable element 170, the flow direction of said element and / or the position of said element.

Likewise, a movable element positioned outside the geographical zone around the first mobile element 170 can be added to the first list as a function of the speed of said element, of the distance between said element and the first movable element 170, of the direction of circulation. said element and / or the position of said element.

For example, a movable element can be removed from the first list if it is traveling at a high speed on another subway of the taxiway VC, behind the first movable element 170 and in a direction of traffic opposite to the direction of traffic. of the first movable member 170.

In another example, a movable element can be removed from the first list if it circulates on another subway of the taxiway VC, in front of the first movable element and in a direction of traffic opposite to the direction of circulation of the first element. mobile 170, but at a low speed.

In another example, a movable element can be added to the first list if it circulates on another underpass of the taxiway VC, in front of the first movable element 170, in a direction of traffic opposite to the direction of flow of the first element. mobile 170, and at a high speed.

In another example, a movable element can be removed from the first list if it circulates on the same VC circulation lane, behind the first mobile element 170, in the same direction of travel, but at a speed below the speed of the first movable member 170.

In another example, a movable element can be added to the first list if it circulates on the same VC circulation lane, behind the first movable element 170, in the same direction of circulation, and at a speed greater than the speed of the first movable member 170.

In another example, a mobile element can be added to the first list if it circulates on the same VC circulation path, in front of the first mobile element 170, in the same direction of travel, but at a speed below the speed of the first movable member 170.

In another example, a movable element can be removed from the first list if it circulates on the same VC circulation path, in front of the first mobile element 170, in the same direction of travel, and at a speed greater than the speed of the first movable member 170.

In another example, a movable member may be removed from the first list if it is traveling on a lane different from the traffic lane VC of the first movable member 170, and which does not lead to an intersection with the lane VC of first movable member 170 or which opens onto an intersection positioned behind the first movable member 170.

In another example, a movable element may be added to the first list if it is traveling at a high speed on a traffic lane different from the traffic lane VC of the first movable element 170, and which opens onto an intersection positioned in front of the first lane. mobile element 170.

At least one other element can be added to the first list based on predictive DCO contextual data of the first mobile element 170 and / or said element, at least a second time corresponding to the first moment to which is added a predicted duration of realization of one or more shares of a series of shares determined in step E430. The forecast contextual data can be:

• a position of predictive geolocation, and / or

• a forecast speed, and / or

• a direction of movement, and / or

• a predicted direction of movement.

As a variant, said at least one other element is added to a second list corresponding to said second instant (or to a duration between the second instant and a third instant, said duration corresponding to a predicted duration of realization of one or more actions of a series of actions determined in step E430). Several other lists corresponding to other times can thus be created.

The DCO contextual data and the predictive DCO contextual data can be obtained by the first terminal 110 by consulting the main remote server 120 or the secondary server 140 concerned.

The predicted geolocation position of the first mobile element 170 can be determined as a function of the speed of the first mobile element 170 at the time of the implementation of the substep E424, the forecast speed and / or the predictive trajectory of the first element mobile 170, and / or one or more actions of the set of actions determined in step E430.

The predicted geolocation position of a neighboring element of the list can be determined according to DCO contextual data obtained by the terminal associated with said neighboring element in step E408 and then sent to step E410, such as the forecast trajectory, the estimated route, the last speed or speeds, and / or the speed evolution.

The predicted geolocation position of a neighboring element of the list can be determined according to a potential impact of the realization of one or more actions of the series of actions by the first mobile element 170 on the contextual data DCO of the neighboring element. In the case where the element of the list is not associated with a terminal capable of implementing the steps E408 and E410, the contextual data COD of said terminal can be obtained and sent by another terminal associated with another positioned element. near said list item.

Step E420 may then comprise a sub-step E426 confirming the location position PG of at least one element next to the list determined in sub-step E424, by means of a measurement made by the first terminal 110.

This substep E426 is implemented by the first terminal 110, and can be reiterated for several neighboring elements.

In addition, the substep E426 can make it possible to update the position of geolocation, in particular in the case where the repeating period of the steps E408 and E410 is high, or in the case where the neighboring element is not associated with a terminal adapted to implement steps E408 and E410. Sub-step E432 can also be used to position one element relative to another.

During the implementation of this substep E426, the neighboring element is detected by the first terminal 110. A geolocation position of the neighboring element and possibly a DID identification data of the neighboring element (typically number of license plate) can then be obtained.

In addition, one or more characterization data DC (typically the general category, and a subcategory of the general category) and / or contextual COD (typically the direction of flow, the direction of flow, the speed, the evolution of the speed, the number of users, etc.) of the neighboring element can be obtained during the implementation of the substep E426.

In one example, the first terminal 110 analyzes one or more images obtained by the on-board camera of the first terminal 110 or the first mobile element 170 in order to identify the neighboring element and to determine the distance between the first mobile element 170 and the neighboring element. Thus, an identification datum and / or a geolocation position of the neighboring element can be obtained.

More specifically, the neighboring element can be identified by comparing the image of the neighboring element transmitted by the camera with image models of predetermined elements to determine the type of element (brand, color, model, size etc.), then comparing the determined type with the characterization data of the neighboring element.

The neighboring element can also be identified by extracting from the image obtained its registration number and comparing it with the identification data of the neighboring element.

In addition, the distance between the first movable element 170 and the neighboring element can be determined by comparing the image of the neighboring element with a reference image representing an element of the same type as the neighboring element. The proportions of the neighboring element on the image obtained can notably be compared to the proportions of the element of the reference image, while taking into account the conditions for capturing the transmitted image and the reference image. , to determine the distance.

The distance between the first movable element 170 and the neighboring element may also be determined according to a geolocated external element, such as a milestone.

In another example that can be combined with the preceding examples, in order to identify the neighboring element and to determine the distance between the first mobile element 170 and the neighboring element, the first terminal 110 analyzes an electromagnetic signal sent by means of the radar. the first terminal 110 or the first movable element 170, reflected by the neighboring element, and then received by the radar.

More specifically, the neighboring element can be identified by determining the signature echo of said element in the received signal. The distance between the first movable element 170 and the neighboring element can also be obtained, typically from the time elapsed between the sending of the signal and the reception of the reflected signal.

In another example that can be combined with the preceding examples, in order to identify the neighboring element and to determine the distance between the first mobile element 170 and the neighboring element, the first terminal 110 analyzes a laser signal sent by means of the scanner. laser of the first terminal 110 or the first movable member 170, reflected by the neighboring element, then received by the scanner.

One or more characterization data of the second element 130 (for example the type of vehicle) can be obtained by analyzing the received signal, typically using charts. The distance between the first movable element 170 and the neighboring element can also be obtained, typically from the time elapsed between the sending of the signal and the reception of the reflected signal.

The detected neighboring element can then be searched in the list or lists obtained in the substep E424, in order to confirm the position of geolocation or to update it.

More precisely, the geolocation position obtained in the substep E426 can be compared to one or more geolocation positions of the list or lists obtained in the substep E424.

In addition, the identification data obtained in the substep E426 can be compared to one or more identification data of the list or lists obtained in the substep E424.

If the data is updated, the first terminal 110 can send the updated data to the main remote server 120 or to the secondary remote server 140 corresponding to the geographical zone 150 in which the first mobile element 170 is positioned.

In addition, if the data is confirmed, the first terminal 110 can send an acknowledgment of the data to the main remote server 120 or to the secondary remote server 140 corresponding to the geographical zone 150 in which is positioned the first movable element 170.

When implementing the substep E426, a new neighboring element, that is to say a neighboring element that is not included in the list or lists, can be detected. This new neighboring element is typically an obstacle on the taxiway VC, or an animal or a human being, for example positioned at the edge of the VC lane on which the first movable element 170 passes.

The new neighbor element is then added to the list or lists, and the geolocation position of this new element is obtained. One or more other identification data DID, DC characterization or contextual DCO can also be obtained.

The first terminal 110 may send the data or data concerning the new neighbor element to the main remote server 120 or to the secondary remote server 140 corresponding to the geographical zone 150 in which the first mobile element 170 is positioned.

Step E420 can furthermore comprise a substep of confirmation of the speed and / or the trajectory of at least one element adjacent to the list or lists determined in sub-step E424 (for example several neighboring elements), by means of a measurement made by the first terminal 110.

More precisely, the substep E426 can be reiterated in order to obtain several successive geolocation positions of the neighboring element, in order to deduce therefrom the speed of the neighboring element (or the speed differential between the neighboring element and the neighboring element). first movable element 170) and / or the path of the neighboring element.

Other identification data DID, DC characterization or contextual DCO can also be confirmed or updated by the first terminal 110. In addition, the first terminal 110 can send acknowledgments or updated data to the main remote server. 120 or the secondary remote server 140 corresponding to the geographical zone 150 in which is positioned the first mobile element 170.

The step E420 may also include a substep E428 for detecting an AC action performed by the user of the first mobile element 170 when the first mobile element 170 is a living being. This substep E428 is implemented by the first terminal 110.

The action performed may be the triggering of a flashing light of the first movable member 170 and / or pressing on a brake pedal or acceleration.

The first terminal 110 may determine the EV event using a first lookup table taking as input a set of data including:

One or more data of the first mobile element 170 of the data series determined in the substep E422, and / or

One or more neighboring elements of the list or lists determined in the substep E424, that is to say one or more data obtained in the substep E464, One or more actions performed by the user or the first mobile element 170, detected in the substep E428, and / or

One or more messages received, sent (typically during the implementation of step E550 described below) by one or more neighboring elements of the list or lists determined in the substep E424, each message being able to indicate an action performed by the neighboring element sending the message.

The first lookup table typically includes several events, each event corresponding to a different set of data.

The detected event thus corresponds to a situation observed in a neighborhood of the first mobile element 170, which may involve one or more other elements, and / or an action performed by the user of the first mobile element 170 (or the first mobile element 170). .

In one example, the event EV determined is the presence, on the VC circulation lane of the first mobile element 170, of an obstacle, or of a mobile element (typically the second moving element 180) circulating:

On the same underpass as the first movable member 170,

In the same direction of circulation as the first movable element 170,

In front of the first mobile element 170, and

At a speed lower than the speed of the first mobile element 170, as well as possibly the presence of another moving mobile element:

• on the same underpass,

In the same direction of circulation as the first mobile element 170, and

Behind the first mobile element 170,

as well as possibly the presence of another moving mobile element:

• on another under way,

In the same direction of circulation as the first mobile element 170, and

Behind the first mobile element 170,

or the presence of another moving mobile element:

• on another under way,

In the opposite direction of circulation of the first movable element 170, and

In front of the first mobile element 170.

The event EV determined can also be the arrival of the first mobile element 170 on an intersection between its taxiway VC and another lane, as well as possibly:

• an obligation to give way to moving parts moving on the other traffic lane, and / or The presence of another mobile element on the other traffic lane, which can arrive at the intersection at the same time as the first mobile element 170.

The first look-up table is a data structure that can take the form of one or more trees, each tree comprising a main branch, each main branch being divisible into at least two sub-branches and so on. The main branch of each tree can then correspond to a global event corresponding to a first set of data (for example an arrival of the first mobile element 170 at an intersection) and each sub-branch corresponding to a more precise event corresponding to a second set of data (for example an arrival of the first mobile element 170 at an intersection, a neighboring element also arriving at the intersection). If the first set of data is checked, then every second set of data in the sub-branch is looked at, and so on.

In a variant, the step E420 is implemented by the main remote server 120 or the secondary remote server 140 associated with the geographical zone 150 in which the first mobile element 170 is positioned. The data obtained by the first terminal 110 in the substep E426 and / or the substep E428 are then sent by the first terminal 110 to the server 120 or 140.

Then, in a step E430, a series of SAC actions that can be performed in response to the event determined in step E420 is determined, by consulting a second correspondence table between at least one event and at least one series. of shares.

The step E430 may be implemented by the first terminal 110 and / or the main remote server 120 or the secondary remote server 140 associated with the geographical zone 150 in which the first mobile element 170 is positioned.

The series of SAC actions that can be performed comprises at least one action, typically several actions. In addition, the second lookup table typically comprises a plurality of events, each event being associated with a series of actions that can be performed.

The second correspondence table is previously developed by associating, with a predefined event, the most appropriate action or actions in response to the event. This association is thus determined according to the potential result of carrying out each action in response to the event.

It is thus possible to find, from the event determined in step E420, the series of actions that can be performed in response to this event. Each action can be a modification of a driving parameter, such as a change of trajectory or a modification of speed (acceleration or deceleration) or, alternatively, the display of a message.

In one example, a first predefined event is the presence, on the VC circulation lane of the first mobile element 170, of an obstacle, or of a mobile element (typically the second moving element 180) circulating:

On the same underpass as the first movable member 170,

In the same direction of circulation as the first movable element 170,

In front of the first mobile element 170, and

• on the same underpass,

In the same direction of circulation as the first mobile element 170, and

Behind the first mobile element 170,

as well as possibly the presence of another moving mobile element:

• on another under way,

In the same direction of circulation as the first mobile element 170, and

Behind the first mobile element 170,

or the presence of another moving mobile element:

• on another under way,

In the opposite direction of circulation of the first movable element 170, and

In front of the first mobile element 170.

The series of actions SAC that can be carried out, associated with this first predefined event, may comprise an acceleration of the first mobile element 170 and a change of trajectory of the first mobile element 170 in order to overtake the mobile element circulating on the same sub-channel. circulation that the first movable member 170, in the same direction of movement as the first movable member 170, and in front of the first movable member 170 (or to overcome the obstacle), possibly preceded by a wait and possibly a slowdown the first movable member 170 to let the other mobile element flowing on the other under traffic lane.

A second predefined event may be the arrival of the first mobile element 170 on an intersection between said VC circulation lane and another lane of traffic, as well as possibly:

The series of actions SAC that can be performed, associated with this second predefined event, may comprise a slowing down of the first mobile element 170 or a stopping of the first mobile element 170 in order to let the other mobile element pass, then an acceleration in order to overtake intersection.

The series of actions can be initiated or modified, for example following a message receiving step F550, described in more detail below with reference to FIG. 6.

Each action can be associated with a start time of the action and / or a projected duration of the action.

The starting instant of completion of the action and / or the estimated duration of one or more actions can be obtained in this step E430.

The starting instant of the action and / or the predicted duration are obtained as a function of contextual data COD of the first mobile element 170 and possibly as a function of contextual data COD of one or more elements neighboring the list or lists. determined in substep E424. The speed, the path and the direction of movement can for example be considered.

The starting instant of completion of the action is typically in the form of a GMT time, or in the form of a remaining time. The starting moment of realization of the action is not necessarily immediate.

In a step E440, for at least one action of the SAC action set determined in step E430, a communications SC scenario associated with said action is determined.

The step E440 can be implemented by the first terminal 110 and / or the main remote server 120 or the secondary remote server 140 associated with the geographical zone 150 in which the first mobile element 170 is positioned.

The communications scenario SC comprises at least one message, typically a series of several messages. Each message of the scenario is intended to be sent or received by the first terminal 110, before the potential realization of the action corresponding to the communications scenario.

As described in more detail below, the same message in the series can have multiple recipients. In addition, several messages of the series can be sent to the same recipient, typically in a successive manner.

The sending and receiving of the scenario messages allow the first terminal 110 to warn neighboring elements that the action should be performed and can enable it to ensure that the action can be performed. The SC scenario is for example determined by consulting a third correspondence table between at least one action and at least one SC communication scenario.

The third lookup table typically includes a plurality of actions, each action being associated with an SC scenario. It is thus possible to find the communications scenario corresponding to the action.

The third correspondence table is previously developed by associating, with a predefined action, the scenario most suited to the implementation of the action.

Step E440 can be implemented for several actions of the series of actions SAC determined in step E430, for example all the actions of this series.

The step E440 comprises a selection sub-step E442, in the first list of neighboring elements determined in the substep E424, for at least one message of the communication scenario SC, of one or more neighboring elements receiving the said message ED.

Alternatively, the element or elements are selected in a second list determined in the substep E424, corresponding to the starting instant of realization of the action in question. The element or elements are then selected according to the starting time and / or the duration of the action considered.

This selection of neighboring ED recipient elements makes it possible to send a message only to the neighboring elements concerned, that is to the neighboring elements on which the action corresponding to the message can have an impact, and thus makes it possible to reduce the number sent messages and thus not to clutter the network. The selection therefore depends on the action considered.

The impact of the action on the neighboring element may be a collision between the first mobile element 170 and the neighboring element, or the modification of a driving parameter of the element (such as the trajectory or the speed) .

When the action is a braking of the first movable element 170, a neighboring element that can be impacted is a moving neighboring element positioned on the same VC circulation path as the first movable element 170, in the same direction of circulation as the first movable element. 170, and behind the first movable member 170.

When the action is an acceleration of the first movable element 170, a neighboring element that can be impacted is a moving neighboring element positioned on the same VC circulation path as the first movable element 170, in the same direction of circulation as the first moving element. 170, and in front of the first movable member 170.

When the action is a change of trajectory of the first movable element 170, a neighboring element that can be impacted is a neighboring element that can cross the first movable element 170, typically a neighboring element flowing in a direction and / or direction different from the direction and / or the direction of the first movable element 170, so that the trajectory of the neighboring element can cut or meet the trajectory of the first movable element 170. In one example, a risk of impact of the action on each neighboring element of the list is calculated in this sub-step E422.

The risk of impact is calculated based on contextual data of the first mobile element 170 and the neighboring element.

The risk of impact is typically calculated according to:

The geolocation position of the first mobile element 170,

• the geolocation position of the neighboring element,

The predicted trajectory of the first mobile element 170,

• the forecast trajectory of the neighboring element,

The speed of the first movable element 170,

• the speed of the neighboring element and its expected evolution,

• an information (communication, flashing, call of lights, ...) emanating from a neighboring element and concerning a DCO contextual data of this neighboring element or another neighboring element.

If the risk is greater than a threshold, the neighboring element is selected and then becomes a neighbor element of the message.

An identification data item of each neighboring message recipient element, typically the MSISDN number of the terminal associated with the neighboring message recipient element, is then obtained, for example by consulting the main remote server 120.

In the case where the neighboring element is not able to receive and / or interpret the message, the neighboring element is not selected. Another visible element of the element and comprising a display module such as a screen (typically a billboard or truck) can then be selected in place of the neighboring element, so that it can then display part of the message to notify the user of the neighboring item.

The substep E442 can be implemented for several messages of the communications scenario SC, for example all the messages of scenario SC.

The neighboring element or elements receiving several messages can thus be searched.

In a substep E444 of step E440, the CM content of at least one message of the communications scenario SC is determined.

CM content can be normalized. In addition, the content may include at least one information from the following list of information:

The scenario determined in step E440,

The action corresponding to said message,

A contextual datum of the first mobile element 170 depending on said action corresponding to said message,

The number of the message in said scenario, An identifier of the sender of said message,

A time indication concerning said action corresponding to said message,

• a temporal indication concerning at least one or more other shares of the said series of shares,

• an indication as to what to do with the message,

• a list of possible answers including at least one answer.

The contextual data of the first mobile element 170 depending on said action corresponding to said message is for example a predictive trajectory of the first mobile element 170 depending on said action (typically a direction of circulation and / or a direction of circulation), and / or an evolution the speed of the first movable member 170 depending on said action.

The identifier of the sender of said message is typically the MSISDN number of the first terminal 110.

The temporal indication concerning the action may include a starting instant of execution of the action, typically in the form of a GMT (Greenwich Mean Time) timetable, in seconds from 1 ^{January 1} , 1970, or in the form of a remaining term, or include a time remaining before the time of departure.

The temporal indication of the action may further include a predicted duration of action. The duration value is typically a few seconds, for example 15 seconds for a braking action when the speed of the first mobile element 140 is 170 km / h, 40 seconds to exceed a vehicle according to a given speed differential, etc. The contextual data of the first mobile element 170 are therefore used to determine said forecast duration.

The indication of the action to be given to the message may include information indicating:

• the message is only informative, no message should be sent as a result of the receipt of this message, or

• one or more messages must be sent, as well as the identifying and possibly contextual data of the recipients of these messages.

The indication concerning the follow-up to be given to the message may further comprise information indicating whether one or more actions should be performed following the reception of the message (a suggestion of action).

The list of possible responses comprises at least one message that can be sent and / or at least one action that can be performed after receiving the message. Each message that can be sent is typically normalized and can be part of the communications scenario. The list of possible responses may further include the sending times of the message that can be sent and / or performing the action that can be performed, as well as the estimated duration of this action.

The action that can be performed is typically the modification of a driving parameter. Alternatively, the action that can be performed is a display of a part of the message. The list may then include an item of identification data that can be prevented by the display (typically its license plate), display instructions and the message to display.

The information list may also include the application used by the first terminal to implement the method.

In a variant, the message is a SIP-options message intended to be sent according to a RCS protocol.

In one example, each piece of information is preceded in the message by:

• a reference code indicating the type of information, and

• a first separator character.

In one example, the reference code of the information of the "application" type is AP, the reference code of the "scenario" type information is SC, the reference code of the "action" type information is ST, and the reference code of the issuer identifier type information is SE.

The first separator character is for example a punctuation mark, typically a double point.

In addition, each piece of information can be separated from the following information by a second separator character, typically the symbol "$$".

Information of the same type is indexed. For example, the message comprises three pieces of information of the same type, the reference code of this type of information being AN, the reference code of the first piece of information is AN1, and the reference code of the second piece of information is AN2, the two pieces of information. information being separated by the second separator character.

When the action to be given to the message includes several messages to be sent, the identification data and the item type of each recipient may be indicated, preceded by the same reference code, the identification data and the type of element being separated by the second separator character.

For example, if the reference code for the recipient elements is DE, we will have for two recipients the following sequence:

DEl: 0645858596 $ ccl $$ DE2: 0658995566 $$ cc2,

in which DE1 and DE2 is the reference code indexed by each recipient element, each reference code being followed by the identification data ("0645858596" and "0658995566") then the item type of each recipient ("ccl" and "cc2").

In an example illustrated in FIG. 5, the first movable element 170 and the second movable element 180 are vehicles traveling on the under right track SCI of a traffic lane SC. The second movable element 180 circulates in front of the first movable element 170, the first movable element 170 wishes to double the second movable element 180, and the second movable element 180 has agreed to the first movable element 170 during a pre-exchange part of the SC scenario.

In this example, the first mobile element 170 must signal its action (double the second mobile element 180) to the two vehicles 510, 520 which follow it on the under right track SCI, without waiting for return from these vehicles 510, 520 .

In addition, in this example, the first movable member 170 must signal its action to the vehicle 530 which arrives on a subway left SC2 of the taxiway SC, and wait for its return to engage.

In addition, in this example:

The identification data of the first mobile element 170 is 0600000000,

• the reference code of the communications scenario to be applied is DA (double on motorway),

The reference code of the message number is 3 (because a first message has been sent by the first mobile element 170 to request the second mobile element 180 the authorization to double it and a second message has been sent by the second mobile element 180 to the first mobile element 170 to give it permission to double it),

The identification data of the two vehicles 510, 520 which follow the first mobile element 170 on the right-hand sub-channel SCI are 0611111111 and 0611111112,

• the identification data of the vehicle traveling on the left sub-SC2 is 0622222222,

The reference code of the vehicle type for the two vehicles 510, 520 which follow the first mobile element 170 is VD, and

The reference code of the vehicle type for the vehicle 530 traveling on the left sub-track SC2 is VG.

The first terminal 110 associated with the first mobile element 170 can then send a message to the vehicle 530 arriving on the left sub-channel SC2, and the content of the message can then be as follows:

AP: GE $$ SC: DA $$ ST: 3 $$ SE: 0600000000 $$ TM: RERA $$ AE: DO $$ AS: 12 $$ AD: 75 $$ AN1: OK $$ AN2: KO $$ OD: 0611111111 $ VG $$ OD: 0611111112 $ VG, In this message, the following reference codes are applied:

• "AP" for the application,

• "SC" for the scenario,

• "ST" for the message number in the scenario,

• "SE" for the identifier of the transmitter,

• "TM" for the indication concerning the follow-up to be given to the message,

• "AE" for the action,

• "AS" for the moment of departure,

• "AD" for the estimated duration of the action,

• "AN" for the list of possible response messages to the first mobile element,

• "OD" for the recipient elements of the messages that can be sent.

In addition, in this message, the RERA code means that a message should be sent to the first mobile element 170 and another message should be sent to the two vehicles 510, 520 which follow the first mobile element 170 on the right under track SCI .

The substep E444 can be implemented for several messages of the communications scenario SC, for example all the messages of this scenario SC.

Fig. 6 shows a communication method according to an exemplary embodiment of the invention.

This communication method is implemented by a system such as the system 100 of FIG.

The communication method comprises the determination method 300 or 400 as described above with reference to FIG. 3 or FIG. 4.

The communication method further comprises a step E550, wherein at least one message MS of the communications scenario SC determined in step E440 is sent, via the telecommunications network 160, by the first terminal 110 to the terminal associated with the neighboring element recipient of said message, determined in the substep E442, or the terminals associated with neighboring elements recipients.

In one example, the sending is done according to a RCS protocol, and the message is a SIP-options message.

The message MS is typically sent before the start time of realization of the action associated with the scenario SC.

The step E550 can be repeated for each message MS of the scenario SC.

In the remainder of the description, it will be considered that the destination element is the second mobile element 180. An MS message is thus sent to the second terminal 130.

The sent MS message (s) may also be transmitted to a remote server dedicated to storing a sent message history, in order to be preserved. In a step F550, the second terminal 130 receives the message MS.

Then, in a step F560, the second terminal 130 analyzes the message MS.

If the message MS comprises information indicating that one or more messages MS2 must be sent in response to the message MS, the second terminal 130 extracts from the message the identifying and possibly contextual data of the recipient elements of these messages MS2 that can be sent, then the list of possible answers.

The second terminal 130 then determines the content of the MS2 message or messages that can be sent using the aforementioned information, then sends (step F570) the MS2 message or messages. The substep E444 can be implemented by the second terminal to determine the content.

The step F550 and possibly the steps F560 and F570 can be implemented by each terminal to which a message of the scenario is sent to the step E550.

If a recipient element is the first terminal 110, the message MS2 sent to the first terminal 110 may be part of the communications scenario. The first terminal 110 may, following receipt of this message MS2 sent by the second terminal 130, repeat step E550 to send yet another message of the communications scenario.

The message MS2 sent by the second terminal 130 may further modify the event occurring at the taxiway SC and / or the communications scenario. The steps E420, E430, E440, E550, F550, F560 and / or F570 are then repeated taking this message into account.

Thus, one or more distinct neighboring elements of the elements selected during the first iteration of the substep E424 can be selected during this reiteration and then contacted.

In addition, the first terminal can determine a new event while the implementation of the method for the previously determined event is not completed. The implementation of the method for the event previously determined can then be interrupted and the steps E420, E430, E440, E550, F550, F560 and / or F570 can then be reiterated for this new event, possibly taking into account messages previously exchanged between the terminals.

Claims

A method for determining a communications scenario (SC) corresponding to at least one action that can be performed by a first mobile element (170) located at a taxiway (VC), in response to at least one event (EV), implemented by a first terminal (110) associated with the first mobile element (170), characterized in that it comprises the following steps:

Determining (E320, E420) at least one event (EV) in a neighborhood of the first movable element (170), as a function of at least one neighboring element of a list (LEV) of neighboring elements positioned in said neighborhood, said list (LEV) of neighboring elements comprising at least one neighboring element,

Determination (E330, E430) of at least one series of actions (SAC), which can be performed in response to said at least one event (EV), by consulting a correspondence table between at least one event and at least one a series of shares, said determined series of shares (SAC) comprising at least one share,

For at least one action of said at least one series of actions (SAC), determining (E340, E440) a communications scenario (SC) associated with said at least one action, said scenario comprising at least one message,

the step of determining (E340, E440) a communications scenario (SC) comprising a selection sub-step (E342, E442), in said list (LEV), for at least one message of the communications scenario, at least one neighbor element (180) recipient of said message.

2. Determination method according to claim 1, wherein said determining step (E420) comprises, for said at least one action of said at least one series of actions (SAC), determining a start time of realization. of the action and a duration of the action, so that said at least one neighboring element (180) receiving said message is selected according to said start time of realization of the action and said duration of realization of the action.

The method of determining according to claim 1 or 2, wherein the step of determining (E440) a communication scenario (SC) comprises obtaining a MSISDN number of a terminal (130) associated with said least one neighboring element (180) recipient of said message.

4. Determination method according to any one of claims 1 to 3, wherein at least one neighboring element of said list (LEV) of neighboring elements is determined according to:

• a geolocation position, and / or

• a speed, and / or

• a direction of travel, and / or

• a direction of movement,

said first movable element (170) and said neighboring element, at a first instant corresponding to the implementation of the determination (E424) of the list (LEV) of neighboring elements, and at least a second instant corresponding to the first instant to which is added a projected duration of realization of one or more shares of the series of actions (SAC).

5. Determination method according to claim 4, the determining step (E420) of said at least one event (EV) further comprises a substep (E426) confirming the position of geolocation of said at least one neighboring element of the list (LEV) of neighboring elements, by means of a measurement made by the first terminal (110).

The method of determining according to any one of claims 1 to 5, wherein a content (CM) of said at least one message of the scenario (SC) is normalized and comprises at least one of the following list of information:

• the scenario (SC),

The action corresponding to said message,

A contextual datum of the first mobile element (170) depending on said at least one action corresponding to said message,

• a message number in the scenario (SC),

An identifier of the first terminal,

A temporal indication concerning said at least one action corresponding to said message,

• a time indication concerning at least one other action of said series of actions (SAC),

• an indication of what to do with the message,

• a list of possible answers including at least one answer.

Communication method comprising the method of determining according to any one of claims 1 to 6, comprising a sending step (E550), the first terminal (110) and a telecommunication network (160), said least one message from the scenario to said neighbor neighbor element (180).

The communication method according to claim 7, wherein the sending is done according to a RCS protocol, and said at least one message is a SIP-options message.

9. Terminal (110) adapted to implement a determination method according to any one of claims 1 to 6.

A computer program (PI) comprising instructions for performing the steps of the determining method according to any one of claims 1 to 6 when said program is executed by a computer.

A computer-readable recording medium on which a computer program (PI) is recorded including instructions for performing the steps of the determining method according to any one of claims 1 to 6.