IP Library › Granted Patent US 12,284,709
Granted Patent B2
US 12,284,709 · App. 18/329,665 · Granted Apr 22, 2025

On-demand ultra-reliable, low-latency communication (URLLC)

Inventors: Xipeng Zhu (San Diego, CA); Gavin Bernard Horn (La Jolla, CA); Miguel Griot (La Jolla, CA); Haris Zisimopoulos (London, GB); Stefano Faccin (San Ysidro, CA)
Assignee: QUALCOMM Incorporated
H04W76/18H04W36/06H04W36/26H04W60/00
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,284,709
App. No.
18/329,665
Granted
Apr 22, 2025
Kind
B2
Abstract

Wireless communications systems and methods related to on-demand ultra-reliable, low-latency communication (URLLC) are provided. In one embodiment, a base station (BS) receives, from a user equipment (UE) in a first cell frequency, a request for a protocol data unit (PDU) session over a network slice. The BS receives, from a core network entity, a resource configuration request for the PDU session over the network slice. The BS transmits, to the core network entity, a resource configuration response indicating a cause for rejecting the resource configuration request. In one embodiment, a UE transmits, in a first cell frequency of a network, a network registration request message requesting a network slice of the network that is not provided by the first cell frequency. The UE receives a network registration response message indicating the network slice is allowed based on a second cell frequency of the network providing the network slice requested.

Claims (63)

1. A method of wireless communication, comprising:

receiving, by a base station (BS) from a user equipment (UE) in a first cell frequency, a request for an ultra-reliable, low-latency communication (URLLC) protocol data unit (PDU) session over a network slice;

receiving, by the BS from a core network entity, a resource configuration request for the URLLC PDU session over the network slice; and

transmitting, by the BS to the core network entity, a resource configuration response indicating a cause for rejecting the resource configuration request, wherein the cause for rejecting comprises an in-progress handover or redirection of the UE to set up the URLLC PDU session.

2. The method of claim 1 , wherein:

the receiving the resource configuration request comprises:

receiving, by the BS from the core network entity, a PDU session resource setup request message including at least one of:

a 5G quality of service identifier (5QI) associated with the network slice; or

single-network slice selection assistance information (S-NSSAI) associated with the network slice, and

the transmitting the resource configuration response comprises:

transmitting, by the BS to the core network entity, the resource configuration response indicating the cause for rejecting the resource configuration request based on the at least one of the 5QI or the S-NSSAI.

3. The method of claim 1 , further comprising:

transmitting, by the BS to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform a handover or a redirection to a second cell frequency.

4. The method of claim 1 , further comprising:

transmitting, by the BS to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform a dual-connectivity with a second cell frequency.

5. The method of claim 1 , further comprising:

transmitting, by the BS to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform a carrier aggregation with a second cell frequency.

6. The method of claim 1 , further comprising:

receiving, by the BS from the core network entity, a second resource configuration request for a second PDU session after a handover or a redirection of a second UE to the first cell frequency, the second PDU session being over a second network slice provided by the first cell frequency.

7. The method of claim 1 , wherein the first cell frequency comprises a first component carrier, wherein the network slice is supported by a second component carrier different from the first component carrier.

8. The method of claim 7 , wherein the network slice comprises a logical network implementing a first access network (AN) and a first core network (CN), and wherein the network slice supports on-demand.

9. The method of claim 1 , wherein the resource configuration response indicates that a handover will be performed for the UE.

10. A base station (BS) comprising:

a transceiver configured to:

receive, from a user equipment (UE) in a first cell frequency, a request for an ultra-reliable, low-latency communication (URLLC) protocol data unit (PDU) session over a network slice;

receive, from a core network entity, a resource configuration request for the URLLC PDU session over the network slice; and

transmit, to the core network entity, a resource configuration response indicating a cause for rejecting the resource configuration request, wherein the cause for rejecting comprises an in-progress handover or redirection of the UE to set up the URLLC PDU session.

11. The BS of claim 10 , wherein:

the transceiver configured to receive the resource configuration request is configured to:

receive, from the core network entity, a PDU session resource setup request message including at least one of:

a 5G quality of service identifier (5QI) associated with the network slice; or

single-network slice selection assistance information (S-NSSAI) associated with the network slice, and

the transceiver configured to transmit the resource configuration response is configured to:

transmit, to the core network entity, the resource configuration response indicating the cause for rejecting the resource configuration request based on the at least one of the 5QI or the S-NSSAI.

12. The BS of claim 10 , wherein the transceiver is further configured to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform to a handover or a redirection to a second cell frequency.

13. The BS of claim 10 , wherein the transceiver is further configured to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform to a dual-connectivity with a second cell frequency.

14. The BS of claim 10 , wherein the transceiver is further configured to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform a carrier aggregation with a second cell frequency.

15. The BS of claim 10 , wherein the transceiver is further configured to:

receive, from the core network entity, a second resource configuration request for a second PDU session after a handover or a redirection of a second UE to the first cell frequency, the second PDU session being over a second network slice provided by the first cell frequency.

16. The BS of claim 10 , wherein the first cell frequency comprises a first component carrier, wherein the network slice is supported by a second component carrier different from the first component carrier.

17. The BS of claim 16 , wherein the network slice comprises a logical network implementing a first access network (AN) and a first core network (CN), and wherein the network slice supports on-demand URLLC.

18. The BS of claim 10 , wherein the resource configuration response indicates that a handover will be performed for the UE.

19. A non-transitory, computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a base station (BS) to cause the BS to:

receive, from a user equipment (UE) in a first cell frequency, a request for an ultra-reliable, low-latency communication (URLLC) protocol data unit (PDU) session over a network slice;

receive, from a core network entity, a resource configuration request for the URLLC PDU session over the network slice; and

transmit, to the core network entity, a resource configuration response indicating a cause for rejecting the resource configuration request, wherein the cause for rejecting comprises an in-progress handover or redirection of the UE to set up the URLLC PDU session.

20. The non-transitory, computer-readable medium of claim 19 , wherein the instructions causing the BS to receive the resource configuration request comprises instructions causing the BS to:

receive, from the core network entity, a PDU session resource setup request message including at least one of:

a 5G quality of service identifier (5QI) associated with the network slice; or

single-network slice selection assistance information (S-NSSAI) associated with the network slice, and

the instructions causing the BS to transmit the resource configuration response comprises instructions causing the BS to:

transmit, to the core network entity, the resource configuration response indicating the cause for rejecting the resource configuration request based on the at least one of the 5QI or the S-NSSAI.

21. The non-transitory, computer-readable medium of claim 19 , wherein the program code further comprises instructions to cause the BS to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform to a handover or a redirection to a second cell frequency.

22. The non-transitory, computer-readable medium of claim 19 , wherein the program code further comprises instructions to cause the BS to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform to a dual-connectivity with a second cell frequency.

23. The non-transitory, computer-readable medium of claim 19 , wherein the program code further comprises instructions to cause the BS to:

transmit, to the UE in response to the resource configuration request for the URLLC PDU session over the network slice, an instruction to perform a carrier aggregation with a second cell frequency.

24. The non-transitory, computer-readable medium of claim 19 , wherein the program code further comprises instructions to cause the BS to:

receive, from the core network entity, a second resource configuration request for a second PDU session after a handover or a redirection of a second UE to the first cell frequency, the second PDU session being over a second network slice provided by the first cell frequency.

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNMENT DOCUMENT TO MATCH THE AS FILED PRIORITY INFORMATION AND THE 1ST ASSIGNOR'S EXECUTION DATE PREVIOUSLY RECORDED ON REEL 064824 FRAME 0206. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 9, 2023
From: ZHU, XIPENG; HORN, GAVIN BERNARD; GRIOT, MIGUEL; ZISIMOPOULOS, HARIS; FACCIN, STEFANO
To: QUALCOMM INCORPORATED
Reel/Frame 065530/0938 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 7, 2023
From: ZHU, XIPENG; HORN, GAVIN BERNARD; GRIOT, MIGUEL; ZISIMOPOULOS, HARIS; FACCIN, STEFANO
To: QUALCOMM INCORPORATED
Reel/Frame 064824/0206 →
Continuity (3)
Division 16937050 · Jul 23, 2020
Provisional Application 62880556 · Jul 30, 2019
Related Publication 20230319935A1 · Oct 5, 2023
References Cited (18)
US 20120142392A1 · Patel et al. · 2012 [cited by applicant]
US 20180270696A1 · Duan et al. · 2018 [cited by applicant]
US 20180324645A1 · Park et al. · 2018 [cited by applicant]
US 20190029065A1 · Park et al. · 2019 [cited by applicant]
US 20190068335A1 · Li et al. · 2019 [cited by applicant]
US 20190141591A1 · Wu · 2019 [cited by applicant]
US 20200145297A1 · Bainbridge et al. · 2020 [cited by applicant]
US 20200163042A1 · Cho · 2020 [cited by examiner]
US 20210037588A1 · Zhu et al. · 2021 [cited by applicant]
CN 109756941A · 2019 [cited by applicant]
JP 2006054856A · 2006 [cited by examiner]
Zhou, Xiaoyun (WO 2018141218 A1) Aug. 9, 2018 User Equipment Maximum Bandwidth Control Method and Device, Computer Storage Medium. [cited by examiner]
International Preliminary Report on Patentability—PCT/US2020/043475, The International Bureau of WIPO—Geneva, Switzerland, Feb. 10, 2022. [cited by applicant]
International Search Report and Written Opinion—PCT/US2020/043475—ISA/EPO—Oct. 29, 2020. [cited by applicant]
ITRI: “RAN Slicing in NR”, 3GPP TSG RAN WG2 NR Ad Hoc, 3GPP Draft; R2-1700262, 3rd Generationpartnership Project (3GPP), MobileCompetence Centre; 650, Route Des Lucioles; F-06921 Sophia-Antipolis Cedex; France, vol. RAN… [cited by applicant]
Qualcomm Incorporated: “Slice isolation in RAN”, 3GPP TSG-RAN WG3 Meeting #94, 3GPP Draft; R3-162828 Use Cases of Celllevel Isolation for Network Slice V1, 3rd Generation Partnership Project (3GPP), Mobile Competence Ce… [cited by applicant]
Samsung: “NGAP Impacts for the Notification about Dual Connectivity Failure during Redundant Sessions Establishment”, 3GPP TSG-RAN WG3 #104, 3GPP Draft; R3-192341-DCFAIL-NGCR, 3rd Generation Partnership Project (3GPP), … [cited by applicant]
European Search Report—EP24153825—Search Authority—Munich—Jun. 20, 2024. [cited by applicant]