Search

EP-4740405-A1 - TECHNOLOGIES FOR STANDALONE OPERATION FOR NETWORK SLICING

EP4740405A1EP 4740405 A1EP4740405 A1EP 4740405A1EP-4740405-A1

Abstract

Techniques are described herein for network slice availability based de-prioritization. An example, method includes receiving user equipment (UE) routing selection policy (URSP) information. The method further includes starting an application associated with a network slice while registered with a standalone (SA) network. The method further includes evaluating routing selection descriptor information in the URSP information to determine an availability of the network slice of the SA network. The method further includes determining whether to de-prioritize the SA network based on a determination of availability of the network slice as indicated by the routing selection descriptor information.

Inventors

  • PRABHAKAR, ALOSIOUS PRADEEP
  • DHANAPAL, MUTHUKUMARAN

Assignees

  • Apple Inc.

Dates

Publication Date
20260513
Application Date
20240717

Claims (20)

  1. 1. A method comprising: receiving user equipment (UE) routing selection policy (URSP) information; causing an application associated with a network slice to be started while registered with a standalone (SA) network; evaluating routing selection descriptor information in the URSP information to determine an availability of the network slice of the SA network; and determining whether to de-prioritize the SA network based on a determination of availability of the network slice as indicated by the routing selection descriptor information.
  2. 2. The method of claim 1, wherein evaluating the routing selection descriptor information in the URSP information comprises: accessing route selection validation criteria based on the routing selection descriptor information in the URSP information; determining that the network slice is unavailable outside of a window based on the route selection validation criteria; and determining that a current time is outside of the time window, wherein determining whether to de-prioritize the SA network is further based on determining that the current time is outside of the time window.
  3. 3. The method of claim 1, wherein evaluating the routing selection descriptor information in the URSP information comprises: accessing route selection validation criteria based on the routing selection descriptor information in the URSP information; determining that the network slice is available within a time window based on the route selection validation criteria; and determining that a current time is within the time window, wherein determining whether to de-prioritize the SA network is further based on determining that the current time is within the time window.
  4. 4. The method of claim 1, wherein evaluating the routing selection descriptor information in the URSP information comprises: accessing route selection validation criteria based on the routing selection descriptor information in the URSP information; determining that the network slice availability is based on a geofence; and determining that a UE is outside of the geofence, wherein determining whether to de-prioritize the SA network is further based on determining that the UE is outside of the geofence.
  5. 5. The method of claim 1, wherein evaluating the routing selection descriptor information in the URSP information comprises: accessing route selection validation criteria based on the routing selection descriptor information in the URSP information; determining that the network slice availability is based on a geofence; and determining that a UE is within the geofence, wherein determining whether to deprioritize the SA network is further based on determining that the UE is within the geofence.
  6. 6. The method of any of claims 1-5, wherein the method further comprises: de-prioritizing from the SA network based on the determination of availability of the network slice; and registering with a non-standalone (NS A) network.
  7. 7. An apparatus comprising: processing circuitry to: cause a registration with a standalone (SA) network, process configuration information based on registering with the SA network, cause an application associated with a network slice to be started while registered with the SA network, determine that the network slice of the SA network is an allowed network slice based on the configuration information, determine whether there is an existing packet data unit (PDU) session associated with the allowed network slice, and determine whether to de-prioritize the SA network based on whether there is an existing PDU session associated with the allowed network slice; and memory coupled to the processing circuitry, the memory to store the configuration information.
  8. 8. The apparatus of claim 7, wherein receiving configuration information based on registering with the SA network comprises: receiving Allowed Network Slice Selection Assistance Information (NSSAI) based on registering with the SA network, wherein the UE determines that the network slice is allowed based on the Allowed NSSAI.
  9. 9. The apparatus of any of claims 7 or 8, wherein the processing circuitry is further to: determine that there is no existing PDU session mapped to the network slice; and determine to de-prioritize the SA network and switch to a non-SA (NSA) network based on determining that there is no existing PDU session mapped to the network slice.
  10. 10. The apparatus of any of claims 7 or 8, wherein the processing circuitry is further to: determine that there is an existing PDU session mapped to the network slice; and determine to not de-prioritize the SA network based on determining that there is the existing PDU session mapped to the network slice.
  11. 11. The apparatus of claim 7, wherein the processing circuitry is further to: process mapped evolved packet system (EPS) bearer contexts information; and determine that the UE can de-prioritize the SA network to a non-SA (NSA) network based on the mapped EPS bearer contexts information.
  12. 12. The apparatus of claim 7, wherein the configuration information comprises data network name (DNN) information, and wherein the processing circuitry is further to: determine whether the SA network supports a DNN, wherein determining whether to de-prioritize the SA network is based on the SA network supports the DNN.
  13. 13. The apparatus of claim 12, wherein determining whether the SA network supports a DNN is based on a mapped bearer context information element (IE).
  14. 14. The apparatus of any of claims 7-14, wherein the configuration information comprises (DNN) information, and wherein the processing circuitry is further to: determine whether a non-SA network supports a DNN, wherein determining whether to de-prioritize the SA network is based on the non-SA network supports the DNN.
  15. 15. The apparatus of claim 14, wherein non-SA network does not support the DNN, and wherein the processing circuitry is further to: determine to remain connected with the SA network.
  16. 16. One or more computer-readable media having stored thereon a sequence of instructions that, when executed, cause processing circuitry to: cause a registration with a standalone (SA) network; determine whether a wireless local area network (WLAN) calling mode is enabled for a user equipment (UE); determine whether a WLAN tethering mode is enabled for the UE, and determine whether to remain registered to the SA network based on whether the WLAN calling mode is enabled for the UE and whether the WLAN tethering mode is enabled for the UE.
  17. 17. The one or more computer-readable media of claim 16, wherein the instructions that, when executed, further cause the processing circuitry to: determine to remain registered to the SA network based on a determination that the WLAN calling mode is not enabled for the UE and a determination that the WLAN tethering mode is not enabled for the UE.
  18. 18. The one or more computer-readable media of claim 17, wherein the instructions that, when executed, further cause the processing circuitry to: determine to remain registered to the SA network based on a determination that the WLAN calling mode is enabled for the UE and a determination that the WLAN tethering mode is enabled for the UE.
  19. 19. The one or more computer- readable media of claim 16, wherein the instructions, when executed, further cause the processing circuitry to: determine to remain registered to the SA network based on a determination that the WLAN calling mode is not enabled for the UE and a determination that the WLAN tethering mode is enabled for the UE.
  20. 20. The one or more computer-readable media of claim 16, wherein the sequence of instructions that, when executed, further cause the processing circuitry to: cause a registration with a non- SA network based on the based on whether the WLAN calling mode is enabled for the UE and whether the WLAN tethering mode is enabled for the UE.

Description

TECHNOLOGIES FOR STANDALONE OPERATION FOR NETWORK SLICING CROSS-REFERENCES TO RELATED APPLICATIONS [0001] This application claims priority to and the benefit of U.S. Provisional Application No. 63/520,404, filed on August 18, 2023; and U.S. Patent Application No. 18/774,399 filed on July 16, 2024; the contents of each of which are herein incorporated by reference in their entireties for all purposes. TECHNICAL FIELD [0002] This application relates to wireless networks and, in particular, to technologies for standalone operation for network slicing in such wireless networks. BACKGROUND [0003] Cellular communications can be defined in various standards to enable communications between a user equipment and a cellular network. For example, a long-term evolution (LTE) network and Fifth generation mobile network (5G) are wireless standards that aim to improve upon data transmission speed, reliability, availability, and more. BRIEF DESCRIPTION OF THE DRAWINGS [0004] Figure 1 is an illustration of a system for network slice-based prioritization and deprioritization decisions, according to one or more embodiments. [0005] Figure 2 is a signaling diagram for a network slice- based de-prioritization decision, according to one or more embodiments. [0006] Figure 3 is a signaling diagram for a network slice- based de-prioritization decision, according to one or more embodiments. [0007] Figure 4 is a signaling diagram for network slice-based de-prioritization and reprioritization decisions, according to one or more embodiments. [0008] Figure 5 is a signaling diagram for a network slice-based re-prioritization decision, according to one or more embodiments. [0009] Figure 6 is a signaling diagram for a network slice-based re-prioritization decision, according to one or more embodiments. [0010] Figure 7 is a table for different de-prioritization decisions, according to one or more embodiments. [0011] Figure 8 is another table for different de-prioritization decisions, according to one or more embodiments. [0012] Figure 9 is a process flow for de-prioritization and prioritization, according to one or more embodiments. [0013] Figure 10 is a process flow for a de-prioritization decision, according to one or more embodiments. [0014] Figure 11 is a process flow for a re-prioritization decision, according to one or more embodiments. [0015] Figure 12 illustrates an example of receive components, in accordance with some embodiments. [0016] Figure 13 illustrates an example of a UE, in accordance with some embodiments. [0017] Figure 14 illustrates an example of a network node, in accordance with some embodiments. DETAILED DESCRIPTION [0018] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B); and the phrase “based on A” means “based at least in part on A,” for example, it could be “based solely on A” or it could be “based in part on A.” [0019] The following is a glossary of terms that may be used in this disclosure. [0020] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. [0021] The term “processor