Transmission process, process implemented by a relay, process implemented by a terminal, process implemented by a server device, information storage medium, communication system, relay, terminal, and server device.

Abstract

An LPWAN type communication system includes a server device (130), at least one gateway (120, 121, 122) and at least one transmitter (100). Each gateway communicates with terminals (110, 111, 112, 113) using a class A communication mode, in which any response destined for a terminal uses a reception window defined in relation to the transmission time of an originating message by said terminal. Each relay (100) is seen as a terminal by each gateway, and communicates with terminals according to a class A' communication mode, defined as follows: the relay transmits beacons at regular intervals and listens to terminals only during time intervals defined in relation to said beacons.In this 'class a' communication mode, the relay propagates any response destined for a terminal using at least one other reception window defined in relation to the transmission time of an originating message by said terminal.

Description

1 / 62 Descriptive Report of the Invention Patent for TRANSMISSION PROCESS, PROCESS IMPLEMENTED BY A RETRANSMITTER, PROCESS IMPLEMENTED BY A TERMINAL, PROCESS IMPLEMENTED BY A SERVER EQUIPMENT, INFORMATION STORAGE SUPPORT, COMMUNICATION SYSTEM, RETRANSMITTER, TERMINAL AND SERVER EQUIPMENT.

[0001] The present invention relates to a relay mechanism between one or more terminals and one or more gateways in an LPWAN (Low-Power Wide-Area Network) type communication system.

[0002] The Internet of Things (IoT) emerges. The Internet of Things represents the extension of the Internet to things and places in the physical world. While the Internet does not usually extend beyond the electronic world, the Internet of Things represents the exchange of information and data from devices in the real world to the Internet, such as collecting measurements of gas or water consumption, or collecting measurements from sensors in general. The Internet of Things is considered the third evolution of the Internet, dubbed Web 3.0. The Internet of Things has a universal character to designate communicating objects, called connected objects, with varied uses, for example in the industrial, agri-food, e-health or home automation fields.These connected objects are typically low-power terminals, in standby mode most of the time, and which wake up occasionally to collect data (sensors) and transmit it via radio.

[0003] In the context of the Internet of Things, gateways located at geographically high points are deployed due to a Petition 870240099175, dated 11 / 21 / 2024, page 6 / 166 2 / 62 service operator, in order to create a network infrastructure to allow these connected objects to communicate. Except for maintenance operations, these gateways are typically fixed and permanent. Examples of this model include SigFox (trademark filed) or ThingPark (trademark filed). These gateways communicate with connected objects thanks to medium or long-range wireless communication systems of the LPWAN type, such as LoRaWAN technology (trademark filed, Long Range Wide-Area Network), also known by the abbreviation LoRa (trademark filed, Long Range) from the name of the alliance that promotes extended long-range network technologies.These gateways allow these connected objects to communicate with a server (main network), called an LNS (for LoRa Network Server, according to LoRaWAN technology terminology), typically to retrieve data collected by said connected objects. The gateways communicate with the LNS server thanks to a network infrastructure, typically wired, adapted to support the load of data traffic exchanged between said connected objects, said gateways, and the LNS server. It should be noted that the exchanges between the gateways and the LNS server generally use a proprietary protocol specific to the service provider (non-standardized) based on the IP protocol (Internet Protocol, as defined in the RFC 791 normative document).

[0004] One problem faced by the service operator is that certain connected objects may be out of range of the LPWAN communication system radio. This may be due to the fact that a previously installed gateway was disconnected for maintenance or that a given geographical area is not yet covered. Petition 870240099175, dated 11 / 21 / 2024, page 7 / 166 3 / 62 for the deployment of service provider gateways. The installation of a gateway is chronophagic, as the operation of such a gateway (permanently listening to the medium) requires a power supply per sector. It is therefore desirable to provide a solution that allows for the rapid and low-cost correction of a radio range defect in the LPWAN communication system, so as to allow connected objects that are out of radio range of the gateways already present in the LPWAN communication system to benefit from the services of said communication system. It is particularly desirable to provide a solution that is energy-efficient, especially compared to the gateways of the LPWAN communication system. On the other hand, it is desirable to provide a solution that is ready for use (Plug and Play).

[0005] To do this, the invention relates to a transmission process in a communication system that includes a server device and at least one gateway connected to the server device, each gateway being configured to communicate with at least one terminal via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: said gateway receives a source message from said terminal and propagates said received source message to the server device; upon receiving a reply message from the server device, said gateway propagates the reply message to said terminal using at least one reception window defined in relation to a transmission time of said source message by said terminal.The process is such that the communication system includes, on the other hand, at least one relay viewed as a terminal for each gateway, each relay using Class A communication mode to communicate with one or more said gateways, and that... Petition 870240099175, dated 11 / 21 / 2024, p. 8 / 166 4 / 62 uses another communication mode, referred to as 'Class A', to communicate with one or more terminals, defined as follows: the relay transmits beacons at regular intervals, each beacon including information representative of at least one predefined time interval in relation to said beacon; the relay listens for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;In the event of a response message from the server equipment provided via said gateway in Class A communication mode, said relay propagates the response message to said terminal using at least one other reception window defined in relation to the transmission time of said source message by said terminal, each said other reception window being subsequently offset by a predefined time in relation to each reception window defined in Class A communication mode. Furthermore, upon receiving by said relay a source message emitted by said terminal in Class A communication mode, said relay performs the following steps: encapsulates the source message in another message destined for the server equipment; transmits said other message in Class A communication mode, so that at least one said gateway propagates said other message to the server equipment;In the event of a response message from the server equipment provided via said gateway that uses a reception window defined in Class A communication mode in relation to the transmission of said other message by said relay, perform a decapsulation of another response message contained within said response message and propagate said other response message to said terminal in said other reception window defined in mode; Petition 870240099175, dated 11 / 21 / 2024, page 9 / 166 5 / 62 of Class A communication in relation to the transmission of said originating message by said terminal. On the other hand, upon receiving a message propagated by one or more gateways, when the received message includes a message retransmitted by said retransmitter, the server equipment performs the following steps: decapsulate the retransmitted message; process the retransmitted message in order to obtain a response message to be addressed to the terminal that issued the retransmitted message; encapsulate the response message in another response message to be addressed to the retransmitter; and transmit said other response message to a gateway, so that said gateway propagates said other response message to said retransmitter in said reception window defined in Class A communication mode in relation to the transmission by said terminal of said propagated message.

[0006] Thus, a radio range defect in the LPWAN type communication system is corrected, so as to allow terminals (connected objects) that are out of radio range of the gateways already present in the LPWAN type communication system to benefit from the services of said communication system. This benefit is achieved at low cost, since the repeater can be in stand-by most of the time, thanks especially to the definition of the communication mode in Class A'.

[0007] According to a special embodiment, each relay is initialized as follows: said relay transmits a registration message to the server equipment; in the event of a response message from the server equipment provided via said gateway, the relay transmits a beacon parameter recovery message to the server equipment; in the event of a response message from Petition 870240099175, dated 11 / 21 / 2024, page 10 / 166 6 / 62 server equipment provided via said gateway, the relay programmed to send said beacons and programmed to listen during each said time interval, said response message including representative information for each said time interval.

[0008] Thus, the repeater is ready for use and the radio range of the LPWAN type communication system can be quickly extended.

[0009] According to a special embodiment, upon receiving by said relay a source message emitted by said terminal in Class A communication mode, the relay performs the following steps: when the source message is a register message from said terminal destined for the server equipment, said relay propagates said source message to the server equipment, and upon receiving a reply message from the server equipment, said relay considers said terminal to be connected to said relay; when the source message is another message, said relay propagates said source message to the server equipment only if said terminal is connected to said relay.

[0010] Thus, exchanges are limited in the case of the presence of several relays that would use the same time slots to listen for any messages to be relayed to the server equipment, thus preventing each relay from being responsible for propagating these potential messages. This, on the other hand, helps preserve the energy autonomy of the relays.

[0011] According to a special embodiment, with the reception of a message propagated by one or more gateways, when the received message includes a message retransmitted by said retransmitter, the server equipment determines whether the Petition 870240099175, dated 11 / 21 / 2024, page 11 / 166 7 / 62 The retransmitted message was also received directly via at least one said gateway, and if this is the case, the server equipment performs the following steps: process the retransmitted message in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted; transmit said reply message to a gateway, so that said gateway propagates said reply message to said terminal in said reception window defined in Class A communication mode in relation to the transmission by said terminal of the message that was retransmitted; transmit to the relay a disconnection message indicating to said relay that said terminal is no longer connected to said relay.Furthermore, the terminal is listening in each said reception window defined in Class A communication mode and in each said reception window defined in Class A communication mode', and when said terminal receives a reply message in said reception window defined in Class A communication mode, said terminal switches to Class A communication mode.

[0012] Thus, it is prevented that a relay continues to propagate messages transmitted by a terminal, while said terminal is henceforth within range of at least one gateway of the communication system.

[0013] According to a special embodiment, two reception windows are defined in Class A communication mode and two reception windows are defined in Class A communication mode'.

[0014] According to a special embodiment, each reception window in Class A communication mode has a longer duration than each corresponding reception window in Class A communication mode.

[0015] Thus, it is possible to use relays that have a Petition 870240099175, dated 11 / 21 / 2024, page 12 / 166 8 / 62 clock accuracy is lower than that of communication system gateways, and clock quality degradations due to successive synchronizations are taken into account.

[0016] According to a special embodiment, the server equipment comprises at least one relay application, each relay application being responsible for carrying out the encapsulations and decapsulations in relation to one or more said relays.

[0017] Thus, the server equipment architecture is simple.

[0018] The invention also relates to a process, implemented by a relay, within the scope of a transmission in a communication system that includes a server equipment and at least one gateway connected to the server equipment, each gateway being configured to communicate with at least one terminal via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: said terminal that wishes to communicate with the server equipment directly via said gateway transmits a source message destined for the server equipment; said terminal is listening for a possible reply message from the server equipment propagated via said gateway during at least one reception window defined in relation to a transmission time of said source message by said terminal.Furthermore, the communication system also includes said relay, which is seen as a terminal by each gateway, said relay using Class A communication mode to communicate with one or more said gateways, and using to communicate with one or more said gateways, and using to communicate with one or more terminals another communication mode, said to be 'Class A', defined as follows: the relay transmits beacons at regular intervals, each beacon including information. Petition 870240099175, dated 11 / 21 / 2024, p. 13 / 166 9 / 62 representative of at least one predefined time interval in relation to said benchmark; the relay is listening for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;In the event of a response message from the server equipment provided via said gateway in Class A communication mode, said relay propagates the response message to said terminal using at least one other reception window defined in relation to the transmission time of said source message by said terminal, each said other reception window being subsequently offset by a predefined time in relation to each reception window defined in Class A communication mode. Furthermore, upon receiving by said relay a source message emitted by said terminal in Class A communication mode, said relay performs the following steps: encapsulates the source message in another message destined for the server equipment; transmits said other message in Class A communication mode, so that at least one said gateway propagates said other message to the server equipment;In the event of a response message from the server equipment provided via said gateway that uses a reception window defined in Class A communication mode relative to the transmission of said other message by said relay, perform a decapsulation of another response message contained within said response message and propagate said other response message to said terminal in said other reception window defined in Class A communication mode relative to the transmission of said original message by said terminal.

[0019] The invention also relates to a process, implemented Petition 870240099175, dated 11 / 21 / 2024, page 14 / 166 10 / 62 by a terminal, within the scope of a transmission in a communication system that includes a server device and at least one gateway connected to the server device, said terminal being configured to communicate with at least one said gateway via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: said terminal that wishes to communicate with the server device directly via said gateway transmits a source message destined for the server device;The said terminal is listening for a possible reply message from the server equipment propagated via said gateway during at least one reception window defined in relation to a transmission time of said originating message by said terminal. Furthermore, the communication system, including on the other hand at least one relay, the said terminal is configured to communicate with each relay according to another communication mode, said to be 'Class A', defined as follows: the terminal receives beacons emitted by said relay, each beacon including information representative of at least one predefined time interval in relation to said beacon; said terminal that wishes to communicate with the server equipment via said relay transmits an originating message destined for the server equipment, only during said time interval;and said terminal is listening for a possible reply message from the server equipment propagated via said relay during at least one other reception window defined in relation to the transmission time of said original message by said terminal, each said other reception window being subsequently offset by a predefined time in relation to each reception window defined in Class A communication mode.

[0020] The invention also relates to a process, implemented Petition 870240099175, dated 11 / 21 / 2024, page 15 / 166 11 / 62 by a server device, within the scope of a transmission in a communication system that includes said server device and at least one gateway connected to the server device, each gateway being configured to communicate with at least one terminal via an LPWAN type communication network.The process is such that, in a communication system that includes at least one relay, upon receiving a message propagated by one or more gateways, when the received message includes a message relayed by said relay, the server equipment performs the following steps: decapsulates the relayed message; processes the relayed message in order to obtain a reply message to be addressed to the terminal that issued the relayed message; encapsulates the reply message in another reply message to be addressed to the relay; and transmits said other reply message to a gateway, so that said gateway propagates said other reply message to said relay.

[0021] The invention also relates to a communication system that includes a server device, each gateway being configured to communicate with at least one terminal via an LPWAN-type communication network that uses a Class A communication mode, defined as follows: said gateway is configured to receive a source message from said terminal and propagates said received source message to the server device; upon receiving a reply message from the server device, said gateway is configured to propagate the reply message to said terminal using at least one reception window defined in relation to the transmission time of said source message by said terminal. Furthermore, the communication system includes Petition 870240099175, dated 11 / 21 / 2024, page 16 / 166 12 / 62 on the other hand, at least one relay is considered a terminal for each gateway, each relay being configured to use Class A communication mode to communicate with one or more said gateways, and to use another communication mode, said to be 'Class A', defined as follows, to communicate with one or more terminals: the relay is configured to transmit beacons at regular intervals, each beacon including representative information for at least one predefined time interval relative to said beacon; the relay is configured to listen for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;In the event of a response message from the server equipment provided via said gateway in Class A communication mode, said relay is configured to propagate the response message to said terminal using at least one other reception window defined in relation to the transmission time of said source message by said terminal, each said other reception window being subsequently offset by a predefined time in relation to each reception window defined in Class A communication mode. Furthermore, upon receiving a source message emitted by said terminal in Class A communication mode, said relay implements: means to encapsulate the source message within another message destined for the server equipment;means to transmit said other message in Class A communication mode, such that at least one said gateway propagates said other message to the server equipment; in the case of a response message from the server equipment provided via said gateway that uses for this purpose a reception window defined in Class A communication mode in relation to the transmission of the message; Petition 870240099175, dated 11 / 21 / 2024, page 17 / 166 13 / 62 said another message by said relay, means to effect a decapsulation of another reply message contained in said reply message and means to propagate said other reply message to said terminal in said other reception window defined in Class A communication mode in relation to the transmission of said source message by said terminal.Furthermore, upon receiving a message propagated by one or more gateways, when the received message includes a message retransmitted by said retransmitter, the server equipment implements: means to decapsulate the retransmitted message; means to process the retransmitted message in order to obtain a reply message to be addressed to the terminal that issued the retransmitted message; means to encapsulate the reply message in another reply message to be addressed to the retransmitter; and means to transmit said other reply message to a gateway, so that said gateway propagates said other reply message to said retransmitter in said reception window defined in Class A communication mode with respect to the transmission by said terminal of said propagated message.

[0022] The invention also relates to a relay intended for use in a communication system that includes a server and at least one gateway connected to the server, each gateway being configured to communicate with at least one terminal via an LPWAN-type communication network that uses a Class A communication mode, defined as follows: the terminal wishing to communicate directly with the server via the gateway is configured to transmit a message from the server; the terminal is configured to be listening. Petition 870240099175, dated 11 / 21 / 2024, page 18 / 166 14 / 62 of any response message from the server equipment propagated via said gateway during at least one reception window defined in relation to a transmission time of said source message by said terminal. Furthermore, said relay being seen as a terminal by each gateway, said relay is configured to use Class A communication mode to communicate with one or more said gateways, and to use another communication mode, said 'Class A', defined as follows, to communicate with one or more terminals: the relay is configured to transmit beacons at regular intervals, each beacon including information representative of at least one predefined time interval in relation to said beacon; the relay is configured to listen for any source messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;In the event of a response message from the server equipment provided via said gateway in Class A communication mode, said relay is configured to propagate the response message to said terminal using at least one other reception window defined in relation to the transmission time of said source message by said terminal, each said other reception window being subsequently offset by a predefined time in relation to each reception window defined in Class A communication mode. Furthermore, upon receiving by said relay a source message emitted by said terminal in Class A communication mode, said relay implements: means to encapsulate the source message in another message destined for the server equipment; means to transmit said other message in Class A communication mode, so that at least one said gateway propagates it; Petition 870240099175, dated 11 / 21 / 2024, p. 19 / 166 15 / 62 says another message to the server equipment; in the case of a reply message from the server equipment provided via said gateway that uses for this purpose a reception window defined in Class A communication mode in relation to the transmission of said other message by said relay, means to effect a decapsulation of another reply message contained in said reply message and means to propagate said other reply message to said terminal in said other reception window defined in Class A communication mode in relation to the transmission of said source message by said terminal.

[0023] The invention also relates to a terminal intended for use with a communication system that includes a server device and at least one gateway connected to the server device, said terminal being configured to communicate with at least one said gateway via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: said terminal that wishes to communicate with the server device directly via said gateway is configured to transmit a source message destined for the server device; said terminal is configured to listen for any response message from the server device propagated via said gateway during at least one reception window defined in relation to a transmission time of said source message by said terminal.Furthermore, the communication system, including on the other hand at least one relay, said terminal is configured to communicate with each relay in accordance with another communication mode, said to be 'Class A', defined as follows: the terminal is configured to receive beacons, emitted by said relay, each beacon including representative information for at least a predefined time interval in relation to said beacon; Petition 870240099175, dated 11 / 21 / 2024, page 20 / 166 16 / 62 said terminal that wishes to communicate with the server equipment via said relay is configured to transmit a source message to the server equipment only during said time interval; said terminal is configured to listen for any response message from the server equipment propagated via said relay during at least one other reception window defined in relation to a transmission time of said source message by said terminal, each said other reception window being subsequently deferred by a predefined time in relation to each reception window defined in Class A communication mode.

[0024] The invention also relates to a server equipment intended for use in a communication system that includes said server equipment and at least one gateway connected to the server equipment, each gateway being configured to communicate with at least one terminal via an LPWAN type communication network.The communication system, including on the other hand at least one relay, with the reception of a message propagated by one or more gateways, when the received message includes a message retransmitted by said relay, the server equipment implements: means to effect a decapsulation of the retransmitted message; means to process the retransmitted message in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted; means to effect a encapsulation of the reply message in another reply message to be addressed to the relay; and means to transmit said other reply message to a gateway, in order that said gateway propagates said other reply message to said relay.

[0025] The invention also relates to a program of Petition 870240099175, dated 11 / 21 / 2024, page 21 / 166 17 / 62 computer, which can be stored on a medium and / or loaded from a communication network in order to be read by a processor. This computer program comprises instructions for implementing the aforementioned process with respect to the relay or the aforementioned process with respect to the terminal or the aforementioned process with respect to the server equipment, when said program is executed by the processor. The invention also relates to a means of storing information that stores such a computer program.

[0026] The features of the invention mentioned above, as well as others, will become clearer upon reading the following description of an embodiment, said description being made in relation to the accompanying drawings, among which:

[0027] - Figure 1 schematically illustrates a communication system that includes a server device, at least one gateway, at least one relay device, and at least one terminal;

[0028] - Figure 2 schematically illustrates an example of the material architecture of said retransmitter and / or server equipment;

[0029] - Figures 3A to 3E schematically illustrate communication sequences within the communication system of Figure 1;

[0030] - Figure 4 schematically illustrates an algorithm, implemented by each relay, for initializing said relay;

[0031] - Figure 5 schematically illustrates an algorithm, implemented by each terminal, for registering said terminal with the server equipment;

[0032] - Figure 6 schematically illustrates an algorithm, implemented by each terminal, for transmitting data to Petition 870240099175, dated 11 / 21 / 2024, page 22 / 166 18 / 62 server equipment;

[0033] - Figure 7 schematically illustrates an algorithm, implemented by each retransmitter, for propagating data to the server equipment;

[0034] - Figure 8 schematically illustrates an algorithm, implemented by the server equipment, to register each retransmitter at the time of initialization of said transmitter;

[0035] - Figure 9 schematically illustrates an algorithm, implemented by the server equipment, to handle a first type of retransmitted message;

[0036] - Figure 10 schematically illustrates an algorithm, implemented by the server equipment, to handle a second type of retransmitted message; and

[0037] - Figure 11 schematically illustrates an example of message exchanges within the communication system, in application of a mode of embodiment of the present invention.

[0038] The invention is more specifically described below within the context of a LoRaWAN type network infrastructure (registered trademark), notably using terminology found in the LoRaWAN specifications (registered trademark). The principles and implementations described below, however, apply more generally to an LPWAN type network infrastructure context.

[0039] Furthermore, the invention is more specifically described below using two Class A transmission mode reception windows, as in the LoRaWAN specifications (trademark filed). However, it is worth noting that a different number of Class A transmission mode reception windows can be used, and notably only one Class A transmission mode reception window. Petition 870240099175, dated 11 / 21 / 2024, page 23 / 166 19 / 62

[0040] Figure 1 schematically illustrates a communication system in which the present invention is implemented.

[0041] The communication system comprises a plurality of GW gateways, which have respective communication links with a SERV 130 server equipment to which said gateways are connected. According to a special embodiment, each GW gateway integrates an Internet access function and the communication link between said gateway and the SERV 130 server equipment relies on the IP protocol. For illustrative purposes, it will be considered that the communication system comprises three GW gateways 120, 121, 122.

[0042] In the communication system, messages must be carried to the SERV 130 server equipment in the form of frames from each EP (End-Point) terminal of a set of EP terminals in said communication system. For illustrative purposes, it will be considered that the communication system comprises four EP terminals 110, 111, 112, 113.

[0043] To enable EP terminals to communicate indirectly with the SERV 130 server equipment, each GW gateway comprises a radio interface that allows said gateway to communicate with said EP terminals by relying for this purpose on a wireless communication network, and preferably in accordance with an LPWAN type communication technology (provided that the radio range of the communication technology allows it). Said radio interface is preferably of the LoRa type (trademark filed) which thus allows the implementation, within the communication system, of a LoRaWAN type data transmission protocol (trademark filed).

[0044] To correct a possible lack of radio range of the LPWAN type communication technology, notably when one or more GW gateways are under maintenance or waiting for the Petition 870240099175, dated 11 / 21 / 2024, p. 24 / 166 20 / 62 Once the deployment of the GW gateways is complete, the communication system includes one or more RL repeaters. For illustrative purposes, Figure 1 will consider that the communication system includes a single RL 100 repeater.

[0045] The RL 100 repeater is therefore intended to be interposed between one or more EP terminals and one or more GW gateways of the communication system. The RL 100 repeater therefore uses the same physical communication layer as the EP terminals and GW gateways use to communicate with the EP terminals and the GW gateways. As detailed below, however, access to the communication medium is different when the RL 100 repeater intervenes in communications between the EP terminals and the SERV 130 server equipment.

[0046] The RL 100 repeater is a sleeping device. This means that the RL 100 repeater is in standby mode except in the following situations: - during predetermined time intervals during which the RL 100 relay station must transmit beacons, as well as time periods necessary for the management of said beacons; - during predetermined time intervals in which one or more EP terminals are authorized to transmit messages to be retransmitted by the RL 100 retransmitter, as well as during time periods necessary for the management of said messages; - during predetermined time intervals during which the RL 100 relay is authorized to send replies to messages transmitted by one or more EP terminals and which the RL 100 relay has retransmitted, as well as time periods necessary for managing said replies; - at predetermined time intervals during which the RL 100 relay must transmit messages. Petition 870240099175, dated 11 / 21 / 2024, page 25 / 166 21 / 62 destined for the SERV 130 server equipment, as well as the time periods necessary for managing said messages; - during predetermined time intervals in which any of the gateways GW 120, 121, 122 is authorized to send replies to messages sent by the relay RL 100 destined for the server equipment SERV 130, as well as during time periods necessary for the management of said replies; and - on the occasion of other predetermined treatments under the responsibility of the RL 100 transmitter.

[0047] In fact, the RL 100 repeater is designed to correct, at a lower cost, the absence of a GW gateway to cover a geographical area where EP terminals are located (or potentially located). The RL 100 repeater is in this case powered autonomously, by battery or solar panel, and conserves its energy, only waking up when necessary to perform the relay between one or more EP terminals and the rest of the communication system (or when necessary to perform other predetermined treatments for which the RL 100 repeater is responsible). To be able to remain in standby mode as much as possible, the RL 100 repeater applies, in its indirect communications with the SERV 130 server equipment (and therefore via one or more GW gateways), a first communication mechanism described below in relation to Figures 3A and 3B.This first communication mechanism corresponds to the communication mode, known as Class A, in the LoRaWAN data transmission protocol (registered trademark). In addition, the RL 100 repeater applies, in its communications with any EP equipment, a second communication mechanism described below in relation to Figures 3C, 3D, and 3E. This second communication mechanism is therefore a different one. Petition 870240099175, dated 11 / 21 / 2024, page 26 / 166 22 / 62 communication mode, referred to as 'Class A', is different from the communication mode in Class A (as well as the communication mode referred to as Class B, in the LoRaWAN type data transmission protocol (trademark registered), even if the 'Class A' communication mode also relies on beacon transmissions). In order to allow for the placement of these communication mechanisms, the RL 100 repeater is initialized as described below in relation to Figure 4.

[0048] In a special embodiment of the SERV 130 server equipment, the SERV 130 server equipment includes an LNS 131 server that has a control and information gathering role with the EP 110, 111, 112, 113 terminals via the GW 120, 121, 122 gateways. The SERV 130 server equipment also includes one or more EPA 133 terminal applications, responsible for processing the information collected by the LNS 131 server from the EP 110, 111, 112, 113 terminals and for sending responses (which include data confirmations and potentially commands) to the EP 110, 111, 112, 113 terminals. The same EPA 133 terminal application can handle one or more EP terminals.Furthermore, in order to account for the presence of the RL 100 relay and to make it transparent to gateways 120, 121, and 122, the SERV 130 server equipment includes one or more RLA relay applications responsible for performing encapsulation and decapsulation operations, as explained below, particularly in relation to Figures 9 and 10. The same RLA relay application can handle one or more RL relays. The LNS 131 server is in this case responsible for managing data and information transfers within the SERV 130 server equipment, especially in relation to the EPA 133 terminal application and the RLA relay application. Petition 870240099175, dated 11 / 21 / 2024, page 27 / 166 23 / 62 132.

[0049] It should be noted that the SERV 130 server equipment may consist of a single machine or a set of interconnected machines. Notably, the SERV 130 server equipment may be such that the LNS server 131 and the RLA relay application 132 on the one hand, and the EPA terminal applications 133 on the other hand, are implemented by distinct machines.

[0050] An example of material architecture applicable to RL repeaters, EP terminals and SERV 130 server equipment is schematically illustrated in Figure 2. The case of the RL 100 repeater will be considered for illustrative purposes.

[0051] The RL 100 repeater in this case comprises, connected by a communication bus 220: a processor or CPU (Central Processing Unit) 210; a RAM (Random Access Memory) 212; a ROM (Read Only Memory) 212; a storage unit or a storage media reader, such as an SD (Secure Digital) card reader 213; and a COM communication interface 214. The COM communication interface 214 allows the RL 100 repeater to communicate with one or more GW gateways, as well as with any one or more EP terminals that implement LPWAN type communication technology.

[0052] When the material architecture example represents the SERV 130 server equipment, the storage unit 213 is preferably one or more HDD (Hard Disc Drive) hard disks. Furthermore, the COM 214 communication interface notably allows the SERV 130 server equipment to communicate with each of the GW 120, 121, and 122 gateways.

[0053] When the material architecture example represents an EP terminal, the COM 214 communication interface allows in this case Petition 870240099175, dated 11 / 21 / 2024, p. 28 / 166 24 / 62 notably that said EP terminal communicates in accordance with LPWAM type communication technology (in order to communicate).

[0054] Processor 210 is capable of executing instructions loaded into RAM 211 from ROM 212, external memory, storage media, or a communication network. When the relay RL 100 is energized, processor 210 is able to read instructions from RAM 212 and execute them. These instructions form a computer program that causes processor 210 to implement all or part of the algorithms and steps described here in relation to the relay RL 100 in question. This principle applies analogously to each EP terminal and the server equipment SERV 130.

[0055] Thus, all or part of the algorithms and steps described here can be implemented in software form by executing a set of instructions on a programmable machine, such as a DSP (Digital Signal Processor) or a microcontroller. All or part of the algorithms and steps described here can also be implemented in physical form by a dedicated machine or component, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit).

[0056] Figures 3A to 3E schematically illustrate communication sequences within the context of access to the communication medium according to LPWAN technology within the communication system.

[0057] Figure 3A schematically illustrates a communication sequence, applied when an EP terminal wishes to transmit a registration request message, called JOIN_REQUEST (JR), to the SERV 130 server equipment, communicating directly with one or more GW gateways for this purpose. Petition 870240099175, dated 11 / 21 / 2024, page 29 / 166 25 / 62 It should be noted that the uplink can be performed via multiple GW gateways that receive the JOIN_REQUEST message in parallel, while the SERV 130 server equipment chooses one GW gateway to perform the downlink. When the EP terminal wishes to transmit such a JOIN_REQUEST message, said EP terminal has access to the communication medium after waiting for a random (limited) amount of time to elapse. The said EP terminal thus transmits its JOIN_REQUEST message, which defines a first reception window Rx1 and a second reception window Rx2. In response to the JOIN_REQUEST message, the EP terminal is supposed to receive a reply message, called JOIN_ACCEPT, in the first reception window Rx1 or in the second reception window Rx2. This allows the EP terminal to go into standby mode after sending the JOIN_REQUEST message and know exactly when to wake up to receive a possible reply to the JOIN_REQUEST message.The first reception window Rx1 is defined at a time Δ1 relative to the sending of the JOIN_REQUEST message, and the second reception window Rx2 is defined at a time Δ2 relative to the first reception window Rx1. For example, Δ1 is 5 seconds and Δ2 is 1 second. The first reception window Rx1 and the second reception window Rx2 are preferably the same size.

[0058] The communication sequencing shown in Figure 3A is also used by any RL relay to itself transmit a JOIN_REQUEST message to the SERV 130 server equipment, communicating for this purpose with one or more GW gateways.

[0059] Figure 3B schematically illustrates a communication sequencing, applied when an EP terminal wishes to transmit a service message MSG to the SERV 130 server equipment, communicating for this purpose directly with one or more GW gateways. A service message MSG is a message of any type Petition 870240099175, dated 11 / 21 / 2024, p. 30 / 166 26 / 62 transmitted upwards by the EP terminal after registration with the SERV 130 server equipment (i.e., outside the message). (JOIN_REQUEST). When the EP terminal wishes to transmit such a service message (MSG), the said EP terminal has access to the communication medium after waiting for a random (limited) amount of time to elapse. The said EP terminal thus transmits its service message (MSG), which defines the first reception window Rx1 and the second reception window Rx2. In response to the service message (MSG), the EP terminal is assumed to receive a reply message in the first reception window Rx1 or in the second reception window Rx2. This allows the EP terminal to go into standby mode after sending the service message and know exactly when to wake up to receive a possible reply to said service message.What differs from Figure 3A is that the first reception window Rx1 is defined at a time Δ3 < Δ1 relative to the sending of the service message MSG, while the second reception window Rx2 remains defined at a time Δ2 relative to the first reception window Rx1. For example, Δ3 equals 1 second. It is indeed considered that the treatments implied by a JOIN_REQUEST message are more chronophagic than those implied by a service message.

[0060] The communication sequencing shown in Figure 3B is also used by any RL relay to transmit a service message MSG (notably with regard to messages that encapsulate messages initially transmitted by an EP terminal for which said RL relay is responsible, as detailed below) to the SERV 130 server equipment, communicating for this purpose with one or more GW gateways.

[0061] The communication sequences shown in Figures 3A and 3B thus define the Class A communication mode. Petition 870240099175, dated 11 / 21 / 2024, p. 31 / 166 27 / 62 already mentioned. A larger number of receiving windows can be used. A single receiving window can also be used.

[0062] It will be considered by way of illustration within the scope of the Figures 3C, 3D and 3E indicate that the communication system comprises only a single RL repeater, namely the RL 100 repeater.

[0063] Figure 3C schematically illustrates a communication sequence applied when an EP terminal wishes to transmit a JOIN_REQUEST message to the SERV 130 server equipment, relying on the RL 100 repeater. When the EP terminal wishes to transmit such a JOIN_REQUEST message, it has access to the communication medium within a predetermined time interval, as described below in relation to Figure 3E. The EP terminal then transmits its JOIN_REQUEST message, which defines the first reception window Rx1 and the second reception window Rx2, as already described in relation to Figure 3A. The definition of the first reception window Rx1 and the second reception window Rx2 allows the EP terminal to detect when it no longer needs to rely on the RL 100 repeater to communicate with the SERV 130 server equipment, as detailed below in relation to Figures 6, 10, and 11.When the aforementioned EP terminal transmits its JOIN_REQUEST message, this also defines a third reception window Rx'1 and a fourth reception window Rx'2. The third reception window Rx'1 is defined at a time Δ4 > Δ1 relative to the first reception window Rx1, and the fourth reception window Rx'2 is defined at a time Δ2 relative to the third reception window Rx'1. It should be noted, therefore, that the time Δ4 is ​​typically greater than the time Δ1 due to the presence of the RL 100 repeater in the transmission chain between the EP terminal in question and the SERV 130 server equipment. The time Δ4 can, however, be equal to the time Δ1, notably starting from... Petition 870240099175, dated 11 / 21 / 2024, page 32 / 166 28 / 62 principle that the time Δ1 was defined with a comfortable margin to bring flexibility to the communication system in the operations to be carried out within the scope of the registration of an EP terminal.

[0064] The third receiving window Rx'1 and the fourth receiving window Rx'2 preferably have the same size. The third receiving window Rx'1 may have the same size as the first receiving window Rx1, and the fourth receiving window Rx'2 may have the same size as the second receiving window Rx2. In a preferred embodiment, the third receiving window Rx'1 is increased by a margin ε relative to the first receiving window Rx1 and the fourth receiving window Rx'2 is increased by a margin ε relative to the first receiving window Rx1, in order to relax the clock accuracy obligations, and in a general way the manufacturing limits, of the RL 100 relay relative to those of the GW gateways.

[0065] In response to the JOIN_REQUEST message, the EP terminal is assumed to have received a JOIN_ACCEPT message in the third reception window Rx'1 or the fourth reception window Rx'2, unless a gateway GW has become within radio range of said EP terminal, in which case the JOIN_REQUEST message is transmitted in the first reception window Rx1 or the second reception window Rx2. This arrangement allows the EP terminal to go into standby mode after sending the JOIN_REQUEST message and to know exactly when to wake up to receive a possible response to the JOIN_REQUEST message when said EP terminal relies on the RL 100 relay to communicate with the SERV 130 server equipment.

[0066] Through the aforementioned eventual margin ε, the definitions of the third reception window Rx'1 and the fourth reception window Rx'2 are respective replicas, offset in time (time Δ4), of the definitions of the first reception window Rx1 and the second Petition 870240099175, dated 11 / 21 / 2024, page 33 / 166 29 / 62 reception window Rx2. Preferably, the same transmission settings (modulation and coding scheme, ...) are used respectively.

[0067] Figure 3D schematically illustrates a communication sequence, applied when an EP terminal wishes to transmit a service message MSG to the server equipment SERV 130, relying for this purpose on the repeater RL 100. When the EP terminal wishes to transmit such a service message MSG, said EP terminal has access to the communication medium within a predetermined time interval, as described below in relation to Figure 3E. Said EP terminal thus transmits its service message MSG, which defines the first reception window Rx1 and the second reception window Rx2, as well as the third reception window Rx'1 and the fourth reception window Rx'2. As for Figure 3B, the first reception window Rx1 is defined at a time Δ3 < Δ1 relative to the sending of the service message MSG, and as for Figure 3C, the third reception window Rx'1 is defined at a time Δ5 > Δ3 relative to the first reception window Rx1.It should be noted, therefore, that time Δ5 is typically greater than time Δ3 due to the presence of the RL 100 repeater in the transmission chain between the EP terminal in question and the SERV 130 server equipment. Time Δ5 can, however, be equal to time Δ3, notably based on the principle that time Δ3 was defined with a comfortable margin to provide flexibility to the communication system in operations performed within the scope of handling MSG service messages. Time Δ5 is preferably equal to time Δ4 and time Δ1, for reasons of simplicity in configuring the communication system.

[0068] In response to the MSG service message, the EP terminal is assumed to have received a corresponding reply message in the third receive window Rx'1 or the fourth receive window Rx'2, Petition 870240099175, dated 11 / 21 / 2024, page 34 / 166 30 / 62 except if a gateway (GW) has become within radio range of said EP terminal, in which case said reply message is transmitted in the first reception window Rx1 or in the second reception window Rx2. This arrangement allows the EP terminal to go into standby mode after sending the service message MSG and to know exactly when to wake up to receive a possible reply to the service message MSG when said EP terminal relies on the repeater RL 100 to communicate with the server equipment SERV 130.

[0069] As with times Δ1, Δ2 and Δ3, times Δ4 and Δ5 are pre-informed within any EP terminal that is aware of the potential presence of the RL 100 repeater in the communication system, as well as within the RL 100 repeater itself (for example, at the time of its manufacture). In a variant embodiment, times Δ4 and Δ5 are pre-informed within the RL 100 repeater (for example, at the time of its manufacture) and the RL 100 repeater informs values ​​of times Δ4 and / or Δ5 within the beacons transmitted by said RL 100 repeater. These beacons are introduced below in relation to Figure 3E.

[0070] Figure 3E schematically illustrates a communication sequence, applied when an EP terminal wishes to rely on the RL 100 relay to communicate with the SERV 130 server equipment. In fact, the communication sequences illustrated in Figures 3A and 3B are initiated by an asynchronous sending of a JOIN_REQUEST or MSG message, respectively, by the EP terminal in question (or by the RL 100 relay when said RL 100 relay communicates with the SERV 130 server via one or more GW gateways). The asynchronicity of the initiation of these sequences does not present a special difficulty, as the gateways are designed to be continuously powered and can therefore be constantly ready to listen to the medium. Petition 870240099175, dated 11 / 21 / 2024, page 35 / 166 31 / 62 scope of LPWAN type communications. To allow the RL 100 repeater to enter standby mode, a certain synchronization is introduced. Thus, the RL 100 repeater regularly emits B beacons. The emission of these B beacons is carried out simultaneously with the emission of beacons by the GW gateways within the scope of LPWAN type communication. In fact, the GW gateways are synchronized with each other and are configured to simultaneously transmit beacons, which provide a temporal reference to the equipment (e.g., EP terminals) that listen to them. Thus, the RL 100 repeater can rely on the beacons emitted by one or more GW gateways to synchronize with the communication system. By emitting B beacons for this purpose alone, the RL 100 repeater also allows EP terminals outside the effective radio range of the GW gateways to be synchronized with the rest of the communication system.The B beacons emitted by the RL 100 repeater include information indicating that said B beacons were emitted by an RL repeater, so as to allow an EP terminal receiving said beacons to know that they were not transmitted by a GW gateway. This allows said EP terminal to know which communication mode to use between Class A and Class A', as described below in relation to Figures 5 and 6.

[0071] B beacons thus have the same format as those issued by GW gateways. By relying on the LoRaWAN data transmission protocol (registered trademark), B beacons can be distinguished from those issued by GW gateways by using a specific value (for example, the value 3) in the Infodesc subfield of the GwSpecific field.

[0072] The time between two successive emissions of B beacons, which is called a cycle, is cut into time intervals SL separated by protection intervals of predefined duration, as shown in Figure 3E in which x+1 time intervals from SL0 to SLx are Petition 870240099175, dated 11 / 21 / 2024, page 36 / 166 32 / 62 represented. The SL time intervals are of a predefined duration known to the EP terminals, the RL 100 repeater, and the GW gateways (e.g., at the time of their manufacture). The SL time intervals begin and end at times deducible relative to the B beacons. Each B beacon includes information indicating which time intervals can be used by the EP terminals to rely on the RL 100 repeater in order to communicate with the SERV 130 server equipment. It is possible that only one SL time interval is authorized to be used per cycle by the EP terminals to rely on the RL 100 repeater in order to communicate with the SERV 130 server equipment.The SL time intervals indicated in the B beacons are therefore SL time intervals during which the RL 100 relay is configured to listen to the medium, and therefore during which the JOIN_REQUEST messages and MSG service messages that must be relayed by the RL 100 relay must be transmitted by the EP terminals in question. This aspect is detailed below in relation to Figure 8. The B beacons may, on the other hand, include information indicating which data rate (DR) is applicable in each SL time interval indicated in said B beacons.

[0073] In a special embodiment in which the relay Since RL 100 is unable to listen to the medium while simultaneously transmitting via said medium, the RL 100 relay cancels the transmission of beacon B for certain cycles. This allows the RL 100 relay to listen to the medium searching for a beacon emitted by a gateway (GW) of the communication system, thus determining the transmission time and remaining synchronized with the rest of the communication system.

[0074] The communication sequences shown in Figures 3C, 3D, and 3E thus define the Class A communication mode already mentioned. A different number of reception windows may Petition 870240099175, dated 11 / 21 / 2024, page 37 / 166 33 / 62 should be used, since the Class A communication mode doubles (time lag (time Δ4 and Δ5)) the number of reception windows used for the Class A communication mode.

[0075] The fact of maintaining the existence of the first Rx1 and second The Rx2 reception windows within Figures 3C and 3D allow signaling operations to be avoided. In fact, if an EP terminal using Class A communication mode receives a reply message in the first reception window Rx1 or the second reception window Rx2, it means that said EP terminal is now within radio range of a communication system gateway (GW). The EP terminal in question can then interpret the reception of said reply message in the first reception window Rx1 or the second reception window Rx2 as an instruction from the SERV 130 server equipment to switch to Class A communication mode.

[0076] Figure 4 schematically illustrates an algorithm, implemented by each RL repeater in the communication system, for initializing said RL repeater. For illustrative purposes, it will be considered that the algorithm in Figure 4 is implemented by RL repeater 100.

[0077] In a 401 step, the RL 100 relay is listening for beacons transmitted by one or more GW gateways. When the RL 100 relay receives such beacons, the RL 100 relay is able to synchronize within the communication system. The RL 100 relay is then able to determine where the Rx1 and Rx2 reception windows are located that would allow a message to be sent from it to the SERV 130 server equipment.

[0078] In a 402 step, the RL 100 relay transmits a JOIN_REQUEST message to the SERV 130 server. Class A transmission mode is used, as already Petition 870240099175, dated 11 / 21 / 2024, page 38 / 166 34 / 62 described in relation to Figure 3A. The RL 100 relay has access to the communication medium after preferably waiting for a random (limited) amount of time to elapse. This JOIN_REQUEST message is captured by at least one gateway (GW) from which the RL 100 relay receives beacons, and is propagated by this gateway(s) to the server equipment SERV 130. This JOIN_REQUEST message is handled by the server equipment SERV 130 as described below in relation to Figure 8.

[0079] In a 403 step, the RL 100 relay waits for a JOIN_REQUEST message in the Rx1 and Rx2 reception windows. Unless there is a predefined handling to perform, the RL 100 relay goes into standby until the first Rx1 reception window occurs, and if no JOIN_REQUEST message is addressed to it in the first Rx1 reception window, the RL 100 relay goes into standby until the second Rx2 reception window occurs.

[0080] In a 404 step, the relay RL 100 checks if a JOIN_REQUEST message was addressed to it in the first receive window Rx1 or in the second receive window Rx2. If so, a 407 step is performed; otherwise, a 405 step is performed.

[0081] In step 405, relay RL 100 checks if a maximum quota of JOIN_REQUEST messages has been reached without a JOIN_REQUEST message being sent in response. If this is the case, a 406 step is performed; otherwise, step 402 is repeated.

[0082] In step 406, an alarm is generated to indicate to an installer that the initialization of the RL 100 transmitter has failed, and the algorithm in Figure 4 is terminated.

[0083] In step 407, the RL 100 relay sends a beacon parameter recovery message to the SERV 130 server. Class A transmission mode is used, Petition 870240099175, dated 11 / 21 / 2024, page 39 / 166 35 / 62 as already described in relation to Figure 3B. The RL 100 repeater has access to the communication medium after preferably waiting for a random (limited) amount of time to pass. The parameters that the RL 100 repeater seeks to obtain from the SERV 130 server equipment are intended to be used by the RL 100 repeater to construct the B beacons mentioned in relation to Figure 3E. These parameters could be predefined, for example, by configuration by the installer or at the factory, in which case the RL 100 repeater does not need to retrieve them from the SERV 130 server equipment as described below in relation to Figure 8.

[0084] In a 408 step, the RL 100 relay waits for a reply message in the Rx1 and Rx2 reception windows. Unless there is a predefined treatment to execute, the RL 100 relay goes into standby until the first Rx1 reception window occurs, and if no reply message is addressed to it in the first Rx1 reception window, the RL 100 relay goes into standby until the second Rx2 reception window occurs.

[0085] In a 409 step, the RL 100 relay checks if a reply message has been addressed to it in the first reception window Rx1 or in the second reception window Rx2. If so, a 411 step is performed; otherwise, a 410 step is performed.

[0086] In step 410, the RL 100 relay checks if a maximum quota of beacon parameter recovery message transmissions has been reached without a reply message being received. If so, step 406 is performed; otherwise, step 407 is performed.

[0087] In step 411, the RL 100 relay activates the regular transmission of the B beacons. The B beacons indicate that they are being transmitted. Petition 870240099175, dated 11 / 21 / 2024, page 40 / 166 36 / 62 by an RL 100 relay and, on the other hand, identify, in accordance with the parameters retrieved from the SERV 130 server equipment, which are the SL time intervals that can be used by any EP terminal to rely on the RL 100 relay in order to communicate with the SERV 130 server equipment. The RL 100 relay also programs wake-up periods that correspond to said SL time intervals during which the RL 100 relay listens to the medium to capture any message that the RL 100 relay would have to retransmit to the SERV 130 server equipment. Other parameters may have been communicated by the SERV 130 server equipment in said reply message, and the RL 100 relay uses them within the scope of programming the regular transmissions of the B beacons and / or the wake-up periods that correspond to said SL time intervals. This brings the algorithm in Figure 4 to an end.

[0088] It is apparent from reading the algorithm in Figure 4 and the communication sequences in Figures 3A to 3E that the RL 100 repeater is a plug-and-play device. In fact, simply inserting the RL 100 repeater into the communication system already constituted by the SERV 130 server equipment and at least one GW 120 gateway within radio range of said RL 100 repeater will allow said RL 100 repeater to take charge of the EP terminals and thus extend the radio range of the communication system.

[0089] Figure 5 schematically illustrates an algorithm, implemented by any EP terminal aware of the potential presence of at least one RL 100 repeater within the communication system, for executing a registration procedure of said EP terminal with the SERV 130 server equipment. For illustrative purposes, it will be considered that the algorithm in Figure 5 is executed... Petition 870240099175, dated 11 / 21 / 2024, page 41 / 166 37 / 62 via terminal EP 110.

[0090] In a 501 step, the EP 110 terminal transmits a JOIN_REQUEST message to the SERV 130 server. Nominally, Class A transmission mode is used, as already described in relation to Figure 3A. The EP 110 terminal has access to the communication medium after preferably waiting for a random (limited) amount of time to elapse.

[0091] In a 502 step, the EP 110 terminal waits for a JOIN_ACCEPT message in the Rx1 and Rx2 reception windows. Unless there is a predefined treatment to execute, the EP 110 terminal is placed in standby until the first Rx1 reception window occurs, and if no JOIN_ACCEPT message is addressed to it in the first Rx1 reception window, the EP 110 terminal is placed in standby until the second Rx2 reception window occurs.

[0092] In a 503 step, terminal 110 checks if a JOIN_ACCEPT message has been addressed to it in the first Rx1 reception window or the second Rx2 reception window. If so, this means that terminal EP 110 is within radio range of at least one GW gateway, and a 504 step is performed; otherwise, a 505 step is performed.

[0093] In step 504, terminal EP 110 handles the message JOIN_ACCEPT is configured to use Class A transformation mode for future communications, that is, within the scope of the algorithm in Figure 6. The algorithm in Figure 5 is then terminated.

[0094] In step 505, the EP 110 terminal checks if a maximum quota of JOIN_REQUEST message transmissions, in Class A transmission mode, has been reached without a JOIN_ACCEPT message in response. If this is the case, a step Petition 870240099175, dated 11 / 21 / 2024, p. 42 / 166 38 / 62 Step 506 is performed; otherwise, step 501 is repeated.

[0095] In step 506, terminal EP 110 searches for a beacon that would be emitted by an RL repeater, such as repeater RL 100. Terminal EP 110 listens to the medium for a time at least equal to the time of one cycle - that is, the time between two successive beacons (128 seconds according to the LoRaWAN data transmission protocol (registered trademark)).

[0096] In a 507 step, the EP 110 terminal checks if at least one B beacon has been detected by said EP 110 terminal. To remember, the B beacons contain information indicating that said beacons are emitted by an RL repeater and not by a GW gateway. If this is the case, a 508 step is performed; otherwise, the 501 step is repeated, after preferably waiting for a predefined time to elapse (during which the EP 110 terminal may be placed in standby mode).

[0097] In step 508, the EP 110 terminal waits for the occurrence of an indicated SL time interval, as indicated in the received beacon, to be authorized to transmit a message to the SERV 130 server equipment, relying for this purpose on the RL relay that emitted said beacon. Unless there is a predefined treatment to be executed, the EP 110 terminal remains in standby until the occurrence of said SL time interval.

[0098] In step 509, terminal EP 110 resends the message JOIN_REQUEST during the specified SL time interval. In this case, the EP 110 terminal uses Class A transmission mode.

[0099] In step 510, the EP 110 terminal waits for a JOIN_ACCEPT message in the Rx1 and Rx2 reception windows, and especially in the Rx'1 and Rx'2 reception windows. In fact, at this stage, the Rx1 and Rx2 reception windows are dispensable, since no GW gateway has a priori received the JOIN_REQUEST message. Petition 870240099175, dated 11 / 21 / 2024, page 43 / 166 39 / 62 transmitted in the preceding execution of step 501. Unless there is a predefined treatment to execute, the EP 110 terminal goes into stand-by mode until the first Rx1 reception window occurs; if no JOIN_ACCEPT message is addressed to it in the first Rx1 reception window, the EP terminal goes into stand-by mode until the second Rx2 reception window occurs; if no JOIN_ACCEPT message is addressed to it in the second Rx2 reception window, the EP 110 terminal goes into stand-by mode until the third Rx'1 reception window occurs; and if no JOIN_ACCEPT message is addressed to it in the third Rx'1 reception window, the EP 110 terminal goes into stand-by mode until the fourth Rx'2 reception window occurs.

[00100] In a 511 step, the EP 110 terminal checks if a JOIN_ACCEPT message has been addressed to it in the third reception window Rx'1 or the fourth reception window Rx'2. It is assumed here that no GW gateway is currently within radio range of the EP 110 terminal, but if the EP 110 terminal were to receive a JOIN_ACCEPT message in the first reception window Rx1 or the second reception window Rx2, then a 504 step would be performed (not shown in Figure 5). If a JOIN_ACCEPT message has been addressed to it in the third reception window Rx'1 or the fourth reception window Rx'2, a 512 step is performed; otherwise, a 513 step is performed.

[00101] In step 512, the EP 110 terminal processes the JOIN_ACCEPT message and configures itself to use Class A transmission mode for future communications, that is, within the scope of the algorithm in Figure 6. The algorithm in Figure 5 is then terminated.

[00102] In step 513, the EP terminal checks if the maximum quota for sending JOIN_REQUEST messages has been reached, in Class A transmission mode, without a message having been sent. Petition 870240099175, dated 11 / 21 / 2024, page 44 / 166 40 / 62 JOIN_ACCEPT is used in response. If so, step 501 is repeated; otherwise, step 506 is repeated.

[00103] Figure 6 schematically illustrates an algorithm, implemented by any EP terminal that is aware of the potential presence of at least one RL repeater within the communication system, for transmitting data to the SERV 130 server equipment, after registration of said EP terminal with the SERV 130 server equipment. For illustrative purposes, it will be considered that the algorithm in Figure 5 is executed by the EP 110 terminal.

[00104] In a step 601, the EP 110 terminal detects that data held by said EP 110 terminal must be transmitted to the SERV 130 server equipment. For example, the EP 110 terminal integrates a sensor (e.g., water or gas consumption sensor) and said data are measurement data collected by said sensor.

[00105] In a step 602, terminal EP 110 determines whether said terminal EP 110 is configured in Class A transmission mode or whether said terminal EP 110 is configured in Class A transmission mode'. If terminal EP 110 is configured in Class A transmission mode, a step 603 is performed; otherwise, a step 609 is performed.

[00106] In step 603, the EP 110 terminal transmits a service message (MSG) containing said data to the SERV 130 server. Class A transmission mode is used, as already described in relation to Figure 3B. The EP 110 terminal accesses the communication medium after preferably waiting for a random (limited) amount of time to elapse.

[00107] In a 604 step, the EP 110 terminal waits for a response message in the Rx1 and Rx2 reception windows. Unless there is a predefined treatment to execute, the EP 110 terminal remains in standby until the first reception window occurs. Petition 870240099175, dated 11 / 21 / 2024, page 45 / 166 41 / 62 Rx1, and if no reply message is addressed to it in the first reception window Rx1, the EP 110 terminal goes into standby mode until the second reception window Rx2 occurs.

[00108] In a step 605, the EP 110 terminal checks if a reply message has been addressed to it in the first Rx1 reception window or in the second Rx2 reception window. If so, a step 606 is performed; otherwise, a step 607 is performed.

[00109] In step 606, terminal EP 110 processes the response message, and then the algorithm in Figure 6 is terminated.

[00110] In step 607, the EP 110 terminal checks if a maximum quota of service message transmissions has been reached without a reply message being received. If so, a step 608 is performed; otherwise, step 603 is repeated.

[00111] In step 608, terminal EP 110 performs a new registration procedure, that is, it executes the algorithm in Figure 5 again. The algorithm in Figure 6 is then terminated.

[00112] In step 609, the EP terminal waits for a beacon that would be emitted by an RL relay, and more specifically by the RL relay through which the EP 110 terminal registered with the SERV 130 server equipment (see the algorithm in Figure 5). This allows the EP 110 terminal to ensure that it remains synchronized with the rest of the communication system, since the EP 110 terminal may have remained in standby for numerous hours, which may have caused a certain time lag between its internal clock and the actual broadcast of the beacons within the communication system. But if the internal clock of the EP 110 terminal is considered reliable, the EP 110 terminal can avoid executing step 609 each time the algorithm in Figure 6 is run and proceed directly to step 610.

[00113] In step 610, terminal EP 110 is placed on hold for Petition 870240099175, dated 11 / 21 / 2024, page 46 / 166 42 / 62 occurrence of an indicated SL time interval, in the received beacon, as being authorized to transmit a message to the server equipment SERV 130, relying for this purpose on the retransmitter RL 100 that emitted said beacon. Unless there is a predefined treatment to be executed, the EP terminal goes into stand-by until the occurrence of said SL time interval.

[00114] In a step 611, the EP 110 terminal transmits during the said time interval SL, destined for the SERV 130 server equipment, a service message MSG that includes said data. The Class A' transmission mode is used, as already described in relation to Figures 3D and 3E.

[00115] In step 612, the EP 110 terminal waits for a reply message in the Rx1 and Rx2 reception windows. Even if the EP 110 terminal is currently passing through an RL relay to communicate with the SERV 130 server equipment, it is possible that the EP 110 terminal is now within radio range of a GW gateway, in which case said GW gateway would also have propagated the service message MSG directly received from the EP 110 terminal to the SERV 130 server equipment. Unless there is a predefined treatment to be executed, the EP 110 terminal goes into standby until the first Rx1 reception window occurs, and if no reply message is addressed to it in the first Rx1 reception window, the EP 110 terminal goes into standby until the second Rx2 reception window occurs.

[00116] In step 613, terminal EP 110 checks whether a reply message has been addressed to it in the first reception window Rx1 or in the second reception window Rx2. If so, step 614 is performed; otherwise, step 615 is performed.

[00117] In step 614, the EP 110 terminal handles the response message and configures itself to use Class 1 transmission mode. Petition 870240099175, dated 11 / 21 / 2024, page 47 / 166 43 / 62 For the next communication destined for the SERV 130 server equipment, that is, within the scope of the next execution of the algorithm in Figure 6, the algorithm in Figure 6 is then terminated.

[00118] In step 615, the EP 110 terminal waits for a reply message in the Rx'1 and Rx'2 reception windows. Unless there is a predefined treatment to execute, the EP 110 terminal is placed on standby until the occurrence of the third Rx'1 reception window, and if no reply message is addressed to it in the third Rx'1 reception window, the EP 110 terminal is placed on standby until the occurrence of the fourth Rx2 reception window.

[00119] In step 616, terminal EP 110 checks whether a reply message has been addressed to it in the third reception window Rx'1 or the fourth reception window Rx'2. If so, step 618 is performed; otherwise, step 617 is performed.

[00120] In step 617, terminal EP 110 checks if a maximum quota of MSG service message transmissions has been reached without a reply message being received. If so, step 608 is performed; otherwise, step 608 is repeated. Terminal EP 110 may also attempt to send its MSG service message again using a different SL time interval, in which the RL relay in question is assumed to be listening to the medium, in the same cycle – that is, before the next beacon broadcast within the communication system. Step 610 is then executed directly.

[00121] In step 618, terminal EP 110 processes the response message, and then the algorithm in Figure 6 is terminated.

[00122] Figure 7 schematically illustrates an RL retransmission algorithm, propagating data received from an EP terminal to the SERV 130 server equipment. For illustrative purposes, it will be considered that the algorithm in Figure 7 is implemented by the RL 100 retransmitter. Petition 870240099175, dated 11 / 21 / 2024, page 48 / 166 44 / 62

[00123] In a 701 step, the RL 100 relay is listening to the medium during the SL time intervals programmed in the 411 step. These are SL time intervals indicated on the B beacons emitted cyclically by the RL 100 relay.

[00124] In a 702 step, the RL 100 relay checks if a message originating from an EP terminal was received during the specified SL time intervals. If so, a 703 step is performed; otherwise, the 701 step is repeated, being placed on standby for as long as possible.

[00125] In step 703, the RL 100 relay checks if the received message should be relayed by the RL 100 relay. If the received message is a JOIN_REQUEST message, said message should be relayed by the RL 100 relay to the SERV 130 server equipment, regardless of the EP terminal that transmitted said message. If the received message is another message, said message should be relayed by the RL 100 relay to the SERV 130 server equipment only if said message was issued by an EP terminal that the RL 100 relay is responsible for, that is, if the EP terminal is enrolled in an L list identifying the EP terminals connected to it, meaning from which service messages should be relayed by the RL 100 relay (see step 711 described below).If the received message must be retransmitted by the RL 100 relay, a 704 step is performed; otherwise, the 701 step is repeated, placing itself on standby as much as possible for this purpose.

[00126] In the 704 step, the RL 100 relay determines at what times the third Rx'1 and fourth Rx'2 reception windows are defined, counting from the reception of said message. The RL 100 relay therefore determines in which time windows said RL 100 relay has the possibility of responding to the received message. Petition 870240099175, dated 11 / 21 / 2024, page 49 / 166 45 / 62

[00127] In a 705 step, the RL 100 relay relays the received message to the SERV 130 server. To do this, the RL 100 relay encapsulates the received message in a service message that the RL 100 relay sends on its behalf to the SERV 130 server. Since the RL 100 relay is viewed as an EP terminal from the perspective of the GW gateways, this encapsulation makes the presence of the RL 100 relay transparent to the GW gateways. The RL 100 relay uses Class A transmission mode, with the GW gateways constantly listening to the medium. This service message sent by the RL 100 relay is handled at the SERV 130 server level as described below in relation to Figures 9 and 10.In a special embodiment, this service message includes signal quality level information for the reception of said message, more specifically with regard to JOIN_REQUEST messages. This can help the SERV 130 server equipment decide which RL relay to entrust with the charge of the EP terminal in question when the same JOIN_REQUEST message is relayed by several RL relays (which assumes that said RL relays indicate at least one common SL time slot in their respective beacons) on behalf of said EP terminal.

[00128] In a 706 step, the RL 100 relay waits for a reply message in the Rx1 and Rx2 reception windows, as described in relation to Figure 3B. Unless there is a predefined treatment to be executed, the RL 100 relay remains in standby until the first Rx1 reception window occurs, and if no reply message is addressed to it in the first Rx1 reception window, the RL 100 relay remains in standby until the second Rx2 reception window occurs. Note well that here the Petition 870240099175, dated 11 / 21 / 2024, page 50 / 166 46 / 62 first Rx1 and second Rx2 reception windows are defined in relation to the service message sent by the RL 100 relay to the SERV 130 server equipment, and should not be confused with the first Rx1 and second Rx2 reception windows defined in relation to the message originally sent by the EP terminal (and which the RL 100 relay retransmits in its service message).

[00129] In a 707 step, the RL 100 relay checks if a reply message has been addressed to it in the first reception window Rx1 or in the second reception window Rx2. If so, a 708 step is performed; otherwise, this means that the EP terminal in question will not a priori have a reply to the message that the said EP terminal had sent and that the RL 100 relay had retransmitted, and the 701 step is repeated, placing itself on standby for this purpose as much as possible.

[00130] In a step 708, the RL 100 relay decapsulates the received reply message and checks if the received reply message encapsulates a JOIN_ACCEPT message (preferably checking on the other hand that the JOIN_ACCEPT message actually corresponds to a previously relayed JOIN_REQUEST message). If so, a step 711 is performed; otherwise, a step 709 is performed.

[00131] In step 709, the RL 100 relay checks if the received reply message is a DETACH message. A detach message is a message that instructs the RL 100 relay to no longer retransmit service messages originating from the EP terminal in question. This occurs when the said EP terminal is now within radio range of one or more GW gateways, as described below in relation to Figure 10. If the received reply message is a Petition 870240099175, dated 11 / 21 / 2024, page 51 / 166 47 / 62 DETACH shutdown message, a 710 step is performed; otherwise, a 712 step is performed.

[00132] In step 710, the RL 100 relay deletes the EP terminal (its DevAddr identifier assigned to it by the SERV 130 server equipment) from the L list identifying the EP terminals connected to it. The algorithm in Figure 7 is then terminated.

[00133] In step 711, the RL 100 relay registers in local memory a DevAddr identifier of the EP terminal contained in the JOIN_ACCEPT message. This DevAddr identifier of the EP terminal is assigned by the SERV 130 server equipment after receiving the JOIN_REQUEST message to which the JOIN_ACCEPT message follows. This DevAddr identifier of the EP terminal enriches the L list of identification of the EP terminals that are connected to it. The RL 100 relay therefore interprets the reception of this JOIN_ACCEPT message as an implicit instruction to connect the said EP terminal to the RL 100 relay. Variants of this approach are described below in relation to step 906. Step 712 is then performed.

[00134] In step 712, the RL 100 relay propagates the JOIN_ACCEPT message in the third reception window Rx'1 or the fourth reception window Rx'2 defined by the execution of step 704, that is, the third Rx'1 and fourth Rx'2 reception windows defined from the sending of the original message by the EP terminal in question. The algorithm in Figure 7 is then terminated.

[00135] Figure 8 schematically illustrates an algorithm, implemented by the SERV 130 server equipment, to register any RL repeater within the communication system (corresponding to Figure 4). The algorithm in Figure 8 is preferably executed by the LNS 131 server.

[00136] In an 801 step, the server equipment SERV 130 Petition 870240099175, dated 11 / 21 / 2024, page 52 / 166 48 / 62 receives a JOIN_REQUEST message originating from an RL relay, such as RL relay 100. Unless the SERV 130 server equipment is aware of the Extended Unique Identifier (EUI) unique identifiers of all RL relays likely to be included in the communication system, the SERV 130 server equipment does not yet know that the JOIN_REQUEST message originates from an RL relay.

[00137] In an 802 step, the SERV 130 server equipment processes the JOIN_REQUEST message and assigns a DevAddr identifier to the RL relay in question. In response to the JOIN_REQUEST message, the SERV 130 server equipment sends a JOIN_ACCEPT message that includes the DevAddr identifier assigned to the RL relay in question. The SERV 130 server equipment selects a gateway (GW) from among those (if there are several) that propagated the JOIN_REQUEST message. Typically, the SERV 130 server equipment selects a gateway that indicated the best signal quality level in receiving the JOIN_REQUEST message. The GW gateway thus selected is therefore responsible for responding to the RL relay in question, using either the first Rx1 or the second Rx2 reception window, which were defined by the JOIN_REQUEST message sent by the RL relay in question (as shown in Figure 3A).

[00138] If the SERV 130 server equipment receives a JOIN_REQUEST message for an already registered RL relay, the SERV 130 server equipment cancels the previous registration of said RL relay (this means that said RL relay had lost its connection to the communication system and initiated a new registration procedure).

[00139] In a step 803, the server equipment SERV 130 Petition 870240099175, dated 11 / 21 / 2024, page 53 / 166 49 / 62 receives a service message (MSG) originating from the RL relay in question. This service message is a beacon parameter retrieval message (as already mentioned in relation to Figure 4). The SERV 130 server equipment then knows that it is dealing with an RL relay.

[00140] In an 804 step, the SERV 130 server equipment registers the unique EUI identifier of the RL relay in question, the DevAddr identifier assigned to it, and indicates accordingly that the device in question is an RL relay.

[00141] In the aforementioned special embodiment of the SERV 130 server equipment, the LNS 131 server informs the RLA 132 relay application, which is responsible for said RL relay, of the presence of said RL relay within the communication system. Said RLA 132 relay application is then able to perform encapsulations and decapsulations to allow said RL relay to perform its relay role. In the event that multiple RLA 132 relay applications exist within the SERV 130 server equipment, the LNS 131 server retains a trace of information indicating to which RLA 132 relay application said RL relay was declared.

[00142] In step 805, the SERV 130 server equipment determines which SL time slots should be used by the RL relay in question to receive messages from EP terminals that will eventually be connected to it later. These are the SL time slots that the RL relay in question must mention in the B beacons (see step 411). The SERV 130 server equipment chooses these SL time slots in the same way as for Class B transmission mode communications implemented by GW gateways under the protocol of Petition 870240099175, dated 11 / 21 / 2024, page 54 / 166 50 / 62 LoRaWAN type data transmission (registered trademark). Other parameters can be selected by the SERV 130 server equipment for sending the B beacons by the RL repeater in question, such as the times Δ4 and Δ5 mentioned in relation to Figures 3C and 3D.

[00143] In step 806, the SERV 130 server equipment sends a reply message to the RL relay in question, which includes the parameters determined in step 805, more specifically representative information of the said SL time intervals. The SERV 130 server equipment uses a gateway GW to propagate the said reply message to the RL relay in question. The said gateway GW uses in this case the first reception window Rx1 or the second reception window Rx2 that were defined by the sending, by the said RL relay, of the said beacon parameter recovery message (according to Figure 3B). The algorithm of Figure 8 then ends.

[00144] Figure 9 schematically illustrates an algorithm, implemented by the SERV 130 server equipment, to handle a JOIN_REQUEST message retransmitted by an RL relay of the communication system.

[00145] In a step 901, the server equipment SERV 130 receives the JOIN_REQUEST message relayed by an RL relay from the communication system. The said JOIN_REQUEST message was therefore encapsulated in a service message MSG by said RL relay. The server equipment SERV 130 then decapsulates said JOIN_REQUEST message.

[00146] In the aforementioned special embodiment of the SERV 130 server equipment, the MSG service message is received by the LNS 131 server, which detects that the message originates from said relay RL thanks to the identifier included in said relay. Petition 870240099175, dated 11 / 21 / 2024, page 55 / 166 51 / 62 service message MSG, which corresponds to the identifier assigned to said relay RL. The LNS 131 server therefore passes said service message MSG to the RLA 132 relay application in charge of said relay RL. Said relay application RLA 132 decapsulates said JOIN_REQUEST message on behalf of the LNS 131 server.

[00147] In a step 902, the SERV 130 server checks if the said JOIN_REQUEST message has been received multiple times, that is, from multiple sources. This means that the SERV 130 server times the processing of said JOIN_REQUEST message long enough to determine, based on the maximum latency in the communication system, whether said JOIN_REQUEST message is actually received or not from another source. If this is the case, a step 903 is performed; otherwise, a step 905 is performed.

[00148] In step 903, the server equipment SERV 130 checks if the said JOIN_REQUEST message was also received via at least one GW gateway. If so, a step 907 is performed; otherwise, a step 904 is performed.

[00149] In step 904, the SERV 130 server equipment selects an RL relay from among those that relayed the JOIN_REQUEST message. For example, each RL relay includes, in its service message MSG that encapsulates the JOIN_REQUEST message, information about the signal quality level for receiving the JOIN_REQUEST message. The SERV 130 server equipment then selects the RL relay that presents the best signal quality level for receiving the JOIN_REQUEST message. According to another example, the SERV 130 server equipment selects the RL relay to which the fewest number of EP terminals are connected among those that relayed the JOIN_REQUEST message. Other criteria Petition 870240099175, dated 11 / 21 / 2024, p. 56 / 166 52 / 62 can be used, alone or in combination with the aforementioned examples. And then, step 905 is carried out.

[00150] In step 905, the SERV 130 server equipment assigns a DevAddr identifier to the EP terminal that transmitted the JOIN_REQUEST message and registers that the said EP terminal is connected to the said RL relay. The SERV 130 server equipment therefore maintains, for each RL relay, a list L' of EP terminals that are connected to the said RL relay, the said EP terminals being respectively identified by their unique identifier EUI and by their DevAddr identifiers. If the SERV 130 server equipment receives a JOIN_REQUEST message for an EP terminal already connected to an RL relay, the SERV 130 server equipment cancels the previous registration of the said EP terminal (this means that the said EP terminal had lost the connection to the communication system and initiated a new registration procedure).

[00151] In step 906, the SERV 130 server equipment generates a JOIN_ACCEPT message destined for the EP terminal that transmitted the said JOIN_REQUEST message, the JOIN_ACCEPT message including the DevAddr identifier assigned to said EP terminal. Furthermore, the SERV 130 server equipment encapsulates said JOIN_ACCEPT message in a reply message to the MSG service message via which said JOIN_REQUEST message arrived at the SERV 130 server equipment. This reply is addressed to the RL relay to which the EP terminal in question is connected. The SERV 130 server equipment uses a GW gateway to propagate said reply message to the MSG service message to said relay RL. The said gateway GW then uses the first reception window Rx1 or the second reception window Rx2 that were defined by the sending, by the said relay RL, of the said service message MSG (according to Figure 3B). The algorithm then ends. Petition 870240099175, dated 11 / 21 / 2024, page 57 / 166 53 / 62 Figure 9.

[00152] In the aforementioned special embodiment of the SERV 130 server equipment, the LNS 131 server passes the said JOIN_ACCEPT message to the RLA relay application in charge of the said RL relay. The said RLA 132 relay application encapsulates the said JOIN_ACCEPT message on behalf of the LNS 131 server.

[00153] It is considered in the description of step 906 above that said RL relay interprets the reception of said reply message encapsulating the JOIN_ACCEPT message destined for said EP terminal as being a connection instruction from said EP terminal to said RL relay. Alternatively, the SERV 130 server equipment may include in said reply message encapsulating the JOIN_ACCEPT message information that explicitly indicates to said RL relay that said EP terminal is henceforth connected to said RL relay. Another alternative consists of said RL relay transmitting a connection confirmation request message, and including the DevAddr identifier of said EP terminal, so that the SERV 130 server equipment knows to which EP terminal the RL relay in question refers.The SERV 130 server then responds to the aforementioned service message MSG, thus confirming, or possibly denying, the connection of the said EP terminal to the said RL relay. Another variant is that, after receiving the said encapsulated JOIN_ACCEPT message, the said RL relay regularly transmits a connection confirmation message to the SERV 130 server. Similarly, the SERV 130 server then responds to the said service message MSG, thus confirming, or denying, the connection of the said EP terminal to the said RL relay. This ensures that the server equipment... Petition 870240099175, dated 11 / 21 / 2024, page 58 / 166 54 / 62 SERV 130 and the aforementioned relay RL are in agreement as to whether or not the EP terminal in question is connected to the aforementioned relay RL. If the SERV 130 server equipment denies the connection of the aforementioned EP terminal or does not respond, the relay RL in question considers that it no longer needs to relay the MSG service messages originating from the aforementioned EP terminal and removes it from its L list identifying the EP terminals connected to it.

[00154] In step 907, the SERV 130 server equipment generates a JOIN_ACCEPT message destined for the EP terminal that transmitted the JOIN_REQUEST message, the JOIN_ACCEPT message including the DevAddr identifier assigned to said EP terminal. The SERV 130 server equipment uses a gateway (GW) to propagate the JOIN_ACCEPT message to the EP terminal in question. The said gateway (GW) then uses the first reception window (Rx1) or the second reception window (Rx2) that were defined by the sending of the JOIN_REQUEST message by said EP terminal (according to Figure 3A). The algorithm in Figure 9 then ends.

[00155] Figure 10 schematically illustrates an algorithm, implemented by the SERV 130 server equipment, to process a service message MSG transmitted by an EP terminal and retransmitted by an RL relay of the communication system.

[00156] In step 1001, the server equipment SERV 130 receives the service message MSG transmitted by the EP terminal and retransmitted by said relay RL. Said service message MSG was therefore itself encapsulated in another service message MSG by said relay RL. The server equipment SERV 130 then decapsulates said service message MSG transmitted by an EP terminal.

[00157] In the aforementioned special embodiment of the SERV 130 server equipment, the said other service message Petition 870240099175, dated 11 / 21 / 2024, page 59 / 166 55 / 62 The MSG message is received by the LNS 131 server, which detects that the message originates from the aforementioned relay station RL thanks to the identifier, included in the aforementioned other service message MSF, which corresponds to the identifier assigned to the aforementioned relay station RL. The LNS 131 server therefore passes the aforementioned other service message MSG to the relay application RLA 132, responsible for the aforementioned relay station RL. The aforementioned relay application RLA 132 then decapsulates the said service message MSG transmitted by an EP terminal, on behalf of the LNS 131 server.

[00158] In a step 1002, the SERV 130 server equipment checks whether the said service message MSG transmitted by an EP terminal was also received via at least one GW gateway. If so, this means that the EP terminal is now within radio range of at least one GW gateway of the communication system, and a step 1003 is performed; otherwise, a step 1006 is performed.

[00159] In step 1003, the SERV 130 server equipment disconnects the EP terminal from said RL relay. In other words, the SERV 130 server equipment deletes the unique identifier EUI and the DevAddr identifier of the EP terminal in question from the L' list of EP terminals connected to said RL relay.

[00160] In step 1004, the server equipment SERV 130 generates a shutdown message from said terminal EP, which is destined for the relay RL. This message is sent to the relay RL in response to said other service message MSG in which the service message MSG originally transmitted by said terminal EP was encapsulated. The server equipment SERV 130 uses a gateway GW to propagate said shutdown message to said relay RL. Said gateway GW then uses the first reception window Rx1 or the second reception window Rx2 that were defined by the sending, by said relay RL, of said other Petition 870240099175, dated 11 / 21 / 2024, pp. 60 / 166 56 / 62 service message MSG (according to Figure 3B). The relay RL will therefore stop propagating the service MSG messages from the EP terminal in question (see step 710).

[00161] In a step 1005, the server equipment SERV 130 processes the service MSG message transmitted by said EP terminal and transmits a reply message to said EP terminal (therefore without passing through said relay RL). The server equipment SERV 130 uses a gateway GW to propagate said reply message to the EP terminal in question. Said gateway GW then uses the first reception window Rx1 or the second reception window Rx2 that were defined by the sending, by said EP terminal, of said reply message (according to Figure 3B). The algorithm of Figure 10 is then terminated.

[00162] In step 1006, the SERV 130 server equipment processes the MSG service message transmitted by the said EP terminal and generates a response message destined for the said EP terminal. Furthermore, the SERV 130 server equipment encapsulates said response message in another response message intended to reply to the aforementioned other MSG service message. This other response message is therefore addressed to the RL relay to which the EP terminal in question is connected. The SERV 130 server equipment uses a GW gateway to propagate said other response message to said RL relay. Said GW gateway then uses the first reception window Rx1 or the second reception window Rx2 that were defined by the sending, by said RL relay, of said other MSG service message (according to Figure 3B). The algorithm of Figure 10 then ends.

[00163] In the aforementioned special embodiment of the SERV 130 server equipment, at step 1006, the LNS 131 server propagates the service message MSG, transmitted by the EP terminal in Petition 870240099175, dated 11 / 21 / 2024, page 61 / 166 57 / 62 question, for the EPA 133 terminal application in charge of said EP terminal, so that said MSG service message is handled by said APA 133 terminal application. Said EPA terminal application then generates said response message and passes it to LNS 131 server for transmission. LNS 131 server notices that the EP terminal in question is connected to said RL relay. LNS 131 server then passes said response message, for encapsulation of said response message, to RLA 132 relay application in charge of said RL relay.

[00164] Figure 11 schematically illustrates an example of message exchanges within the communication system, in application of a mode of embodiment of the present invention.

[00165] Terminal EP 110 will be considered to be attempting to register within the communication system comprising repeater RL 100, gateway GW 120, and server equipment SERV 130. Repeater RL 100 is already registered with server equipment SERV 130 and is within radio range of gateway GW 120. Terminal EP 110 is not within radio range of gateway GW, nor of any other gateway GW in the communication system.

[00166] In step 1101, the EP terminal transmits a JOIN_REQUEST (JR) message to the SERV 130 server. The EP 110 terminal uses Class A communication mode, thus expecting its JOIN_REQUEST message to be received by at least one gateway (GW). The EP 110 terminal does not receive a response from a gateway, neither in the first reception window Rx1 nor in the second reception window Rx2 (defined in relation to the sending of the JOIN_REQUEST message in step 1101).

[00167] In step 1102, terminal EP 110 reiterates the transmission of the JOIN_REQUEST (JR) message to the server equipment SERV 130. Terminal EP 110 also uses the mode of Petition 870240099175, dated 11 / 21 / 2024, page 62 / 166 58 / 62 Class A communication. The EP 110 terminal does not receive a return from the gateway (GW), neither in the first reception window Rx1 nor in the second reception window Rx2 (defined in relation to sending the JOIN_REQUEST message in step 1102).

[00168] In step 1103, terminal EP 110 reiterates the transmission of the JOIN_REQUEST (JR) message destined for server equipment SERV 130. Terminal EP 110 is still using Class A communication mode. Terminal EP 110 does not receive a return from a gateway GW, neither in the first reception window Rx1 nor in the second reception window Rx2 (defined in relation to the sending of the JOIN_REQUEST message in step 1102). Terminal EP 110 then considers that it has reached the maximum quota of unsuccessful transmissions of its JOIN_REQUEST (JR) message, and terminal EP 110 decides to switch to Class A communication mode.

[00169] In a step 1104, terminal EP 110 receives a beacon B transmitted by repeater RL 100. The beacon specifies the time intervals SL, defined in relation to the transmission of said beacon B, during which repeater RL 100 is listening to the medium.

[00170] In step 1105, terminal EP 110 waits for one of the said SL time intervals to occur and reiterates the transmission of the JOIN_REQUEST (JR) message destined for server equipment SERV 130. The JOIN_REQUEST (JR) message is received by relay RL 100.

[00171] In step 1106, the relay RL 100 transmits, destined for the server equipment SERV 130, a service message MSG(JR) that encapsulates the JOIN_REQUEST (JR) message transmitted by terminal EP 110 in step 1105. This service message MSG(JR) is received by gateway GW 120, which propagates it to the server equipment SERV 130 in step 1107. The server equipment SERV 130 obtains, by decapsulation, the message Petition 870240099175, dated 11 / 21 / 2024, pp. 63 / 166 59 / 62 JOIN_REQUEST (JR) transmitted by terminal EP 110 and processed. Terminal EP 110 is then registered within the communication system.

[00172] In step 1108, server equipment SERV 130 transmits a REP(JA) reply message to the service message issued by relay RL 100 in step 1106. Server equipment SERV 130 addresses gateway GW 120 to propagate said REP(JA) reply message, which encapsulates a JOIN_ACCEPT (JA) message to be addressed to terminal EP 110.

[00173] In step 1109, gateway 120 propagates the reply message REP(JA) to relay RL 100, which receives said reply message REP(JA). Gateway GW 120 uses the first reception window Rx1 or the second reception window Rx2, defined in relation to the sending of the service message MSG(JR) by relay RL 100 in step 1106. Relay RL 100 obtains, by decapsulation, the JOIN_ACCEPT (JA) message to be addressed to terminal EP 110 and transmits it in step 1110. Relay RL 100 notices that terminal EP 110 is now connected to said relay RL 100. Terminal EP 110 receives the JOIN_ACCEPT (JA) message and knows it is registered within the communication system.Terminal EP 110 is hereby authorized to transmit MSG service messages, which are then retransmitted by relay station RL 100, and the replies are also retransmitted by relay station RL 100 (provided that terminal EP 110 respects the SL time interval obligations imposed by the Class A communication mode).

[00174] Thus, in a retransmission phase R 1111, retransmissions of service messages MSG issued by terminal EP 110 destined for server equipment SERV 130 are carried out. Furthermore, during this retransmission phase R 1111, the retransmitter RL 100 ensures the retransmission of response messages that the Petition 870240099175, dated 11 / 21 / 2024, pp. 64 / 166 Server equipment SERV 130 wishes to transmit to terminal EP 110 in response to said service messages MSG. Relay transmitter RL 100 uses, to do this, the third receiving window Rx'1 or the fourth receiving window Rx'2, defined in relation to the sending of the service message MSG that was emitted by terminal EP 110 and to which the considered response message refers. It will be considered that, at the end of this retransmission phase R 1111, gateway GW 120 becomes within radio range of terminal EP 110, for example because terminal EP 110 has moved.

[00175] In step 1112, terminal EP 110 transmits a service message MSG to server equipment SERV 130, thus waiting for the occurrence of one of the said time intervals SL specified in the beacons B emitted by relay RL 100. This service message MSG is received by relay RL 100.

[00176] In step 1113a, relay RL 100 transmits, to server equipment SERV 130, another service message MSG(MSG) that encapsulates the service message MSG transmitted by terminal EP 110 in step 1112. This other service message MSG(MSG) is received by gateway GW 120, which propagates it to server equipment SERV 130 in step 1114a. The SERV 130 server equipment obtains, through decapsulation, the MSG service message transmitted by the EP 110 terminal.

[00177] In parallel, the MSG service message was also received by gateway GW 120 in step 1113b. Gateway GW 120 propagates it to server equipment SERV 130 in step 1114b. Server equipment SERV 130 then obtains another copy of the MSG service message transmitted by terminal EP 110. Server equipment SERV 130 therefore notes that it has received this MSG service message simultaneously via relay RL 100 as expected (since terminal EP is 110 connected to relay RL 100). Petition 870240099175, dated 11 / 21 / 2024, pp. 65 / 166 61 / 62 RL 100), but also by direct reception from the GW 120 gateway.

[00178] In a step 1115a, the server equipment SERV 130 sends to the relay RL 100, in response to said other service message MSG(MSG), a DETACH disconnection message by which the server equipment SERV 130 instructs the relay RL 100 that the terminal EP 110 is no longer connected to it. The server equipment SERV 130 addresses the gateway GW 120 to propagate said DETACH disconnection message.

[00179] In step 1116a, gateway GW 120 propagates the DETACH shutdown message to relay RL 100. Gateway GW 120 uses either the first receive window Rx1 or the second receive window Rx2, defined in relation to the sending of said other service message MSG(MSG) by relay RL 100 in step 1113a. The RL 100 relay receives the aforementioned DETACH disconnection message and notes that the EP 110 terminal is no longer connected to the said RL 100 relay. The RL 100 relay will no longer relay the MSG service messages transmitted by the EP 110 terminal (for the coincidences in which the EP 110 terminal would send such an MSG service message exactly during an SL time interval occurrence among those specified in the B beacons emitted by the RL 100 relay, which is very unlikely).

[00180] In step 1115b, server equipment SERV 130 sends a response message REP to terminal EP 110 in response to the service message MSG transmitted by terminal EP 110. Server equipment SERV 130 addresses gateway GW 120 to propagate said response message REP to terminal EP 110.

[00181] In step 1116b, gateway GW 120 propagates the REP response message to terminal EP 110. The Petition 870240099175, dated 11 / 21 / 2024, pp. 66 / 166 Terminal 62 / 62 EP 110 receives the said REP reply message and notes that said REP reply message was transmitted in the first reception window Rx1 or in the second reception window Rx2, in relation to the sending of the MSG service message in step 1112. Terminal EP concludes that it is now within radio range of a communication system gateway GW, and switches to Class A communication mode. Petition 870240099175, dated 11 / 21 / 2024, pp. 67 / 166

Claims

1 / 16 CLAIMS 1. Transmission process in a communication system that includes a server equipment (130) and at least one gateway (120, 121, 122) connected to the server equipment, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: - said gateway receives a source message from said terminal and propagates said received source message to the server equipment; - upon receiving a reply message from the server equipment, said gateway propagates the reply message to said terminal using at least one reception window (Rx1, Rx2) defined in relation to a transmission time of said source message by said terminal;characterized by the fact that the communication system includes, on the other hand, at least one relay (100) seen as a terminal for each gateway, each relay using the Class A communication mode to communicate with one or more said gateways, and which uses to communicate with one or more terminals another communication mode, said to be Class A', defined as follows: - the relay transmits beacons (B) at regular intervals, each beacon including representative information for at least one predefined time interval (SL0, SLx) in relation to said beacon; - the relay is listening (701) for any source messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;Petition 870240099175, of 11 / 21 / 2024, page 68 / 166 2 / 16 - in case of a response message from the server equipment provided via said gateway in Class A communication mode, said retransmitter propagates (712) the response message to said terminal using at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently deferred by a defined time (Δ5) in relation to each reception window (Rx1, Rx2) defined in Class A communication mode; and because, upon receiving (701, 702) a said relay of an originating message emitted by a said terminal in Class A communication mode, the said relay performs the following steps: - perform (705) an encapsulation of the originating message in another message destined for the server equipment;- transmit (705) said other message in Class A communication mode, so that at least one said gateway propagates said other message to the server equipment; - in the case of a reply message from the server equipment provided via said gateway that uses (706) for this purpose a reception window defined in Class A communication mode in relation to the transmission of said other message by said retransmitter, perform (707) a decapsulation of another reply message contained in said reply message and propagate (712) said other reply message to said terminal in said other reception window defined in Class A communication mode in relation to the transmission of said source message by said terminal;and because, with the reception (1001) of a message propagated by one or more gateways, when the message Petition 870240099175, of 11 / 21 / 2024, page 69 / 166 3 / 16 received includes a message retransmitted by said retransmitter, the server equipment performs the following steps: - perform (1001) a decapsulation of the retransmitted message; - process (1005) the retransmitted message, in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted; - perform (1006) an encapsulation of the reply message in another reply message to be addressed to the retransmitter; and - transmit (1006) said other reply message to a gateway, in order for said gateway to propagate said other reply message to said relay in said reception window defined in Class A communication mode with respect to the transmission by said terminal of said propagated message.; 2. Process according to claim 1, characterized in that each relay is initialized as follows: - said relay transmits (402) a registration message to the server equipment; - in case of a reply message (403, 404) from the server equipment provided via said gateway, the relay transmits (407) a beacon parameter recovery message to the server equipment; - in case of a reply message (408, 409) from the server equipment provided via said gateway, the relay programs (411) the sending of said beacons and programs (411) the listening during each said time interval, said reply message including representative information for each said time interval.

3. Process according to any of the claims Petition 870240099175, of 11 / 21 / 2024, p. 70 / 166 4 / 16 1 and 2, characterized in that, upon receiving (701,702) a said relay of an originating message emitted by a said terminal in Class A communication mode, the relay performs the following steps: - when the originating message is a register message from the said terminal destined for the server equipment, the said relay propagates the said originating message destined for the server equipment, and upon receiving a reply message from the server equipment, the said relay considers that the said terminal is connected to the said relay; - when the originating message is another message, the said relay propagates the said originating message destined for the server equipment only if the said terminal is connected to the said relay.

4. Process according to claim 3, characterized in that, upon receiving a message propagated by one or more gateways, when the received message includes a message retransmitted by said retransmitter, the server equipment determines (903, 1002) whether the retransmitted message was also received directly via at least one said gateway, and if so, the server equipment performs the following steps: - process (1005) the retransmitted message in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted; - transmit (1006) said reply message to a gateway in order for said gateway to propagate said reply message to said terminal in said reception window defined in Class A communication mode in relation to the transmission by said terminal of the message that was retransmitted; - transmit (1004) to the relay message of Petition 870240099175, of 11 / 21 / 2024, page.71 / 166 5 / 16 disconnection which indicates to said relay that said terminal is no longer connected to said relay; and because the terminal is listening in each said reception window defined in Class A communication mode and in each said reception window defined in Class A communication mode', and when said terminal receives a reply message in said reception window defined in Class A communication mode, said terminal flips (614) in Class A communication mode.

5. Process according to any one of claims 1 to 4, characterized in that two receiving windows (Rx1, Rx2) are defined in Class A communication mode and two receiving windows (Rx'1, Rx'2) are defined in Class A' communication mode.

6. A process according to any one of claims 1 to 5, characterized in that each reception window in Class A communication mode has a longer duration than each corresponding reception window in Class A communication mode.

7. Process according to any one of claims 1 to 6, characterized in that the server equipment (130) comprises at least one relay application (132), each relay application being responsible for carrying out the encapsulations and decapsulations in relation to one or more said relays.

8. Process, implemented by a relay (100), within the scope of a transmission in a communication system that includes a server equipment (130) and at least one gateway (120, 121, 122) connected to the server equipment, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network that uses for this purpose a communication mode, said to be Class A, defined as follows: - said terminal that wishes to communicate with the server equipment directly via said gateway transmits a source message destined for the server equipment; - said terminal is listening for a possible response message from the server equipment propagated via said gateway during at least one reception window (Rx1, Rx2) defined in relation to a transmission time of said originating message by said terminal;characterized by the fact that the communication system includes, on the other hand, said retransmitter (100) which is seen as a terminal by each gateway, said retransmitter using the Class A communication mode to communicate with one or more said gateways, and using to communicate with one or more said gateways, and using to communicate with one or more terminals another communication mode, said in Class A', defined as follows: - the retransmitter transmits beacons (B) at regular intervals, each beacon including representative information for at least one predefined time interval (SL0, SLx) in relation to said beacon; - the retransmitter is listening (701) for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;- in the case of a response message from the server equipment provided via said gateway in Class A communication mode, said relay propagates (712) the response message to said terminal using at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently deferred by a defined time (Δ5) in relation to each reception window (Rx1, Rx2) defined in Class A communication mode; and because, upon receiving (701, 702) a message from a terminal in Class A communication mode, the said relay performs the following steps: - perform (705) an encapsulation of the original message into another message destined for the server equipment;- transmit (705) said other message in Class A communication mode, so that at least one said gateway propagates said other message to the server equipment; - in the case of a reply message from the server equipment provided (706) via said gateway that uses for this purpose a reception window defined in Class A communication mode in relation to the transmission of said other message by said relay, perform (707) a decapsulation of another reply message contained in said reply message and propagate (712) said other reply message to said terminal in said other reception window defined in Class A communication mode in relation to the transmission of said source message by said terminal.; 9. Process, implemented by a terminal (100), within the scope of a transmission in a communication system that includes a server equipment (130) and at least one gateway (120, 121, 122) connected to the server equipment, said terminal being configured to communicate with at least one said gateway via an LPWAN type communication network that uses for this purpose a communication mode, said to be Class A, defined as follows: Petition 870240099175, dated 11 / 21 / 2024, page 74 / 166 8 / 16 - said terminal that wishes to communicate with the server equipment directly via said gateway transmits a source message destined for the server equipment; - said terminal is listening for a possible response message from the server equipment propagated via said gateway during at least one reception window (Rx1, Rx2) defined in relation to a transmission time of said source message by said terminal;characterized by the fact that, the communication system including on the other hand at least one relay (100), said terminal is configured to communicate with each relay according to another communication mode, said to be in Class A', defined as follows: - said terminal receives beacons (B) emitted by said relay, each beacon including representative information of at least one predefined time interval (SL0, SLx) in relation to said beacon; - said terminal that wishes to communicate with the server equipment via said transmitter transmits a source message to the server equipment, only during said time interval;- said terminal is listening (615) for a possible reply message from the server equipment propagated via said gateway during at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently deferred by a time defined in relation to each reception window (Rx1, Rx2) defined in Class A communication mode.; 10. Process, implemented by a server equipment Petition 870240099175, of 11 / 21 / 2024, page 75 / 166 9 / 16 (130), within the scope of a transmission in a communication system that includes said server equipment and at least one gateway (120, 121, 122) connected to the server equipment, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network, characterized by the fact that the communication system which includes on the other hand at least one relay (100), with the reception (1001) of a message propagated by one or more gateways, when the received message includes a message relayed by said relay, the server equipment performs the following steps: - perform (1001) a decapsulation of the relayed message; - process (1005) the retransmitted message, in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted;- perform (1005) an encapsulation of the reply message in another reply message to be addressed to the relay; and - transmit (1006) said other reply message to a gateway, in order that said gateway propagates said other reply message to said relay.; 11. Information storage medium characterized in that it comprises a set of instructions that cause the execution, by a processor (210), of the process as defined in claim 8 or as defined in claim 9 or as defined in claim 10, when the instructions are executed by said processor.

12. Communication system that includes a server equipment (130) and at least one gateway (120, 121, 122) connected to the server equipment, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: - said gateway is configured to receive a message originating from said terminal and propagates said received message to the server equipment; - Upon receiving a response message from the server equipment, the said gateway is configured to propagate the response message to the said terminal using at least one reception window (Rx1, Rx2) defined in relation to the transmission time of the said originating message by the said terminal;characterized by the fact that the communication system includes, on the other hand, at least one relay (100) seen as a terminal for each gateway, each relay being configured to use the Class A communication mode to communicate with one or more said gateways, and to use to communicate with one or more terminals another communication mode, said to be Class A', defined as follows: - the relay is configured to transmit beacons (B) at regular intervals, each beacon including representative information for at least one predefined time interval (SL0, SLx) in relation to said beacon; - the relay is configured to be listening (701) for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;- in case of a reply message from the equipment Petition 870240099175, dated 11 / 21 / 2024, page 77 / 166 11 / 16 server provided via said gateway in Class A communication mode, said relay is configured to propagate (712) the reply message to said terminal using at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently deferred by a defined time (Δ5) in relation to each reception window (Rx1, Rx2) defined in Class A communication mode; and because, with the reception (701, 702) by said relay of an origin message emitted by said terminal in Class A communication mode, said relay implements: - means to effect (705) an encapsulation of the origin message in another message destined for the server equipment;- means for transmitting (705) said other message in Class A communication mode, such that at least one said gateway propagates said other message to the server equipment; - in the case of a reply message (706) from the server equipment provided via said gateway that uses for this purpose a reception window defined in Class A communication mode in relation to the transmission of said other message by said relay, means for effecting (707) an unwrapping of another reply message contained in said reply message and means for propagating (712) said other reply message to said terminal in said other reception window defined in Class A communication mode in relation to the transmission of said source message by said terminal;and because with the reception (1001) of a message Petition 870240099175, of 11 / 21 / 2024, page 78 / 166 12 / 16 propagated by one or more gateways, when the received message includes a message retransmitted by said retransmitter, the server equipment implements: - means to perform (1001) a decapsulation of the retransmitted message; - means to process (1005) the retransmitted message, in order to obtain a reply message to be addressed to the terminal that issued the message that was retransmitted; - means to (1006) perform an encapsulation of the reply message in another reply message to be addressed to the retransmitter; and - means for transmitting (1006) said other reply message to a gateway, in order for said gateway to propagate said other reply message to said relay in said reception window defined in Class A communication mode with respect to the transmission by said terminal of said propagated message.; 13. Relay device (100) intended to be used in a communication system that includes a server device (130) and at least one gateway (120, 121, 122) connected to the server device, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: - said terminal that wishes to communicate with the server device directly via said gateway is configured to transmit a message from source to destination to the server device; - said terminal is configured to listen for any response message from the server equipment propagated via said gateway during at least one reception window (Rx1, Petition 870240099175, dated 11 / 21 / 2024, page 79 / 166 13 / 16 Rx2) defined in relation to a transmission time of said originating message by said terminal;characterized by the fact that, said relay being seen as a terminal by each gateway, said relay is configured to use Class A communication mode to communicate with one or more said gateways, and to use to communicate with one or more terminals another communication mode, said to be 'Class A', defined as follows: - the relay is configured to transmit beacons (B) at regular intervals, each beacon including representative information for at least one predefined time interval in relation to said beacon; - the relay is configured to listen (701) for any originating messages emitted by one or more terminals, destined for the server equipment, only during each said time interval;- in the case of a reply message (706) from the server equipment provided via said gateway in Class A communication mode, said relay is configured to propagate (712) the reply message to said terminal using at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently deferred by a defined time (Δ5) in relation to each reception window (Rx1, Rx2) defined in Class A communication mode; and by the fact that, with the reception (701) by said relay of a source message emitted by said terminal in Class A communication mode, said relay implements: Petition 870240099175, of 11 / 21 / 2024, p. 80 / 166 14 / 16 - means to perform (705) an encapsulation of the source message into another message destined for the server equipment;- means for transmitting (705) said other message in Class A communication mode, such that at least one said gateway propagates said other message to the server equipment; - in the case of a reply message (706) from the server equipment provided via said gateway that uses for this purpose a reception window defined in Class A communication mode in relation to the transmission of said other message by said relay, means for effecting (707) an unwrapping of another reply message contained in said reply message and means for propagating (712) said other reply message to said terminal in said other reception window (Rx'1, Rx'2) defined in Class A communication mode in relation to the transmission of said source message by said terminal.

14. Terminal (110) intended to be used with a communication system that includes a server equipment (130) and at least one gateway (120, 121, 122) connected to the server equipment, said terminal being configured to communicate with at least one said gateway via an LPWAN type communication network that uses a communication mode, said to be Class A, defined as follows: - said terminal that wishes to communicate with the server equipment directly via said gateway is configured to transmit a source message destined for the server equipment; - said terminal is configured to listen for any response message from the server equipment propagated via said gateway during at least one reception window (Rx1, Petition 870240099175, of 11 / 21 / 2024, page 81 / 166 15 / 16 Rx2) defined in relation to a transmission time of said source message by said terminal;characterized by the fact that, the communication system including on the other hand at least one relay (100), said terminal is configured to communicate with each relay according to another communication mode, said to be in Class A', defined as follows: - the terminal is configured to receive beacons (B), emitted by said relay, each beacon including representative information of at least one predefined time interval (SL0, SLx) in relation to said beacon; - said terminal that wishes to communicate with the server equipment via said relay is configured to transmit a source message to the server equipment, only during said time interval;- said terminal is configured to be listening (615) for a possible reply message from the server equipment propagated via said relay during at least one other reception window (Rx'1, Rx'2) defined in relation to a transmission time of said source message by said terminal, each said other reception window (Rx'1, Rx'2) being subsequently delayed by a defined time (Δ5) in relation to each reception window (Rx1, Rx2) defined in Class A communication mode.; 15. Server equipment (130) intended to be used in a communication system that includes said server equipment and at least one gateway (120, 121, 122) connected to the server equipment, each gateway being configured to communicate with at least one terminal (110, 111, 112, 113) via an LPWAN type communication network, characterized in that the communication system Petition 870240099175, dated 11 / 21 / 2024, page.82 / 166 16 / 16 including on the other hand at least one relay (100), with the reception (1001) of a message propagated by one or more gateways, when the received message includes a message relayed by said relay, the server equipment implements: - means to effect (1001) a decapsulation of the relayed message; - means to process (1005) the relayed message, in order to obtain a reply message to be addressed to the terminal that issued the message that was relayed; - means to (1006) effect a encapsulation of the reply message in another reply message to be addressed to the relay; and - means to transmit (1006) said other reply message to a gateway, in order that said gateway propagates said other reply message to said relay. Petition 870240099175, dated 11 / 21 / 2024, pp. 83 / 166.

Images