On-demand ultra-reliable, low-latency communication (URLLC)
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.
1. A method of wireless communication, comprising:
transmitting, by a user equipment (UE) in a first component carrier supporting a first network slice of a network, a network registration request message requesting an ultra-reliable low latency communication (URLLC)-supported network slice of the network, wherein the first network slice comprises a first logical network implementing a first access network (AN) and a first core network (CN), wherein the URLLC-supported network slice comprises a second logical network implementing a second AN and a second CN, and wherein the first component carrier does not support URLLC services;
receiving, by the UE in response to the network registration request message requesting the URLLC-supported network slice, a network registration response message indicating the URLLC-supported network slice is allowed based on a second component carrier of the network providing the URLLC-supported network slice, wherein the second component carrier is different from the first component carrier;
receiving, by the UE based on the network registration response message, an instruction to perform at least one of:
a handover to the second component carrier;
a dual-connectivity procedure with the second component carrier; or
a carrier aggregation procedure with the second component carrier; and
transmitting, by the UE in the second component carrier based on the instruction, URLLC data.
2. The method of claim 1 , wherein the receiving includes:
receiving, by the UE, the network registration response message including allowed network slice selection assistance information (NSSAI) with the URLLC-supported network slice requested.
3. The method of claim 1 , further comprising:
transmitting, by the UE in the first component carrier, a protocol data unit (PDU) session establishment request message requesting a PDU session establishment over the URLLC-supported network slice not supported by the first component carrier; and
receiving, by the UE in the first component carrier in response to the PDU session establishment request message, a PDU session establishment response message indicating an acceptance of the PDU session establishment with an inactive user plane.
4. The method of claim 1 , further comprising:
receiving, by the UE, application data; and
transmitting, by the UE in response to the application data received, a service request message indicating the URLLC-supported network slice.
5. The method of claim 1 , further comprising:
receiving, by the UE, application data; and
transmitting, by the UE in response to the application data received, a protocol data unit (PDU) session activation message indicating the URLLC-supported network slice.
6. The method of claim 1 , further comprising:
receiving, by the UE, application data; and
transmitting, by the UE in response to the application data received, a flow setup request message indicating the URLLC-supported network slice.
7. A user equipment (UE) comprising:
a transceiver configured to:
transmit, in a first component carrier supporting a first network slice of a network, a network registration request message requesting an ultra-reliable low latency communication (URLLC)-supported network slice of the network, wherein the first network slice comprises a first logical network implementing a first access network (AN) and a first core network (CN), wherein the URLLC-supported network slice comprises a second logical network implementing a second AN and a second CN, and wherein the first component carrier does not support URLLC services;
receive, in response to the network registration request message requesting the URLLC-supported network slice, a network registration response message indicating the URLLC-supported network slice is allowed based on a second component carrier of the network providing the URLLC-supported network slice, wherein the second component carrier is different from the first component carrier;
receive, based on the network registration response message, an instruction to perform at least one of:
a handover to the second component carrier;
a dual-connectivity procedure with the second component carrier; or
a carrier aggregation procedure with the second component carrier; and
transmit, in the second component carrier based on the instruction, URLLC data.
8. The UE of claim 7 , wherein the transceiver configured to receive the network registration response message is further configured to:
receive the network registration response message including allowed network slice selection assistance information (NSSAI) with the URLLC-supported network slice.
9. The UE of claim 7 , wherein the transceiver is further configured to:
transmit, in the first component carrier, a protocol data unit (PDU) session establishment request message requesting a PDU session establishment over the URLLC-supported network slice not supported by the first component carrier; and
receive, in the first component carrier in response to the PDU session establishment request message, a PDU session establishment response message indicating an acceptance of the PDU session establishment with an inactive user plane.
10. The UE of claim 7 , wherein the transceiver is further configured to:
receive application data; and
transmit, in response to the application data received, a service request message indicating the URLLC-supported network slice.
11. The UE of claim 7 , wherein the transceiver is further configured to:
receive application data; and
transmit, in response to the application data received, a protocol data unit (PDU) session activation message indicating the URLLC-supported network slice.
12. The UE of claim 7 , wherein the transceiver is further configured to:
receive application data; and
transmit, in response to the application data received, a flow setup request message indicating the URLLC-supported network slice.
13. The UE of claim 7 , wherein the transceiver configured to transmit the network registration request message is further configured to:
transmit, in the first component carrier, the network registration request message requesting the URLLC-supported network slice of the network that is not provided by the first component carrier.
14. A method of wireless communication, comprising:
receiving, by a core network entity from a user equipment (UE) associated with a first component carrier supporting a first network slice of a network, a network registration request message requesting an ultra-reliable low latency communication (URLLC)-supported network slice of the network, wherein the first network slice comprises a first logical network implementing a first access network (AN) and a first core network (CN), wherein the URLLC-supported network slice comprises a second logical network implementing a second AN and a second CN, and wherein the first component carrier does not support URLLC services;
transmitting, by the core network entity to the UE in response to the network registration request message requesting the URLLC-supported network slice, a network registration response message indicating the URLLC-supported network slice is allowed based on a second component carrier of the network providing the URLLC-supported network slice, wherein the second component carrier is different from the first component carrier; and
transmitting, based on the network registration response message, an instruction to perform at least one of:
a handover to the second component carrier;
a dual-connectivity procedure with the second component carrier; or
a carrier aggregation procedure with the second component carrier; and
receiving, by the core network entity in the second component carrier based on the instruction, URLLC data.
15. The method of claim 14 , wherein the transmitting includes:
transmitting, by the core network entity to the UE, the network registration response message including allowed network slice selection assistance information (NSSAI) with the URLLC-supported network slice requested.
16. The method of claim 14 , further comprising:
receiving, by the core network entity from the UE, a protocol data unit (PDU) session establishment request message requesting a PDU session establishment over the URLLC-supported network slice not supported by the first component carrier; and
transmitting, by the core network entity to the UE in response to the PDU session establishment request message, a PDU session establishment response message indicating an acceptance of the PDU session establishment with an inactive user plane.
17. The method of claim 14 , further comprising:
transmitting, by the core network entity, application data; and
receiving, by the core network entity in response to the transmitted application data, a service request message indicating the URLLC-supported network slice.
18. The method of claim 14 , further comprising:
transmitting, by the core network entity, application data; and
receiving, by the core network entity in response to the transmitted application data, a protocol data unit (PDU) session activation message indicating the URLLC-supported network slice.
19. The method of claim 14 , further comprising:
transmitting, by the core network entity, application data; and
receiving, by the core network entity in response to the transmitted application data, a flow setup request message indicating the URLLC-supported network slice.
20. The method of claim 14 , wherein the receiving the network registration request message comprises:
receiving, in the first component carrier, the network registration request message requesting the URLLC-supported network slice of the network that is not provided by the first component carrier.
21. A core network entity, comprising:
a transceiver configured to:
receive, from a user equipment (UE) associated with a first component carrier supporting a first network slice of a network, a network registration request message requesting an ultra-reliable low latency communication (URLLC)-supported network slice of the network, wherein the first network slice comprises a first logical network implementing a first access network (AN) and a first core network (CN), wherein the URLLC-supported network slice comprises a second logical network implementing a second AN and a second CN, and wherein the first component carrier does not support URLLC services;
transmit, to the UE in response to the network registration request message requesting the URLLC-supported network slice, a network registration response message indicating the URLLC-supported network slice is allowed based on a second component carrier of the network providing the URLLC-supported network slice requested, wherein the second component carrier is different from the first component carrier; and
transmit, based on the network registration response message, an instruction to perform at least one of:
a handover to the second component carrier;
a dual-connectivity procedure with the second component carrier; or
a carrier aggregation procedure with the second component carrier; and
receive, in the second component carrier based on the instruction, URLLC data.
22. The core network entity of claim 21 , wherein the transceiver configured to transmit the network registration response message is further configured to:
transmit, to the UE, the network registration response message including allowed network slice selection assistance information (NSSAI) with the URLLC-supported network slice requested.
23. The core network entity of claim 21 , wherein the transceiver is further configured to:
receive, from the UE, a protocol data unit (PDU) session establishment request message requesting a PDU session establishment over the URLLC-supported network slice not supported by the first component carrier; and
transmit, to the UE in response to the PDU session establishment request message, a PDU session establishment response message indicating an acceptance of the PDU session establishment with an inactive user plane.
24. The core network entity of claim 21 , wherein the transceiver is further configured to:
transmit application data; and
receive, in response to the transmitted application data, a service request message indicating the URLLC-supported network slice.
25. The core network entity of claim 21 , wherein the transceiver is further configured to:
transmit application data; and
receive, in response to the transmitted application data, a protocol data unit (PDU) session activation message indicating the URLLC-supported network slice.
26. The core network entity of claim 21 , wherein the transceiver is further configured to:
transmit application data; and
receiving, in response to the transmitted application data, a flow setup request message indicating the URLLC-supported network slice.
27. The core network entity of claim 21 , wherein the transceiver configured to receive a PDU session establishment request message is further configured to:
receive, in the first component carrier, the network registration request message requesting the URLLC-supported network slice of the network that is not provided by the first component carrier.