# US 2018/0324307 A1 · Charging Record Authentication for Anonymized Network Service Utilization

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

- Number: US 2018/0324307 A1
- Document ID: US20180324307A1
- Status: Published application
- Kind: A1
- Application number: 15/774,023
- Filed: 2015-11-24
- Published: 2018-11-08
- Earliest claimed: 2015-11-24
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Thomas Weidenfeller
- Web page: https://patentgrep.com/patent/US20180324307A1

## CPC

- H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]}
- H04M 15/04: Recording calls {, or communications} in printed, perforated or other permanent form
- H04M 15/06: Recording class or number of calling {, i.e. A-party} or called party {, i.e. B-party}
- H04M 15/48: {Secure or trusted billing, e.g. trusted elements or encryption}
- H04M 15/857: {Cumulative charges}
- H04M 17/103: {using SIMs (USIMs) or calling cards}
- H04W 4/24: Accounting or billing
- H04W 12/041: Key generation or derivation
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04W 12/069: using certificates or pre-shared keys
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A user device (10) provides a subscriber with access to a network service. The user device (10) determines service-specific key material and charging-specific key material. The user device (10) determines a charging record indicating usage of the network service by the subscriber and associates the charging record with first authentication information based on the charging-specific key material. The user device (10) generates at least one message including the charging record and the associated first authentication information. The user device (10) associates the at least one message with second authentication information based on the service-specific key material. The user device (10) sends the at least one message to a first network node (150) which is incapable of relating the charging-specific key material or the service-specific key material to a subscriber identity of the subscriber. The first network node (150) receives the at least one message and the associated second authentication information from the user device (10) and authenticates the at least one message based on the service-specific key material and the second authentication information. In response to authenticating the at least one message, the first network node forwards the charging record and the associated first authentication information to a second network node (120). The second network node (120) is capable of relating the charging-specific key material to the subscriber identity of the subscriber. The second network node (120) receives the charging record and the associated first authentication information from the first network node (150) and authenticates the charging record based on the charging-specific key material and the first authentication information. In response to authenticating the charging record, the second network node (120) controls charging of the network service.

## Claims

### Claim at position 1

1-65. (canceled)

### Claim 66

A method of controlling utilization of a network service, the method comprising a user device:
providing a subscriber with access to a network service;
determining service-specific key material;
determining charging-specific key material;
determining a charging record indicating usage of the network service by the subscriber;
associating the charging record with first authentication information based on the charging-specific key material;
generating at least one message comprising the charging record and the associated first authentication information;
associating the at least one message with second authentication information based on the service-specific key material; and
sending the at least one message and the associated second authentication information to a network node which is incapable of relating any of the service-specific key material and the charging-specific key material to a subscriber identity of the subscriber.

### Claim 67 (depends on 66)

The method of claim 66, further comprising the user device deriving the charging-specific key material:
from the subscriber identity; or
from the subscriber identity and the service-specific key material.

### Claim 68 (depends on 66)

The method of claim 66, further comprising the user device receiving a response from the network node, the response indicating that usage of the network service by the subscriber is authorized.

### Claim 69 (depends on 66)

The method of claim 66, further comprising the user device:
determining generic key material through interaction with another network node; and
deriving the charging-specific key material and/or the service-specific key material from the generic key material.

### Claim 70

A method of controlling utilization of a network service, the method comprising a network node:
providing access to a network service through a user device connected to the network node;
receiving, from the user device, at least one message and first authentication information associated with the at least one message, the first authentication information being based on service-specific key material, the at least one message comprising a charging record and second authentication information associated with the charging record, the charging record indicating usage of the network service by a subscriber, the second authentication information being based on charging-specific key material; wherein the network node is incapable of relating any of the service-specific key material and the charging-specific key material to a subscriber identity of the subscriber;
authenticating the at least one message based on the service-specific key material and the first authentication information; and
in response to authenticating the at least one message, forwarding the charging record and the associated second authentication information to a further network node which is capable of relating the charging-specific key material to a subscriber identity of the subscriber.

### Claim 71 (depends on 70)

The method of claim 70, wherein the charging-specific key material is derived:
from the subscriber identity;
from the subscriber identity and the service-specific key material.

### Claim 72 (depends on 70)

The method of claim 70, further comprising the network node receiving the service-specific key material from another network node.

### Claim 73 (depends on 70)

The method of claim 70, further comprising the network node receiving a response from the further network node, the response indicating whether the charging record was authenticated by the further network node.

### Claim 74

A method of controlling utilization of a network service, the method comprising a network node:
determining charging-specific key material related to a subscriber identity of a subscriber;
receiving, from a further network node, a charging record and authentication information associated with the charging record, the charging record indicating usage of a network service by the subscriber and being based on the charging-specific key material; wherein the further network node is incapable of relating the charging-specific key material to the subscriber identity of the subscriber;
authenticating the charging record based on the charging-specific key material and the associated authentication information; and
controlling, in response to authenticating the charging record, charging of the network service.

### Claim 75 (depends on 74)

The method of claim 74, further comprising the network node deriving the charging-specific key material from the subscriber identity.

### Claim 76 (depends on 74)

The method of claim 74, further comprising the network node:
receiving service-specific key material from another network node; and
deriving the charging-specific key material from the subscriber identity and the service-specific key material.

### Claim 77 (depends on 74)

The method of claim 74, further comprising the network node sending a response to the further network node, the response indicating:
whether the charging record was authenticated by the network node; or whether charging of the network service is authorized for the subscriber.

### Claim 78

A user device, the user device comprising:
processing circuitry;
memory containing instructions executable by the processing circuitry whereby the user device is operative to:
provide a subscriber with access to a network service;
determine service-specific key material;
determine charging-specific key material;
determine a charging record indicating usage of the network service by the subscriber;
associate the charging record with first authentication information based on the charging-specific key material;
generate at least one message comprising the charging record and the associated first authentication information;
associate the at least one message with second authentication information based on the service-specific key material; and
send the at least one message and the associated second authentication information to a network node which is incapable of relating any of the charging-specific key material and the service-specific key material to a subscriber identity of the subscriber.

### Claim 79 (depends on 78)

The user device of claim 78, wherein the instructions are such that the user device is operative to derive the charging-specific key material from the subscriber identity.

### Claim 80 (depends on 78)

The user device of claim 78, wherein the instructions are such that the user device is operative to receive a response from the network node, the response indicating that usage of the network service by the subscriber is authorized.

### Claim 81 (depends on 78)

The user device of claim 78, wherein the instructions are such that the user device is operative to:
determine generic key material through interaction with another network node; and
derive the charging-specific key material and/or the service-specific key material from the generic key material.

### Claim 82 (depends on 78)

The user device of claim 78, wherein the at least one message includes an identifier associated with the charging-specific key material and the service-specific key material.

### Claim 83

A network node, the network node, comprising:
processing circuitry;
memory containing instructions executable by the processing circuitry whereby the network node is operative to:
provide access to a network service through a user device connected to the network node;
receive, from the user device, a at least one message and first authentication information associated with the at least one message, the first authentication information being based on service-specific key material, the at least one message comprising a charging record and second authentication information associated with the charging record, the charging record indicating usage of the network service by a subscriber, the second authentication information being based on charging-specific key material, wherein the network node is incapable of relating any of the charging-specific key material and the service-specific key material to a subscriber identity of the subscriber;
authenticate of the at least one message based on the service-specific key material and the first authentication information; and
forward, in response to authenticating the at least one message, the charging record and the associated second authentication information to a further network node which is capable of relating the charging-specific key material to the subscriber identity of the subscriber.

### Claim 84 (depends on 83)

The network node of claim 83, wherein the instructions are such that the network node is operative to derive the charging-specific key material from the subscriber identity.

### Claim 85 (depends on 83)

The network node of claim 83, wherein the instructions are such that the network node is operative to receive the service-specific key material from another network node.

### Claim 86 (depends on 83)

The network node of claim 83, wherein the instructions are such that the network node is operative to receive a response from the further network node, the response indicating:
whether the charging record was authenticated by the further network node; or
whether charging of the network service is authorized for the subscriber.

### Claim 87

A network node, the network node comprising:
processing circuitry;
memory containing instructions executable by the processing circuitry whereby the network node is operative to:
determine charging-specific key material related to a subscriber identity of a subscriber;
receive, from a further network node, a charging record and authentication information associated with the charging record, the charging record indicating usage of a network service by a subscriber, the authentication information being based on the charging-specific key material; wherein the further network node is incapable of relating the charging-specific key material to the subscriber identity of the subscriber;
authenticate the charging record based on the charging-specific key material and the associated authentication information; and
control charging of the network service in response to authenticating the charging record.

### Claim 88 (depends on 87)

The network node of claim 87, wherein the instructions are such that the network node is operative to derive the charging-specific key material from the subscriber identity.

### Claim 89 (depends on 88)

The network node of claim 88, wherein the instructions are such that the network node is operative to:
receive service-specific key material from another network node; and
derive the charging-specific key material from the subscriber identity and the service-specific key material.

### Claim 90 (depends on 89)

The network node of claim 89, wherein the instructions are such that the network node is operative to:
receive the charging record in a message which further includes an identifier; and
receive the service-specific key material based on the identifier.

### Claim 91 (depends on 87)

The network node of claim 87, wherein the instructions are such that the network node is operative to send a response to the further network node, the response indicating:
whether the charging record was authenticated by the network node;
whether charging of the network service is authorized for the subscriber.
