# US 2019/0246247 A1 · Sdci pull and push mode optimization

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

- Number: US 2019/0246247 A1
- Document ID: US20190246247A1
- Status: Published application
- Kind: A1
- Application number: 16/340,518
- Filed: 2016-10-09
- Published: 2019-08-08
- Earliest claimed: 2016-10-09
- Assignees: Nokia Solutions and Networks Oy
- Applicants: Nokia Solutions and Networks Oy
- Inventors: Yang SHEN
- Web page: https://patentgrep.com/patent/US20190246247A1

## CPC

- H04W 4/24: Accounting or billing
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/09: {Third party charged communications}
- H04M 15/66: {Policy and charging system}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- 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)

## Abstract

A method, apparatus, and machine readable non-transitory storage medium for a SDCI pull and push mode optimization are provided, which comprise synchronizing a caching timer and an allowed delay between a Policy and Charging Enforcement Function (PCEF) and a Packet Flow Description Function (PFDF); comparing the caching timer and the allowed delay; and pushing an updated Packet Flow Description (PFD) from the PFDF to the PCEF based on a result of the comparing.

## Claims

### Claim 1

A method, comprising:
synchronizing a caching timer and an allowed delay between a policy and charging enforcement function (PCEF) or a traffic detection function (TDF) and a packet flow description function (PFDF);
comparing the caching timer and the allowed delay; and
pushing an updated packet flow description (PFD) from the PFDF to the PCEF or to the TDF, respectively, based on a result of the comparing.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the synchronizing comprises:
sending a PFD fetching request which includes an application identifier from the PCEF or from the TDF, respectively, to the PFDF.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising:
triggering a reset of the caching timer based on a preconfigured value in the PFDF, when the PFD fetching request is received.

### Claim 4

(canceled)

### Claim 5 (depends on 2)

The method according to claim 2, further comprising:
determining a validity of the application identifier based on the caching timer,
wherein the updated PFD is associated with the valid application identifier.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the determining comprises:
determining the application identifier is not valid, if the caching timer expires and no new PFD fetching request for the application identifier is received.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the pushing comprises:
distributing the updated PFD directly from the PFDF to the PCEF or to the TDF, respectively, or notifying the PCEF or, the TDF, respectively, to fetch the updated PFD within the allowed delay, if the allowed delay is smaller than the caching timer.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the synchronizing comprises:
sending a PFD updating notification from the PFDF to the PCEF or to the TDF, respectively,
wherein the PFD updating notification includes an application identifier and the allowed delay.

### Claim 9

(canceled)

### Claim 10 (depends on 8)

The method according to claim 8, further comprising:
determining a validity of the application identifier based on the caching timer.

### Claim 11 (depends on 10)

The method according to claim 10, further comprising:
sending a PFD fetching request from the PCEF or from the TDF, respectively, to the PFDF, if the allowed delay is smaller than the caching timer;
wherein the PFD fetching request only includes the valid application identifier.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the pushing comprises:
pushing the updated PFD associated with the PFD fetching request.

### Claim 13

(canceled)

### Claim 14

An apparatus, comprising:
at least one processor; and
at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to perform a process comprising:
synchronizing a caching timer and an allowed delay between a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), and a packet flow description function (PFDF);
comparing the caching timer and the allowed delay; and
pushing an updated packet flow description (PFD) from the PFDF to the PCEF or to the TDF, respectively, based on a result of the comparing.

### Claim 15 (depends on 14)

The apparatus according to claim 14, wherein the synchronizing comprises:
sending a PFD fetching request which includes an application identifier from the PCEF or from the TDF, respectively, to the PFDF.

### Claim 16 (depends on 14)

The apparatus according to claim 14, wherein the triggering comprises:
triggering a reset of the caching timer based on a preconfigured value in the PFDF, when the PFD fetching request is received.

### Claim 17

(canceled)

### Claim 18 (depends on 15)

The apparatus according to claim 15, further comprising:
determining a validity of the application identifier based on the caching timer,
wherein the updated PFD is associated with the valid application identifier.

### Claim 19 (depends on 18)

The apparatus according to claim 18, wherein the determining comprises:
determining the application identifier is not valid, if the caching timer expires and no new PFD fetching request for the application identifier is received.

### Claim 20 (depends on 14)

The apparatus according to claim 14, wherein the pushing comprises:
distributing the updated PFD directly from the PFDF to the PCEF or to the TDF, respectively, or notifying the PCEF or the TDF, respectively, to fetch the updated PFD within the allowed delay, if the allowed delay is smaller than the caching timer.

### Claim 21 (depends on 14)

The apparatus of claim 14, wherein the synchronizing comprises:
sending a PFD updating notification from the PFDF to the PCEF or to the TDF, respectively,
wherein the PFD updating notification includes an application identifier and the allowed delay.

### Claim 22

(canceled)

### Claim 23 (depends on 21)

The apparatus according to claim 21, further comprising:
determining a validity of the application identifier based on the caching timer.

### Claim 24 (depends on 23)

The apparatus according to claim 23, further comprising:
sending a PFD fetching request from the PCEF or from the TDF, respectively, to the PFDF, if the allowed delay is smaller than the caching timer;
wherein the PFD fetching request only includes the valid application identifier.

### Claim 25 (depends on 24)

The apparatus according to claim 24, wherein the pushing comprises:
pushing the updated PFD associated with the PFD fetching request.

### Claim at position 26

-39. (canceled)
