Method for sharing personal data with a service, method for configuring a service, service provider device, and user terminal

Abstract

The invention relates to a method for sharing personal data with a service, to a program implementing same, to a service provider device and to a user terminal. One subject of the invention is a method for sharing personal data with a service, the sharing method comprising: - selecting personal data of one type from among the set of personal data of a user of a service depending on a functionality selected by the user of the service, the selected personal data being able to constitute the personal data shared with the service. The sharing method thus enables graduated sharing of personal data linked to a provided graduated service level.

Description

Method of sharing personal data with a service, method of configuring a service, service provider device and user terminal

[0001] The invention relates to a method of sharing personal data with a service, a method of configuring a service, a service provider device and a user terminal. State of the art

[0002] Personal data is used by service providers, in particular to personalize the service provided, to generate revenue to finance improvements to the service provided…

[0003] In order to protect users of these services, and more specifically to protect their personal data, various laws and regulations have been adopted. In particular, the GDPR, or General Data Protection Regulation of May 25, 2018, requires service providers to obtain user consent for the use of their personal data. This consent is defined by the GDPR as "any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her." Therefore, this consent has four cumulative criteria: 1. Freely given: consent must not be coerced or influenced. The individual must be offered a genuine choice without suffering any negative consequences for refusing. 2.Specific: consent must correspond to a single processing activity for a specific purpose. 3. Informed: for it to be valid, consent must be accompanied by certain information provided to the individual before they consent. 4. Unambiguous: consent must be given by a statement or other clear affirmative action. No ambiguity regarding the expression of consent can remain.

[0004] The GDPR mandates that data subjects be provided with concise, transparent, understandable, and easily accessible information. This obligation of transparency is defined as enabling data subjects to: - know the reason for the collection of their data; - understand how their data will be processed; - maintain control over their data by facilitating the exercise of their rights.

[0005] Today, service delivery technology only allows users to authorize or deny the sharing of certain personal data. Depending on the personal data the user consents to share, the service provider delivers a specific level of service. For example, a service provider that earns revenue by selling personal data, particularly to advertising providers, offers an abbreviated service (such as a preview of a news article) to users who do not consent to sharing their personal data, while providing a full service to users who do consent.

[0006] The drawback of current techniques for providing services associated with sharing personal data is that the user is unaware of the level of service provided in relation to the personal data they intend to share. Another drawback is that the service provider only offers two levels of service: abridged service vs. full service, and general service vs. fully personalized service.

[0007] One of the aims of the present invention is to remedy some drawbacks of the prior art.

[0008] An object of the invention is a method of sharing personal data with a service, the sharing method comprising: - selecting personal data of a type from the set of personal data of a user of a service according to a functionality selected by the user of the service, the selected personal data being suitable to constitute the personal data shared with the service.

[0009] Thus, the sharing process allows for a graduated sharing of personal data linked to a graduated level of service provided. The level of consent for data sharing is therefore graduated, allowing the user to clearly consent to a level of personal data sharing based on the type and level of service sought.

[0010] Advantageously, the sharing process involves: - validating the selected personal data as personal data shared with the service.

[0011] Advantageously, the sharing process involves: - reproducing information associating the type of personal data selected and the service functionality selected.

[0012] Advantageously, the reproduction is carried out prior to the validation of the selected personal data.

[0013] An object of the invention is also a method of configuring a service provided to a user, the configuration method comprising: - selecting a feature from among all the features of a service, the selection of the feature triggering a selection of personal data of a type from among all the personal data of a user of a service according to a selected feature.

[0014] Advantageously, the configuration process includes: - adding the selected functionality upon validation by the user of the personal data selected as personal data shared with the service.

[0015] Advantageously, the configuration process includes: - removing the selected functionality upon validation of the deletion of the selected personal data from the personal data shared with the service.

[0016] Advantageously, the configuration process includes: - reproducing information associating, for the service, the selected functionality and the type of personal data shared for that functionality.

[0017] Advantageously, the reproduction is carried out prior to the validation of the selected personal data.

[0018] Advantageously, according to one implementation of the invention, the various steps of the process according to the invention are implemented by a software or computer program, this software comprising software instructions intended to be executed by a data processor of a device forming part of a service delivery device and / or a user terminal and being designed to control the execution of the various steps of this process.

[0019] The invention therefore also relates to a program comprising program code instructions for the execution of the steps of the personal data sharing process and / or the service configuration process when said program is executed by a processor.

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

[0021] An object of the invention is also a service provider device capable of providing at least one service to a user comprising: - a service configuration device capable of selecting a feature from among all the features of a service, the selection of the feature triggering a selection of personal data of a type from among all the personal data of a user of a service according to a selected feature, the service provider device being capable of providing the service according to the selected feature.

[0022] Advantageously, the service provider device includes: - a processing device capable of executing one or more functionalities of a service depending on the service configuration for a given user.

[0023] Advantageously, the service provider device includes: - a device for accessing a service executed by a processing device capable of executing one or more functionalities of a service depending on the configuration of the service for a given user.

[0024] Advantageously, the service provider device includes: - a receiver of a selection instruction from a user interface to the service configuration device.

[0025] An object of the invention is also a user terminal comprising: - a user interface capable of selecting a feature from among the features of a service provided by a service provider device to the user terminal, the selection of the feature triggering a selection of personal data of a type from among the personal data of a user of a service according to a selected feature, the service provider device being capable of providing the service according to the selected feature.

[0026] Advantageously, the user terminal includes at least one of the following devices: - the service provider device; - a communication interface with a remote device including the service provider device.

[0027] The features and advantages of the invention will become clearer upon reading the description, given by way of example, and the related figures which represent:

[0028] , a simplified diagram of a method for sharing personal data with a service according to the invention,

[0029] , a simplified diagram of how personal data sharing works according to the invention,

[0030] , a simplified diagram of a method for configuring a service provided to a user according to the invention,

[0031] , a simplified diagram of a user interface for a user terminal during the first stage of a particular service,

[0032] , a simplified diagram of a user interface for a user terminal during a second step allowing the selection of a desired level and / or type of service for the particular service,

[0033] , a simplified diagram of a user interface of a user terminal during a third step in the initial selection of certain personal data for the level and / or type of service of the particular service,

[0034] , a simplified diagram of a user interface of a user terminal during a third step in a second selection of certain personal data for the level and / or type of service of the particular service,

[0035] , a simplified diagram of a method for configuring a service when the user authorizes the sharing of some of the personal data necessary for the implementation of the service level chosen according to the invention,

[0036] , a simplified diagram of a service delivery device according to the invention,

[0037] , a simplified diagram of a user terminal according to the invention.

[0038] Laillustre a simplified diagram of a process for sharing personal data with a service according to the invention.

[0039] The process of sharing personal data with a DPSH service involves: - selecting DP_SLCT personal data of a type ni , among the set of personal data {dp} of a user U of a service sv according to a selected function fct i : sv_fct i selected personal data by the service user being able to constitute the personal data shared with the service.

[0040] In particular, the DPSH sharing process includes: - validating the selected personal data (VLD) as personal data shared with the SV service.

[0041] In particular, the sharing process includes: - reproducing ASS_RPR information associating the type of personal data selected and the service functionality selected: .

[0042] In particular, RPR reproduction is performed prior to VLD validation of the selected personal data. .

[0043] In a particular embodiment, a configuration method for an SV_CNF service informs the DPSH personal data sharing process of a selected function. i in particular by the user U of the sv service: sv_fct i .

[0044] In particular, the DPSH personal data sharing process includes: - determining TY_DT the type(s) of personal data (dp) used by the service sv.

[0045] The determination of the types of personal data TY_DT is carried out in particular according to personal data dp of the user U which can be consulted, for example, in a personal data storage device, such as a personal database BDDP.

[0046] In particular, the DPSH personal data sharing process includes: - providing LST_PV to the DP_SLCT personal data selection, the list of personal data types of personal data (dp) used by the service sv.

[0047] In particular, the provision of the list of personal data types LST_PV uses the personal data types provided by the determination of personal data types TY_DT used by the sv service.

[0048] In particular, providing a list of personal data types LST_PV provides the personal data types of personal data dp used by the service sv to the selection of personal data DP_SLCT.

[0049] In particular, the selection of personal data DP_SLCT includes: - selecting TY_SLCT, a type ty ni , from a list of types of personal data of personal data (dp) used by the service (sv) depending on a selected function (fct) i : sv_fct i by the user of the service.

[0050] In particular, the selection of personal data DP_SLCT includes: - reproducing RPR the selected type(s) ty ni , in particular provided by the TY_SLCT type selection.

[0051] Optionally, the RPR reproduction reproduces information associating the selected type(s) ty ni , to the selected function fct i , sv_fct i from the customer service department: .

[0052] In particular, the selection of personal data DP_SLCT involves: - selecting personal data in relation to an SLCT / SV service of a type ni , among the set of personal data {dp} of a user U of the sv service.

[0053] Specifically, the type(s) ty ni , of selected personal data is / are the type(s) provided by providing a list of personal data types LST_PV.

[0054] In particular, the selection relating to an SLCT / SV service receives personal data of a type ni , among all personal data of a user U of the sv service, in particular of a personal data storage device BDDP.

[0055] Specifically, the selection relating to an SLCT / SV service receives personal data in response to a personal data request dp_rq(ty ni ) function of the selected type(s) ty ni , .

[0056] In one particular embodiment, personal data provided by the selection relating to an SLCT / SV service are suitable for constituting the shared personal data dpp.

[0057] In particular, the selection of personal data DP_SLCT involves: - selecting personal data by an SLCT / U user among the personal data of selected type(s) ty ni , corresponding to a selected function of an sv_fct service i .

[0058] Specifically, the selection by an SLCT / U user involves: - selecting a type , among the selected types ty ni , corresponding to a selected function of an sv_fct service isuch as those provided by the TY_SLCT type selection.

[0059] Specifically, the type(s) , of personal data selected by the user U correspond to an action of the user U, in particular by means of a user interface on one or more type(s) ty ni , corresponding to a selected function of an sv_fct service i such as those provided by the provision of a list of personal data types LST_PV possibly reproduced RPR(s).

[0060] In particular, the selection by a user SLCT / U receives personal data of a type , among the set of personal data {dp} of a user U of the sv service, in particular of a personal data storage device BDDP.

[0061] Specifically, the selection by a user SLCT / U receives personal data in response to a request for personal data depending on the selected type(s) , by user U.

[0062] In one particular embodiment, personal data provided by the SLCT / U user selection are suitable for constituting the shared personal data dpp.

[0063] In particular, following VLD validation, notably triggered by the user U's "ack" of the selected personal data The DPSH personal data sharing process provides the selected personal data as shared personal data (dpp). : .

[0064] An embodiment of the personal data sharing process is a program comprising program code instructions for executing the steps of the personal data sharing process when said program is executed by a processor.

[0065] Laillustrates a simplified diagram of how personal data sharing works according to the invention.

[0066] In this example, a service configuration process SV_CNF indicates to a personal data sharing process DPSH which service sv the sharing process is implemented for. The service configuration process SV_CNF can be requested both when accessing the service and / or during service use. Thus, DPSH personal data sharing can be implemented at any time during the implementation of the service sv. This allows the user U to modify their personal data sharing at any time while using the service.

[0067] In particular, the sharing of personal data DPSH involves: - determining the list of personal data {dp(sv)} that can be used by the sv service. Specifically, determining the list of personal data {dp(sv)} that can be used by the sv service involves determining the TY_DT type of personal data {ty n (sv)} n usable by the sv service.

[0068] In particular, the sharing of personal data DPSH involves: - selecting SLCT / U a type of personal data by the user U from the set of types {ty n (sv)} n of personal data usable by the sv service.

[0069] Specifically, the personal data shared by user U is the user U's personal data of the selected type(s). .

[0070] In particular, the sharing of personal data DPSH involves: - determining ASS_DT the correspondence between the shared personal data dpp and the functionalities {fct j} j of the service rendered sv*.

[0071] Specifically, the sharing of personal data DPSH includes: - reproducing ASS_RPR the correspondence between the shared personal data dpp and the functionalities {fct j} j of the service rendered sv*, possibly provided by the determination of the ASS_DT correspondence.

[0072] In particular, the sharing of personal data DPSH includes: - validating VLD the selected types of personal data .

[0073] Specifically, user U performs VLD validation following the reproduction of the ASS_RPR correspondence.

[0074] Optionally, if user U does not validate the SLCT / U selection made by user U, also called user choice: a = [N], then the personal data sharing process includes a new SLCT / U selection.

[0075] Optionally, if user U validates the SLCT / U selection made by user U, also called user choice: a = [Y], then the personal data sharing process includes a SYNT synthesis of the shared personal data dpp and the associated service rendered sv*.

[0076] Optionally, if user U validates the SLCT / U selection made by user U, also called user choice: a = [Y], then the personal data sharing process provides the shared personal data dpp and the required service sv* associated with an execution of service SV_X.

[0077] Specifically, the SYNT synthesis provides the SV_X service execution with the shared personal data dpp and the associated required service sv*: (dpp, sv*).

[0078] This method of obtaining user consent for sharing personal data is innovative on two levels: - firstly, the user can explicitly identify which data the assistant is likely to use to fulfill its role; - secondly, the user can see in real time the impact of this personal data sharing on the effectiveness of the service offered by the assistant. Thus, the more data the user agrees to share, the more effective the service will be.

[0079] In this way, the user has control over what they agree to share, while understanding the impact of the level of sharing on the level of service provided, all in a completely transparent manner. This approach moves away from an "all or nothing" consent model.

[0080] Laillustre a simplified diagram of a method for configuring a service provided to a user according to the invention.

[0081] The SV_CNF configuration process for an SV service provided to a user U is a configuration process that includes: - selecting FCT_SLCT, a function fct i among the set of features {fct k} k of a service sv, the selection of the FCT_SLCT functionality triggers a selection of personal data DP_SLCT of a type ty ni , among all personal data of a user U of a service sv depending on a selected function fct i .

[0082] In particular, the SV_CNF configuration process includes: - adding the selected functionality (fct) to FCT_ADD i upon validation of the selected personal data by user U via VLD such as personal data shared with the service sv.

[0083] In particular, the SV_CNF configuration process includes: - deleting the selected functionality FCT_RMV i upon validation of the selected personal data by user U via VLD such as personal data shared with the service sv.

[0084] In particular, the SV_CNF configuration process includes: - reproducing ASS_RPR information associating, for the sv service, the selected functionality fct i and the type ty ni personal data is shared for this feature.

[0085] In particular, especially following a request for access (not illustrated) to a given service sv, the SV_CNF configuration process is implemented for the given service sv.

[0086] In particular, the SV_CNF configuration process includes: - determining FCT_DT the set of functionalities of the sv service.

[0087] In particular, the determination of FCT_DT functionalities is implemented based on functionalities of the sv service that can be consulted, for example, in a service storage device, such as a BDS service database.

[0088] In particular, the FCT_DT feature determination receives the set of features {fct k} k of the service, specifically the BDS service storage device. In particular, the determination of FCT_DT functionalities receives all the functionalities {fct k} k of the sv service in response to a request for sv service features: fct_rq(sv).

[0089] In particular, the SV_CNF configuration process includes: - reproducing FCT_RPR information containing the functionalities {fct k} kavailable for the service. Available features {fct k} k for the sv service include the functionalities provided by the determination of FCT_DT functionalities for the sv service.

[0090] In particular, the FCT_SLCT selection is performed among the features {fct k} k of the service sv provided by determining the FCT_DT functionalities. In particular, the FCT_SLCT selection is performed based on an action a of the user U. The action a of the user U indicates, for example, a functionality of the service fct i , sv_fct i :a(fct i The action of user U is performed in particular following an FCT_RPR reproduction of the set of functionalities {fct k} k of the sv service.

[0091] In a particular embodiment, the SV_CNF configuration process includes: - sharing DPSH personal data according to the functionality fct i of selected sv service. In this particular embodiment, the sharing of personal data is specifically said to be internal to the SV_CNF configuration process because it is implemented by it.

[0092] In an alternative embodiment, the SV_CNF configuration process includes: - exchanging with a DPSH personal data sharing process.

[0093] In this particular embodiment, the sharing of personal data is said to be external to the SV_CNF configuration process because it is implemented outside of it.

[0094] In particular, DPSH personal data sharing is a sharing process as illustrated by 1a and / or 1b.

[0095] In particular, the SV_CNF configuration process provides the selected functionality to the DPSH personal data sharing (internal or external to the configuration process). i , sv_fct i .

[0096] In particular, the DPSH personal data sharing process provides the SV_CNF configuration process with shared personal data (dpp) based on the selected service functionality. Specifically, the personal data (dpp) shared by the DPSH sharing process with the SV_CNF configuration process is personal data of a type associated with the selected service functionality: {dp i} i , or even selected by user U from personal data of a type associated with the selected service functionality: {dp j} j .

[0097] In particular, the SV_CNF configuration process involves: - modifying the SV_MDF service according to the selected functionality. i .

[0098] In particular, the SV_MDF service modification involves: - performing an operation on a selected function i depending on an action a of the user U. In particular, the operation on the selected functionality fcti is at least one of the following operations: - add the selected functionality ADD; - delete the selected functionality RMV.

[0099] In particular, the SV_MDF service modification includes: - checking the action a of the user U, the checking of the action a triggering an ADD, RMV operation depending on the action a.

[0100] Specifically, if action `a` is an add action: `a=ADD`, then the SV_MDF service modification implements an ADD operation of the selected functionality `fct`. ito the sv service: sv* = sv + fct i Specifically, if action 'a' is a delete action: 'a=SUPR', then the SV_MDF service modification implements an RMV delete operation of the selected feature 'fct'. i to the sv service: sv* = sv - fct i .

[0101] In particular, the sv* service resulting from the modification of the SV_MDF service based on the action a of the user U is then provided to an execution of the SV_X service.

[0102] An embodiment of the SV_CNF service configuration process is a program comprising program code instructions for executing the steps of the SV_CNF service configuration process when said program is executed by a processor.

[0103] The invention proposes to grade the level of consent for data sharing and to clearly display the link between this level of sharing of personal data and the type and level of service made possible.

[0104] While using the service, users will be able to measure in real time the impact of the level of personal data sharing on the effectiveness of the service offered. They will retain control over what they agree to share, and will be able to adjust the level of consent with complete transparency regarding the link between the level of personal data sharing and the type and level of service provided.

[0105] During the 1 ereWhen using the service in which the solution is integrated, the user will select the personal information they agree to share in order to obtain the desired service. The service will then configure itself in real time based on this sharing, offering features that vary in complexity and personalization.

[0106] The user can also adjust this level of personal data sharing at any time by choosing to decrease or increase it. They will then see in real time the effect of these changes on the level and type of service available.

[0107] Information regarding this correlation between the shared data and the level or manner in which the service will be provided is presented clearly and explicitly to the user. This can be done globally (sharing 10% of one's personal data grants access to 20% of the service's features, sharing 40% of one's data grants access to 75% of the service's features) or in a more targeted way (sharing personal data D grants access to feature F).

[0108] Figures 3a to 3d show reproductions made on a user interface of a user terminal during a particular case of configuration of an SV_CNF service.

[0109] The proposed invention is illustrated in a service provider, such as the "assigned home" service. This is a domestic assistant at home who supports household members in achieving an individual or collective goal.

[0110] To illustrate this service provider, user U chooses to develop a "digital home" service in which a home assistant will support household members in achieving more responsible digital practices. This support could be extended to various other services corresponding to missions such as ecology, health, or budgeting, for example… it is up to the user to choose the area in which they wish to change their behavior and receive support to reach their chosen goal.

[0111] The assigned home assistant will use various incentive-based "solicitation devices" (also called "nudges") to support users in achieving their self-defined goals. A "nudge" is a tool used to influence individuals to take action, to modify their behavior, for their own benefit or that of the community. To be considered a "nudge," the action suggested by the assistant must not be coercive for the user; they must be able to easily avoid it.

[0112] The proposed invention intervenes in the service configuration phase. During this configuration phase, the user will be able to define the task assigned to the home assistant and configure the conditions for its execution.

[0113] This parameterization is broken down into 3 steps which we describe below in association with figures 3a to 3d.

[0114] Laillustre un schema simplifiée dune interface de un terminal utilisateur pendant un premier scène de un service particulier.

[0115] In the first step, the user is asked a question about the service they wish to implement, specifically: What mission does the user want to give to the home assistant? How do they want to be helped by the home assistant? This objective can be defined for themselves alone or with other members of the household.

[0116] Lamontre a 221 screen reproducing a 211 user interface PV including all sv1, sv2, sv3, sv4, sv5, sv6 services that are suitable for provision.

[0117] In particular, the services offered in the example of the "commissioned home" service provider are as follows: - sv1: an "energy-efficient home" service;

[0118] - sv2: a "healthy home" service;

[0119] - sv3: a "media library house" service;

[0120] - sv4: a "curious house" service;

[0121] - sv5: an "eco-friendly home" service;

[0122] - sv6: a "digital home" service; - etc.

[0123] In particular, the 211 service delivery user interface PV feature selectable hexagonal buttons. Each of the hexagonal buttons in the 211 service delivery user interface PV is associated with the configuration of a service offered sv1…sv6.

[0124] In the example illustrated by the, user U selects the sv6 digital home service.

[0125] Laillustre a simplified diagram of a user interface of a user terminal during a second step allowing a selection of a desired level and / or type of service of the particular service.

[0126] In a second step, the user is asked a question about the features of the chosen service that they wish to implement, in particular: What uses does the user wish to act on to achieve the set objective?

[0127] To do this, the assistant will be able to offer the user the option to select, from among the uses that could have an impact on the objective, those on which they think / want to be able to modify their behavior.

[0128] Following the selection of the sv6 digital home service, the watch displays a 221 screen reproducing a 211 user interface SV_CNF including all the functionalities {fct 6n} n=1…12 of the sv6aptes service to be implemented by the chosen service.

[0129] In particular, the features offered in the example of the sv6 service of "digital home" are as follows: - fct61: a "lighten your email" feature;

[0130] - fct62: a feature "prioritize wifi over mobile network, especially 4G or 5G, at home";

[0131] - fct63: a "remove duplicates in stored content" feature;

[0132] - fct64: a feature "limit music playback in video mode";

[0133] - fct65: a "moderate screen time" feature;

[0134] - fct66: a "prefer downloading to streaming" feature;

[0135] - fct67: a feature to "prioritize local storage over online storage";

[0136] - fct68: a "switch screens to dark mode" feature;

[0137] - fct69: a "disable automatic synchronizations" feature;

[0138] - fct6 10 : a "delete browsing history" feature;

[0139] - fct6 11: a "turn off unused equipment" feature;

[0140] - fct6 12 : a feature that "closes unused mobile applications";

[0141] - etc.

[0142] In particular, the user interface for configuring a 211 service SV_CNF feature selectable hexagonal buttons. Each of the hexagonal buttons in the user interface for configuring a service 211 SV_CNF is associated with a feature of the selected service fct 61 …function 612 .

[0143] At this stage, user U can select one or more features, in this case the first, fourth, sixth and seventh features (illustrated by the validation symbol « » in the selected hexagonal button).

[0144] In particular, the user interface for configuring a 211 service SV_CNFThese buttons may include at least one other button that can be selected after at least one of the selectable hexagonal buttons has been selected. A button that can be selected afterward is, in particular: - a VLD validation button. The validation button can trigger the next step using either the features selected afterward or the features of the currently selected service plus the features selected during the second configuration step of the selected service; - an RMV removal button. The validation button can trigger the next step using the features of the currently selected service minus the features selected during the second configuration step of the selected service; - a BCK return button. The return button can trigger a return to the previous service selection step.

[0145] Thus, once one or more features (fct61) have been selected, fct64, fct66 et fct67 par l’utilisateur U, l’utilisateur U peut :- soit valider sa sélection en cliquant sur le bouton de validation vld, ce qui permet d’ajouter les fonctionnalités sélectionnées au service choisi,- soit retirer les fonctionnalités sélectionnées au service choisi en cliquant sur le bouton de retrait rmv,- soit revenir à l’interface précédente en cliquant sur le bouton de retour bck, en l’occurrence à l’interface illustrée par laà avoir une interface de fourniture de services 221PV.

[0146] Figures 3c and 3d illustrate the third step in configuring a service according to the invention.

[0147] Laillustre un schema simplifié d'un interface d'un terminal utilisateur pendant un tiers dans un étape d'un début d'une sélection de certains data personnelles pour la niveau et / ou type de service de particulier service.

[0148] Laillustre un schema simplifiée d’un interface d’un terminal utilisateur pendant un s’un scène troisième lors de un seconde sélection de certains data personnel pour la niveau et / ou type de service de particulier service.

[0149] In a third step illustrated by figures 3c and 3d, the user is asked about the type of personal data they authorize to be shared for the implementation of the selected functionalities of the chosen service they wish to implement, in particular: What data do they agree to share with the assistant so that it can support them in achieving the chosen objective?

[0150] Following the selection of functionalities 61 , fct 64 , fct 66 , fct 67 From the SV6 digital home service, figures 3c and 3d show a screen 221 reproducing a data sharing user interface 211 DPSH including in particular all the types {ty n6} n6 of personal data that can be used to implement functionalities 61 , fct 64 , fct 66 , fct 67 selected from the sv6 service.

[0151] In particular, the types of personal data usable by the selected functionalities 61 , fct 64 , fct 66 , fct 67 The following are from the sv6 service of "digital home": - ty1: usage data;

[0152] - ty2: connected equipment;

[0153] - ty3: content from messaging apps;

[0154] - ty4: geolocation of equipment;

[0155] - ty5: content (photos, videos, documents…);

[0156] - ty6: connection duration of equipment;

[0157] - etc.

[0158] In particular, the 211 data sharing user interface DPSH feature selectable hexagonal buttons. Each of the hexagonal buttons in the 211 data sharing user interface DPSH is associated with a data type ty1…ty6.

[0159] At this stage, user U can select one or more types of personal data, in this case the first, second, and sixth types of personal data in the case of the and the first, second, third, and sixth types of personal data in the case of the (illustrated by the validation symbol « » in the selected hexagonal button).

[0160] Thus, the user can specify the personal data they are willing to share with the home assistant to help it achieve the defined objective. This choice will be made from a list of data types identified by the assistant as useful for achieving the objective, namely, implementing the selected service features. The home assistant will only offer to share information that is relevant to the objective, and nothing more.

[0161] In particular, the user interface for sharing personal data 211 DPSHThey may include at least one other selectable button after at least one of the selectable hexagonal buttons has been selected. A selectable button is, in particular: - a validation button (vld). The validation button is capable of triggering the next step by sharing personal data of the types selected during the third step for the execution of the chosen service with the selected features; - a cancel button. The cancel button is capable of deselecting the types already selected; - a back button (bck). The back button is capable of triggering a return to the previous feature selection step.

[0162] Thus, once one or more features (fct61) have been selected, fct64, fct66 et fct67 par l’utilisateur U, l’utilisateur U peut :- soit valider sa sélection en cliquant sur le bouton de validation vld, ce qui permet d’ajouter les fonctionnalités sélectionnées au service choisi,- soit retirer les fonctionnalités sélectionnées au service choisi en cliquant sur le bouton de retrait rmv,- soit revenir à l’interface précédente en cliquant sur le bouton de retour bck, en l’occurrence à l’interface illustrée par laà avoir une interface de fourniture de services 221PV.

[0163] Optionally, the 211 data sharing user interface DPSHincludes an illustration of the performance of the chosen service with the selected features based on the selected data types.

[0164] In this case, the performance of the service prf(sv6, dp(ty1, ty2, ty6)) is 60%.

[0165] Thus, if user U considers this performance insufficient, they can, prior to the vld validation of the selected personal data types, select an additional personal data type, for example the third type ty3 as illustrated by the.

[0166] In the case of the, the performance of the service prf(sv6, dp(ty1, ty2, ty3, ty6)) is 80%.

[0167] As illustrated in the application example of figures 3a to 3d, the invention allows the user to improve their impact on the environmental footprint of their uses, their home.

[0168] The invention may also have uses in other CSR aspects, particularly for accessibility aspects by allowing the user to adapt a service to their disabilities or difficulties.

[0169] The invention can also be applied to all digital uses by allowing the user to better understand how to best adjust the sharing of their personal data to obtain the right level of service desired and thus simplify its use by avoiding features that they consider superfluous.

[0170] Laillustre a simplified diagram of a method for configuring a service when the user authorizes the sharing of some of the personal data necessary for the implementation of the service level chosen according to the invention.

[0171] In this example, a service configuration process SV_CNF indicates to a personal data sharing process DPSH which service sv the sharing process is implemented for. The service configuration process SV_CNF can be requested both when accessing the service and / or during service use. Thus, DPSH personal data sharing can be implemented at any time during the implementation of the service sv. This allows the user U to modify their personal data sharing at any time while using the service.

[0172] In particular, the sharing of personal data DPSH involves: - determining the list of personal data {dp(sv)} that can be used by the sv service. Specifically, determining the list of personal data {dp(sv)} that can be used by the sv service involves determining the TY_DT type of personal data {ty n (sv)} n usable by the sv service.

[0173] In particular, the sharing of personal data DPSH involves: - selecting SLCT / U a type of personal data by the user U from the set of types {ty n (sv)} n of personal data usable by the sv service.

[0174] Specifically, the personal data shared by user U is the user U's personal data of the selected type(s). .

[0175] In particular, the sharing of personal data DPSH involves: - determining ASS_DT the correspondence between the shared personal data dpp and the functionalities {fct j} j of the service rendered sv*.

[0176] Specifically, the sharing of personal data DPSH includes: - reproducing ASS_RPR the correspondence between the shared personal data dpp and the functionalities {fct j} jof the service rendered sv*, possibly provided by the determination of the ASS_DT correspondence.

[0177] In particular, the sharing of personal data DPSH includes: - validating VLD the selected types of personal data .

[0178] Specifically, user U performs VLD validation following the reproduction of the ASS_RPR correspondence.

[0179] Optionally, if user U does not validate the SLCT / U selection made by user U, also called user choice: a = [N], then the personal data sharing process includes a new SLCT / U selection.

[0180] Optionally, if user U validates the SLCT / U selection made by user U, also called user choice: a = [Y], then the personal data sharing process includes a SYNT synthesis of the shared personal data dpp and the associated service rendered sv*.

[0181] Optionally, if user U validates the SLCT / U selection made by user U, also called user choice: a = [Y], then the personal data sharing process provides the shared personal data dpp and the required service sv* associated with an execution of service SV_X.

[0182] Specifically, the SYNT synthesis provides the SV_X service execution with the shared personal data dpp and the associated required service sv*: (dpp, sv*).

[0183] In the case of a service requiring full consent, dummy data could be included if the user chooses not to provide their own. For example, the execution of service SV_X uses the personal data of the user who has consented to the sharing as shared personal data (dpp). U i} and separate data from the user's personal data to supplement the data necessary for the execution of the service {dp j≠i}=dp_gn. For example, this data, separate from the user's personal data, is default data or average data from data previously used by the service…

[0184] Laillustre a simplified diagram of a service delivery device according to the invention.

[0185] The service provider device 1, capable of providing at least one service (sv) to a user U, comprises: - a service configuration device 12 capable of selecting a functional function i among the set of features {fct k} k of a service, the selection of the feature triggers a selection of personal data of a type ty ni , among all personal data of a user U of a service sv depending on a selected function fct i , the service provider device 1 being capable of providing the sv* service according to the selected functionality.

[0186] In particular, the service provider device 1 comprises: - a processing device 14 capable of performing one or more functionalities i of an sv* service depending on the service configuration for a given user U.

[0187] In particular, the service provider device 1 includes: - a device 11 for accessing a service executed by a processing device 14 capable of executing one or more functionalities of a service depending on the configuration of the service for a given user.

[0188] The processing device 14 is either a remote device from the service provider device 1 or implemented within the service provider device 1.

[0189] In particular, the service provider device 1 includes: - a receiver 10 of a selection instruction a(fct i ) from a user interface 2, 22 to the service configuration device 12.

[0190] In particular, the service provider device 1 includes a communication interface 10 with a user terminal 2 comprising, in particular, a user interface 22 (see). The communication interface 10 includes a receiver and, in particular, a transmitter.

[0191] In particular, the communication interface 10, in particular its receiver, receives a request to access a service a(sv) from the user terminal 2n, in particular from the user interface 22.

[0192] In particular, the service provider device 1 includes a service access request device 11. In particular, the access request device 11 receives a service access request a(sv) from a user interface 2, 22, for example via a communication interface 10, such as the receiver 10.

[0193] The access device 11 is notably capable of proposing to the user interface 2, 22 a list of services that can be provided by the service provider device 1, based on services previously registered, for example, in a service database 110. Optionally, the access request device 11 consults a service database 110 implemented in the service provider device or in a remote device (in this case, via a communication network 4). Following an access request a(sv) to a given service sv, the service provider device 1 is capable of implementing the requested service sv.

[0194] In particular, the configuration device 12 includes: - a device 120 for determining all the functionalities of the sv service.

[0195] In particular, the functionality determination device 120 is capable of determining the functionalities of a service sv to which the access device 11 requests access based on functionalities of the service sv that can be consulted, for example, in the service storage device 110, such as a service database.

[0196] In particular, the functionality determination device 120 is capable of receiving all the functionalities {fct k} k of the service sv, in particular the service storage device 110. In particular, the functionality determination device 120 is capable of receiving all the functionalities {fct k} kof the sv service in response to a service functionality request: fct_rq(sv). Optionally, the functionality determination device 120 is capable of issuing the service functionality request: fct_rq(sv) to the service storage device 110.

[0197] In particular, configuration device 12 is capable of triggering: - reproducing information containing the functionalities {fct k} k available for the service. Available features {fct k} k For the sv service, the functionalities provided by the 120 functionality determination device for the sv service are notably those. In particular, the 120 functionality determination device is capable of controlling rpr({fct k} k ) a reproduction of information containing the functionalities {fct k} kavailable for the sv service at terminal 2, for example at user interface 22.

[0198] In particular, the service provider device 1, specifically the configuration device 12, is capable of selecting the function fct i among the features {fct k} k of the sv service provided by the functionality determination device 120. In particular, the FCT_SLCT selection is carried out according to an action a of the user U.

[0199] In particular, the service provider device 1, specifically the configuration device 12, includes: - a function selector 121 capable of selecting the function fct i among the features {fct k} kof the service sv, notably provided by the functionality determination device 120. Optionally, the functionality selector 121 is capable of performing the selection based on an action a, a(fct i ) of user U.

[0200] In particular, terminal 2, for example user interface 22, transmits the action a, a(fct i ) from user U to function selector 121, in particular via transmitter 10, for example receiver.

[0201] The action of user U indicates, for example, a function of the service fct i , sv_fct i :a(fct i The action of user U is performed in particular following a reproduction of all the functionalities {fct k} k of the sv service via user interface 22, in particular on command of the functionality determination device 120 and / or the functionality selector 121.

[0202] In a particular embodiment, the service provider device 1 and / or the configuration device 12 comprises: - a sharing device 13, 123 for personal data depending on the functionality fct i of selected service sv. In the particular embodiment in which the configuration device 12 includes the personal data sharing device 123, the personal data sharing is specifically said to be internal to the configuration because it is implemented by the latter.

[0203] In the alternative embodiment in which the personal data sharing device 13 is implemented in the service provider device 1 but not in the configuration device 12, the configuration device 12 includes: - means of exchange with the personal data sharing device 13.

[0204] In this particular embodiment, the sharing of personal data is said to be external to the configuration because it is implemented outside of it.

[0205] In this particular embodiment, the configuration device of a service 12 is capable of informing the personal data sharing device 13 of a selected function. i in particular by the user U of the sv service: sv_fct i .

[0206] In particular, the personal data sharing mechanism 13, 123 includes: - a type determination mechanism 130 capable of determining the type(s) of personal data (dp) used by the service sv.

[0207] The device for determining the types of personal data 130 is capable of carrying out the determination in particular on the basis of personal data dp of the user U which can be consulted, for example, in a personal data storage device, such as a personal database 131.

[0208] In particular, the personal data sharing mechanism 13, 123 includes: - a data type provisioning mechanism 132 capable of providing a list of personal data types of personal data used by the service sv, in particular to a personal data selector 133.

[0209] In particular, the device for providing a list of types of personal data 13, 123 is capable of using the types of personal data provided by the device for determining types of personal data 130 used by the sv service.

[0210] In particular, the LST_PV device for providing a list of personal data types is capable of providing the personal data types of personal data(s) used by the sv service, in particular to the personal data selector 133.

[0211] In particular, the personal data sharing mechanism 13, 123 includes: - a personal data selector 133 capable of selecting personal data of a type ni , among the set of personal data {dp} of a user U of a service sv according to a selected function fct i : sv_fct i selected personal data by the service user being able to constitute the personal data shared with the service.

[0212] In particular, the personal data selector 133 includes: - a first personal data type selector (not shown) capable of selecting a type ni , from a list of types of personal data of personal data (dp) used by the service (sv) depending on a selected function (fct) i : sv_fct i by the user of the service.

[0213] In particular, the personal data selector 133 is capable of ordering rpr( ) to reproduce the selected type(s) ni , in particular provided by the first type selector.

[0214] Optionally, the personal data selector 133 is capable of instructing a user terminal 2 and / or a user interface 22 to reproduce information associating the selected type(s) ty ni , to the selected function fcti , sv_fct i from the customer service department: .

[0215] In particular, the personal data selector 133 includes: - a selector for a service (not shown) of personal data of a type ni , among the set of personal data {dp} of a user U of the sv service.

[0216] Specifically, the type(s) ty ni , of selected personal data is / are the type(s) provided by the provisioning device 132 of a list of types of personal data.

[0217] In particular, the selector in relation to a service (not shown) receives personal data of a type ni , among all personal data of a user U of the sv service in particular of a personal data storage device 131.

[0218] Specifically, the selector in relation to a service (not shown) receives personal data in response to a personal data request dp_rq(ty ni ) function of the selected type(s) ty ni , .

[0219] In one particular embodiment, personal data provided by the selector in relation to a service (not illustrated) are suitable for constituting the shared personal data dpp.

[0220] In particular, the personal data selector 133 includes: - a user selector (not shown) capable of allowing a user to select personal data among the personal data of selected type(s) ty ni , corresponding to a selected function of an sv_fct service i .

[0221] Specifically, the user selector (not shown) includes: - a second type selector (not shown) capable of selecting a type , among the selected types ty ni , corresponding to a selected function of an sv_fct service i such as those provided by the first type selector.

[0222] Specifically, the type(s) , of personal data selected by the user U correspond to an action of user U, in particular by means of a user terminal 2 and / or a user interface 22 on one or more type(s) ty ni , corresponding to a selected function of an sv_fct service i such as those provided by the supply device 132 of a list of types of personal data LST_PV possibly reproduced.

[0223] In particular, the user selector is capable of receiving personal data of a type , among the set of personal data {dp} of a user U of the sv service in particular of a personal data storage device 131.

[0224] In particular, the user selector is capable of receiving personal data in response to a request for personal data depending on the selected type(s) , by user U.

[0225] In one particular embodiment, personal data provided by the user selector are suitable for constituting the shared personal data (dpp).

[0226] In particular, following receipt of an ack agreement from user U, the personal data sharing process device 13, 123 is then able to provide the selected personal data as shared personal data (dpp) : .

[0227] Specifically, the personal data sharing mechanism 13, 123 includes: - a validator 134 capable of defining the shared personal data (dpp) as consisting of the selected personal data : upon receipt of an ack agreement from user U.

[0228] Specifically, validator 134 is triggered by the ack agreement of user U.

[0229] In particular, the configuration device 12 is capable of providing the personal data sharing device 13, 123 with the selected functionality fct i , sv_fct i .

[0230] In particular, the personal data sharing device 13, 123 is capable of providing the configuration device 12 with shared personal data (dpp) depending on the selected service functionality. Specifically, the personal data shared (dpp) by the sharing device 13, 123 with the configuration device 12 is personal data of a type associated with the selected service functionality: {dp i} i , or even selected by user U from personal data of a type associated with the selected service functionality: {dp j} j .

[0231] In particular, configuration device 12 includes: - a service modifier 122 capable of modifying the service sv according to the selected functionality fct i .

[0232] In particular, service modifier 122 includes: - an operator (not shown) capable of performing an operation on a selected function fct i relative to the service sv according to an action a of the user U. In particular, the operator able to perform an operation on the selected functionality fcti is at least one operator among the following:- an adder (not illustrated) able to add the selected functionality to the service sv;- a remover (not illustrated) able to remove the selected functionality RMV from the service sv.

[0233] In particular, service modifier 122 includes: - an action checker (not shown) capable of checking the action a of user U, the action checker being capable of triggering an ADD, RMV operation depending on the action a.

[0234] Specifically, if action a is an add action: a=ADD, then service modifier 122 is capable of triggering the adder of the selected function fct i to the sv service: sv* = sv + fct i Specifically, if action `a` is a delete action: `a=DELETE`, then service modifier 122 is capable of triggering the deleter for the selected feature `fct`. i to the sv service: sv* = sv - fct i .

[0235] In particular, the service modifier 122 depending on the action a of user U is then able to provide the resulting service sv* to a processing device 14 able to perform a service.

[0236] In particular, the processing device 14 is then capable of executing the resulting sv* service provided by the configuration device 12 and / or the service modifier 122.

[0237] Laillustre a simplified diagram of a user terminal according to the invention.

[0238] User terminal 2 includes: - a user interface 22, 222 capable of selecting a function fct i among the set of features {fct k} k of a service provided by a service provider device 1, 31 to the user terminal 2, the selection of the feature triggering a selection of personal data of a type ty ni , among all personal data of a user U of a service sv depending on a selected function fct i ,the service provider device 1, 31 being capable of providing the sv* service according to the selected functionality fct i .

[0239] In particular, the user terminal 2 includes at least one of the following devices: - the service provider device 21; - a communication interface 20 with a remote device 1, 3 including the service provider device 1, 31.

[0240] The service provider device 1, 21, 31 is a service provider device as illustrated by the.

[0241] In particular, when the service provider device 1, 31 is remote from the user terminal 2, they communicate via a communication network 4, notably by means of communication interfaces 10 and 20 respectively.

[0242] In particular, user interface 2 includes: - a user input interface 222 receiving user actions a and transmitting commands and / or selections made by user action a U, such as a selected function fct i , a type selected by the user , an ack agreement…; and / or - a user output interface 221, such as a playback interface capable of receiving a playback command rpr. The playback interface 221 is in particular a screen of user terminal 2.

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

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

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

[0246] In another implementation, the invention is implemented using software and / or hardware components. In this context, the term "module" can refer to either a software component or a hardware component. A software component corresponds to one or more computer programs, one or more subroutines of a program, or more generally, any element of a program or software capable of implementing a function or set of functions as described above. A hardware component corresponds to any element of a hardware assembly capable of implementing a function or set of functions.

Claims

The process of sharing personal data with a service, the sharing process comprising: - selecting personal data of a type from among all the personal data of a user of a service according to a functionality selected by the user of the service, the selected personal data being suitable to constitute the personal data shared with the service. Sharing method according to the preceding claim, the sharing method comprising: - validating the selected personal data as personal data shared with the service. Sharing method according to the preceding claim, the sharing method comprising: - reproducing information associating the type of personal data selected and the service functionality selected. Sharing method according to one of claims 2 or 3, reproduction being carried out prior to validation of the selected personal data. A method for configuring a service provided to a user, the configuration method comprising: - selecting a feature from among all the features of a service, the selection of the feature triggering a selection of personal data of a type from among all the personal data of a user of a service according to a selected feature. Configuration method according to the preceding claim, the configuration method comprising: - adding the selected functionality upon validation by the user of the personal data selected as personal data shared with the service. Configuration method according to one of claims 5 or 6, the configuration method comprising: - deleting the selected functionality upon validation of the deletion of the selected personal data from the personal data shared with the service. Configuration method according to one of claims 6 or 7, the configuration method comprising: - reproducing information associating, for the service, the selected functionality and the type of personal data shared for this functionality. Program comprising program code instructions for executing the steps of the personal data sharing method according to any one of claims 1 to 4 and / or the service configuration method according to any one of claims 5 to 8 when said program is executed by a processor. A service provider device capable of providing at least one service to a user, comprising: - a service configuration device capable of selecting a feature from among all the features of a service, the selection of the feature triggering a selection of personal data of a type from among all the personal data of a user of a service according to a selected feature, the service provider device being capable of providing the service according to the selected feature. Service provider device according to the preceding claim, the service provider device comprising: - a processing device capable of performing one or more functionalities of a service depending on the configuration of the service for a given user. Service provider device according to the preceding claim, the service provider device comprising: - a device for accessing a service executed by a processing device capable of executing one or more functionalities of a service depending on the configuration of the service for a given user. Service provider device according to any one of claims 10 to 12 comprising: - a receiver of a selection instruction from a user interface to the service configuration device. User terminal comprising: - a user interface capable of selecting a feature from among all the features of a service provided by a service provider device to the user terminal, the selection of the feature triggering a selection of personal data of a type from among all the personal data of a user of a service according to a selected feature, the service provider device being capable of providing the service according to the selected feature. User terminal according to the preceding claim, the user terminal comprising at least one of the following devices: - the service provider device according to any one of claims 10 to 13; - a communication interface with a remote device comprising the service provider device according to any one of claims 10 to 13.

Images