# US 2019/0245861 A1 · Method for user administration of a field device

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0245861 A1
- Document ID: US20190245861A1
- Status: Published application
- Kind: A1
- Application number: 16/268,732
- Filed: 2019-02-06
- Published: 2019-08-08
- Earliest claimed: 2018-02-06
- Assignees: Endress+Hauser Conducta GmbH+Co. KG
- Applicants: Endress+Hauser Conducta GmbH+Co. KG
- Inventors: Björn Haase; Thomas Alber; Günter Jahl
- Web page: https://patentgrep.com/patent/US20190245861A1

## CPC

- H04L 63/102: {Entity profiles}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04L 9/0841: {involving Diffie-Hellman or related key agreement protocols}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/3247: {involving digital signatures}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 63/126: {the source of the received data}
- H04W 12/009: {specially adapted for networks, e.g. wireless sensor networks, ad-hoc networks, RFID networks or cloud networks}
- H04W 12/06: Authentication
- H04W 12/08: Access security
- H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)}
- H04L 63/123: {received data contents, e.g. message integrity}
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure relates to a method for user administration of a field device of process automation technology, comprising the steps of connecting a transport medium, such as a smartphone, to a user database, synchronizing user data from the user database with the transport medium, and connecting the transport medium to the field device. The method also includes transmitting the user data from the transport medium to the field device, checking of the user data by the field device, and granting access to the field device on the basis of verified valid user data.

## Claims

### Claim 1

A method for user administration of a field device of process automation technology, comprising steps of:
connecting a transport medium to a user database;
synchronizing user data from the user database with the transport medium;
connecting the transport medium to the field device;
transmitting the user data from the transport medium to the field device;
checking of the user data by the field device; and
granting access to the field device on the basis of verified valid user data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the user data comprise at least one ticket, and wherein the at least one ticket is user-specific and field device-specific.

### Claim 3 (depends on 2)

The method of claim 2, wherein the at least one ticket is created exclusively by the user database.

### Claim 4 (depends on 2)

The method of claim 2, wherein a public key of the field device and a public key of the user database are exchanged via the transport medium.

### Claim 5 (depends on 4)

The method of claim 4, wherein the field device computes a shared secret from the public key of the user database and a private key; and wherein the user database computes the shared secret from the public key of the field device and a private key of the user database.

### Claim 6 (depends on 5)

The method of claim 5, wherein the shared secret is exchanged via the transport medium.

### Claim 7 (depends on 6)

The method of claim 6, wherein the at least one ticket includes one or more of the following characteristic data: user name; password; encrypted password; identification of the transport medium; serial number of the field device; rights; revision counter; validity counter; validity from “validity counter;” validity until “validity counter;” access type; validity duration; valid from; valid to; date of the ticket creation; and a function code; and wherein the function code one of remove, add, and forceflag.

### Claim 8 (depends on 7)

The method of claim 7, wherein the at least one ticket corresponding to a currently logged-on user at the transport medium and including the function code of forceflag is transmitted.

### Claim 9 (depends on 8)

The method of claim 8, wherein the characteristic data are encrypted with a first key derived from the shared secret.

### Claim 10 (depends on 9)

The method of claim 9, wherein the at least one ticket in the field device is encrypted based on the shared secret.

### Claim 11 (depends on 10)

The method of claim 10, wherein the at least one ticket includes a nonce.

### Claim 12 (depends on 11)

The method of claim 11, wherein the at least one ticket includes a message authentication code.

### Claim 13 (depends on 12)

The method of claim 12, wherein the message authentication code is computed and verified with a second key derived from the shared secret.

### Claim 14 (depends on 13)

The method of claim 13, wherein the at least one ticket includes a signature generated from the private key of the user database and verified from the public key of the user database.

### Claim 15 (depends on 14)

The method of claim 14, wherein the at least one ticket is encrypted and authenticated using symmetric keys that each field device shares with the central user database.

### Claim 16 (depends on 15)

The method of claim 15, wherein the at least one ticket is exchanged via an unencrypted channel before the authentication is carried out.

### Claim 17 (depends on 16)

The method of claim 16, wherein the at least one ticket includes payload data information for a key exchange or an authentication protocol.

### Claim 18 (depends on 16)

The method of claim 16, wherein the at least one ticket contains payload data information about a smart card, and wherein the payload data information is sued for a key exchange to an authentication protocol which incorporates keys stored on the smart card.

### Claim 19 (depends on 18)

The method of claim 18, wherein the at least one encrypted ticket includes payload information data about a control device, and wherein the payload data information is used for a key exchange or an authentication protocol which incorporates keys stored on the control device.
