METHOD OF CONFIGURING A CENTRAL CONTROL UNIT BELONGING TO A HOME-AUTOMATION INSTALLATION

Abstract

The present invention relates to a method of configuring a central control unit (U) belonging to a home-automation installation (U) or a home-automation device (D) comprising a central control unit (U) and belonging to a home-automation installation, the method being implemented by the central control unit (U) and comprising the following steps: Obtaining (EcfU16) of a location identifier (SvclcL) of a first remote configuration service (Svlc); Dispatching (EcfU17) of a configuration request (MConn) destined for the first remote configuration service (Svclc) by using the location identifier (SvclcL) and linked with an identifier of the central control unit (U); Reception (ECfU 19) of at least one set of data or of configuration instructions (cfgl) and/or of at least one identifier of a second functional remote service (Svc2) originating from the first remote configuration service (Svclc); Configuration (ECfU20) on the basis of the at least one set of data or of configuration instructions (cfgl) and/or of the at least one identifier of a second functional remote service (Svc2);

Claims

1. A method for configuring a central control unit (U) belonging to a home automation installation or to a home automation device comprising a central control unit and belonging to a home automation installation , the method being implemented by the central control unit and comprising the following steps: obtainment of a location identifier of a first configuration remote service (Sv1c); sending a configuration request to the first configuration remote service using the location identifier and linked to an identifier of the central control unit; reception of at least one set of configuration data or instructions and/or of at least one identifier of a second functional remote service originating from the first configuration remote service; configuration on the basis of the at least one set of configuration data or instructions and/or of the at least one identifier of a second functional remote service.

2. The configuration method according to claim 1, further comprising the following step: establishment of a communication to the functional service.

3. The configuration method according to claim 2, further comprising the following step: reception of at least one second set of configuration data or instructions originating from the second functional remote service; complementary configuration on the basis of the second set of configuration data or instructions.

4. A method for configuring a central control unit belonging to a home automation installation or a home automation device comprising a central control unit and belonging to a home automation installation , the method being implemented by a first configuration remote access service (Svclc) executed by a management unit (Sv1) and comprising the following steps: reception of a configuration request originating from the central control unit linked to an identifier of the central control unit; determination of at least one set of configuration data or instructions and/or of at least one identifier of a second functional remote service associated to the identifier of the central control unit in an assignment repository; sending a configuration message comprising the at least one set of configuration data or instructions and/or the at least one identifier of a second functional remote service.

5. The configuration method according to claim 4, further comprising the following steps: reception of a registration request in connection with a unique identifier of the central control unit or of the home automation device comprising the central control unit and with a second functional service; Registration registration in an assignment repository of an association between the central control unit or of its identifier linked to a functional service.

6. The configuration method according to claim 4, further comprising the following steps: subscription in a user repository of an association between the central control unit or its identifier linked to a user.

7. The configuration method according to claim 5, further comprising the following steps: check of the availability of the unique identifier before an assignment repository.

8. The configuration method according to claim 4, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

9. The configuration method according to claim 5, further comprising the following steps: subscription in a user repository of an association between the central control unit or its identifier linked to a user.

10. The configuration method according to claim 9, further comprising the following steps: check of the availability of the unique identifier before an assignment repository.

11. The configuration method according to claim 6, further comprising the following steps: check of the availability of the unique identifier before an assignment repository.

12. The configuration method according to claim 5, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

13. The configuration method according to claim 6, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

14. The configuration method according to claim 7, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

15. The configuration method according to claim 9, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

16. The configuration method according to claim 10, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

17. The configuration method according to claim 11, further comprising the following steps: check of the existence and of the rights of the user corresponding to the identifier before a user repository.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0076] The invention will be better understood from the detailed description which is exposed hereinafter with reference to the appended drawing in which:

[0077] FIG. 1 is a schematic view of a building and of a home automation installation in accordance with an embodiment of the invention;

[0078] FIG. 2 is a diagram presenting an architecture of a system comprising the home automation installation illustrated in FIG. 1, a second home automation installation, as well as a plurality of servers intended to be connected to the home automation installations;

[0079] FIG. 3 is a diagram illustrating an implementation of a configuration method;

DESCRIPTION WITH REFERENCE TO THE FIGURES

[0080] In the following detailed description of the figures defined hereinabove, the same elements or the elements filling identical functions may preserve the same references so as to simplify the understanding of the invention.

DESCRIPTION OF A SYSTEM COMPRISING A HOME AUTOMATION INSTALLATION

[0081] As illustrated in FIG. 1, a building 1 comprises for example three rooms Ro1, Ro2, Ro3. The building 1 also comprises home automation equipment 3 and sensors 5.

[0082] A home automation equipment 3 may consist of an actuator arranged to displace or set an element of the building 1, for example an actuator 7 for displacing a rolling shutter 9 or a terrace awning 19, or a regulation system 10 for a heater 11 or a ventilation system 13. A home automation equipment 3 may also consist of a lighting, for example a terrace external lighting 21 or a lighting control system, an alarm system, or still a video camera, in particular a video-surveillance camera.

[0083] The home automation installation Su may also comprise a control point 15 an actuator 7, such as a wireless control box B for the rolling shutter 9.

[0084] The home automation installation Su may comprise one or several sensor(s) 5, integrated to an actuator 7, to a control point 15 or to the control box B or independently of these elements. In particular, a sensor 5 may be arranged to measure a physical unit, for example a temperature sensor, an insolation sensor or a humidity sensor. Position sensors 5 of home automation equipment 3 of the building 1, such as, for example, sensors of the open state of a rolling shutter 9 or sensors of the position of a door leaf such as a window, whether motorized or not, may also be provided. The home automation installation may also comprise one or several presence sensor(s). The installation may also comprise one or several electric consumption sensor(s).

[0085] A home automation equipment 3 and a sensor 5 should thus be considered as units having information on observed actual states of elements of the building 1 and being capable of sharing this information with other elements of the home automation installation Su.

[0086] The home automation equipment 3 and the sensors 5 can thus have access to any measurable physical unit, such as the temperature of each room Ro1, Ro2, Ro3 or a state of an element of the building 1, such as the open state of a rolling shutter 9, the state of an alarm, etc.

[0087] In the following, we will use the home automation device or device D designation indifferently to designate sensors or home automation equipment, or parts of home automation equipment 3 or sensors 5.

[0088] In general, the home automation devices comprise a processing unit comprising a processor executing an embedded software. This software undergoes updates to improve the functions thereof or to proceed with corrections.

[0089] The home automation installation Su comprises a central control unit or a plurality of central control units U1, U2. In particular and as example, two central control units U1, U2 are represented in FIG. 1. According to one variant, a home automation installation may also comprise one single central control unit.

[0090] Each central control unit U1, U2 is arranged to control and/or monitor part of the devices D of the installation Su forming a group DGrU1, DGrU2. As example, in FIG. 1, the central control unit U1 is in charge of the devices D disposed in the rooms Ro1 and Ro2 of the first floor of the building, whereas the central control unit U2 is in charge of the devices D disposed in the room Ro3 on the ground floor of the building and the external devices.

[0091] In particular, the control and/or monitoring is carried out remotely, in particular using a wireless communication protocol, for example a radio communication protocol. Each central control unit U1, U2 is arranged to group together all data originating from the devices D of its group DGrU1, DGuU2 and to process these data.

[0092] As represented in FIG. 2, each central control unit U is arranged to communicate with one or several remote server(s) Sv1i, Sv1c, Sv2.

[0093] The central control units U1, U2, U3 are disposed on a private network PN, PNʹ, whose access is generally protected by a firewall FW. In particular, in the example represented in FIG. 2, two central control units U1, U2 are disposed on a first private network corresponding to a first home automaton installation, while a third central control unit U3 is disposed on a second private network PNʹ, independent of the private network PN corresponding to a second home automation installation Su’. The private network PN is linked to a wide area network N, for example the Internet. We will describe in the following one of these units.

[0094] A central control unit U comprises a processing unit 2 arranged to contain and execute a first computer program. As example, the processing unit 2 comprises a processor, a storage flash memory as well as a random access memory, and an Ethernet chip.

[0095] The processing unit executes an embedded software. This software undergoes updates to improve the functions thereof or to proceed with corrections.

[0096] The central control unit U further comprises at least one communication module 2ʹ intended to monitor and/or control home automation equipment 3 and/or sensors 5, the home automation equipment 3 may consist of actuators 7, lightings 21, an alarm system, or a video camera.

[0097] As example, as represented in FIG. 2, the communication module 2ʹ enables the monitoring and control of at least one actuator 7, a movable element of the building 1, such as for example a rolling shutter 9, or an orientable sunshade 9ʹ or other actuators 7 or lightings 21, as previously described with reference to FIG. 1, according to at least one local communication protocol.

[0098] As example, the communication module 2ʹ may be arranged to implement for example one or more of the local first protocols P1 such as for example Z-Wave, EnOcean, io-Homecontrol, Somfy RTS, KNX, MODBUS, Wavenis, Philips HUE. In general, these local first protocols are non-IP local communication protocols.

[0099] According to another possibility, for example in the context of alarm systems, the central control unit may be integrated into the home automation device. According to still another possibility, the central control unit may also be integrated to a router and/or a modem achieving a connection to a wide area network, in particular the Internet.

[0100] When the central control unit is integrated to a home automation device, the communication module 2ʹ intended for the monitoring and/or control of the device may be a communication module internal to the home automation device and/or a communication module intended for the monitoring and/or control of other home automation devices.

[0101] There is also provided the reception of information from a sensor 5 providing information on the presence of a user or values of the surrounding parameters such as temperature, humidity and luminosity. In the same manner, the central control unit U may enable the monitoring and/or control of an alarm system.

[0102] Each central control unit U may further comprise a communication module 4ʹ for communicating according to a communication protocol other than the local first protocol. For example, the target second communication protocol may be a communication protocol above the IP protocol on a local area network, or else a generic point-to-point protocol. As example, the application protocol WEAVE using transport protocols 6lowpan and thread for a mesh network may constitute a second protocol. Other examples include Bluetooth, Zigbee or Wifi.

[0103] The communication terminal T may contain and execute an application software APP.

[0104] Each central control unit U further comprises a module 4 for communication with remote servers Sv1i, Sv1c, Sv2.

[0105] The server Sv enables the remote control and/or monitoring and comprises one or several processing unit(s) 102 arranged to contain and execute a second computer program.

[0106] In some applications, a central control unit U may communicate with the server Sv2 through an intermediate server, for example a third-party service provider, whose intermediate server provides a service interface or API. In turn, the server Sv2 comprises at least one communication interface 104 intended for the communication with the central control unit U.

[0107] The server Sv2 may also comprise a communication interface 106 intended for the communication with a control and/or monitoring interface IN enabling an end user Usr1 to remotely monitor the home automation installation, in particular via a functional service Svc2.

[0108] It should be noted that the term server is a logical designation which may cover the use of several physical servers to distribute the computer processing load to be carried out.

[0109] For example, the control and/or monitoring interface IN comprises a web server 107 and a mobile communication terminal T communicating via the wide area network N. For example, the mobile communication terminal T may consist of a smartphone or a tablet. The mobile communication terminal T may be the same or a terminal of the same type as that with which the central control unit U communicates locally by means of the communication module 4ʹ, or a different terminal. We will designate these mobile terminals indifferently by the reference T. Alternatively, the end user may also use a stationary terminal.

[0110] The control and/or monitoring interface IN comprises a processor which may be disposed at the level of the web server 107 and/or the mobile communication terminal T.

[0111] The processor of the control and/or monitoring interface IN is arranged to use a third computer program. In turn, this third computer program is arranged to execute a downloadable application.

[0112] The mobile communication terminal T comprises a data input device and a display device, for example in the form of a tactile control portion of a screen of the terminal T and in the form of one or several button(s) of the terminal T.

[0113] The Server Sv2 may also use the communication interface 104 or another interface for the communication with another server or several servers Sv1i and Sv1c for subscription and configuration implementing subscription and configuration services Svc1i and Svc1c that we will describe later on.

[0114] This interface enables the communication between the servers Sv1i, Sv1c and Sv2 on a local or wide area network, for example the Internet.

[0115] The servers Sv1c and Sv1i may take on the same architecture as the server Sv2.

UNIQUE IDENTIFIER OF A HOME AUTOMATION DEVICE

[0116] The servers Sv2, Sv1i and Sv1c, the services Svc1i, Svc1c and Svc2 as well as the central control units U may use a unique identifier to identify the home automation devices. The structure of a unique identifier of a home automation device DURL will now be described in connection with a particular embodiment.

[0117] According to this embodiment, the unique identifier of a home automation device comprises information on: [0118] The local native protocol of the home automation device D; [0119] The communication path to the device D, including the intermediate central control units U and the termination addresses to cross, whether organized or not in a hierarchical topology; [0120] A subsystem identifier subsystemId if the device belongs to a group of devices D associated to the same address. The devices that are a unique expression of an address have no extension for identifying a subsystem.

[0121] Thus, the form of the unique identifier of a device DURL may be as follows:

[0122] <protocol>://<gatewayId>/<rawDeviceAddress>(#<subsystemId>)

[0123] Wherein the following fields are present: [0124] protocol: identifier of the native device local protocol. [0125] gatewayld: identifier of the first central control unit U, for example a serial number or a unique identifier. [0126] rawDeviceAddress: a simple or multi-level path. Its meaning and its format depend on the addressing scheme of the local communication protocol of the device D. [0127] subsystemld: this optional field indicates an identification, for example a rank of the subsystem (starting for example at 1), if such a subsystem is present.

EXAMPLES

1) Knx://0201-0001-1234/1.1.3

[0128] This unique identifier DURL corresponds to a device D communicating by the KNX procotol with an individual address 1.1.3 accessible to the central control unit U carrying the identifier #0201-0001-1234.

2) Io://0201-0001-1234/145036#2

[0129] This unique identifier GDURL corresponds to a subsystem carrying the number 2 associated to a device D communicating by the io-Homecontrol protocol with a radio address 145036 accessible to the central control unit U carrying the identifier #0201-0001-1234.

FIRST SUBSCRIPTION AND/OR CONFIGURATION SERVICE AND SECOND SERVICE

[0130] The first configuration service Svc1c is intended to identify the correct technical configuration for the home automation device or the considered central control unit and to communicate configuration information to the central control unit. In particular, the configuration service Svc1c allows assigning a central control unit or a home automation device to a user service.

[0131] The first subscription service Svc1i allows proceeding with the subscription by a user of a central control unit or a home automation device to a user service. By user, it should be understood an end user, an installer or a maintenance operator. Alternatively, the subscription request may be directly emitted by the central control unit U or the home automation device D comprising the central control unit U during the initial operation thereof through a connection on this service Svc1i.

[0132] These two first services Svc1c and Svc1i will be described separately, but they may be confused. These two first services may be hosted by the same server or group of servers or by distinct servers or groups of servers Sv1i and Sv1c as described as example in FIG. 2.

[0133] The second service or functional service Svc2 corresponds to a user service intended for the monitoring and/or control and/or supervision of the home automation installation by a user or by an application. The functional service is a remotely-accessible computerized service, which enables access to at last one control or supervision function of a home automation installation or of a home automation device, by means of a user interface or an application. The user interface may be accessible by a graphical interface, or through a programming interface.

[0134] The service Sv2 may be implemented by the same server as the first services, or by another server or group of servers Sv2, as described as example in FIG. 2.

[0135] The first services Svc1i, Sv1c may be under the monitoring of a first entity and the second service Svc2 may be under the monitoring of a second entity.

[0136] As example, the first entity may be an infrastructure or home automation installation management supplier, and the second entity may be a supplier of services related to the supervision or the control of home automation devices.

ASSIGNMENT REPOSITORY

[0137] The first configuration service Svc1c implements an assignment repository R1. The assignment repository R1 stores the correspondence between an identifier of a central control unit U and an identifier of a second functional service Svc2. The Table 1 below provides an example of a first data structure of the repository R1. This repository may also comprise optional configuration information.

[0137] TABLE-US-00001 Example of a second data structure of the repository Rf Identifier of the central control unit UID Identifier of the functional service Optional specific configuration cfg UID1 Svc2ID1 Cfg11 UID2 Svc2ID2 Cfg 12

[0138] As example, the repository may be constituted by a data base or a depository service. This repository may be comprised in the first configuration service Svc11 or external and accessible by the first configuration service Svc11.

USER REPOSITORY

[0139] In order to define the configuration that has to be applied to a central control unit U, the second functional service Svc2 may use a repository Rf2, which may be comprised in the assignment repository or distinct, but still accessible by the second functional service Svc2.

[0140] The user repository Rf2 comprises associations between an identifier of a central control unit UID, an identifier of a user account USrID, and possibly a specific functional configuration cfgF. An example of a definition table contained in the user repository Rf2 is represented hereinbelow in Table 2.

TABLE-US-00002 Example of a definition table in the repository Rf2 Identifier of the central control unit UID Identifier of the user USrID Optional specific functional configuration cfg2 UID1 UsrID1 Cfg21 UID2 UsrID2 Cfg22

CONFIGURATION METHOD

First Embodiment

[0141] We will now describe a method for configuring a remote access to at least one home automation device D belonging to a home automation installation Su with reference to FIG. 3.

[0142] In an initial state, the user Usr has made the acquisition or obtained a home automation device D and/or a central control unit U.

[0143] The home automation device D or the central control unit U contains at least one location identifier Svc1cL corresponding to an information related to the address of the service Svc1c.

[0144] According to one variant, the central control unit U may contain a plurality of services Sv1c accessible according to the geographical area. In these conditions, the central control unit may attempt to enter into communication successively with these services.

[0145] However, the home automation device D or the central control unit U has no information related to the functional service Svc2. Moreover, the configuration of the central control unit U or of the home automation device D may be incomplete with regards to: [0146] the technical configuration; [0147] all or part of its software; [0148] the connectivity to the server; [0149] its behavior; [0150] the functional or commercial offerings to be implemented.

[0151] In a prior step, the service Svc1 obtains a list of the possible services SvC2, as well as the address of the service Sv1D, as well as a catalog of services offerings.

[0152] At a step ECfUsr1, the end user Usr emits a subscription request Min before the service Svc1i which receives this request at a step ECfSvc1i1. In particular, the subscription request comprises a unique identifier UID of the central control unit U. This unique identifier UID may for example comprise a MAC address or a serial number. This identifier may be in the form of a QR (or QR-Code, standing for “Quick Response Code”) code or another on or two dimension barcode optically readable on the central control unit U or the device D or their packaging, or in the form of a radio frequency identification tag (or RFID, standing for “Radio Frequency IDentification”), a near field communication tag (or NFC, standing for “Near Field Communication”) or any other tag readable by a device available to the user, such as for example a mobile communication terminal T.

[0153] The subscription request also comprises the identifier UsrID of the user if the user has a user account. The subscription request also comprises a service selection to associate to the central control unit U. The subscription request may also comprise at least one option selection. As example, the options may correspond: to the number and to the nature of the home automation communication protocols or others that are activated; to the activation, or not, of a feedback of values from a sensor for data logging on the management unit; to a setting of a limit on the number of home automation devices that can be paired.

[0154] The service Svc1i proceeds with a check of the availability of the unique identifier UID before an assignment repository Rf1. According to one possibility, this repository Rf1 is implemented by a configuration and distribution service Svc1c. In these conditions, the subscription service Svc1i sends a check request at a step ECfsvc1i2.

[0155] The configuration service Sv1c receives the request MDisp at a step ECfSvc1c2 and proceeds with the check at a step ECfSvc1c3. The result of the check MRDisp is communicated to the service Svc1i at a step EcfSvc1c4, which receives it at a step ECfSvc1i4. In this case, we will suppose that the availability of the identifier UID has been recognized. Otherwise, this means that the subscription request cannot be addressed because the central control unit is already associated to a service. Hence, a conflict concerning this identifier should be solved.

[0156] To the extent that the availability of the identifier UID is confirmed, the service Sv1i proceeds with a check of the existence and of the rights of the user Usr corresponding to the identifier UsrID before a user repository Rf2. According to one possibility, this repository Rf2 is implemented by the functional service Svc2. In these conditions, the subscription service Svc1 sends a check request at a step ECfsvc1i5.

[0157] The considered service Svc2 receives the request MUsrDisp at a step ECfSvc25 and proceeds with the check at a step ECfSvc26. The result of the check MUsrRDisp is communicated to the service Svc1 at a step EcfSvc27, which receives it at a step ECfSvc1i7.

[0158] If a user account for the user Usr does not exist yet, a user account creation step may be carried out at this level. If it already exists, the check of the user account may comprise a request for a password from the user, as represented at step ECfUsr6.

[0159] In this case, we will suppose that the availability of the identifier Usr has been recognized. Otherwise, this means that the subscription request cannot be addressed because the associated user account associated on the service is not valid. Hence, a valid user account on this service should be determined before resuming the subscription.

[0160] To the extent that the validity of the user account and of the identifier is confirmed, the service Svc1i proceeds with a step of registering the service Svc2. According to one possibility, this registration is operated by the configuration service Svc1c.

[0161] Thus, at a step EcfSvc1i8, the service Svc1i sends a registration request MReg to the configuration service Svc1c comprising a functional service selection Svc2, for example Samsung IOT or Google IOT, the identifier of the central control unit UID, a service offering selection and possible configuration options. The configuration service Svc1c receives this request at a step ECfSvc1c8.

[0162] At a registration step ECfSvc1c9, the service Svc1c proceeds with the registration in the assignment repository Rf1 of an association between the central control unit U or its identifier UID linked to a functional service Svc2 and possibly with complementary configuration information Cfg1.

[0163] The service Svc1c sends a confirmation MRUIn of this subscription at a step ECfSvc1c10 to the service Svc1i which receives it at a step ECfSvc1i10.

[0164] Afterwards, the service Svc1i proceeds with a subscription of the service Svc2. According to one possibility, this subscription is operated by the functional service Svc2.

[0165] Thus, at a step EcfSvc1i11, the service Svc1i sends a subscription request MUsrln to the functional service Svc2 comprising: the identifier of the central control unit UID, the identifier of the user UsrID, a service offering selection and possible configuration options. The functional service receives this request at a step ECfSvc211.

[0166] At a configuration/subscription step ECfSvc212, the service Svc2 proceeds with the subscription in the user repository Rf2 of an association between the central control unit U or of its identifier UID linked to a user Usr and possibly to complementary functional configuration information Cfg2.

[0167] The service Svc2 sends a confirmation MRUsrln of this subscription at a step ECfSvc213 to the service Svc1i which receives it at a step ECfSvc1i13.

[0168] Afterwards, the service Svc1i may confirm the subscription to the user Usr through his terminal at a step EcfSvc1i14, the confirmation being received at a step EcfUsr114.

[0169] Next, it is proceeded with a plugging or initialization of the central control unit U at a step ECfU15. This plugging/initialization may be triggered by an electric power supply or by an order, at a step EcfUSr115, originating from an instruction of the user through a physical action on the central control unit U such as a press on a button or a sending of instruction via a terminal T. In the context of this plugging or following this initialization, the central unit obtains, at a step EcfU16, the location identifier Svc1cL of the configuration service which may correspond to a URL, this identifier having been stored beforehand, for example in factory, in the memory of the central control unit U.

[0170] Afterwards, the central control unit U proceeds, at a step EcfU17, with an attempt to connect to the configuration service SV1c using the location identifier Svc1cL. This connection attempt MConn identifies the central control unit by the identifier UID. This connection attempt corresponds to a configuration request. Of course, several successive steps may be carried out corresponding to the establishment of a communication, and then to the configuration request.

[0171] When the plugging of the central control unit is performed before the subscription having been carried out, the service Svc1c may indicate to the central control unit U that it cannot proceed with the configuration. In this case, the central control unit U may proceed with requests periodically.

[0172] On reception of this configuration request at a step EcfSvc1c17, the service Svc1c proceeds with a check at a step ECfSvc1c18 in the assignment repository Rf1 in order to determine whether the identifier UID is actually assigned, and which are the associated data. In particular, the service Svc1c may determine an associated functional service Svc2 and the associated connection information, but also possible configuration information Cfg1.

[0173] Afterwards, the service Svc1c may send back one or several configuration message(s) MCfg at a step ECfSvc1c19 which are received by the central control unit U at a step ECfU19.

[0174] At a step ECfU20, the central control unit U proceeds with its configuration on the basis of the information received from the service in the message MCfg, and in particular with the registration of the connection data concerning the functional service Svc2 and other configuration elements Cfg1.

[0175] For example, the identifier of a second remote functional service may correspond to: a host name or IP address of the service; a port number to be used; a protocol to be used, for example HTTPS or COAP.

[0176] The other configuration information in the set of configuration data Cfg1 may comprise: an adaption of the frequency band, in particular depending on the geographical position; an authorization of the use of determined communication protocols; the loading of software components, for example particular drivers; the update, possibly depending on the geographical area; or else the configuration of the graphical interface, comprising for example the download of a logos/icons or software components to modify the appearance or the behavior of a display.

[0177] At a step EcfU21, the central control unit U proceeds with the establishment of a connection MConnF, whether permanent or not, or with the emission of information in a periodic or event-based manner to the functional service Svc2 which receives the corresponding information at a step ECfSvc221.

[0178] According to one possibility, at a step ECfU22, the central control unit U proceeds with a complementary configuration on the basis of a configuration portion Cfg2 originating from the functional service Svc2 which provides this configuration at a step EcfSvc222.

[0179] This configuration may correspond for example to a download of a software element, or to a complementary configuration of services.

[0180] At a step ECfUsr23, according to one possibility, the user may start using the service Svc2.

[0181] According to one possibility, a reset of the central control unit U may be provided for. In this case, a notification step may be carried out before the subscription service Svc1i in order to reset the repositories Rf1 and Rf2, respectively via the services Svc1c and Svc2. Afterwards, the central control unit U can be used again in a different configuration, based on the selections communicated by the user.