IP Library › Granted Patent US 12,593,371
Granted Patent B2
US 12,593,371 · App. 18/501,547 · Granted Mar 31, 2026

Network node apparatus and methods for achieving end-to-end reliability and improving fault tolerance in wireless systems

Inventors: Achref Methenni (Montreal, CA); Michael Starsinic (Newtown, PA); Rocco Di Girolamo (Laval, CA); Ulises Olvera-Hernandez (Saint-Lazare, CA); Magurawalage Chathura Madhusanka Sarathchandra (London, GB); Saad Ahmad (Montreal, CA); Renan Krishna (Brighton, GB)
Assignee: InterDigital Patent Holdings, Inc.
H04W76/20
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,593,371
App. No.
18/501,547
Granted
Mar 31, 2026
Kind
B2
Abstract

A first policy control function (PCF) in a first network node may receive an indication from a session management function (SMF) that a protocol data unit (PDU) session is an alternative PDU session, and an indication of whether the PDU session is in a drop state. The first PCF may send a message with an indication to a second PCF in a second network node to indicate that the network node is serving a PDU session that is an alternative PDU session. In an example, the message with an indication to the second PCF may also identify the PDU session. The first PCF may receive a message from the second PCF with an indication that a second PDU session has experienced a fault or degraded performance. Further, the first PCF may send a message to the SMF to change the PDU session to a no-drop state.

Claims (28)

1 . A method for use in a first policy control function (PCF) in a first network node, the method comprising:

receiving an indication from a session management function (SMF) that a protocol data unit (PDU) session is an alternative PDU session, and an indication of whether the PDU session is in a drop state;

sending a message with an indication to a second PCF to indicate that the first network node is serving a PDU session that is the alternative PDU session, wherein the message with the indication to the second PCF also identifies the PDU session;

receiving a message from the second PCF with an indication that a second PDU session has experienced at least one of a fault or degraded performance; and

sending a message to the SMF to change the PDU session to a no-drop state.

2 . The method of claim 1 , wherein the message with the indication to the second PCF further indicates whether the PDU Session is in the drop state.

3 . The method of claim 1 , wherein the PDU Session is identified with a session identity (ID).

4 . The method of claim 1 , wherein the PDU Session is identified with a data network name (DNN).

5 . The method of claim 1 , wherein the PDU Session is identified with a single network slice selection assistance information (S-NSSAI).

6 . The method of claim 1 , further comprising:

initiating a procedure to trigger the first network node to transmit downlink data to a wireless transmit receive unit (WTRU) when the PDU session is in the no-drop state.

7 . The method of any claim 6 , wherein the downlink data is ultra-reliable low latency (URLLC) data.

8 . The method of claim 1 , wherein the second PCF is in a second network node.

9 . A first network node, including a first policy control function (PCF), the first network node comprising:

a transceiver; and

a processor operatively coupled to the transceiver; wherein:

the transceiver is configured to receive an indication from a session management function (SMF) that a protocol data unit (PDU) session is an alternative PDU session, and an indication of whether the PDU session is in a drop state;

the transceiver and the processor are configured to send a message with an indication to a second PCF to indicate that the first network node is serving a PDU session that is the alternative PDU session, wherein the message with the indication to the second PCF also identifies the PDU session;

the transceiver is configured to receive a message from the second PCF with an indication that a second PDU session has experienced at least one of a fault or degraded performance; and

the transceiver and the processor are configured to send a message to the SMF to change the PDU session to a no-drop state.

10 . The first network node of claim 9 , wherein the message with the indication to the second PCF further indicates whether the PDU Session is in the drop state.

11 . The first network node of claim 9 , wherein the PDU Session is identified with a session identity (ID).

12 . The first network node of claim 9 , wherein the PDU Session is identified with a data network name (DNN).

13 . The first network node of claim 9 , wherein the PDU Session is identified with a single network slice selection assistance information (S-NSSAI).

14 . The first network node of claim 9 , further comprising:

initiating a procedure to trigger the first network node to transmit downlink data to a wireless transmit receive unit (WTRU) when the PDU session is in the no-drop state.

15 . The first network node of claim 14 , wherein the downlink data is ultra-reliable low latency (URLLC) data.

16 . The first network node of claim 9 , wherein the second PCF is in a second network node.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2025
From: METHENNI, ACHREF; STARSINIC, MICHAEL; DI GIROLAMO, ROCCO; OLVERA-HERNANDEZ, ULISES; SARATHCHANDRA, MAGURAWALAGE CHATHURA MADHUSANKA; AHMAD, SAAD; KRISHNA, RENAN
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 073099/0588 →
Continuity (2)
Provisional Application 63422263 · Nov 3, 2022
Related Publication 20240155722A1 · May 9, 2024
References Cited (33)
US 12413653B1 · Yi · 2025 [cited by examiner]
US 20170317894A1 · Dao · 2017 [cited by examiner]
US 20200145876A1 · Dao · 2020 [cited by examiner]
US 20200214054A1 · Qiao · 2020 [cited by examiner]
US 20200382941A1 · Lee · 2020 [cited by examiner]
EP 4329417A1 · 2024 [cited by applicant]
WO 2022115561A1 · 2022 [cited by applicant]
IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
Interdigital, “Update to the Use Case for supporting Metaverse for Critical HealthCare Services,” 3GPP TSG-SA WG1 Meeting #100, S1-223236, Toulouse, France (Nov. 14-18, 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501 V17.6.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501 V17.10.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18),” 3GPP TS 23.501 V18.3.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18),” 3GPP TS 23.502 V18.3.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.502 V17.10.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.502 V17.6.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.503 V17.10.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.503 V17.6.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 18),” 3GPP TS 23.503 V18.3.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Tsg Sa; Feasibility Study on Localized Mobile Metaverse Services (Release 19),” 3GPP TR 22.856 V19.1.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group TSG SA; Feasibility Study on Localized Mobile Metaverse Services (Release 19),” 3GPP TR 22.856 V0.2.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3 (Release 18),” 3GPP TS 24.526 V18.4.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3 (Release 18),” 3GPP TS 24.526 V18.0.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; 5G System; Session Management Services; Stage 3 (Release 18),” 3GPP TS 29.502 V18.4.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; 5G System; Session Management Services; Stage 3 (Release 18),” 3GPP TS 29.502 V18.0.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 18),” 3GPP TS 29.512 V18.3.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 17),” 3GPP TS 29.512 V17.8.0 (Sep. 2022). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 17),” 3GPP TS 29.512 V17.12.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18),” 3GPP TS 24.501 V18.4.0 (Sep. 2023). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18),” 3GPP TS 24.501 V18.0.1 (Sep. 2022). [cited by applicant]