# US 12,604,260 B2 · Systems and methods for dynamic slice selection in a wireless network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,604,260 B2 - Document ID: US12604260B2 - Status: Granted - Kind: B2 - Application number: 18/332,859 - Filed: 2023-06-12 - Published: 2024-12-12 - Granted: 2026-04-14 - Earliest claimed: 2023-06-12 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Shanthala Kuravangi-Thammaiah; Sudhakar Reddy Patil; Jerry Steben; Suzann Hua - Web page: https://patentgrep.com/patent/US12604260B2 ## CPC - H04W 24/02: Arrangements for optimising operational condition - H04W 48/18: Selecting a network or a communication service - H04W 48/14: using user query {or user detection} - H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA - H04W 72/56: based on priority criteria - H04W 76/11: Allocation or use of connection identifiers - H04W 76/12: Setup of transport tunnels - H04W 88/14: Backbone network devices - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A system described herein may receive a communication session request associated with a particular User Equipment (“UE”) and a network that includes a plurality of network slices. The communication session request may include a particular identifier, such as a Data Network Name (“DNN”) or other type of identifier. The system may output a request for network slice information, wherein the request includes the particular identifier; and may receive network slice information that indicates multiple network slices that were selected based on the particular identifier. A Unified Data Management function (“UDM”), Unified Data Repository (“UDR”), and/or other element of the network may provide such information. The system may identify network slice priority information that indicates relative priorities of the network slices, may select a particular network slice based on the network slice priority information, and may respond to the communication session request in accordance with the selected first network slice. ## Claims ### Claim 1 A device, comprising: one or more processors configured to: receive a first communication session request associated with a first User Equipment (“UE”) and a network that includes a plurality of network slices, wherein the first communication session request includes a particular identifier; output a first request for network slice information, wherein the first request for network slice information includes the particular identifier; receive, in response to the first request for network slice information, network slice information that indicates at least a first network slice and a second network slice that were selected based on the particular identifier; identify first network slice priority information, associated with the first UE, that indicates relative priorities of the first and second network slices, wherein the network further maintains second slice priority information associated with a second UE, wherein the first and second slice priority information are different; select the first network slice based on the first network slice priority information; respond to the first communication session request in accordance with the selected first network slice; receive a second communication session request associated with the second UE, wherein the second communication session request includes the particular identifier; select the second network slice based on the second network slice priority information; and respond to the second communication session request in accordance with the selected second network slice. ### Claim 2 (depends on 1) The device of claim 1, wherein the particular identifier includes a Data Network Name (“DNN”). ### Claim 3 (depends on 1) The device of claim 1, wherein the communication session request includes at least one of: a Protocol Data Unit (“PDU”) session request, or an attach request. ### Claim 4 (depends on 1) The device of claim 1, wherein the network slice information is received from at least one of: a Unified Data Management (“UDM”) function, or a Unified Data Repository (“UDR”). ### Claim 5 (depends on 1) The device of claim 1, wherein responding to the communication session request includes facilitating a communication session establishment between the UE and the network via the selected first network slice. ### Claim 6 (depends on 1) The device of claim 1, wherein responding to the first and second communication session requests is performed by an Access and Mobility Management Function (“AMF”) of the network. ### Claim 7 A non-transitory computer-readable medium, storing a plurality of processor-executable instructions to: receive a first communication session request associated with a first User Equipment (“UE”) and a network that includes a plurality of network slices, wherein the first communication session request includes a particular identifier; output a first request for network slice information, wherein the first request for network slice information includes the particular identifier; receive, in response to the first request for network slice information, network slice information that indicates at least a first network slice and a second network slice that were selected based on the particular identifier; identify first network slice priority information, associated with the first UE, that indicates relative priorities of the first and second network slices, wherein the network further maintains second slice priority information associated with a second UE, wherein the first and second slice priority information are different; select the first network slice based on the first network slice priority information; respond to the first communication session request in accordance with the selected first network slice; receive a second communication session request associated with the second UE, wherein the second communication session request includes the particular identifier; select the second network slice based on the second network slice priority information; and respond to the second communication session request in accordance with the selected second network slice. ### Claim 8 (depends on 7) The non-transitory computer-readable medium of claim 7, wherein the particular identifier includes a Data Network Name (“DNN”). ### Claim 9 (depends on 7) The non-transitory computer-readable medium of claim 7, wherein the communication session request includes at least one of: a Protocol Data Unit (“PDU”) session request, or an attach request. ### Claim 10 (depends on 7) The non-transitory computer-readable medium of claim 7, wherein the network slice information is received from at least one of: a Unified Data Management (“UDM”) function, or a Unified Data Repository (“UDR”). ### Claim 11 (depends on 7) The non-transitory computer-readable medium of claim 7, wherein responding to the communication session request includes facilitating a communication session establishment between the UE and the network via the selected first network slice. ### Claim 12 (depends on 7) The non-transitory computer-readable medium of claim 7, wherein responding to the first and second communication session requests is performed by at least one of an Access and Mobility Management Function (“AMF”) of the network or a Session Management Function (“SMF”) of the network. ### Claim 13 A method, comprising: receiving a first communication session request associated with a first User Equipment (“UE”) and a network that includes a plurality of network slices, wherein the first communication session request includes a particular identifier; outputting a first request for network slice information, wherein the first request for network slice information includes the particular identifier; receiving, in response to the first request for network slice information, network slice information that indicates at least a first network slice and a second network slice that were selected based on the particular identifier; identifying first network slice priority information, associated with the first UE, that indicates relative priorities of the first and second network slices, wherein the network further maintains second slice priority information associated with a second UE, wherein the first and second slice priority information are different; selecting the first network slice based on the first network slice priority information; responding to the first communication session request in accordance with the selected first network slice; receiving a second communication session request associated with the second UE, wherein the second communication session request includes the particular identifier; selecting the second network slice based on the second network slice priority information; and responding to the second communication session request in accordance with the selected second network slice. ### Claim 14 (depends on 13) The method of claim 13, wherein the particular identifier includes a Data Network Name (“DNN”). ### Claim 15 (depends on 13) The method of claim 13, wherein the communication session request includes at least one of: a Protocol Data Unit (“PDU”) session request, or an attach request. ### Claim 16 (depends on 13) The method of claim 13, wherein the network slice information is received from at least one of: a Unified Data Management (“UDM”) function, or a Unified Data Repository (“UDR”). ### Claim 17 (depends on 13) The method of claim 13, wherein responding to the communication session request includes facilitating a communication session establishment between the UE and the network via the selected first network slice. ### Claim 18 (depends on 13) The method of claim 13, wherein responding to the first and second communication session requests is performed by an Access and Mobility Management Function (“AMF”) of the network. ### Claim 19 (depends on 13) The method of claim 13, wherein responding to the first and second communication session requests is performed by Session Management Function (“SMF”) of the network. ### Claim 20 (depends on 13) The method of claim 13, wherein responding to the first and second communication session requests is performed by Session Management Function (“SMF”) of the network.