EP3688584A1

EP3688584A1 - Remote administration technique

Info

Publication number: EP3688584A1
Application number: EP18786846.8A
Authority: EP
Inventors: Emna MEZGHANI; Samuel BERLEMONT; Julien ROULAND
Original assignee: Orange SA
Current assignee: Orange SA
Priority date: 2017-09-29
Filing date: 2018-09-25
Publication date: 2020-08-05
Also published as: WO2019063932A1; FR3071939A1; US20200267204A1

Abstract

The invention concerns a technique for remote administering of a device (20,21) by an administration server (31). A management operation is to be executed by the administration server on the device. A piece of information on state of use of the device is then obtained and an execution impact of the management operation is evaluated for a quality of service for a service supplied by the device, depending on the piece of information obtained and the management operation to be executed. A postponement of the execution of the management operation is requested from the administration server. This postponement is determined according to the piece of information obtained, that impact and a policy for executing management operation defining an association between a state of use of a device, an operation and an impact.

Description

Remote Administration Technique

The invention relates to the general field of telecommunications.

The invention more particularly relates to the remote administration of a device by an administration server. This device belongs for example to a local network.

In order to guarantee quality services, it is preferable for a network operator to remotely administer devices.

Remote administration of devices requires, in particular:

to detect and know the devices administered, for example their serial numbers, their hardware and software versions;

supervise these devices, for example by obtaining supervisory information and performance indicators.

In a local area network, an access gateway allows devices located in a customer site to access a Wide Area Network (WAN), such as the Internet. These devices are also known as CPE for Customer Premises Equipment. For a local network, these include the access gateway, a set-top-box TV decoder, a mobile terminal. In the context of a home automation network, it is also equipment of household appliances, alarm systems, sensors.

The remote management of the devices of a local network relies for example on a technical report developed by the Broadband Forum, TR-069 "CPE WAN Management Protocol". This technical report defines a CWMP protocol, specifying the communication between an administration server, called the ACS remote auto-configuration server (for "Auto-configuration Server"), and a device of the local network. The CWMP protocol defines a mechanism that allows in particular secure self-configuration of the devices of the local network and other management functions of these devices.

In particular, it is possible for the network operator to perform remote interventions, such as:

updating the software ("software") or the firmware of a device, when a change in the software version or microcode is required; - make a diagnosis when a device has a malfunction;

dynamically install and configure new services;

monitor the operating status and performance of a device. The CWMP protocol relies on the Internet protocol, more specifically on TCP / IP (for Transmission Control Protocol).

Remotely updating the software or firmware is an operation that requires special precautions. It is best not to interrupt while running. This may corrupt the software or firmware and prevent operation of the device being updated. In addition, the update operation may generate a service interruption at the device. When the device is a WAN access gateway for a set of LAN devices, the service is also interrupted for that set of devices. The updates are then often programmed by the operator to run during the night in order to limit the impacts. However, it is not guaranteed that the device to be updated is not in use during a night update. It is emphasized here that the updates generally take place without a validation request from a user of the device. This problem related to the execution of an update arises for any device administered remotely.

One of the aims of the invention is to remedy the shortcomings / disadvantages of the state of the art and / or to make improvements thereto.

According to a first aspect, the subject of the invention is a method of remote administration of a device by an administration server. This process comprises:

obtaining status information of use of the device for which a management operation is to be performed;

a request to postpone the execution of the management operation to the administration server, said report being determined according to the information obtained, an evaluation of an impact of the execution of the operation of management on the operation of the device and a management operation execution policy.

More specifically, the method comprises:

obtaining status information of use of the device for which a management operation is to be executed;

- evaluating an impact of the execution of the management operation for a quality of service for a service provided by the device according to the information obtained and the management operation to be performed:

determination of a postponement of the execution of the management operation according to the information obtained, the said impact and a management operation execution policy, defining an association between a state of use of the management operation a device, an operation and an impact;

- Request to postpone the execution of the management operation to the administration server The remote administration method originates from a problem associated with an update of the software or the firmware of a device , likely to result in a complete cessation of the service or services provided by this device. However, it is applicable to any management operation to be performed on this device. The implementation of the administration method as proposed makes it possible to minimize the impact of a management operation on the quality of service provided to the user of the device. It is understood that, thanks to the method, the impact of the management operation for a user of the device is limited. This is especially important when this update causes a service interruption associated with a device restart.

This method is particularly advantageous when the network operator does not have technical means to warn the person or persons likely to use the device and seek their agreement before carrying out a management operation. Indeed, some devices do not have an elaborate human-machine interface allowing them to interact in a simple and user-friendly way. This is the case for example for TV decoders, access points to the extended communication network, residential gateways. Thus, a postponement of the management operation can be decided according to a state of use of the device on which this management operation is to be executed.

A state of use of the device is representative of an availability of the device for a management operation. This usage state takes into account one or more services running on the device and / or resources of the device. It makes it possible to evaluate an impact of a management operation on the device, in particular on the quality of service for a service provided by the device. In one embodiment, the service is a primary service provided by the device. In another embodiment, the service is a service provided by the device and in use. This evaluation of an impact on the quality of service is not taken into account in the methods of remote administration known to date.

The implementation of the proposed remote administration method thus makes it possible to adapt the existing methods by evaluating an impact of a management operation according to a state of use of the device. This results in a remote administration adapted to the device targeted by the management operation to ensure availability of services for users of the device and thus offer them a better quality of service.

The various embodiments or features mentioned below may be added independently or in combination with each other, to the steps of the remote administration method as defined above.

In a particular embodiment, the request to postpone the execution of the management operation comprises time information enabling the administration server to orchestrate the execution of the management operation.

In this embodiment, this allows the administration server to orchestrate the execution of the management operation, without the need to re-implement the method of administration.

In a particular embodiment, the postponement of the execution of the management operation is also determined according to a context associated with a user of the device.

The context associated with a device user includes information about a user of the device or its environment. These can be favorite times for a management operation, user profile, ... In this embodiment, the execution of the management operation takes into account this context in order to adapt the quality of service to the user.

In a particular embodiment, the state of use of the device is determined from information collected from the device.

In this embodiment, the device itself provides the information for determining the device usage status information. This makes it possible to better take into account the use that is made of the device to evaluate the impact of the management operation.

According to a particular characteristic, the collected information belongs to the group comprising information relating to a process running on the device, information relating to the resources available on the device.

This allows to take into account when determining a state of use of the information provided by the device such as the resources available in terms of RAM, processor capacity, and also the service or services running. on the device.

In a particular embodiment, the impact is evaluated according to a class of the management operation.

According to a second aspect, the invention also relates to an administration device arranged to cooperate with a remote administration server of a device. The administration device comprises:

a obtaining module, arranged to obtain device usage status information for which a management operation is to be executed;

a planning module, arranged to determine a postponement of the execution of the management operation according to the information obtained, of an evaluation of an impact of the execution of the management operation on the operation the device and a management operation execution policy and to request the transfer to the administration server.

More specifically, the planning module is arranged to evaluate an impact of the execution of the management operation for a quality of service for a service provided by the device according to the information obtained and the management operation to be performed. execute, to determine a postponement of the execution of the management operation based on the information obtained, an evaluation of said impact and a management operation execution policy defining an association between a state of management use of a device, an operation and an impact and to request the transfer to the administration server.

In a particular embodiment, the delivery device and the device to be administered are combined in a single device.

The advantages stated for the remote administration method according to the first aspect are directly transferable to the delivery device. In a particular embodiment, the obtaining module is further arranged to determine the status of use of the device from information collected from the device.

This delivery device can of course include in structural terms the various characteristics relating to the method of administration as described above, which can be combined or taken in isolation.

According to a third aspect, the invention also relates to a system arranged to cooperate with a remote administration server. This system includes:

at least one device to be administered comprising:

an administration module, arranged to be administered remotely by an administration server:

a module arranged to collect information relating to the device making it possible to determine information on the state of use of the device;

said system further comprising:

a module for determining a usage state, arranged to determine usage state information of the device for which a management operation is to be executed;

The advantages stated for the remote administration method according to the first aspect can be transposed directly to the system.

According to a particular characteristic, the system further comprises a collection module, arranged to obtain information relating to the device making it possible to determine information on the state of use of the device.

This system can of course include in structural terms the various characteristics relating to the method of administration as described above, which can be combined or taken in isolation.

According to a fourth aspect, the invention relates to a program for a device, comprising program code instructions for controlling the execution of those steps of the remote administration method previously described implemented by the device, when this program is executed by this device and a recording medium readable by a device on which is recorded a program for a device.

The advantages stated for the remote administration method according to the first aspect are directly transferable to the program for a device and the recording medium.

The technique of remote administration of a device will be better understood with the aid of the following description of particular embodiments, with reference to the appended drawings in which:

FIG. 1 represents a remote administration environment in a communication network in a particular embodiment;

FIG. 2 illustrates an exemplary implementation of a method of remote administration according to a particular embodiment;

FIG. 3 illustrates steps of a method of remote administration according to a particular embodiment;

FIG. 4 represents a device that can be managed remotely according to a particular embodiment;

FIG. 5 represents a delivery device according to a particular embodiment.

The environment shown in Figure 1 corresponds to that of the remote administration of devices of a local network. It is given here by way of illustration, the remote administration technique being able to be implemented in other environments.

Figure 1 shows a plurality of devices of a LAN administered remotely by a set of management equipment. The IP ("Internet Protocol") protocol is used by the devices to communicate with each other in the local network and also to communicate with a wide area network (WAN), such as the Internet network, not shown in Figure 1.

For the environment shown in FIG. 1, the term "local communication network 2" refers to a LAN (Local Area Network) network. This network can be in particular a home network or a corporate network. An access gateway 20 is arranged to provide devices on the local network with access to the extended communication network (for example the Internet) via an access network 1. The access network 1 is connected to an access network. example an xDSL access network (for "Digital Subscriber Line", the x indicating that it may be an ADSL network, HDSL, VDSL, ...). It can also be an FTTH network (for "Fiber To The Home"). No limitation is attached to the type of access network. The local network 2 may be both a wired Ethernet network, according to the IEEE 802.3 standard, a Wi-Fi type wireless network, according to the IEEE 802.11 standard or a CPL power line network.

The devices of a local area network 2 can be any device, for example domestic, having a wired or wireless network connection. This may be, for example, a computer, a touch pad 21, a mobile phone 22, a connected radio 23, a fixed telephone 24, an overhead projector 25, a television 26, a set-top box 27, a game console, electrical appliances, etc. It is limited thereafter devices administered remotely by the set of administration equipment. These devices are also known as CPE for Customer Premises Equipment. Such devices contribute to the implementation of a service provided by the operator at a customer. As such, they provide a service to a user. This is for example the gateway 20 for access to the extended communication network, the TV decoder 27, a home network controller, etc.

The set of management equipment includes a plurality of devices enabling the operator of the communication network to administer and supervise devices, including devices belonging to local networks, including the access gateway 20 and The set of administration equipment includes, in particular, an administration server 31, also called an auto-configuration server (ACS), a call center 32 and operational support centers 33 (OSS, for "Operational Support System") or business-oriented (BSS, for "Business Support System").

In the embodiment described, the administration server 31 communicates with the devices of the local network 2 for the purpose of their administration according to the CWMP remote management protocol ("CPE WAN Management Protocol") defined in the technical report TR-069 developed by the Broadband Forum, for example Amendment 5, dated November 2013. The data models used by the CWMP protocol are defined in the technical report TR-181 "Device Data Model for TR-069", for example the version Issue 2 Amendment 11, dated July 2016. No limitations are attached to the use of this particular protocol. In other embodiments, it is for example possible to implement the OMA-Device Management specification defined by the organization OMA (for "Open Mobile Alliance") for the administration of mobile terminals, for example the approved version 2.0.

By means of the CWMP protocol, the administration server 31 can notably:

- obtain and remotely manage the configuration of a device;

- initiate diagnostic tests;

- download software or firmware files and

- manage events. In the case of an access gateway, the administration server 31 can also obtain information relating to the devices connected to it.

The remote administration application uses the CWMP protocol and relies on TCP / IP protocol standards, SSL / TLS (for "Secure Sockets Layer / Transport Layer Security", HTTP (for "Hyper Text Transfer Protocol"), SOAP (for "Simple Object Access Protocol"), RPC (for "Remote Procedure Call").

FIG. 1 also shows an administration device 40 whose functions are detailed below.

We then place for illustrative purposes in the context of a local home network. No limitation is attached to this particular example and the following description is easily transferable to a local area network business network. It is also transferable to any type of device to be administered remotely.

With reference to FIG. 2, a remote administration system comprises in particular:

the administration server 31 connected to an extended communication network, arranged to remotely administer a device:

a module 101 for collecting information relating to a device;

a module 102 for determining a state of use of a device;

a module 103 for planning a management operation to be executed.

The collection module 101 is in particular arranged to obtain from a device of a local network information relating to the device, such as an identifier of the device, information relating to the (x) process (and therefore to the service (s)) running on the device, to the resources available on this device. The resources correspond for example to a processor capacity and its utilization rate, an available RAM memory capacity, a storage capacity, a battery level. The running process may be a service provided to a user of the device or a device management service executed by a remote administration device. This information is intended to help determine a state of use of the device. The collection module 101 is arranged to provide the module 102 for determining a use state this information obtained.

The module 102 for determining a usage state is arranged in particular to obtain the module 101 for collecting the information relating to a device and for determining a state of use of the device based on this information. Subsequently, this usage state is defined as follows:

"Unavailable": in this state, the communication between the administration server and the device is possible, but it is advisable not to perform any management operation;

"Used": in this state, one or more services are running and the device is partially available for a management operation; "Available": In this state, no services are running and the device is available for a management operation;

"Reserved": in this state, the device is reserved by another administration server for a management operation.

The "unavailable" usage state is determined based on information obtained from the device. As an illustration, when the battery level of a device is insufficient, it is advisable not to perform an update to avoid an interruption during the execution thereof. Still for illustrative purposes, when the RAM capacity is insufficient, it is advisable not to perform an update to avoid a failure during the execution of it.

In a particular embodiment, the determination module 102 of a use state is arranged to provide information relating to the main service associated with the device. As an illustrative example, the main service associated with an STB decoder is the television service. Still as an illustrative example, the main service associated with an access gateway is the Internet service.

In another particular embodiment, the determination module 102 of a usage state is arranged to provide, when the state of use of the device is "unavailable" or "used", additional information relating to the state such as a list of identifiers of running services, a set of available resources, a substatus of the device (for example: unavailable battery, or unavailable processor). This embodiment makes it possible to have a better precision as to the impact of the execution of a management operation on the services running on the device.

The planning module 103 is in particular arranged to determine an impact of a management operation to be executed for a device as a function of the state of use of the device received from the determination module 102 and of the management operation to be executed Op .

The management server 31 determines that an operation operation Op is to be executed for a device and sends a planning request for the management operation to be executed to the scheduling module 103.

We define a Class_Op operation class associated with each management operation. This class of operation includes the following classes:

- update of a software or a firmware of the device;

write action for data stored by the device: configuration, writing, allocation (in English "provisioning");

action of reading data stored by the device: reading, monitoring (in English "monitoring");

- diagnostic ;

restarting the device. An impact on the quality of service is determined for each management operation by the planning module 103:

definitive cessation of the service;

temporary interruption of service;

- temporary degradation of service;

no impact.

In a particular embodiment, when the impact is a temporary interruption of the service, an estimate of the interruption duration is also determined.

The scheduling module 103 is thus arranged to evaluate an impact of the management operation to be performed for the device.

In a particular embodiment, the planning module 103 also receives, when the state of use of the device is "unavailable" or "used", additional information such as a list of identifiers of the services in progress. implementation of a set of available resources. In this case, the scheduling module 103 is arranged to evaluate a plurality of impacts of the management operation to be performed for each of the determined services being executed.

The planning module 103 is also arranged to determine a decision relating to the management operation to be performed from the use state of the device, the management operation to be performed and the evaluated impact (s). More specifically, this decision corresponds to an authorization to execute the management operation or a request to postpone the execution of the management operation. To do this, the scheduling module 103 is arranged to obtain management operation execution policies, stored in a first memory zone 104.

A management operation execution policy is an association between a device usage state, an operation, and an impact.

As a first illustrative example, the impact of an update of a firmware is a risk of temporary interruption on the device concerned by this update. The following execution policy is defined:

state of use = "available", update, temporary interruption of service, authorize the management operation

state of use = "used" or "unavailable" or "reserved", update, temporary interruption of service, postpone the management operation.

As a second illustrative example, a reading of data on the device has no impact. The following execution policy is defined:

state of use = "used" or "available" or "reserved", read, no impact, authorize the management operation

state of use = "unavailable", read, no impact, postpone the management operation. It is reminded that this is only an example and any other execution policy can be defined. For example, another execution management policy may indicate that the management operation may be postponed when the use state of the device is "reserved".

The scheduling module 103 is then arranged to determine from the management operation execution policies obtained if the execution of the management operation is authorized or postponed, and to send to the administration server 31 the decision relating to to the requested management operation.

In a particular embodiment, the scheduling module 103 is further arranged to obtain a context associated with a user of the device, stored in a second memory area 105. The context associated with a user of the device comprises one or more information relating to a user of the device or its environment.

As a first illustrative example, the information obtained corresponds to a date, a time or a time slot at which the user accepts the execution of the management operation. In a particular embodiment, this information has been parameterized by the user in order to adapt it to his own needs.

As a second illustrative example, the information obtained corresponds to a criticality of the update to be performed, for example because it is associated with a security problem. This type of software update or critical firmware is allowed at any time of the day even if it interrupts the services provided by the device and in use by the user.

When this update is a critical security update, the following execution policy is defined:

state of use = "unavailable" or "used" or "available", critical security update, temporary service disruption, allow management operation

state of use = "reserved", critical security update, temporary service interruption, postpone the management operation.

Otherwise, that is, when this update does not correspond to a critical security update, the following execution policy is defined:

state of use = "unavailable" or "used" or "reserved", update, temporary interruption of service, postpone the management operation

state of use = "available", update, temporary interruption of service, allow the management operation.

As a third illustrative example, the information obtained corresponds to a profile of the user of the device. It is thus possible to define different management operation execution policies for so-called "premium" users, for which the operator does not wish to disrupt the service offering, and for other so-called "tester" users. , for which updates can be executed immediately, even to disrupt the service offer. When the user's profile is "premium", the following execution policy is defined:

state of use = "unavailable" or "used" or "reserved", update, temporary interruption of service, postpone the management operation.

When the user's profile is "tester", the following execution policy is defined:

state of use = "unavailable" or "used" or "available", update, temporary interruption of service, authorize the management operation

state of use = "reserved", update, temporary interruption of service, postpone the management operation.

Two actions with respect to the management operation are given in the preceding examples: authorizing or requesting the postponement of the execution of the management operation. It is of course possible to define other actions. In a particular embodiment, the postponement of the execution of the management operation is limited in time. The decision sent to the administration server 31 then comprises temporal information controlling an orchestration of the execution of the management operation. This temporal information is for example a transfer time or a date, allowing the administration server to orchestrate the execution of the management operation. The scheduling module 103 can then apply a policy of limiting the postponement of the execution of a management operation by authorizing it when a certain duration has elapsed since the first request. The planning module 103 is thus arranged to allow a planning of the execution of the management operation at a later date. The administration server 31 is in charge of orchestrating the execution of the management operation at a later date according to the time information provided by the scheduling module 103.

Because of this planning, the quality of service provided to a user of the device is further improved.

The described embodiment comprises different modules, each of them being dedicated to a particular function of the method of administration. It is recalled here that this cut into modules is given for illustrative purposes. For example, in a particular embodiment, the collection module 101 and the usage state determination module 102 are combined in a single module. Other combinations of these modules are also possible. The skilled person selects according to his choice and implementation constraints the location of these different modules, and their grouping where appropriate.

In a particular embodiment, the device 20, 27 comprises the information collection module 101, the usage state determination module 102 and the module 103 of planning a management operation. The device also comprises the first memory zone 104 storing the management operation execution policies and, where appropriate, the second memory zone 105 storing information relating to the user or his environment. The device is thus in charge of authorizing, postponing or planning a management operation to be executed. This embodiment is suitable for devices with sufficient processing and memory capabilities.

In a particular embodiment, the device 20, 27 comprises the information collection module 101 and the use state determination module 102. Another device, the administration device 40, located for example in the network of the operator, then comprises the module 103 for planning a management operation, the first memory area 104 memorizing the operation execution policies management and if necessary the second memory zone 105 storing information relating to the user or his environment. This administration device 40 located in the network of the operator is thus in charge of authorizing, deferring or planning a management operation to be executed. This embodiment is suitable for devices that do not have sufficient processing and memory capacities. This embodiment is also suitable when the user does not wish to make resources available to the device. This other device is mandated to contribute to the implementation of the proposed administration method. This other device can also be the access gateway 20 in charge of the local network to which the device to be administered belongs.

In a particular embodiment, a management device 40, for example located in the network of the operator, comprises the information collection module 101, the module 102 for determining a usage state, the module 103 for scheduling a management operation, the first memory area 104 storing the management operation execution policies and if necessary the second memory area 105 storing information relating to the user or his environment. The device to be administered comprises a module 208 cooperating with the collection module 101 in order to collect information relating to the device making it possible to determine information on the state of use of the device. The administration device 40 located in the network of the operator is thus completely in charge of authorizing, postponing or planning a management operation to be executed. This embodiment is suitable for devices that do not have sufficient processing and memory capacities. This embodiment is also suitable when the user does not wish to make resources available to the device. This other device is mandated to contribute to the implementation of the proposed administration method. This other device can also be the access gateway 20 in charge of the local network to which the device to be administered belongs.

These different embodiments can coexist in order to adapt to devices of different capacities. It is for example possible to obtain from the device information relating to the embodiment chosen for remote management: the device to be administered is autonomous to implement the method of administration; the device to be administered plans the management operations that target it,

the device to be administered cooperates with a device located in the network to implement the method of administration:

the device to be administered determines its state of use and the device located in the network plans the management operation,

or else the device to be administered sends only the information making it possible to determine a usage status information of the device and the device located in the network determines the utilization state and plans the management operation.

It is emphasized here that the proposed remote administration technique is independent of the application domain of the devices administered.

In particular, it can be implemented in the field of the home network, particularly for the remote management of access gateways, TV decoders and connected TVs. It is thus possible to avoid an interruption of service when an update operation of the firmware is requested by the administration server. It also helps to avoid disturbing the customer by asking if he wants to postpone this update. Based on the TV program and a context of TV usage by the customer, the proposed administration technique schedules a date for the update.

It can also be implemented in the medical field, in particular for the remote management of connected medical devices. These devices make it possible to transmit in real time data on the evolution of the state of health of the patient to the health care team. The proposed administration technique makes it possible to guarantee the transmission of this information based on the state of use of the equipment. By taking into account a medical device reservation schedule, the proposed administration technique plans the management operation to be performed when the device is in an "available" usage state. Depending on the capabilities of the device, the administration technique is implemented on the device itself or in the remote network.

In the field of connected objects, it is also possible to implement it to remotely manage for example a connected watch. In this case, the administration technique is preferably implemented in the network of the operator.

The remote administration technique will now be described in a particular embodiment in connection with FIGS. 2 and 3.

The execution of the following steps is triggered when a management operation is to be executed on a device 20, 27 administered by the administration server 31.

The administration server 31 sends a planning request message Ml of a management operation to be executed to the planning module 103. This Ml message includes in particular information relating to the management operation to be executed and an identifier of the device concerned by this management operation.

The planning module 103 then sends to the collection module 101 a message M2 requesting the collection of information relating to the device.

The collection module 101 interrogates the device by a message M3 and obtains (step S1) in return an identifier of the device, information relating to the (x) process (and therefore the service (s)) running on the device , to the resources available on this device.

The collection module 101 transmits to the module 102 for determining a usage state the information obtained in a message M4.

The determination module 102 determines (step S2) a state of use of the device from this information and transmits it in a message M5 to the planning module 103. This message M5 is received by the scheduling module 103 in response to the request message M2 for collecting information relating to the device. In a particular embodiment, this message M5 comprises information relating to the main service associated with the device determined by the determination module 102. In another particular embodiment, this message M5 includes additional information relating to the state such as a list of identifiers of services running, a set of available resources.

The planning module 103 determines (step S3a) then one or more impacts of the management operation to be executed for the device according to the state of use of the device and the management operation to be executed and (step S3b ) a decision on the management operation to be performed based on the device utilization state, the management operation to be performed, and the impact (s) evaluated against management operation execution policies , read from the first memory zone 104 (message M6).

The scheduling module 103 then sends the management server 31 in an M8 message the decision relating to the requested management operation.

The administration server 31 executes (step S4) then the management operation for the device concerned when the decision received from the planning module 103 corresponds to an authorization. This execution can be immediate or deferred. The administration technique is again implemented when the decision corresponds to a postponement of the management operation, without indication of date.

In a particular embodiment, the scheduling module 103 also takes into account for determining the decision on the management operation to execute one or more information relating to a user of the device or its environment, read from the second memory zone 105 (message M7).

In the particular embodiment described above, the planning module

103 sends directly to the collection module 101 the M2 request message for collecting information relating to the device. In another particular embodiment, the module 103 The scheduler sends a device usage status request message to the usage state determination module 102, which then sends the device information collection request message to the collection module 101.

The device 20 administered by the administration server 31 comprises in particular in a particular embodiment, as represented in FIG. 4:

a processor 200 for executing code instructions of software modules;

a memory zone 202, arranged to store an application that includes code instructions for implementing the method of administration, as described above;

a storage memory 204, arranged to store data used during the implementation of the method of administration, as described previously:

a communication interface 206, arranged to send and receive data;

a module 208, arranged to collect information relating to the device making it possible to determine information on the state of use of the device

an administration module 210, arranged to be administered remotely by an administration server, in particular for exchanging administration data with this server.

It is emphasized here that the device 20 also comprises other processing modules, not shown in Figure 4, arranged to implement the various functions of this device.

The administration module 210 implements, for example, the administration functions defined in the technical report TR-069.

An administration device 40 is described with reference to FIG. 5 in a particular embodiment. The administration device 40 comprises in particular:

a processor 400 for executing code instructions of software modules;

a storage memory 402, arranged to store data used during the implementation of the method of administration, as described previously:

a memory zone 404, arranged to store an application that includes code instructions for implementing steps of the method of administration, as described above;

a communication interface 406 with the extended communication network, arranged to transmit and receive data.

In a particular embodiment, the device 20 comprises the collection module 101 (which may correspond to the module 208), the usage state determination module 102, the planning module 103 and the first memory area 104 It includes, where appropriate, the second memory area 105.

In a particular embodiment, the device 20 comprises the collection module

101 (which may correspond to module 208) and the module for determining a state of use 102. The administration device 40, or any other device mandated for this purpose, then comprises a module for obtaining the state of use cooperating with the module for determining a usage state, the planning module 103 and the first memory area 104. It comprises, where appropriate, the second memory area 105 .

In a particular embodiment, the device 20 comprises the module 208, arranged to collect information relating to the device making it possible to determine information on the state of use of the device, and the administration device 40, or any other mandated device. for this purpose, comprises the collection module 101, the usage state determination module 102, the planning module 103 and the first memory area 104. It comprises, if appropriate, the second memory area 105.

The device to be administered and, where appropriate, the administration device thus form a system arranged to cooperate with the remote administration server. This system comprises: at least one device to be administered, comprising:

an administration module 210, arranged to be administered remotely by an administration server 31:

a module 208, arranged to collect information relating to the device making it possible to determine information on the state of use of the device;

this system further comprising:

a determination module 102 of a usage state, arranged to determine usage state information of the device for which a management operation is to be executed;

a planning module 103, arranged to determine a postponement of the execution of the management operation according to the information obtained, of an evaluation of an impact of the execution of the management operation on the operation of the device and a management operation execution policy and to request the transfer to the administration server.

In a particular embodiment, the system also comprises a collection module 101, arranged to obtain information relating to the device for determining device usage status information.

The administration technique is implemented by means of software and / or hardware components. In this context, the term "module" may correspond in this document to both a software component, a hardware component or a set of hardware and / or software components, capable of implementing a function or a set of functions, as described above for the module concerned.

A software component corresponds to one or more computer programs, one or more subroutines of a program, or more generally to any element of a program or software. Such a software component is stored in memory and then loaded and executed by a data processor of a physical entity and is capable of accessing hardware resources of this physical entity (memories, recording media, communication bus, input / output electronic boards, user interfaces, etc.).

In the same way, a material component corresponds to any element of a material set (or hardware). It may be a programmable hardware component or not, with or without an integrated processor for running software. This is for example an integrated circuit, a smart card, an electronic card for executing a firmware, etc.

In a particular embodiment, the modules 101, 102, 103 are arranged to implement the previously described method of administration. These are preferably software modules comprising software instructions for executing portions of code for the implementation of the previously described method of administration, during the execution of said program by the processor of a device. The invention therefore also relates to:

a program for a device, comprising program code instructions intended to control the execution of those of the steps of the previously described administration method implemented by the device, when said program is executed by this device;

- A recording medium readable by a device on which is recorded the program for a device.

The software modules can be stored in or transmitted by a data carrier. This may be a hardware storage medium, for example a CD-ROM, a magnetic diskette or a hard disk, or a transmission medium such as an electrical signal, optical or radio, or a telecommunications network.

It goes without saying that the embodiments which have been described above have been given for purely indicative and non-limiting reasons, and that many modifications can easily be made by those skilled in the art without departing from the scope of the present invention. 'invention.

Claims

A method of remote administration of a device (20, 27) by an administration server (31), said method comprising:

obtaining (S2) a usage status information of the device for which a management operation is to be executed;

- evaluation (S3a) of an impact of the execution of the management operation for a quality of service for a service provided by the device according to the information obtained and the management operation to be performed:

determination (S3b) of a postponement of the execution of the management operation according to the information obtained, of said impact and of a management operation execution policy, defining an association between a state of management, use of a device, an operation and an impact;

- Request to postpone the execution of the management operation to the administration server.

2. Administration method according to claim 1, wherein the request to postpone the execution of the management operation comprises time information allowing the administration server to orchestrate the execution of the management operation.

3. Administration method according to claim 1, wherein the postponement of the execution of the management operation is also determined according to a context associated with a user of the device.

4. The method of administration of claim 1, wherein the device usage status information is determined from information collected (SI) from the device.

The method of administration of claim 4, wherein the collected information belongs to the group comprising information about a process running on the device, information about the resources available on the device.

The method of administration according to claim 1, wherein the impact is evaluated (S3) according to a class of the management operation.

7. Administration device arranged to cooperate with an administration server (31) remote from a device (20, 27), the administration device comprising:

- a obtaining module (102), arranged to obtain a state of use of the device for which a management operation is to be performed; a planning module (103), arranged to evaluate an impact of the execution of the management operation for a quality of service for a service provided by the device according to the information obtained and the management operation to execute, to determine a postponement of execution of the management operation based on the information obtained, an evaluation of said impact and a management operation execution policy defining an association between a state use of a device, an operation and an impact and to request the transfer to the administration server.

8. The administering device according to claim 7, wherein the obtaining module is further arranged to determine the status of use of the device from information collected from the device.

9. System arranged to cooperate with a remote administration server (31), said system comprising:

at least one device to be administered (20, 27) comprising:

an administration module (210), arranged to be administered remotely by an administration server (31):

a module (208) arranged to collect information relating to the device making it possible to determine information on the state of use of the device;

said system further comprising:

a determination module (102) for a usage state, arranged to determine usage state information of the device for which a management operation is to be executed;

a planning module (103), arranged to evaluate an impact of the execution of the management operation for a quality of service for a service provided by the device according to the information obtained and the management operation to execute, to determine a postponement of execution of the management operation based on the information obtained, of said impact and of a management operation execution policy defining an association between a state of use of a device, an operation and an impact and to request the transfer to the administration server.

The system of claim 9, further comprising a collection module (101), arranged to obtain device information for determining device usage status information.

11. Program for a device, comprising program code instructions for controlling the execution of those of the steps of the method of administration according to one of the Claims 1 to 6 implemented by the device, when said program is executed by said device.

12. Recording medium readable by a device on which the program according to claim 11 is recorded.