# US 2026/0238506 A1 · Methods and systems for policy and charging control rule generation

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

- Number: US 2026/0238506 A1
- Document ID: US20260238506A1
- Status: Published application
- Kind: A1
- Application number: 19/147,949
- Filed: 2023-01-17
- Published: 2026-08-13
- Earliest claimed: 2023-01-17
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Rémi ROBERT; Arif AHMED
- Web page: https://patentgrep.com/patent/US20260238506A1

## CPC

- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04M 15/66: {Policy and charging system}
- H04M 15/8033: {location-dependent, e.g. business or home}
- H04M 15/8038: {Roaming or handoff}
- H04M 15/81: {Dynamic pricing, e.g. change of tariff during call}
- 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

Embodiments include methods, electronic device, storage medium, and computer program for policy and charging control rule generation. In one embodiment, a method is to be implemented for policy and charging control rule generation, the method comprising: receiving a first policy and charging control rule that identifies an edge application, a location of the edge application, and policy information for the edge application; generating a second policy and charging control rule for a user equipment (UE) interacting with an edge application server of the edge application based on the first policy and charging control rule, the second policy and charging control rule identifying the policy information for the edge application and an Internet Protocol (IP) address corresponding to the edge application server; and causing application of the second policy and charging control rule on a traffic flow between the UE and the edge application server.

## Claims

### Claim 1

A method to be implemented in a network node of a network for policy and charging control rule generation, the method comprising:
receiving a first policy and charging control rule that identifies an edge application, a location of the edge application, and policy information for the edge application;
generating a second policy and charging control rule for a user equipment interacting with an edge application server of the edge application based on the first policy and charging control rule, the second policy and charging control rule identifying the policy information for the edge application and an Internet Protocol address corresponding to the edge application server; and
causing application of the second policy and charging control rule on a traffic flow between the UE and the edge application server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first policy and charging control rule identifies the edge application through one or more of an edge application identifier of the edge application and a domain name of the edge application.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
initiating a query to a network exposure function (NEF) about the edge application; and
receiving additional information from the NEF to be used for generating the second policy and charging control rule.

### Claim 4 (depends on 1)

The method of claim 1, wherein upon the edge application server being created, the network node receives a first notification that indicates information of the edge application server, including:
one or more of an edge application identifier of the edge application and a domain name of the edge application,
the IP address corresponding to the edge application server; and
a location of the edge application server.

### Claim 5 (depends on 4)

The method of claim 4, wherein the network node receives the first notification responsive to the network node subscribing to lifecycle event notification regarding the edge application.

### Claim 6 (depends on 4)

The method of claim 4, wherein the network node stores the information of the edge application server and the first policy and charging control rule in a datastore coupled to the network node.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first policy and charging control rule is stored in the datastore with a search key being one or more of the edge application identifier of the edge application and the domain name of the edge application.

### Claim 8 (depends on 4)

The method of claim 4, wherein generating the second policy and charging control rule for interacting with the edge application server based on the first policy and charging control rule is responsive to receiving a second notification that indicates:
one or more of the edge application identifier of the edge application server and the domain name of the edge application, and
the IP address corresponding to the edge application server.

### Claim 9 (depends on 1)

The method of claim 1, wherein the edge application server is discovered through one or more of an edge application server discovery function (EASDF), a domain name system (DNS) server, and an edge enabler server of the network.

### Claim 10 (depends on 9)

The method of claim 9, wherein one or more of the IP address corresponding to the edge application server and other attributes of the edge application server are obtained responsive to a request initiated from the UE.

### Claim 11 (depends on 10)

The method of claim 10, wherein the UE initiates the request upon moving to a new location.

### Claim 12 (depends on 9)

The method of claim 9, wherein the network node discovers the edge application server responsive to subscription of the network node for notification from one or more the EASDF, the DNS, and the edge enabler server of the network.

### Claim 13 (depends on 1)

The method of claim 1, wherein the application of the second policy and charging control rule comprises causing the UE to be charged for the traffic flow between the UE and the edge application server using the second policy and charging control rule.

### Claim 14 (depends on 13)

The method of claim 13, wherein causing the UE to be charged for the traffic flow between the UE and the edge application server using the second policy and charging control rule comprises transforming one or more attributes of the edge application server into a parameter mapping to a charging key.

### Claim 15 (depends on 1)

The method of claim 1, wherein the network node implements a session management function (SMF) for the policy and charging control rule generation.

### Claim 16

A network node to perform policy and charging control rule generation in a network, comprising:
a processor and machine-readable storage medium that provides instructions that, when executed by the processor, are capable of causing the processor to perform operations of:
receiving a first policy and charging control rule that identifies an edge application, a location of the edge application, and policy information for the edge application;
generating a second policy and charging control rule for a user equipment (UE) interacting with an edge application server of the edge application based on the first policy and charging control rule, the second policy and charging control rule identifying the policy information for the edge application and an Internet Protocol (IP) address corresponding to the edge application server; and
causing application of the second policy and charging control rule on a traffic flow between the UE and the edge application server.

### Claim 17 (depends on 16)

The network node of claim 16, wherein the first policy and charging control rule identifies the edge application through one or more of an edge application identifier of the edge application and a domain name of the edge application.

### Claim 18 (depends on 16)

The network node of claim 16, wherein the operations further comprise:
initiating a query to a network exposure function (NEF) about the edge application; and
receiving additional information from the NEF to be used for generating the second policy and charging control rule.

### Claim 19 (depends on 16)

The network node of claim 16, wherein upon the edge application server being created, the network node receives a first notification that indicates information of the edge application server, including:
one or more of an edge application identifier of the edge application and a domain name of the edge application,
the IP address corresponding to the edge application server; and
a location of the edge application server.

### Claim 20 (depends on 19)

The network node of claim 19, wherein the network node receives the first notification responsive to the network node subscribing to lifecycle event notification regarding the edge application.

### Claim at position 21

21-31. (canceled)
