# US 2021/0342460 A1 · Method for synchronizing frame counters and arrangement

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

- Number: US 2021/0342460 A1
- Document ID: US20210342460A1
- Status: Published application
- Kind: A1
- Application number: 17/197,605
- Filed: 2021-03-10
- Published: 2021-11-04
- Earliest claimed: 2020-05-02
- Assignees: Diehl Metering Systems GmbH
- Applicants: Diehl Metering Systems GmbH
- Inventors: BENJAMIN MEYER; CHRISTIAN JAMBOR
- Web page: https://patentgrep.com/patent/US20210342460A1

## CPC

- G06F 21/606: {by securing the transmission between two devices or processes}
- H04W 4/38: for collecting sensor information
- H04J 3/0667: {Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays (arrangements for monitoring round trip delays in packet switching networks H04L43/0864)}
- H04J 3/0682: {by delay compensation, e.g. by compensation of propagation delay or variations thereof, by ranging}
- H04L 9/12: Transmitting and receiving encryption devices synchronised or initially set up in a particular manner
- H04L 9/3271: {using challenge-response}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04W 12/03: Protecting confidentiality, e.g. by encryption
- H04W 12/106: Packet or message integrity
- H04W 12/12: Detection or prevention of fraud
- G06F 2221/2151: Time stamp
- H04L 2463/121: Timestamp
- Y04S 40/18: Network protocols supporting networked applications, e.g. including control of end-device applications over a network
- Y04S 40/20: Information technology specific aspects, e.g. CAD, simulation, modelling, system security
- 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)
- H04J: MULTIPLEX COMMUNICATION (transmission in general H04B; peculiar to transmission of digital information H04L5/00; systems for the simultaneous or sequential transmission of more than one television signal H04N7/08; in exchanges H04Q11/00; stereophonic systems H04S)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y04S: SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS

## Abstract

A method synchronizes frame counters for protecting data transmissions between a first end-device and a second end-device. The data, in particular data frames, are transferred between the first end-device and the second end-device. The data frames are provided with frame counters to protect the data transfer between the first end-device and the second end-device. The second end-device sends a first data frame to the first end-device. The first data frame contains a marker in its payload data. The first end-device sends back a second data frame as an answer to the second end-device. The second data frame contains a frame counter in the header data, and the second data frame contains the frame counter and the marker in its payload data.

## Claims

### Claim 1

A method for synchronizing frame counters to protect data transmissions between a first end-device and a second end-device, which comprises the steps of:
transferring data, via data frames, between the first end-device and the second end-device, wherein the data frames are provided with frame counters to protect a data transfer between the first end-device and the second end-device;
sending, via the second end-device, a first data frame to the first end-device, wherein the first data frame containing a marker in its payload data; and
sending backing, via the first end-device, a second data frame as an answer to the second end-device, wherein the second data frame containing a frame counter in its header data, and the second data frame containing the frame counter and the marker in its payload data.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the second end-device receives the second data frame and compares the frame counter in the header data with the frame counter in the payload data, and compares the marker in the first data frame with the marker in the payload data of the second data frame, and designates the first end-device as trusted on there being a match of the frame counters and of the markers.

### Claim 3 (depends on 2)

The method according to claim 2, wherein:
the marker is a time stamp, the time stamp represents a current time at a time of sending the first data frame; and
the time stamp in the second data frame is checked for plausibility, for which purpose a time of sending the first data frame and delays in transmission and/or processing in the first end-device are taken into account.

### Claim 4 (depends on 2)

The method according to claim 2, wherein:
the marker is a token; and
the second end-device generates the token before sending the first data frame by generating once for synchronization a random number, which acts as the token in the first data frame.

### Claim 5 (depends on 2)

The method according to claim 2, which further comprises sending further data frames from the first end-device to the second end-device which contain incremented frame counters, which are incremented for each further data frame, and, once the first end-device is designated as trusted, a validity of the further data frames from the first end-device is determined in the second end-device by comparing an incremented frame counter contained in a further data frame with an increment of the frame counter of the data frame preceding the further data frame, and the further data frame is deemed valid if the frame counter and the incremented frame counter are consistent.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the frame counter in the header data in the second data frame and the frame counter in the payload data of the second data frame is a frame counter for an uplink.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the second end-device receives the second data frame and compares the frame counter for the uplink in the header data with the frame counter for the uplink in the payload data, and compares the marker in the first data frame with the marker in the payload data of the second data frame, and designates the first end-device as trusted on there being a match of the frame counters for the uplink and of the markers.

### Claim 8 (depends on 6)

The method according to claim 6, wherein the second data frame contains a frame counter for a downlink.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the second end-device is a mobile end-device, wherein the first end-device and the second end-device move at a relative speed to each other.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the relative speed is up to 70 kilometres per hour.

### Claim 11 (depends on 9)

The method according to claim 9, wherein for the data transfer, the relative speed is reduced by less than 50%.

### Claim 12 (depends on 1)

The method according to claim 1, wherein:
the first end-device is an end point, a sensor, a smart meter, or a consumption meter;
the second end-device is a base station, a data collector, or a mobile readout system;
the first data frame is a wake-up data frame; and
the second data frame contains the frame counter and the marker in encrypted, payload data.

### Claim 13 (depends on 6)

The method according to claim 6, wherein the second data frame contains in the payload data, a frame counter for a downlink.

### Claim 14 (depends on 9)

The method according to claim 9, wherein the relative speed is up to 50 kilometres per hour.

### Claim 15 (depends on 9)

The method according to claim 9, wherein for the data transfer, the relative speed is reduced by less than 20%.

### Claim 16 (depends on 9)

The method according to claim 9, wherein for the data transfer, the relative speed is reduced by less than 10%.

### Claim 17 (depends on 9)

The method according to claim 9, wherein for the data transfer no reduction in relative speed takes place.

### Claim 18 (depends on 1)

A configuration for transmitting data, the configuration comprising:
a first end-device;
a second end-device; and
said first end-device and said second end-device each containing communication means in order to transfer data frames between said first end-device and said second end-device, wherein the data frames are provided with frame counters to protect a data transfer between said first end-device and said second end-device, and in order to protect data transmissions, said frame counters are synchronized according to a method of claim 1.
