IP Library › Granted Patent US 12,402,183
Granted Patent B2
US 12,402,183 · App. 17/782,086 · Granted Aug 26, 2025

Techniques for supporting connectivity of remote user equipments with relay access via an interworking function

Inventors: Karthika Paladugu (San Diego, CA); Hong Cheng (Basking Ridge, NJ); Gavin Bernard Horn (La Jolla, CA); Haris Zisimopoulos (London, GB); Stefano Faccin (San Ysidro, CA); Miguel Griot (La Jolla, CA)
Assignee: QUALCOMM Incorporated
H04W76/14H04W88/04
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,402,183
App. No.
17/782,086
Granted
Aug 26, 2025
Kind
B2
Abstract

The present disclosure relates to wireless communications, and more particularly to providing connectivity of a PC5 remote user equipment (UE) with UE-to-network (NW) relay access to the 5G core (5GC) via an IWF (e.g., N3IWF). In one aspect, a remote UE may be provided support for a network access stratum (NAS) connection with 5GC via an IWF. In another aspect, Access Traffic Steering, Switching and Splitting (ATSSS) support may be provided for a remote UE.

Claims (44)

1. A method of wireless communications at a relay user equipment (UE), comprising:

receiving at least one relay discovery parameter from a network entity;

determining, based at least on the at least one relay discovery parameter, at least one parameter for establishing one or more packet data unit (PDU) sessions towards an Interworking Function (IWF), while connected to a remote UE over a sidelink interface; and

establishing, for the remote UE, a single relay PDU session or multiple relay PDU sessions corresponding to the at least one relay discovery parameter.

2. The method of claim 1 , wherein the single relay PDU session supports communication of both Non-Access Stratum (NAS) and User Plane (UP) data via the IWF.

3. The method of claim 1 , wherein the multiple relay PDU sessions corresponding to at least two PDU sessions include:

a first PDU session for relaying Internet Key Exchange (IKE)/Non-Access Stratum (NAS) and User Plane (UP) data of the remote UE via a non-3GPP IWF (N3IWF), and

a second PDU session for relaying UP data of the remote UE to the Data Network (DN) directly.

4. The method of claim 1 , wherein the multiple relay PDU session corresponding to the two PDU sessions includes separate PDU sessions for relaying Internet Key Exchange (IKE)/Non-Access Stratum (NAS) and User Plane (UP) data of the remote UE via the IWF.

5. The method of claim 1 , wherein establishing the single relay PDU session or multiple relay PDU sessions includes determining at least one packet filter for the PDU sessions to restrict the Non-Access Stratum (NAS) and User Plane (UP) data through the IWF to a specific PDU session.

6. The method of claim 1 , further comprising transmitting, to the remote UE, a plurality of Internet Protocol (IP) addresses for a unicast PC 5 link, wherein one of the IP address is for User Plane (UP) traffic via IWF and another IP address is for UP traffic sent to DN directly.

7. The method of claim 1 , wherein establishing the single relay PDU session or multiple relay PDU sessions includes at least one of:

forming a Non-Access Stratum (NAS) and User Plane (UP) data session of the remote UE via the IWF, or

forming the UP data session when an Internet Protocol Security (IPSec) tunnel with IWF is successfully established by the remote UE.

8. The method of claim 7 , wherein forming the UP data session is further based on determining that one or more NAS messages with an IPSec tunnel mode are transmitted on a NAS PDU Session.

9. The method of claim 1 , further comprising receiving, from the remote UE, an PC 5 message on a PC 5 unicast link indicating a successful establishment of an Internet Protocol Security (IPSec) tunnel.

10. The method of claim 1 , further comprising:

transmitting a capability indication representing support for a connection to the network entity via the IWF in a registration message via a radio interface; and

receiving, based on transmitting the capability indication, provisioning information including at least one ProSe parameter by an Access and Mobility Management Function (AMF).

11. The method of claim 1 , further comprising receiving, from the network entity, one or more relay service codes for relay access via the IWF.

12. The method of claim 1 , wherein the network entity corresponds to a 5G Core (5GC) entity and the sidelink interface corresponds to a PC 5 interface, and wherein the IWF corresponds to a Non-3GPP Interworking Function (N3IWF).

13. An apparatus corresponding to a relay UE for wireless communication, comprising:

memory; and

at least one processor coupled with the memory, wherein the at least one processor is configured to:

receive at least one relay discovery parameter from a network entity;

determine, based at least on the at least one relay discovery parameter, at least one parameter for establishing one or more PDU sessions towards an Interworking Function (IWF), while connected to a remote UE over a sidelink interface; and

establish, for the remote UE, a single relay PDU session or multiple relay PDU sessions corresponding to the at least one relay discovery parameter.

14. The apparatus of claim 13 , wherein the single relay PDU session supports communication of both Non-Access Stratum (NAS) and User Plane (UP) data via the IWF.

15. The apparatus of claim 13 , wherein the multiple relay PDU sessions corresponding to at least two PDU sessions include:

a first PDU session for relaying Internet Key Exchange (IKE)/Non-Access Stratum (NAS) and User Plane (UP) data of the remote UE via a non-3GPP IWF (N3IWF), and

a second PDU session for relaying UP data of the remote UE to a Data Network (DN) directly.

16. The apparatus of claim 13 , wherein the multiple relay PDU session corresponding to the two PDU sessions includes separate PDU sessions for relaying Internet Key Exchange (IKE)/Non-Access Stratum (NAS) and User Plane (UP) data of the remote UE via the IWF.

17. The apparatus of claim 13 , wherein to establish the single relay PDU session or multiple relay PDU sessions, the at least one processor is further configured to determine at least one packet filter for the PDU sessions to restrict the Non-Access Stratum (NAS) and User Plane (UP) data through the IWF to a specific PDU session.

18. The apparatus of claim 13 , wherein the at least one processor is further configured to transmit, to the remote UE, a plurality of Internet Protocol (IP) addresses for a unicast PC 5 link, wherein one of the IP address is for User Plane (UP) traffic via IWF and another IP address is for UP traffic sent to DN directly.

19. The apparatus of claim 13 , wherein to establish the single relay PDU session or multiple relay PDU sessions, the at least one processor is further configured to include at least one of:

form a Non-Access Stratum (NAS) and User Plane (UP) data session of the remote UE via the IWF, or

form the UP data session when an Internet Protocol Security (IPSec) tunnel with IWF is successfully established by the remote UE.

20. The apparatus of claim 19 , wherein forming the UP data session is further based on determining that one or more NAS messages with an IPSec tunnel mode are transmitted on a NAS PDU Session.

21. The apparatus of claim 13 , wherein the at least one processor is further configured to receive, from the remote UE, an PC 5 message on a PC 5 unicast link indicating a successful establishment of an Internet Protocol Security (IPSec) tunnel.

22. The apparatus of claim 13 , wherein the at least one processor is further configured to:

transmit a capability indication representing support for a connection to the network entity via the IWF in a registration message via a radio interface; and

receive, based on transmitting the capability indication, provisioning information including at least one ProSe parameter by an Access and Mobility Management Function (AMF).

23. The apparatus of claim 13 , wherein the at least one processor is further configured to receive, from the network entity, one or more relay service codes for relay access via the IWF.

24. The apparatus of claim 13 , wherein the network entity corresponds to a 5G Core (5GC) entity and the sidelink interface corresponds to a PC 5 interface, and wherein the IWF corresponds to a Non-3GPP Interworking Function (N3IWF).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 6, 2022
From: PALADUGU, KARTHIKA; CHENG, HONG; HORN, GAVIN BERNARD; ZISIMOPOULOS, HARIS; FACCIN, STEFANO; GRIOT, MIGUEL
To: QUALCOMM INCORPORATED
Reel/Frame 060106/0791 →
Priority Claims (1)
GR 20200100002 · Jan 3, 2020 · national
Continuity (1)
Related Publication 20230007709A1 · Jan 5, 2023
References Cited (17)
US 12108494B2 · Paladugu · 2024 [cited by examiner]
US 20190174449A1 · Shan et al. · 2019 [cited by applicant]
US 20200053802A1 · Li et al. · 2020 [cited by applicant]
US 20240224355A1 · Lei · 2024 [cited by examiner]
CN 109997334A · 2019 [cited by applicant]
WO 2019121497A1 · 2019 [cited by applicant]
WO 2021045859A1 · 2021 [cited by applicant]
Qualcomm Incorporated: “N3IWF selection for Layer-3 UE-to-Network Relay”, 3GPP Draft; S2-2005831, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis … [cited by applicant]
Qualcomm Incorporated: “Solution to support end-to-end security for Layer-3 UE-to-Network Relay”, 3GPP Draft; S2-2000575, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F… [cited by applicant]
Intel: “Solution of 5GC Capable UE behind 5G-RG connected to 5GC via NG-RAN/W-5GAN”, 3GPP Draft; S2-1810426-5WWC-5G-RG-RELAYUE-V3, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Luc… [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS) (Release 17), 3GPP Standard; Technic… [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 Standard; Technical Specification; 3GPP TS 23.501, 3… [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity-based services (ProSe); Stage 2 (Release 15), 3GPP Standard; Technical Specification; 3GPP TS 23.303, 3rd Generati… [cited by applicant]
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2020/067592 dated Apr. 22, 2021. [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 Standard, Technical Specification, 3GPP TS 23.502, 3rd Genera… [cited by applicant]
Intel: “Solution of 5GC Capable UE Behind 5G-RG Connected to 5GC via NG-RAN/W-5GAN”, SA WG2 Meeting #S2-128Bis, S2-188141, Aug. 20-24, 2018, Sophia Antipolis, France, Aug. 14, 2018, pp. 1-7, Section 2. [cited by applicant]
Intel: “Solution of 5GC Capable UE Behind 5G-RG Connected to 5GC Via NG-RAN/W- 5GAN”, 3GPP Draft, SA WG2 Meeting SA2#129, S2-1810426-5WWC- 5G-RG-RELAYUE-V3, (revision of S2-18xxxx), Dongguan, China, Oct. 15, 2018-Oct. 1… [cited by applicant]