IP Library › Granted Patent US 12,231,949
Granted Patent B2
US 12,231,949 · App. 18/501,743 · Granted Feb 18, 2025

Always-on packet data unit session indication

Inventors: Weihua Qiao (Herndon, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Peyman Talebi Fard (Vienna, VA); Jayshree Bharatia (Plano, TX); Jinsook Ryu (Oakton, VA)
Assignee: Ofinno, LLC
H04W28/0268H04W8/20H04W76/10
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,231,949
App. No.
18/501,743
Granted
Feb 18, 2025
Kind
B2
Abstract

A session management function (SMF) receives, from a wireless device, an indication that an always-on packet data unit (PDU) session is requested. The SMF determines to establish the PDU session as an always-on PDU session based on: the indication that the always-on PDU session is requested; and the PDU session being for an ultra-reliable low-latency communication (URLLC) service. The SMF sends, to the wireless device, an indication that the PDU session is to be established as the always-on PDU session.

Claims (39)

1. A session management function (SMF), comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the SMF to:

receive, from a wireless device, a packet data unit (PDU) session establishment request message comprising:

an indication that an always-on PDU session is requested; and

an indication that the always-on PDU session is for an ultra-reliable low-latency communication (URLLC) service;

determine to establish the PDU session as an always-on PDU session based on:

the indication that the always-on PDU session is requested; and

the indication that the always-on PDU session is for the URLLC service; and

send, to the wireless device, a PDU session establishment accept message comprising the always-on PDU session indication.

2. The SMF of claim 1 , wherein the determining is based on the URLLC service being on a list of services for which the always-on PDU session is allowed.

3. The SMF of claim 2 , wherein the list of services for which the always-on PDU session is allowed indicates at least one of:

the URLLC service;

emergency service;

vehicle-to-everything (V2X) service;

internet of things (IoT) service; and

voice over long term evolution (LTE) service.

4. The SMF of claim 2 , wherein the list of services for which the always-on PDU session is allowed is received from a unified data management (UDM).

5. The SMF of claim 2 , wherein the instructions further cause the SMF to send, to a unified data management (UDM), a subscription retrieval request indicating that the list of services is requested.

6. The SMF of claim 1 , wherein the PDU session establishment request message comprises a PDU session identifier of the PDU session.

7. The SMF of claim 1 , wherein the PDU session establishment request message comprises an information element indicating that the always-on PDU session is requested.

8. The SMF of claim 1 , wherein the PDU session establishment accept message indicates successful establishment of the PDU session.

9. The SMF of claim 1 , wherein the PDU session establishment accept message comprises an information element indicating that the PDU session is an always-on PDU session.

10. A wireless device, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

determine that data packets are for an ultra-reliable low-latency communication (URLLC) service;

send, to a session management function (SMF), a packet data unit (PDU) session establishment request message comprising:

an indication that an always-on PDU session is requested; and

an indication that the always-on PDU session is for the URLLC service; and

receive, from the SMF, a PDU session establishment accept message comprising the always-on PDU session indication, wherein the always-on PDU session indication being set to a value indicating that the PDU session is to be established as the always-on PDU session is based on:

the indication that the always-on PDU session is requested; and

the indication that the always-on PDU session is for the URLLC service.

11. The wireless device of claim 10 , wherein the PDU session establishment request message comprises a PDU session identifier of the PDU session.

12. The wireless device of claim 10 , wherein the PDU session establishment request message comprises an information element indicating that the always-on PDU session is requested.

13. The wireless device of claim 10 , wherein the PDU session establishment accept message indicates successful establishment of the PDU session.

14. The wireless device of claim 10 , wherein the PDU session establishment accept message comprises an information element indicating that the PDU session is an always-on PDU session.

15. The SMF of claim 1 , wherein user plane resources of the always-on PDU session are activated during every transition from connection management (CM) idle (CM-IDLE) mode to CM connected (CM-Connected) state.

16. The SMF of claim 1 , wherein the SMF does not deactivate a user plane (UP) connection of the always-on PDU session due to inactivity.

17. The SMF of claim 1 , wherein a user plane (UP) connection of the always-on PDU session is not deactivated due to inactivity.

18. The wireless device of claim 10 , wherein user plane resources of the always-on PDU session are activated during every transition from connection management (CM) idle (CM-IDLE) mode to CM connected (CM-Connected) state.

19. The wireless device of claim 10 , wherein the SMF does not deactivate a user plane (UP) connection of the always-on PDU session due to inactivity.

20. The wireless device of claim 10 , wherein a user plane (UP) connection of the always-on PDU session is not deactivated due to inactivity.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 6, 2023
From: QIAO, WEIHUA; DINAN, ESMAEL; PARK, KYUNGMIN; BHARATIA, JAYSHREE A; TALEBI FARD, PEYMAN; RYU, JINSOOK
To: OFINNO, LLC
Reel/Frame 065784/0006 →
Continuity (6)
Continuation 17543077 · Dec 6, 2021
Continuation 16721232 · Dec 19, 2019
Provisional Application 62791490 · Jan 11, 2019
Provisional Application 62786897 · Dec 31, 2018
Provisional Application 62785946 · Dec 28, 2018
Related Publication 20240064559A1 · Feb 22, 2024
References Cited (46)
US 6854014B1 · Amin et al. · 2005 [cited by applicant]
US 11202223B2 · Qiao et al. · 2021 [cited by applicant]
US 11825335B2 · Qiao · 2023 [cited by examiner]
US 20120246325A1 · Marcos et al. · 2012 [cited by applicant]
US 20170201849A1 · Chandramouli · 2017 [cited by applicant]
US 20170288886A1 · Marcos et al. · 2017 [cited by applicant]
US 20190364541A1 · Ryu · 2019 [cited by applicant]
US 20200099750A1 · Kim et al. · 2020 [cited by applicant]
US 20210227597A1 · Kawasaki · 2021 [cited by examiner]
EP 3419374A1 · 2018 [cited by applicant]
WO 2014016676A1 · 2014 [cited by applicant]
WO 2018008980A1 · 2018 [cited by applicant]
WO 2018231029A1 · 2018 [cited by applicant]
C1-182183; 3GPP TSG-CT WG1 Meeting #110; Kunming (P.R of China), Apr. 16-20, 2018 (was C1-181196); Source: Qualcomm Incorporated, Intel, Nokia, Nokia Shanghai Bell, InterDigital, ZTE; Title: Concurrent service request p… [cited by applicant]
C1-182334; 3GPP TSG CT WG1 Meeting #110; Kunming (P.R. of China), Apr. 16-20, 2018; Source: Samsung; Title: Disc of 5G SR in comparison with legacy SR.; Agenda item: 15.2.2.3; Document for: Discussion. [cited by applicant]
C1-182335; 3GPP TSG CT WG1 Meeting #110; Kunming (P.R. of China), Apr. 16-20, 2018; Source: Samsung; Title: Discussion on KPIs in 5G.; Agenda item: 15.2.2.3; Document for: Discussion. [cited by applicant]
C1-182336; 3GPP TSG-CT WG1 Meeting #110; Kunming (P.R. of China), Apr. 16-20, 2018; Source: Samsung, Vodafone, Deutsche Telekom; Title: SR in 5G ; Spec: 3GPP TS 24.501 v1.0; Agenda item: 15.2.2.3; Document for: Agreemen… [cited by applicant]
C1-182708; 3GPP TSG-CT WG1 Meeting #110; Kunming (P.R. of China), Apr. 16-20, 2018; Source: Samsung, Qualcomm Incorporated, Vodafone, Deutsche Telekom, InterDigital, Huawei, Hisilicon, Intel, T-Mobile USA; Title: SR in … [cited by applicant]
C1-188319; 3GPP TSG-CT WG1 Meeting #113; West Palm Beach (FL), USA, Nov. 26-30, 2018; Change Request; 24.501; CR 0632; rev -; Current version: 15.1.0. [cited by applicant]
C1-188350; 3GPP TSG-CT WG1 Meeting #113; West Palm Beach (FL), USA, Nov. 26-30, 2018; Change Request; 24.501; CR 0646; rev -; Current version: 15.1.0. [cited by applicant]
S2-184683; SA WG2 Meeting #S2-127BIS; May 28-Jun. 1, 2018, Newport Beach, California, USA; 3GPP TSG CT WG1 Meeting# 110; TDoc C1-182809; Kunming (P.R. of China), Apr. 16-20, 2018; Title: LS on SR in 5G; Response to: Non… [cited by applicant]
S2-186173; SA WG2 Meeting #127bis; May 28-Jun. 1, 2018, Newport Beach, USA; Title: Reply LS on SR in 5G; Reply to: (C1-182809/S2-184638) LS on SR in 5G; Release: Release 15; Work Item: 5GS_Ph1-CT. [cited by applicant]
S2-1810016; SA WG2 Meeting #S2-129; Oct. 15-19, 2018, Dongguan, P.R. China; 3GPP TSG CT WG1 Meeting 112 TDoc C1-185795; West Palm Beach, FL (USA), Aug. 20-24, 2018; Title: Working Agreement on “Network control for alway… [cited by applicant]
S2-1811571; 3GPP TSG-SA WG2 Meeting #129; Oct. 15-19, 2018, Dongguan, P. R. China (revision of S2-1811425); Change Request; 23.501; CR 0679; rev 3; Current version: 15.3.0. [cited by applicant]
S2-1811572; 3GPP TSG-SA WG2 Meeting #129; Oct. 15-19, 2018, Dongguan, P. R. China (revision of S2-1811426); Change Request; 23.502; CR 0786; rev 3; Current version: 15.3.0. [cited by applicant]
S2-1811843; 3GPP TSG-SA WG2 Meeting #129-Bis; Nov. 26-30, 2018, West Palm Beach, USA (revision of S2-181xxx); Change Request; 23.501; CR 0699; rev; Current version: 15.3.0. [cited by applicant]
S2-1811844; 3GPP TSG-SA WG2 Meeting #129-Bis; Nov. 26-30, 2018, West Palm Beach, USA (revision of S2-181xxxx); Change Request; 23.502; CR 0817; rev; Current version: 15.3.0. [cited by applicant]
S2-1812148; 3GPP TSG-SA WG2 Meeting #129bis; Nov. 26-30, 2018, West Palm Beach, USA; Change Request; 23.501; CR 0721; rev -; Current version: 15.3.0. [cited by applicant]
S2-1812149; 3GPP TSG-SA WG2 Meeting #129bis; Nov. 26-30, 2018, West Palm Beach, USA; Change Request; 23.502; CR 0844; rev -; Current version: 15.3.0. [cited by applicant]
S2-1812159; 3GPP TSG-SA WG2 Meeting #129bis; West Palm Beach, USA, Nov. 26-30, 2018; Source: LG Electronics; Title: Discussion on Always-on PDU Session; Document for: Discussion; Agenda Item: 6.5.7 3GPP access specific … [cited by applicant]
S2-1812168; 3GPP TSG-SA WG2 Meeting #129; Oct. 15-19, 2018, Dongguan, P. R. China (revision of S2-1811571); Change Request; 23.501; CR 0679; rev 4; Current version: 15.3.0. [cited by applicant]
S2-1812341; 3GPP TSG-SA WG2 Meeting #129bis; Nov. 26-30, 2018, West Palm Beach, USA (revision of S2-18xxxxx); Change Request; 23.503; CR 0184; rev -; Current version: 15.3.0. [cited by applicant]
S2-1812344; 3GPP TSG-SA WG2 Meeting #129bis; Nov. 26-30, 2018, West Palm Beach, USA (revision of S2-1811425); Change Request; 23.501 CR 0679 rev 5 Current version: 15.3.0. [cited by applicant]
3GPP TS 23.203 V15.0.0 (Sep. 2017); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 15). [cited by applicant]
3GPP TS 23.502 V15.0.0 (Dec. 2017); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15). [cited by applicant]
3GPP TS 24.501 V15.0.0 (Jun. 2018); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15). [cited by applicant]
3GPP TS 23.501 V15.0.0 (Dec. 2017); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15). [cited by applicant]
3GPP TS 23.502, SA WG2, VI 5.4.0, Dec. 18, 2018, pp. 1-346, XP051591142. [cited by applicant]
International Search Report and Written Opinion of the International Searching authority mailed May 11, 2020, in International Application No. PCT/US2019/067472. [cited by applicant]
European Office Action, mailed Apr. 28, 2022, in EP Patent Application No. 19839580.8. [cited by applicant]
Extended European Search Report, mailed May 3, 2022, in EP Patent Application No. 22153370.6. [cited by applicant]
C1-184544; 3GPP TSG CT WG1 Meeting #111 bis; Sophia-Antipolis (France), Jul. 9-13, 2018; Source: Huawei, HiSilicon, Samsung, T-Mobile USA; Title: Discussion on network control for always-on PDU sessions; Agenda item: 15… [cited by applicant]
C1-184545; 3GPP TSG-CT WG1 Meeting #111 bis; Sophia-Antipolis (France), Jul. 9-13, 2018; Change Request; 24.501; CR 0107; rev 1; Current version: 15.0.0. [cited by applicant]
3GPP TS 23.203 V15.4.0 (Sep. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture; (Release 15). [cited by applicant]
3GPP TS 23.501 V15.4.0 (Dec. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2; (Release 15). [cited by applicant]
3GPP TS 24.501 V15.2.0 (Dec. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; … [cited by applicant]
Cited By (1)
US 12,701,418