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

Abstract

Method for sharing personal data with a service, method for configuring a service, service provider device, and user terminal. The invention relates to a method for sharing personal data with a service, a program implementing it, a service provider device, and a user terminal. One object of the invention is a method for sharing personal data with a service, the sharing method comprising: selecting personal data of a certain type from among all the personal data of a service user based on a functionality selected by the service user, the selected personal data being suitable for constituting the personal data shared with the service. Thus, the sharing method allows for a graduated sharing of personal data linked to a graduated level of service provided. Figure for the abstract: Figure 1a

Description

Title of the invention: Method for sharing personal data with a service, method for configuring a service, service provider device and user terminal technical field

[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 comprises four cumulative criteria: 1. Free: consent must not be coerced or influenced. The person must be offered a genuine choice without suffering negative consequences for refusing. 2. Specific: consent must correspond to a single processing operation for a specific purpose. 3. Informed: for it to be valid, consent must be accompanied by a certain amount of information communicated to the person before they consent. 4. Unambiguous: consent must be given by a declaration or other clear affirmative act. No ambiguity regarding the expression of consent may remain.

[0004] The GDPR requires that data subjects be informed in a concise, transparent, intelligible, and easily accessible manner. This obligation of transparency is defined as enabling data subjects to: - to know the reason for the collection of the different data concerning them; - to understand how their data will be processed; - to ensure control over their data by facilitating the exercise of their rights.

[0005] Today, service provision technology only allows the user to authorize or refuse the sharing of certain personal data. Depending on the personal data whose sharing the user consents to, the service provider provides a given level of service. For example, a service provider that earns revenue from the sale of personal data, particularly to advertising providers, provides an abbreviated service (e.g., a preview of a press article) for users who do not consent to the sharing of their personal data, while providing a full service for users who do consent to such sharing.

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

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

[0008] An object of the invention is a method for sharing personal data with a service, the sharing method comprising: - to select personal data of a type from the set of personal data of a user of a service based on 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 and allows the user to clearly consent to a level of personal data sharing depending on the type and level of service sought.

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

[0011] Advantageously, the sharing process comprises: - reproduce 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 for configuring a service provided to a user, the configuration method comprising: - select a feature from the set of features of a service, the selection of the feature triggering a selection of personal data of a type from the set of personal data of a user of a service according to a selected feature.

[0014] Advantageously, the configuration process comprises: - add the selected functionality as soon as the user validates the selected personal data as personal data shared with the service.

[0015] Advantageously, the configuration process comprises: - delete the selected feature upon validation of the deletion of the selected personal data of the personal data shared with the service.

[0016] Advantageously, the configuration process comprises: - reproduce 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 may 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 further 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 features personal data of a user of a service based on a selected feature, the service provider device being capable of providing the service according to the selected functionality.

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

[0023] Advantageously, the service provider device comprises: - 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 comprises: - 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 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 based on a selected feature, the service provider device being capable of providing the service according to the selected functionality.

[0026] Advantageously, the user terminal comprises at least one of the following devices: - the service provider device; - a communication interface with a remote device comprising the service provider device. Brief description of the drawings

[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] [Fig. 1a], a simplified diagram of a method for sharing personal data with a service according to the invention,

[0029] [Fig.lb], a simplified diagram of the operation of personal data sharing according to the invention,

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

[0031] [Fig.3a], a simplified diagram of a user interface of a user terminal during a first step of a particular service,

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

[0033] [Fig.3c], 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] [Fig.3d], a simplified diagram of a user interface of a user terminal during a third step during a second selection of certain personal data for the level and / or type of service of the particular service,

[0035] [Fig.4], 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] [Fig. 5], a simplified diagram of a service delivery device according to the invention,

[0037] [Fig.6], a simplified diagram of a user terminal according to the invention. Description of the implementation methods

[0038] Fig. 1a illustrates a simplified diagram of a method for sharing personal data with a service according to the invention.

[0039] The process of sharing personal data with a DPSH service includes: - select DP_SLCT of personal data {dp.} ? of a type tyni, tynj from the set of personal data {dp} of a user U of a service sv according to a functionality selected fct; : sv_fct; by the user of the service, the selected personal data {dp.} , {dp. j being suitable to constitute the personal data shared with the service.

[0040] In particular, the DPSH sharing method comprises: - validate VLD the selected personal data, {^Pj} as personal data shared with the SV service.

[0041] In particular, the sharing process comprises: - reproduce ASS_RPR information associating the type of personal data selected and the service functionality selected: {^7 **

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

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

[0044] In particular, the DPSH personal data sharing process includes: - determining TY_DT the type(s) {ty} of personal data dp used by the 1 n 'n customer service.

[0045]

[0046]

[0047]

[0048]

[0049]

[0050]

[0051]

[0052] 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. 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 | tyn ] of dp personal data used by the sv service. 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. In particular, providing a list of personal data types (LST_PV) provides the personal data types (ty) of personal data (dp) used by the sv service to the selection of personal data DP_SLCT. In particular, the selection of personal data DP_SLCT includes: - Select TY_SLCT, a type tyni, 11y . ! from a list of data types 1 nt 1 m personal {tyn} of personal data dp used by the service sv according to a functionality selected fct; : sv_fct; by the user of the service. In particular, the selection of personal data DP_SLCT includes: - reproducing RPR the selected type(s), notably provided by the selection of type TY_SLCT. Optionally, the RPR reproduction reproduces information associating the selected type(s) tyni, Ity .1 with the selected function fcf, sv_fct; of the sv service: l ni In particular, the selection of personal data DP_SLCT includes: - selecting, relative to an SLCT / SV service, personal data [dp. J of a type tyni, {fy .) from the set of personal data {dp} of a user U of the sv service.

[0053] In particular, the type(s) tyni, [U -I of selected personal data 1 J ni 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 (dp.| of a type tyni, from the set of personal data ^dpÇty^ j of a user U of the sv service in particular from a personal data storage device BDDP.

[0055] In particular, the selection relating to an SLCT / SV service receives personal data in response to a personal data request dp_rq(tyni) function of the selected type(s) tyni, { / J .} . 1 m 1 neither

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

[0057] In particular, the personal data selection DP_SLCT includes: - selection by a user SLCT / U of personal data { dp. j from among the personal data pZ / zj = {dp^ty^ j of selected type(s) tyni, {ty^.} corresponding to a selected function of a service sv_fct;.

[0058] In particular, the selection by an SLCT / U user includes: - select a type tyn- [ / J -l from the selected types tyni, \ty . IJ l ' nj m ni corresponding to a selected function of an sv_fct service; such as those provided by the TY_SLCT type selection.

[0059] In particular, the type(s) ty . [ ty .1 of personal data selected by ln"nj user U corresponds to an action a^tyn^ of user U in particular by means of a user interface on one or more type(s) tyni, { / y .} corresponding to a selected function of a service sv_fcf such as those provided by the provision of a list of personal data types LST_PV possibly reproduced RPR.

[0060] In particular, the selection by a user SLCT / U receives personal data personal data {dp} of a user U of the sv service, including a personal data storage device BDDP. . | of a type tyn.-, [ ty . I among the set of data J1 j ' ' ni

[0061]

[0062]

[0063] Specifically, the selection by a user SLCT / U receives the personal data |dp| in response to a personal data request dp_rq{tynj.} depending on the type(s) selected tynj, ,By the user U. In one particular embodiment, personal data {dp. j provided by the SLCT / U user selection are suitable for constituting the shared personal data dpp. In particular, following the VLD validation triggered by the user U of the selected personal data, i.e. The DPSH personal data sharing process provides the selected personal data as shared personal data dpp? {^Pj] : dpp= {dp.}., dpp= {dp}} .

[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] Figure 1b illustrates a simplified diagram of the operation of personal data sharing according to the invention.

[0066] In this example, a service configuration process SV_CNF indicates to a personal data sharing process DPSH the service sv for which the sharing process is implemented. 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 during service use.

[0067] In particular, the sharing of personal DPSH data includes: - determine the list of personal data {dp(sv)} usable by the sv service. In particular, the determination of the list of personal data {dp(sv)} usable by the sv service includes the determination TY_DT of the type of personal data {tyn(sv)]n usable by the sv service.

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

[0069] In particular, the personal data shared dpp by user U is the personal data dp of user U of the selected type(s)

[0070] In particular, the sharing of personal DPSH data includes: - determine ASS_DT the correspondence between the shared personal data dpp and the functionalities {fctj}j of the service provided sv*.

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

[0072] In particular, the sharing of DPSH personal data includes: - validate VLD the selected personal data types [fv .(sv) 1 .

[0073] In particular, 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 in particular 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] In particular, the SYNT synthesis provides T service execution SV_X with the shared personal data dpp and the associated required service sv*: (dpp, sv*).

[0078] This method of obtaining user consent for the sharing of their personal data is innovative on two levels: - On the one hand, the user can explicitly identify what data the assistant is likely to use to fulfill its role On the other hand, the user will be able to see in real time the impact of this sharing of personal data on the effectiveness of the service offered by the assistant. Thus, the more data they agree 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, and this by Complete transparency. This allows us to move away from an "all or nothing" consent model.

[0080] Figure 2 illustrates 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 comprising: - select FCT_SLCT a feature fct; from the set of features {fctk}k of a service sv, the selection of the feature FCT_SLCT triggering a selection of personal data DP_SLCT of a type tyni, tynj from the set of personal data [dp^ty^ ] of a user U of a service sv according to a selected feature fct;.

[0082] In particular, the SV_CNF configuration process comprises: - add FCT_ADD the selected functionality fct; upon validation VLD by the user U of the selected personal data {dp.| , as personal data shared dpp with the service sv.

[0083] In particular, the SV_CNF configuration process includes: - delete FCT_RMV the selected function fct; upon validation VLD by user U of the selected personal data { dp. | as data personal data shared with the SV service.

[0084] In particular, the SV_CNF configuration process includes: - reproduce ASS_RPR information associating, for the sv service, the selected functionality fct; and the type tyni of the personal data shared for this functionality.

[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 {fctk]k features of the sv service, specifically from the BDS service storage device. In particular, the FCT_DT feature determination receives the set of {fctk]k features of the sv service in response to a feature request for the sv service: fct_rq(sv).

[0089] In particular, the SV_CNF configuration process includes: - reproduce FCT_RPR information containing the functionalities {fctk]k available for the sv service. The available features {fctk]k for the sv service include the features provided by the FCT_DT feature determination for the sv service.

[0090] In particular, the FCT_SLCT selection is performed among the functionalities {fctk}k of the service sv provided by determining the functionalities FCT_DT. Specifically, 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; , sv_fcf :a(fcti). The action a of the user U is performed, in particular, following an FCT_RPR replication of the set of functionalities {fctk}k of the service sv.

[0091] In a particular embodiment, the SV_CNF configuration process comprises: - share DPSH personal data according to the selected service function. 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 comprises: - exchange using 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 [Fig. 1a] and / or 1b.

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

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

[0097] In particular, the SV_CNF configuration process includes: - modify SV_MDF the sv service according to the selected functionality fct;.

[0098] In particular, the SV_MDF service modification includes: - perform an operation on a selected function fct; based on an action a of the user U. Specifically, the operation on the selected feature fcti is at least one of the following: - add the selected ADD functionality; - remove the selected RMV feature.

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

[0100] In particular, if action a is an add action: a=ADD, then the modification of service SV_MDF implements an add operation ADD of the selected functionality fct; to service sv: sv* = sv + fct;. In particular, if action a is a delete action: a=SUPR, then the modification of service SV_MDF implements a delete operation RMV of the selected functionality fcf from service sv: sv* = sv - fcti.

[0101] In particular, the sv* service resulting from the modification of the SV_MDF service according to 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] During use of the service, the user will be able to measure in real time the impact of the degree 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 first use of 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 according to from this sharing, by offering features, more or less rich, more or less personalized

[0106] The user can also change 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 made possible.

[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 functionalities, sharing 40% of one's data grants access to 75% of the service's functionalities) or in a more targeted way (sharing personal data D grants access to functionality 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 members of the household in achieving an individual or collective goal.

[0110] To illustrate this service provider, user U chooses to develop the "digital home" service in which the home assistant will support household members in achieving a goal of 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 modify their behavior and receive support to achieve their chosen goal.

[0111] The assigned home assistant will use various incentive-based "solicitation devices" (also known as "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. In 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] Fig. 3a illustrates a simplified diagram of a user interface of a user terminal during a first step of a particular service.

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

[0116] Fig. 3a shows a screen 221 reproducing a user interface 211PV comprising all the svb services sv2, sv3, sv4, sv5, sv6 capable of being provided.

[0117] In particular, the services offered in the example of the "assigned house" service provider are as follows: - svi: 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 211PV service delivery user interface includes selectable hexagonal buttons. Each of the hexagonal buttons in the 211PV service delivery user interface is associated with the configuration of an offered service svi...sv6.

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

[0125] Fig. 3b illustrates a simplified diagram of a user interface of a user terminal during a second step allowing 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 functionalities of the chosen service that he wishes 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 him the option of selecting, from among the uses that may have an impact on the objective, those on which he thinks / wishes to be able to modify his behavior.

[0128] Following the selection of the sv6 digital home service in [Fig.3a], [Fig.3b] shows a screen 221 reproducing a user interface 21 1sv_cnf containing all the functionalities {fct6n]n=i...i2 of the sv6 service capable of being implemented by the chosen service.

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

[0130] - fct6 2: a feature to "prioritize Wi-Fi over mobile network, especially 4G" or 5G, at home";

[0131] - fct6 3: a "delete duplicates in stored content" feature;

[0132] - fct6 4: a "limit music listening in video mode" feature;

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

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

[0135] - fct6 7: a feature "prefer local storage rather than online storage";

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

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

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

[0139] - fct6 h: a "turn off unused equipment" function;

[0140] - fct612: a "closes unused mobile applications" feature;

[0141] - etc.

[0142] In particular, the configuration user interface of a service 21 1sv_cnf includes selectable hexagonal buttons. Each of the hexagonal buttons in the configuration user interface of a service 211sv_cnf is associated with a function of the selected service fct6i...fct6i2.

[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 configuration user interface of a service 21 1sv_cnf may include at least one other button that can be selected after at least one of the selectable hexagonal buttons has been selected. A subsequently selectable button is, in particular: - a vld validation button. The validation button is capable of triggering the next step using either the features selected later or the features of the service currently in use plus the features selected during the second step of configuring the selected service; - a rmv removal button. The validation button is capable of triggering the next step using the functionalities of the selected service currently in use minus the functionalities selected during the second step of configuring the selected service; - a back button. The back button is capable of triggering a return to the previous step of service selection.

[0145] Thus, once one or more functionalities fct6 i, fct6 4, fct6 6 and fct6 7 have been selected by user U, user U can: - either validate your selection by clicking the vld validation button, which adds the selected features to the chosen service, - either remove the selected features from the chosen service by clicking on the rmv removal button, - either return to the previous interface by clicking on the back button, in this case to the interface illustrated by [Fig.3a] to have a 221PV service provision interface.

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

[0147] Fig. 3c illustrates 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.

[0148] Fig. 3c illustrates a simplified diagram of a user interface of a user terminal during a third step during a second selection of certain personal data for the level and / or type of service of the particular service.

[0149] In a third step illustrated by figures 3c and 3d, the user is asked about the type of personal data which he authorizes to be shared for the implementation of the selected functionalities of the chosen service which he wishes to implement, in particular: What data does he agree to share with the assistant so that it can assist him in achieving the chosen objective?

[0150] Following the selection of functionalities fcLi, fct64, fct66, fct67 of the sv6 digital home service in [Fig.3b], figures 3c and 3d show a screen 221 reproducing a data sharing user interface 21 1Dpsh including in particular all types {tyn6]n6 of personal data usable for the implementation of the selected functionalities fct6i, fct64, fct66, fct67 of the sv6 service.

[0151] In particular, the types of personal data that can be used by the selected functionalities fct6i, fct^, fct66, fct67 of the sv6 service of "digital home" are as follows: - tyi: usage data;

[0152] - ty2: connected equipment;

[0153] - ty3: contents of messaging services;

[0154] - ty4: geolocation of equipment;

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

[0156] - ty6: connection duration of equipment;

[0157] - etc.

[0158] In particular, the 21 1Dpsh data sharing user interface includes selectable hexagonal buttons. Each of the hexagonal buttons in the 21 1Dpsh data sharing user interface is associated with a tyi.. .ty6 data type.

[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 [Fig.3c] and the first, second, third, and sixth types of personal data in the case of [Fig.3d] (illustrated by the validation symbol « » in the selected hexagonal button).

[0160] Thus, the user can indicate the personal data they agree 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, i.e., implementing the selected functionalities of the service. The home assistant will only offer for sharing information that can be useful for the objective, and no more.

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

[0162] Thus, once one or more functionalities fct6 i, fct6 4, fct6 6 and fct6 7 have been selected by user U, user U can: - either validate your selection by clicking the vld validation button, which adds the selected features to the chosen service, - either remove the selected features from the chosen service by clicking on the rmv removal button, - either return to the previous interface by clicking on the back button, in this case to the interface illustrated by [Fig.3a] to have a 221PV service provision interface.

[0163] Optionally, the 21 1Dpsh data sharing user interface includes an illustration of the performance of the chosen service with the features selected according to the types of data selected.

[0164] In the case of [Fig.3c], the performance of the service prf(sv6, dp(tyi, ty2, ty6)) is 60%.

[0165] Thus, if the user U considers this performance insufficient, he 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 [Fig.3d].

[0166] In the case of [Fig.3d], the performance of the service prf(sv6, dp(tyi, 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, in particular 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] Figure 4 illustrates 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 the service sv for which the sharing process is implemented. 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 during service use.

[0172] In particular, the sharing of personal DPSH data includes: - determine the list of personal data {dp(sv)} usable by the sv service. In particular, the determination of the list of personal data {dp(sv)} usable by the sv service includes the determination TY_DT of the type of personal data {tyn(sv)]n usable by the sv service.

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

[0174] In particular, the personal data shared dpp by user U is the personal data dp of user U of the selected type(s)

[0175] In particular, the sharing of personal DPSH data includes: - determine ASS_DT the correspondence between the shared personal data dpp and the functionalities {fctj}j of the service provided sv*.

[0176] In particular, the sharing of personal data by DPSH includes: - reproduce ASS_RPR the correspondence between the shared personal data dpp and the functionalities {fctj}j of the service provided sv*, possibly provided by the determination of correspondence ASS_DT.

[0177] In particular, the sharing of personal data DPSH includes: - validating VLD the selected types of personal data -15^)1 •

[0178] In particular, 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, in particular, 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] In particular, the SYNT synthesis provides the execution of service SV_X 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 decides not to provide their own. For example, the execution of service SV_X uses as shared personal data dpp the personal data of the user for whom they have consented to sharing {dpu;} and data separate from the user's personal data to supplement the data necessary for the execution of the service [dp,,}=dp_gn. For example, this data Separate from the user's personal data are default data or average data from data previously used by the service...

[0184] Figure 5 illustrates 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 to a user U comprises: - a service configuration device 12 capable of selecting a feature fch from the set of features {fctk]k of a service sv, the selection of the feature triggering a selection of personal data of a type tyni, tynj from the set of personal data [dp(tyn )} of a user U of a service sv according to a selected feature fct;, the service provider device 1 being capable of providing the service sv* according to the selected feature.

[0186] In particular, the service provider device 1 comprises: - a processing device 14 capable of executing one or more functionalities fct; of a service sv* according to the configuration of the service for a given user U.

[0187] In particular, the service provider device 1 comprises: - 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 in the service provider device 1.

[0189] In particular, the service provider device 1 comprises: - a receiver 10 of a selection instruction a(fct;) 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 [Fig. 5]). 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 comprises: - a device 120 for determining all the functionalities of the service sv.

[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 feature determination device 120 is capable of receiving all the features {fctk]k of the service sv, specifically from the service storage device 110. In particular, the feature determination device 120 is capable of receiving all the features {fctk]k of the service sv in response to a feature request from the service sv: fct_rq(sv). Optionally, the feature determination device 120 is capable of issuing the feature request from the service sv: fct_rq(sv) to the service storage device 110.

[0197] In particular, the configuration device 12 is capable of triggering: - reproducing information containing the functionalities {fctk]k available for the sv service. The available functionalities {fctk]k for the sv service include the functionalities provided by the functional determination device 120 for the sv service. In particular, the functional determination device 120 is capable of commanding rpr({fctk]k) a reproduction of information containing the functionalities {fctk]k available for the sv service at terminal 2, for example at user interface 22.

[0198] In particular, the service provider device 1, in particular the configuration device 12, is capable of selecting the functionality fct; from among the functionalities {fctk}k of the service sv 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, comprises: - a feature selector 121 capable of selecting the feature Here, among the features {fctk}k of the service sv, notably provided by the feature determination device 120. Optionally, the feature selector 121 is capable of performing the selection according to an action a, a(fct;) of the user U.

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

[0201] The action a of user U indicates, for example, a functionality of the service fcti, sv_fcti :a(fcti). The action a of user U is performed in particular following a reproduction of the set of functionalities {fctk]k of the service sv by the 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 device for sharing 13, 123 personal data depending on the selected service function. In the particular embodiment in which the configuration device 12 includes the personal data sharing device 123, the personal data sharing is 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 for exchanging data with the personal data sharing device 13.

[0204] In this particular embodiment, the personal data sharing 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 fct; : in particular by the user U of the service sv : sv_fct;.

[0206] In particular, the personal data sharing device 13, 123 includes: - a type determination device 130 capable of determining the type(s) l ty ) 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:

[0209]

[0210]

[0211]

[0212] - a data type provisioning device 132 capable of providing a list of personal data types {tyn j of personal data dp used by the service sv, in particular to a personal data selector 133. 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. In particular, the LST_PV personal data type provisioning device is capable of providing the personal data types {tyn j of personal data dp used by the sv service, in particular to the personal data selector 133. In particular, the personal data sharing mechanism 13, 123 includes: - a personal data selector 133 capable of selecting personal data of a type tyni, tynj from among all the data JJ personal {dp} of a user U of a service sv according to a feature selected fcf: sv_fct; by the user of the service, the selected personal data 1« / ^ j , being suitable to constitute the personal data shared with the service. In particular, the personal data selector 133 includes: - a first personal data type selector (not shown) capable of selecting a type tyni, \ty .] from a list of personal data types { / y} of personal data dp used by the service sv according to an i - njn functionality selected fct; : sv_fct; by the user of the service.

[0213] In particular, the personal data selector 133 is capable of commanding rpr({ / .V •) ) to reproduce the selected type(s) tyni, I ty .} notably 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) tyni, {ty .} with the selected function fch, sv_fcti of the service sv: pj .1 ** SV_fct..

[0215] In particular, the personal data selector 133 includes: - a selector relative to a service (not illustrated) of personal data [dp. J of a type tyni, {tyni} from the set of personal data {dp} of a user U of the service sv.

[0216]

[0217]

[0218]

[0219]

[0220]

[0221]

[0222]

[0223] Specifically, the type(s) of selected personal data 1 J ni is / are the type(s) provided by the provisioning device 132 of a list of types of personal data. In particular, the selector relative to a service (not illustrated) receives personal data { dp. | of a type tyni, {ty^.} from the set of personal data ^dpÇty^ j of a user U of the service sv in particular from a personal data storage device 131. Specifically, the selector for a service (not shown) receives the personal data {dp. | in response to a personal data query dp_rq(tyni) based on the selected type(s) tyni, {ty . 1 . 1 m 1 neither In a particular embodiment, the personal data 1^^-] provided by the selector in relation to a service (not illustrated) are suitable for constituting the shared personal data dpp. In particular, the personal data selector 133 includes: - a user selector (not shown) capable of allowing a user to select personal data j dp.} from the personal data | dp. | = {dp[ ty*. )} of selected type(s) tyni, {ty„. | corresponding to a selected function of a service sv_fct;. Specifically, the user selector (not shown) includes: - a second type selector (not shown) capable of selecting a type tynj, from among the selected types tyni, corresponding to a function selected from an sv_fct service; such as those provided by the first type selector. Specifically, the type(s) of selected personal data actions performed by user U correspond to an action by user U, in particular by means of a user terminal 2 and / or a user interface 22 on one(s) type(s) tyni, \ty .} corresponding to a selected function of a service sv_fct; such as those provided by the provisioning device 132 of a list of personal data types LST_PV possibly reproduced. In particular, the user selector is able to receive personal data | dp.} of a type tynp | from among the set of personal data {dp} of a user U of the service sv in particular from a personal data storage device 131.

[0224]

[0225]

[0226]

[0227]

[0228]

[0229]

[0230] In particular, the user selector is able to receive personal data |dp| in response to a personal data request dp_rq[tynj.] depending on the type(s) selected tynj, ,By the user U. In a particular embodiment, the personal data {dp.j provided by the user selector are suitable for constituting the shared personal data dpp. In particular, following receipt of an ack agreement from user U, the personal data sharing process device 13, 123 is then able to provide as shared personal data dpp the selected personal data [dp;], [dp A .dpp = [dp.] , dpp= [dp} . 1 'J'} In particular, 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 [dp.} , : dpp= [dp.], dpp= [dp.] upon receipt of an ack agreement from user U. Specifically, validator 134 is triggered by the ack agreement of user U. In particular, the configuration device 12 is capable of providing the personal data sharing device 13, 123 with the selected functionality fct;, sv_fcti. 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 data personal data shared by the sharing device 13, 123 to the configuration device 12 are personal data of a type associated with the selected service functionality: {dp;};, or even selected by the user U from personal data of a type associated with the selected service functionality: {dpj}j.

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

[0232] In particular, service modifier 122 includes: - an operator (not shown) capable of performing an operation on a selected function (fct); relative to the service (sv) based on a user action (a) U. Specifically, the operator qualified to perform an operation on the selected functionality fcti must be at least one of the following operators: - an adder (not shown) capable of adding the selected functionality to the sv service; - a suppressor (not shown) capable of removing the selected RMV functionality from the sv service.

[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] In particular, if action a is an add action: a=ADD, then service modifier 122 is capable of triggering the adder of the selected feature fct; on the service sv: sv* = sv + fct;. In particular, if action a is a delete action: a=SUPR, then service modifier 122 is capable of triggering the deleter of the selected feature fct; on the service sv: sv* = sv - Here,.

[0235] In particular, the service modifier 122 as a function of the action a of the 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] Figure 6 illustrates 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; from the set of functions {fctk]k of a service sv provided by a service provider device 1,31 to the user terminal 2, the selection of the function triggering a selection of personal data of a type tyni, tynj from the set of personal data [dpÇty^} of a user U of a service sv according to a selected function fct;, the service provider device 1,31 being capable of providing the service sv* according to the selected function fct;.

[0239] In particular, 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 comprising the service provider device 1,31.

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

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

[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, such as a selected function fct;, a type selected by the user tyn-r, an agreement ack...; and / or - a user output interface 221, such as a reproduction interface capable of receiving a reproduction command rpr. The reproduction interface 221 is in particular a screen of the user terminal 2.

[0243] The invention also relates to a medium. The information 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, especially an Internet-type network.

[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 by means of 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 to any element of a program or software capable of implementing a function or a set of functions as described above. A hardware component corresponds to any element of a hardware assembly capable of implementing a function or a set of functions.

Claims

Demands

1. A method of sharing personal data with a service, the sharing method 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.

2. Sharing method according to the preceding claim, the sharing method comprising: - validating the selected personal data as personal data shared with the service.

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

4. Sharing method according to one of claims 2 or 3, reproduction being carried out prior to validation of the selected personal data.

5. 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 based on a selected feature.

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

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

8. Configuration method according to any 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 that functionality.

9. A 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.

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

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

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

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

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

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