IP Library › Granted Patent US 12,507,040
Granted Patent B2
US 12,507,040 · App. 17/713,554 · Granted Dec 23, 2025

Distributing multicast packets in individual protocol data unit (PDU) sessions

Inventors: Philippe Godin (Versailles, FR); Bruno Landais (Pleumeur-bodou, FR); Horst Thomas Belling (Erding, DE); David Navrátil (Helsinki, FI)
Assignee: NOKIA TECHNOLOGIES OY
H04W4/06H04W76/12H04W76/30
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,507,040
App. No.
17/713,554
Granted
Dec 23, 2025
Kind
B2
Abstract

Systems, methods, apparatuses, and computer program products for distributing multicast packets in individual protocol data unit (PDU) sessions are provided. One method may include receiving, at a user plane node, a request from a session management node, to receive packets for a multicast session and/or to send packets from the multicast session within a protocol data unit (PDU) session. The method may also include determining whether the user plane node was already configured to receive incoming packets for the multicast session, and informing the session management node as to whether the user plane node was already configured to receive the incoming packets for the multicast session.

Claims (66)

1 . A method, comprising:

receiving, at a user plane node, a request from a session management node, to receive packets for a multicast session within a protocol data unit (PDU) session, wherein the receiving of the request comprises receiving a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the user plane node will be receiving data for the multicast session;

determining whether the user plane node was already configured to receive incoming packets for the multicast session; and

informing the session management node as to whether the user plane node was already configured to receive the incoming packets for the multicast session, the method further comprising:

when it is determined that the user plane node is not yet configured to receive the incoming packets for the multicast session, creating a context for the multicast session and transmitting a context created indicator to the session management node; or

when it is determined that the user plane node is already configured to receive the incoming packets for the multicast session, transmitting a context exists indicator to the session management node.

2 . The method of claim 1 , wherein the receiving of the request comprises receiving a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the user plane node will be forwarding data from the multicast session within a protocol data unit (PDU) session.

3 . The method of claim 2 , further comprising:

when it is determined that the user plane node is not yet configured to receive the incoming packets for the multicast session,

transmitting a context missing indicator to the session management node, and

configuring a protocol data unit (PDU) session context to associate the PDU session context with the multicast session and forward related data; or

when it is determined that the user plane node is already configured to receive the incoming packets for the multicast session,

transmitting a context exists indicator to the session management node, and

configuring the protocol data unit (PDU) session context to associate it with the multicast session and forward related data.

4 . The method of claim 2 , further comprising:

when it is determined that the user plane node is not yet configured to receive the incoming packets for the multicast session, transmitting an error response comprising a context missing indicator to the session management node; or

when it is determined that the user plane node is already configured to receive the incoming packets for the multicast session, configuring a protocol data unit (PDU) session context to associate the PDU session context with the multicast session and forward related data.

5 . A method, comprising:

transmitting, by a session management node, to a user plane node, a request for the user plane node to receive packets for a multicast session within a protocol data unit (PDU) session, wherein the transmitting of the request comprises transmitting a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the user plane node will be receiving data for the multicast session;

receiving, at a session management node, an indication as to whether the user plane node was already configured to receive incoming packets for the multicast session, the method further comprising:

receiving a context created indicator from the user plane node; or

receiving a context exists indicator from the user plane node.

6 . The method of claim 5 , further comprising:

if the user plane node was not configured to receive the incoming packets for the multicast session, configuring user plane node to receive the incoming packets for the multicast session.

7 . The method of claim 5 , further comprising:

if the user plane node was not configured to receive the incoming packets for the multicast session, sending a request to a third node to send data for the multicast session to the user plane node.

8 . The method of claim 5 , wherein the transmitting of the request comprises transmitting a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the user plane node will be forwarding data from the multicast session within a protocol data unit (PDU) session.

9 . The method of claim 5 , further comprising:

transmitting an indication to a user plane node to terminate receiving packets for the multicast session; and

receiving, from the user plane node, an indication that there are protocol data unit (PDU) sessions to which packets from the multicast session are to be sent.

10 . An apparatus, comprising:

at least one processor; and

at least one memory comprising computer program code,

the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to:

receive a request, from a session management node, to receive packets for a multicast session within a protocol data unit (PDU) session, wherein the request comprises a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the apparatus will be receiving data for the multicast session;

determine whether the apparatus was already configured to receive incoming packets for the multicast session; and

inform the session management node as to whether the apparatus was already configured to receive the incoming packets for the multicast session, the at least one memory and computer program code are configured, with the at least one processor, to further cause the apparatus at least to:

when it is determined that the user plane node is not yet configured to receive the incoming packets for the multicast session, create a context for the multicast session and transmit a context created indicator to the session management node; or

when it is determined that the user plane node is already configured to receive the incoming packets for the multicast session, transmit a context exists indicator to the session management node.

11 . The apparatus of claim 10 , wherein the request comprises a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the apparatus will be forwarding data from the multicast session within a protocol data unit (PDU) session.

12 . The apparatus of claim 11 , wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:

when it is determined that the apparatus is not yet configured to receive the incoming packets for the multicast session,

transmit a context missing indicator to the session management node, and

configure a protocol data unit (PDU) session context to associate the PDU session context with the multicast session and forward related data; or

when it is determined that the apparatus is already configured to receive the incoming packets for the multicast session,

transmit a context exists indicator to the session management node, and

configure the protocol data unit (PDU) session context to associate it with the multicast session and forward related data.

13 . The apparatus of claim 11 , wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:

when it is determined that the apparatus is not yet configured to receive the incoming packets for the multicast session, transmit an error response comprising a context missing indicator to the session management node; or

when it is determined that the apparatus is already configured to receive the incoming packets for the multicast session, configure a protocol data unit (PDU) session context to associate the PDU session context with the multicast session and forward related data.

14 . An apparatus, comprising:

at least one processor; and

at least one memory comprising computer program code,

the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to:

transmit, to a user plane node, a request for the user plane node to receive packets for a multicast session within a protocol data unit (PDU) session, wherein the request comprises a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the apparatus will be transmitting data for the multicast session;

receive an indication as to whether the user plane node was already configured to receive incoming packets for the multicast session, the at least one memory and computer program code are configured, with the at least one processor, to further cause the apparatus at least to:

receive a context created indicator from the user plane node; or

receive a context exists indicator from the user plane node.

15 . The apparatus of claim 14 , wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:

if the user plane node was not configured to receive the incoming packets for the multicast session, configure user plane node to receive the incoming packets for the multicast session.

16 . The apparatus of claim 14 , wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:

if the user plane node was not configured to receive the incoming packets for the multicast session, send a request to a third node to send data for the multicast session to the user plane node.

17 . The apparatus of claim 14 , wherein the request comprises a packet forwarding control protocol (PFCP) session creation or modification request comprising an indication that the user plane node will be forwarding data from the multicast session within a protocol data unit (PDU) session.

18 . The apparatus of claim 14 , wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:

transmit an indication to a user plane node to terminate receiving packets for the multicast session; and

receive, from the user plane node, an indication that there are protocol data unit (PDU) sessions to which packets from the multicast session are to be sent.

Assignments (6)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: GODIN, PHILIPPE; LANDAIS, BRUNO
To: ALCATEL-LUCENT INTERNATIONAL S.A.
Reel/Frame 069229/0555 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: NAVRÁTIL, DAVID
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 069231/0620 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: ALCATEL-LUCENT INTERNATIONAL S.A.
To: NOKIA TECHNOLOGIES OY
Reel/Frame 069231/0749 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG
To: NOKIA TECHNOLOGIES OY
Reel/Frame 069231/0978 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: NOKIA SOLUTIONS AND NETWORKS OY
To: NOKIA TECHNOLOGIES OY
Reel/Frame 069232/0113 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: BELLING, HORST THOMAS
To: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG
Reel/Frame 070594/0269 →
Continuity (2)
Provisional Application 63171283 · Apr 6, 2021
Related Publication 20220322048A1 · Oct 6, 2022
References Cited (18)
US 11246011B1 · Satyanarayana · 2022 [cited by examiner]
US 20180192390A1 · Li et al. · 2018 [cited by applicant]
US 20190098536A1 · Qiao · 2019 [cited by examiner]
US 20200351984A1 · Talebi Fard et al. · 2020 [cited by applicant]
CN 111866757A · 2020 [cited by applicant]
CN 112105088A · 2020 [cited by applicant]
WO 2019114939A1 · 2019 [cited by applicant]
WO WO2020015503A1 · 2020 [cited by examiner]
Second Office Action dated Mar. 12, 2024 corresponding to Chinese Patent Application No. 202210368595.0, with English summary thereof. [cited by applicant]
Office Action and Search Report dated Jul. 28, 2023, corresponding to Chinese Patent Application No. 202210368595.0. [cited by applicant]
Communication under Rule 71(3) EPC dated Jun. 11, 2024 corresponding to European Patent Application No. 22166875.9. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16); 3GPP TS 23.501, V16.7.0, Dec. 2020. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16); 3GPP TS 23.502, V16.7.1, Jan. 2021. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17); 3GPP TR 23.757, V0.4.0, Jun. 2020. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; Stage 3 (Release 16); 3GPP TS 29.244, V16.6.0, Dec. 2020. [cited by applicant]
Extended Search Report and Written Opinion dated Aug. 29, 2022, corresponding to European Patent Application No. 22166875.9. [cited by applicant]
Communication under Rule 71(3) EPC dated Nov. 11, 2024 corresponding to European Patent Application No. 22166875.9. [cited by applicant]
Indian Office Action, with full English translation, corresponding to Indian Application No. 202214020686, dated Oct. 30, 2025. [cited by applicant]