communication management system and process

Abstract

Communication Management Device and Method The present invention relates to a communication management device 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 piece of information relating to an energy state of said terminal (C1) connected to said network through a first interface, - transmit to said first terminal (C1), based on at least said information relating to an energy state of said first terminal (C1), at least one connection piece of information to allow said first terminal (C1) to connect to said network through a second interface. Figure for the abstract: Fig. 1.

Description

Title of the invention: Communication management device and method. Technical field.

[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. Previous technique

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

[0003] One of the constraints of network infrastructures enabling these terminals to communicate is the implementation of solutions to prevent a terminal from running out of power and therefore shutting down. To achieve this, known solutions primarily use oversized infrastructures to prevent a terminal from running completely out of power. These solutions are based on "worst-case" scenarios and deploy, often statically, 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 level of each terminal to prevent this disconnection due to a lack of battery, but often lead to an oversizing of the resources deployed from an overall network perspective. Therefore, there is a need to improve network operation by optimizing their power consumption. Description of the invention

[0004] The purpose of this disclosure is to overcome all or part of the drawbacks 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 piece of information relating to the 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 can make new network infrastructure resources available to a device, based on information relating to its energy consumption, thereby advantageously enabling it to switch from one network interface to another. This can compensate for a lack of energy resources for a device when it communicates 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 can also prevent a terminal from defaulting to its least power-intensive interface to avoid a power-depletion situation, instead switching to that 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, the present disclosure enables dynamic management of terminal and network infrastructure management in a system in which terminals do not benefit from stability in terms of energy charging.

[0007] According to certain embodiments, said at least one piece of information relating to an energy state comprises one or more of the following: - Information indicating 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 may, for example, take into account a threshold below which the terminal no longer has enough energy resources to operate, for example, over a specified future time window. This threshold may, for example, be determined based on: - average consumption over a past period, and / or - current terminal activity, and / or - energy consumption related to the terminal's normal operation, - of an amount of energy available from the energy source powering the terminal.

[0010] The criterion relating to the battery charge level may include a threshold above or below which the communication management device may 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 may 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 may 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 certain 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 certain embodiments, said at least one selected relay device is chosen from: - at least one second terminal, - at least one third-party device, either mobile or fixed.

[0013] By fixed terminal type, we can mean for example an access gateway or a second terminal which 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] By mobile terminal, we can mean for example, a drone, a mobile phone, a tablet, 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 certain embodiments, said at least one connection information comprises: - an identifier of one or more relay devices allowing 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 certain embodiments, the device is further configured to: - receive from said first terminal, in addition to at least one piece of 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 certain 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 certain 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 requirement can be understood as determining the average energy consumption of the terminal and, based on this average consumption, determining a current or future energy requirement. For example, one can determine an average consumption over a past period and, based on this determination, establish a projection of consumption over a future period. This can be particularly predictable when the terminal is a sensor-type device that transmits messages comprising captured data, for example, at regular intervals or repeatedly. One can, for example, determine the energy consumption associated with transmitting a message or a volume of messages over a period and thus anticipate future consumption of the terminal.

[0021] According to certain 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 for said vehicles as a function of said projection, - obtain a switchover plan for said terminals from said first interface to said second interface according to said movement plan and said projection.

[0023] According to 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 travel plan, it can be understood that the communication management system - determines the geographical location of one or more relay devices, - determines the distance between the terminal and the geolocated devices, - determines, for at least one geolocated device selected from among the geolocated devices, a movement plan including a route for the selected geolocated device to move within range of the terminal, enabling the terminal to use the selected geolocated device as a relay terminal. The selected geolocated terminal is chosen based on one or more criteria selected from: - Availability to be configured as a relay terminal, - Distance from the terminal, - a performance rate.

[0025] According to 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 and the date on which it must switch over.

[0026] A failover plan can be understood, for example, as a priority management system in a network where the network comprises multiple terminals whose energy state 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 interface to a second interface of the terminal(s). The communication management system may take into account several criteria to determine when a terminal switches its network interface to another network interface. Among these criteria, the communication management system may consider one or more of the following: - a priority associated with the terminal, - a battery charge level, - an average energy consumption, - average consumption over a past period, and / or - current terminal activity, and / or - energy consumption related to the terminal's normal operation, - 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 for example, or from vehicles.

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

[0032] This disclosure also relates to a method for managing communication on a network to which at least one first terminal is connected, said method comprising: - a reception of said first terminal of at least one piece of information relating to an energy state of said terminal connected to said network through a first interface, - a transmission to said first terminal, based on said information relating to an energy state of said first terminal, of at least one connection information to allow 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 may use any programming language, and be in the form of source code, object code, or code intermediate 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 comprising 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 can 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 disk 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 downloaded onto an Internet-type network.

[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: - to transmit at least one piece of information relating to the energy state of said terminal 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 information relating to an emitted energy state.

[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. Brief description of the drawings

[0041] [Fig-1] [Fig.1] [Fig.1] represents a system according to one embodiment of the present invention,

[0042] ] [Fig.2] Fig.2 represents a system according to one embodiment of the present invention wherein the relay device is a fixed device,

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

[0044] [Fig.4] Figure [Fig.4] represents, in the form of a flowchart, a particular method of implementing a communication management process according to this disclosure,

[0045] [Fig.5] Figure 5 schematically represents an example of the hardware architecture of a terminal,

[0046] [Fig.6] Figure 6 schematically represents an example of the hardware architecture of an electronic network management device, Description of the implementation methods

[0047] Fig. 1 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 terminal device, also called a client terminal, CL. It should be noted that the system may, in certain implementations, include a plurality of terminals such as the CL terminal.

[0049] Terminal Cl is connected to a power generation device using one or more intermittent energy sources, such as renewable energy sources or a rechargeable battery. The terminal can also use energy recovered from streetlights, for example, or from vehicles. Terminal Cl can be a connected sensor, as 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 generally low or at least limited.

[0050] A solar energy source SI, in the form of solar panels, is shown in [Fig. 1]. 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, - kinetic energy.

[0051] Renewable energy is converted into electrical energy to power the CL device

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

[0053] The hardware architecture of device Cl is shown in [Fig.3]. Device Cl further comprises at least two network interfaces IFS and IFL.

[0054] The IFL interface can, for example, be a long-range interface and the IFS interface can, for example, be a short-range interface. Of the at least two network interfaces, at least two of them are connected to networks using Different network infrastructures are used 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 to operate. 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] According to certain embodiments, the IFS interface may be of the "BLE" type for "Bluetooth® Low Energy," used, for example, to connect connected objects and whose energy consumption is known to be low. The IFS interface may also conform to the IEEE 802.15.4 protocol.

[0058] In some embodiments, the IFL interface is a LoRa® (Long Range) type radio interface with higher power consumption than a BLE type IFS interface. In some embodiments, the IFL interface may also be a Wi-Fi Halow®, LTE protocol compliant interface.

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

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

[0061] The Cl device may have insufficient energy to communicate through the INFRAL interface, since it is powered by a renewable, and therefore intermittent, energy source dependent on natural resources. It may therefore 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 insufficiency 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 Cl and other terminals on the network.

[0064] The INFRAS network infrastructure is based on network equipment / devices / servers, for example mobile devices or a fixed device such as an access gateway, to enable communication between terminal Cl and other terminals present on the network. By mobile device, we mean cell phones, drones, or other connected vehicles, connected virtual reality headsets—in other words, devices equipped with a network interface that can move geographically. These devices are relay devices that establish a connection between terminal Cl and the network.

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

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

[0067] According to one embodiment, the GR communication management device is located on a network interconnecting client terminals. It can be connected to the 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 Cl 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 Cl, depending on the information relating to the energy state, at least one connection piece of information to allow the first client terminal Cl to connect to the network through the second interface.

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

[0071] The GR communication management device may also, upon receiving information relating to an energy state: - Select at least one relay device to allow the first client terminal Cl to establish communication with the network through the second interface and the selected relay device. In one embodiment, the relay device enables 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 the relay terminal is selected from a set of relay terminals, a Selection criteria may be linked to the proximity of an INFRAS device (mobile or fixed) to the client terminal. The selected device may be the one closest to the terminal, or it may be a device determined from a mobile device movement plan.

[0074] By travel plan, we can understand that the communication management system - 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 selected geo-located device to be within range of the client terminal to allow the client terminal to use the selected geo-located device as a relay terminal.

[0075] The selected geolocated terminal being selected according to 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. The client terminal Cl can select which relay terminal to use in order to utilize the second IFS interface and transmit to the communication management device GR information relating at least to the identity of the client terminal Cl that it has selected. To do this, the client terminal Cl may have information relating to 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 determined to provide a terminal Cl in the fleet with one or more relay devices of the INFRAS infrastructure, enabling the terminal Cl to communicate on the network using its IFS interface. This deployment plan can optimize the spatial and temporal coverage of the client terminals Cl.

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

[0081] A switchover plan for the Cl terminals of 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 in a network where the network comprises multiple client terminals whose power state 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 interface to a second interface of the client terminal(s). The communication management system may consider several criteria to determine when a client terminal switches its network interface to another network interface. Among these criteria, the communication management system may consider one or more of the following: - a priority associated with the client terminal, - a battery charge level, - average energy consumption, - average consumption over a past period, and / or - current activity of the client terminal, and / or - energy consumption related to a current activity of the customer terminal, - an amount of energy available from the energy source supplying the terminal.

[0083] The switching and moving plans can be updated regularly, or even periodically, from the energy state of each customer terminal Cl and / or from the class of the terminal and / or from the information relating to the interface it uses and / or from the location of the mobile relay devices.

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

[0085] The client terminal Cl 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 on the basis of a SW_TOKEN switchover token previously established by the management device.

[0086] A proximity connection is established between the client terminal Cl and the selected relay device which directs messages from the client terminal Cl 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 TypeO or Typel (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 communication management device GR 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 communication management device GR validates the switchover of the client terminal Cl to the INFRAS infrastructure and updates the connection information of the client terminals CL

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

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

[0091] The GR communication management device 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 the energy status, it can also take into account consumption projections or energy requirements, based on energy status information and / or historical consumption data. or available information relating to future consumption or future energy needs, to establish the classification.

[0092] This classification may contain 4 classes and in particular: - A first class includes customer terminals whose energy consumption exceeds the energy recharge - A second class includes customer terminals whose energy consumption is lower than the energy recharge - a third class includes terminals whose operation has stopped, - a fourth class includes terminals in transition from the first class to the second class.

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

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

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

[0096] When a client terminal Cl belongs to the third class, it is considered to be discharged. The communication management device GR 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 rate.

[0097] When a client terminal Cl 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 communication management device GR has not yet received an acknowledgment from the first terminal.

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

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

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

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

[0102] Fig. 2 represents a first example of application; the client terminal Cl can be an environmental sensor installed for a long period to make periodic readings.

[0103] This sensor is powered by a solar panel SI, the energy from which is converted into electrical energy and stored in the device CL. 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 Cl 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 from an IFS interface to an IFL interface.

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

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

[0107] In certain cases, solar energy is no longer sufficient to allow 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 operation of the IFL interface. The sensor Cl then transmits information about its energy state to the communication management device GR, via its IFL interface, using MESS-TYPEla messages. This information allows the communication management device GR to perform the necessary calculations (estimates and projections) concerning the client terminal Cl in order to anticipate / suggest and / or command a possible switchover between the IFL interface and the IFS interface. In some embodiments, the information about the energy state may include a network interface switchover request.

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

[0109] MESS-Typela messages can enable the communication management device to manage the connectivity of client terminals based on their energy resources. This information can allow the communication management device to obtain an overview of the energy situation along with projections of its evolution.

[0110] Terminal Cl can also transmit information relating to an access gateway of the INFRAS infrastructure, which it has discovered can serve as a relay to switch over to the IFS interface, in a message of type MESS-TYPElb, for example when its power state is insufficient. MESS-TYPElb messages can transmit connectivity information concerning the alternative connectivity mode to the current mode between the communication management device GR and the client terminal CL. This information, by way of example, can correspond to the discovery of the radio neighborhood / landscape represented either by the relay devices near a client terminal Cl, or by the relay devices accessible depending on the connectivity mode to which it would be likely to switch over.

[0111] Terminal Cl can also transmit additional information to the GR communication management device to enable it to obtain information on the availability of the INFRAL network infrastructure and the evolution of said availability. It can also transmit information relating to an access gateway that it wishes to use. This information can enable the GR communication management device to configure the access gateway. These messages from MESS-TYPE 1b data can also be transmitted at any time, for example, as soon as the client terminal Cl connects to the network during the detection of accessible access gateways. The GR communication management device can record 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 Cl, the communication management device GR can request permission from a thread network manager to open the thread network of the access gateway to client terminal Cl by transmitting an OUV-THREAD message. To do this, it transmits to the thread network an OUV-THREAD message including information about terminal Cl 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 the client terminal Cl to communicate with the thread network via an AUTH-OUV-THREAD message. The access gateway can transmit information enabling the client terminal Cl to connect to the thread network via an INFO-CONNECT1 message.

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

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

[0116] .11 can also transmit configuration information to the gateway access, not represented.

[0117] Upon receiving the configuration information, the Cl sensor connects to the access gateway thread network and communicates through this interface to transmit MESS-TYPEO, 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-TYPEO messages, passing over the thread network.

[0119] Figure 3 represents a second application example, in which a plurality of Cl client terminals, such as a fleet of data collection terminals, are deployed. To ensure the integrity of the application using this data, the Cl client terminals transmit it to a centralized processing information system with predetermined delays. To do this, the Cl terminals use their IFL interface. for example, a LoRA® type connection. The INFRAL infrastructure can include a plurality of fixed access gateways (PAs).

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

[0121] In order to compensate for a total discharge of the battery, which would result in the cessation of data transmission, the Cl 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 enabling them to be identified.

[0124] A session identifier ID_SESSION is also included in a header field of messages exchanged between the client terminal Cl 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 from an IFS interface to an IFL interface.

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

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

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

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

[0129] In some cases, solar energy is no longer sufficient to allow 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 operation of the IFL interface. The sensor Cl then transmits information about its energy status to the communication management device GR, via its IFL interface, by means of a MESS-TYPE1 message. This information allows the communication management device GR to perform the necessary calculations (estimates and projections) concerning the client terminal Cl for Anticipate / suggest and / or command a possible switchover between the IFL interface and the IFS interface. In some embodiments, the energy status information may include a network interface switchover request information.

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

[0131] Typela messages can enable the communication management device to manage the connectivity of client terminals based on their energy resources. This information can allow the communication management device to obtain an overview of the energy situation along with projections of its evolution.

[0132] Terminal Cl can also transmit information relating to an access gateway of the INFRAS infrastructure, which it has discovered can serve as a relay to switch over to the IFS interface, in a message of type MESS-TYPElb, for example when its power state is insufficient. MESS-TYPElb messages can transmit connectivity information concerning the alternative connectivity mode to the current mode between the communication management device GR and the client terminal CL. This information, by way of example, can correspond to the discovery of the radio neighborhood / landscape represented either by the relay devices near a client terminal Cl, or by the relay devices accessible depending on the connectivity mode to which it would be likely to switch over.

[0133] Terminal Cl can also transmit additional information to the GR communication management device to enable it to obtain information on the availability of the INFRAL network infrastructure and its evolution. It can also transmit information relating to an access gateway it wishes to use. This information can allow the GR communication management device to configure the access gateway. These MESS-TYPElb messages can also be transmitted at any time, for example, as soon as client terminal Cl 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 device obtains an overall view of the energy situation of the Cl terminals of the fleet and can thus select a relay device from among the relay devices available in the INFRAS infrastructure. It can also establish a relocation plan and a switchover plan for mobile terminals.

[0135] The communication management device GR transmits a MESS-Type2 message to a client terminal Cl, 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 the client terminal Cl 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] The devices of the INFRAS network interface can also transmit information relating to their availability, in MESS-TYPE-INFRAS messages, their bandwidth or performance, to the network manager GR. This can advantageously allow the network manager GR to have up-to-date information on the terminals of the INFRAS infrastructure.

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

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

[0139] According to one variant, the client terminal Cl itself requests to switch from the first interface to the second interface; it transmits a MESS-TYPElc request to the communication management device GR in order to obtain the switchover token, SW_TOKEN. This variant can allow the decision to be deferred in distributed mode to the client devices CL

[0140] According to an alternative, not shown in [Fig. 3], the communication management device GR does not select the relay device in the INFRAS infrastructure to be used but transmits connection information to the client terminal Cl in the form of the SW_TOKEN failover token. The client terminal Cl then selects a relay device from among those available to it in the INFRAS infrastructure. The client terminal Cl transmits the SW_TOKEN token to the selected relay device so that the relay device is accepted as a relay device by the communication management device GR.

[0141] According to one variant, the MESS-TYPE2 message contains not a request to switch over its interface but a suggestion to switch over the interface. The client terminal, upon receiving a MESS-TYPE2 message suggesting a Failover determines the availability of a relay device in the INFRAS infrastructure. The client terminal Cl can then transmit a MESS-TYPElb message to inform the communication management device of the availability of a relay device. 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 described previously.

[0142] Figure 4 represents, in flowchart form, a particular implementation of a communication management method according to this disclosure. The method is implemented in a communication management device terminal (GR) in a system as described opposite Figure 1. The various embodiments described opposite Figure 1 also apply to the method in Figure 2. The messages exchanged as described above can be used in the exchanges mentioned below in the method.

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

[0144] The client terminal Cl is connected to the network management device GR 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] By insufficient energy state, one can understand an energy state insufficient to communicate through the IFL interface.

[0146] The method 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 Cl 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, the client terminal Cl does not wait for the network manager to request it to change network interfaces but makes the decision itself. This can occur when the energy state of the client terminal Cl 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 method may include a step E3, during which the network manager GR receives information from the client terminal Cl regarding a request to activate the second interface. It may then transmit a failover approval to the client terminal Cl.

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

[0151] According to a second option, the method includes a step E4 in which the communication management device GR, depending on the energy state of terminal Cl, 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 state over time.

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

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

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

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

[0156] According to some variants, the method may include a step (not shown) in which the client terminal Cl 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 method may also include a step E7 of determining a switchover plan for the terminals Cl of the fleet to determine, based on their energy state or a projection of their energy state, a switchover moment from the IFL interface to the IFS interface.

[0158] The switching and relocation plans can be updated regularly, or even periodically, based on the energy state of each customer terminal Cl and / or based on the terminal class and / or based on information relating to the interface it uses and / or based on 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 method 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 allow the client terminal Cl to communicate on the network through its IFS interface via the INFRAS network infrastructure.

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

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

[0162] The selection can also be based on information received from the client terminal. In one variant, the client terminal Cl can select which relay terminal to use in order to utilize the second IFS interface and transmit to the communication management device GR information relating at least to the identity of the client terminal Cl that it has selected. To do this, the client terminal Cl may have information relating to the terminals that can serve as its relay. 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 to request it to serve as a relay device for the client terminal CL. If the selected relay device acknowledges, then we proceed to step E10; otherwise, another relay device is selected and we repeat steps E8 and E9.

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

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

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

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

[0168] The process as described above can also be applied to switching from the second interface to the first interface, depending on the energy state of terminal CL. When terminal CL reaches a sufficient charge level and is connected via its second interface, the communication management device GR 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 the connection of terminal CL to the network. Terminal CL can itself decide to switch to its first network interface and inform or request authorization from the communication management device GR.

[0169] [Fig.5] schematically represents the hardware architecture of a CL client terminal. As illustrated by [Fig.3], the Cl client terminal has the hardware architecture of a computer.

[0170] Thus, the client terminal Cl includes, in particular, a processor 31, a memory It includes a RAM 32, a ROM 33, and a non-volatile memory 34. It further 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] The read-only memory 33 constitutes a recording 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 Implementation of this disclosure, including instructions for executing steps implemented in terminal Cl according to at least one embodiment of this disclosure. The PROG1 program defines functional modules of the device.

[0172] Figure 6 schematically represents the hardware architecture of a GR communication management device. As illustrated by Figure 4, 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] The read-only memory 43 constitutes a recording 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

Demands

1. Communication management device (CM) on a network to which at least one first terminal (Cl) is connected said management device being configured to: - receive from said first terminal (Cl) at least one information relating to an energy state of said terminal (Cl) connected to said network through a first interface, - transmit to said first terminal (Cl), depending at least on said information relating to an energy state of said first terminal (Cl), at least one connection information to allow said first terminal (Cl) to connect to said network through a second interface.

2. 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 of insufficient available energy resources, - a battery charge level, - information relating to current consumption, - information relating to a recharge or discharge rate

3. 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 (Cl) 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 (Cl).

4. Device according to claim 4 wherein said at least one selected relay device is chosen from: - at least one second terminal (Cl), - at least one mobile device.

5. 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 (Cl) to connect via said second interface to said network through said relay devices.

6. Device according to any one of the preceding claims further configured to: - detect a connection switchover from said network from the first interface to said second interface during a first data transfer of said terminal (Cl) through said second interface.

7. Device according to any one of the preceding claims further configured to: - receive said first terminal (Cl) 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 (Cl), an approval of said switch over.

8. Device according to claim 6 further configured to: - pending detection of said switchover, provide said terminal (Cl) with bimodal connectivity infrastructure resources configured to permit connection through said first interface and said second interface.

9. Device according to any one of the preceding claims configured to - determine a projection of an energy requirement of said first terminal (Cl) from said information relating to an energy state.

10. 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 (Cl) to enable said terminal (Cl) to establish short-range communication with said selected vehicle.

11. Device according to any one of the preceding claims wherein said first interface is a more energy-consuming interface than said second interface.

12. A method for managing communication on a network to which at least one first terminal (Cl) is connected, said method comprising: - receiving from said first terminal (Cl) at least one piece of information relating to an energy state of said terminal (Cl) connected to said network through a first interface, - transmitting to said first terminal (Cl), according to said information relating to an energy state of said first terminal (Cl), of at least one connection information to allow said first terminal (Cl) to connect to said network through a second interface.

13. Terminal connected to a communications network configured to: - transmit at least one piece of information relating to an energy state of said terminal (Cl) 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.

14. Computer program comprising instructions for carrying out the steps of the process according to claim 12, when said program is executed by a computer.

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