Terminal device with a virtual chip card terminal and mobile terminal

Abstract

Mobile device equipped for near field communication (NFC) and on which an application (150) is stored in an executable manner, wherein the mobile device is configured as follows: - to recognize that a chip card (20) designed for near field communication is located within the communication range of the terminal device; - to establish a secure communication connection with the chip card using the application; - to transmit a message to a virtual smart card terminal (200) using the application, indicating that a communication connection with the smart card has been established; and - to forward commands between the chip card and the virtual chip card terminal using the application.

Description

[0001] The invention relates to a terminal device with a virtual chip card terminal. The virtual chip card terminal is stored as an executable software application on the terminal device. The invention further relates to a mobile terminal device configured for near-field communication (NFC), on which an executable application is stored. The terminal device and the mobile terminal device are configured to support communication between a chip card configured for near-field communication and a secure communications infrastructure. Technological background

[0002] With ever-increasing digitalization, particularly in the healthcare sector in Germany, new challenges arise, for example in connection with the so-called e-prescription.

[0003] The handling of the same by a patient can be further improved, because current solutions still require a patient to insert their electronic health card (eGK) into a card terminal on site in a pharmacy to redeem an e-prescription, whereupon the e-prescription is retrieved by the specialist service and read out by a pharmacy employee.

[0004] Other applications related to the eGK, such as a so-called master data comparison, which is required for billing a service by a doctor, cannot be carried out without the patient's eGK being inserted into a card terminal in the doctor's practice, which makes billing for telemedicine services more difficult, for example.

[0005] The above information is provided only as background information to facilitate understanding of the description. It does not constitute a determination or claim as to whether any of it may be applicable as prior art to the disclosure.

[0006] The object of the present invention is to take the above-mentioned problems into account.

[0007] This problem is solved by terminal devices having the features of the independent claims. Advantageous embodiments and further developments are specified in the dependent claims. Summary of the invention

[0008] A first aspect of the invention relates to a mobile device configured for near-field communication (NFC). An executable application is stored on the mobile device. The device is preferably an NFC-enabled smartphone.

[0009] NFC stands for "Near Field Communication." This technology is specified in several industry standards, with ISO / IEC 14443 being particularly relevant in this context.

[0010] The mobile device is configured to detect that a chip card configured for near-field communication is within the device's communication range. For security reasons, the communication range is very short, and to enable stable communication with the application, the chip card must be appropriately aligned with the mobile device and in relation to an NFC sensor on the device.

[0011] The mobile device is also configured to establish a secure communication connection with the chip card.

[0012] According to a preferred embodiment, the communication connection between the application and the chip card is password-protected. A well-established method is the so-called "Password Authenticated Connection Establishment" (PACE). A so-called "Card Access Number" (CAN) can be used as the password. In the case of an electronic health card (eGK), for example, this is a six-digit number visibly printed on the card.

[0013] Furthermore, the mobile device is configured, e.g. as soon as the secure communication connection is established, to transmit a message to a virtual chip card terminal, vKT, by means of the application, which message indicates that a communication connection with the chip card has been established.

[0014] The virtual chip card terminal is designed as a software application and stored in an executable format on an external device, for example in a secure data center.

[0015] The communication between the mobile device and the device with the virtual chip card terminal, which can take place via the Internet, for example, is suitably secured, for example using TLS (Transport Layer Security).

[0016] Finally, the mobile device is configured to forward chip card commands between the chip card and the virtual chip card terminal on the device using the application. This is described in more detail below.

[0017] According to a preferred embodiment, the mobile device is configured to use an MQTT protocol for communication between the application on the mobile device and the virtual chip card terminal on the device. MQTT is a client-server protocol, with the virtual chip card terminal assuming the role of the server and, for example, implementing a so-called "message broker," which enables asynchronous and scalable communication with a multitude of clients, in this case, mobile devices.

[0018] Chip cards that can preferably be used in connection with the present invention are, for example, an electronic health card, eGK, or an electronic health professional card, eHBA, according to the gematik specification.

[0019] gematik is the “National Agency for Digital Medicine” in Germany and has overall responsibility for the so-called telematics infrastructure, TI, i.e. the central platform for digital applications in the German healthcare system, whereby gematik defines and enforces binding standards for services, components and applications in the TI.

[0020] A second aspect of the invention, which interacts with the first aspect, relates to a terminal on which a virtual chip card terminal, as already mentioned above and embodied as a software application, is stored in an executable manner. As already mentioned, the virtual chip card terminal can preferably be embodied by a software application that is executed on a terminal in a suitable computer environment, for example, in a secure data center.

[0021] The terminal is configured to establish a first secure communication connection with an application on a mobile terminal configured for near-field communication (NFC) by means of the virtual chip card terminal, as has already been described above with reference to the first aspect.

[0022] Furthermore, the terminal device is configured to use the virtual chip card terminal to establish a second secure communication connection to a connection element configured to provide secure access to a predefined communication infrastructure. The connection element can be represented, for example, by a secure router or the like.

[0023] According to a preferred embodiment, the connecting element is a connector according to the gematik specification. Only via such a connector can a connection to the telematics infrastructure according to the gematik specification be established. According to gematik specifications, a connector can also be connected to a so-called stationary e-health card terminal and a practice management system (PSV) or a pharmacy management system (AVS). An e-health terminal is used, for example, in a doctor's office to read an electronic health card (eGK) or an electronic health insurance card (eHBA), or to register the practice in the TI using another chip card, the so-called practice card (SMC-B (Security Module Card Type B).

[0024] The terminal device is configured to preferably use a SICCT protocol (see TeleTrusT SICCT Specification V1.2.3, hereinafter "SICCT Specification") for communication between the virtual chip card terminal and the connection element. SICCT stands for "Secure Interoperable Chip Card Terminal." The requirements of this specification arise from the intended (partial) conformity and harmonization of the following norms and standards: ISO / IEC 7816 for contact chip cards, ISO / IEC 14443 (Proximity Cards, PICC) for contactless chip cards, as well as the industry specifications MKT, PC / SC, and EMV.

[0025] Back to the terminal according to the second aspect: The terminal is configured to receive, by means of the virtual chip card terminal via the first secure communication connection, a first message from the application on the mobile terminal, which indicates that a secure communication connection has been established between the application and a chip card.

[0026] Furthermore, the terminal device is configured to transmit a second message to the connecting element, e.g., the connector, via the virtual chip card terminal. This message indicates that the secure communication connection between the application and the chip card has been established. This informs the connecting element that communication with the chip card can now take place.

[0027] Finally, the terminal device is configured to forward commands between the chip card and the connection element by means of the virtual chip card terminal via the first secure communication connection to the application and the second secure communication connection to the connection element.

[0028] In the preferred application case here, with reference to electronic health cards or electronic health professional cards as chip cards and a connector as a connecting element, these commands can relate to at least one of the following example application cases: - e-prescription; - Insured person master data comparison; - Emergency data management; - Electronic medication plan; - Release of an electronic patient record; - Consent, especially for organ donation - Digital signature.

[0029] Details on these applications can be found at gematik, e.g. at https: / / www.gematik.de / anwendungen.

[0030] A third aspect relates to a system comprising at least one terminal according to the second aspect and at least one mobile terminal according to the first aspect.

[0031] The terminal is preferably configured to use the virtual chip card terminal to simultaneously establish a plurality of secure first communication connections to applications which are each executed on different mobile terminals configured for near-field communication (NFC).

[0032] Furthermore, the terminal is preferably configured to simultaneously establish a plurality of secure second communication connections to different connection elements (connectors) by means of the virtual chip card terminal.

[0033] The virtual chip card terminal on the end device can be configured to differentiate between different connectors, for example, as follows: Firstly, the chip card terminal can use multiple network interfaces and thus multiple IP addresses, with each IP address assigned to a connector. Secondly, the chip card terminal can use virtual hosts. This allows an institution, such as a doctor's office, to connect its connector to the following URL: [BSNR].med-united.health. The BSNR is the doctor's office's business location number.

[0034] In order to ensure that an assignment of an application on a mobile device and a chip card connected to it to a connector connected to the virtual chip card terminal on the device is unambiguous in the case that, on the one hand, several applications and, on the other hand, several connectors are connected to the virtual chip card terminal, the application on the mobile device can be set up to transmit information to the virtual chip card terminal for the unambiguous identification of the desired connector when establishing communication with the virtual chip card terminal.

[0035] In practice, a patient could use a search function to locate the desired practice before booking an appointment at a doctor's office. The search function could be integrated into the application on the mobile device. For example, a name or the patient's current location data could be entered as a search term. After selecting a practice and placing the eGK on the patient's smartphone to establish a connection to the virtual chip card terminal, an identifier uniquely identifying the selected practice would be transmitted to the virtual chip card terminal.

[0036] Technically, it is also possible to store doctor data on the eGK, e.g. a prescriber in the medication plan, which would make it possible to use this data to identify a connector in the scenario described above.

[0037] In the manner described, it becomes possible for a single virtual chip card terminal, running on a device in a secure data center, to connect a multitude of chip cards to the specified communications infrastructure via various connectors. This allows multiple organizations, such as doctor's offices, hospitals, or pharmacies, to use the same data center installation of the virtual chip card terminal.

[0038] Particularly in the context of digital medicine, the present application offers a number of additional advantages. An electronic health card or an electronic health professional card can be read from any location using a mobile device described above, on which the described application is installed. No additional hardware is required. Furthermore, the described applications are fully compatible with any common PVS or AVS.

[0039] The invention allows, for example, a patient to verify their identity for a teleconsultation via their smartphone from anywhere. Once the electronic health card has been stored in the system, in addition to the so-called insured person master data management (VSDM), direct billing is also possible. Furthermore, scanning the chip card can be used to activate the electronic patient record (ePA).

[0040] Another application, which is described in more detail below with reference to the figures, is retrieving an e-prescription. According to the present invention, unlike the corresponding gematik app, no eGK PIN is required for this (not to be confused with the CAN described above). Currently, only approximately 1.5% of the German population has a PIN for their eGK. Short description of the characters

[0041] The invention is explained in more detail below using various embodiments and accompanying drawings. The figures show: Fig. 1 schematically shows an initial situation according to the state of the art Fig. 2 shows a scenario according to a first embodiment; Fig. 3 a scenario according to a second embodiment; Fig. 4 schematic steps of an exemplary application, and Fig. 5 so-called SICCT functional units implemented by the virtual chip card terminal. Detailed description of the invention

[0042] Fig. Figure 1 shows an example of a situation according to the state of the art. To read a chip card 20, e.g., an electronic health card (eGK) or an electronic health card (eHBA), of a patient 10, it must be read on-site, e.g., in a doctor's office, using an e-health card terminal 30, for example, using contact technology, as specified by the ISO / EIC 7816 standard. The e-health card terminal 30, in turn, is connected to a connector 40 in the practice, to which, for example, a practice management system 50 can be connected. The practice can only be connected to the telematics infrastructure (not shown) via the connector 40.

[0043] Fig. 2 shows a scenario according to a first embodiment of the present invention.

[0044] A patient 10 holds their chip card (eGK) 20 to an NFC sensor 120 of a mobile terminal 100 described above with reference to the first aspect, e.g., a smartphone with NFC functionality. The described application 140 is installed on this smartphone.

[0045] The mobile terminal is configured to detect that a chip card 20 configured for near-field communication, the electronic health card of the patient 10, is located within communication range of the terminal 100, and to establish a secure communication connection with the chip card 20 by means of the application.

[0046] A secure communication connection can also be established between the application 140 on the mobile device 100 and a virtual chip card terminal 200, which is embodied as a software application and stored executably on a terminal, as described above with reference to the second aspect of the invention. The mobile device 100 is then configured to transmit a message to the virtual chip card terminal 200 via this communication connection using the application 140, indicating that a communication connection has been established between the application 140 and the chip card 20.

[0047] The virtual chip card terminal 200 on the terminal device is, as in Fig. 2, is configured to be connected to the connector 40, as already described above with reference to the second aspect. A connection to the TI (not shown) is established via the connector 40, to which a PVS 50 can in turn be connected.

[0048] The mobile terminal 100 is then configured, by means of the application 140, as described below with reference to Fig. 4, commands that are to be exchanged between the chip card 20 and the connector 40 via the virtual chip card terminal 200 are forwarded to the chip card terminal. Similarly, the terminal is configured to forward, by means of the virtual chip card terminal, such commands that are to be exchanged between the chip card 20 and the connector 40 via the mobile terminal with the application 140 to the application 140 on the mobile terminal 100.

[0049] Fig. 3 illustrates an example scenario according to a second embodiment.

[0050] In contrast to the situation in Fig. 2, a plurality of mobile terminals 100.1, 100.2, 100.3 of different users 10.1, 10.2, 10.3 are provided, each of which has an application 140.1, 140.2, 140.3 installed. The virtual chip card terminal 200 on the terminals is configured to be connected simultaneously to each of these applications 140.1, 140.2, 140.3, preferably, as described, using the MQTT protocol.

[0051] Similarly, the virtual chip card terminal 200 on the terminal device is configured to be connected simultaneously to a plurality of connectors 40.1, 40.2, 40.3 using the SICCT protocol. These connectors 40.1 to 40.4 can be located in various institutions 300.1 to 300.4, e.g., a doctor's office 300.1, a hospital 300.2, a conventional pharmacy 300.3, or an online pharmacy 300.4. Each of the institutions 300.1 to 300.4 logs on to the TI (not shown) with its respective ID card (SMC-B) 60.1 to 60.4 via the respective connector 40.

[0052] The mobile terminal 100 with the application 140 and the terminal on which the virtual chip card terminal 200 is stored as a software application are configured to execute steps of an exemplary method which is described in Fig. 4. These steps are carried out when an insured person's e-prescription is to be retrieved from the TI, more precisely from an e-prescription specialist service 90 located therein. The entire process from the creation of the eGK 20 on the smartphone to the transmission of the retrieved e-prescription to an inventory system of a service provider institution is based on the components described above and is described in Fig. 4 reproduced.

[0053] A wireless communication between the application 140 on the mobile terminal 100 and eGK 20 via the NFC interface between the mobile terminal 100 (in Fig. 4 not shown) and chip card 20 can be "overheard" at short distances. Therefore, a mutually authenticated encrypted secure channel is established between the application 140 and the eGK 20 using "Password Authenticated Connection Establishment" (PACE), as described in Fig. 4 with reference to steps S1 to S3.

[0054] The password is the six-digit Card Access Number (CAN), which is printed on the eGK 20 and stored on the chip of the eGK 20, and is entered by the user in the application 140 (see step S2).

[0055] The secure channel is preferably set up in accordance with the ISO / IEC 14443 specification (see step S3).

[0056] After establishing the secure communication connection to the chip card 20, the application 140 on the mobile terminal 100 can already read data from the chip card 20 (see step S4), which are required for the subsequent execution of the use case TUC_KON_001 “Open card” (see step S7) and FM_VSDM_01 “Read VSD from eGK” (see step S10).

[0057] In preparation for the expected card APDU “INTERNAL AUTHENTICATE”, the healthcare application on the card can also be selected (“SELECT DF.HCA”) and the keys for internal, asymmetric authentication can be selected (“MANAGE SECURITY ENVIRONMENT”).

[0058] The application 140 on the mobile terminal 100 then notifies the virtual chip card terminal 200 on the terminal (see step S5) that a communication connection has been established between the application 140 and the chip card 20.

[0059] Thereafter, as indicated with reference to step S6, the virtual chip card terminal 200 forwards this message to the connector 40.

[0060] In response to this message (SICCT event message slot event "Card inserted"), a card terminal service of connector 40 (according to TIP1-A_4541) initiates the event "CT / SLOT_IN_USE." In response to this, the card service of connector 40 (according to TIP1-A_4563) initiates the execution of the use case TUC_KON_001 "Open Card" (according to the gematik specification, see step S7). This creates a so-called card handle under which the chip card 20 (eGK) can subsequently be addressed.

[0061] The successful opening of the chip card 20 is made known to the AVS 70 together with the card handle (see step S8).

[0062] The AVS 70 then calls the ReadVSD operation of the VSDM specialist module on a SOAP interface of the connector 40 (see step S9). This operation is used to initiate a use case FM_VSDM_01 "Read VSD from eGK" (according to the gematik specification; see step S10). The VSDM specialist module then sends card commands to the virtual chip card terminal 200 on the end device, which forwards them to the application 140 on the mobile device 100 and, via it, to the eGK 20 for response.

[0063] In particular, the card APDU “INTERNAL AUTHENTICATE” must be forwarded.

[0064] As described, the virtual chip card terminal 200 on the terminal implements the transport of card commands from the connector 40 to the eGK 20 on the smartphone 100, and back.

[0065] The virtual chip card terminal 200 on the terminal implements only the Fig.5, see Chapter 5.5.9.1, "Functional Units and Their Multiplicity," of the SICCT specification mentioned above, which are limited to a conventional card slot. Additional functional units, including in particular the display, keypad, RFID antenna, and RFID slot, are not implemented. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited non-patent literature

[0000] ISO / IEC 7816

[0024] ISO / IEC 14443

[0024]

Claims

[1] A mobile terminal configured for near-field communication (NFC) and having an executable application (150) stored thereon, the mobile terminal being configured: - to detect that a chip card (20) configured for near-field communication is located within the communication range of the terminal device; - to establish a secure communication connection with the chip card using the application; - to transmit, by means of the application, a message to a virtual chip card terminal (200) indicating that a communication connection with the chip card has been established; and - to forward commands between the chip card and the virtual chip card terminal using the application. [2] Mobile terminal according to claim 1, wherein the virtual chip card terminal is designed as a software application on an external terminal. [3] Mobile terminal according to claim 1 or 2, wherein the mobile terminal is configured to use an MQTT protocol for communication with the virtual chip card terminal. [4] Mobile terminal according to one of claims 1 to 3, wherein the chip card is an electronic health card, eGK, or an electronic health professional card, eHBA, according to gematik specification. [5] Mobile terminal according to one of claims 1 to 4, wherein the communication connection to the chip card is a connection secured by means of Password Authenticated Connection Establishment, PACE, and wherein a Card Access Number, CAN, of the chip card serves as a password for the PACE. [6] Terminal on which a virtual chip card terminal (200) designed as a software application is stored in an executable manner, wherein the terminal is set up by means of the virtual chip card terminal: - to establish a first secure communication connection with an application (140) on a mobile terminal (100) configured for near-field communication, NFC; - to establish a second secure communication connection to a connection element (40) which is configured to provide secure access to a predetermined communication infrastructure; - to receive a first message from the application indicating that a communication connection has been established between the application and a chip card (20); - to transmit a second message to the connecting element that the communication link between the application and the chip card has been established; - To forward commands between the chip card and the connection element via the first secure communication connection to the application and the second secure communication connection to the connection element. [7] Terminal according to claim 6, wherein the terminal is configured to use an MQTT protocol for communication with the application on the mobile terminal configured for near field communication, NFC. [8] Terminal according to one of claims 6 or 7, wherein the terminal is arranged to use a SICCT protocol for communication with the connecting element. [9] Terminal according to one of claims 6 to 8, wherein the chip card is an electronic health card, eGK, or an electronic health professional card, eHBA, according to gematik specification. [10] Terminal according to one of claims 6 to 9, wherein the connecting element (40) is a connector according to gematik specification, via which a connection to a telematics infrastructure according to gematik specification can be made. [11] Terminal according to claim 9 and 10, wherein the terminal is arranged to forward commands relating to one of the following application cases: - e-prescription; - Insured person master data comparison; - Emergency data management; - Electronic medication plan; - Release of an electronic patient record; - Consent, especially for organ donation - Digital signature. [12] Terminal according to one of claims 6 to 11, wherein the virtual chip card terminal (200) is configured to simultaneously establish a plurality of secure first communication connections to applications (140.1, 140.2, 140.2) which are each executed on different mobile terminals (100.1, 100.2, 100.3) configured for near field communication, NFC. [13] Terminal according to one of claims 6 to 12, wherein the virtual chip card terminal (200) is configured to simultaneously establish a plurality of secure second communication connections to respectively different connection elements (30.1, 40.2, 40.3, 40.4). [14] System comprising at least one terminal according to one of claims 6 to 13 and at least one mobile terminal according to one of claims 1 to 5.

Images