# US 2024/0187498 A1 · Stale cache data in charging function

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

- Number: US 2024/0187498 A1
- Document ID: US20240187498A1
- Status: Published application
- Kind: A1
- Application number: 18/062,323
- Filed: 2022-12-06
- Published: 2024-06-06
- Earliest claimed: 2022-12-06
- Assignees: T-Mobile USA, Inc.
- Applicants: T-Mobile USA, Inc.
- Inventors: Muhammad Zaeem Afzal
- Web page: https://patentgrep.com/patent/US20240187498A1

## CPC

- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04M 15/66: {Policy and charging system}
- H04M 15/8228: {Session based}
- H04W 4/24: Accounting or billing
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- 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 charging function (CHF) of a carrier network may perform charging operations despite stale cache data. For example, the CHF may request that a first subscriber database server (SDS) perform operations associated with a charging request associated with a subscriber based on a mapping of the subscriber to the first SDS in the cache of the CHF. The CHF may receive a response indicating the first SDS failed to perform the operations associated with the charging request and request a mapping of the subscriber to a SDS of a plurality of SDSs from a server mapping subscribers of the carrier network to respective SDSs of the plurality of SDSs. The CHF may receive a mapping of the subscriber to a second SDS of the plurality of SDSs and request that the second SDS perform the operations associated with the charging request.

## Claims

### Claim 1

A method comprising:
requesting, by a charging function (CHF) of a carrier network, that a first subscriber database server (SDS) perform operations associated with a charging request, wherein:
the charging request is associated with a subscriber in a subscriber database maintained by a plurality of SDSs including the first SDS; and
the first SDS is mapped to the subscriber in a cache of the CHF;
receiving, by the CHF and from the first SDS, a response indicating the first SDS failed to perform the operations associated with the charging request;
requesting, by the CHF and based on the response from the first SDS, a mapping of the subscriber to a SDS of the plurality of SDSs from a mapping server mapping subscribers of the carrier network to respective SDSs of the plurality of SDSs;
receiving, by the CHF and from the mapping server, the mapping of the subscriber to a second SDS of the plurality of SDSs; and
requesting, by the CHF, that the second SDS perform the operations associated with the charging request.

### Claim 2 (depends on 1)

The method of claim 1, wherein the charging request is one of an update charging request associated with a charging session associated with the subscriber or a terminate charging request associated with the charging session.

### Claim 3 (depends on 1)

The method of claim 1, wherein the response from the first SDS indicating the first SDS failed to perform the operations associated with the charging request indicates that the subscriber was not found in a portion of the subscriber database maintained by the first SDS.

### Claim 4 (depends on 1)

The method of claim 1, wherein the mapping server is a domain name system (DNS) server.

### Claim 5 (depends on 1)

The method of claim 1, further comprising, prior to requesting the first SDS perform the operations associated with the charging request:
receiving, by the CHF, the charging request from a session management function (SMF); and
retrieving a cached mapping of the subscriber to the first SDS of the plurality of SDSs from the cache of the CHF, wherein the requesting the first SDS perform the operations associated with the charging request is based at least in part on the cached mapping.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving, by the CHF, a response from the second SDS indicating the second SDS successfully performed the operations associated with the charging request; and
sending, to an SMF associated with the charging request, a charging response indicating the charging request was performed.

### Claim 7 (depends on 1)

The method of claim 1, wherein the mapping of the subscriber to the second SDS of the plurality of SDSs includes an identifier of the second SDS.

### Claim 8 (depends on 1)

The method of claim 1, wherein the charging request is associated with usage by the subscriber of 5G services of the carrier network.

### Claim 9

A system comprising:
one or more computing devices of a first carrier configured to perform actions comprising:
requesting, by a charging function (CHF) of a carrier network, that a first subscriber database server (SDS) perform operations associated with a charging request, wherein:
the charging request is associated with a subscriber in a subscriber database maintained by a plurality of SDSs including the first SDS; and
the first SDS is mapped to the subscriber in a cache of the CHF;
receiving, by the CHF and from the first SDS, a response indicating the first SDS failed to perform the operations associated with the charging request;
requesting, by the CHF and based on the response from the first SDS, a mapping of the subscriber to a SDS of the plurality of SDSs from a mapping server mapping subscribers of the carrier network to respective SDSs of the plurality of SDSs;
receiving, by the CHF and from the mapping server, the mapping of the subscriber to a second SDS of the plurality of SDSs; and
requesting, by the CHF, that the second SDS perform the operations associated with the charging request.

### Claim 10 (depends on 9)

The system of claim 9, wherein the charging request is one of a update charging request associated with a charging session associated with the subscriber or a terminate charging request associated with the charging session.

### Claim 11 (depends on 9)

The system of claim 9, wherein the response from the first SDS indicating the first SDS failed to perform the operations associated with the charging request indicates that the subscriber was not found in a portion of the subscriber database maintained by the first SDS.

### Claim 12 (depends on 9)

The system of claim 9, wherein the actions further comprise, prior to requesting the first SDS perform the operations associated with the charging request:
receiving, by the CHF, the charging request from a session management function (SMF); and
retrieving a cached mapping of the subscriber to the first SDS of the plurality of SDSs from the cache of the CHF, wherein the requesting the first SDS perform the operations associated with the charging request is based at least in part on the cached mapping.

### Claim 13 (depends on 9)

The system of claim 9, wherein the actions further comprise:
receiving, by the CHF, a response from the second SDS indicating the second SDS successfully performed the operations associated with the charging request; and
sending, to an SMF associated with the charging request, a charging response indicating the charging request was performed.

### Claim 14 (depends on 9)

The system of claim 9, wherein the charging request is associated with usage by the subscriber of 5G services of the carrier network.

### Claim 15

A non-transitory computer-readable media storing computer-executable instructions, which when executed by one or more processors, cause the one or more processors to perform actions comprising:
requesting, by a charging function (CHF) of a carrier network, that a first subscriber database server (SDS) perform operations associated with a charging request, wherein:
the charging request is associated with a subscriber in a subscriber database maintained by a plurality of SDSs including the first SDS; and
the first SDS is mapped to the subscriber in a cache of the CHF;
receiving, by the CHF and from the first SDS, a response indicating the first SDS failed to perform the operations associated with the charging request;
requesting, by the CHF and based on the response from the first SDS, a mapping of the subscriber to a SDS of the plurality of SDSs from a mapping server mapping subscribers of the carrier network to respective SDSs of the plurality of SDSs;
receiving, by the CHF and from the mapping server, the mapping of the subscriber to a second SDS of the plurality of SDSs; and
requesting, by the CHF, that the second SDS perform the operations associated with the charging request.

### Claim 16 (depends on 15)

The non-transitory computer-readable media of claim 15, wherein the charging request is one of a update charging request associated with a charging session associated with the subscriber or a terminate charging request associated with the charging session.

### Claim 17 (depends on 15)

The non-transitory computer-readable media of claim 15, wherein the response from the first SDS indicating the first SDS failed to perform the operations associated with the charging request indicates that the subscriber was not found in a portion of the subscriber database maintained by the first SDS.

### Claim 18 (depends on 15)

The non-transitory computer-readable media of claim 15, wherein the actions further comprise, prior to requesting the first SDS perform the operations associated with the charging request:
receiving, by the CHF, the charging request from a session management function (SMF); and
retrieving a cached mapping of the subscriber to the first SDS of the plurality of SDSs from the cache of the CHF, wherein the requesting the first SDS perform the operations associated with the charging request is based at least in part on the cached mapping.

### Claim 19 (depends on 15)

The non-transitory computer-readable media of claim 15, wherein the actions further comprise:
receiving, by the CHF, a response from the second SDS indicating the second SDS successfully performed the operations associated with the charging request; and
sending, to an SMF associated with the charging request, a charging response indicating the charging request was performed.

### Claim 20 (depends on 15)

The non-transitory computer-readable media of claim 15, wherein the charging request is associated with usage by the subscriber of 5G services of the carrier network.
