Provision and acquisition of one or more data sets via a digital communications network

Abstract

A server for providing one or more datasets over a digital communications network, the server being configured to: associate a unique identifier with the identified dataset, the unique identifier representing a network address for accessing the identified dataset over the digital communications network, the unique identifier being unique to the identified dataset; verify authentication information provided by an authenticator of a client requesting access to the server via the unique identifier; and selectively provide the client with access to the one or more datasets if the authentication information identifies the authenticator as associated with a registered user. A device for acquiring datasets over the digital communications network is configured to acquire a unique identifier for the dataset, the unique identifier representing a network address for accessing the dataset over the digital communications network, the unique identifier being unique to the dataset. The device comprises a client configured to use the unique identifier to send a request to the server providing the dataset to access the dataset. The client is configured to provide the server with authentication information of the authenticator for authenticating the client to the server, the authenticator being associated with the registered user.

Description

[Technical field]

[0001] The embodiments according to the invention relate to the field of data transfer over digital communication networks. More particularly, the embodiments relate to servers and methods for providing one or more data sets over a digital communication network. Further embodiments relate to devices and methods for acquiring data sets over a digital communication network. Further embodiments relate to methods and systems for securely retrieving information about analyzed data over a digital communication network such as the Internet, an intranet, etc. Further embodiments of the present invention relate to computer methods and systems for securely granting access to analyzed data over the Internet. [Background technology]

[0002] Providing or transferring information, e.g. analyzed data, can be done in a separate way, e.g. traditional way via printout report. In this way, it is easy to ensure that a) the recipient receives the message at the right time, with the right security features and with the right convenience. In many cases, the classical postal delivery system with registered mail is used to meet such requirements. As an example, a registered notarized document or an analysis report / diagnosis result is sent to the customer / patient.

[0003] However, another way of global information transmission today is through the use of the World Wide Web / Internet. Here, many conveniences come into play. By using the Internet, or digital communication networks in general, access to information can be given and / or created quickly, easily, and instantly to almost anyone, regardless of the requester's location. By using a worldwide network of servers, the Internet allows any kind of information to be transmitted to a client. Today, the Internet is used in unlimited ways, such as social networking, processing financial transactions, or controlling industrial equipment. With increasing penetration into all areas, security has become a major concern. Most people already have access to the Internet and it is available through multiple methods. One of them is email. Email, as a "ubiquitous" feature of information exchange, is undoubtedly the most frequently used method to exchange any kind of information from documents to videos, photos, etc. Today, the widespread availability of smartphones makes it possible to check for new information about yourself or the processes around you almost always and anywhere. However, especially in the healthcare field, this information is often of a valuable and private nature, and email and most other information sharing products, such as instant messengers, image / photo or video sharing platforms, or document exchange software, are often not suitable for this type of information.

[0004] In the last few years, a lot of effort has been made to create a secure yet very convenient place to store information (even important and private information) in the cloud. Keeping data secure while at rest, i.e. not in transit, is mainly a matter of what encryption algorithms are used. This also applies to data that is persisted on some kind of computer hardware. However, in most cases, even today, the authentication process of some user credentials is not very secure. Again, hashing the password in a database is a very secure way to keep this information (as this database is kept on some computer hardware). The process of logging in (checking the credentials) and retrieving the data, especially healthcare data, requires additional subsequent permission checks to assure the user that only those with the appropriate permissions have access to the analyzed data.

[0005] In IT system design, there is a constant evaluation of security versus convenience. Many, if not all, people want their personal data (especially healthcare data) to be secure and safe wherever it is stored. However, it is recognized that in order to use such data, one needs to have the most convenient, yet most secure, way to access it.

[0006] Accessing sensitive information such as personal data over the Internet requires a secure transport channel as well as a secure authentication mechanism. The gold standard in practice is authentication by username and password, which depends heavily on the strength of the password used. Weak passwords are easy to guess, while strong passwords are difficult to remember. In addition, the username often consists of part or all of the name of the person who wants to authenticate himself. In most scenarios, the authenticator is the person to whom the data belongs. However, especially in an increasingly digitalized healthcare environment, the requester of an individual's personal data is the service provider. In a medical setting, this may be a doctor, a clinician, or a laboratory service provider. As explained, the transfer of data is most often secure, but the information about the individual requesting the specific (healthcare) data is not protected, since the login credentials (i.e., username and password) are submitted and transferred. Thus, the identity of such an individual is traceable, since in addition to the login credentials, the actual geographic location (via IP address) is also traceable. This also creates a vulnerability for the individual who is the subject of the data. Another problem in accessing information over the Internet is the identification of that information. For example, a request for detailed information about a particular product may result in different information about different products. Summary of the Invention [Problem to be solved by the invention]

[0007] It is an object of embodiments of the present invention to provide a concept for transferring information, which offers an improved trade-off between user convenience and data security, both of the information transferred and of the information relating to the user. [Means for solving the problem]

[0008] According to the present invention, such a concept is provided by identifying information provided by a server, such as a data set, with a unique identifier specific to that information, and verifying the access rights of a user requesting access to that information using an authenticator associated with a registered user. The combination of these features allows for the secure and specific provision of information, while keeping information regarding the identity of a user requesting access to information private.

[0009] An embodiment according to the invention provides a server for providing one or more datasets via a digital communication network such as the Internet or an intranet. The server is configured to associate a unique identifier with an identified dataset, e.g., a particular dataset of the one or more datasets, the particular dataset being identified by the unique identifier. The unique identifier represents a network address for accessing the identified dataset via the digital communication network, the unique identifier being specific to the identified dataset. The server is further configured to verify, via the unique identifier, authentication information provided by an authenticator of a client requesting access to the server, e.g., requesting access to one or more datasets hosted or provided by the server. For example, verifying the authentication information includes evaluating the authentication information to obtain or verify the identity of the authenticator. The server is configured to selectively provide the client with access to the one or more datasets if the authentication information identifies the authenticator as a registered user, e.g., associated with a previously registered user. For example, verifying the authentication information may include verifying if the authenticator is associated with a registered user.

[0010] For example, the server is configured to provide a unique identifier to the registered user. Having a unique identifier for the identified dataset allows the user to identify the identified dataset, ensuring that the user requests the desired dataset, thereby preventing false information. The registered user can access the server by using the client, using the network address represented by the unique identifier. Since the client uses the authenticator to authenticate to the server, the registered user does not need to authenticate to the server with a credential that contains information about the registered user's identity. Thus, the identity of the registered user requesting access to the server is secure, since the identity of the registered user does not need to be transferred between the client and the server to access the dataset on the server. In other words, by using this type of authentication, no personal data needs to be exchanged between the client and the server. Furthermore, by using an authenticator for the authentication of the registered user, the registered user does not necessarily need to represent an individual natural person, but can also represent a user entity, e.g., a group of people, such that multiple people or users can use the same authenticator associated with the registered user. Thus, the use of an authenticator increases flexibility and user convenience, for example in situations where multiple people share a task associated with a provided dataset. The access rights to one or more datasets may include, for example, access rights to the identified dataset, but also access rights to further datasets hosted by the server, such that the user can access multiple datasets hosted by the server if the client used by the user is authenticated as a registered user. Thus, granting registered users access to one or more datasets increases the user convenience of data provision.

[0011] According to one embodiment, the server is configured to verify authentication information provided by an authenticator of a client requesting access to the identified dataset via a unique identifier, and the server is configured to selectively provide the client with access rights to the identified dataset, the access rights to the identified dataset being specific to a registered user associated with the authenticator. The user-specific access rights allow the identified dataset to be provided to a unique registered user. Thus, the server can ensure that the identified dataset is specifically and selectively provided to a registered user granted with unique access rights. Thus, the server can grant individual access rights to the identified dataset to multiple users. Thus, the user-specific access rights enhance data security of the identified dataset, since only one or more unique registered users can access the identified dataset.

[0012] One embodiment according to the invention provides a server for providing a dataset, e.g., designated as an identified dataset, over a digital communications network. The server is configured to associate a unique identifier with the dataset, the unique identifier representing a network address for accessing the dataset over the digital communications network, the unique identifier being specific to the dataset. The server is further configured to verify authentication information provided by an authenticator of a client requesting access to the dataset via the unique identifier. The server is configured to selectively provide the client with access rights to the dataset, the access rights being specific to a registered user associated with the authenticator. The server combines the features and advantages of the previous embodiments.

[0013] According to one embodiment, the server is configured to register the authenticator by associating the authenticator with identity information identifying the user. For example, a registered user may be a user who may have been previously registered by providing identity information for verifying the user's identity. For example, a registered user may register an authenticator by providing information identifying the authenticator, for example by providing authentication information. For example, the server is configured to store information identifying the authenticator in order to associate the authenticator with the user's identity, which information may be based on or derived from the authentication information, for example. After registering the authenticator, the server may identify the registered user via the authenticator, for example by receiving or evaluating the authentication information, such that repeated provision or transfer of identity information to authenticate the registered user to the server may not be necessary. For example, the server may be configured to associate multiple authenticators with the registered user. For example, multiple natural persons may use multiple authenticators associated with the registered user, improving the flexibility and user convenience of the system.

[0014] According to one embodiment, the server is configured to register users, for example by storing identity information about the users. The server is configured to register users so that new users can conveniently join the system.

[0015] According to one embodiment, the server contains access information that associates registered users with access rights to the identified datasets and, optionally, to further datasets. For example, the access information may define one or more registered users that possess individual access rights to a particular dataset. Having the access information allows the server to organize the access rights to one or more datasets in a very efficient manner.

[0016] According to one embodiment, the server is configured to direct a client requesting access to the server to an identified dataset, e.g., a dataset identified by a unique identifier used by the client to access the server. Directing a client to an identified dataset is highly convenient for a user requesting access to the identified dataset.

[0017] According to one embodiment, the server is configured to use a cryptosystem to verify the authentication information, and the server is configured to associate the authenticator with a cryptographic key unique to the authenticator. For example, the cryptosystem may be based on an asymmetric cryptosystem, and the server may associate the authenticator with the authenticator's public key information. The use of cryptography allows for secure, efficient, and user-convenient verification of the authenticator's identity.

[0018] An embodiment according to the invention provides a device for obtaining a dataset, e.g. designated as an identified dataset, via a digital communication network. The device is configured to obtain, e.g. receive or recognize, a unique identifier of the dataset, the unique identifier representing a network address for accessing the dataset via the digital communication network, the unique identifier being specific to the dataset. The device comprises a client configured to use the unique identifier to send a request for accessing the dataset to a server providing the dataset. The client is configured to provide the server with authentication information of an authenticator for authenticating the client to the server, the authenticator being associated with a registered user. By using the unique identifier specific to the dataset to send the request for accessing the dataset, it is possible to avoid retrieving false information from the server, e.g. a different dataset. For example, the device may act as a counterpart of said server. For example, a user may use the device to retrieve or request a dataset from the server. Thus, details of the server and its features, functions and advantages, whenever applicable, apply equally to the device.

[0019] According to one embodiment, the device comprises an authenticator, thus making the authenticator particularly available to devices and clients and improving user convenience.

[0020] According to one embodiment, the device is configured to access the authenticator via a digital interface. For example, the authenticator is part of an external device connected to the device via a digital interface. Thus, the external device with the authenticator can be removed from the device such that the device cannot authenticate to the server. Thus, only persons who own the external device with the authenticator or have access to the authenticator can use the device to request the data set. By preventing unauthorized persons from using the device, data security can be improved.

[0021] According to one embodiment, the device comprises an input interface for receiving user input, the device being configured to selectively provide authentication information to the server in response to the user input. For example, the device may be configured to enable the use of an authenticator for providing authentication information dependent on the presence of a user or verification of a user's identity. Thus, the input interface can ensure the authorization of a user to use the device, enhancing data security for requesting a data set.

[0022] According to one embodiment, the device is configured to obtain biometric information about a user, and the device is configured to selectively provide authentication information to a server if the biometric information identifies the user as being associated with the authenticator. For example, the biometric information may be obtained from user input or user interaction via an input interface. Biometric information is a particularly secure and particularly convenient way of identifying a natural person.

[0023] According to one embodiment, the device is configured to derive the unique identifier from a graphical pattern, such as a barcode or a QR code, that represents the unique identifier. Providing the unique identifier to the device as a graphical pattern is a convenient way for a user to input the unique identifier to the device. Additionally, providing the unique identifier as a graphical pattern can avoid incorrect input of the unique identifier or providing an incorrect unique identifier to the device, thereby ensuring that the correct data set is requested.

[0024] According to one embodiment, the authenticator includes a cryptographic key, e.g. a secret or private key, and the authenticator is configured to use the cryptographic key to provide authentication information to the server. For example, the authenticator's cryptographic key known to the server and a further cryptographic key, e.g. a cryptographic key that the server associates with the authenticator, e.g. a public key, may be part of an asymmetric cryptosystem. For example, each of the cryptographic keys may be adapted to decrypt messages encrypted with the respective other key. The use of the cryptographic keys to provide authentication information allows secure verification of the authenticator to the server.

[0025] According to one embodiment, the authentication information allows anonymous authentication of a registered user to a server, e.g., without transmitting username or password data, e.g., relying on verification that the authentication information, e.g., an encrypted message, was generated by using an authenticator, e.g., an authenticator that includes a cryptographic key of a particular registered user. For example, the authenticator is anonymized. For example, the authenticator may be represented by information that does not include hints regarding personal data (e.g., name or contact information) of the registered user associated with the authenticator.

[0026] One embodiment according to the present invention provides a method of providing one or more data sets over a digital communications network. The method includes associating a unique identifier with an identified data set, the unique identifier representing a network address for accessing the identified data set over the digital communications network, the unique identifier being unique to the identified data set. The method further includes verifying authentication information provided by an authenticator of a client requesting access to the one or more data sets via the unique identifier. The method further includes selectively providing the client with access to the one or more data sets if the authentication information identifies the authenticator as associated with a registered user.

[0027] An embodiment according to the present invention provides a method for acquiring a dataset over a digital communications network, the method comprising acquiring a unique identifier for the dataset, the unique identifier representing a network address for accessing the dataset over the digital communications network, the unique identifier being specific to the dataset, the method further comprising using the unique identifier to send a request to access a server hosting the dataset, the method further comprising providing to the server authentication information of an authenticator for authenticating the client to the server, the authenticator being associated with a registered user.

[0028] The described methods rely on the same concepts as the above-mentioned devices, namely the server and the device for obtaining the data set, and these methods offer comparable functions and advantages. The methods may, if desired, be combined with or supplemented by any of the features, functions and details described herein with respect to the corresponding devices. The methods may, if desired, be combined with both mentioned features, functions and details, individually or in any combination thereof. Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. [Brief description of the drawings]

[0029] [Figure 1] FIG. 2 is a schematic diagram of a server according to one embodiment. [Diagram 2] FIG. 2 is a schematic diagram of a device for acquiring a dataset according to one embodiment. [Diagram 3] FIG. 2 is a schematic diagram of a server and a device for acquiring a data set according to one embodiment. [Figure 4] 1 is a flowchart of a method for registering a user according to one embodiment. [Diagram 5] 1 is a flowchart of a method for providing one or more data sets according to one embodiment. [Figure 6] FIG. 2 illustrates a flow diagram of a method for acquiring a data set according to one embodiment. [Figure 7] 5 is a flowchart of a method for transferring a dataset between a server and a device for acquiring the dataset according to a further embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] Different embodiments and aspects of the invention are described below, with further embodiments defined by the appended claims.

[0031] It should be noted that any embodiment defined by the claims may be supplemented by any of the details (features and functions) described herein. Also, the embodiments described herein may be used individually and may be supplemented, if desired, by any of the details (features and functions) contained in the claims. Also, it should be noted that each aspect described herein may be used individually or in combination. Thus, a detail may be added to each of the individual aspects without adding the detail to another one of the aspects. Also, it should be noted that the present disclosure explicitly or implicitly describes features that may be used to transfer, provide, retrieve, request, or receive information.

[0032] The present invention will be more fully understood from the detailed description given below and the accompanying drawings of embodiments of the invention, which should not be construed to limit the invention to the particular embodiments described, but are merely for purposes of illustration and understanding. The figures show elements drawn with dashed lines to facilitate a better understanding, but these elements are not necessarily part of the embodiment shown.

[0033] 1. An embodiment of a server for providing one or more data sets according to FIG. 1 shows a schematic diagram of a server 100 according to one embodiment. The server 100 is configured to provide one or more datasets via a digital communication network 90. ​​The server 100 is further configured to associate a unique identifier 115 with an identified dataset 110, which may be part of the one or more datasets. The unique identifier 115 represents a network address for accessing the identified dataset 110 via the digital communication network 90, and the unique identifier 115 is unique to the identified dataset 110. The server 100 is further configured to verify authentication information 172 provided by an authenticator 170 of a client 160 requesting access to the server 100 via the unique identifier 115. The server is configured to selectively provide the client 160 with access rights 120 to the one or more datasets if the authentication information 172 identifies the authenticator as associated with a registered user.

[0034] According to one embodiment, the server 100 is configured to verify authentication information 172 provided by an authenticator 170 of a client 160 requesting access to an identified dataset 110 via a unique identifier 115. Thus, the server may be configured to process a request to access a particular dataset of one or more datasets, e.g., dataset 110. Additionally, the server 100 may be configured to selectively provide the client 160 with access rights 120 to the identified dataset 100, the access rights 120 to the identified dataset being specific to a registered user associated with the authenticator. Thus, the server may provide different access rights to the client 160 depending on the identity of the authenticator 170 with which the client 160 authenticates to the server by sending authentication information 172, the identity of the authenticator 170 being associated with a registered user.

[0035] According to an alternative embodiment, the server 100 is configured to provide the dataset 110, also referred to as the identified dataset 110, via the digital communication network 90. ​​Furthermore, the server 100 is configured to associate a unique identifier 115 with the dataset 110, the unique identifier 115 representing a network address for accessing the dataset 110 via the digital communication network 90, the unique identifier 115 being specific to the dataset 110. The server 100 is further configured to verify authentication information 172 provided by an authenticator 170 of a client 160 requesting access to the dataset 110 via the unique identifier 115. According to this embodiment, the server 100 is further configured to selectively provide the client 160 with access rights 120 to the dataset 110, the access rights 120 being specific to a registered user associated with the authenticator 160.

[0036] Further details of the server 100 are explained in the context of further embodiments according to the following figures. In particular, for clarity, further details of the server 100 are explained in the context of the interaction between the server and the device for obtaining the data set. It is noted that the embodiment of the server can be supplemented, if desired, with any of the features, functions and details described herein with respect to the other embodiments, both individually and in combination.

[0037] 2. Device for acquiring the dataset according to Fig. 2 2 shows a schematic diagram of an embodiment of a device 250 for obtaining a dataset 210 via the digital communication network 90. ​​The dataset 210 may be similar to the dataset 110 or the identified dataset 110 and may be provided by a server 200, for example the server 100. The device 250 is configured to obtain a unique identifier 215 of the dataset 210, the unique identifier 215 representing a network address for accessing the dataset 210 via the digital communication network 90, the unique identifier 215 being specific to the dataset 210. For example, the unique identifier 215 may be provided by the server 200. The device 250 comprises a client 260, which may be similar to the client 160. For example, the client 360 may be an internet browser or a file browser or another unit configured to communicate with the digital communication network 90. ​​The client 260 is configured to send a request 262 for accessing the dataset 210 to the server 200 providing the dataset 210, using the unique identifier 215. The client 260 is further configured to provide to the server 200 authentication information 272 of an authenticator 270 for authenticating the client 260 to the server 200, the authenticator 270 being associated with a registered user. For example, the authenticator 270 and authentication information 272 may be similar to the authenticator 170 and authentication information 172, respectively.

[0038] Further details of the device 250 are described in the context of further embodiments according to the following figures. In particular, for clarity, further details of the device 250 are described in the context of the interaction between a server and the device for obtaining a data set. It is noted that the embodiment of the device 250 can be supplemented, if desired, with any of the features, functions and details described herein with respect to the other embodiments, both individually and in combination.

[0039] 3. Interaction between server and device to obtain the dataset according to Fig. 3 3 shows a schematic of the interaction between a server 300, which may be similar to the server 100;200, and a device 350 for obtaining a dataset, which may be similar to the device 150;250. The server 300 and the device 350 may communicate via a digital communication network 90, for example the Internet. The server 300 may provide one or more datasets, including the dataset 310, for example the server 300 may host one or more datasets or the server 300 may be capable of providing access to one or more datasets hosted elsewhere. The server is configured to associate the dataset 310 with a unique identifier 315, for example the unique identifier 115;215. The unique identifier 315 represents a network address that may allow the dataset 310, 110 to be specifically addressed when accessing the server via the digital communication network 90. For example, a user wishing to retrieve the dataset 310 may use the device 350 to specifically request the dataset 310 by invoking the unique identifier 315 using a client 360 of the device 350, thereby transmitting a request 362 to the server 300 to access the dataset 310.

[0040] For example, the unique identifier 315 may include a network address of the server 300 and a unique dataset identifier that uniquely identifies the dataset 310 within an entity of information or datasets provided by the server 300. The unique dataset identifier may be globally unique within a particular entity of identifiers. The unique identifier 315 may further include information regarding the syntax or type or scheme of the unique dataset identifier. Additionally, the unique identifier 315 may include information about the syntax of the unique identifier 315.

[0041] According to one embodiment, the unique identifier 315 is represented by a Uniform Resource Identifier (URI). In other words, the requested data, e.g. the dataset 310, is identified by using a specially constructed URI. The URI consists of four parts: SCHEME, BASEURL, IDENTIFIERTYPE, and the IDENTIFIER itself. SCHEME is defined by the IETF in RFC3986 [1]. BASEURL is the domain name of the server that receives the user request, e.g. example.com [1]. IDENTIFIERTYPE defines the type of identifier below, ideally an international standard like GS1 GDTI (for documents), but it may be any internally defined identifier type or a similar technical approach. The identifier type is followed by the IDENTIFIER itself, which consists of a unique string that represents a link to the analyzed data. The IDENTIFIER must be system specific or combined with the IDENTIFIERTYPE globally unique string. Combining all parts, a possible valid URI is: https: / / example.com / gdti / 408980809ADHJKCGGHBKN

[0042] For example, it may be important that the identifier is a unique string for every requested data object. A possible way to ensure the uniqueness of this identifier, e.g. the unique identifier 315, is to comply with an international standard, such as the standard from GS1, which is also mentioned in the EU Medical Device Regulation (MDR) and the In Vitro Diagnostics Regulation (IVDR). By using the URI format described above, a data object, e.g. the dataset 310, can be uniquely identified and made accessible.

[0043] The client 360 may be similar to the clients 160, 260. For example, the client 360 may comprise or be part of a separate unit for navigating an Internet browser for navigating within a digital communication network, which may be utilized by a user to access the server 100 or one of the data sets hosted by the server.

[0044] The server 300 may be configured to selectively allow access to the dataset 310, and optionally additional datasets, depending on the identity of a user using a client 360 to access the server 300. To this end, the server 300 may verify whether a request 362 to access the dataset originates from a registered user, and, if desired, the server 300 may check the identity of a registered user requesting access to the server.

[0045] To authenticate as a registered user, a user may be represented by an authenticator 370. For example, a registered user may simply be represented by a pre-registered authenticator 370. The authenticator 370 may include a cryptographic entity that allows for unique identification of the authenticator 370 within a cryptosystem. For example, the authenticator may include a pair of cryptographic keys, such as a private key and a public key that are secret to the authenticator.

[0046] According to one embodiment, the server 300 is configured to register the authenticator 370 by associating the authenticator 370 with identity information that identifies a registered user.

[0047] For example, a registered user may register the authenticator 370, and after registration, the authenticator 370 may be associated with the registered user. For example, the server 300 may store the public key of the authenticator 370 to register the authenticator 370.

[0048] For example, the server 300 may be configured to use a cryptosystem to verify the authentication information 372 , and the server 300 may be configured to associate the authenticator 370 with a cryptographic key that is unique to the authenticator 370 .

[0049] According to one embodiment, a registered user can register one or more authenticators. A possible scheme for registering an authenticator is explained in the context of FIG.

[0050] The client 360 may use an authenticator 370 associated with a registered user to verify that a request to access a server occurs on behalf of the registered user and / or to verify the identity of the registered user requesting access to the server. For example, authentication of the identity of the authenticator 370 may be based on an exchange of encrypted messages between the server 300 and the client 360.

[0051] According to one embodiment, the authenticator 370 can include an encryption key, and the authenticator 370 can be configured to use the encryption key to provide authentication information 372 to a server.

[0052] For example, the server 300 may send the verification information to the device 350. The device 350 may encrypt or sign the verification information by using a private key of the authenticator 370, e.g., a private key of a key pair, to obtain the authentication information 372. The client 360 may send the authentication information 372 to the server 300. The server 300 may verify the identity of the authenticator 370 by testing whether decrypting the authentication information 372 using the public key of the authenticator 370 results in the verification information originally sent to the client 370, or by using the public key to test whether the signature of the authentication information was generated by using the private key. Since the server may associate the authenticator 370 with a registered user, this authentication procedure allows authentication of the registered user to the server without transmitting any information about the user identity. Thus, the authentication information 372 may allow anonymous authentication of the registered user to the server.

[0053] Alternatively, the cryptosystem may be symmetric, i.e. the server 300 contains an encryption key associated with the authenticator 370, the common encryption key being secret to the authenticator 370 and the server 300, the server 300 using the common encryption key to decrypt the authentication information 372, which is obtained by the device 350 by decrypting the verification information by using the common encryption key.

[0054] In other words, to access the requested information, e.g. a data set, the requester may have to authenticate to the system or server that holds this information. For example, the authentication itself may be based on the WebAuthn standard and may require a so-called authentication device. Each user of the system may be able to register one or more of these devices as an alternative method for the classical username-password authentication. By using this kind of authentication, it may not be necessary to exchange personal data between the client and the server. For example, the only data exchanged is a public key based on the user authentication device.

[0055] 1-3 are schematic and exemplary. The device 350 or the client 360 may include the authenticator 370. Thus, the device may access the authenticator at any time during operation, for example.

[0056] According to one embodiment, device 350 is configured to access authenticator 370 via a digital interface. For example, authenticator 370 may be part of an external device connected to device 350 via a digital interface. Thus, device 350 can authenticate using authenticator 370 only if the external device is connected to device 350.

[0057] According to one embodiment, the server contains access information that associates registered users with access rights to the data set 310 and, optionally, to further data sets.

[0058] For example, access rights to a dataset 310 may include specific permissions for the dataset 310, such as the right to receive the dataset 310 in a particular format, or the right to download, delete, or modify the dataset 310. For example, access rights may be defined for a particular user or for a particular group of users or roles. For example, the access information may associate a registered user with one or more roles or groups of users.

[0059] According to one embodiment, server 300 is configured to provide a client that authenticates using an authenticator associated with any registered user with access to dataset 310, and optionally access to further datasets, such as all datasets provided by server 300. According to one embodiment, the server 300 is configured to direct a client 360 requesting access to the server 300 to the identified data set.

[0060] For example, a client 360 may access the server 300 by using the unique identifier 315. After authentication, the server 300 can direct the client 360 to a data set 310 identified by the unique identifier 315. Optionally, the server 300 can provide the client 360 with access to further data sets without requiring authentication again.

[0061] According to one embodiment, the device 350 comprises an input interface 380 for receiving user input 372, and the device 350 is configured to selectively provide the authentication information 372 to the server in response to the user input 382.

[0062] For example, device 350 may require a user to actively initiate a request to access dataset 310 or to confirm the initiation of a request to access dataset 310 via user input 382. For example, the device may allow client 360 to use authenticator 370 only after a user has initiated or confirmed use via user input 382. For example, user input 382 may include input via a keyboard, a touch screen, a scanner unit, or a camera.

[0063] According to one embodiment, device 350 is configured to obtain biometric information regarding a user, and device 350 is configured to selectively provide authentication information 372 to server 300 if the biometric information identifies the user as associated with authenticator 372.

[0064] For example, user input includes a user's fingerprint or an image of the user's face. Device 350 can associate authenticator 370 with the identity of one or more users authorized to use authenticator 370. For example, device may allow client 360 to use authenticator 370 only after an associated user initiates or confirms use via user input 382.

[0065] According to one embodiment, the device 300 is configured to derive the unique identifier 315 from a graphical pattern representing the unique identifier 315. For example, the device may receive the unique identifier 315 from a scanner unit or camera functionality that may be part of the device 350 or may be an external device, if desired.

[0066] For example, user input 382 may include scanning a graphical pattern. For example, a user scanning the graphical pattern may initiate a request to access a data set identified by a unique identifier represented by the graphical pattern.

[0067] 4. Registering an authenticator as shown in Figure 4 4 shows a flowchart of a method 400 for registering an authenticator, e.g., authenticator 170; 270; 370, according to one embodiment. The authenticator to be registered may be part of or connected to a device for acquiring a data set, e.g., device 150, 250, 350. For registration, the authenticator may also be connected to another device.

[0068] The method 400 may be applied for the initial registration of an authenticator. Step 402 involves a user, e.g. a registered user, logging in to a personal administration page with a username and password. For example, the administration page may be hosted by the server 100, 200, 300. The administration page may be hosted on another server configured to share information about registered authenticators with the server 100, 200, 300. In another step 403, the user may select an option to register a new authenticator. Then, in step 404, the server asks the user to follow browser or specific application (i.e., part of the software from something like Apple's App-Store) instructions. Then, in step 405, the user follows an authenticator-specific registration process. In step 406, the server receives and stores public key information from the authenticator to complete the registration of the authenticator.

[0069] For example, the registration of an authentication device may follow the principles defined by the WebAuthn standard [2]. After a successful initial login, the user can register a new security key / device. A security device can be either a platform authenticator or a roaming authenticator, according to the WebAuthn standard. The main difference is that a platform authenticator is physically tied to the client device (e.g., a smartphone or laptop), whereas a roaming authenticator (e.g., a USB security key) is removable and can be attached to different client devices. During the registration process, a server-side component associates the public key provided by the authenticator with the user information.

[0070] 5. Method for Providing One or More Data Sets According to FIG. FIG. 5 illustrates a flow chart of one embodiment of a method 500 for providing one or more data sets, such as data sets 110; 210; 310, over a digital communications network.

[0071] The method 500 includes a step 501 of associating a unique identifier 115;215;315 with the identified data set 110;210;310, the unique identifier 115;215;315 representing a network address for accessing the identified data set 110;210;310 via the digital communications network 90, the unique identifier 115;215;315 being unique to the identified data set. A further step 502 includes verifying (502) authentication information 172;272;372 provided by an authenticator 170;270;370 of a client 160;260;360 requesting access to one or more data sets via the unique identifier 115;215;315. The method 500 includes a further step 503 of selectively providing the client 160;260;360 with access to one or more data sets if the authentication information 172;272;372 identifies the authenticator 170;270;370 as associated with a registered user. 5 is selected exemplarily. For example, steps 502 and 503 may be performed independently of step 501.

[0072] 6. Method for obtaining the data set according to Fig. 6 FIG. 6 illustrates a flow chart of one embodiment of a method 600 for acquiring a data set 110 ; 210 ; 310 over a digital communications network 90 .

[0073] The method 600 comprises a step 601 of obtaining a unique identifier 115;215;315 for the dataset 110;210;310, the unique identifier 115;215;315 representing a network address for accessing the dataset 110;210;310 via the digital communications network 90, the unique identifier 115;215;315 being specific to the dataset 110;210;310. The method comprises a further step 602 of using the unique identifier 115;215;315 to send a request for accessing a server 100;200;300 hosting the dataset 110;210;310. A further step 603 includes providing the server 100;200;300 with authentication information 172;272;372 of an authenticator 170;270;370 for authenticating the client 160;260;360 to the server 100;200;300, the authenticator 170;270;370 being associated with a registered user.

[0074] The order of the steps of the method 600 shown in Fig. 6 is exemplary. For example, after obtaining the unique identifier (601), steps 602 and 603 may be repeated and / or performed independently from step 601.

[0075] 7. Method for transferring a data set according to FIG. 7 shows a flow chart of an embodiment of a method 700 for transferring a dataset between a server and a device to obtain the dataset. For example, the method 700 may combine features of the methods 500 and 600, which may be performed by the server 100; 200; 300 or the device 150; 250; 350.

[0076] The method 700 comprises opening (702) a unique URI of the analyzed data item, for example a data set 110;210;310. For example, step 702 may comprise step 602. For example, the URI is directed to a server, for example server 100;200;300. Then, in step 703, the server requests authentication. In a next step 704, the user authenticates himself via an authenticator, for example authenticator 170;270;370. For example, step 704 may comprise step 603. In step 705, the server determines whether the authentication was successful, for example whether the user was authenticated as a registered user or whether the user was authenticated as a registered user authorized to access the requested data set. For example, step 705 may comprise step 502. If the authentication was successful, step 706 is executed, otherwise step 707 is executed. In step 706, the server responds with the analyzed data item. For example, step 706 may include step 503. In step 707, the server may, for example, deny access to the server or the data item or data set.

[0077] In other words, after successful registration of an authenticator, e.g. authenticator 170;270;370, the user can access the analyzed data, e.g. dataset 110;210;310, via the provided URI, e.g. unique identifier 115;215;315, without providing a username or password. When opening the URI, e.g. by typing the URI or by scanning a two-dimensional code, the user may have to authenticate himself by using the registered authenticator. The authentication process itself may also follow the principles of a WebAuthn compatible public key authentication mechanism, in which case the server verifies the authentication information by having the user authenticator cryptographically sign a given message with his private key and send it to the server. The server then ensures that the sent message can be verified with the public key stored on the server and associated with the user [3].

[0078] According to one embodiment, using this authentication method, it may not be necessary to transport any personal data to identify the user to access information.

[0079] 8. Further Aspects and Embodiments The embodiments of the present disclosure relate to a method and system for securely retrieving information about analyzed (healthcare) data via the Internet. For example, information is requested by a client invoking a qualified URI [4] based on an international standard that ensures a unique one-to-one relationship between the analyzed data and the collected information about the data. The URI itself may be encoded and presented as a two-dimensional code such as a QR code, GS1 Data Matrix, or similar technological approaches, which is accessible via handheld and fixed devices.

[0080] According to one embodiment, to retrieve the information, the client must authenticate itself to the server using a public key cryptography mechanism based on the Web Authentication API specification [2] or a similar technical approach. For example, after receiving the authentication information by the client, the server presents the information in HTML or a structured data format, such as json. Embodiments of the present disclosure relate to methods and systems for secure retrieval of analyzed (healthcare) data through a convenient yet secure manner.

[0081] SUMMARY OF THE DISCLOSURE Embodiments of the present disclosure relate to a system for securely granting access to analyzed data over the Internet while keeping the identification of data items unique and keeping the identity of the requesting party secure.

[0082] An embodiment of the present invention relates to a method, device or system that can create pseudonymized access to a remote service system, authenticate a specific user to the remote system using pseudonymized data and grant this user certain access rights, i.e. permissions, based on their role, thereby allowing the requested data to be uniquely identified in order to prevent false information.

[0083] While much progress has been made in securing the transport of information over secure channels using encrypted transport protocols, the invention of new authentication mechanisms that do not rely on personal information such as usernames or email addresses has not received much attention.

[0084] For example, combining unique URIs for object identification, the use of the WebauthN standard to authenticate users without relying on personal data, and finally presenting the requested information in a structured way, solves the problems of the current solutions described in a modular and unique way.

[0085] For example, detailed information requested, such as specific identification of a requested object or data set, may be unavoidable, especially in the context of clinical data that contains information about specific individuals.

[0086] Although some aspects have been described in the context of an apparatus, it will be apparent that these aspects also represent descriptions of corresponding methods, where a block or device corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method step also represent descriptions of a corresponding block or item or feature of a corresponding apparatus.

[0087] Some or all of the method steps may be performed by (or using) a hardware apparatus such as, for example, a microprocessor, a programmable computer or an electronic circuit. In some embodiments, one or more of the most important method steps may be performed by such an apparatus.

[0088] Depending on the specific implementation requirements, embodiments of the present invention can be implemented in hardware, or in software, or at least partly in hardware, or at least partly in software. The implementation can be carried out using a digital storage medium, for example a floppy disk, DVD, Blu-ray, CD, ROM, PROM, EPROM, EEPROM or flash memory, on which electronically readable control signals are stored, which cooperate (or can cooperate) with a programmable computer system such that the respective method is executed. The digital storage medium may therefore be computer readable.

[0089] Some embodiments according to the invention include a data carrier having electronically readable control signals capable of cooperating with a programmable computer system to cause one of the methods described herein to be performed.

[0090] Generally, embodiments of the present invention can be implemented as a computer program product having program code which operates to perform one of the methods when the computer program product is run on a computer. The program code may for example be stored on a machine readable carrier. Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine readable carrier.

[0091] In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described herein, when the computer program runs on a computer.

[0092] A further embodiment of the inventive method is therefore a data carrier (or digital storage medium, or computer readable medium) having recorded thereon the computer program for performing one of the methods described herein. The data carrier, digital storage medium or recording medium is typically tangible and / or non-transitory.

[0093] A further embodiment of the inventive method is therefore a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be arranged to be transferred via a data communication connection, for example via the Internet.

[0094] A further embodiment comprises a processing means, for example a computer, or a programmable logic device, configured to or adapted to perform one of the methods described herein. A further embodiment comprises a computer having installed thereon the computer program for performing one of the methods described herein.

[0095] Further embodiments according to the invention include an apparatus or system configured to transfer (e.g. electronically or optically) a computer program for performing one of the methods described herein to a receiver. The receiver may for example be a computer, a mobile device, a memory device, etc. The apparatus or system may for example comprise a file server for transferring the computer program to the receiver.

[0096] In some embodiments, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functionality of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by any hardware apparatus.

[0097] The apparatus described herein may be implemented using a hardware apparatus, or using a computer, or using a combination of a hardware apparatus and a computer.

[0098] The methods described herein may be performed using a hardware apparatus, or using a computer, or using a combination of a hardware apparatus and a computer.

[0099] While the present disclosure has been described with reference to exemplary embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the exemplary embodiments, as well as other embodiments of the present disclosure, will be apparent to those skilled in the art upon reference to the description. It is therefore intended that the appended claims cover any such modifications or embodiments.

[0100] References [1]https: / / tools.ietf.org / html / rfc3986 [2]https: / / w3c.github.io / webauthn / [3]https: / / w3c.github.io / webauthn / #sctn-sample-authentication [4]https: / / tools.ietf.org / html / rfc1630

Claims

1. A server (100; 200; 300) for providing one or more data sets over a digital communications network (90), said server (100; 200; 300) comprising: Associating a unique identifier (115; 215; 315) with the identified data set (110; 210; 310), the unique identifier (115; 215; 315) representing a network address for accessing the identified data set (110; 210; 310) via the digital communications network (90), the unique identifier (115; 215; 315) being unique to the identified data set (110; 210; 310); - verifying authentication information (172; 272; 372) provided by an authenticator (170; 270; 370) of a client (160; 260; 360) requesting access to said server (100; 200; 300) via said unique identifier (115; 215; 315); selectively providing the client (160; 260; 360) with access to one or more data sets if the authenticator identifies the client (160; 260; 360) as being associated with a registered user by verifying the authentication information, the one or more data sets including the identified data set; configured to: The unique identifier is provided to a user of the client, the server (100; 200; 300).

2. the server (100; 200; 300) is configured to verify the authentication information (172; 272; 372) provided by the authenticator (170; 270; 370) of the client (160; 260; 360) requesting access to the identified dataset (110; 210; 310) via the unique identifier (115; 215; 315), the server (100; 200; 300) is configured to selectively provide access to the identified data sets (110; 210; 310) to the clients (160; 260; 360); the access rights to the identified data set (110; 210; 310) are specific to the registered user associated with the authenticator (170; 270; 370); 2. The server (100; 200; 300) of claim 1.

3. A server (100; 200; 300) for providing a data set (110; 210; 310) over a digital communications network (90), said server (100; 200; 300) comprising: Associating a unique identifier (115; 215; 315) with said dataset (110; 210; 310), said unique identifier (115; 215; 315) representing a network address for accessing said dataset (110; 210; 310) via said digital communications network (90), said unique identifier (115; 215; 315) being unique to said dataset (110; 210; 310); - verifying authentication information (172; 272; 372) provided by an authenticator (170; 270; 370) of a client (160; 260; 360) requesting access to said dataset (110; 210; 310) via said unique identifier (115; 215; 315); selectively providing said client (160; 260; 360) with access rights to said data set (110; 210; 310), said access rights being specific to a registered user associated with said authenticator (170; 270; 370); configured to: The unique identifier is provided to a user of the client, the server (100; 200; 300).

4. the server (100; 200; 300) is configured to register the authenticator (170; 270; 370) by associating the authenticator (170; 270; 370) with identity information identifying the registered user; A server (100; 200; 300) according to any one of claims 1 to 3.

5. said server (100; 200; 300) containing access information, said access information associating said registered users with said access rights to said identified data sets (110; 210; 310); A server (100; 200; 300) according to any one of claims 1, 2 or 4.

6. the server (100; 200; 300) is configured to provide the identified data set to the client (160; 260; 360) requesting access to the server (100; 200; 300); A server (100; 200; 300) according to any one of claims 1, 2, 4 or 5.

7. A device (150; 250; 350) for acquiring a data set (110; 210; 310) via a digital communication network (90), comprising: the device is configured to obtain a unique identifier (115; 215; 315) for the dataset (110; 210; 310), the unique identifier (115; 215; 315) representing a network address for accessing the dataset (110; 210; 310) via the digital communications network (90), the unique identifier (115; 215; 315) being unique to the dataset (110; 210; 310); said device comprising a client (160; 260; 360) configured to use said unique identifier (115; 215; 315) to send a request to access said dataset (110; 210; 310) to a server (100; 200; 300) providing said dataset (110; 210; 310), The client (160; 260; 360) is configured to provide the server (100; 200; 300) with authentication information (172; 272; 372) of an authenticator (170; 270; 370) for authenticating the client (160; 260; 360) to the server (100; 200; 300), the authenticator (170; 270; 370) being associated with a registered user, a device (150; 250; 350).

8. The device (150; 250; 350) of claim 7, wherein the device comprises the authenticator (170; 270; 370).

9. The device (150; 250; 350) of claim 7, wherein the device is configured to access the authenticator (170; 270; 370) via a digital interface.

10. The device comprises an input interface (380) for receiving user input (382); the device is configured to selectively provide the authentication information (172; 272; 372) to the server (100; 200; 300) in dependence on the user input (382); A device (150; 250; 350) according to any one of claims 7 to 9.

11. the device is configured to acquire biometric information about a user; the device is configured to selectively provide the authentication information (172; 272; 372) to the server (100; 200; 300) if the biometric information identifies the user as associated with the authenticator (170; 270; 370). A device (150; 250; 350) according to any one of claims 7 to 10.

12. The device (150; 250; 350) according to any one of claims 7 to 11, wherein the device is configured to derive the unique identifier (115; 215; 315) from a graphical pattern representative of the unique identifier (115; 215; 315).

13. said authentication information (172; 272; 372) enabling anonymous authentication of said registered user to said server (100; 200; 300); A device (150; 250; 350) according to any one of claims 7 to 12.

14. the authentication information does not include the registered user's username, password, or personal data, thereby enabling anonymous authentication of the registered user to the server; 2. The server (100; 200; 300) of claim 1.

15. the authentication information includes an encrypted message generated by using the authenticator; the authentication information does not include personal data or hints regarding personal data of the registered user associated with the authenticator; A server (100; 200; 300) according to claim 14.

16. A method (500) for providing one or more data sets over a digital communications network (90), the method comprising: Associating (501) a unique identifier (115; 215; 315) with an identified data set (110; 210; 310), the unique identifier (115; 215; 315) representing a network address for accessing the identified data set (110; 210; 310) via the digital communications network (90), the unique identifier (115; 215; 315) being unique to the identified data set; providing said unique identifier to a user of the client; verifying (502) authentication information (172; 272; 372) provided by an authenticator (170; 270; 370) of said client (160; 260; 360) requesting access to one or more data sets via said unique identifier (115; 215; 315); selectively providing (503) the client (160; 260; 360) with access to one or more data sets if the authenticator identifies the client (160; 260; 360) as being associated with a registered user by verifying the authentication information, the one or more data sets including the identified data set; The method (500).

17. A method (600) for acquiring a data set (110; 210; 310) over a digital communications network (90), the method comprising: Obtaining (601) a unique identifier (115; 215; 315) for said dataset (110; 210; 310), said unique identifier (115; 215; 315) representing a network address for accessing said dataset (110; 210; 310) via said digital communications network (90), said unique identifier (115; 215; 315) being unique to said dataset (110; 210; 310); using (602) said unique identifier (115; 215; 315) to send a request to access a server (100; 200; 300) hosting said dataset (110; 210; 310); providing (603) to the server (100; 200; 300) authentication information (172; 272; 372) of an authenticator (170; 270; 370) for authenticating a client (160; 260; 360) to the server (100; 200; 300), the authenticator (170; 270; 370) being associated with a registered user; The method (600).

18. 17. A computer program for carrying out the method according to claim 16 when the computer program is run on a computer or signal processor.

19. 18. A computer program for performing the method according to claim 17 when the computer program is run on a computer or signal processor.

Images