METHOD AND DEVICE FOR MANAGING AN UPDATE OF A TERMINAL DEVICE IN A TELECOMMUNICATION NETWORK.
Patent Information
- Application Number
- FR2023013772
- Authority / Receiving Office
- FR · FR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-07
- Publication Date
- 2026-09-11
- Estimated Expiration
- 2043-12-07
AI Technical Summary
Existing methods for updating terminal devices in telecommunications networks are complex and require significant hardware resources, especially when multiple communication protocols need to be supported, leading to manual intervention and service disruptions.
A method that involves storing a first part of a new communication protocol in the terminal device, using it to transmit probe messages to the controller device, and upon receiving a response, downloading the complementary second part to update the protocol stack, thereby simplifying the update process and optimizing storage space.
This approach allows for automated updates of terminal devices without manual intervention, reduces storage requirements, and minimizes service disruptions by enabling seamless protocol stack updates.
Smart Images

Figure 00000023_0000 
Figure 00000023_0001 
Figure 00000023_0002
Abstract
Description
Title of the invention: METHOD AND DEVICE FOR MANAGING AN UPDATE OF A TERMINAL DEVICE IN A TELECOMMUNICATIONS NETWORK. Technical field
[0001] The present disclosure relates to the field of telecommunications networks, for example wireless telecommunications networks. In particular, the present disclosure relates to the management of an update of a communication protocol of a terminal device belonging to a local communication network. More specifically, the present disclosure relates to the updating of the protocol stack of the terminal device according to the communication protocol currently used by a controller device managing the local communication network. STATE OF PRIOR ART
[0002] A wireless telecommunications network (hereinafter "communications network") compliant with one of the IEEE 802.11 standards (for example one or more of the amendments b, g, a, n, ac, ax, be, etc., of the IEEE 802.11 standard) typically comprises a plurality of nodes. Each node is an electronic device comprising at least one radiofrequency module allowing the establishment of communications in accordance with one of the IEEE 802.11 standards, or in other words, in accordance with one of the Wi-Fi standards. Such a communications network is for example a local area network (LAN), for example a home network or professional network.
[0003] Some local LAN communication networks include, for example, wireless communication coverage extension systems typically comprising one or more electronic devices, commonly called access points (APs), and a plurality of electronic devices called users (or clients) (hereinafter "user devices") capable of establishing wireless connections with one of the access points and / or with each other. These different access points are interconnected by means of a routing or backhaul subnetwork and all make the same WLAN (Wireless Local Area Network) available to the user devices. These access points are, for example, wireless repeaters (or "extenders"). The user devices are typically computers, televisions, TV decoders, etc.It is thus commonly said that user devices are associated "in Wi-Fi" with access points. Subsequently, access points and user devices are called "terminal devices".
[0004] Among the electronic devices, one may be a so-called "controller" device insofar as the other terminal devices of the local LAN communication network are dependent on its control. This may be the case in a mesh-type wireless communication network, in which one of the access points centralizes certain configuration decisions of the other access points. In one example, the controller device decides the communication protocol used for exchanges between the terminal devices among themselves or with a home gateway, within the local LAN communication network. In one example, in a residential or professional environment, the controller device may be integrated into a "box" provided by an Internet operator, i.e. the home gateway, or "residential gateway", in English, or professional gateway.
[0005] The domestic or professional gateway is connected to the extended network, or WAN (in English "Wide Area Network"), such as for example an Internet network, by ADSL copper link (in English "Asymmetric Digital Subscriber Line"), or similar, by fiber and / or by 3G / 4G / 5G type mobile access, allowing the terminal devices of the network to access the extended network WAN and to communicate with each other.
[0006] In the local communication network LAN, the communication protocol (eg, communication protocol according to the EASY-MESH standard, etc.) used by all the different terminal devices to communicate with each other or with the home gateway for access to the wide area network WAN, is therefore managed by the controller device. Thus, in general, the communication protocol used by the terminal devices at a time t corresponds to that used at the same time by the controller device. Subsequently, it is considered that the communication protocol used in the local communication network LAN corresponds to that used by the controller device.
[0007] When the communication protocol of the controller device is updated (i.e., updating its protocol stack), then the terminal devices communicating via the old version of the communication protocol of the controller device can no longer communicate with each other or with the gateway for access to the WAN, for example. Their protocol stack must then also be updated.
[0008] In order to be able to dynamically adapt to changes in the communication protocol of the controller device, the terminal devices may comprise several protocol modules each having their own communication protocol. To discover, or detect, which communication protocol is used by the controller device at time t, the terminal devices may sequentially activate each on-board communication protocol. Alternatively, the dis positive terminals can simultaneously activate all on-board communication protocols in order to detect the communication protocol currently used by the controller device.
[0009] The major drawback of sequential or simultaneous activation of all the on-board communication protocols is a high operational complexity, particularly for simultaneous activation. Furthermore, in order to support the multiple communication protocols, the terminal devices must include sufficient hardware resources, particularly with regard to storage space.
[0010] However, some older or low-cost terminal devices do not necessarily have these hardware resources for the coexistence of several protocol modules, each housing its own communication protocol. Thus, when the communication protocol in use must evolve (for example following an update of the protocol stack of the controller device or when a newer, more recent controller device is integrated into the local LAN communication network), it is often necessary to manually intervene on these terminal devices to update them. This task can be particularly complicated for a user and cause a prolonged interruption of the service offered by the terminal devices.
[0011] It is then desirable to overcome these drawbacks of the state of the art.
[0012] EXPOSE
[0013] It is desirable to provide a solution that makes it possible to simplify the updating of the protocol stack of the terminal devices, when the communication protocol used by the controller device managing the local communication network is different from that currently used by the terminal device.
[0014] For these purposes, a method is proposed here for managing an update of a terminal device belonging to a local communication network managed by a controller device, the terminal device communicating with the controller device via a current communication protocol. The method is implemented by the terminal device, and comprises:
[0015] - store in memory a first part of another communication protocol, different from the current communication protocol,
[0016] - execute a discovery phase during which the terminal device uses the said first part for:
[0017] - transmit at least one probe message to the controller device specific to said other communication protocol,
[0018] - wait for at least one response message responding to the at least one probe message sent from the controller device,
[0019] - check if at least one said response message is received and then download a second part of said other communication protocol, complementary to said first part, so as to have a complete version of said other communication protocol,
[0020] - execute a terminal device update phase comprising: replacing, in the terminal device, the current communication protocol by said other communication protocol as the new current communication protocol.
[0021] Thus, the present disclosure proposes a completely new and inventive approach to managing the update of a terminal device (eg, wireless repeater, decoder, etc.).
[0022] More particularly, the present disclosure proposes to update the protocol stack of the terminal device of a local communication network, thanks to the storage and execution of a first specific part of a new communication protocol different from that currently used by the controller device managing the local communication network.
[0023] The use of this first specific part of the new communication protocol makes it possible to detect whether this new communication protocol is used by the controller device managing the local communication network (for example following the update of the protocol stack of this controller device).
[0024] The detection of the use by the controller device of the new communication protocol is done by sending a probe message specific to the new communication protocol and receiving a response message in return. Thus, when the new communication protocol replaces the current communication protocol in the local communication network, then a second part complementary to the first part of the new protocol is downloaded, to obtain the complete version of this new communication protocol. It is thus possible, for the terminal device, to execute the entirety of the new communication protocol.
[0025] It is thus possible to easily update the protocol stack of the terminal device, without manual intervention.
[0026] Furthermore, it is further possible to optimize a storage space, such as a memory of the terminal device, because there is only a specific part of the new communication protocol which is stored in memory. It is thus possible to store several “partial” communication protocols (i.e., several specific parts of several communication protocols), different from that currently used by the controller device managing the local communication network.
[0027] According to one embodiment, the phase of updating the terminal device further comprises deleting from the terminal device the current communication protocol which has become obsolete.
[0028] Advantageously, it is thus possible to optimize the storage space, or memory, of the terminal device by storing only the new communication protocol supported by the local communication network (i.e., communication protocol used by the controller device managing the local communication network). In particular, it is possible to free up storage space by deleting the current communication protocol that has become obsolete, which is then replaced by the new communication protocol.
[0029] According to one embodiment, the probe message is transmitted repeatedly and the second part of the other communication protocol, complementary to the first part, is downloaded if, over a predefined period, a number of response messages received is greater than or equal to a predefined reliability threshold.
[0030] Advantageously, the detection of the use by the controller device of the new communication protocol is done by repeatedly sending the probe message specific to the new communication protocol and receiving a number of reliable response messages in return. A response message is considered reliable when the number of response messages is greater than or equal to a predefined reliability threshold.
[0031] According to one embodiment, the transmitted probe message is transmitted according to a broadcast type transmission.
[0032] Advantageously, in the case where the local communication network comprises several controller devices, it is thus possible to address all these controller devices.
[0033] According to one embodiment, the probe message is transmitted according to a predefined transmission frequency.
[0034] It is thus possible to limit the period of interruption of services so as not to inconvenience users, while not degrading network performance.
[0035] According to one embodiment, the predefined transmission frequency is between 1s and 5min.
[0036] According to one embodiment, the method further comprises storing in memory a list of a plurality of other communication protocols, different from the current communication protocol, said other communication protocols being classified according to an order from the most recent communication protocol to the least recent, and for each other communication protocol in the list, storing in memory a first part of said other communication protocol in question, and in which the discovery phase, during which the first part of each said other communication protocol is used, is carried out according to the order of said list.
[0037] Advantageously, when several controller devices are connected to the local communication network at the same time and use different communication protocols communications (i.e., one of the communication protocols of a controller device being more recent than another communication protocol of another controller device), it is possible to prioritize, in a list, these communication protocols in order from the most recent to the least recent. The terminal device is then updated according to the most recent communication protocol found in the list and being used by one of the controller devices.
[0038] Also proposed here is a method for updating a system comprising a terminal device and a controller device which belong to a local communication network managed by the controller device. The terminal device communicates with the controller device via a current communication protocol, the method comprising:
[0039] - updating the terminal device by downloading a first part of another communication protocol, different from the current communication protocol,
[0040] - trigger an execution of the update management method as described above immediately, so as to trigger the discovery phase by the terminal device;
[0041] - update the controller device by downloading the full version of said other communication protocol, so that the controller device responds to said probe messages received from the terminal device during the discovery phase by the terminal device.
[0042] Also provided herein is a terminal device intended to belong to a local communication network managed by a controller device, the terminal device being configured to communicate with the controller device via a common communication protocol. This terminal device comprises electronic circuitry configured to
[0043] - store in memory a first part of another communication protocol, different from the current communication protocol,
[0044] - execute a discovery phase during which the terminal device uses the said first part for:
[0045] - transmit at least one probe message to the controller device specific to said other communication protocol,
[0046] - wait for at least one response message responding to the at least one probe message sent from the controller device,
[0047] - check if at least one said response message is received and then download a second part of said other communication protocol, complementary to said first part, so as to have a complete version of said other communication protocol,
[0048] - execute a terminal device update phase comprising: replacing, in the terminal device, the communication protocol current by said other communication protocol as a new current communication protocol.
[0049] Also provided herein is a computer program product, comprising instructions causing a processor to execute the update management method as described above, when said instructions are executed by the processor.
[0050] Also provided here is a storage medium, storing a computer program comprising instructions causing the execution, by a processor, of the update management method as described above, when said instructions are read and executed by the processor. Brief description of the drawings
[0051] The characteristics of the embodiments mentioned above, as well as others, will appear more clearly on reading the following description of at least one exemplary embodiment, said description being made in relation to the attached drawings, among which:
[0052] [Fig-1] schematically illustrates an example of an implementation environment of the method for managing an update of a terminal device, according to a particular embodiment;
[0053] [Fig.2] illustrates in diagrammatic form a method for managing an update of a terminal device according to one embodiment;
[0054] [Fig.3A] schematically illustrates an example of the exchanges between a terminal device and a controller device during the execution of the method for managing an update of the terminal device, according to one embodiment,
[0055] [Fig.3B] schematically illustrates another example of the exchanges between a terminal device and a controller device during the execution of the method for managing an update of the terminal device, according to one embodiment,
[0056] [Fig.4] schematically illustrates the hardware architecture of a terminal device configured to execute all or part of the steps of the management method illustrated in Figs. 2 and 3.
[0057] DETAILED DESCRIPTION OF EMBODIMENTS
[0058] The general principle of either embodiment relates to updating the communication protocol of a terminal device (i.e., access point or user device) following the implementation of a new communication protocol within the local communication network LAN.
[0059] The change of communication protocol within the local communication network may originate from: - an update of the communication protocol (eg, update of the protocol stack of the controller device) currently used by the controller device managing the local LAN communication network (for example: upgrading to a communication protocol according to a more recent standard, switching to a mesh network management solution from a different provider), - the installation of a new controller device in the local communication network LAN. This new controller device uses a newer communication protocol than the one currently used in the local communication network (i.e., communication protocol of the old controller device).
[0060] In particular, the present disclosure relates to the storage and use of a first specific part of this new communication protocol, prior to the implementation of this new communication protocol in its complete version in the terminal device. The use of this first specific part of the new communication protocol corresponds to a discovery function of the latter. This discovery function makes it possible, during a discovery phase, to detect that this new communication protocol is used within the local LAN communication network. Thanks to this first part of the new communication protocol, the terminal device can, if necessary, download a second part complementary to the first part of the new communication protocol for use of a complete version of the latter.
[0061] [Fig.l] thus schematically illustrates an example of an implementation environment of the method for managing an update of a terminal device according to a particular embodiment.
[0062] The local communication network LAN comprises a gateway, denoted GW, for access to a wide area network WAN, for example an Internet network. The gateway GW is connected to the wide area network WAN by an ADSL or fiber link. Of course, it can also connect to a cellular network of an operator by a wireless radio link of type 2G to 5G.
[0063] In the embodiment related to [Fig.l], the local communication network LAN is a mesh type Wi-Fi network. For this, this local communication network LAN comprises, for example, a wireless communication coverage extension system coordinating several access points (“Access Point” in English) integrated into communication nodes denoted NI, N2 and N3. These different access points are interconnected by means of a routing or backhaul subnetwork. These access points all allow access to the local communication network LAN to user devices denoted UE1, UE2, UE3. The access points NI, N2 and N3 can be connected to the gateway GW by wired link or by wireless link for access to the wide area network WAN.
[0064] In general, in the case of a mesh-type wireless network, each communication node N1, N2 and N3 of the routing subnetwork comprises a plurality of access points on the same radio:
[0065] - an access point interface called “AP-BH” (for “Access Point Backhaul” in English) corresponding to an access point interface of the routing subnetwork,
[0066] - an access point interface "STA-BH" (for "Station Backhaul" in English) cor responding to a user (or client) access point interface of the routing subnet,
[0067] - an access point interface “AP-FH” (for “Access Point Fronthaul” in English) corresponding to an access point interface of the local communication network LAN, this interface being dedicated to the association of user devices UE1, UE2, UE3 to the local communication network LAN.
[0068] The communication nodes NI, N2 and N3 of the routing subnetwork are connected to each other using a tree-shaped structure, a node then being able to serve as a relay between two other nodes of the routing subnetwork. The communication nodes NI, N2 and N3 are thus interconnected using wired links, for example of the Ethernet type, and / or wireless links. The communication nodes NI, N2 and N3 of the routing subnetwork thus communicate with each other using logical links, for example IP communications or encrypted tunnels or communications according to a proprietary communication protocol. In one example, the node NI is connected to the node N2 using a wireless link between the access point radio interface AP-BH of the node NI and the client radio interface ST-BH of the node N2.The links between two nodes in the routing subnetwork are called forwarding links or backhaul links and can be wired or wireless.
[0069] Where appropriate, the user devices UE1, UE2, UE3 can connect to the different nodes NI to N3 via their AP-FH radio interface for their access to the local communication network LAN.
[0070] This local communication network LAN therefore also includes all the user devices UE1, UE2, UE3 such as a TV decoder, a personal computer, a tablet, etc. These user devices UE1, UE2, UE3 can be connected directly to the gateway GW or via one of the access points located in the communication nodes NI, N2 or N3 (as shown in [Fig.l]). The connection with the gateway GW or the access points located in the communication nodes NI, N2, N3 can be made by wired connection (for example of the Ethernet type), or by other types of connection such as for example USB, wireless connection (for example of the type: Wi-Fi, Bluetooth, Bluetooth Low Energy, Zwave, Zigbee, DECT-ULE...etc.).
[0071] Subsequently, the user devices UE1, UE2, UE3 and the access points located in the communication nodes NI, N2, N3 are called terminal devices 400. An exemplary embodiment of such a terminal device 400 is shown below in connection with [Fig. 4]. These terminal devices 400 are capable of connecting to the local communication network LAN in that they have the authorizations and configurations necessary to access the resources of said local communication network LAN.
[0072] The local communication network LAN of [Fig.l] also comprises a controller device CONT managing said network. In the embodiment according to [Fig.l], the controller device CONT is located in the gateway GW. In this case, the gateway GW not only provides access to the wide area network WAN, but also manages the communication network LAN via the controller device CONT.
[0073] In a variant, the controller device CONT is an electronic device independent of the gateway GW. In this case, the controller device CONT manages the local communication network LAN and the gateway GW provides access to the extended network to the terminal devices 400 and to the controller device CONT. It should be noted that the terminal devices 400 can alternatively or additionally access the extended network via other equipment, such as for example a USB key providing access to the extended network (for example 4G key).
[0074] All or part of the method for managing an update of a terminal device 400 as described below in connection with [Fig.2] and [Fig.3A] and 3B is carried out by a terminal device 400 described below in connection with [Fig.4].
[0075] In order to illustrate the implementation of the method for managing the update of a terminal device 400, it is considered that said terminal device 400 is for example a wireless repeater type access point.
[0076] [Fig.2] illustrates in diagrammatic form a method for managing an update of a terminal device 400, according to a particular embodiment.
[0077] [Fig.3A] schematically illustrates an example of the exchanges between: a terminal device 400, a controller device CONT located in the gateway GW, during the execution of the management method according to a particular embodiment.
[0078] [Fig.3B] schematically illustrates another example of the exchanges between: a terminal device 400, a controller device CONT located in the gateway GW, during the execution of the management method according to a particular embodiment.
[0079] It is considered here that the controller device CONT currently uses a first communication protocol, denoted Proto_l and therefore imposes the use of this communication protocol Proto_l in the local communication network LAN. The terminal device 400 therefore uses this first communication protocol Proto_l in order to be able to fully communicate in the communication network LAN and access the wide area network WAN, in which case via the gateway GW.
[0080] To be able to detect a change of communication protocol in the local communication network LAN, the terminal device 400 stores in memory and also implements a specific first part FD_Proto_2 of a second communication protocol Proto_2, different from the first communication protocol Proto_l. It should be noted that this second communication protocol Proto_2 may be a newer communication protocol than the first communication protocol Proto_l. Thus, subsequently, the second communication protocol Proto_2 is also called the new communication protocol, and the first communication protocol Proto_l is also called the old communication protocol or the current communication protocol.
[0081] The implementation of this first specific part FD_Proto_2 of the second communication protocol Proto_2 is done in addition to the implementation of the native functions of the terminal device 400. In other words, the execution of the different steps of the update management method as described below, is done in parallel with the native functions of the terminal device 400.
[0082] This specific part FD_Proto_2 of this second communication protocol Proto_2 corresponds to a discovery function of this second communication protocol Proto_2. Subsequently, it is called "discovery function", the first specific part of the second communication protocol Proto_2, different from the first communication protocol Proto_1 currently used by the controller device CONT managing the local communication network LAN. This discovery function makes it possible to discover, or detect, the use, in the local communication network LAN, of the corresponding communication protocol. In this case, the discovery function FD_Proto_2 makes it possible to discover, or detect, the use of the second communication protocol Proto_2 in the local communication network LAN. In particular, this discovery function FD_Proto_2 comprises: - a module configured to emit a probe message S_Proto_2, interpretable by the CONT controller device using the second communication protocol Proto_2; - a module configured to interpret a response message RS_Proto_2 to the probe message S_Proto_2 sent from the controller device CONT (in particular when the latter has evolved towards the second communication protocol Proto_2); - a module configured to download from a dedicated SER server, via the wide area network WAN, a second complementary part C_Proto_2 of the second communication protocol Proto_2, so that a complete version of the latter can be implemented in the terminal device 400.
[0083] This FD_Proto_2 discovery function is simple in its operation in that it only includes the modules described above. This allows for optimization the storage space of the terminal device 400. The memory footprint of the discovered function is therefore smaller than if the terminal device 400 had to embed the entire second communication protocol Proto_2. Thus, in one embodiment, the terminal device 400 can store and implement several discovered functions specific to different communication protocols more recent than that currently used in the local communication network LAN.
[0084] In one example, a terminal device 400 natively compatible with a proprietary communication protocol stores in memory and implements the discovery function of a proprietary communication protocol from another provider.
[0085] It should be noted that this discovery function is specific to a particular communication protocol. In other words, the specificities of the new communication protocol to be discovered (for example the communication protocol Proto_2 in the example linked to Figs. 3A and 3B) impact the type of discovery function. In other words, each communication protocol corresponds to a corresponding discovery function.
[0086] Consequently, in order to discover a new communication protocol used in the local communication network LAN (eg second communication protocol Proto_2), the terminal device 400 must embed the corresponding discovery function (eg, the discovery function FD_Proto_2 of the second communication protocol Proto_2), before the new communication protocol is implemented in the local communication network LAN. Indeed, in the event of incompatibility between the communication protocols of the terminal device 400 and the controller device CONT, the terminal device 400 can no longer access the local communication network LAN, nor the wide area network WAN.
[0087] In the case of a terminal device 400 already present in the local communication network LAN, it is possible that the latter does not natively embed the discovery function of the new communication protocol (for example because this new communication protocol may not exist at the time of deployment of this terminal device 400.). Then, in this case, an update of the terminal device 400 is necessary so that it embeds the discovery function of the new communication protocol. In other words, prior to the implementation of the new communication protocol in the local communication network LAN (i.e., before the update of the protocol stack of the controller device CONT or before the addition of a new, more recent controller device CONT), a software update of the terminal device 400 is carried out so that it embeds the discovery function associated with the new communication protocol.This software update of the terminal device 400 makes it possible to anticipate the implementation of a new communication protocol in the local communication network LAN. The anticipation of the . updating the discovery function allows the terminal device 400 to always be able to connect, even in a restricted manner, to the local communication network LAN in order to be able to access the wide area network WAN (for example via the controller device CONT providing access to the wide area network WAN). The terminal device 400, thanks to this discovery function (and in particular to the module configured to download) can access a SER server of a service provider for downloading the second complementary part of the new communication protocol associated with the discovery function used, for an implementation of the complete version of this new communication protocol.
[0088] Once the terminal device 400 is updated to embed the discovery function FD_Proto_2, it can execute the steps described in connection with Figs 2 and 3A and 3B for the discovery of a new communication protocol Proto_2 used in the local communication network LAN and the update of its protocol stack if necessary.
[0089] During a step 201, a probe message S_Proto_2, specific to the second communication protocol Proto_2, is sent by the terminal device 400 to the control device CONT. More particularly, the probe message S_Proto_2 is sent by the terminal device 400 in a frame characteristic of the transmission mode of the probe message S_Proto_2. In one embodiment, the probe message S_Proto_2 is sent repeatedly.
[0090] In an exemplary embodiment, when the terminal device 400 is connected to the local communication network LAN via an Ethernet link, then this probe message S_Proto_2 is encapsulated in a frame of the Ethernet protocol. In another exemplary embodiment, when the terminal device 400 is connected to the local communication network LAN via Wi-Fi, then the probe message _Proto_2 is encapsulated in a frame of the 802.11 / Wi-Fi protocol.
[0091] In an exemplary embodiment, when the discovery function is specific to a communication protocol according to the EasyMesh standard, this S_Proto_2 probe message is a message of type “1905 AP-Autoconfiguration Search” (for example in accordance with paragraph 6.1 of the Wi-Fi Alliance, or “WFA”, EasyMesh R3 specification).
[0092] This probe message S_Proto_2 can only be interpreted by the control device CONT when the latter uses, at the time of receiving the probe message S_Proto_2, the second communication protocol Proto_2. Otherwise, if the control device CONT still uses the first protocol Proto_1, then the probe message S_Proto_2 cannot be interpreted by the control device CONT ([Fig.3A]).
[0093] In one embodiment, so that this S_Proto_2 probe message can be possibly detected by the controller device CONT in the entire LAN communication network, the terminal device 400 transmits the probe message S_Proto_2 according to a broadcast type transmission. It is thus possible, unlike a unicast type transmission, to address all the devices (terminal devices and controller devices) of the local LAN communication network and be sure that one or more controller devices receive this probe message S_Proto_2.
[0094] In an exemplary embodiment, when the terminal device 400 is a wireless repeater, this transmission is made on each of its interfaces that can be connected to controller devices of the LAN communication network. In this case, the interfaces that can be connected are generally Ethernet interfaces, the AP BH radio interface or the STA-BH radio interface.
[0095] In one embodiment, the transmission of the probe message S_Proto_2 is executed during a period during which the terminal device 400 is not executing a native function.
[0096] In another embodiment, the transmission of the probe message S_Proto_2 is executed periodically, that is to say that the probe message S_Proto_2 is transmitted repeatedly, according to a predefined transmission frequency F. It is thus possible to detect (or discover) the use of the second communication protocol Proto_2 by the controller device CONT. Indeed, when the controller device CONT has evolved to another communication protocol, then the management service of the local communication network LAN is interrupted because the terminal device 400 (eg, wireless repeater) and the controller device CONT each use different protocols, in other words they no longer speak the same language.Thus, the transmission frequency F of the probe message S_Proto_2 must be carefully chosen so that on the one hand the service interruption suffered by the user due to the incompatibility between the first communication protocol Proto_l commonly used by the terminal device 400 and the second / new communication protocol Proto_2 used by the controller device CONT, is not too long. On the other hand, the transmission frequency F of the probe message S_Proto_2 must not be too short because sending the probe message S_Proto_2 with too high a frequency could disturb the other native functions of the terminal device 400, as well as induce an additional load due to the transmissions of the probe message S_Proto_2 on the LAN communication network.
[0097] Thus, in one embodiment, the transmission frequency F of the probe message S_Proto_2 does not exceed 5 minutes to make the service interruption acceptable to the user and is not less than one second so as not to degrade the performance of the local communication network LAN. In one embodiment, the message of S_Proto_2 probe is sent every 5 minutes.
[0098] During a step 202, denoted R_REP_PROBE, the terminal device 400 waits for a response message RS_Proto_2 following the transmission of the probe message S_Proto_2.
[0099] As mentioned previously and presented in connection with [Fig.3A], if the controller device CONT does not yet use the second communication protocol Proto_2 specific to the probe message S_Proto_2, then no response message RS_Proto_2 is transmitted (step 202, result “no”) from the controller device CONT to the terminal device 400. In this case, during step 204, noted PCOM_C, the terminal device 400 and the controller device CONT continue to use the first communication protocol Proto_1 for their exchanges in the local communication network LAN.
[0100] On the contrary, as presented in connection with [Fig.3B], if the communication protocol used by the control device CONT has evolved towards the second communication protocol Proto_2, then the latter sends to the terminal device 400 a response message RS_Proto_2. In other words, when the controller device CONT is updated by downloading the complete version of the second communication protocol Proto_2, then the controller device CONT can interpret the probe message S_Proto_2 transmitted by the terminal device 400 and send to the terminal device 400 a response message RS_Proto_2 during the discovery phase carried out by the terminal device 400.
[0101] For example, when the CONT controller device uses a communication protocol according to the EasyMesh standard, the RS_Proto_2 response message sent by the CONT controller device is of type “1905 AP-Autoconfiguration Response”.
[0102] In this case, during this step 202 R_REP_PROBE the terminal device 400 checks whether it receives a response message RS_Proto_2 from the controller device CONT. Thanks to the discovery function FD_Proto_2, the terminal device 400 is able to interpret this response message RS_Proto_2.
[0103] If the terminal device 400 receives a response message RS_Proto_2 (step 202, result "yes"), following the emission of the probe message S_Proto_2, then the second communication protocol Proto_2 is used by the controller device CONT and is therefore supported by the Local LAN communication network.
[0104] During an optional step 203, denoted DET_NREP, the terminal device 400 determines, over a predefined period P, a number of RS_Proto_2 response messages received following the transmission of successive S_Proto_2 probe messages during the predefined period P. In other words, the terminal device 400 determines whether for each S_Proto_2 probe message it receives an RS_Proto_2 response message in return over the predefined period P. The terminal device 400 then counts the number of RS_Proto_2 response messages received over the predefined period P.
[0105] In one embodiment, the predefined period P depends on the transmission frequency F of the probe message S_Proto_2. In one embodiment, this period P is between 5 seconds and 5 minutes.
[0106] At the end of step 203 DET_NREP, the terminal device 400 determines whether the number of RS_Proto_2 response messages received during the predefined period P is reliable. More particularly, during an optional step 205, denoted NREP_F, the terminal device 400 determines whether the number of RS_Proto_2 response messages is greater than or equal to a predefined response message reliability threshold S. It is thus possible to ignore intermittent communication protocol developments that may occur during the installation of the new controller device CONT in the local communication network LAN. In an exemplary embodiment, an RS_Proto_2 response message is considered reliable if the terminal device 400 receives at least 4 responses out of 5 S_Proto_2 probe message transmissions.
[0107] Thus, at the end of the optional step 205 NREP_F, if the number of RS_Proto_2 response messages received is greater than or equal to the reliability threshold S (step 205, result “yes”) then the terminal device 400 considers that the second communication protocol Proto_2 is used in the local communication network LAN (i.e., the controller device CONT uses the second communication protocol Proto_2 corresponding to the discovery function used FD_Proto_2). On the contrary (step 205, result “no”), if the number of RS_Proto_2 response messages received is insufficient (i.e., below the reliability threshold S) then the terminal device 400 considers that the second communication protocol Proto_2 corresponding to the discovery function FD_Proto_2 is not used by the controller device CONT and the download procedure described below is not initiated.In this case, during step 207, denoted PCOM_C, the terminal device 400 and the controller device CONT continue to use the first communication protocol Proto_1 for their exchanges in the local communication network LAN. Optionally, at the end of step 207 PCOM_C, the terminal device 400 begins a new cycle of discovery or detection of the second communication protocol Proto_2 thanks to its discovery function FD_Proto_2.
[0108] Thus, if the number of RS_Proto_2 response messages received is greater than or equal to the reliability threshold S (step 205, result “yes”) then the terminal device 400 executes the optional step 206 DL_NW_PC0M. During this step 206, DL_NW_PC0M, the terminal device 400 uses the discovery function FD_Proto_2 to access the wide area network WAN to download the second complementary part C_Proto_2 of the second communication protocol Proto_2 specific to the discovery function FD_Proto_2. For this, the terminal device 400 downloads this second complementary part C_Proto_2 from a dedicated SER server.
[0109] In an exemplary embodiment, the update of the terminal device 400 can be carried out by downloading according to a transmission protocol of the HTTPS type (Hyper Text Transfer Protocol Secure) from a URL address (for “Uniform Resource Locator” in English, or “uniform resource locator”) pre-filled in the memory of the terminal device 400. The URL must be different from that used for a conventional update without evolution of the protocol stack of the terminal device 400. The terminal device 400 changes this URL on its own initiative.
[0110] In another exemplary embodiment, the updating of the terminal device 400 and, in particular, the downloading of the complementary part of the new communication protocol, can also be carried out by the TR-069 protocol. The TR-069 protocol (“Technical Report” or CWMP for “CPE WAN Management Protocol”) is a protocol defined for managing communication between equipment on a user’s local network and a remote autoconfiguration server accessible via a WAN. In this case, a version download URL address is provided by a SER server, which is for example an ACS (for “Automatic Configuration Server” in English) type server. The terminal device (for example a wireless repeater) cannot therefore differentiate the URL address for a conventional update from that for an evolution of the communication protocol (for example communication protocol according to the EasyMesh standard). The terminal device 400 (eg, wireless repeater) will therefore indicate a change of protocol by a TR-69 notification called “inform value change”. The name of the new communication protocol detected must be present in a field called “data model” and when the value of this field changes then the terminal device 400 sends the notification to inform the ACS server that an update is desirable.
[0111] At the end of the discovery phase comprising steps 201 to 207, the terminal device 400 executes a phase of updating its current communication protocol.
[0112] During a step 208, denoted CHG_P, the terminal device 400 then performs a phase of updating its communication protocol or protocol stack. In particular, the terminal device 400 replaces the old communication protocol (i.e., first communication protocol Proto_1) with the new communication protocol (i.e., second communication protocol Proto_2). The terminal device 400 can then fully use the new communication protocol Proto_2 in its complete version.
[0113] During a step 209, noted SUP_PCOM_C, the terminal device 400 deletes the old communication protocol (i.e., the first communication protocol Proto_l) has become obsolete. It is thus possible to optimize storage space by keeping only the communication protocol, for example the most recent one, used in the local LAN communication network.
[0114] In a particular embodiment, it may happen that several controller devices are present in the local communication network. This is the case, for example, when a new controller device is added to the local communication network LAN, for example to replace the one currently present. These controller devices then implement different communication protocols. In particular, one of the controller devices implements a more recent communication protocol than the other controller device. In this case, the terminal device 400 implements several discovered functions associated with these different communication protocols. The terminal device 400 then detects several different communication protocols.Determining the “dominant” communication protocol consists of selecting the most recent communication protocol from the set of communication protocols used by the different controller devices. For this, the terminal device 400 has in memory a list of communication protocols classified from the most recent to the least recent with for each communication protocol the discovery function relating to it. The terminal device 400 then attempts to discover each communication protocol in the order of this list. In other words, the terminal device 400 first executes the discovery function of the most recent communication protocol. The download procedure is then triggered for the most recent communication protocol from the set of communication protocols used by the controller devices.
[0115] [Fig.4] schematically illustrates the hardware architecture of a terminal device 400 configured to execute all or part of the steps of the method illustrated in Figs. 2 and 3A and 3B.
[0116] The terminal device 400 comprises, connected by a communication bus 410: a processor or CPU (Central Processing Unit) 401; a RAM (Random Access Memory) 402; a ROM (Read Only Memory) 403, for example a Flash memory; a data storage device, such as a hard disk drive (HDD), or a storage media reader, such as an SD card reader (Secure Digital) 404; at least one I / f communication interface 405 allowing the terminal device 400 to interact with the other terminal devices of the local communication network LAN, as well as with the controller device CONT.
[0117] The processor 401 is capable of executing instructions loaded into the RAM 402 from ROM 403, from an external memory (not shown), from the data storage device 404, such as an SD card, or from a communication network (not shown). When the terminal device 400 is powered on, the processor 401 is capable of reading instructions from RAM 402 and executing them. These instructions form a computer program causing the processor 401 to implement the behaviors, steps and algorithms described herein, in particular in combination with all or part of the steps of Figs. 2 and 3A and 3B.
[0118] All or part of the behaviors, steps and algorithm described herein may thus be implemented in software form by executing a set of instructions by a programmable machine, such as a DSP (Digital Signal Processor) or a microcontroller, or be implemented in hardware form by a machine or a dedicated component (chip) or a set of components (chipset), such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Generally speaking, the terminal device 400 comprises electronic circuitry arranged and configured to implement the behaviors, steps and algorithms described herein.
[0119] It should also be noted that the term "module" can correspond to a software component as well as to a hardware component or a set of hardware and software components, a software component itself corresponding to one or more computer programs or sub-programs or more generally to any element of a program capable of implementing a function or a set of functions.
Claims
Claims
1. Method for managing an update of a terminal device (400, NI, N2, N3, UE1, UE2, UE3) belonging to a local communication network (LAN) managed by a controller device (CONT), the terminal device (400, NI, N2, N3, UE1, UE2, UE3) communicating with the controller device (CONT) via a current communication protocol, the method being implemented by the terminal device (400, NI, N2, N3, UE1, UE2, UE3), and comprising: - storing in memory a first part of another communication protocol, different from the current communication protocol, - executing a discovery phase during which the terminal device (400, NI, N2, N3, UE1, UE2, UE3) uses said first part to: - transmit to the controller device (CONT) at least one probe message specific to said other communication protocol, - waiting for at least a response message responding to at least one probe message sent,from the controller device (CONT), - checking whether at least one said response message is received and then downloading a second part of said other communication protocol, complementary to said first part, so as to have a complete version of said other communication protocol, - executing an update phase of the terminal device (400, NI, N2, N3, UE1, UE2, UE3) comprising: replacing, in the terminal device (400, NI, N2, N3, UE1, UE2, UE3), the current communication protocol with said other communication protocol as the new current communication protocol.,
2. Method according to claim 1, in which the phase of updating the terminal device further comprises deleting from the terminal device (400, NI, N2, N3, UE1, UE2, UE3) the current communication protocol which has become obsolete.
3. Method according to one of claims 1 and 2, in which the probe message is transmitted repeatedly and the second part of said other communication protocol, complementary to said first part is downloaded if, over a predefined period (P), a number of response messages received is greater than or equal to a predefined reliability threshold (S).
4. A method according to any one of claims 1 to 3, wherein the transmitted probe message is transmitted according to a broadcast type transmission.
5. Method according to any one of claims 1 to 4, wherein the probe message is transmitted according to a predefined transmission frequency (F).
6. Method according to claim 5, wherein the predefined transmission frequency (F) is between 1s and 5min.
7. A method according to any one of claims 1 to 6, further comprising storing in memory a list of a plurality of other communication protocols, different from the current communication protocol, said other communication protocols being classified according to an order from the most recent communication protocol to the least recent, and for each other communication protocol in the list, storing in memory a first part of said other communication protocol in question, and in which the discovery phase, during which the first part of each said other communication protocol is used, is carried out according to the order of said list.
8. Method for updating a system comprising a terminal device (400, NI, N2, N3, UE1, UE2, UE3) and a controller device (CONT) which belong to a local communication network (LAN) managed by the controller device (CONT), the terminal device (400, NI, N2, N3, UE1, UE2, UE3) communicating with the controller device (CONT) via a current communication protocol, the method comprising: - updating the terminal device (400, NI, N2, N3, UE1, UE2, UE3) by downloading a first part of another communication protocol, different from the current communication protocol, - triggering an execution of the method according to any one of claims 1 to 7, so as to trigger the discovery phase by the terminal device (400, NI, N2, N3, UE1, UE2, UE3);- updating the controller device (CONT) by downloading the full version of said other communication protocol, so that the controller device (CONT) responds to said probe messages received from the terminal device (400, NI, N2, N3, UE1, UE2, UE3) during the discovery phase by the terminal device (400, NI, N2, N3, UE1, UE2, UE3).;
9. Terminal device (400, NI, N2, N3, UE1, UE2, UE3) intended to ap- participate in a local communication network (LAN) managed by a controller device (CONT), the terminal device (400, NI, N2, N3, UE1, UE2, UE3) being configured to communicate with the controller device (CONT) via a common communication protocol, said terminal device comprising electronic circuitry configured to: - store in memory a first part of another communication protocol, different from the current communication protocol, - execute a discovery phase during which the terminal device (400, NI, N2, N3, UE1, UE2, UE3) uses said first part to: - send to the controller device (CONT) at least one probe message specific to said other communication protocol, - wait for at least one response message responding to T at least one probe message sent, from the controller device (CONT), - checking whether at least one said response message is received and then downloading a second part of said other communication protocol, complementary to said first part, so as to have a complete version of said other communication protocol, - performing an update phase of the terminal device (400, NI, N2, N3, UE1, UE2, UE3) comprising: replacing, in the terminal device (400, NI, N2, N3, UE1, UE2, UE3), the current communication protocol with said other communication protocol as the new current communication protocol.
10. Computer program product, comprising instructions causing the execution, by a processor, of the method according to any one of claims 1 to 6, when said instructions are executed by the processor.
11. Storage medium, storing a computer program comprising instructions causing a processor to execute the method according to any one of claims 1 to 6, when said instructions are read and executed by the processor.