# US 2023/0413118 A1 · Apparatus and method for background data transfer

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

- Number: US 2023/0413118 A1
- Document ID: US20230413118A1
- Status: Published application
- Kind: A1
- Application number: 18/240,391
- Filed: 2023-08-31
- Published: 2023-12-21
- Earliest claimed: 2017-03-17
- Assignees: NEC Corporation
- Applicants: NEC Corporation
- Inventors: Takanori IWAI; Toshiyuki Tamura
- Web page: https://patentgrep.com/patent/US20230413118A1

## CPC

- 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}
- H04W 28/18: Negotiating wireless communication parameters
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04M 3/00: Automatic or semi-automatic exchanges
- H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]}
- H04M 15/42: {Dynamic individual rates per user}
- H04M 15/50: {for cross-charging network operators}
- H04M 15/51: {for resellers, retailers or service providers}
- H04M 15/66: {Policy and charging system}
- H04M 15/8083: {involving reduced rates or discounts, e.g. time-of-day reductions or volume discounts}
- H04W 4/24: Accounting or billing
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- 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)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An exposure node (50) receives a first request for resource management for future background data transfer between an application service provider and a plurality of radio terminals (10) from a server (60) associated with the application service provider and send a second request to a policy control node (40) in response to receiving the first request. The first request includes a parameter indicating whether background data transfer not complying with a previously agreed or negotiated transfer policy should be stopped, or whether the background data transfer should continue under a charging rule different from a previously agreed charging rule. The second request includes the parameter obtained from the first request. This enables the application service provider to negotiate with the radio communication network about handling of background data transfer not complying with a previously agreed transfer policy.

## Claims

### Claim at position 1

1-12. (canceled)

### Claim 13

A policy function entity comprising:
at least one memory storing instructions;
at least one processor configured to execute the instructions to retrieve policy information based on a reference identifier (ID) for a background data transfer provided by an application function entity; and
an interface configured to send the policy information for the background data transfer to a user equipment (UE),
wherein the policy information comprises a time window and a location criteria.

### Claim 14 (depends on 13)

The policy function entity according to claim 13, further comprising at least one of a Policy and Charging Rules Function (PCRF) and a Policy Control function (PCF).

### Claim 15 (depends on 13)

The policy function entity according to claim 13, wherein the application function entity comprises an Application Function (AF).

### Claim 16

A User Equipment (UE) comprising:
a transceiver configured to receive policy information for a background data transfer from a policy function entity,
wherein the policy information comprises a time window and a location criteria, and
wherein the policy information is retrieved by the policy function entity based on a reference identifier (ID) for the background data transfer provided by an application function entity, and
wherein the policy information is received by the UE.

### Claim 17 (depends on 16)

The method according to claim 16, wherein the policy function entity comprises at least one of a Policy and Charging Rules Function (PCRF) and a Policy Control function (PCF).

### Claim 18 (depends on 16)

The method according to claim 16,
wherein the application function entity comprises an Application Function (AF).

### Claim 19

A method performed by a policy function entity, the method comprising:
retrieving policy information based on a reference identifier (ID) for a background data transfer provided by an application function entity; and
sending the policy information for the background data transfer to a user equipment (UE),
wherein the policy information comprises a time window and a location criteria.

### Claim 20 (depends on 19)

The method according to claim 19, wherein the policy function entity comprises at least one of a Policy and Charging Rules Function (PCRF) and a Policy Control function (PCF).

### Claim 21 (depends on 19)

The method according to claim 19, wherein the application function entity comprises an Application Function (AF).

### Claim 22

A method performed by a User Equipment (UE), the method comprising:
receiving policy information for a background data transfer from a policy function entity,
wherein the policy information comprises a time window and a location criteria, and
wherein the policy information is retrieved by the policy function entity based on a reference identifier (ID) for the background data transfer provided by an application function entity, and
wherein the policy information is received by the UE.

### Claim 23 (depends on 22)

The method according to claim 22, wherein the policy function entity comprises at least one of a Policy and Charging Rules Function (PCRF) and a Policy Control function (PCF).

### Claim 24 (depends on 22)

The method according to claim 22, wherein the application function entity comprises an Application Function (AF).
