Communication management device and method

Abstract

The present invention relates to a management device for managing communication over a network to which at least one first terminal (C1) is connected, the management device being configured to: - receive, from the first terminal (C1), at least one item of information relating to an energy state of the terminal (C1) connected to the network via a first interface; - on the basis of at least the item of information relating to an energy state of the first terminal (C1), transmit, to the first terminal (C1), at least one item of connection information for allowing the first terminal (C1) to connect to the network via a second interface.

Description

communication management system and process

[0001] The present invention relates to the management of communications in a network taking into account the consumption of terminals powered by intermittent energy resources, for example supplied by renewable energy sources.

[0002] Communication devices, and in particular connected sensors, can be advantageously connected to renewable energy sources, which are sometimes dependent on climatic or geographical conditions. This is especially true for wind and solar power. These devices may therefore have insufficient energy resources at certain times to function and, in particular, to communicate with other devices. This can occur, for example, when the device discharges faster than it charges.

[0003] One of the constraints of network infrastructures enabling these terminals to communicate is implementing solutions to prevent a terminal from running out of power and therefore shutting down. To achieve this, existing solutions primarily use oversized infrastructure to prevent a terminal from becoming completely depleted of battery. These solutions are based on "worst-case" scenarios and often statically deploy resources to avoid these worst-case scenarios in which a terminal would become inoperable due to a lack of battery. These deployments aim for optimization at the individual terminal level to prevent disconnection due to battery failure, but often lead to an over-provisioning of deployed resources from an overall network perspective. Therefore, there is a need to improve network performance by optimizing power consumption.

[0004] The purpose of this disclosure is to overcome all or part of the disadvantages of the prior art and relates to a communication management device on a network to which at least one first terminal is connected, said management device being configured to: - receive from said first terminal at least one information relating to an energy state of said terminal connected to said network through a first interface, - transmit to said first terminal, based at least on said information relating to an energy state of said first terminal, at least one connection information to allow said first terminal to connect to said network through a second interface.

[0005] Thus, this disclosure may enable the provision of new network infrastructure resources to a device, based on information about its energy consumption, allowing it to advantageously switch from one network interface to another. This can compensate for a lack of energy resources for a device communicating through an initial energy-intensive interface by providing it with network infrastructure that allows it to switch to a less energy-intensive interface. This can also allow a device to switch to a more energy-intensive network interface when its energy status permits.Advantageously, this also allows a device to avoid connecting to the network by default through its least power-intensive interface, thus preventing situations where it might run out of power. Instead, it switches to this interface when power is scarce. This can be particularly relevant when the least power-intensive interface is also the least efficient in terms of throughput, for example.

[0006] Thus, this disclosure enables dynamic management of terminal and network infrastructure in a system where terminals do not benefit from energy charging stability.

[0007] According to some embodiments, said at least one piece of information relating to an energy state includes one or more of the following: - information of insufficient available energy resources, - a battery charge level, - information relating to current consumption, - information relating to a recharge or discharge rate.

[0008] Thus, several criteria relating to an energy state can allow the communication management device to determine whether it is desirable for the first terminal to communicate on its other interface.

[0009] The criterion related to insufficient energy resources can, for example, take into account a threshold below which the terminal no longer has enough energy to operate, for example, over a specific future time window. This threshold can, for example, be determined based on: - an average consumption over a past period, and / or - the terminal's current activity, and / or - energy consumption related to the terminal's current activity, - the amount of energy available from the power source supplying the terminal.

[0010] The battery charge level criterion may include a threshold above or below which the communication management device can transmit connection information to allow the first terminal to connect to the network through a second interface. Thus, when the battery charge level is below a first threshold, the communication management device can transmit connection information to allow the first terminal to connect to the network through a second interface that is less power-intensive than the first interface. Similarly, when the battery charge level is above a second threshold, which is different from or equal to the first threshold, the communication management device can transmit connection information to allow the first terminal to connect to the network through a second interface that is more power-intensive than the first interface.Advantageously, when a more energy-intensive interface is also associated with a more efficient interface in terms of range and / or throughput, this can allow the use of the more efficient interface as soon as the terminal's energy level allows, dynamically, by making available the network resources enabling the terminal to connect to the network via one or the other of the interfaces.

[0011] According to some embodiments, following the receipt of said information relating to an energy state, the device is further configured to: - select at least one relay device to allow said first terminal to establish communication with said network through said second interface and said selected device, said relay device allowing a short-range connection with said first terminal.

[0012] According to some embodiments, said at least one selected relay device is chosen from: - at least one second terminal, - at least one third device of mobile or fixed type.

[0013] A fixed terminal can be understood, for example, as an access gateway or a second terminal that would be within communication range of the first terminal and could allow the first terminal to interface with the network via its second interface capable of communicating with the selected relay device.

[0014] A mobile terminal can be understood, for example, as a drone, a mobile phone, a tablet, or a laptop, which would be within communication range of the first terminal or could receive a request to move near the first terminal and could allow the first terminal to interface with the network via its second interface capable of communicating with the selected relay device.

[0015] According to some embodiments, said at least one connection information includes: - an identifier of one or more relay devices enabling said first terminal to connect via said second interface to said network through said relay devices.

[0016] According to some embodiments, the device is further configured to: - detect a switchover of connection to said network from the first interface to said second interface during a first transfer of data from said terminal through said second interface.

[0017] According to some embodiments, the device is further configured to: - receive from said first terminal, in addition to at least one information relating to an energy state, a request to switch over to said second interface, - transmit to said first terminal, an approval of said switch over.

[0018] According to some embodiments, the device is further configured to: - pending detection of said switchover, provide said terminal with connectivity infrastructure resources configured to allow a connection through said first interface and said second interface.

[0019] According to some embodiments, the device is further configured to: - determine a projection of an energy requirement of said first terminal from said information relating to an energy state.

[0020] Projecting an energy need involves determining the average energy consumption of the terminal and, based on this average consumption, determining current or future energy requirements. For example, one can determine average consumption over a past period and, using this data, project consumption over a future period. This can be particularly predictable when the terminal is a sensor-type device that transmits messages containing captured data, for example, at regular intervals or repeatedly. One can, for instance, determine the energy consumption associated with transmitting a message or a volume of messages over a given period and thus anticipate future terminal energy consumption.

[0021] According to some embodiments, said mobile device is a vehicle, for example an autonomous vehicle, said management device being further configured to: - move said at least one selected vehicle near said first terminal to enable said terminal to establish short-range communication with said selected vehicle.

[0022] According to certain embodiments, the device is further configured to: - obtain a movement plan of said vehicles according to said projection, - obtain a switching plan of said terminals from said first interface to said second interface according to said movement plan and said projection.

[0023] In some embodiments, a travel plan can be represented by a correspondence between a location and a date. This correspondence can be a table matching a location and a date for each mobile device.

[0024] To obtain a routing plan, the communication management system can be understood as follows: - determining the geographic location of one or more relay devices, - determining the distance between the terminal and the geolocated devices, - determining, for at least one geolocated device selected from among the geolocated devices, a routing plan including a route for the selected geolocated device to come within range of the terminal, allowing the terminal to use the selected geolocated device as a relay terminal. The selected geolocated terminal is chosen based on one or more criteria chosen from: - its availability for configuration as a relay terminal, - its distance from the terminal, - its performance rate.

[0025] In some embodiments, the switchover plan can be represented by a correspondence between the identifier of a piece of equipment and the date on which it must switch over. This correspondence can be a table matching the identifier of a piece of equipment with the date on which it must switch over.

[0026] A failover plan can be understood, for example, as a priority management system within a network that includes multiple terminals. The energy state of these terminals is used to select the communication interface they use to communicate on the network. The failover plan may include a time schedule for switching from one terminal interface to another. The communication management system can consider several criteria to determine when a terminal switches its network interface to another network interface.Among these criteria, the communication management system can take one or more of the following criteria: - a priority associated with the terminal, - a battery charge level, - an average energy consumption, - an average consumption over a past time period, and / or - current terminal activity, and / or - energy consumption related to current terminal activity, - an amount of energy available from the energy source powering the terminal.

[0027] According to some embodiments, said first interface is a more energy-consuming interface than said second interface.

[0028] According to some embodiments, said first interface is a long-range network interface and said second interface is a short-range network interface.

[0029] According to some embodiments, said intermittent energy source is a renewable energy source and / or a rechargeable battery.

[0030] According to some embodiments, the terminal can also use energy recovered from streetlights, public ones for example, or from vehicles.

[0031] According to some embodiments, the said intermittent energy source is a renewable energy source chosen from one or more of the following: - solar energy, - wind energy, - hydroelectric energy, - geothermal energy, - wave energy, - ambient thermal energy, - kinetic energy.

[0032] This disclosure also relates to a communication management method on a network to which at least one first terminal is connected, said method comprising: - receiving said first terminal at least one piece of information relating to an energy state of said terminal connected to said network through a first interface, - transmitting to said first terminal, based on said information relating to an energy state of said first terminal, at least one connection information to enable said first terminal to connect to said network through a second interface.

[0033] This disclosure also relates to a computer program comprising instructions for carrying out the steps of the process according to this disclosure, when said program is executed by a computer.

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

[0035] This disclosure also relates to a computer-readable recording medium on which is recorded a computer program containing instructions for carrying out the steps of the process according to this disclosure.

[0036] The information or recording medium can be any entity or device capable of storing the program. For example, the medium may include a storage means, such as a ROM, for example a CD-ROM or a microelectronic circuit ROM, or a magnetic recording means, for example a hard drive.

[0037] On the other hand, the information or recording medium can be a transmissible medium such as an electrical or optical signal, which can be transmitted via an electrical or optical cable, by radio, or by other means. The program according to the invention can, in particular, be uploaded to a network such as the Internet.

[0038] Alternatively, the information or recording medium may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the process in question.

[0039] This disclosure also relates to a terminal connected to a communications network configured to: - transmit at least one piece of information relating to an energy state of said terminal through a first interface, - receive at least one piece of connection information enabling it to connect to said communications network through a second interface, said at least one piece of connection information received being a function of said at least one piece of information relating to an energy state transmitted.

[0040] Other features and advantages of the present invention will become apparent from the description given below, with reference to the accompanying drawings which illustrate an example of an embodiment without any limiting character.

[0041] Lare represents a system according to an embodiment of the present invention.

[0042] [The diagram represents a system according to an embodiment of the present invention in which the relay device is a fixed device,]

[0043] Lare represents a system according to an embodiment of the present invention in which the relay device is a mobile device,

[0044] This diagram represents, in the form of a flowchart, a specific method of implementing a communication management process as described in this disclosure.

[0045] This schematically represents an example of the hardware architecture of a terminal.

[0046] This schematically represents an example of the hardware architecture of an electronic network management device.

[0047] Lare represents an example of a system in which a network management device according to certain embodiments of the invention can be implemented.

[0048] The system includes a device, or terminal device C1, also called client terminal C1. Note that the system may, in some implementations, include a plurality of terminals such as terminal C1.

[0049] Terminal C1 is connected to a power generation device that uses one or more intermittent energy sources, such as renewable energy sources or a rechargeable battery. The terminal can also use energy harvested from streetlights, for example, or from vehicles. Terminal C1 can be a connected sensor; power from a renewable energy source is suitable for such devices, which generally do not require permanent or high-speed network connections and whose energy consumption is typically low or at least limited.

[0050] A solar energy source S1, in the form of solar panels, is shown. It is easy to understand that other renewable energy sources can be used in addition to or as an alternative to solar energy. Examples include: wind energy, hydroelectric energy, geothermal energy, wave energy, ambient thermal energy, and kinetic energy.

[0051] Renewable energy is converted into electrical energy to power device C1.

[0052] The load on a C1 terminal can depend on its environment, which is linked to the power output of the renewable energy source to which it is connected. Renewable energy sources can indeed be highly dependent on the weather. A solar-powered C1 device has limited energy resources if the weather is not sunny. It includes at least one means of energy storage, such as a rechargeable battery.

[0053] The hardware architecture of device C1 is shown. Device C1 also includes at least two network interfaces, IFS and IFL.

[0054] The IFL interface, for example, can be a long-range interface, and the IFS interface, for example, can be a short-range interface. Of the at least two network interfaces, at least two are connected to networks using different network infrastructures to communicate over a network, such as a wide area network managed by an operator. These two network interfaces connected to networks with different infrastructures require or use different amounts of energy resources for their operation. In other words, these network interfaces have different energy profiles.

[0055] According to some embodiments, the IFL network interface is a network interface requiring more energy resources to operate than the IFS interface.

[0056] According to some embodiments, the IFL network interface is a so-called long-range network interface and the IFS network interface is a short-range network interface.

[0057] In some embodiments, the IFS interface can be of type "BLE" for "Bluetooth". ® Low Energy (Low Energy) is used, for example, to connect smart devices and is known for its low energy consumption. The IFS interface can also comply with the IEEE 802.15.4 protocol.

[0058] In some embodiments, the IFL interface is a LoRa-type radio interface ® (English acronym for "Long Range") whose energy consumption is higher than that of the "BLE" type IFS interface. In some embodiments, the IFL interface can also be a Wi-Fi Halow compliant interface. ® LTE.

[0059] . The client terminal C1 communicates through (via) the IFL interface using an INFRAL network infrastructure comprising at least one network device.

[0060] The client terminal C1 communicates through (via) the IFS interface using an INFRAS network infrastructure comprising at least one network device.

[0061] Device C1 may have insufficient energy to communicate via the INFRAL interface, as it is powered by a renewable, and therefore intermittent, energy source dependent on natural resources. Consequently, it may discharge faster than it charges.

[0062] It can also determine a projection of its energy consumption, based for example on a consumption history, or on future consumption, and anticipate a possible energy shortage to maintain communication on the first interface when it uses the first interface or will use the first interface.

[0063] The INFRAL network infrastructure includes permanently deployed network equipment / devices / servers to enable communication between terminal C1 and other terminals on the network.

[0064] The INFRAS network infrastructure is based on network equipment / devices / servers, such as mobile devices or a fixed device like an access gateway, to enable communication between terminal C1 and other terminals on the network. Mobile devices include cell phones, drones, other connected vehicles, and connected virtual reality headsets—in short, devices equipped with a network interface that can move geographically. These devices act as relays, establishing a connection between terminal C1 and the network.

[0065] The network operator's equipment includes, in particular, a communication management device (GR). The hardware architecture of the GR communication management device is shown in Figure 1. The GR management device is configured to implement the communication management process as described in Figure 2.

[0066] The GR communication management system can be connected to the INFRAL and INFRAS network infrastructures through a variety of network equipment.

[0067] In one embodiment, the GR communication management device is located on a network interconnecting client terminals. It can be connected to client terminals, for example via an IP network (wired or wireless), such as an Internet of Things (IoT) network, and also connected to an operator's network, such as a cellular network or other technology. For example, it can be located in an access gateway between an IoT network and a cellular network.

[0068] According to another embodiment, the GR communication management device is located in a core network equipment of an operator.

[0069] The GR communication management device is configured to: - receive from the first client terminal C1 at least one piece of information relating to its energy state when it is connected to the network through the first interface, - transmit to the first client terminal C1, depending on the information relating to the energy state, at least one connection information to allow the first client terminal C1 to connect to the network through the second interface.

[0070] According to some embodiments, said at least one piece of information relating to an energy state includes one or more of the following: - information of insufficient available energy resources, - a battery charge level, - information relating to current consumption, - information relating to a recharge or discharge rate.

[0071] The communication management system GR can also, upon receiving information relating to an energy state: - select at least one relay device to allow the first client terminal C1 to establish communication with the network through the second interface and the selected relay device. In one embodiment, the relay device allows a short-range connection with the first terminal.

[0072] The selection of the relay device can be based on one or more criteria.

[0073] When selecting a relay terminal from a set of relay terminals, one of the selection criteria may be related to the proximity of an INFRAS device (mobile or fixed) to the client terminal. The selected device may be the one closest to terminal C1. It may also be a device determined from a mobile device movement plan.

[0074] By movement plan, we can understand that the communication management device - determines a geographical location of one or more relay devices, - determines a distance between the client terminal and the geo-located devices, - determines, for at least one geo-located device selected from among the geo-located devices, a movement plan including a movement route of the geo-located device selected to be within range of the client terminal to allow the client terminal to use the geo-located device selected as a relay terminal.

[0075] The geo-located terminal selected is chosen based on one or more criteria chosen from: - availability to be configured as a relay terminal, - distance from the client terminal, - performance rate.

[0076] When selecting the relay terminal from a set of fixed or mobile terminals, the selection criterion can be chosen from one or more of the following: - the performance of the relay terminal, in terms of bandwidth, or in terms of energy capacity - the availability of the relay terminal, - the function of the relay terminal, - the network interface of the relay terminal.

[0077] When fixed and mobile relay terminals are available, the selection criteria mentioned above can be combined to select one of the terminals from among the fixed or mobile terminals.

[0078] The selection can also be based on information received from the client terminal. Client terminal C1 can select which relay terminal to use in order to utilize the second IFS interface and transmit information to the communication management device GR, at least regarding the identity of the selected client terminal C1. To do this, client terminal C1 may have information about the terminals that can serve as its relay. Such a relay terminal could, for example, be a network gateway.

[0079] A mobile device deployment plan can be established to provide a C1 terminal in the fleet with one or more relay devices from the INFRAS infrastructure, enabling the C1 terminal to communicate on the network using its IFS interface. This deployment plan can optimize the spatial and temporal coverage of C1 client terminals.

[0080] Thus, guidance information for mobile relay devices can be transmitted by the GR communication management device to these mobile relay devices, enabling them to move closer to the client terminal C1 and establish communication between the client terminal C1 and the relay device. This communication can be based, as mentioned previously, on short-range communication.

[0081] A switchover plan for the C1 terminals in the fleet can be established by the GR communication management device to determine, based on their energy state or a projection of their energy state, a switchover time from the IFL interface to the IFS interface.

[0082] A failover plan can be understood, for example, as a priority management system within a network that includes multiple client terminals. The power status of these terminals is used to select the communication interface they use to communicate on the network. The failover plan may include a schedule for switching from one interface to another for the client terminal(s). The communication management system can consider several criteria to determine when a client terminal switches its network interface to another network interface.Among these criteria, the communication management system can take one or more of the following criteria: - a priority associated with the client terminal, - a battery charge level, - an average energy consumption, - an average consumption over a past time period, and / or - current activity of the client terminal, and / or - energy consumption related to current activity of the client terminal, - an amount of energy available from the energy source powering the terminal.

[0083] The switchover and relocation plans can be updated regularly, or periodically, based on the energy status of each C1 customer terminal and / or based on the terminal class and / or based on information about the interface it uses and / or based on the location of mobile relay devices.

[0084] When, following guidance information received, a mobile relay device, such as a drone, arrives near a C1 client terminal to serve as INFRAS infrastructure, it can inform the C1 client terminal that it is available to act as a relay. For example, it can send a wake-up message to notify the terminal.

[0085] The client terminal C1 initiates a short-range radio broadcast communication of IP messages to the IP address of the communication management device GR in order to connect to the selected relay device based on a SW_TOKEN switchover token previously established by the management device.

[0086] A proximity connection is established between the client terminal C1 and the selected relay device which routes messages from the client terminal C1 to the communication management device GR and vice versa and given that these messages contain the same session identifier ID_SESSION as the messages exchanged via the IFL interface, the association of the old connection and the new connection can be established.

[0087] The client terminal sends a first message of Type0 or Type1 (these messages will be described below with reference to figures 2 and 3) to the GR communication management device via the IFS interface and the selected relay device.

[0088] The GR communication management device receives this message, which serves as acknowledgment of the switchover from the first network interface to the second network interface. If the ID_SESSION of the messages previously exchanged before the switchover is the same as the ID_SESSION of the new message arriving after the switchover, the GR communication management device validates the switchover of the client terminal C1 to the INFRAS infrastructure and updates the connection information of the client terminals C1.

[0089] The operation between client terminal C1 and the communication management device GR continues on the second interface until the conditions for switching back to the first interface are met. Switching from the second interface back to the first interface can be done in the same way as switching from the first interface back to the second interface.

[0090] The selection of a relay device may be accompanied by the activation of intermittent relays, the provision of local means of communication, and a request to other client terminals other than terminal C1 to serve as a relay for terminal C1.

[0091] The GR communication management system can also maintain a classification of client terminals based on energy status information received from the devices. It can also receive client terminal classification information. In addition to energy status, it can also consider consumption projections or energy requirements, based on energy status information and / or historical consumption data or available information regarding future consumption or energy requirements, to establish the classification.

[0092] This classification can contain 4 classes and in particular: - a first class includes client terminals whose energy consumption is greater than the energy recharge - a second class includes client terminals whose energy consumption is less than the energy recharge - a third class includes terminals whose operation is stopped, - a fourth class includes terminals in transition from the first class to the second class.

[0093] The GR communication management system can deploy network infrastructure resources to allow a C1 client terminal to connect to the network through the second interface, depending on its classification. Infrastructure resources can be understood as providing at least one relay terminal.

[0094] When a C1 client terminal belongs to the first class, it is considered to have insufficient or soon insufficient energy capacity to meet current or projected energy needs. The GR communication management device can transmit at least one connection information to the first C1 client terminal to allow it to connect to the network through the second interface.

[0095] When a C1 client terminal belongs to the second class, it is considered to be a terminal whose energy capacity is sufficient to allow the first C1 client terminal to connect or remain connected to the first interface.

[0096] When a C1 client terminal belongs to the third class, it is considered to be discharged. The GR communication management device associates it with the first or second classification when it is in operation, that is, when its charge level is positive or has exceeded a predetermined charge level.

[0097] When a C1 client terminal belongs to the fourth class, it has received at least one connection information to enable it to connect to the network through the second interface and the GR communication management device has not yet received an acknowledgment from the first terminal.

[0098] In general, the GR communication management system detects a connection switchover from the first interface to the second interface during the first data transfer from client terminal C1 through the second interface. No dedicated acknowledgment is required.

[0099] The GR communication management device, while waiting for failover detection, provides the client terminal with bimodal connectivity infrastructure resources configured to allow connection through the first and second interfaces.

[0100] In some embodiments, the communication management device GR can receive from the first client terminal C1, in addition to at least one energy state information, a failover request to the second interface. The network manager can then transmit a failover approval to client terminal C1. It can also update the class of client terminal C1. This can occur, for example, when terminal C1 is in a critical energy state and can no longer maintain communication via the IFL interface.

[0101] When a client terminal C1 uses its second interface and its power status allows it to communicate again through the first interface, the network manager can transmit, based on the power status information, at least one connection instruction to allow the first client terminal C1 to connect to the network through the first interface. This can advantageously allow client terminal C1 to benefit from better communication performance when the first interface performs better than the second. Thus, dynamic connection management is implemented based on the client terminal's power status.

[0102] Lare represents a first example of application, the C1 client terminal can be an environmental sensor installed for a long period to make periodic readings.

[0103] This sensor is powered by a solar panel S1, the energy from which is converted into electrical energy and stored in device C1. Its IFL interface is an LTE-M type interface, and its IFS interface is a "Thread" type interface compatible with the IEEE 802.15.4 protocol. The LTE-M interface consumes more energy than the Thread interface. However, the LTE-M interface offers better performance than the Thread interface.

[0104] A session identifier, ID_SESSION, is also included in a header field of messages exchanged between the client terminal C1 and the network manager. This session identifier can be retained in the messages during a switchover from an IFL interface to an IFS interface or vice versa.

[0105] By default, the C1 sensor uses its IFL interface to transmit data related to its periodic readings, using MESS-TYPE0 messages. MESS-TYPE0 messages are regular (application-specific) messages linked to the application and implemented by the C1 client terminal network.

[0106] It can be noted that the GR communication management device can also transmit application-related MESS-TYPE0 messages to the client terminal C1.

[0107] In some cases, solar energy is no longer sufficient to enable the use of the IFL interface, for example, in the event of insufficient sunlight, and / or when the battery can no longer charge and contains an insufficient charge to provide the energy required for the IFL interface to function. The sensor C1 then transmits information about its energy status to the communication management device GR via its IFL interface using a MESS-TYPE1a message. This information allows the communication management device GR to perform the necessary calculations (estimates and projections) concerning the client terminal C1 in order to anticipate / suggest and / or command a possible switchover between the IFL and IFS interfaces. In some embodiments, the energy status information may include a network interface switchover request.

[0108] According to some embodiments, this information is transmitted, in MESS-TYPE1a messages, on a regular or periodic basis to the GR communication management device, and not only when the energy resources of terminal C1 are insufficient.

[0109] MESS-Type1a messages enable the communication management system to manage client terminal connectivity based on their energy resources. This information allows the communication management system to gain an overview of the energy situation along with projections of its evolution.

[0110] Terminal C1 can also transmit information about an INFRAS infrastructure access gateway that it has discovered can act as a relay to switch over to the IFS interface in a MESS-TYPE1b message, for example, when its power state is insufficient. MESS-TYPE1b messages can transmit connectivity information regarding the alternative connectivity mode to the current mode between the communication management device (GR) and client terminal C1. For example, this information might correspond to the discovery of the radio neighborhood / landscape represented either by relay devices near a client terminal C1 or by relay devices accessible based on the connectivity mode to which it would likely switch over.

[0111] Terminal C1 can also transmit additional information to the GR communication management device, enabling it to obtain information on the availability of the INFRAL network infrastructure and its evolution. It can also transmit information about an access gateway it wishes to use. This information allows the GR communication management device to configure the access gateway. These MESS-TYPE1b messages can be transmitted at any time, for example, as soon as client terminal C1 connects to the network when it detects available access gateways. The GR communication management device can store this type of data in a database to which it is connected.

[0112] Communication management device: According to one embodiment, depending on the energy state of terminal C1, the communication management device GR can request authorization from a thread network manager to open the thread network of the access gateway to client terminal C1 by transmitting an OUV-THREAD message. To do this, it transmits an OUV-THREAD message to the thread network containing information about terminal C1 and at least its identifier, as well as information about the thread network to be used.

[0113] In one embodiment, the thread network manager transmits to the selected access gateway authorization for client terminal C1 to communicate with the thread network via an AUTH-OUV-THREAD message. The access gateway can transmit information enabling client terminal C1 to connect to the thread network via an INFO-CONNECT1 message.

[0114] The thread network manager then transmits an acknowledgment of thread network usage by the client terminal to the GR communication management device via a VALID message. Along with the acknowledgment, it transmits the information enabling client terminal C1 to connect to the thread network.

[0115] The communication management device transmits to the client terminal C1 an authorization (or an acknowledgment) to use its IFS interface and the configuration information allowing it to connect to the network through the access gateway, via an INFO-CONNECT2 message.

[0116] It can also transmit configuration information to the access gateway, not shown.

[0117] Upon receiving the configuration information, the C1 sensor connects to the access gateway's thread network and communicates through this interface to transmit MESS-TYPE0, MESS-TYPE1 and subsequent messages until the next interface switchover.

[0118] The GR communication management device detects the switchover when it sees communications, via MESS-TYPE0 messages, passing over the thread network.

[0119] This represents a second application example, in which a plurality of C1 client terminals, such as a fleet of data collection terminals, are deployed. To ensure the integrity of the application using this data, the C1 client terminals transmit it to a centralized processing information system with predetermined intervals. To do this, the C1 terminals use their IFL interface, of the LoRa type. ®For example, the INFRAL infrastructure may include a plurality of fixed access gateways (PA).

[0120] These terminals are energy self-sufficient and include batteries charged from solar energy, and whose charge can therefore be highly dependent on climatic conditions.

[0121] In order to compensate for a total battery discharge which would result in the cessation of data transmission, the C1 terminals benefit from a short-range IFS interface, for example a BLE interface, which is less energy-intensive and allows, in particular for example during a period of battery charging, to limit energy consumption.

[0122] A fleet of drones, or other mobile or fixed devices, can constitute the INFRAS infrastructure.

[0123] Client terminals, the network manager and devices present in the INFRAS and INFRAL network infrastructures have a unique address allowing them to be identified.

[0124] A session identifier, ID_SESSION, is also included in a header field of messages exchanged between the client terminal C1 and the network manager. This session identifier can be retained in the messages during a switchover from an IFL interface to an IFS interface or vice versa.

[0125] In this application example, communications between the client terminal C1 and the communication management device GR use the IP protocol (acronym for "Internet Protocol").

[0126] The devices in the INFRAL infrastructure are devices that have an IP router role.

[0127] By default, a C1 sensor uses its IFL interface to transmit data related to its periodic readings, using MESS-TYPE0 messages. MESS-TYPE0 messages are regular (application-specific) messages linked to the application and implemented by the C1 client terminal network.

[0128] It can be noted that the GR communication management device can also transmit application-related MESS-TYPE0 messages to the client terminal C1.

[0129] In some cases, solar energy is no longer sufficient to enable the use of the IFL interface, for example, in the event of insufficient sunlight, and / or when the battery can no longer charge and contains an insufficient charge to provide the energy required for the IFL interface to function. The sensor C1 then transmits information about its energy status to the communication management device GR via its IFL interface using a MESS-TYPE1a message. This information allows the communication management device GR to perform the necessary calculations (estimates and projections) concerning the client terminal C1 in order to anticipate / suggest and / or command a possible switchover between the IFL and IFS interfaces. In some embodiments, the energy status information may include a network interface switchover request.

[0130] According to some embodiments, this information is transmitted, in MESS-TYPE1a messages, on a regular or periodic basis to the GR communication management device, and not only when the energy resources of terminal C1 are insufficient or below a determined threshold.

[0131] Type 1a messages enable the communication management system to manage the connectivity of client terminals based on their energy resources. This information allows the communication management system to gain an overview of the energy situation along with projections of its evolution.

[0132] Terminal C1 can also transmit information about an INFRAS infrastructure access gateway that it has discovered can act as a relay to switch over to the IFS interface in a MESS-TYPE1b message, for example, when its power state is insufficient. MESS-TYPE1b messages can transmit connectivity information regarding the alternative connectivity mode to the current mode between the communication management device (GR) and client terminal C1. For example, this information might correspond to the discovery of the radio neighborhood / landscape represented either by relay devices near a client terminal C1 or by relay devices accessible based on the connectivity mode to which it would likely switch over.

[0133] Terminal C1 can also transmit additional information to the GR communication management device, enabling it to obtain information on the availability of the INFRAL network infrastructure and its evolution. It can also transmit information about an access gateway it wishes to use. This information allows the GR communication management device to configure the access gateway. These MESS-TYPE1b messages can be transmitted at any time, for example, as soon as client terminal C1 connects to the network when it detects available access gateways. The GR communication management device can store this type of data in a database to which it is connected.

[0134] The GR communication management system obtains a comprehensive view of the energy status of the fleet's C1 terminals and can thus select a relay device from among those available in the INFRAS infrastructure. It can also establish a relocation plan and a failover plan for the mobile terminals.

[0135] The GR communication management device transmits a MESS-Type2 message to a client terminal C1, requesting it to switch from its IFL interface to its IFS interface. In addition to the ID_SESSION already present in its header, the transmitted MESS-Type2 message includes connection information to allow client terminal C1 to connect to the network through the IFS interface using the selected relay terminal. It contains information to identify the selected relay terminal, such as its IP address.

[0136] Devices on the INFRAS network interface can also transmit information about their availability, bandwidth, or performance to the network manager (GR) in MESS-TYPE-INFRAS messages. This can advantageously allow the network manager (GR) to have up-to-date information on the INFRAS infrastructure endpoints.

[0137] The MESS-Type2 message may also include a failover token, SW_TOKEN, established by the GR communication management device and communicated to the client terminal C1 and also to the elements of the INFRAS infrastructure in order to enable a fast link between the client terminal C1 and a selected relay device of this INFRAS infrastructure.

[0138] The MESS-Type2 message is also transmitted to the devices of the INFRAS infrastructure in order to allow a rapid failover between the selected relay device in the INFRAS infrastructure and the client terminal.

[0139] In one variant, the C1 client terminal itself requests a switch from the first interface to the second interface, transmitting a MESS-TYPE1c request to the GR communication management device to obtain the switchover token, SW_TOKEN. This variant allows the decision to be delegated in a distributed manner to the C1 client devices.

[0140] According to a variant, not shown in the diagram, the communication management device GR does not select the relay device from the INFRAS infrastructure to use but transmits connection information to the client terminal C1 in the form of the SW_TOKEN failover token. The client terminal C1 then selects a relay device from among those available in the INFRAS infrastructure. The client terminal C1 transmits the SW_TOKEN to the selected relay device so that the relay device is accepted as a relay device by the communication management device GR.

[0141] In one variant, the MESS-TYPE2 message contains not a failover request for its interface, but a failover suggestion. Upon receiving a MESS-TYPE2 message suggesting a failover, the client terminal determines the availability of a relay device in the INFRAS infrastructure. The client terminal C1 can then transmit a MESS-TYPE1b message to inform the communication management device of the relay device's availability. The communication management device can then accept the failover to the available device selected by the client terminal and transmit a MESS-TYPE2 message containing a failover request, as previously mentioned.

[0142] The diagram represents, in flowchart form, a specific implementation of a communication management process as described in this disclosure. The process is implemented in a communication management device (CMD) within a system as described opposite the diagram. The various embodiments described opposite the diagram also apply to the process. The messages exchanged as described above can be used in the exchanges mentioned below in the process.

[0143] The process includes a step E1 during which the network management device GR receives at least one piece of information representative of the energy state of at least one customer terminal C1. This information may include, in particular: - information indicating insufficient available energy resources, - a battery charge level, - information relating to current consumption, - information relating to a recharge or discharge rate

[0144] The C1 client terminal is connected to the GR network management device via its IFL interface. It can transmit this information on an ad hoc basis, for example when its energy status is insufficient, or on a regular or periodic basis.

[0145] Insufficient energy state can be understood as an energy state that is insufficient to communicate through the IFL interface.

[0146] The process may include an optional step E2, in which it establishes energy consumption projections for at least one customer terminal. It may establish these projections from recorded historical data. Alternatively, it may also receive projections from customer terminals and record these projections.

[0147] The client terminal C1 can decide, according to a first option, depending on its energy state, to switch from its IFL interface to its IFS interface.

[0148] In this option, client terminal C1 does not wait for the network manager to request a change of network interface but makes the decision itself. This can occur when the power state of client terminal C1 is critical to ensuring communication through the first interface.

[0149] This occurs, for example, when the IFS interface requires less power to operate than the IFL interface. The process may include a step E3, during which the network manager GR receives information from client terminal C1 regarding a request to activate the second interface. It can then transmit a failover approval to client terminal C1.

[0150] Following step E3, the process includes a step E9 described later.

[0151] The process includes, according to a second option, a step E4 in which the communication management device GR, depending on the energy status of terminal C1, decides to switch its communication interface from the first interface to the second interface. This decision can be based, for example, on a comparison of the battery charge against a threshold or on changes in consumption history, depending on the evolution of the energy status over time.

[0152] This decision can also take into account an energy state of a plurality of terminals and a consolidation of the energy state of a plurality of terminals when the GR communication management device manages several C1 terminals.

[0153] To this end, the process may include a step E5 for classifying C1 client terminals, as described previously in relation to [reference missing] and not repeated here. This classification step is implemented continuously and not sequentially with respect to the other steps of the process, the classification being updated upon receipt of a message relating to the energy status of a C1 client terminal.

[0154] The process may also include a step E6 for determining a relocation plan for the INFRAS infrastructure's mobile devices, to make available to a C1 terminal in the fleet one or more INFRAS infrastructure relay devices, enabling the C1 terminal to communicate on the network using its IFS interface. This relocation plan can optimize the spatial and temporal coverage of the C1 client terminals.

[0155] Thus, guidance information for mobile relay devices can be transmitted by the GR communication management device to these mobile relay devices, enabling them to move closer to the client terminal C1 and establish communication between the client terminal C1 and the relay device. This communication can be based, as mentioned previously, on short-range communication.

[0156] According to some variants, the process may include a step (not shown) in which the client terminal C1 transmits at least one piece of information relating to at least one type of network accessible through the second interface to communicate via the INFRAS network infrastructure.

[0157] The process may also include a step E7 of determining a switchover plan for the C1 terminals of the fleet to determine, based on their energy state or a projection of their energy state, a switchover time from the IFL interface to the IFS interface.

[0158] The switching and relocation plans can be updated regularly, or periodically, based on the energy status of each C1 customer terminal and / or the terminal class and / or information about the interface it uses and / or the location of the mobile relay devices. For this purpose, steps E6 and E7 are not sequential to each other or to the other steps of the process.

[0159] The process includes a step E8 during which the communication management device GR selects a relay terminal from among the relay terminals of the INFRAS infrastructure to enable the client terminal C1 to communicate on the network through its IFS interface via the INFRAS network infrastructure.

[0160] The selection of the relay device can be based on one or more criteria. One criterion may be related to the proximity of an INFRAS mobile device to the client terminal. The selected device may be the one closest to terminal C1. It may also be a device determined from a mobile device movement plan.

[0161] Another selection criterion may be the availability of a terminal that can serve as a relay, or the performance of the selected device, in terms of bandwidth and energy capacity.

[0162] The selection can also be based on information received from the client terminal. In one variant, client terminal C1 can select which relay terminal to use in order to access the second IFS interface and transmit information to the communication management device GR, including at least the identity of the selected client terminal C1. To do this, client terminal C1 may have information about the terminals that can act as relays. Such a relay terminal could, for example, be a network gateway.

[0163] The process may include a step E9 during which the communication management device GR transmits a request to at least one selected device asking it to act as a relay device for the client terminal C1. If the selected relay device acknowledges, then the process proceeds to step E10; otherwise, another relay device is selected and steps E8 and E9 are repeated.

[0164] The process includes a step E10 during which the communication management device GR transmits to the client terminal C1, at least one connection information to allow the client terminal C1 to connect to the network through the IFS interface.

[0165] A connection message may include an identifier for one or more relay devices, allowing the first client terminal C1 to connect to the network via the second interface through said relay devices. A connection message may also include a token authorizing the client terminal C1 to switch to a second interface, while still allowing it to select a relay device to communicate on the second network through its IFS interface, according to the variant described above in which the client terminal C1 selects the relay device.

[0166] The process may include a step E11 in which the network manager, while awaiting detection of interface failover by client terminal C1, provides the client terminal with bimodal connectivity infrastructure resources configured to allow connection through both the first and second interfaces. It thus maintains the INFRAL and INFRAS connection resources (through the selected relay terminal) available simultaneously.

[0167] The process includes a step E12 during which the network manager detects the failover when it observes communication from terminal C1 via its IFS interface.

[0168] The process described above can also be applied to switching from the second interface to the first interface, depending on the energy status of terminal C1. When terminal C1 reaches a sufficient charge level and is connected via its second interface, the GR communication management device can send it a request to switch interfaces, and the steps described above can be repeated, possibly in a simpler manner without selecting a relay terminal if the INFRAL infrastructure is fixed and always available to ensure terminal C1's connection to the network. Terminal C1 can itself decide to switch to its first network interface and inform or request authorization from the GR communication management device.

[0169] The diagram schematically represents the hardware architecture of a C1 client terminal. As illustrated by the diagram, the C1 client terminal has the hardware architecture of a computer.

[0170] Thus, the client terminal C1 includes, in particular, a processor 31, a random access memory 32, a read-only memory 33, and a non-volatile memory 34. It also includes two communication interfaces 35 and 36, representing the IFL and IFS communication interfaces, respectively. It may also include one or more sensors 37 for obtaining data that is transmitted via the IFL or IFS interfaces.

[0171] Read-only memory 33 constitutes a storage medium conforming to at least one embodiment of this disclosure, readable by the processor 31, and on which is stored a computer program PROG1 conforming to at least one embodiment of this disclosure, comprising instructions for executing steps implemented in the terminal C1 according to at least one embodiment of this disclosure. The PROG1 program defines functional modules of the device.

[0172] The diagram schematically represents the hardware architecture of a GR communication management device. As illustrated by the diagram, the GR communication management device has the hardware architecture of a computer.

[0173] Thus, the communication management device GR includes, in particular, a processor 41, a random access memory 42, a read-only memory 43 and a non-volatile memory 44. It also includes a communication interface 45.

[0174] Read-only memory 43 constitutes a storage medium conforming to at least one embodiment of this disclosure, readable by the processor 41, and on which is stored a computer program PROG conforming to at least one embodiment of this disclosure, comprising instructions for executing steps of the communication management process according to at least one embodiment of this disclosure. The PROG program defines functional modules of the device.

Claims

Communication management device (CMD) on a network to which at least one first terminal (C1) is connected said management device being configured to: - receive from said first terminal (C1) at least one information relating to an energy state of said terminal (C1) connected to said network through a first interface, - transmit to said first terminal (C1), according to at least said information relating to an energy state of said first terminal (C1), at least one connection information to allow said first terminal (C1) to connect to said network through a second interface. A device according to claim 1, wherein said at least one piece of information relating to an energy state comprises one or more of the following: - information on insufficient available energy resources, - a battery charge level, - information relating to current consumption, - information relating to a recharge or discharge rate Device according to any one of the preceding claims wherein, following the receipt of said information relating to an energy state, the device is further configured to: - select at least one relay device to enable said first terminal (C1) to establish communication with said network through said second interface and said selected device, said relay device enabling a short-range connection with said first terminal (C1). Device according to claim 4 in which said at least one selected relay device is chosen from:- at least one second terminal (C1),- at least one mobile device. Device according to any one of the preceding claims wherein said at least one connection information comprises: - an identifier of one or more relay devices enabling said first terminal (C1) to connect via said second interface to said network through said relay devices. Device according to one of the preceding claims further configured to:- detect a switchover of connection of said network from the first interface to said second interface during a first transfer of data of said terminal (C1) through said second interface. Device according to one of the preceding claims further configured to: - receive said first terminal (C1) in addition to at least one information relating to an energy state, a request to switch over to said second interface, - transmit to said first terminal (C1), an approval of said switch over. Device according to claim 6 further configured to: - pending detection of said switchover, provide said terminal (C1) with bimodal connectivity infrastructure resources configured to allow connection through said first interface and said second interface. Device according to any one of the preceding claims configured to determine a projection of an energy requirement of said first terminal (C1) from said information relating to an energy state. Device according to claim 4 wherein said mobile device is a vehicle, said management device being further configured to:- move said at least one selected vehicle in the vicinity of said first terminal (C1) to enable said terminal (C1) to establish short-range communication with said selected vehicle. Device according to any one of the preceding claims wherein said first interface is a more energy-consuming interface than said second interface. A method for managing communication on a network to which at least one first terminal (C1) is connected, said method comprising: - receiving from said first terminal (C1) at least one piece of information relating to an energy state of said terminal (C1) connected to said network through a first interface, - transmitting to said first terminal (C1), according to said information relating to an energy state of said first terminal (C1), at least one connection information to enable said first terminal (C1) to connect to said network through a second interface. Terminal connected to a communications network configured to: - transmit at least one piece of information relating to an energy state of said terminal (C1) through a first interface, - receive at least one connection information enabling it to connect to said communication network through a second interface, said at least one connection information received being a function of said at least one piece of information relating to an energy state transmitted. Computer program comprising instructions for carrying out the steps of the process according to claim 12, when said program is executed by a computer. Computer-readable recording medium on which is recorded a computer program comprising instructions for carrying out the steps of the process according to claim 12.

Images