# US 2026/0101292 A1 · Providing information about multi-modal services to a ran

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

- Number: US 2026/0101292 A1
- Document ID: US20260101292A1
- Status: Published application
- Kind: A1
- Application number: 18/905,943
- Filed: 2024-10-03
- Published: 2026-04-09
- Earliest claimed: 2024-10-03
- Assignees: InterDigital Patent Holdings, Inc.
- Applicants: InterDigital Patent Holdings, Inc.
- Inventors: Magurawalage Chathura Madhusanka Sarathchandra; Michael Starsinic; Samir Ferdi; Jaya Rao; Samuli Turtinen; Faris Alfarhan; Srinivas Gudumasu; Francois Periard; Kevin Di Lallo; Achref Methenni
- Web page: https://patentgrep.com/patent/US20260101292A1

## CPC

- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04W 56/001: {Synchronization between nodes}
- H04M 15/66: {Policy and charging system}
- H04W 4/24: Accounting or billing
- H04W 28/24: Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

Systems, methods, and instrumentalities are described herein related to providing information about multi-modal services to a radio access network (RAN). In examples, a first network node may receive information associated with an application layer session and a multi-modal service identifier (MMSID) that may be associated with the application layer session. The first network node may generate a policy and charging control (PCC) rule for a wireless transmit/receive unit (WTRU) using the received information. The MMSID may be used to generate an association ID. The PCC rule may be sent to a second network node. The PCC rule may include the association ID.

## Claims

### Claim 1

A first network node, comprising:
a processor configured to:
receive information associated with an application layer session and a multi-modal service identifier (MMSID) that is associated with the application layer session;
generate a policy and charging control (PCC) rule for a wireless transmit/receive unit (WTRU) using the received information;
use the MMSID to generate an association ID; and
send the PCC rule to a second network node, wherein the PCC rule includes the association ID.

### Claim 2 (depends on 1)

The first network node of claim 1, wherein:
the received information includes a synchronization threshold,
the synchronization threshold is a maximum tolerable time delay between two data flows, and
the received information includes descriptions of the two data flows.

### Claim 3 (depends on 1)

The first network node of claim 1, wherein:
the application layer session includes a first media type and a second media type, and
the received information includes a first synchronization threshold associated with the first media type and a second synchronization threshold associated with the second media type.

### Claim 4 (depends on 3)

The first network node of claim 3, wherein:
the first synchronization threshold is associated with a first synchronization group ID, and the second synchronization threshold is associated with a second synchronization group ID, and
the first synchronization group ID and the second synchronization group ID identify two or more data flows.

### Claim 5 (depends on 4)

The first network node of claim 4, wherein the PCC rule includes at least one of the first synchronization threshold, the second synchronization threshold, the first synchronization group ID, or the second synchronization group ID.

### Claim 6 (depends on 1)

The first network node of claim 1, wherein the processor is further configured to:
generate the association ID by performing a hash function on input values, wherein the input values include at least one of the MMSID, an application function (AF) ID, a media type of a data flow, or a synchronization group ID.

### Claim 7 (depends on 1)

The first network node of claim 1, wherein the association ID is generated based on both the MMSID and an AF ID.

### Claim 8 (depends on 1)

The first network node of claim 1, wherein the processor is further configured to:
assign a common admission control group ID to the application layer session.

### Claim 9 (depends on 8)

The first network node of claim 8, wherein the PCC rule includes the common admission control group ID.

### Claim 10 (depends on 1)

The first network node of claim 1, wherein the PCC rule includes at least one of the MMSID, an AF ID, a media type of a data flow, or a synchronization group ID.

### Claim 11

A method associated with a first network node, the method comprising:
receiving information associated with an application layer session and a multi-modal service identifier (MMSID) that is associated with the application layer session;
generating a policy and charging control (PCC) rule for a wireless transmit/receive unit (WTRU) using the received information;
using the MMSID to generate an association ID; and
sending the PCC rule to a second network node, wherein the PCC rule includes the association ID.

### Claim 12 (depends on 11)

The method of claim 11, wherein:
the received information includes a synchronization threshold,
the synchronization threshold is a maximum tolerable time delay between two data flows, and
the received information includes descriptions of the two data flows.

### Claim 13 (depends on 11)

The method of claim 11, wherein:
the application layer session includes a first media type and a second media type, and
the received information includes a first synchronization threshold associated with the first media type and a second synchronization threshold associated with the second media type.

### Claim 14 (depends on 13)

The method of claim 13, wherein:
the first synchronization threshold is associated with a first synchronization group ID, and the second synchronization threshold is associated with a second synchronization group ID, and
the first synchronization group ID and the second synchronization group ID identify two or more data flows.

### Claim 15 (depends on 14)

The method of claim 14, wherein the PCC rule includes at least one of the first synchronization threshold, the second synchronization threshold, the first synchronization group ID, or the second synchronization group ID.

### Claim 16 (depends on 11)

The method of claim 11, further comprising:
generating the association ID by performing a hash function on input values, wherein the input values include at least one of the MMSID, an application function (AF) ID, a media type of a data flow, or a synchronization group ID.

### Claim 17 (depends on 11)

The method of claim 11, wherein the association ID is generated based on both the MMSID and an AF ID.

### Claim 18 (depends on 11)

The method of claim 11, further comprising:
assigning a common admission control group ID to the application layer session.

### Claim 19 (depends on 18)

The method of claim 18, wherein the PCC rule includes the common admission control group ID.

### Claim 20 (depends on 11)

The method of claim 11, wherein the PCC rule includes at least one of the MMSID, an AF ID, a media type of a data flow, or a synchronization group ID.
