IP Library › Granted Patent US 12,231,956
Granted Patent B2
US 12,231,956 · App. 17/753,724 · Granted Feb 18, 2025

Back-off mechanisms for transmission of data over control plane

Inventors: Mahmoud Watfa (St-Leonard, CA); Miguel Griot (La Jolla, CA); Sebastian Speicher (Wallisellen, CH); Juan Zhang (Beijing, CN); Lenaig Genevieve Chaponniere (La Jolla, CA)
Assignee: QUALCOMM Incorporated
H04W28/0908H04W28/0289H04W48/06
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,956
App. No.
17/753,724
Granted
Feb 18, 2025
Kind
B2
Abstract

Various techniques and approaches described herein may be applied to control congestion at a session management (SM) function (SMF) based on at least one back-off timer maintained at a user equipment (UE). In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE may be configured to establish a protocol data unit (PDU) session with a SMF. The UE may be configured to determine whether a back-off timer associated with the PDU session is terminated. The UE may refrain from sending, to the SMF, data over a control plane associated with the PDU session when the back-off timer is unterminated. The UE may send, to the SMF, the data over the control plane associated with the PDU session when the back-off timer is terminated.

Claims (70)

1. A method of wireless communication by a user equipment (UE), the method comprising:

establishing a protocol data unit (PDU) session with a session management (SM) function (SMF);

receiving, from an access and mobility management function (AMF), a message including a duration of a back-off timer associated with the PDU session;

setting the back-off timer to the duration;

starting the back-off timer;

determining whether the back-off timer associated with the PDU session is terminated;

refraining from sending, to the SMF, data over a control plane associated with the PDU session when the back-off timer is unterminated; and

sending, to the SMF, the data over the control plane associated with the PDU session when the back-off timer is terminated,

wherein the message including the duration of the back-off timer is received based on transmission of one of a control plane service request message (CPSR) or an uplink non-access stratum (NAS) transport message to the AMF,

wherein the one of the CPSR message or the uplink NAS transport message indicates an identifier (ID) associated with the PDU session,

wherein the message including the duration of the back-off timer further includes at least one of the ID associated with the PDU session or a cause code associated with the back-off timer,

wherein the cause code indicates that SM signaling associated with control information is allowed when the back-off timer is unterminated.

2. The method of claim 1 , wherein the back-off timer is associated with at least one of a data network name (DNN), a network slice, or service gap control (SGC).

3. The method of claim 1 , wherein the back-off timer is configured at a SM layer of the UE.

4. The method of claim 1 , wherein the back-off timer is terminated based on at least one of expiration of the back-off timer, reception of a SM message indicating the back-off timer is to be terminated, or reception of downlink data over the control plane associated with the PDU session from the SMF.

5. A method of wireless communication by an access and mobility management function (AMF), the method comprising:

receiving a mobility management (MM) message from a user equipment (UE), wherein the MM message includes data over a control plane associated with a protocol data unit (PDU) session established between the UE and a session management (SM) function (SMF);

determining whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session;

sending, to the UE, a first message including a duration of a first back-off timer when the UE is prohibited to send the data over the control plane to the SMF;

sending, to the SMF, the data over the control plane when the UE is allowed to send the data over the control plane to the SMF; and

maintaining a local back-off timer associated with the PDU session established between the UE and the SMF,

wherein the determination of whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session is based on the local back-off timer.

6. The method of claim 5 , wherein the MM message comprises one of a control plane service request message (CPSR) or an uplink non-access stratum (NAS) transport message.

7. The method of claim 5 , wherein the first message comprises at least one of a Service Accept message, Service Reject message, or a downlink non-access stratum (NAS) transport message.

8. The method of claim 5 , further comprising:

receiving, from the SMF, a second message indicating a congestion status associated with the SMF,

wherein the determination of whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session is based on the congestion status.

9. The method of claim 8 , wherein the congestion status is associated with at least one of a data network name (DNN) or a network slice.

10. The method of claim 8 , wherein a cause code is included in the first message based on the congestion status.

11. The method of claim 10 , wherein the cause code indicates that SM signaling associated with control information is allowed by the UE when the first back-off timer is unterminated.

12. The method of claim 5 , wherein the first message includes at least one of an identifier (ID) associated with the PDU session, the data included in the MM message, or a container type associated with the MM message.

13. The method of claim 5 , wherein the first back-off timer is associated with at least one of a data network name (DNN), a network slice, or service gap control (SGC).

14. The method of claim 5 , wherein the local back-off timer comprises a service gap control (SGC) timer, and wherein the duration of the first back-off timer included in the first message is based on the SGC timer when SGC is unsupported by the UE.

15. A user equipment (UE) comprising:

a memory; and

at least one processor coupled to the memory and configured to:

establish a protocol data unit (PDU) session with a session management (SM) function (SMF);

receive, from an access and mobility management function (AMF), a message including a duration of a back-off timer associated with the PDU session;

set the back-off timer to the duration;

start the back-off timer;

determine whether the back-off timer associated with the PDU session is terminated;

refrain from sending, to the SMF, data over a control plane associated with the PDU session when the back-off timer is unterminated; and

send, to the SMF, the data over the control plane associated with the PDU session when the back-off timer is terminated,

wherein the message including the duration of the back-off timer is received based on transmission of one of a control plane service request message (CPSR) or an uplink non-access stratum (NAS) transport message to the AMF,

wherein the one of the CPSR message or the uplink NAS transport message indicates an identifier (ID) associated with the PDU session,

wherein the message including the duration of the back-off timer further includes at least one of the ID associated with the PDU session or a cause code associated with the back-off timer,

wherein the cause code indicates that SM signaling associated with control information is allowed when the back-off timer is unterminated.

16. The UE of claim 15 , wherein the back-off timer is associated with at least one of a data network name (DNN), a network slice, or service gap control (SGC).

17. The UE of claim 15 , wherein the back-off timer is configured at a SM layer of the UE.

18. The UE of claim 15 , wherein the back-off timer is terminated based on at least one of expiration of the back-off timer, reception of a SM message indicating the back-off timer is to be terminated, or reception of downlink data over the control plane associated with the PDU session from the SMF.

19. An Access and Mobility Management Function (AMF) comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive a mobility management (MM) message from a user equipment (UE), wherein the MM message includes data over the control plane associated with a protocol data unit (PDU) session established between the UE and a session management (SM) function (SMF);

determine whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session;

send, to the UE, a first message including a duration of a first back-off timer when the UE is prohibited to send the data over the control plane to the SMF;

send, to the SMF, the data over the control plane when the UE is allowed to send the data over the control plane to the SMF; and

maintain a local back-off timer associated with the PDU session established between the UE and the SMF,

wherein the determination of whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session is based on the local back-off timer.

20. The AMF of claim 19 , wherein the MM message comprises one of a control plane service request message (CPSR) or an uplink non-access stratum (NAS) transport message.

21. The AMF of claim 19 , wherein the first message comprises at least one of a Service Accept message, Service Reject message, or a downlink non-access stratum (NAS) transport message.

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

receive, from the SMF, a second message indicating a congestion status associated with the SMF,

wherein the determination of whether the UE is allowed or prohibited to send the data over the control plane to the SMF for the PDU session is based on the congestion status.

23. The AMF of claim 22 , wherein the congestion status is associated with at least one of a data network name (DNN) or a network slice.

24. The AMF of claim 22 , wherein a cause code is included in the first message based on the congestion status.

25. The AMF of claim 24 , wherein the cause code indicates that SM signaling associated with control information is allowed by the UE when the first back-off timer is unterminated.

26. The AMF of claim 19 , wherein the first message includes at least one of an identifier (ID) associated with the PDU session, the data included in the MM message, or a container type associated with the MM message.

27. The AMF of claim 19 , wherein the first back-off timer is associated with at least one of a data network name (DNN), a network slice, or service gap control (SGC).

28. The AMF of claim 19 , wherein the local back-off timer comprises a service gap control (SGC) timer, and wherein the duration of the first back-off timer included in the first message is based on the SGC timer when SGC is unsupported by the UE.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2022
From: WATFA, MAHMOUD; GRIOT, MIGUEL; SPEICHER, SEBASTIAN; ZHANG, JUAN; CHAPONNIERE, LENAIG GENEVIEVE
To: QUALCOMM INCORPORATED
Reel/Frame 059245/0239 →
Continuity (1)
Related Publication 20220377613A1 · Nov 24, 2022
References Cited (18)
US 20180270778A1 · Bharatia · 2018 [cited by applicant]
US 20190223093A1 · Watfa et al. · 2019 [cited by applicant]
US 20190357118A1 · Kim · 2019 [cited by examiner]
US 20200037203A1 · Ianev · 2020 [cited by examiner]
US 20210037415A1 · Liu · 2021 [cited by examiner]
US 20210092634A1 · Kang · 2021 [cited by applicant]
CL 2019000076A1 · 2019 [cited by applicant]
CN 108574964A · 2018 [cited by applicant]
WO 2018063800A1 · 2018 [cited by applicant]
WO 2018131970A1 · 2018 [cited by applicant]
WO 2019011190A1 · 2019 [cited by applicant]
WO 2019072681A1 · 2019 [cited by applicant]
WO 2019135581A1 · 2019 [cited by applicant]
WO WO2020001102A1 · 2020 [cited by examiner]
Clarivate Analytics, English Translation of WO 20200001102, 2024 (Year: 2024). [cited by examiner]
Supplementary European Search Report—EP19947093—Search Authority—The Hague—May 11, 2023. [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,… [cited by applicant]
International Search Report and Written Opinion—PCT/CN2019/108406—ISA/EPO—Jun. 29, 2020. [cited by applicant]