Abstract:
This invention relates to a system comprising a unified identity management system ( 2 ) for the users ( 3 ) within a certain area on which it is centered intended to create a unified identity means ( 23 ) with which the user one and the same account employs to make themselves known, and this to authenticate for various applications based on different application containers ( 63 ). For instance, users ( 3 ) access to multiple applications using 1 bill. The authentication process implements a two- factor authentication is based on a knowledge and possession factor, with the use of specific codes, and a two-stage mechanism to achieve a user experience, which is remarkable in that the authentication mechanism is provided with mobile detection means for detecting whether there are 2 copies of the same mobile registration active which action to take if this is the case. The user experience comprises two main steps: scanning a QR tag and the attachment of the context to provide by insertion of a PIN code.

Description:
FIELD OF THE INVENTION 
       [0001]    The present invention relates to an “Internet” system that is based on an apparatus for providing authenticated access to the Internet-supported services and applications. 
       BACKGROUND OF THE INVENTION 
       [0002]    The breakthrough of the Internet in everyday life has made this a lot easier with the wide range of applications that are now available therewith offering up to a true revolution that have fundamentally changed many customs and habits. Due to the ever growing capabilities and applications that were opened this including some originally freely accessible, were laid gradually restrict which user was asked to register in order to have an access to the desired web services. With many web services having become of daily use, the identification problem became almost unmanageable, given the ever increasing number of user names and passwords for each Web service on each occasion to be remembered and therefore kept separately by the user. This whole identification process soon turned into a hopeless task. Regular web service users had to go through cumbersome procedures to retrieve forgotten login data indeed, or even to create a new account, even if in the meantime a different email address was used by the user, for those who use multiple email addresses, depending on the circle in which he is engaged. 
         [0003]    To remedy this, his credentials can be stored on the computer, but this is only when the user logs on that one device. However, this is not always possible, such as when the user must have access to its desired web service via another computer device, when he is in a different environment. Moreover, a further disadvantage is that the more the user stores, the easier it is for hackers to hijack all that personal information. So this clearly states a security problem that may become critical for the regular user. This therefore creates a true identity jungle, with the aim here is to prune them thoroughly. 
         [0004]    It is well known that conditions wherein a user is in possession of a multiplicity of passwords in order to gain access to a wide variety of websites cause a problem for the user: it becomes somewhat difficult for the user after a while to remember the passwords properly in order for them to be used correctly with regard to a required website. To remedy this, a number of management systems have been developed which provide access to a multiplicity of computers via the Internet by means of one single authentication process. 
       STATE OF THE ART 
       [0005]    A system of this type is known from WO 2009/018564 of RITARI. A single-sign-on user account known as SSO is disclosed herein, as well as a set of websites with protected access which are linked to the SSO user account, and various user identification IDs and password combinations that are linked with the set of access-protected websites. A computer program which is installed on a local computer is configured to enter in advance the so called log-in and password intended for the access-protected websites. 
         [0006]    A further system is also disclosed in WO 2008/024454, in which a trusted platform module referred to as TPN is described, which cooperates with a so-called PROXY SSO unit and with access applications to the web to generate, store and search for passwords in so-called SSO credentials. The same problem is again raised herein that the user is faced to a constantly growing number of passwords every time he wishes to get access to a new website or wishes to re-activate one. 
         [0007]    With the constant increase in electronic transactions and all kinds of Internet-related operations, the protected use of a suitable identification during the operations on the Internet has become a critical problem that resulted in the setting up of Internet models for the identification and management of the user, who is normally registered with a well-defined username and password linked to a specific domain, with the aim of hindering theft or even any unauthorized use of the identification by a third party from site to site. Models of this type, referred to here as application-oriented identity models, are characterised by a strong support for domain management, but nevertheless reveal scaling and flexibility limitations as soon as they are faced with more extensive identity requirements of Internet scenarios. 
         [0008]    Known authentication systems tend to be rather oriented on an application basis, having the disadvantage that they entail severe limitations for both users and agents or service providers of the intended applications. The latter remain locked into one authentication method or technology to which they are restricted indeed. Furthermore, they have an increasing total cost of ownership (TCO) in facilities, for maintaining a helpdesk and the like. The latter also have to contend with the quality of the user data, such as problems of double use, false data, or even data that are no longer current. In addition, they have little or even no mutual exchange at all among the applications, neither cross-marketing nor cross-costing known as TCO. Furthermore, they must provide support for privacy conformity. 
         [0009]    As far as the users are concerned, they are somehow forced to use specific authentication means dedicated to the application. Furthermore, they experience difficulties in maintaining their credentials. They are similarly unable to enjoy multiple reciprocal authentication/application interaction. Finally, they reveal an increasing concern relating to the control and management of their identity, their credentials and their privacy. 
       THE AIM OF THE INVENTION 
       [0010]    The object of the present invention is likewise to find a solution to the aforementioned drawbacks and problems, but in a more sophisticated manner that is based on an innovative combination of a number of elements, resulting in a more powerful system thanks to which highly practical and inventive applications using the possibilities of the Internet are created thanks to a user-oriented identity management system. 
       SUMMARY OF THE INVENTION 
       [0011]    According to the present invention, a system is thus proposed as defined in the attached main claim, wherein according to a main embodiment, the mobile authentication method proposed with the present invention implements a 2-factor authentication that is based on both a knowledge factor and possession factor. It uses QR codes and a 2-phase commit sequence to create a secure, stable and smooth user experience. The authentication process can be extended to confirm and configure additional items, such as privacy settings, terms and conditions, and payments. 
         [0012]    A first step in developing a solution to remedy the abovementioned problems is to make use of a mobile device, such as, in particular, a so-called smart phone or a tablet, which thereby serves as a key to the desired web services and web sites that the user wants to apply. Mobile devices are everywhere indeed, and we carry them around wherever we go. This makes mobile devices prime candidates for making them part of a 2 factor authentication mechanism, since the user doesn&#39;t have to carry an additional device in that case. 
         [0013]    A mobile device also has a keyboard and display that might be separated from the display and keyboard being used to run the main application. The separated display can show a context about what should be happening on the main display. It generates trust by asserting that the main display really shows what is going on, and is thus not a fraudulent application. 
         [0014]    The separated keyboard allows for a secure entry of the possession factor. Users don&#39;t have to use the keyboard of the other, possibly not trusted device on which the main application runs. 
         [0015]    The current-generation devices are also provided with a good camera, suited for fast QR scanning and often have additionally an always-on Internet connection. Both can be used to create a real smooth and secure user experience. The QR code scanning allows for quick and error-free synchronization of the main application and the mobile application. 
         [0016]    In other 2-factor authentication methods, the possession factor is often implemented using some kind of secure element, like a smart card, which can only be unlocked by the knowledge factor, often a PIN code. The linked mobile authentication system according to the invention implements a 2-factor authentication. It is based on both a knowledge factor and a possession factor. It uses QR codes and a 2-phase commit mechanism so as to generate a secure, stable and fluent users experience. In contrast, the possession factor in the mobile authentication system according to the invention is implemented entirely in software as secure elements are not widely available on the current mobile devices. 
         [0017]    A secure element cannot be copied within reasonable and payable limits. In contrast, the possession factor according to the invention, which is based on data and code in memory, can be copied by malicious code running on the mobile device or by insecure backup practices. To counter this loss of protection, the mobile authentication mechanism according to the invention is built up such that it is able to detect if 2 copies of the same registered mobile device are being used and take appropriate action if this should be the case. 
         [0018]    A first advantage of this invention thus consists of the far-reaching simplification in the use of the Internet and web services thus available, thanks to the elimination of the chaotic multiplicity of passwords, and all kinds of codes, which has now become totally out of control, in that their number could finally be reduced to a single binomial or couple, which is much easier to remember by the user of course. This is just the direct result of the remarkable structure of the system according to the invention, wherein it is the user of the software who is placed in the center of the system instead of the software application that he wants to use. 
         [0019]    A further significant advantage of the invention consists in the enhanced security of the system, particularly against hackers who get less chance to parasitize the large multiplicity of personal information that would otherwise be inserted in each case as indicated above. This system also works quite simply as indicated below. The user comes to a website that uses the system, wherein the user may scan a QR code. Then, the user enters his PIN on his mobile device and he is thus submitted. It&#39;s that simple. The user is also able to order products and/or pay with the same ease. 
         [0020]    The user decides what information he wants to share with any application or website. This link system according to the invention can also make a link in a remarkable way with the data on the electronic identity (eID), which is useful for government applications. The system then remembers which data may be displayed to which application. If something changes on the user&#39;s personal information, such as a new address after a move, this is adjusted by itself everywhere. 
         [0021]    Thanks to this mobile solution, the user recovers control over his own personal information, which is a decisive factor in the enhanced security of the system of the invention against the known system. 
         [0022]    The app makes it also possible that the applications that the user is using, exchange their own information with each other. This allows them to set up joint commercial actions, such as newspapers giving their subscribers discount on products from partner companies. It is true that more and more companies in a privileged way to collaborate with other companies of their choice. Now, this invention provides an excellent opportunity to support this privileged partnership with manageable tools. 
         [0023]    Furthermore, it is emphasized that the system is a neutral platform, in the meaning that it does not depend on a Telecom operator or a financial operator of the bank type, or any other operator or sponsor. 
         [0024]    Moreover, the data are not stored on the mobile device of type smart-phone itself, allowing the user not to lose his whole identity in case of loss or theft of his mobile device. All data are thus secured, stored in a so-called cloud on servers that are hosted by the government in a secure way under the exclusion of their own mobile device that the user used during the authentication process or for the use thereof. 
         [0025]    A further aspect of this invention consists in that it is perfectly susceptible to an efficient expansion of its potentialities. Indeed, in order to further spread out the link system according to the invention, a range of useful apps that make use of it is developed, still in the context of this invention as it were by a kind of nest structure. 
         [0026]    An example thereof consists of the known app called i Wish, which allows to set up wish lists of interesting products. This works by scanning in the bar code of a particular product such as a book, allowing this to be added to the virtual wish list of the user. In an analogous manner, a similar app around wines is in development, and further a payment application as well. 
         [0027]    Still in the context of the pursuit of a still further increasing development and dissemination of the system, other key players may be involved in a partnership as well. 
         [0028]    It is known that in the increasingly crowded digital world, which the web sub-world also belongs to, cybercrime still continues to grow and this exponentially. The worldwide publicity surrounding recent spying scandals resulted in that everyone is now really aware that one must take the necessary organizational and technical measures around information protection. As a matter of fact, the present invention provides a useful contribution to this problem by significantly improving the security of personal data by making it less exposed to the hijacker work of hackers. The aim is clearly to increase digital security in an efficient attempt to prevent an organization from being hit hard by cybercrime. An effective way to get prepared against cyber attacks, consists of the use of the link system according to the invention, which is in fact a simplified form of cyber security management CSM which involves more than the traditional securing of information as known from the prior art. 
         [0029]    In short, thanks to the system proposed by the invention, everything can be accomplished through one single application run that manages all the users identity, including both sign up, register, buy, pay, etc. 
         [0030]    It is specific to the system according to the invention that it is the user herein who is central, and not the software application that the user wishes to use, in contrast with known systems. Those who have installed the application currently designated by its common abbreviation app, is able to manage himself the exchange of people&#39;s data across various applications and platforms. The app is based on the principle of scanning and pins. 
         [0031]    As an extension, during the authentication process the mobile client may according to the invention also ask for confirmation for other items, such as confirming and configuring the privacy settings of an account, accepting terms and conditions, or completing a payment by selecting payment credentials. By doing so the user not only proves who he/she is, but at the same time complies with all other requirements to get access to the protected resource. 
         [0032]    This invention also relates to a device intended to carry out the method concerned as set out above, comprising the basic embodiment to carry out the linked method. With respect to the user experience, it consists of 2, optionally 3, main steps: 
         [0033]    1. Scan a QR tag 
         [0034]    2. Confirm the context by entering a PIN code 
         [0035]    3. Optionally, confirm or configure additional items 
         [0036]    2.1 Registration 
         [0037]    The process in which a user attaches a mobile device to his user account is called the “registration” process. 
         [0038]    1. The user is authenticated or created by the system through some other trusted process 
         [0039]    2. The user installs the linkID mobile authentication application on his mobile device 
         [0040]    3. The system presents a QR code to the user 
         [0041]    4. The user scans the QR code 
         [0042]    5. The user verifies the context on display on his mobile device 
         [0043]    6. The user chooses and confirms his PIN code 
         [0044]    7. The user confirms or configures additional items 
         [0045]    8. The system registers the mobile device to the user account. 
         [0046]    2.2 Authentication 
         [0047]    In the authentication process the system tries to identify and authenticate a person who tries to access a protected resource. 
         [0048]    1. The user tries to access or use a protected resource 
         [0049]    2. The system presents a QR code to the unknown user 
         [0050]    3. The user scans the QR code 
         [0051]    4. The user verifies the context on the display of his mobile device 
         [0052]    5. The user enters his PIN code 
         [0053]    6. The user confirms or configures additional items 
         [0054]    7. The system grants the now known user access to the protected resource. 
         [0055]    3 Algorithm 
         [0056]    The solution according to the invention consists of a mobile application and a server application. The user holds the mobile device with the mobile application installed and is at the same time in contact with the server application through another display (like a browser for example). 
         [0057]    The mobile application and the server both carry a persistent state. These states change through interaction between mobile application and server application. The sections below describe these interactions and state changes. 
         [0058]    3.1 Persistent State 
         [0059]    The mobile application state is quite simple. At any time it holds two items: 
         [0060]    RegistrationID This is a UUID which is created during the registration process. It is the link between a registered mobile device and a user account on the server application. 
         [0061]    OTP This is a UUID which serves as a One-Time-Password to authenticate this mobile device to the server application. It can only be used once. 
         [0062]    The server application state consists of registration records and session records. The registration record holds: 
         [0063]    RegistrationID This references a registered mobile device (see mobile application state). 
         [0064]    PIN This is a 4 digit number. It is chosen by the user at registration time. 
         [0065]    OTP1 This is a first candidate OTP as possibly stored in the mobile application. 
         [0066]    OTP2 This is a second candidate OTP as possibly stored in the mobile application. 
         [0067]    Counter This is a value that counts the number of consecutive failed logins with a wrong PIN code. 
         [0068]    Blocked This indicates if this registration is blocked and thus cannot be used to authenticate. 
         [0069]    Activated This field indicates if this registration has been completed. 
         [0070]    Device name This is a human readable identifier of the device for management purposes. 
         [0071]    Current session This is the session ID of the current authentication or registration session for this registration record. 
         [0072]    The session records of the server application hold: 
         [0073]    SessionID This is a reference to the session used during client server communication and in the registration record&#39;s current session. 
         [0074]    Status This field tells if this session was successfully authenticated. 
         [0075]    Start date This tells when the session was started. This field is used to expire old sessions. 
         [0076]    RegistrationID This links this session to a specific registration record. 
         [0077]    The registration starts out with a user which is authenticated by the server application using any sufficiently trusted means. This authentication allows the user to start the mobile registration process on the server application. The following sections show in order what happens on client and server side.  FIG. 1  shows a diagram of the complete registration process. 
         [0078]    3.2.1 Fetching Authentication/Registration Context 
         [0079]    The context is a string that will be displayed after scanning the QR so the user can verify that the tag he just scanned indeed relates to what he is seeing on the main screen, the browser for example. It can also optionally contain the logo of the application the user is authenticating for. This context is fetched by the client right after the QR code is parsed successfully. The sessionID from the OR code is used to retrieve the context from the server. 
         [0080]    3.2.2 Generate a QR 
         [0081]    The server generates a QR code. This OR code is an encoded url which is defined as: 
         [0000]      URL=&lt;urlhandler&gt;://reg/&lt;version&gt;/&lt;SessionID&gt; 
         [0000]      QR=encode(URL) 
         [0082]    The urlhandler is a string which makes that this URL will be opened by the mobile client application if the QR were to be scanned by a generic QR scanning application. 
         [0083]    The literal reg string tells the mobile client to enter the registration procedure instead of an authentication procedure. 
         [0084]    The version indicates the version of the authentication protocol so the client can react appropriately if a QR of an unsupported protocol is scanned. 
         [0085]    The Session ID is a random number, length 6 in base 62 encoding, used for retrieving the context of this registration. 
         [0086]    The server side state is changed by adding a session in the session records. The session record looks like this: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
                   
               
             
             
               
                   
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt;current time&gt; 
                 &lt;RegID&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0087]    At the same time the server enters a record in its registration table: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP′ 
                 counter  
                 blocked  
                 activated  
                 device name  
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 — 
                 — 
                 — 
                 0 
                 NO 
                 NO 
                 — 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0088]    The SessionID is a type 4 UUID. 
         [0089]    The QR tag is now shown to the user within the previously authenticated context. 
         [0090]    3.2.3 Submit Registration Data 
         [0091]    The user&#39;s mobile client scans the QR, decodes and parses the URL. Alternatively, the URL can be scanned by a generic QR scanning application or, if displayed in a web page, it can be clicked by the user. The specific URL handler in the QR code will launch the mobile authentication application according to the invention. 
         [0092]    The mobile client extracts the sessionID from the URL and uses it to fetch the context that will be displayed to the user later on. The mobile client then connects to the server on a hardcoded SSL protected URL and submits the sessionID. The server returns the context message and an optional application logo to present to the user. 
         [0093]    Because of the reg string literal in the URL, the mobile client enters the registration procedure. The mobile client presents the context message to the user and prompts the user to choose and confirm a reproducible knowledge factor, mostly a PIN code. 
         [0094]    The mobile, again connecting to the same server within the same session, submits: chosen PIN and a human readable identifier of the device. 
         [0095]    The server checks if the session is still valid and the associated client is not yet activated. If good the server checks the pin format (length==4). 
         [0096]    If all is good, an OTP is created (UUID) and stored in the registration record and the OTP and registration ID is returned to the client. The PIN code is also stored in the registration record. The registration record looks like this: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP′ 
                 counter 
                 blocked  
                 activated  
                 device name  
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 — 
                 0 
                 NO 
                 NO 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0097]    The server responds to the mobile client by sending the OTP, registrationID and a list of optional items to be confirmed or configured. 
         [0098]    Upon reception of the OTP and registration ID the client updates its persistent state: 
         [0000]    
       
         
               
               
               
             
           
               
                   
                   
               
               
                   
                 RegID 
                 OTP 
               
               
                   
                   
               
             
             
               
                   
                 &lt;RegID&gt; 
                 &lt;OTP&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0099]    The client then presents the items to be confirmed and configured to the user and records the user&#39;s input. 
         [0100]    3.2.4 Commit Registration 
         [0101]    The mobile client, still in the same server session, sends a commit message. The commit message contains the recorded answers to the optional items to be confirmed or configured. The server looks up the session and checks if it is not yet expired. If all is good, the server updates the registration record: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                   
               
               
                 RegID  
                 PIN 
                 OTP 
                 OTP′ 
                 counter  
                 blocked  
                 activated 
                 device name  
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 — 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0102]    and the session record: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
                   
               
             
             
               
                   
                 &lt;SessionID&gt; 
                 SUCCESS 
                 &lt;current time&gt; 
                 &lt;RegID&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0103]    The authentication starts out with a user which is not known by the server application. This unknown user starts the mobile authentication process on the server application. The following sections show in order what happens on client and server side.  FIG. 2  shows a sequence diagram of the complete authentication process thereof in said management system of the invention as described more in detail below. 
         [0104]    3.3.1 Generate a QR code 
         [0105]    The server generates a QR code in about same way as it is generated during registration: 
         [0000]      URL=&lt;urlhandler&gt;://auth/&lt;version&gt;/&lt;sessionID&gt; 
         [0000]      QR=encode(URL) 
         [0106]    The sessionID is again used to fetch the context of the authentication in the same way it is done during registration. 
         [0107]    The server side state is changed by adding a session in the session records. The session record looks like this: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
                   
               
             
             
               
                   
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt;current time&gt; 
                 — 
               
               
                   
                   
               
             
          
         
       
     
         [0108]    The QR tag is now shown to the unknown user. 
         [0109]    3.3.2 Submit Authentication Data 
         [0110]    The user&#39;s mobile client scans the QR, decodes and parses the URL. As during the registration the QR can be scanned by a generic QR scanner or the URL can be opened by clicking on the QR tag. Because of the auth literal in the URL the mobile client enters the authentication procedure. 
         [0111]    Using the sessionID from the QR, the client retrieves the context and optional application logo for this authentication by connecting to the server on a hardcoded SSL protected URL. 
         [0112]    The mobile client presents the context message to the user and prompts the user to enter his knowledge factor, most often a PIN code, thereby to confirm. 
         [0113]    The mobile client, in the same server session submits: the RegID, PIN and the OTP where RegID and OTP are obtained from the mobile client&#39;s local persistent state. 
         [0114]    The server checks if the session exists and is still valid. 
         [0115]    The server checks if the registration record (Reg ID) is activated and not blocked. If it is blocked the server aborts the authentication process. 
         [0116]    The server checks if the OTP matches one of the OTP values that are stored in the registration record matching the RegID parameter. If none of the OTP values matches the submitted values the registration record can be marked as blocked. This prevents any future authentication attempts until unblocked by some registration procedure. 
         [0117]    The server also checks if the PIN code matches the PIN code that is stored in the registration record matching the RegID parameter. If the submitted PIN code does not match the PIN code in the server&#39;s persistent state a PIN failure counter can be increased. If the PIN failure counter exceeds a configured threshold the registration record can be marked as blocked. The PIN counter can be reset to zero after every successful authentication attempt. 
         [0118]    If all checks are passed the server generates a new OTP (OTP&#39;) and stores it in the non-matching OTP field of the registration record. The resulting server state for the registration record is: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                   
               
               
                 RegID  
                 PIN 
                 OTP 
                 OTP′ 
                 counter  
                 blocked  
                 activated 
                 device name  
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 &lt;OTP′&gt; 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0119]    and for the session record: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
                   
               
             
             
               
                   
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt;current time&gt; 
                 &lt;RegID&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0120]    The OTP&#39; and the optional items to be confirmed or configured are sent back to the mobile client. 
         [0121]    Upon reception of the OTP&#39; value the client updates its persistent state: 
         [0000]    
       
         
               
               
               
             
           
               
                   
                   
               
               
                   
                 RegID 
                 OTP 
               
               
                   
                   
               
             
             
               
                   
                 &lt;RegID&gt; 
                 &lt;OTP′&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0122]    The client then presents the items to be confirmed and configured to the user and records the user&#39;s input. 
         [0123]    3.3.3 Commit Authentication 
         [0124]    The mobile client now sends a commit call within the same session. The commit message contains the recorded answers to the optional items to be confirmed or configured. The non-matching OTP from the previous call is removed so the server&#39;s persistent state looks like this: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                   
               
               
                 RegID  
                 PIN 
                 OTP 
                 OTP′ 
                 counter 
                 blocked  
                 activated  
                 device name  
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP′&gt; 
                 — 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0125]    Only now the server marks the user server session as authenticated: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
                   
               
             
             
               
                   
                 &lt;SessionID&gt; 
                 SUCCESS 
                 &lt;current time&gt; 
                 &lt;RegID&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0126]    The algorithm is designed as such to have 2 important side-effects. The first side effect is that if the mobile client&#39;s persistent state were to be copied and successfully used subsequently then on a first use of the original client the registration entry would be blocked. This is because if a client successfully authenticates the OTP is changed so a copied client will carry an out-of-date OTP. If a non-matching OTP is sent to the server, the server can block the account. 
         [0127]    A second side effect is that the client can never get out-of-sync with the server because of client-side or network failure. In other words: no matter when or how the client loses contact with the server during authentication, the client will just work -maybe after a client restart—as soon as the problem conditions are resolved. The reason for this is that the OTP is rolled over in a 2 phase commit: the OTP values are only rolled over after the client has stored the new OTP value. 
         [0128]    Further features and particularities of the invention are defined in corresponding appended subclaims. 
         [0129]    Further details are set out more in detail in the description hereinafter which is illustrated by means of the appended drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0130]      FIG. 1  shows a sequence diagram of the registration process in a first embodiment of the system according to the invention; 
           [0131]      FIG. 2  shows a sequence diagram of the authentication process thereof; 
           [0132]      FIG. 3  shows a diagram of the complete registration process in a first main embodiment of the management system of the invention; 
           [0133]      FIG. 4  shows a diagram of the entire authentication process in said basic main embodiment of the management system of the invention; 
           [0134]      FIG. 5  shows a schematic representation of a payment application supported on the link system according to the invention. 
           [0135]      FIG. 6  shows a block diagram of a conventional application-oriented identity model management system from the known prior art. 
           [0136]      FIG. 7  shows a block diagram of a conventional user-oriented identity model according to a basic main embodiment of the management system. 
           [0137]      FIG. 8  shows a block diagram of a variant of an identity model from the prior art. 
           [0138]      FIG. 9  shows a block diagram of a variant of a user-oriented identity model management system. 
           [0139]      FIG. 10  is a schematic presentation of the identity components used in the management system according to the invention. 
           [0140]      FIG. 11  is a schematic presentation of the parties involved in the management system according to the invention. 
           [0141]      FIG. 12  is a flow diagram as a schematic representation of the operation of the management system according to the invention. 
           [0142]      FIG. 13  shows a block diagram of a conventional application-oriented identity model according to a particular application example of the invention. 
           [0143]      FIG. 14  is a schematic presentation of an exemplary embodiment of the method according to the invention. 
           [0144]      FIG. 15  shows a block diagram of an application-oriented identity model according to an additional application example according to the invention. 
       
    
    
     DESCRIPTION 
       [0145]      FIG. 1  shows a sequence diagram for the registration process of the system according to the invention as described below, wherein the invention relates to a mobile authentication system in which the applied users experience consists of two main steps including Scanning a QR tag and confirming the context by entering a PIN code. Optionally, there is confirming or configuring additional items. 
         [0146]    In a main embodiment of the present invention, a process is proposed wherein the user links his mobile device to a users account, which constitutes the registration process. The process in which a user attaches a mobile device to his user account is called the “registration” process. 
         [0147]    The Registration thus includes the following steps: 
         [0148]    the user is authenticated or created by the system through some other trusted process; 
         [0149]    the user installs the linked mobile authentication application on his mobile device; 
         [0150]    the system presents a QR code to the user; 
         [0151]    the user scans the QR code; 
         [0152]    the user verifies the context on display on his mobile device; 
         [0153]    the user chooses and confirms his PIN code; 
         [0154]    the user confirms or configures additional items; 
         [0155]    the system registers the mobile device to the user account. 
         [0156]    As to the subsequent authentication process, the system tries with same to identify and authenticate a person who tries to access a protected resource as follows: 
         [0157]    the user tries to get access or use a protected resource 
         [0158]    the system presents a QR code to the unknown user 
         [0159]    the user scans the QR code 
         [0160]    the user verifies the context on the display of his mobile device 
         [0161]    the user enters his PIN code 
         [0162]    the user confirms or configures additional items 
         [0163]    the system grants the now known user access to the protected resource. 
         [0164]    The solution proposed according to the invention notably supported on an algorithm consists of a mobile application and a server application. The user holds a mobile device with the mobile application installed thereon, and is at the same time in contact with the server application through another display, like a browser on his PC for example. 
         [0165]    The mobile application and the server both carry a persistent state. These states change through interaction between mobile application and server application. The sections below describe these interactions and state changes. 
         [0166]    In said Persistent state, the mobile application state is quite simple. At any time it holds two items: 
         [0167]    the RegistrationID, which is a UUID that is created during the registration process. It is the link between a registered mobile device and a user account on the server application; and 
         [0168]    the OTP, which is a UUID that serves as a One-Time-Password to authenticate this mobile device to the server application. It can only be used once. 
         [0169]    The server application state consists of registration records and session records. The registration record holds the following fields: 
         [0170]    said RegistrationID. This refers to a said registered mobile device; 
         [0171]    a PIN, which is a 4 digit number. It is chosen by the user at registration time; 
         [0172]    OTP1 as first candidate OTP such as possibly stored in the mobile application; 
         [0173]    OTP2 as second candidate OTP such as possibly stored in the mobile application; 
         [0174]    Counter is a value counting the number of consecutive failed logins with a wrong PIN code; 
         [0175]    Blocked indicating if this registration is blocked and can thus not be used to authenticate; 
         [0176]    Activated wherein this field indicates if this registration has been completed; 
         [0177]    Device name which is a human readable identifier of the device for management purposes. This name is displayed during the management of a user account; 
         [0178]    Current session which is the session ID of the current authentication or registration session for this mobile registration record. 
         [0179]    The session records of the server application hold: 
         [0180]    QRhash which is a value that is the so-called hash of the QR tag that was generated for that session; 
         [0181]    SessionID which is a reference to this session used during client/server communication and in the registration record&#39;s current session; 
         [0182]    Status which is a field that tells if this session was successfully authenticated; 
         [0183]    Start date: this tells when the session was started; this field is used to expire old sessions. 
         [0184]    RegistrationID, which links the session to a specific registration record. 
         [0185]    The registration starts out with a user which is yet authenticated by the server application using any sufficiently trusted means. This authentication allows the user to start the mobile registration process on the server application. The following sections show what happens on client and server side.  FIG. 3  shows a diagram of the complete registration process. 
         [0186]    The server generates a QR code. This QR code is an encoded URL which is defined as: 
         [0000]      URL=&lt;urlhandler&gt;://reg/&lt;version&gt;/&lt;RegistrationID&gt;/&lt;context&gt; 
         [0000]      QR=encode(URL). 
         [0187]    The URLhandler is a string which makes that this URL will be opened by the mobile client application according to the invention, if the QR were to be scanned by a generic QR scanning application. 
         [0188]    The literal reg string tells the mobile client to enter the registration procedure instead of an authentication procedure. 
         [0189]    The version indicates the version of the authentication protocol so the client can react appropriately if a QR of an unsupported protocol is scanned. 
         [0190]    The RegistrationID is a random number in the UUID format that will serve as identification of this registered device during the further registration or a later authentication. 
         [0191]    The context is a text that will be displayed after scanning the QR code enabling the user to verify that the tag which he just scanned indeed corresponds to what he currently sees on the main application. 
         [0192]    The server side state is changed by adding a session in the session records, which session record is represented in the following table  1 : 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
               
                 QRhash 
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
               
             
             
               
                 &lt;QRhash&gt; 
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt; current time &gt; 
                 &lt;RegID&gt; 
               
               
                   
               
             
          
         
       
     
         [0193]    At the same time, the server adds a registration as represented in the following table 2 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                 TABLE 2 
               
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP&#39; 
                 Counter  
                 blocked 
                 activated 
                 Device name 
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 — 
                 — 
                 — 
                 0 
                 NO 
                 NO 
                 — 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0194]    wherein QRhash=securehash(URL). 
         [0195]    This securehash function is a so-called hashing function which is known as SHA1. The SessionID is a random UUID. 
         [0196]    The QR tag is now displayed to the user within the previously authenticated context. 
         [0197]      FIG. 3  further shows a diagram of the complete registration process in a management system of the invention, resp.  FIG. 4  a diagram of the complete authentication process. Registration data are submitted as follows: the user&#39;s mobile client scans the QR code, decodes and parses the URL. Alternatively, the URL may be scanned by a generic OR scanning application or, if displayed in a web page, it can be clicked by the user. The specific URL handler in the QR code will launch the mobile authentication application according to the invention. 
         [0198]    Because of the reg string literal in the URL, the mobile client enters the registration procedure. The mobile client presents the context message to the user and prompts the user to choose and confirm a reproducible knowledge factor, mostly a PIN code. 
         [0199]    The mobile client extracts the sessionID from the URL that will serve as identification for this registered device for later contacts with the server. 
         [0200]    The mobile application then connects to the server on a fixed SSL-secured URL, and sends the following data: RegID, chosen PIN and a human readable identifier of the device. 
         [0201]    The server checks if the Registration (RegID) exists, is not yet activated and if the current session is still valid. If all is good, an OTP is created (a random number in UUID format) and stored in the registration record. The PIN code is also stored in the registration record as represented in the following table 3: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                 TABLE 3 
               
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP′ 
                 Counter 
                 blocked 
                 activated 
                 Device name 
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 — 
                 0 
                 NO 
                 NO 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0202]    The server responds to the mobile client by sending the OTP thereto. Upon reception of the OTP the client updates its persistent state as represented in the following table 4: 
         [0000]    
       
         
               
               
               
             
           
               
                   
                 TABLE 4 
               
               
                   
                   
               
               
                   
                 RegID 
                 OTP 
               
               
                   
                   
               
             
             
               
                   
                 &lt;RegID&gt; 
                 &lt;OTP&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0203]    The commit of the registration happens as follows: the mobile client, still in the same server session, now sends the QRhash and the RegID as a commit message to the server. The server validates by looking up if this hash matches the hash of the current session of the registration. The server also checks if the session is not yet expired. If all is good, the server updates the registration record as represented in the following table 5: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                 TABLE 5 
               
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP′ 
                 Counter 
                 blocked 
                 activated  
                 Device name 
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 — 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0204]    and also the session record as represented in the following table 6: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 6 
               
               
                   
               
               
                 QRhash 
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
               
             
             
               
                 &lt;QRhash&gt; 
                 &lt;SessionID&gt; 
                 SUCCESS 
                 &lt; current time &gt; 
                 &lt;RegID&gt; 
               
               
                   
               
             
          
         
       
     
         [0205]    With regard to the authentication, it begins with a user who is unknown from the server application. This unknown user starts the authentication process on the server. The following sections show what happens successively in the mobile application and the server application.  FIG. 4  shows a diagram of the complete authentication process. 
         [0206]    The server generates a QR code in fairly the same way as during the registration: 
         [0000]      URL=&lt;urlhandler&gt;://auth/&lt;versie&gt;/&lt;seed&gt;/&lt;context&gt; 
         [0000]      QR=encode(URL). 
         [0207]    The seed is a random string to make the URL and QR different for each session. the server state is adapted by adding a session. The session is as represented in the following table  7 : 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 7 
               
               
                   
               
               
                 QRhash 
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
               
             
             
               
                 &lt;QRhash&gt; 
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt; current time &gt; 
                 — 
               
               
                   
               
             
          
         
       
     
         [0208]    wherein QRhash is generated in the same way as during the registration. The QR tag is now shown to the unknown user. 
         [0209]    Submitting authentication data then takes place as follows: 
         [0210]    the user&#39;s mobile client scans the QR code, decodes and parses the URL. As during the registration, the QR can be scanned by a generic QR scanner or the URL can be opened by clicking on the QR tag. Because of the auth string literal in the URL the mobile client enters the authentication procedure. The mobile client presents the context message to the user and prompts the user to enter his knowledge factor, mostly a PIN code. 
         [0211]    The mobile client then connects with the server session on a hardcoded SSL protected URL and submits: the RegID, PIN and the OTP, where RegID and OTP are obtained from the mobile client&#39;s local persistent state. 
         [0212]    The server checks if the session (QRhash) exists and is still valid. 
         [0213]    The server checks if the registration record (RegID) is activated and not blocked. If it is blocked, the server aborts the authentication process; the server checks if the OTP matches one of the OTP values that are stored in the registration record matching the RegID parameter. If none of the OTP values matches the submitted value, the registration record is marked as blocked. This prevents any future authentication attempts until unblocked by some sufficiently trustful registration procedure. 
         [0214]      FIG. 2  shows the sequence diagram for the authentication process. 
         [0215]    The server also checks if the PIN code matches the PIN code that is stored in the registration record matching the RegID parameter. If the submitted PIN code does not match the PIN code in the server&#39;s persistent state, a PIN failure counter is increased by the server. If the PIN failure counter exceeds a configured threshold, the registration record is marked as blocked. The PIN counter is reset to zero after every successful authentication attempt. 
         [0216]    If all checks are passed, the server generates a new OTP (OTP&#39;) and stores it in the non- matching OTP field of the registration record. The resulting server state for the registration record is then as represented in the following table 8: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                 TABLE 8 
               
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP′ 
                 Counter 
                 blocked 
                 activated 
                 Device name 
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP&gt; 
                 &lt;OTP′&gt; 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0217]    and for the session record as represented in the following table 9: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 9 
               
               
                   
               
               
                 QRhash 
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
               
             
             
               
                 &lt;QRhash&gt; 
                 &lt;SessionID&gt; 
                 IN PROGRESS 
                 &lt; current time &gt; 
                 &lt;RegID&gt; 
               
               
                   
               
             
          
         
       
     
         [0218]    The OTP&#39; and SessionID values are sent back to the mobile client. 
         [0219]    Upon reception of the OTP&#39; and SessionID values, the client updates its persistent state as represented in the following table 10: 
         [0000]    
       
         
               
               
               
             
           
               
                   
                 TABLE 10 
               
               
                   
                   
               
               
                   
                 RegID 
                 OTP 
               
               
                   
                   
               
             
             
               
                   
                 &lt;RegID&gt; 
                 &lt;OTP′&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0220]    The client then presents the items to be confirmed and configured to the user and records the user&#39;s input. 
         [0221]    For sake of authentication committing, the mobile client sends a last commit message to the server within the same session. The non-matching OTP value from the previous interaction is removed. The server&#39;s persistent state looks like it is represented in the following table 11: 
         [0000]    
       
         
               
               
               
               
               
               
               
               
               
             
           
               
                 TABLE 11 
               
               
                   
               
               
                 RegID 
                 PIN 
                 OTP 
                 OTP&#39; 
                 Counter 
                 blocked 
                 activated 
                 Device name 
                 session 
               
               
                   
               
             
             
               
                 &lt;RegID&gt; 
                 &lt;PIN&gt; 
                 &lt;OTP′&gt; 
                 — 
                 0 
                 NO 
                 YES 
                 &lt;name&gt; 
                 &lt;SessionID&gt; 
               
               
                   
               
             
          
         
       
     
         [0222]    Only now the server marks the user server session as authenticated as represented in the following table 12: 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 12 
               
               
                   
               
               
                 QRhash 
                 SessionID 
                 Status 
                 Start 
                 RegID 
               
               
                   
               
             
             
               
                 &lt;QRhash&gt; 
                 &lt;SessionID&gt; 
                 SUCCESS 
                 &lt;current time&gt; 
                 &lt;RegID&gt; 
               
               
                   
               
             
          
         
       
     
         [0223]    The algorithm implemented for the system according to the invention is designed such as to have 2 important side-effects. The first side effect is that if the mobile client&#39;s persistent state were to be copied and successfully used subsequently then on a first next use of the original client the registration entry would be blocked by the server. This is because the original state will contain an OTP that will no longer be on the server and if a client successfully authenticates the OTP which is changed, a copied client will thus carry an out-of-date OTP. If a non-matching OTP is sent to the server, the server blocks registrations for which an invalid OTP is submitted and it can block the account. 
         [0224]    A second side effect is that the mobile client can never get out-of-sync with the server because of client-side or network failure. In other words: no matter when, where or how the client loses contact with the server during authentication, the client will just work again (maybe after a client restart) as soon as the temporary connection problem conditions are resolved. The reason for this is that the OTP is rolled over in a 2 phase commit: the OTP values are only rolled over after the client has stored the new OTP value. 
         [0225]    By way of example, a payment application according to the link system is shown schematically in a user-friendly manner in  FIG. 5 / 10 , in which the link system cloud  99  is centrally displayed, and which can be activated with the user  61  via his mobile device  62 , in this case a mobile phone. 
         [0226]      FIG. 6  and following ones show the system in general according to an embodiment relating to authentication systems that differ from the known systems  1  in that the latter are oriented on an application basis with the disadvantage of entailing severe limitations, both for users  3  and for agents or service providers of the aforementioned applications, as shown in  FIG. 6 . This shows the condition wherein a user  3  possesses one specific identity  13 ,  14 ,  15  for each online application a, b, c, possibly operated by the same owner, wherein the respective specified identities  13 ,  14 ,  15  may also differ in specific cases. Three identity fields  13 ,  14 ,  15  are thus to be considered. 
         [0227]    In contrast, the linked identity management system  2  which is oriented towards the user  3  shown in  FIG. 7  presents none of the aforementioned limitations of the application-oriented models of the management system  1 . Instead, this creates new service possibilities for application owners or operators and offers user-friendly access to more useful applications by the users  3 . 
         [0228]    The management system  2  forms a unified identity management system which is oriented towards the user  3 , and the aim of which consists in creating a unified identity model  23  intended for users within a specific region or industry. This user is therefore able to use the same account to identify himself and authenticate this for different applications a, b, c, wherein these applications can originate from different application owners. This is shown schematically in  FIG. 7  with reference to the schematic representation of the current condition shown in  FIG. 6 . 
         [0229]    In the additional example shown in  FIG. 8 , applications  31  and  32  are operated by the same owner AA, wherein they can share the same identity  35 . Herein, the user  30  has one specific identity  35 ,  36 ,  37  for each online application  31 ,  32 ,  33 ,  34  separately, possibly operated by the same owner AA or BB, wherein the respective specified identities  35 ,  36 ,  37  may differ from one another. In any event, a minimum of 3 identity fields  35 ,  36  and  37  are to be considered with this example. 
         [0230]    However, the user-oriented management means L according to the invention offers a simplification of the existing system by offering a unified identity field  40  that can thus be used for the aforementioned applications  31 ,  32 ,  33 ,  34  simultaneously, which can also be operated by a plurality of aforementioned application owners AA or BB, as shown in  FIG. 7 . 
         [0231]    The main embodiment of the invention can thus be determined as a management system L of the identity fields  40  of a user  3  who is identified by one global unified identity  40  which he must enter in order to gain access to his required applications  31 ,  32 ,  33 ,  34  which are operated by agents AA, BB, which is noteworthy in that this management system  2  is oriented towards the user  3 , wherein the latter can gain access to all of the aforementioned applications  31 ,  32 ,  33 ,  34  which differ from one another, via one single identity field  40  which uniquely identifies the aforementioned user. 
         [0232]    The advantage thereof is clearly that a global unified identity field  40  is obtained thanks to the system  2 . 
         [0233]    Identity components  51 ,  52 ,  53 ,  54  thus arising intervene in the unified identity  40  which is created by this system  2  and comprise four different components which are all connected via the core element L, shown schematically in  FIG. 10 . 
         [0234]    The first component consists of so-called attributes  52 , consisting of pieces of data which have been allocated to the physical person who possesses the identity concerned in his capacity as user  3 , such as name, age, gender, town, etc. A further component consists of subscriptions  51  which determine the applications  31 ,  32 ,  33 ,  34  in which the identity  40  concerned can be used. These accessions  51  form the link between an application and an identity. These similarly control the legal and confidentiality compliance between a user and an application that the latter wishes to orient. 
         [0235]    A further component concerns the authentication means  53  which are intended to be registered and used by a user  3  to authenticate himself. Here, one specific identity  40  may have registered a plurality of authentication means, and examples of this are the username/password pair, an identity card, a conventional credit card, a mobile telephone, etc. 
         [0236]    Finally, there is the historical component  54 , wherein the user  3  can keep track of all actions relating to his identity  40 . 
         [0237]    The management system  2  can guarantee the uniqueness of the user  3  by means of his devices  53 , on the understanding that the core L will not allow a physical device to be used for two different accounts, thereby making the identities in this management system  2  particularly strong. 
         [0238]    Attributes  52  form the substance of the identity  40  of the user  3 , and make the user what he ultimately is. The essence of attributes lies in their repeated use between different applications  31 ,  32 ,  33 ,  34 , wherein the user can check at any time which application provides access to which attribute. Attributes  52  have determined data types, such as e.g. Boolean or string characters, and can be linked to single or even multiple values. The attributes can also be combined to form new data types, e.g. a street combined with a city together form the address. It should be noted that attributes are not hard-coded but can be added by the operator at the request of its customers, i.e. the application owners. 
         [0239]    In the general structure of the system  2 , there is the noteworthy core element L thereof, which assumes a central position therein, wherein it communicates with different parties which are determined as follows, as shown in  FIG. 11 . End users  3  are formed by physical persons who have an account and who wish to use applications  61  which are linked to the core L of the management system  2 . The end users interact with the system core L by means of an interface  62 , e.g. a web interface, wherein integration with non-web systems is also possible. 
         [0240]    A further party is formed by the applications  61 , which are intended to perform functions consisting in specific services which are offered to the aforementioned end users  3 . In order to be able to identify their users  3 , they then use the aforementioned core L. In order to communicate with the core L, they use web services  62 . 
         [0241]    There are also application owners or operators  63  who own and operate the aforementioned applications. They are the actual customers of a core operator  64 . They enter into interaction with the core L by means of a web application which provides statistics and accounting relating to the applications which they own. 
         [0242]    Furthermore, there are also the operators  65  who manage the system software in so-called data centres and who sell the various system functions and services to the aforementioned application owners  63 . Here, they work together with the aforementioned application owners to have their applications  61  connected to the management system L. 
         [0243]    Finally, there are also the device suppliers who supply the necessary authentication means  53  to the users  3 . They can have their device  53  carried by the management system  2 , which is understood to mean that this is formed by the so-called LinkID system. 
         [0244]    Attribute values can be obtained by the user himself  3 , by an application  61 , by a device  53 , a remote system such as a database, a web service, LDAP, or also from a calculation of other attributes. An attribute can be read in by an application  61  if the following conditions are met, namely that the operator gives the application access to the attribute, the user  3  gives permission to the application  61  to use the attribute and finally that the attribute has a value. A further advantageous characteristic of attributes is that they can be designated as being anonymous. In this case, applications  61  cannot read in the specific value of an attribute from a specific user, but they are nevertheless able to receive statistics relating thereto. Thus, if a location was designated as anonymous for an application e.g., this application cannot read in the location of a specific person X, but it can nevertheless receive a statistic of the type “20 % of your users live in a town Y”, which forms particularly useful information for the application owner  63 , and is then also a trump card of this management system L. 
         [0245]    Different functions can be performed here by the system  2  in respect of the applications, namely first an authentication function: if an application calls on this function, the user is authenticated by the system  2  in the use of one of his configured devices  53 . Provided that this runs successfully, the application is notified and will then give access to the user  3 . 
         [0246]    Furthermore, there is the attribute function: an application can retrieve the attributes  52  of the user and use the values thereof in its commercial operations. Attributes can only be read in on condition that the user  3  has given his express permission to this effect. 
         [0247]    There is also the data function, wherein an application  31  can push attributes  52  to the profile of the user  3 . In this case, these attributes can be used by other applications  32 ,  33 ,  34 , provided that this is permitted by the user and the supplying application. 
         [0248]    For the end user, the advantages in the use of the management system  2  lie in a noteworthy strengthening of his accounts, the functions and the attributes and also a stronger control over his identity  40 , seen from management, confidentiality and security perspectives. 
         [0249]    For this application, more specifically the owner  63  thereof, the advantages lie primarily in device autonomy, stronger identities with higher quality profiles, simplified registration and user management, simplified legal and confidentiality compliance. This furthermore also permits a new use of the partner of the user of the application. Moreover, it also permits a lowering of the access threshold to the application. Furthermore, it underpins marketing schemes by the reading-in and provision of attributes to or from partner applications. 
         [0250]    In the authentication process, an authentication flow  71  takes place which propagates according to arrow direction F via an authentication path visualized in  FIG. 12  in the form of an identification pipeline  70 . In order to be authenticated, the user  3  moves through various stages of the flow  71 , wherein each stage provides specific guarantees to the agent or customer application. The successive steps of the authentication process are explained below. 
         [0251]    In a first step referred to as the device selection A, the user  3  is prompted to select the authentication means  53  that he wishes to use for authentication purposes. In this way, the user can select this means  53  which he has to hand or which suits him best at that time and at that place. However, this means selection A can be restricted at the request of the application, for example only stronger authentication means for high-value transactions. 
         [0252]    The authentication then takes place B, as required by the relevant device  53 . 
         [0253]    In the following step, which is the one of the agreements C, a general legal conformity is confirmed by asking the user  3  to express his agreement with regard to a user agreement C. This step occurs only if a new version of the user agreement is available. 
         [0254]    Furthermore, the management system  2  asks the user  3  whether he is in agreement with the relevant application  61  using specific attributes  52 . This is therefore the confirmation step D of the attributes which are determined by the aforementioned operator  65 . The core L asks this once only, so that in subsequent authentication events, this step D will not occur, except if the application attribute requirements have since changed. 
         [0255]    Finally, there is the comparison step E, where the core L compares the user attributes with the attributes retrieved by the relevant application  61 . Some attributes can be designated as requested. However, in the event that the user is not provided with these attributes, the management system L will first ask the user  3  to obtain the attributes. 
         [0256]    The authentication flow  70  described above can be incorporated into various protocols. As far as the authentication means  53  are concerned, some of these are supported in a dynamic manner by the management system  2 . These elements  53  are not hard-coded in the management system  2 , so that new authentication elements  53  can be added without the need for new software for the management system  2 . For each authentication element  53 , the management system  2  knows the location of the registration/update/deletion and authentication workflow  70 . These workflows are jointly determined by the management system operator  65  and the device provider  64 . These workflows  70  differ for each device  53 , given that there are differences in both the technology and the delivery procedures. 
         [0257]    The software that implements these workflows can be accommodated and processed by the management system operator  65  or by the equipment owner  64 . This choice depends on a number of factors, such as security, costs and experience. In any case, the management system can use workflows from remote elements, which can be developed and maintained separately. 
         [0258]    For a number of strongly regulated authentication elements, the operator  65  of the management system  2  does not require much cooperation from the element provider. A good example of this is the large PKI-based electronic identity card. 
         [0259]    A number of technical choices are set out below in relation to tools and means that are used, which should not be regarded as limiting in the context of this application however. The management system  2  designated as LinkID is independent from both the operating system and the database, and it uses only open standards, in order to ensure maximum compatibility with the customer applications. 
         [0260]    The management system according to the invention is built on an extremely flexible architecture in order to make it technology-independent. All technology-dependent components are plug-ins and can be extended. The following features have been developed in this way and can thus be extended: among the authentication means  53 , mobile authentication, EMV cards, OTP tokens, etc. As far as authentication protocols are concerned: Cardspace, OpenID, windows live ID protocol, Shibboleth. 
         [0261]    In an advantageous manner, the implementation of a signature service is similarly provided. If this service is used, an application  61  can ask the management system  2  to arrange for a user to sign a specific document or transaction with the use of his authentication elements  53 . In this way, an application can use the management system  2  to strongly seal transactions in a technology-independent manner in perfect accordance with legal conformity. 
         [0262]    If different LinkID instances are in production in different regions or industries, possibly being processed by different operators, the operating system  2  will have the facility to allow users  3  to move between these instances. Users who are connected to one management system  2  will be able to use applications that are connected to a different LinkID instance. 
         [0263]    An overview of the advantages produced by the LinkID management system  2  is presented below. Thanks to this system, the agent or service provider can do more with the users. In this respect, application providers have a requirement for management systems that involve a larger number of users, with more applications and ultimately more revenues. This management system offers a reliable authentication which covers all the requirements, by offering their users an identification management in which they can trust. 
         [0264]    This is done by acquiring deeper and broader levels of commitment from its user base, by allowing trust and control to be increased. Membership levels with simple management and transactions in one click intended for a migration to premium services also come into consideration here. Moreover, traffic and use increase, given that users find it more convenient and more productive to manage their use by means of one single ID which they control more effectively and can trust. 
         [0265]    An example of a system set-up is described on the basis of the relevant  FIG. 13 , in which an identity service is presented, with one single identity number  80  which is confirmed by the system  2  according to the invention. This system service extends the internal identity management of the service provider to external partners. This service allows users to move freely between the agent or service provider and its partner applications, and furthermore also simply allows sharing of personal and marketing data. 
         [0266]    This identity number service eliminates the need among specific users to take advantage of their partnership between service providers. This similarly allows exposure of service provider applications and customer data to external parties. 
         [0267]    Application examples which can provide the sharing of the advantages or profits are known as co-branded services from the physical world, or the possibility for the sharing of payment or trusted systems between applications. 
         [0268]    The system offers a number of important characteristics in cases where the customer is located outside the service provider area, namely in the domain of user convenience; no further need to arrange re-registration in the domain of confidentiality control, the customer can decide which data can be read in by external parties in the domain of standard interfaces for partner applications; and furthermore, in the domain of simple and reliable authentication, wherein the customer can choose from the suitable and reliable devices without the slightest integration problem for the partner application. Existing external authentication means  53 , such as elDs already used or pairs of usernames/passwords  82  can be re-used  83 . 
         [0269]    Said identity system thus becomes the integration point for external applications as clearly presented in  FIG. 13 , where this identity number system  80  assumes a central position in the graphic, around which everything revolves, and thus acts as a type of central processing unit for the above. However, it could even be used for new or existing applications. 
         [0270]    A strong authentication is then to be regarded as the advantage of the system according to the invention, wherein the access to an account of a management system  2  can be protected with the use of a plurality of authentication means  53  which differ in complexity and reliability. This offers a large number of advantages. 
         [0271]    First of all, an online application may include a strong authentication if needed, for example if it is based on a transaction value. However, if a strong protection is not strictly necessary, simpler authentication methods can be used, in other words the reliability level of the authentication means  53  can be adapted to the required application  31 ,  32 , . . . ;  61 . 
         [0272]    Furthermore, users  3  can use an authentication method as a back-up for a further method: if one method is unavailable, the user can fall back on a different method thanks to this characteristic. 
         [0273]    Moreover, the authentication system L is completely deployable; it can at any rate support any proposed authentication mechanism and can also offer this as an authentication method to its account holders. 
         [0274]    Authentication methods are e.g. a mobile telephone, wherein different technologies are available, notably SMS, software on the telephone or PKI on the SIM card; with password  82 , wherein the management system  2  similarly supports normal username/password combinations, either as a stand-alone database or linked to an existing user base; furthermore, also an electronic identity card, wherein the management system  2  already supports the PKI electronic identity cards, i.e. presently the Belgian electronic identity card; and finally also a digipass  86 , wherein the management system  2  already supports implemented digipass solutions. This digipass means  86  is available to users to certify all applications or a restricted number of applications, according to the policy adopted here by the operator of the base installed with digipass. 
         [0275]    For the user registration, customers can obtain an account in two ways. They can either create their own account themselves, or an account is automatically converted or mirrored from an existing identity system. 
         [0276]    In both cases, the account of the management system  2  will grow with time. The customer, agent or service provider and its partners will add data to the account. New authentication means  53  are incorporated along the way as they become available or are required for a specific application  61 . 
         [0277]    The end result is then a particularly rich account that can be used in any given commercial condition as long as all information relating to the user  3  is present and he can be identified to the extent that the new application requires. The account can then be extended into new applications without delay due to technical interfacing issues or user registration obstacles. 
         [0278]    In short, the management system according to the invention is an appropriate means of capturing the information value of the customer file and making efficient re-use thereof. 
         [0279]    An additional extension of the functionality of the LinkID management system according to the invention referred to as L is explained below, consisting in the development of an additional contrivance referred to as the “red button”. This essentially involves an activation means of a specific application in a specially designed format that is described below in connection with an application example in a TV broadcast. 
         [0280]    In this format, a LinkID application is installed on a mobile terminal of the user, which may be any given mobile device that is capable of running third-party applications. Examples of this are an iPhone, an iPad, Android devices, etc. 
         [0281]    The aforementioned application has a distinguishing logo and brand, which identifies an identity provider. In the TV world, the latter may be a broadcaster, a cable network, a media group, or an advertiser, etc. If this logo appears in a LinkID or “L”-activated TV programme or advert, the user can activate this logo by pressing it on his mobile terminal. 
         [0282]    The L application starts up and downloads interactive content relating to this advert or TV programme from an L server, which then decides which content to broadcast, based on the time when the interactive content was requested. 
         [0283]    This content comprises normal multimedia information material, but also actions that the user can undertake. If required, a part of these actions and content can be exclusive and specific to the user of the L application and could, in other words, not be obtained by, for example, surfing on the broadcaster, the television station or the advertising website. 
         [0284]    A typical example of exclusive action consists in a price reduction which is offered to the viewer. The exclusive content and privileges can be immediately used via the L mobile application, or can also be used later, similarly via the L mobile application, or via a website, or also a point of sale (POS). 
         [0285]    In order to install the aforementioned mobile application, the relevant L format requires the installation of a telephone application on the telephone terminal of the user. 
         [0286]    A marketing campaign must convince the users to download the application free of charge from their mobile shop. 
         [0287]    When the LinkID application is started up for the first time, the user can create an account, including a chosen account name, and may optionally choose a PIN code, again via the mobile L application. The mobile device is connected to the account that has just been created, so that any action that is carried out via the mobile terminal is charged. 
         [0288]    The synchronization of the content takes place as follows: if the user presses on the aforementioned logo on his mobile terminal, specific content for the user is displayed, given that the application owner must be aware of the content that appears when a user presses on the aforementioned logo on his mobile terminal, the Link-ID application must be synchronized with the TV content. Given that collaboration takes place between the producers of the TV program or advertisers and the management system  2 , it is known roughly when these begin. 
         [0289]    The synchronization is obtained with the activated TV program and at least one of the following techniques: the core L is automatically informed when the programs or adverts activated with the core begin; the core L itself detects the beginning of a TV program or advert that has been activated with the core L with a touch of the screen; and/or the core L is manually configured by an operator. 
         [0290]    In the event that different TV programs or adverts activated with the core L occur simultaneously, the core L will simply ask the user to choose which content he wants to see, or which channel he was viewing. 
         [0291]    The sequence of the content is as follows: when a user has activated a Link-ID application by pressing on the selection means provided for this purpose during an activated or provided television program or advert, he has the facility to visualize a specific content or to perform specific actions. 
         [0292]    In addition, the core will indicate to the account of the user that he has pressed the relevant selection means or button in a specific program or advert, the user can then transfer to a website of a producer or advertiser subject to use of his PC or mobile means and he can then further log in using his mobile application. 
         [0293]    The website can then ask for the account of the user and check whether he has joined the current system campaign. If so, the website can give special privileges to the user. Simultaneously all required personal particulars of the user are shared with the producer/advertiser. If privacy legislation and regulation so requires, this data sharing can be carried out in such a way that the user must expressly confirm this. 
         [0294]    The user can also claim his benefits on a point of sale POS provided that the POS software is connected online. To identify himself, the user can notify his core system, username—chosen by him on registration—to the POS operator, or he can have a barcode and the like generated by a system mobile application. 
         [0295]    The POS software can then scan this barcode or TAG and further use it to identify the user in the system server. 
         [0296]    Application examples of the system button are particularly in the following possible conditions by pressing the system button during an advert thanks to which the user can enjoy an exclusive price reduction on the advertiser&#39;s web shop. 
         [0297]    Furthermore, by pressing the button various times, the user can obtain a benefit if he views all parallel-running adverts of a specific product. This means also allows a vote to be placed during a TV program in the context thereof, in a poll. Finally, pressing the system button during a TV program can provide additional content known as a bonus, or additional background information on the subject concerned. 
         [0298]    In the context of a further extension of the functionality of the management system, a further development of the possibilities of the attributes is also explained below in  FIG. 15 . 
         [0299]    Examples: some scenarios in which the so-called mobile authentication according to the invention may be used follow below. Each scenario is based on a user who has already registered. 
         [0300]    A. For an authentication on a Web site, the user follows the next system steps: 
         [0301]    1. a user goes to a web site; 2. the user clicks on submit; 
         [0302]    3. the web site shows a QR code; 4. the user scans the QR code with his mobile application according to the invention; 5. the user recognizes the context of his mobile application “sign in at site X”; 
         [0303]    6. The user enters his PIN code in the mobile application according to the invention; 
         [0304]    7. Web site reads the successful session status and enables user to the protected part of web site. 
         [0305]    B. For a payment on a web site, the user follows the following System Steps: 
         [0306]    1. a user goes to a web site and composes an order; 2. the user clicks on pay; 
         [0307]    3. the web site displays a QR code; 
         [0308]    4. the user scans the QR code with his mobile application according to the invention; 
         [0309]    5. the user recognizes the context of its mobile application “ pay X Euros on site Y”; 
         [0310]    6. the user enters his PIN code in the mobile application according to the invention; 
         [0311]    7. the web site reads the successful session state and uses the stored payment data of the user to pay the order. 
         [0312]    C. For a payment in a physical store, the user follows the following System Steps: 
         [0313]    1. a user goes to a store checkout; 2. the cashier clicks on pay in the POS system; 
         [0314]    3. the cash register displays a QR code; 4. the user scans the QR code with his mobile application according to the invention; 
         [0315]    5. the user recognizes the context of his mobile application “pay X Euros in store Y”; 
         [0316]    6. the user enters his PIN code in the mobile application according to the invention; 
         [0317]    7. the POS system reads the successful session state and uses the stored payment data from the user to pay the order. 
         [0318]    D. For an access control to an event, the user follows the next System Steps: 
         [0319]    1. a user to the access control; 2. the control system displays a QR code; 
         [0320]    3. the user scans the QR code with his mobile application according to the invention; 
         [0321]    4. the user recognizes the context of his mobile application “to enter event X”; 
         [0322]    5. the user enters his PIN code in the mobile application according to the invention; 
         [0323]    6. the control system reads the successful session state and verifies in its database whether this user actually has the right to enter.