WO2014090412A1

WO2014090412A1 - Method for obtaining hierarchical feedback from entity-location tracking in a theater of operations

Info

Publication number: WO2014090412A1
Application number: PCT/EP2013/003786
Authority: WO
Inventors: Laurent VROMMAN; Vincent LOMBART; Maxime LORIDAN
Original assignee: Cassidian Sas
Priority date: 2012-12-14
Filing date: 2013-12-16
Publication date: 2014-06-19

Abstract

The invention relates to a method for obtaining hierarchical feedback from entity-location tracking, whether said entities are technical, functional or human, by relying on an interface for tracking entity locations, in order to minimize both the data feedback time and the bandwidth used for said feedback.

Description

METHOD FOR HIERARCHICAL UPGRADING OF GEOLOCATION OF ENTITIES

ON A THEATER OF OPERATION

Field of the invention

The present invention relates to a method for the hierarchical reassembly of geolocation of entities, whether said entities are technical, functional, or human, present on a set of networks or subnets deployed. More particularly, the invention is in the context of exchanges of geographical positions between entities present in tactical systems and using networks of a theater of operations.

State of the art and technical problems encountered

In the state of the art, a telecommunication system deployed on a civilian or military theater of operations usually relies on a set of networks, subnets and a set of ad-hoc mobile radio units. These networks include a set of autonomous host nodes or terminals that, because they are generally mobile, are sometimes within range of each other, and generally can not rely on a predefined fixed infrastructure in their environment.

Nodes in an ad-hoc communication network can move, or be destroyed, or new nodes can join the network. In other words, the network environment is mobile, wireless, dynamic and without infrastructure.

The topology of such a network is called "ad-hoc" in that it evolves dynamically over time because the connectivity between the nodes can vary over time.

Each terminal has a common technical base to improve the implementation of operational capabilities, such as simplification of deployment. This allows the establishment of end-to-end secure exchange capacity over the entire communication chain. These terminals offer total interoperability on all the networks or subnetworks crossed.

Considering, for example, a set of tactical vehicles distributed according to a pre-established planning over a large or restricted geographical area, each tactical vehicle is provided with a mobile terminal. Each mobile terminal is able to connect either with other mobile terminals, or at least one fixed network node, when the vehicle passes close to said network. Each tactical vehicle is then considered in this example as an ad-hoc mobile radio unit. The geographical area of deployment of mobile terminals is when considered as the theater of operations.

The fact that the mobile terminals communicate with each other by wireless links, they must suffer the effects of radio communications, such as for example noise, fading also called "fading" and jamming.

Factors such as the variable quality of wireless links, loss of propagation paths, interference due to the multiplicity of users, dissipated power and changes in topology can become particularly problematic in urban, mountainous or jungle environments.

The connections between the different terminals can also be interrupted or established, depending for example on the distance, the variation of the signal strength due to multiple paths, the weather, the presence of mountains, the presence of buildings, loss of terminals, etc.

Thus, changes in the condition of propagation and environment, as well as the unpredictability of the motions of the mobile terminals and any failures thereof, may contribute to the dynamic nature of an ad-hoc network, as previously predefined.

Additional constraints can also be added to this environment. These are, for example, aspects concerning the security of communications between the different terminals, and the reliability or integrity of the communications received.

Indeed, each terminal is provided with a messaging service. The role of this messaging service is to allow the transport of messages to one or more recipients identified by their mailbox SMTP address. This transport of messages is done by making transparent to the users the path and the borrowed media. Message transport takes into account mobility and application routing. As such, the messaging service acts as a proxy for user applications. However, the fact that terminal users are mobile, for example, via their vehicles, is a major drawback. Indeed, being mobile terminals change networks or subnets regularly, making their dynamic IP address on each of these networks. In one example, when a sender sends his message through his terminal, his mail server must determine which is the recipient's mail server or the next mail relay, to bring the message to port.

There is therefore a need for a component or service to go up hierarchically with respect to the topology of the network the positions of each entity previously located or geolocated on a geographical area or theater of operation.

Presentation of the invention

The present invention aims to solve all the disadvantages of the state of the art. For this, the invention proposes a method for the hierarchical reassembly of geolocation of entities, whether technical, functional, or human. The invention relies for this on a feature geolocation interface, to minimize both the data ascent time, but also the bandwidth used for this ascent.

The invention thus allows the messaging service to use all the capabilities of the topology of the various networks constrained to optimize the bandwidth. It also allows an automatic and synthetic management of the positions of the entities raised by the networks at levels lower than a master network. The invention also makes it possible to automatically and synthetically manage the positions of entities injected at the access points of the networks. This allows a consolidation of the tactical network step by step.

Brief description of the figures

The invention will be better understood on reading the description which follows and on examining the figures which accompany it. These are presented for illustrative purposes only but not limited to the invention. The figures show:

- Figures 1 - 2: schematic representations of the principle of ascending entity positions, through flows, according to one embodiment of the invention; FIG. 3: an initialization functional diagram of the method of hierarchical reporting of geolocated positions of entities, according to one embodiment of the invention;

FIG. 4: a functional diagram of a method of subscription to the receipt of notifications resulting from the geolocation of entities, according to one embodiment of the invention;

- Figure 5: a functional diagram of a method of unsubscription upon receipt of notifications from the geolocation feedback, according to one embodiment of the invention;

- Figures 6 - 7: a functional diagram of a position injection method for the recovery of the geolocation of entities, according to one embodiment of the invention;

- Figures 8 - 9: a functional diagram of the method of geolocation reassembly of entities, according to one embodiment of the invention;

FIGS. 10-11 show a functional diagram of a method for receiving positions with a view to raising the geolocation of entities, according to one embodiment of the invention;

Description of the invention

It is already noted that the figures are not to scale.

The following achievements are examples. Although the description refers to one or more embodiments, this does not necessarily mean that each reference relates to the same embodiment, or that the features apply only to a single embodiment. Simple features of different embodiments can also be combined to provide other embodiments.

The invention finds an advantageous application in the deployment of tactical type telecommunication systems in a theater of operations. Such a telecommunication system is able to deploy autonomously. To constitute such a telecommunication system, it is first necessary to determine an exchange platform for each entity.

The exchange platform is able to ensure the deployment of the telecommunication system according to the information contained in a data file FD. This FD data file is then loaded into each terminal intended to communicate in the communication system. The FD data file contains the list of symbolic addresses according to the type of network used. With this FD data file, the exchange platform implements a routing system to automatically discover the accessibility of the various entities that are deployed in the theater of operations. The telecommunication system is considered operational when the different entities are able to communicate with each other.

The exchange platform is based on digitization of the theater of operations. In other words, each entity within the theater of operations has at least one address. A terminal can be considered as a non-limiting example of an entity.

This telecommunication system comprises a set of networks each belonging to operators of access to the telecommunication means, which may be distinct. The transmission of data between each network is established through a set of routers or network access point, so as to form a network of networks deployed in the theater of operations. This mesh of networks is made in such a way as to take into account, on the one hand, the mobility of an entity in one of the networks and, on the other hand, the switching of an entity from one network to another without interruption of the networks. data transmissions.

The exchange platform is able to coherently ensure the transport and routing of all communications, relying on autonomous tactical transmission systems such as a wired internalized zone network, a wired zone network. outsourced, a high frequency network called HF (High Frequency), or a very high frequency network said VHF (Very High Frequency).

The trading platform implements a secure communication architecture for the benefit of each entity. The exchange platform also makes it possible to deploy several levels of security within the same network.

This exchange platform is constituted by a set of interconnections of data transport services such as a messaging service. Each messaging service is implemented in a terminal that can be fixed or mobile. The messaging service of each terminal is fully interoperable on any network deployed in the theater of operation. The exchange platform implements an architecture that takes into account the dispersion of the various entities in the theater of operations by allowing access to long-lived transmission means.

Said platform allows sharing and cross-circulation of information between the users of the messaging service and its application platform.

However, it is necessary to determine geographical position information of each of the entities in the theater of operations, in particular on the constrained networks. In order to make this determination while taking into account the radio resource limitations of the constrained networks, only routers allowing access to IP-WAN networks will have a global vision of the positions of the entities of the theater of operations, after aggregating the partial information reported by the networks. different networks constrained.

Indeed, the exchange platform relies on a set of IP-WAN radio or wired networks, as well as a set of constrained networks connected to IP-WAN networks, and a set of ad-hoc radiomobile entities.

In the invention, IP-WAN (Wide Area Network) technology networks are networks such as LTE (Long Term Evolution), 3G (Third Generation), 2G (Second Generation),

WIMAX, WIFI, etc.

The constrained network or PRG4 is a network with fourth-generation radios to establish a communication network. This type of PRG4 network was created to counter potential threats to communication devices in the context of electronic warfare. Listens, electromagnetic impulses, intrusions, localization and jamming are the most formidable manifestations. So we had to invent a system of very high frequency tactical radiocommunications or VHF (for Very High Frequency), which is safe enough to keep an entity in operational conditions. PRG4 has, for example, a built-in digital encryption against eavesdropping, a frequency evasion system that prevents localization and interception, and a free channel search for jamming. These networks include a set of autonomous host terminals which, because they are generally mobile, are sometimes within range of each other, and generally can not rely on a predefined fixed infrastructure in their environment.

To this end, the invention proposes a method of hierarchical reporting of the positions of entities to the IP-WAN network, enabling different terminals, equipped with a messaging service, circulating inside the inter-terminal exchange platform. , to determine at any time, the position of one or more entities. The invention allows an exchange of information between the different instances of the mail server of each terminal, such as geolocation information entities and application routes to access these entities.

A geolocation server relies on a data transport service, such as a messaging service, as well as the specific geolocation services provided by the available radio networks. Each instance of the geolocation server keeps a geolocation database locally for all users of the theater of operations of which it is aware. This geolocation data is updated by mechanisms of the geolocation server: injection, announcement, collection, synthesis, etc. The operating mode of the geolocation server is said to be replicated, because when a geolocation server no longer functions, another server takes over, without the users realizing it.

The geolocation data consist mainly of an association between a symbolic reference representing a terminal user or a theater entity, with a geolocated position.

The geolocation service will generate two distinct streams, depending on the role played by the entity in the tactical theater topology. Thus, when the entity plays a geolocation relay role, the platform will generate a stream called "synthesis flow". Similarly, when the entity does not play a geolocation relay role, the exchange platform will generate a flow called "ad flow". The information concerning the relocation role of geolocation or not of the entity is deduced from data provided by the application location and routing service. The same entity is able to play different roles at different times. The purpose of the ad flow is to allow each relay to know the positions of the entities of the immediately lower networks, also called subnets.

Figures 1 and 2 are illustrations of the principle of ascending entity positions, through flows. In these figures, an IP-WAN network comprises two points P1, P2, access to forced networks RC5, RC6. These networks constrains RC5, RC6, comprise a set of entities of which respectively a Q1 entity and a Q2 entity. The entity Q1 is able to establish a constrained RC3 network of lower level compared to the RC5 network. Similarly, the entity Q2 is able to establish a constrained network RC4 lower level compared to the RC6 network. The network RC3 comprises a set of entities Q1a, Q1b, Q1c and R1. The entity R1 is able to establish a constrained network RC1 and a constrained network RC2, these two networks RC1 and RC2 being of lower level with respect to the network RC3. The network RC2 comprises a set of entities R1a, R1b, R1c, and the network RC1 also comprises a set of entities (not referenced)

With regard to the advertisement flow, illustrated in FIG. 1, it enables the R1 entity acting as relay to acquire the positions of the entities R1a, R1b, R1c of the network RC2, as well as those of the entities of the RC network. The ad flow also enables the Q1 entity acting as relay to acquire the positions of the entities Q1a, Q1b, Q1c as well as the positions of the entities acquired by the relay entity R1. This principle applies as follows, until the announcement flow allows the network access point P1 forced to go back to the IP-WAN network, the positions of the entities of the network RC5, as well as the positions acquired. by the relay entity Q1.

To achieve this announcement flow, mechanisms specific to the types of forced networks traversed, are implemented, such as, for example, network collection messaging. The ad feed is only active on constrained networks.

With regard to the synthesis flow, illustrated in FIG. 2, it allows each relay to acquire the known positions of the relays of the immediately lower level networks and / or of the injected positions. On the IP-WAN network, this flow allows the exchange of positions between the different technical centers of access to networks constrained CTA. In the example of FIG. 2, the entity R1 acting as a relay, is able to give Q1 its position and the positions of the entities collected on the constrained networks RC1 and RC2. Of even, the entities Q1 and Q2 acting as relays, are respectively able to give points P1 and P2 access to the constrained network, their position and the positions of the entities collected on the respective constrained networks RC5 and RC6. Thus, step by step, the points P1 and P2 know the positions of all the entities of networks RC1, RC2, RC3, RC4, RC5, RC6, lower level. On the IP-WAN network, only the synthesis flows are active. The synthesis flows stop at points P1 and P2 in order to be processed by the exchange platform.

In the majority of cases, the geolocation service will be responsible, through ad flows, for collecting the positions of the entities of a network at the router. However, it is necessary to allow the terminals to use their own position collection mechanisms and to inject these positions into the geolocation service.

To provide such a hierarchical escalation service of entity positions, while limiting the amount of information exchanged, the exchange platform must provide a suitable data routing mechanism. The exchange platform thus makes it possible to define a period of recovery of the positions of entities. The geolocation service filters the information so as to transmit the position of an entity only if the emission delay of said position has expired or if the position has changed. The routing of position information is periodic, which depends on the type of network traversed. For example, this period will be more important on High Frequency (HF) type networks, because of the access time to the relatively large radio resource on this type of network.

It is possible to administer the geolocation retrieval service on the constrained network access service, in order to stop the previously started geolocation service, by deactivating the position and summary retrieval capabilities, or to start the geolocation service. geolocation service previously stopped. The feature lift function is enabled by default.

The position of each entity is associated with information such as the fact that the entity is a terminal or a network node, as well as the timestamp of said position. Other optional information may also supplement this information, such as speed of travel, altitude, latitude, longitude, or direction of travel. the entity. The collection of the positions of each entity on the constrained networks stops at the first CTA technical center of a constrained network access point, and is not broadcast to other IP-WAN access technical center. In the case where two access points to a constrained network deployed are available, then, depending on the state of the networks, the congestion of the transmission channels, the location of the transmitting entity or relay in the topology of said network the position of each entity arrives on one of the two access points randomly.

Conveniently, with respect to the relaying position phase of a relay entity, such as R1, Q1 and Q2, the geolocation service maintains a timer for each flow type. A first timer is for the ad stream, and a second timer is for the summary stream.

When the ad timer expires, when the ad stream is active, and all the components or services connected to the IP-WAN network, necessary for the exchange platform, no longer perform their routing functions. information, then the entity position feedback service sends its position data to a routing relay for routing to the next router to the IP-WAN network. Mail Relay is a component used to ensure the routing of data conveyed by the exchange platform.

When the synthesis timer expires, when all the components or services connected to the IP-WAN network, which are necessary for the exchange platform, carry out their information routing functions, then the entity position feedback service sends its position data to the messaging relay for routing to the next router to the IP-WAN.

The entity position feedback service records said positions until the next position is transmitted. At each position reception, the entity position feedback service notifies the subscribers who have requested it, the positions received.

On the IP-WAN network, the positions received from the constrained networks are exchanged between the various technical access centers CTA to networks constrained using the messaging service.

With regard to the reception phase, irrespective of the origin of the data received, ie by radio or by injection into the exchange platform, the entity's reporting service enriches its list of positions. When a position relative to an entity already exists, then said reassembly service verifies that this received position is more recent than the one previously stored, taking into account the time stamp of said position.

There is also a so-called disengage phase, corresponding to the deactivation of the entity position feedback service. In general, the Feature Lift service is not disengaged by default. On a SARC constrained network access server, it is possible to disengage or deactivate the callback service via a service management human machine interface. When the entity position feedback service is disengaged, no position is raised, regardless of the type of network used. Likewise, no position interrogation is performed and there is no more position picking load on the SARC. In addition, the exchange platform can no longer use this service for both position injection, but also, in terms of syntheses.

In such a case, it is possible to restart the entity position feedback service via the service management human machine interface. Thus, all the positions issued by the subordinate entities between the start and the end of the disengagement are ignored and are therefore not reassembled at the end of the disengagement.

The object of the invention therefore relates to a hierarchical method of ascending entity position implemented by one or more control units (not shown).

Such a control unit is known to those skilled in the art and is not the subject of our invention. A further description of this control unit is therefore unnecessary. However, the actions performed by the control unit of each terminal or entity are ordered by a microprocessor (not shown). This microprocessor produces, in response to the instruction codes stored in a program memory (not shown), commands intended to implement the method of the invention, as well as the various members associated with said control unit. For this purpose, the program memory comprises several program areas corresponding respectively to a sequence of steps. FIG. 3 is an exemplary functional diagram of initialization of the method of hierarchical reassembly of geolocated positions of entities, according to an embodiment of the invention

At a step 100, the control unit of the terminal initializes the parameters and variables that will be useful for the proper operation of the method. When step 100 has been executed, then the control unit performs a step 101.

In step 101, the control unit waits for configuration of the AGST management agent of the entity upstream service. An AGST management agent is a component or service that supports the configuration and alarms of terminal services and equipment. When the management agent has been configured, then in a step 102, the control unit stores or stores this configuration.

When the control unit has performed step 102, then it executes a step 400.

FIG. 4 is an example of a functional diagram of a method for subscribing to the receipt of notifications resulting from the geolocation retrieval of entities, according to one embodiment of the invention.

At a step 200, the terminal control unit waits for a registration request via a soap interface. When step 200 has been executed, then the control unit performs a step 201.

At a step 201, an external system requests to subscribe by subscribing to an entity position feedback notification receive subscription. When step 201 has been performed, then the control unit executes a step 202.

At a step 202, the terminal control unit determines whether the maximum number of subscription audites notifications has been reached. When the maximum number of notification subscriptions has been reached, then the control unit executes a step 203, otherwise it executes a step 204.

In step 203, the control unit of the terminal informs the external system that the subscription to the notification has been accepted in response to the request. When step 203 has been performed, then the control unit executes a step 205.

At a step 205, the terminal control unit adds the e-mail address of the terminal to a list of notification subscriptions. When step 205 is executed, then the control unit executes step 206.

At a step 206, the control unit of the terminal determines whether there are positions of entities waiting for recovery. When there are entity positions awaiting recovery, then at a step 207, the control unit sends an entity position notification, otherwise, the control unit repeats step 200.

In step 204, the terminal control unit informs the user that the notification subscription has not been accepted, because the maximum number of subscriptions has been reached. When step 204 has been performed, then the control unit repeats step 200.

FIG. 5 is an example of a functional diagram of a method of waiting for a soap request to unsubscribe to the notifications resulting from the geolocation of entities, according to one embodiment of the invention.

At a step 300, the terminal control unit waits for an entity position provided by the location service. When step 300 has been executed, then the control unit performs a step 301.

At a step 301, the terminal control unit receives a soap unsubscribe request upon receipt of entity upstream notification. When step 301 has been performed, then the control unit performs a step 302.

In step 302, the terminal control unit determines whether its e-mail address is known from the subscription list. When the e-mail address is known then, the control unit executes a step 303, otherwise it executes a step 304.

In step 303, the control unit of the terminal informs the external system that unsubscription upon receipt of notification will be performed. When step 303 has been performed, then the control unit performs a step 305.

In step 305, the terminal control unit deletes the e-mail address from the list of notification subscriptions. When step 305 has been executed, then the control unit repeats steps 300 and following.

In step 304, the terminal control unit informs the user that unsubscription is impossible because the e-mail address is unknown. When step 304 is performed, the control unit repeats steps 300 and following.

FIGS. 6 and 7 illustrate an example of a functional diagram of a position injection method with a view to raising the geolocation of entities, according to one embodiment of the invention.

In step 400, the terminal controller expects an entity position provided by the position injection interface. When the control unit has received an entity position, then it executes a step 401.

At a step 401, the control unit of the terminal receives the positions from the position injection interface of each entity, as well as its name, latitude, longitude, speed and direction of movement. When step 401 has been performed, then the control unit executes step 402.

At a step 402, the control unit of the terminal repeats the execution of a sequence of steps, which will be defined subsequently, for each received entity position. Thus, when the control unit reaches the execution of step 402, then it executes a step 403. In step 403, the control unit of the terminal checks whether it has all the necessary parameters in order to determine the latitude and longitude of the entity relative to a predefined PREF reference position. When the control unit has all the parameters necessary to determine the latitude and longitude of the entity with respect to PREF, then the control unit executes a step 404 otherwise, it executes a step 405. At the step 404, the terminal control unit converts the latitude and longitude of the entity into relative position. In step 405, the control unit validates that the position indicator is out of the reference area and approximates the nearest position. In the invention, reference zone is understood to mean a center disk PREF and radius RayPREF, with RayPREF previously defined. When one of steps 404 or 405 has been executed, then the control unit performs a step 406. In step 406, the terminal control unit approximates the speed and direction of movement of the the entity, and then stores the position of the entity in the data memory of the terminal. As long as there is an untreated entity position, then the control unit repeats step 402. When all feature positions have been processed, then the control unit performs a step 407. In step 407, the control unit of the terminal responds to the soap injection request, specifying the list of entities for which a relative position could not be determined. When step 407 has been performed, then the control unit performs a step 408. In step 408, the terminal control unit determines if there is only one relevant position in the position list of entities outside the zone. When there is only one position, then the control unit executes a step 500 otherwise, it executes a step 409.

In step 409, the terminal control unit determines whether the timer for sending ad streams is enabled. If the timer for sending adflows is activated then, a step 600 is executed otherwise, a step 410 is executed.

In step 410, the terminal controller activates the timer for sending adflows. When step 410 has been executed, then the control unit executes step 600.

In step 500, the control unit of the terminal executes a step

501. At step 501, the control unit of the terminal repeats the execution of a sequence of steps, which will be defined subsequently, for each constrained network capable of supporting the collection of entity positions. Thus, when the control unit reaches the execution of step 501, then it executes a step

502. At step 502, the control unit of the terminal asks the exchange platform if it is a relay for the considered network. When step 502 has been executed, then the control unit executes a step

503. In step 503, the control unit of the terminal determines the role of the network referenced "i". When step 503 has been executed, then the control unit executes step 504. In step 504, the terminal control unit determines whether the node is a relay for the concerned "i" network. If the network "i" concerned is not a relay network, then the control unit executes a step 505. In step 505, the control unit of the terminal sends a notification with the positions of the entities, to the different terminal messaging services in the network referenced "i". When step 505 has been executed, then the control unit performs step 510.

In a step 510, the control unit of the terminal injects the positions of entities in the access server to the constrained networks. When step 510 has been executed, then the control unit executes step 409. FIGS. 8 and 9 illustrate an example of a functional diagram of the method of geolocation of entities, according to one embodiment of the invention.

At a step 600, the control unit of the terminal is in a waiting phase of the end of the delay required to perform a position feedback. When step 600 has been performed then, the control unit performs a step 601.

In step 601, the control unit of the terminal determines the timing of the delay. When step 601 has been performed, then the control unit performs a step 602.

In step 602, the control unit of the terminal determines whether entity positions are waiting for recovery. When entity positions are waiting to be raised then, the control unit determines whether the position will be raised by an access server to a constrained network SARC or an access technical center CTA to the IP-WAN network. When an entity position is reassembled by one of the CTA access technical centers, then the control unit executes a step 605. When this position goes back through one of the network access servers constrained by SARC, then the control unit executes a step 700.

In step 605, the control unit of the terminal sends diffuse to the other CTA positions raised by the radio synthesis. When step 605 has been executed, then the control unit performs a step 607.

In step 607, the control unit resets the positions of the entities to go back into its data memory. When step 607 has been performed, then the control unit performs a step 608.

At a step 608, the control unit activates the timer for sending ad streams. When step 608 has been performed, the control unit repeats step 600 and the following steps.

At a step 604, the controller activates the timer for sending ad streams. When step 604 has been performed, the control unit repeats step 600 and the following steps.

In step 700, the control unit of the terminal executes a step 701. In step 701, the control unit of the terminal repeats the execution of a sequence of steps, which will be defined thereafter. for each radio network, ie IP-WAN and / or network constrained. Thus, when the control unit reaches the execution of step 701, then it executes a step 702. In step 702, the control unit asks the exchange platform if it is a relay for the network "i" considered. When step 702 has been executed, then the control unit executes a step 703. In step 703, the control unit of the terminal determines the role of the network referenced "i". When step 703 has been executed, then the control unit performs a step 704. In step 704, the terminal control unit determines whether the network referenced "i" is a PMV2 network. A PMV2 network is a particular type of constrained network, more specifically, it is a particular profile of the PRG4 VS2 station. If the network referenced "i" is a PMV2 network, then the control unit performs a step 705, otherwise it executes a step 706. In the invention, the term PMV2 network (or Mixed Profile Version 2), a network whose profile allows to use both voice and data transmission, but the PMV2 network has the distinction of making the collection.

In step 705, the control unit of the terminal determines if one is relay for the network "i" considered. If the referenced network "i" is not a relay network, then the control unit executes a step 707, otherwise it executes a step 708.

At step 707, the terminal control unit determines whether there is a single loaded position when injecting feature positions. When there is only one position loaded, then the control unit performs a step 712, otherwise it executes a step 709.

In step 708, the control unit of the terminal sends a collection request to the non-relay stations of the network. When step 708 has been executed and step 701 has been repeated for each radio network, then the controller executes step 600, otherwise it repeats step 701.

In step 706, the control unit of the terminal determines whether the network referenced "i" is not a relay network. If the network referenced "i" is not a relay network, then the control unit executes step 709 else it executes a step 710.

In step 709, the control unit sends a message to the other members of the network. If the network "i" is not relayed, then the control unit sends the local positions and the positions received by the lower networks. This program is broadcast to all members of the network, so that all members of the network have the same knowledge.

When step 709 has been executed, then the control unit performs a step 711.

In step 710, the control unit sends a message to the other members of the network. If the network "i" is relayed, then the control unit sends only the local positions injected into the lower networks. This program is broadcast to all members of the network, so that all members of the network have the same knowledge. When step 710 has been performed, then the control unit executes step 711.

In step 711, the control unit sends to all the nodes of the network the message formatted in step 709 or 710, to the different terminal messaging services located in the network referenced "i". When step 711 has been performed, then the control unit executes step 712.

In step 712, the control unit determines whether step 701 has been repeated for each radio network. If step 701 has been repeated for each radio network, then the control unit performs step 713, otherwise it repeats step 701.

In step 713, the control unit resets the entity positions to be transmitted in the data memory. When step 713 has been executed, the control unit performs step 714.

In step 714, the control unit activates the delay necessary for sending ad streams. When step 714 has been executed, the control unit executes step 600.

FIG. 10 illustrates an example of a functional diagram of a method for receiving positions with a view to raising the geolocation of entities, according to one embodiment of the invention.

At a step 800, the control unit of the terminal waits, on the one hand, for the reception of positions via a network by the location service and, on the other hand, the end of the delay necessary for the reassembly of the position. When step 800 has been executed, then the control unit executes a step 801. In step 801, the terminal control unit receives a message containing positions from a CTA or a SARC. When step 801 has been performed, then the control unit performs a step 802.

In step 802, the control unit of the terminal calculates absolute positions of each entity based on the positions from the geolocation service. When step 802 has been performed, then the control unit performs a step 803.

In step 803, the terminal control unit performs a step 804 for each subscriber in the list of entity position notification subscriptions. In step 804, the control unit notifies entity positions to the different subscribers. When step 803 has been reiterated for each e-mail address of the subscription list, then the control unit performs a step 805.

In step 805, the control unit determines whether the received positions have been issued by a SARC or CTA. When the received positions have been issued by a SARC, then the control unit performs a step 806, otherwise it executes a step 807.

In step 806, the control unit of the terminal stores the relative positions in its data memory. When step 806 has been performed, then the control unit performs a step 808.

In step 808, the control unit determines whether the timing for sending ad streams is enabled. When the delay for sending adflows is enabled, then the control unit executes a step 900, otherwise it executes a step 809.

In step 809, the controller activates the timer for sending adflows. When step 809 has been performed, then the control unit executes step 900.

In step 807, the control unit determines whether the timing for sending ad streams is enabled. When the timing for sending adflows is turned on, then the control unit executes step 900, otherwise it executes step 400.

In step 900, the control unit waits for the end of the time delay necessary for the reassembly of the position of entities. When step 900 has been executed, then the control unit performs a step 901.

In step 901, the control unit receives a geolocation service summary message containing the symbolic address of the entity, as well as than the network where the entity is located. When step 901 has been executed, then the control unit performs a step 902.

In step 902, the control unit of the terminal calculates absolute positions. When step 902 has been performed, then the control unit performs a step 903.

In step 903, the terminal control unit performs a step 904 for each e-mail address that is in the list of entity position notification subscriptions. In step 904, the control unit notifies entity locations to the different e-mail addresses of said subscription list. When step 903 has been repeated for each e-mail address of the subscription list, then the control unit executes a step 905.

In step 905, the control unit performs a formatting of an XSMTP message containing both the positions of the entities collected in the network "i", but also the positions of the entities relayed in the networks of lower levels. When step 905 has been performed, then the control unit performs a step 906.

In step 906, the control unit of the terminal sends the formatted message in step 905 to the different terminal messaging services in the network referenced "i", excluding the original network of the entity. When step 906 has been performed, then the control unit performs a step 907.

In step 907, the control unit resets the feature positions in the data memory. When step 907 has been executed, the control unit performs a step 908.

In step 908, the control unit activates the delay necessary for sending ad streams. When step 908 has been executed, the control unit executes step 900.

Claims

1 - Hierarchical method of hierarchical geolocation of entities characterized in that it comprises the following steps:

- we wait for a request for registration of each terminal via a soap interface,

an email address of each terminal is added to a list of notification subscriptions,

- it is determined whether there are positions of entities waiting for recovery,

- when there are positions of entities waiting for reassembly, we send an entity position notification,

- the timer is activated for sending an ad stream,

- we determine the role of a network "i", in other words, whether it is a relay or not for the network

if it is not a relay for the network, then a notification is sent with the positions of the entities, to the different terminal messaging services located in the network referenced "i",

when entity positions are waiting to be raised then, it is determined whether the position will be raised by an access server to a constrained network SARC or an access technical center CTA to the IP-WAN network,

- When a position goes up through one of the network access servers constrained by SARC, then the other CTAs are broadcast the positions reported by the radio synthesis.

2 - Process according to claim 1, characterized in that one receives entity positions from the position injection interface of each entity, as well as its name, latitude, longitude, speed and direction of movement.

3 - Process according to claim 2, characterized in that one has all the necessary parameters to determine the latitude and longitude of the entity with respect to a reference position (PREF),

4 - Process according to claim 3, characterized in that one converts the latitude and longitude of the entity in relative position. 5 - Process according to claim 2, characterized in that it validates the fact that the position indicator of the entity is out of reference area and an approximation is made of the nearest position.

6 - Process according to claim 5, characterized in that one approximates the speed and direction of movement of the entity, then stores the position of the entity in the data memory of the terminal.