END DEVICE, DEVICE FOR ADJUSTING SERVICE REQUIREMENTS AND METHOD FOR ENCOURAGING A ADJUSTED SERVICE

Description

Previous technique

[0001] The invention relates to the general field of telecommunications. It relates more particularly to the provision of a service.

[0002] In accordance with current technology, some websites or software applications use a unique, anonymous identifier for each user to provide a personalized service. For example, a retailer's website might provide a user with content based on that user's purchase history or browsing history.

[0003] According to current technology, a user can be identified by personal contact information, such as their email address or phone number, usually associated with a password. Alternatively, the user can be identified by one of their user accounts on social networks, for example, their Facebook or LinkedIn account (registered trademarks).

[0004] These prior art methods are unsatisfactory because they require the user to provide certain personal information to receive a service. This contradicts personal data protection regulations, such as the General Data Protection Regulation (GDPR) 2018 in Europe.

[0005] There is therefore a need for a solution that does not present the disadvantages of known state-of-the-art methods to allow a user to access a personalized service without disclosing their personal information, in other words, anonymously.

[0006] Finally, document GB 2 549 786 A1, describing a method and system for storing and controlling access to anonymous personalized behavioral data, is also known. Description of the invention

[0007] The invention relates to a method of requesting a personalized service by a communication terminal according to claim 1.

[0008] Correspondingly, the invention relates to a communication terminal configured to request a personalized service according to claim 13.

[0009] The terminal, according to the invention, implements the personalized service request process according to the invention.

[0010] The features and advantages of the personalized service request method according to the invention, presented below, apply equally to a terminal conforming to the invention, and vice versa. According to the invention, the terminal can be a smartphone, a tablet, a smartwatch, or any other communicating device, particularly one equipped with a fingerprint reader. For the purposes of the invention, the anonymous unique identifier allows an account to be identified with the service request personalization device. The terminal inserts the identifier into its requests so that the personalization device recognizes that these requests correspond to the same account.In other words, the anonymous unique identifier makes it possible to identify all requests coming from the terminal without disclosing, either to the service delivery device(s) or to the personalization device, any information about the terminal itself (MAC address, brand, model), or about the terminal user (name, email address, telephone number).

[0011] The invention allows the terminal user to receive a response to the service request via an account associated with the anonymous unique identifier, without having provided personal information such as their email address, telephone number or a social network account.

[0012] The anonymous unique identifier according to the invention is an anonymous identifier that does not allow the identification of the terminal user. The anonymous unique identifier according to the invention is associated with an account on the personalization device for the terminal.

[0013] The anonymous unique identifier can constitute a unique application code, for a software application installed on the terminal, this application including instructions for executing the steps of a personalized service request process according to the invention.

[0014] In one embodiment, the anonymous unique identifier is obtained using a random number generation function. In practice, this random number generation function is configured to avoid generating identical identifiers and to statistically ensure that all generated identifiers are unique.

[0015] In one embodiment, the terminal itself generates the anonymous unique identifier, for example by executing a random generation function.

[0016] In particular, obtaining the unique anonymous identifier by the terminal involves: sending a request for an anonymous unique identifier to the personalization device; and receiving the anonymous unique identifier from the personalization device.

[0017] In another embodiment, the personalization device can generate the anonymous unique identifier using a random generation function.

[0018] In one embodiment, the personalized service request process includes: a sending of a service request associated with the anonymous unique identifier to the service delivery device; and following this sending, a receipt of a personalized response from the service delivery device, the personalized response resulting from a processing implemented by the service delivery device based on a modified request received from the service request personalization device, the modified request having been generated by the service request personalization device from the service request sent and the associated anonymous unique identifier.

[0019] In one embodiment, the personalized service request process further includes a step of capturing a service-related code. The service request sent by the terminal consists either of an initial service request based on the captured code or a first service request obtained based on the initial service request. In this embodiment, the terminal also includes a code sensor, for example, this sensor comprising a camera, a radio receiver such as NFC or Zigbee, or capable of digitizing a code, etc.

[0020] In particular, the terminal generates an initial service request based on: the initial service request obtained based on the captured code, and the anonymous unique identifier of the terminal for the personalization device.

[0021] The invention thus allows the terminal user to easily and anonymously receive a personalized service. The user simply needs to photograph the code using their terminal. The terminal, implementing the method of the invention, generates the initial request containing the anonymous unique identifier and the initial service request resulting from the captured code, and sends this initial request to the personalization device to access the service.

[0022] In particular, the code can be a "QR code" type code or an "NFC tag" type code.

[0023] A program installed on the terminal to implement the personalized service request process according to the invention, and the code can be managed by the same administrative entity, for example the same company developing a software application for purchasing products, and offering codes affixed to products sold by that company.

[0024] Two terminals scanning the same code can access two different services. This is because the two terminals have different unique identifiers, and therefore the content of the requests sent to the personalization device is different. According to one application of the invention, when the code identifies a product sold in a store, the prices for the same product may differ, for example, if one of the unique identifiers corresponds to an account that benefits from a discount.

[0025] In one embodiment of the invention, obtaining an identifier is implemented upon receipt by the personalized service request device of a notification from the terminal following a successful unlocking of the personalized service request device.

[0026] In one embodiment of the invention, obtaining an identifier is implemented upon receipt by the personalized service request device of a notification from the terminal following a first successful unlocking of the personalized service request device.

[0027] These two modes allow verification that the custom service request device is being used by the terminal owner or its usual user, since they have successfully unlocked it, for example, using a PIN or the user's fingerprint. Therefore, when the terminal supports unlocking the custom service request device, the unlock authorization notification transmitted by the terminal—specifically, a system device on the terminal—to the custom service request device is used to trigger the retrieval of the anonymous unique identifier.

[0028] Furthermore, these methods ensure that the anonymous unique identifier is obtained through legitimate use of the personalized service request mechanism. The obtained identifier is stored in the terminal's memory and included in requests sent from the terminal to the personalization system. In this way, the identifier allows for the identification of an account associated with the terminal's regular user, while preserving the user's anonymity.

[0029] Obtaining the anonymous unique identifier is contingent upon unlocking the terminal's personalized service request device. Therefore, if the terminal is a multi-user terminal, a distinct anonymous unique identifier is associated with each user of the terminal via a separate account with the personalized service request device and the personalization device. The invention also relates to a method for personalizing service requests using a service request personalization device according to claim 7.

[0030] Correspondingly, the invention relates to a device for personalizing service requests according to claim 14.

[0031] The personalization device according to the invention implements the service request personalization method of the invention. The characteristics and advantages of the personalization method of the invention presented below apply equally to a personalization device according to the invention, and vice versa.

[0032] The personalization device according to the invention can be connected, via a telecommunications network, to several terminals, including terminals conforming to the invention. Furthermore, the personalization device according to the invention is connected to one or more service delivery devices and allows requests for at least one service provided by this or these service delivery devices.

[0033] In one embodiment, the personalization device according to the invention obtains the anonymous unique identifier by generating it, for example using a random generation function, following the receipt of a request from a terminal according to the invention.

[0034] In another mode, the personalization device according to the invention obtains the anonymous unique identifier by receiving it from a terminal according to the invention.

[0035] Specifically, when the terminal sends the anonymous unique identifier to the personalization device for the first time, it can send it alone, or as part of a service request. In the latter case, the personalization device's retrieval of the anonymous unique identifier is triggered upon receiving a request containing that identifier.

[0036] Updating the database by recording access information allows service requests to be tracked using the anonymous unique identifier. The personalization device can thus collect data useful for customer relationship management for the services it provides access to. In particular, the database managed by the personalization device according to the invention can be shared across multiple services, especially when the personalization device is connected to different service delivery devices.

[0037] In one embodiment of the invention, the service request personalization process includes a database consultation, the second request being obtained by modifying the first request based on a result of the database consultation.

[0038] In this mode, the request manager of the personalization device, according to the invention, is configured to consult the database and to obtain the second request by modifying the first request based on a result of the database consultation.

[0039] For example, the personalization device according to the invention can enrich or modify the first request with data on a purchase history made by the same account identified by the anonymous unique identifier, and thus obtain the second modified request, which will be transmitted to the service delivery device. The service delivery device can then provide a personalized response, for example, web pages relating to products likely to interest the user associated with the anonymous unique identifier, or special discounts based on a certain number of purchases, without the service delivery device having any knowledge of this anonymous unique identifier, or even of the user's identity or their terminal. The user of the terminal according to the invention therefore benefits from the personalized service without having provided personal identifiers such as an email address or a telephone number.

[0040] In another example, the personalization device according to the invention obtains the second request by enriching the first request with a status related to the number of requests for the same service, using the anonymous unique identifier, for example, a status among "visitor," "customer," and "premium customer." Upon receiving this modified request, the service delivery device for that service can provide a personalized service based on the status to which the anonymous unique identifier is associated.

[0041] In one embodiment, the personalized service request method according to the invention, implemented by the terminal, further includes a step of sending terminal location information, such as a GPS (Global Positioning System) position, to the personalization device. This information allows the personalization device to direct the request to a specific service provider based on the location information. For example, if the request relates to a service offered by an international retailer's website, the personalization device can direct the request to a service provider offering that service in the country corresponding to the terminal's location, for example, "orange.fr" for a terminal in France and "orange.be" for a terminal in Belgium.

[0042] In another example, information about the terminal's location can be transmitted from the personalization device according to the invention to a service delivery device, the service delivery device providing a personalized service based on this location information. For example, if the request relates to an event communication service, the service delivery device can provide a communication service about events occurring in the same geographic region as the terminal.

[0043] The invention also relates to a computer program according to claim 11.

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

[0045] The invention also relates to a computer-readable recording medium according to claim 12.

[0046] Information or recording media can be any entity or device capable of storing programs. For example, media 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 drive, or a flash memory.

[0047] On the other hand, information or recording media can be transmissible media such as an electrical or optical signal, which can be carried via an electrical or optical cable, by radio link, by wireless optical link or by other means.

[0048] The programs according to the invention can in particular be downloaded onto an Internet-type network.

[0049] Alternatively, each information or recording medium can be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of one of the methods according to the invention. Brief description of the drawings

[0050] Other features and advantages of the present invention will become apparent from the description below, with reference to the accompanying drawings, which illustrate an example of an embodiment without being limiting in any way. In the figures: Fig. 1 , an architecture of a telecommunications network in which processes of the invention are implemented according to an embodiment of the invention; Fig. 2, an organizational chart representing the steps of a personalized service request process and the steps of a process enabling the personalization of service requests, the processes being in accordance with the invention and implemented according to a first embodiment; Fig. 3 , an organizational chart representing the steps of a personalized service request process, the process being in accordance with the invention and implemented according to a second embodiment; Fig. 4 , functional architectures of a terminal according to the invention and of a system comprising a service request personalization device according to the invention; Fig. 5 , a hardware architecture of a terminal according to an embodiment of the invention; and Fig. 6 , a hardware architecture of a service request personalization device according to an embodiment of the invention. Description of the implementation methods

[0051] There figure 1This illustrates the architecture of a NET telecommunications network in which the personalized service request process and the service request personalization process, according to the invention, are implemented according to an embodiment of the invention. No limitations are imposed as to the nature of the NET. The NET can be, for example, the Internet. A terminal T and a service request personalization device P, according to the invention, are connected to the NET. The service request personalization device P cooperates with one or more SRV service delivery devices that are either co-located with the personalization device P or remote. The pair formed by the service request personalization device P and an SRV service delivery device during a personalized service request constitutes a SYS.

[0052] The terminal T can be a smartphone, tablet, smartwatch, or any other type of communicating device. In this example, the terminal T has a sensor, which may include a camera, a device for scanning a code such as a barcode or QR code, or a transmitter, such as an NFC receiver.

[0053] This T terminal includes a DSP device for personalized service requests.

[0054] The SRV service delivery device may include a server hosting at least one website or a software application providing one or more services to clients. The personalization device P acts, in particular, as an intermediary between the SRV service delivery device and its clients, such as the user of terminal T.

[0055] Optionally, the personalization device P is implemented in the SRV service delivery device (not shown). In this case, the personalization device P of the SRV service delivery device provides a second service request based on the first service request received from the communication terminal T to one or more servers or a processing device implementing a service based on the second service request.

[0056] The personalization device P and / or the service delivery device SRV can be software modules implemented on physical devices with a computer architecture. For example, the personalization device P is a service intermediation platform implemented in PHP, and the service delivery device SRV can be implemented in HTML.

[0057] Alternatively, the P personalization device and / or the SRV service delivery device can be physical devices.

[0058] In this mode illustrated by the figure 1 In one mode, the personalization device P is implemented in a device separate from the device implementing the SRV service delivery device. In another mode, the personalization device P is implemented in the same physical device as the SRV service delivery device.

[0059] In the mode illustrated by the figure 1The personalization device P is dedicated to intermediating the services offered by the SRV service delivery device. Alternatively, the personalization device P can be shared between several service delivery devices, including the SRV service delivery device, and form a personalization device for the different services offered by these service delivery devices.

[0060] There figure 2 is an organizational chart representing steps in the personalized service request process, and steps in the service request personalization process according to a first embodiment of the invention, the processes being in accordance with the invention.

[0061] The personalized service request process is implemented by terminal T, while the service request personalization process is implemented by the personalization device P. In particular, the steps Exxx described below are steps of the personalized service request process according to the invention. The steps Fxxx described below are steps of the service request personalization process according to the invention.

[0062] In particular, the personalized service request method according to the invention is executed by a computer program PROG1 stored in the terminal T. In the mode described here, the PROG1 program is a software application installed on the terminal T. In particular, the PROG1 application can be downloaded from the personalization device P or from another device managed by the same administrative authority as the personalization device P.

[0063] In particular, Terminal T is configured through its PROG1 application to obtain an AoC_P address from the personalization device P in order to communicate with it.

[0064] Access to the terminal T's personalized service request device is unlocked by its user, for example, via a PIN code or the user's fingerprint. During step E060, the PROG1 program receives a notification from a lock and unlock mechanism implemented in the terminal, informing it of the successful unlocking of the terminal T's personalized service request device.

[0065] Following the unlocking of terminal T and during step E100, terminal T obtains a unique anonymous CUA identifier. This identifier identifies an account with the personalization device P, accessible from the PROG1 application installed on terminal T. Thus, the unique anonymous identifier is associated not with terminal T itself, but with the user who, through unlocking, gained access to the DSP device for requesting personalized services. On a multi-user terminal, this allows each user to benefit from a personalized service, rather than a personalized service for the terminal as a whole.

[0066] In this first embodiment, terminal T obtains the anonymous unique identifier (CUA) by executing a random generation function. The anonymous unique identifier (CUA) is thus generated by terminal T. To guarantee the uniqueness of the identifier generated by the terminal, it is based either on a unique piece of data provided by the personalization device P or on user-specific identification data. In particular, the function applied to the user-specific identification data to generate the anonymous unique identifier prevents a third party from recovering this identification data through a reverse function. Thus, the anonymity of the anonymous unique identifier is secured.

[0067] In the embodiment described here, during a step E200, the terminal T stores the anonymous unique identifier CUA in a memory of the terminal T. Alternatively, the anonymous unique identifier CUA is regenerated, preferably identically, at each unlock or for each service request sent by the terminal to the service request personalization device P.

[0068] During step E120, terminal T sends, for example via its PROG1 application, the anonymous unique identifier CUA to the personalization device P. Specifically, terminal T knows the address of the personalization device P thanks to the configuration of the PROG1 application. Terminal T does not send the personalization device P an email address, a phone number, or any other personal information that could identify the user of terminal T. The anonymous unique identifier CUA guarantees the anonymity of the user initiating the service request.

[0069] During a step F100a of the service request personalization process, the personalization device P obtains the anonymous unique identifier CUA from terminal T. In a subsequent step F200a, the personalization device P creates, in association with the anonymous unique identifier CUA, a log Nw_lg in its memory, for example in a database, to store traces of service requests associated with this anonymous unique identifier CUA. This log can, for example, be in the form of a history or a record of service requests associated with the anonymous unique identifier CUA.

[0070] In particular, in this embodiment, the personalization device P implements a customer relationship management system or runs customer relationship management software. The personalization device P stores in its memory, for example in the database BD, the unique identifiers of several accounts corresponding to user accounts of services provided by the service delivery device SRV. The identity of the users is not known by either the personalization device P or the service delivery device SRV.

[0071] During step E280 of the personalized service request process according to the invention, terminal T captures a code, for example a QR code, by scanning, reading, photographing, etc. This code can provide an initial QR request to access a web page hosted by the SRV service delivery device. The first request within the meaning of the invention may include this initial QR request.

[0072] Thus, in particular, during step E300, terminal T, and more specifically the terminal T's personalized service request device, generates the first request Req containing the initial request QR. This first request is associated with the anonymous unique identifier CUA read from terminal T's memory. In one embodiment, the first request Req contains the anonymous unique identifier CUA. In another embodiment, the first request Req is sent with the anonymous unique identifier CUA in the same data packet to the personalization device P, the first request Req indicating that the initial request QR is to be personalized.In particular, terminal T can, during the E300 step of generating the first Req request, either enrich the initial QR request with other information, or generate a first Req request by integrating the initial QR request and possibly other information, such as GPS location information of terminal T; such information allows the personalization device P to identify the geographical position of the captured code.

[0073] In particular, terminal T sends the first Req request to the personalization device P during an E400 step. Indeed, the personalization device P is an intermediary device between terminal T and the SRV service delivery device, allowing terminal T to receive in particular the web page corresponding to the captured code.

[0074] In particular, during a step F300 of the service request personalization process, the personalization device P receives the first Req request and extracts from this first Req request the anonymous unique identifier CUA and the initial QR request, notably in the form of a link to the web page corresponding to the captured code.

[0075] In particular, the personalization device P stores the CUA identifier in its memory, for example in the database BD indexed by anonymous unique identifiers. In the embodiment described here, this database BD contains information on the history of services provided by the SRV service delivery device, for example, the history of services requested by the terminal T (in particular, via its DSP device for requesting personalized services, or via its PROG1 application to the SRV service delivery device). For example, when the SRV service delivery device hosts a merchant's website, the database BD may contain a history of purchases made by the terminal T's account from that website, or a history of web pages of that website visited by the terminal T's account.In another example, the database records the number of requests containing the anonymous unique identifier CUA that it has received to connect to the SRV service delivery device.

[0076] In the mode described here, the database BD is stored in a memory of the personalization device P. Alternatively, the database BD can be stored in a device separate from the personalization device P but accessible by the personalization device P.

[0077] In particular, based on the obtained CUA identifier, the personalization device P consults the database BD during a step F400. The personalization device P can update the database BD during a step F200b, according to the content of the Req request, for example by recording the content of the Req request in association with the CUA identifier, or by incrementing a counter of the number of accesses to the same service as that designated by the Req request, or by recording the GPS location information of the terminal T. The personalization device P thus records, in a field of the database BD, information relating to the service provided by the SRV service delivery device.

[0078] During an F500 step, the personalization device P modifies the first Req request based on a hist(CUA) result from the database query, for example, by specifying the number of views of the QR web page associated with the captured code, or by specifying the GPS location of terminal T. The personalization device P then obtains a second ReqM request from the first Req request. Thus, to obtain a personalized service from the SRV service delivery device, the SRV service delivery device does not need to know that the service request comes from the same user (even if anonymous).

[0079] In particular, the second ReqM request does not include the anonymous unique identifier. User anonymity is thus doubly guaranteed since not only does the service delivery device not have access to the user's identity, but it also does not have access to all of the user's service request habits, but only to those useful for personalizing the service.

[0080] In particular, during an F600 step, the personalization device P sends the second ReqM request to the SRV service delivery device.

[0081] The SRV service delivery device receives the ReqM request during a G100 step.

[0082] During a G200 step, the SRV service delivery device obtains Resp data based on the ReqM request and in particular based on traces linked to the anonymous unique identifier, this Resp data being personalized according to the traces provided hist(CUA).

[0083] For example, personalized data could be a web page determined based on QR information included in the captured code (E280) and the GPS location of terminal T, such as a web page relating to museums in Paris, when the QR information included in the code corresponds to a website describing museums in France and when the GPS location of terminal T corresponds to Paris.

[0084] According to another example, personalized data can be a web page determined based on a purchase history associated with the anonymous unique identifier CUA and a QR link to a merchant site included in the captured code (E300).

[0085] In particular, during the G200 step, the SRV service delivery device sends the personalized Resp data to the personalization P device in response to the ReqM request.

[0086] In particular, during an F700 step, the personalization device P receives the personalized data Resp and transmits it to the terminal T.

[0087] Terminal T receives the personalized Resp service, including personalized data, during an E500 step. Thus, the personalization device P enabled Terminal T to access the service offered by the SRV service delivery device in a personalized and anonymous manner without revealing any identifier of the Terminal T user. By sending the personalized data, the SRV service delivery device provides a personalized service for the account identified at the personalization device P level by the anonymous unique identifier CUA.

[0088] Each time terminal T sends a request to the personalization device P, it inserts the anonymous unique identifier CUA to enable the personalization device P to identify the same account, personalize the service request transmitted to the SRV service delivery device, and return personalized data for that account to terminal T.

[0089] We note that the anonymous unique identifier CUA identifies the account with the personalization device, for terminal T, and not the terminal T user. For this reason, in the mode described with reference to the figure 2 , the anonymous unique identifier CUA is generated (E100) by terminal T upon receipt (E060) of a notification corresponding to a successful unlocking by terminal T of the personalization request device to guarantee the uniqueness of the identifier per user.

[0090] For better security, the PROG1 application is only executed upon detection of a notification relating to a successful unlocking of the personalized service request device, for obtaining (E100) the anonymous unique identifier CUA.

[0091] In a variant of the first mode described with reference to the figure 2 , when terminal T obtains (E100) the CUA identifier, it does not transmit it directly to the personalization device P. Step E120 described previously, and a fortiori steps F100a and F200a are not implemented.

[0092] According to this second variant, terminal T sends the anonymous unique identifier (CUA) to the personalization device P only as part of a request transmission (E400). Suppose that the request Req is the first request that terminal T sends (E400) to the personalization device P. When the personalization device P receives (F300) this first request Req, it extracts (F100b) the CUA. The personalization device P then obtains the anonymous unique identifier (CUA) for the first time during a step F100a, and stores it in its memory during step F200b.

[0093] In particular, the personalization process extracts (F100b) from the first Req request received (F300) from terminal T the initial QR request and the associated anonymous unique identifier CUA.

[0094] In particular, the personalization process uses these two elements extracted from the first Req request (the initial QR request and the anonymous unique identifier CUA) to record (F200b) the initial request or elements based on the initial QR request in a memory of the personalization device in association with the anonymous unique identifier, thus enabling the generation and / or maintenance of traces of personalized service requests associated with the anonymous unique identifier CUA. Specifically, the recording of Ig(QR) traces (F200b) is performed in a database BD indexed by the anonymous unique identifiers of users using the service request personalization device P.

[0095] In particular, the modification of query modifQR (F500) modifies or enriches the initial extracted QR query (F100b) based on the results of the F400 consultation based on the anonymous unique identifier CUA of the traces previously recorded in the memory of the service request personalization device P, in particular in the indexed database BD.

[0096] In one embodiment, the second ReqM query is identical to the first Req query. In particular, the second ReqM query is identical to the first Req query during a first request for a personalized service by a user since the personalization device has no personal data on the user, because it has not yet recorded a history of service requests.

[0097] In particular, depending on the service request, the user may exceptionally wish to transmit identifying data to the service delivery device, such as their postal address in the case of purchasing a physical item, their email address in the case of purchasing content, etc. In these cases, the personalized service request process according to the invention further includes lifting the anonymity of a terminal user (not illustrated) upon receipt of an explicit request from that user.

[0098] For example, the terminal checks whether its user wishes to request a personalized service anonymously or not, particularly depending on the type of service requested. If the terminal verifies that the user wishes to disclose one of their identifiers, such as their email address or phone number, then the terminal lifts anonymity, for example by sending the user's identifier to the personalization device P.

[0099] There figure 3 is a flowchart representing steps in the personalized service request process and steps in the service request personalization process according to a second embodiment of the invention, the processes being consistent with the invention. In particular, steps E060, E080, E100c, and E200 described below are steps in the personalized service request process according to the invention, implemented by terminal T. Steps F080, F100c, F200c, and F220 described below are steps in the process for personalizing service requests according to the invention, implemented by the personalization device P.

[0100] This second mode differs from the first mode described with reference to the figure 2 in the method of obtaining the unique and anonymous CUA code.

[0101] During an E060 step, similar to the E060 step described with reference to the figure 2, terminal T and in particular its PROG1 application receives information indicating a successful unlocking of terminal T.

[0102] During an E080 step, terminal T sends a request D for an anonymous unique identifier to the personalization device P.

[0103] The personalization device P receives the request D during a step F080.

[0104] In this second mode, the personalization device P obtains the anonymous unique identifier CUA during a step F100c by generating it, for example by executing a random generation function.

[0105] During a step F200c, the personalization device P creates for the anonymous unique identifier CUA in its memory a space for managing traces of service requests originating from this anonymous unique identifier, notably by indexing a part of a database using the generated anonymous unique identifier CUA.

[0106] In parallel and during a step F220, the personalization device P sends the anonymous unique identifier CUA to terminal T in response to its request D.

[0107] Terminal T receives the anonymous unique identifier CUA during step E100c and stores it in its memory during step E200, similar to step E200 described in reference to the figure 2 .

[0108] The methods of the invention, according to this second mode, further comprise steps identical to steps E280, E300, E400 and E500 of the personalized service request method and to steps F300, F400, F500, F600 and F700 of the service request personalization method, these steps having already been described with reference to the figure 2 .

[0109] There figure 4represents functional architectures, according to an embodiment of the invention, of the terminal T, the personalization device P, and the service delivery device SRV, the terminal T, the personalization device, and the service delivery device conforming to the invention. Optionally, the personalization device P and the service delivery device SRV constitute a personalized service delivery system SYS.

[0110] The SYS system, comprising the P personalization device and the SRV service delivery device, allows the terminal T to receive a service from the SRV service delivery device, personalized for an account identified by the P service request personalization device using the CUA identifier.

[0111] Terminal T is configured to request a customized service provided by the SRV service delivery device. Terminal T includes: an identification obtainr (mID) configured to obtain, following an unlock (E060) of access to a personalized service request device implemented in the terminal (T), a unique anonymous identifier (CUA), capable of being transmitted, by said terminal (T), in association with a service request, to a service request personalization device (P), the service request being destined for the service delivery device (SRV).

[0112] In particular, terminal T also includes: a memory configured to store (E200) the anonymous unique identifier CUA.

[0113] In particular, the terminal also includes: an mGEN query generator configured to generate (E300) the first Req query in association with the anonymous unique identifier CUA to access said service.

[0114] Specifically, the first Req request is formed from an initial impersonal QR request. The initial request is, for example, provided by a code reading device, such as a QR code or NFC code reader, etc.

[0115] The barcode reader is, for example, implemented in or connected to the terminal. The terminal then receives the initial QR code request from the barcode reader. The barcode reader includes, for example, a sensor such as a camera, scanner, etc., or a radio receiver such as an NFC receiver, which allows it to either directly read or receive the initial QR code request within the code or, upon reading the code, trigger a search for data associated with the code containing the initial QR code request. Specifically, the barcode reader includes a command to search a remote database of codes for associated data. For example, the user can photograph or scan a QR code or barcode on an advertising or information panel using the camera on the terminal.Either the reader includes a decoder and / or an extractor allowing the initial QR request to be extracted from the code, or the reader uses the code (possibly decoded) to search a remote code database for data associated with the read code and receive from this remote code database the initial QR request allowing a quick service request.

[0116] In particular, terminal T includes an mCOM transmitter configured to send (E400) the first Req request to the personalization device P.

[0117] Terminal T does not send any identifier of the terminal T user to the personalization device P.

[0118] The service request personalization mechanism is, in particular, placed between a personalized service request mechanism implemented in a communication terminal (T) and a service delivery mechanism. It comprises: a transmitter (mCOM') configured to receive a first service request (Req) associated with an anonymous unique identifier (AUI) from the communication terminal (T), said anonymous unique identifier (AUI) having been obtained following an unlock (E060) of access to said personalized service request device, the first service request (Req) enabling the service request personalization device (P) to generate a second request (ReqM) from said first service request (Req), said second request (ReqM) being personalized according to data previously recorded by the service request personalization device in association with said anonymous unique identifier (AUI).

[0119] The P personalization device allows personalization of at least one service, including the service provided by the SRV service delivery device.

[0120] In particular, the P personalization system includes: an acquirer mID' (F100a, F100b, F100c) of the anonymous unique identifier CUA of an account with the personalization device, this identifier not identifying a user of a terminal;

[0121] In particular, the P personalization system includes: a memory configured to record (F200a, F200b, F200c) traces of service requests in association with the anonymous unique identifier CUA;

[0122] In particular, the P personalization system includes: an mCOM' transmitter configured to receive the first Req request containing the anonymous unique identifier CUA; this transmitter being configured to send the second ReqM request to the SRV service delivery device, this second ReqM request being obtained from the first Req request of prior service requests associated with the anonymous unique identifier CUA.

[0123] In particular, the P personalization system includes: an extractor configured to extract from the first Req query, the initial QR query and the associated anonymous unique identifier CUA.

[0124] In particular, the P personalization system includes: an mBD access manager, configured to record, in a field of the database indexed by said unique identifiers, information relating to said service requests (traces of service requests).

[0125] In particular, the P personalization system includes: an mBD access manager, configured to consult, in particular in a field of the BD database indexed by said unique identifiers, information relating to said service requests (traces of service requests) associated with the anonymous unique identifier received in the first Req request.

[0126] The SRV service delivery device provides (G200) a personalized service for the account based on the CUA identifier.

[0127] In the embodiment described here, the terminal T has the hardware architecture of a computer, as illustrated in the figure 5 .

[0128] The architecture of terminal T includes in particular a processor 7, a random access memory 8, a read-only memory 9, a non-volatile flash memory 10 in a particular embodiment of the invention, as well as communication means 11. Such means are known per se and are not described in more detail here.

[0129] The read-only memory 9 of the terminal T according to the invention constitutes a recording medium according to the invention, readable by the processor 7 and on which is recorded here a computer program PROG1 according to the invention.

[0130] The memory 10 of terminal T allows for the recording of variables used for the execution of the steps of the personalized service request process according to the invention, such as the anonymous unique identifier CUA, the Req request, the personalized data Resp, and an AoC_P contact address of the personalization device P.

[0131] The computer program PROG1 defines functional and software modules here, configured to access a service anonymously. These functional modules rely on and / or control the hardware elements 7-11 of the T terminal mentioned previously.

[0132] Terminal T can also implement the service access method according to the invention, when it is configured to lift anonymity upon receipt of an explicit request from the user of terminal T.

[0133] In this case, the read-only memory 9 of the terminal T according to the invention constitutes a recording medium conforming to the invention, readable by the processor 7, and on which a computer program PROG1 conforming to the invention is recorded. The computer program PROG1 defines functional and software modules, configured to access a service. These functional modules rely on and / or control the hardware elements 7-11 of the terminal T mentioned above.

[0134] In the embodiment described here, the personalization device P has the hardware architecture of a computer, as illustrated in the figure 6 .

[0135] The architecture of the personalization device P includes in particular a processor 7, a random access memory 8, a read-only memory 9, a non-volatile flash memory 10 in a particular embodiment of the invention, as well as communication means 11. Such means are known per se and are not described in more detail here.

[0136] The read-only memory 9 of the personalization device P according to the invention constitutes a recording medium according to the invention, readable by the processor 7 and on which is recorded here a computer program PROG2 according to the invention.

[0137] The memory 10 of the personalization device P allows for the recording of variables used for the execution of the steps of the process enabling a request for a personalized service to at least one service, according to the invention, such as the anonymous unique identifier CUA, the Req query, the personalized data Resp, the database BD or an address to access this database, and an AoC_SRV contact address of the SRV service delivery device.

[0138] The PROG2 computer program defines functional and software modules here, configured to allow anonymous access to at least one service. These functional modules rely on and / or control the hardware elements 7-11 of the P personalization device mentioned previously.

Claims

1. Method for requesting a personalized service by a communication terminal (T), said method comprising, following an unlocking (E060) of an access to a personalized service request device, said device being implemented in the communication terminal: - obtaining (E100, E100c) an anonymous unique identifier (CUA), capable of being transmitted by said terminal (T), in association with a service request, to a service request personalization device (P), the service request being intended for a service provision device (SRV) .

2. Method according to Claim 1, wherein obtaining the identifier (CUA) comprises one of the following steps: - generating the anonymous unique identifier (CUA), - receiving the anonymous unique identifier (CUA) from an anonymous unique identifier generator implemented in an equipment of a communication network distinct from the service provision device (SRV).

3. Method according to either one of Claims 1 and 2, the method comprising: - sending (E400) a service request (Req) associated with the anonymous unique identifier (CUA) to the service provision device (SRV); and - following this sending, receiving (E500) a personalized response (Resp) from the service provision device (SRV), the personalized response (Resp) resulting from processing (G200) implemented by the service provision device (SRV) based on a modified request (ReqM) received from the service request personalization device (P), the modified request (ReqM) having been generated (F500) by the service request personalization device (P) on the basis of the sent service request (Req) and of the associated anonymous unique identifier (CUA).

4. Method according to any one of Claims 1 to 3, furthermore comprising capturing (E280) data relating to said service, the data capturing triggering sending of said service request (Req).

5. Method according to Claim 4, wherein the data are obtained from a QR code or NFC tag code.

6. Method according to any one of Claims 1 to 5, furthermore comprising sending information concerning the location of said terminal (T) to the service provision device (SRV).

7. Method for personalizing service requests by a service request personalization device (P), said method comprising: - receiving (F300) a first service request (Req) associated with an anonymous unique identifier (CUA) from a communication terminal (T), the first service request (Req) enabling the service request personalization device (P) to generate a second request (ReqM) on the basis of said first service request (Req), said second request (ReqM) being personalized based on data previously recorded by the service request personalization device in association with said anonymous unique identifier (CUA).

8. Method according to Claim 7, comprising sending (F600) said second request (ReqM) to said service provision device (SRV).

9. Method according to Claim 7 or 8, comprising recording, in a database (BD), information relating to the first request indexed by the anonymous unique identifier.

10. Method according to Claim 9, comprising consulting said database (BD), said second request being obtained by modifying (F500) the first request based on a result of said consultation.

11. Computer program (PROG1, PROG1b, PROG2) comprising instructions for carrying out the steps of a method for requesting a personalized service according to any one of Claims 1 to 6 or the steps of a method for personalizing service requests according to one of Claims 7 to 10.

12. Computer-readable recording medium on which a computer program according to Claim 11 is recorded.

13. Communication terminal (T) configured to request a personalized service, and characterized in that it comprises: - an identification obtainer (mID) configured to obtain, following an unlocking (E060) of an 3access to a personalized service request device implemented in the terminal (T), an anonymous unique identifier (CUA) capable of being transmitted by said terminal (T), in association with a service request, to a service request personalization device (P), the service request being intended for a service provision device (SRV).

14. Service request personalization device (P), comprising: - a transmitter (mCOM') configured to receive a first service request (Req) associated with an anonymous unique identifier (CUA) from a communication terminal (T), the first service request (Req) enabling the service request personalization device (P) to generate a second request (ReqM) on the basis of said first service request (Req), said second request (ReqM) being personalized based on data previously recorded by the service request personalization device in association with said anonymous unique identifier (CUA).