WO2022069481A2 - Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence - Google Patents

Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence Download PDF

Info

Publication number
WO2022069481A2
WO2022069481A2 PCT/EP2021/076675 EP2021076675W WO2022069481A2 WO 2022069481 A2 WO2022069481 A2 WO 2022069481A2 EP 2021076675 W EP2021076675 W EP 2021076675W WO 2022069481 A2 WO2022069481 A2 WO 2022069481A2
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
network
network slice
radio access
assistance information
Prior art date
Application number
PCT/EP2021/076675
Other languages
English (en)
Other versions
WO2022069481A3 (fr
Inventor
Philippe Godin
Alessio Casati
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2022069481A2 publication Critical patent/WO2022069481A2/fr
Publication of WO2022069481A3 publication Critical patent/WO2022069481A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • An example embodiment relates generally to supporting the identification and selection of available network slices and frequency bands via a radio access network.
  • a communication system can be seen as a facility that enables communication sessions between two or more entities such as user equipment (UE), base stations/access points, Network Functions (NF), and/or other nodes by providing connectivity between the various entities involved in the communication path.
  • a communication system can be provided, for example, by means of a communication network and one or more compatible communication devices.
  • Telecommunication networks such as the fifth generation of mobile networks (5G networks) are expected to be the next major phase of mobile telecommunication standards and to bring many improvements in the mobile network user experience. For instance, 5G networks should provide new technical solutions allowing a greater throughput, lower latency, higher reliability, higher connectivity, and higher mobility range. In addition to these improvements in terms of performance, 5G networks are also expected to extend the flexibility in the network usage and to provide users with a wider range of use cases and business models.
  • the 3rd Generation Partnership Project (3GPP) is a standards organization which develops protocols for mobile telephony and is known for the development and maintenance of various standards including second generation (2G), third generation (3G), fourth generation (4G), Long Term Evolution (LTE), and fifth generation (5G) standards.
  • the 5G network has been designed as a Service Based Architecture (SBA), e.g., a system architecture in which the system functionality is achieved by a set of NFs providing services to other authorized NFs to access their services.
  • SBA Service Based Architecture
  • the 5G network system allows for the support of network slices, which are end to end logical networks which support a certain set of NFs.
  • a network slice is a logical network that provides specific network capabilities and network characteristics.
  • particular network slices can be configured to support particular features (e.g., hardware specifications, NFs, domain access, etc.) not common to all network slices.
  • User equipment can be configured to access multiple network slices over the same access point.
  • Identification of a network slice is done via Single Network Slice Selection Assistance Information (S-NSSAI) which is sent to the user equipment via signaling messages between the user equipment and the connected network.
  • the Network Slice Selection Assistance Information (NSSAI) is a collection of S-NSSAIs sent to the user equipment via signaling messages between the user equipment and the connected network.
  • a single user equipment can be served by multiple network slices at a time.
  • the S-NSSAI signaled by the user equipment to the network, assists the network in selecting a particular network slice instance.
  • the network slice instance is a set of NF instances and their required resources (e.g., computing, processing, storage, networking, etc.) which form a deployed network slice.
  • the S-NSSAI is associated with a Public Land Mobile Network (PLMN), for example, the S-NSSAI is configured to indicate an associated PLMN identification code, or other ID information, having network-specific values or standard global values.
  • PLMN Public Land Mobile Network
  • An S-NSSAI is used by the user equipment for selecting and accessing the PLMN that the S-NSSAI is associated with.
  • Radio Resource Management (RRM) functions are configured to facilitate user equipment connection allocation and maintenance, via radio communication paths to PLMNs and individual network slices, and are performed by Radio Access Networks (RANs).
  • the RRM function strategy may be based on user specific information or frequency bands specific to particular PLMNs or network slices.
  • RANs can provide the mapping parameters to identify frequency bands associated with particular PLMNs or network slices to user equipment in the form of an Index to Radio Access Technology Frequency Selection Priority (RFSP Index).
  • RFSP Index is mapped by the RAN to locally defined configurations in order to apply specific RRM strategies.
  • the RFSP Index is specific to the user equipment and applies to all the radio bearers associated with the RAN.
  • a method, apparatus, and computer program product which facilitate the identification and selection of network slice specific frequency bands and associated cells by user equipment to connect to respective network slices.
  • the S-NSSAI attribute in each network slice profile is associated by the core network to one or more spectrum band(s) to the RAN.
  • the spectrum band attribute provides an indication, to the RAN, for each network slice, via a respective S-NSSAI, of the frequency bands supported by the respective network slice for communications over the RAN.
  • Communications via the RAN between user equipment and individual network slices of a network may be supported by all frequency bands associated with the network and all cells associated with the RAN.
  • individual network slices may be configured to receive and transmit communications only over a subset of frequency bands that cover an associated network.
  • the subset of frequency bands may be supported only by a subset of cells associated with the RAN.
  • the spectrum band attribute associated with each network slice identifying the subset of frequency bands used by each network slice is not provided by the RAN to the user equipment in conventional communication systems. Additionally, in conventional systems, the RAN is unable to make the frequency band selection for the user equipment because the RAN is unaware of particular software or application requirements of the user equipment at a given point in time (e.g., which services the UE is mostly interested to access if not all available in a given band). Moreover, user equipment can be configured to reserve particular frequency bands for certain communications (e.g., emergency communications, etc.) and thus cannot use some frequency bands for communication with some network functions (e.g., non-emergency network slices, etc.).
  • some network functions e.g., non-emergency network slices, etc.
  • An example embodiment provides for a registration area update that the user equipment may indicate a requested NSSAI that comprises a list of requested S-NSSAI(s).
  • An Access and Mobility Management Function can take this information into account together with subscribed NSSAI associated with the user equipment to determine allowed NSSAI sent back to the user equipment.
  • the allowed NSSAI represents the list of S-NSSAI(s) that the user equipment can be configured to use for further requests taking place in the current registration area.
  • Such procedures also takes into account whether the requested network slices are supported in the area where the UE is located. It should be appreciated that such aforementioned procedures reoccur with each iteration of registration updates.
  • An example embodiment of the present disclosure optimizes the acceptance of new NSSAI requests and overcome conventional system shortcomings by providing information comprising frequency band and S-NSSAI priority details to the user equipment via/from the RAN.
  • the user equipment can provide informed registration requests based on relationships between cells, network slices, and frequency bands supported by the RAN.
  • Other embodiments of the present disclosure optimize the acceptance of new NSSAI requests and overcome conventional system shortcomings by allowing the RAN to directly select an AMF for the user equipment based on usage information provided by the user equipment to the RAN via at least the radio resource control message carrying the registration request message.
  • An example embodiment provides a core network that can transmit frequency band and cell/slice information to user equipment via a RAN during initial context setup between the network and the user equipment.
  • the RAN receives from the core network a configured NSSAI, associated with the user equipment and in response transmits an enhanced cell reselection priority list to the user equipment during initial context setup.
  • the configured NSSAI can be transmitted to different types of RAN nodes (e.g., cells, NodeB, gNB, NG-RAN node, etc.).
  • the configured NSSAI comprises a plurality of S- NSSAI(s).
  • the RAN e.g., NG-RAN node, etc.
  • the RAN can determine which frequency bands are associated with which networks, network slices, and/or RAN nodes.
  • network slices and/or RAN nodes may communicate over all frequency bands associated with a network.
  • network slices and/or RAN nodes may communicate over only a subset of all frequency bands associated with a network.
  • a network slice may be associated with a plurality of frequency bands.
  • a RAN node may be associated with a plurality of frequency bands.
  • a data object may contain a list of frequency bands that identify a plurality of frequency bands (e.g., at least a subset of frequency bands associated with a RAN node, a RAN, a network slice, a network, a core network, or the like).
  • a plurality of cells, associated with a RAN, and a plurality of network slices may be communicably connected over a plurality of frequency bands.
  • mapping information between network slices and frequency bands of the network in which they are supported is known by the RAN via configuration (e.g., configured by an operating and maintenance system, etc.).
  • the mapping information between network slices and frequency bands of the network in which they are supported is known by the RAN via Xn interface signaling exchanges.
  • a RAN may determine that some frequency bands are compatible with some RAN nodes by transmitting and receiving signals between nodes via one or more Xn interfaces (e.g., associated with respective frequency bands, associated with particular neighboring cells/nodes, supporting particular network slices, etc.).
  • the RAN, or a node thereof may store, for example, successful signaling exchanges for one or more nodes and associate the successful signaling exchanges with one or more frequency bands.
  • the stored successful signaling exchange information for one or more nodes may be used to generate, or determine, at least partially, the mapping information between network slices and frequency bands in the network with at least the frequency bands supported by neighboring RAN nodes.
  • the mapping information may be generated based on Xn interface signaling exchanges between neighboring RAN nodes.
  • the mapping information may be stored by individual RAN nodes within an internal database.
  • the mapping information may comprise a list of cells cross-referenced to a list of frequency bands indicating which frequency bands are supported by which cells.
  • the mapping information may comprise a list of S- NSSAI(s) of the configured NS SAI which are further referenced to the list of cells to indicate which cells, and frequency bands, support which S-NSSAI (i.e., network slices).
  • the mapping information may contain information provided by the core network, or a function thereof.
  • the RAN, or a node thereof may transmit the mapping information to a user equipment for use by the user equipment to identify one or more frequency bands, cells, and/or network slices for communication requests.
  • the RAN, or a node thereof may direct communication requests from a user equipment based on the mapping information.
  • the RAN can transmit the configured NS SAI to the user equipment.
  • the configured NS SAI can be compiled, along with other pertinent cell, frequency band, network slice, or network information, into a cell selection/reselection priorities list that can be utilized by the user equipment to make informed registration/connection/establishment requests via the RAN (e.g., a RAN node, etc.) to the network (e.g., a core network function, etc.).
  • the configured NSSAI can be provided to the user equipment via one or more Radio Resource Control (RRC) messages (e.g., RRC release messages, etc.).
  • RRC Radio Resource Control
  • a ‘cellreselectionprioritylist’ e.g., configured NSSAI and associated bands, or the like
  • the RRC release message may include, without limitation, for each indicated frequency band the list of supported S-NSSAI(s) among the configured NSSAI list.
  • the RAN may not include the configured NSSAI (e.g., because all S-NSSAI associated therewith will be supported by that particular frequency band).
  • a black list (e.g., a list of respective S-NSSAI(s) that are not configured to communicate via one or more respective frequency bands and/or cells) can be configured and transmitted to user equipment (e.g., by the RAN, by the core network, etc.) from the RAN.
  • a white list (e.g., a list of respective S-NSSAI(s) that are configured to communicate via one or more respective frequency bands and/or cells) can be configured and transmitted to user equipment (e.g., by the RAN, by the core network, etc.) from the RAN.
  • a cell reselection/selection priorities list can comprise, at least partially, a white list and/or a black list of respective S-NSSAI(s) of the configured NSSAI (e.g., a subset of the S-NSSAI(s) of the configured NSSAI).
  • the user equipment is aware of any pertinent frequency band(s) that only supports a subset of the network slices the user equipment can potentially request to use (e.g., via the RAN, etc.).
  • An example embodiment provides for a cell reselection/selection priorities list that contains all of the frequency bands in the local area that allows the user equipment to access (e.g., request, register with, etc.) any S-NSSAI of the configured NSSAI for such frequency bands that exist within the local area.
  • the local area may comprise one or more of a RAN, RAN node, PLMN, Stand-alone Non-Public Network (SNPN), a geographic location (e.g., town, county, state, country, or the like), a geolocation radius to a current location, an area of service, the like, or combinations thereof.
  • the additional frequency band information i.e., the cell reselection/selection priorities list, or the like
  • the user equipment may allow the user equipment to find (e.g., request, select, etc.) the right band to serve a requested NSSAI as long as any such band exists in the local area.
  • An example embodiment provides for localized frequency band selection. For example, a limited area of service may be associated with a particular frequency band and a user equipment may know (e.g., via a cell selection priorities list, or the like) that a network slice does not work locally (e.g., within a geolocation radius determined via a user equipment’s global positioning system) in the particular frequency band.
  • the user equipment may not attempt to connect to a network slice via the locally restricted frequency band but may connect via another frequency band, that supports the same network slice, more readily available within the user equipment’s current area of service (e.g., within a current geolocation radius of the user equipment, etc.).
  • a core network may be configured to provide a context setup (e.g., an initial context setup) via the RAN where the RAN transmits frequency band and S-NSSAI priority details (e.g., a cell reselection priorities list, or the like) to the user equipment in response to a user equipment request (e.g., RRC request message, or the like) for new NSSAI.
  • a context setup e.g., an initial context setup
  • S-NSSAI priority details e.g., a cell reselection priorities list, or the like
  • the core network may be configured with logic triggers to generate and/or transmit the said context setup via the RAN, to the user equipment in response to one or more detected conditions (e.g., interaction signals from a RAN, interaction signals from a user equipment, internal configuration changes from other network functions, etc.).
  • the core network may detect an idle-connected transition for a first user equipment and in response the core network, via the RAN, transmits a cell reselection priorities list, comprising a black list, to the first user equipment to utilize for reconnection operations.
  • the core network may detect an initial connection request from a second user equipment and in response the core network provides a cell selection priorities list, comprising a white list, to the second user equipment to utilize for initial context setup.
  • a RAN or the like, that is configured to, at least partially, control or direct selection of a network (e.g., AMF, core network, RAN node, network slice, or the like) for the user equipment.
  • a network e.g., AMF, core network, RAN node, network slice, or the like
  • a first AMF may be isolated from other AMFs of an, at least partially, shared network (e.g., disjoint/isolated network slices configured with respective AMFs, etc.) and therefore the first AMF may be associated with one or more specific network slices that are not associated (e.g., handled by, accessible through, etc.) the other AMFs of the shared network.
  • a cell selection priorities list may be configured to identify (e.g., to a user equipment, RAN, core network, or the like) one or more network functions (e.g., an AMF, etc.) associated with one or more of a cell, a frequency band, a network slice, or the like.
  • network functions e.g., an AMF, etc.
  • NAS Non-Access Stratum
  • a RAN or a node thereof, that may be configured to determine, at least partially, based on signals (e.g., RRC messages, or the like) received from the user equipment, which frequency band(s), cell(s), or AMF(s) to connect the user equipment with, to reach a particular network slice, or network function associated therewith.
  • signals e.g., RRC messages, or the like
  • the user equipment may disconnect from any active RRC connections (e.g., release a current RRC connection) with one or more AMFs, enter an idle mode (e.g., RRC idle, etc.), and transmit a request for new NSSAI without including the current user equipment identifier (e.g., a Globally Unique Access and Mobility Management Function Identity (GUAM!), an S-Temporary Mobile Subscriber Identity (S- TMSI), or the like) in the request message (e.g., RRC request, message 5, etc.).
  • the request for new NS SAI may not contain any user equipment identifiers (e.g., IP address, S-TMSI, GUAM!, or the like).
  • a RAN (e.g., NG-RAN, etc.), that receives the request message, can be configured to determine that the request for the new NS SAI does not comprise a user equipment identifier and in response the RAN determines/selects an AMF that best matches the requested NS SAI.
  • the RAN may determine an AMF from a cell/frequency band/network slice configuration setup, configured on the RAN, which has the most overlap with the NS SAI requested by the user equipment and then the RAN selects the determined AMF as the recipient of the request message and causes transmission of the request message to the selected AMF.
  • the RAN may select one or more AMFs based on the request for the new NS SAI received from the user equipment.
  • the RAN may direct requests to one or more AMFs associated with disjoint/isolated network slices.
  • a user associated with the user equipment may determine whether to include a user equipment identifier (e.g., GUAMI, S-TMSI, etc.) when requesting one or more network slices via a RAN.
  • a user equipment identifier e.g., GUAMI, S-TMSI, etc.
  • An example embodiment provides for a RAN that provides a user equipment with camping policies for a network.
  • the camping policies configure the user equipment to camp on RAN cells/nodes that may serve the greatest possible number of S-NSSAIs of the configured NSSAI.
  • the camping policies may configure the user equipment to avoid frequency bands, and/or cells, that support none of the S-NSSAIs with which the user equipment can potentially register.
  • the RAN may be configured not to provide camping policies with frequency bands that do not support any of the network slices in the configured NSSAI.
  • the RAN may configure the user equipment to establish a connection with a default AMF.
  • the RAN may select/direct the user equipment to connect to a default AMF associated with the same network of the specific AMF.
  • the user equipment may indicate (e.g., via RRC messages, etc.), to the RAN, one or more firmware, software, and/or hardware limitations, or restrictions, associated with the user equipment and, based on this information, the RAN, or a node thereof, may direct the user equipment’s connection request to one or more AMFs (e.g., a specific or default AMF) over one or more frequency bands compatible with one or more respective network slices, cells, and/or the user equipment configuration.
  • AMFs e.g., a specific or default AMF
  • a method that comprises receiving, by a radio access network node from a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the method may further comprise determining, by the radio access network node, a cell reselection priorities list comprising a list of frequency bands, wherein each respective frequency band of the list of frequency bands may be associated with a plurality of network slice identifiers, wherein the plurality of network slice identifiers comprises a subset of the configured network slice selection assistance information.
  • the method may further comprise causing transmission, by the radio access network node to a user equipment, of the cell reselection priorities list.
  • the method may further comprise receiving, by the radio access network node from the user equipment over one of the frequency bands earlier received in the cell reselection priorities list, a radio resource control message containing a registration request message and comprising at least one of the network slice identifiers that was associated with the frequency band within the cell reselection priorities list, wherein the radio access nodes supports communication signaling over the frequency band.
  • the method may further comprise causing transmission, by the radio access network node to the core network, of the registration request message, wherein the registration request message comprises information indicating the network slice associated with the network slice identifier.
  • the method may further comprise receiving, by the radio access network node from the core network, a registration response message comprising an acceptance of the registration request message. In some embodiments, the method may further comprise causing transmission, by the radio access network node to the user equipment, of the registration response message.
  • the radio access network node determines the list of frequency bands in the cell reselection priorities list based on an internal database of the radio access network node comprising mapping information between network slice identifiers and frequency bands supported by the radio access node or frequency bands supported by one or more neighboring radio access nodes.
  • the mapping information of the internal database has been received from an operation and maintenance system.
  • at least part of the mapping information of the internal database has been received from the one or more neighboring radio access nodes via transfer signaling exchange over a direct interface between the radio access network node and the one or more neighboring radio access nodes.
  • the cell reselection priorities list is transmitted to the user equipment within a radio resource control release message.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are unsupported by the respective frequency band.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are supported by the respective frequency band.
  • a respective frequency band in the cell reselection priorities list that is not associated with any single network slice selection assistance information indicates that all network slices identified by the configured network slice selection assistance information are supported in that frequency band.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, by a radio access network node from a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the apparatus may be further caused to at least determine, by the radio access network node, a cell reselection priorities list comprising a list of frequency bands, wherein each respective frequency band of the list of frequency bands may be associated with a plurality of network slice identifiers, wherein the plurality of network slice identifiers comprises a subset of the configured network slice selection assistance information.
  • the apparatus may be further caused to at least cause transmission, by the radio access network node to a user equipment, of the cell reselection priorities list.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to receive, by the radio access network node from the user equipment over one of the frequency bands earlier received in the cell reselection priorities list, a radio resource control message containing a registration request message and comprising at least one of the network slice identifiers that was associated with the frequency band within the cell reselection priorities list, wherein the radio access nodes supports communication signaling over the frequency band.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to cause transmission, by the radio access network node to the core network, of the registration request message, wherein the registration request message comprises information indicating the network slice associated with the network slice identifier.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to receive, by the radio access network node from the core network, a registration response message comprising an acceptance of the registration request message.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to cause transmission, by the radio access network node to the user equipment, of the registration response message.
  • the radio access network node determines the list of frequency bands in the cell reselection priorities list based on an internal database of the radio access network node comprising mapping information between network slice identifiers and frequency bands supported by the radio access node or frequency bands supported by one or more neighboring radio access nodes.
  • the mapping information of the internal database has been received from an operation and maintenance system.
  • at least part of the mapping information of the internal database has been received from the one or more neighboring radio access nodes via transfer signaling exchange over a direct interface between the radio access network node and the one or more neighboring radio access nodes.
  • the cell reselection priorities list is transmitted to the user equipment within a radio resource control release message.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are unsupported by the respective frequency band.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are supported by the respective frequency band.
  • a respective frequency band in the cell reselection priorities list that is not associated with any single network slice selection assistance information indicates that all network slices identified by the configured network slice selection assistance information are supported in that frequency band.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution by at least a processor, to receive, by a radio access network node from a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least determine, by the radio access network node, a cell reselection priorities list comprising a list of frequency bands, wherein each respective frequency band of the list of frequency bands may be associated with a plurality of network slice identifiers, wherein the plurality of network slice identifiers comprises a subset of the configured network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node to a user equipment, of the cell reselection priorities list.
  • the computer program product may be further configured, upon execution by at least the processor, to at least receive, by the radio access network node from the user equipment over one of the frequency bands earlier received in the cell reselection priorities list, a radio resource control message containing a registration request message and comprising at least one of the network slice identifiers that was associated with the frequency band within the cell reselection priorities list, wherein the radio access nodes supports communication signaling over the frequency band.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node to the core network, of the registration request message, wherein the registration request message comprises information indicating the network slice associated with the network slice identifier.
  • the computer program product may be further configured, upon execution by at least the processor, to at least receive, by the radio access network node from the core network, a registration response message comprising an acceptance of the registration request message. In some embodiments, the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node to the user equipment, of the registration response message.
  • the radio access network node determines the list of frequency bands in the cell reselection priorities list based on an internal database of the radio access network node comprising mapping information between network slice identifiers and frequency bands supported by the radio access node or frequency bands supported by one or more neighboring radio access nodes.
  • the mapping information of the internal database has been received from an operation and maintenance system.
  • at least part of the mapping information of the internal database has been received from the one or more neighboring radio access nodes via transfer signaling exchange over a direct interface between the radio access network node and the one or more neighboring radio access nodes.
  • the cell reselection priorities list is transmitted to the user equipment within a radio resource control release message.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are unsupported by the respective frequency band.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are supported by the respective frequency band.
  • a respective frequency band in the cell reselection priorities list that is not associated with any single network slice selection assistance information indicates that all network slices identified by the configured network slice selection assistance information are supported in that frequency band.
  • an apparatus that comprises means for receiving, by a radio access network node from a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the apparatus may further comprise means for determining, by the radio access network node, a cell reselection priorities list comprising a list of frequency bands, wherein each respective frequency band of the list of frequency bands may be associated with a plurality of network slice identifiers, wherein the plurality of network slice identifiers comprises a subset of the configured network slice selection assistance information.
  • the apparatus may further comprise means for causing transmission, by the radio access network node to a user equipment, of the cell reselection priorities list.
  • the apparatus may further comprise means for receiving, by the radio access network node from the user equipment over one of the frequency bands earlier received in the cell reselection priorities list, a radio resource control message containing a registration request message and comprising at least one of the network slice identifiers that was associated with the frequency band within the cell reselection priorities list, wherein the radio access nodes supports communication signaling over the frequency band.
  • the apparatus may further comprise means for causing transmission, by the radio access network node to the core network, of the registration request message, wherein the registration request message comprises information indicating the network slice associated with the network slice identifier.
  • the apparatus may further comprise means for receiving, by the radio access network node from the core network, a registration response message comprising an acceptance of the registration request message. In some embodiments, the apparatus may further comprise means for causing transmission, by the radio access network node to the user equipment, of the registration response message.
  • the radio access network node determines the list of frequency bands in the cell reselection priorities list based on an internal database of the radio access network node comprising mapping information between network slice identifiers and frequency bands supported by the radio access node or frequency bands supported by one or more neighboring radio access nodes.
  • the mapping information of the internal database has been received from an operation and maintenance system.
  • at least part of the mapping information of the internal database has been received from the one or more neighboring radio access nodes via transfer signaling exchange over a direct interface between the radio access network node and the one or more neighboring radio access nodes.
  • the cell reselection priorities list is transmitted to the user equipment within a radio resource control release message.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are unsupported by the respective frequency band.
  • the subset of the configured network slice selection assistance information, associated with each frequency band of the cell reselection priorities list are network slices that are supported by the respective frequency band.
  • a respective frequency band in the cell reselection priorities list that is not associated with any single network slice selection assistance information indicates that all network slices identified by the configured network slice selection assistance information are supported in that frequency band.
  • a method that comprises receiving, by a radio access network node from a network function of a core network, a user equipment configuration setup comprising instructions for direct core network node selection associated with particular registration requests for one or more particular network slices and comprising also configured network slice selection assistance information.
  • the method may further comprise causing transmission, by the radio access network node to a user equipment, of the user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with the core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the method may further comprise receiving, by the radio access network node from the user equipment, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the method may further comprise determining, by the radio access network node based on the network slice selection assistance information, an access and mobility management function at which to direct the registration request, wherein the access and mobility management function supports the network slice selection assistance information.
  • the method may further comprise causing transmission, by the radio access network node, of the registration request to the determined access and mobility management function.
  • the method may further comprise receiving, by the radio access network node from the access and mobility management function in addition to configured network slice selection assistance information, a rejection list comprising at least one rejected single network slice selection assistance information and direct core network node selection information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the method may further comprise generating, by the radio access network node, a cell reselection priorities list and an associated list of network slice identifiers, that includes and prioritizes any applicable frequency bands where the network slices identified by the list of rejected network slice selection assistance information are operating.
  • the user equipment is associated with a CM- CONNECTED state connected to additional network slices with ongoing communications
  • the method may further comprise determining, by the radio access network node, to handover the user equipment to a cell associated with a respective frequency band, wherein the one or more network slices identified by the rejection list and the additional network slices with ongoing communications are supported by the cell and the respective frequency band, wherein a selection of the cell and the respective frequency band is at least partially determined based on the configured network slice selection assistance information.
  • the user equipment is associated with a CM-CONNECTED state connected to additional network slices with ongoing communications
  • the method may further comprise causing transmission, by the radio access network node to the user equipment, of an indication comprising a list of network slices that operate within the respective frequency band of the target cell of the handover, wherein the indication is transmitted within the radio resource control reconfiguration request message triggering the handover.
  • the radio access network node erases the list of rejected network slice selection assistance information from a user equipment context configuration upon completion of the handover.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, by a radio access network node from a network function of a core network, a user equipment configuration setup comprising instructions for direct core network node selection associated with particular registration requests for one or more particular network slices and comprising also configured network slice selection assistance information.
  • the apparatus may be further caused to at least cause transmission, by the radio access network node to a user equipment, of the user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with the core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the apparatus may be further caused to at least receive, by the radio access network node from the user equipment, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the apparatus may be further caused to at least determine, by the radio access network node based on the network slice selection assistance information, an access and mobility management function at which to direct the registration request, wherein the access and mobility management function supports the network slice selection assistance information.
  • the apparatus may be further caused to at least cause transmission, by the radio access network node, of the registration request to the determined access and mobility management function.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to receive, by the radio access network node from the access and mobility management function in addition to configured network slice selection assistance information, a rejection list comprising at least one rejected single network slice selection assistance information and direct core network node selection information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to generate, by the radio access network node, a cell reselection priorities list and an associated list of network slice identifiers, that includes and prioritizes any applicable frequency bands where the network slices identified by the list of rejected network slice selection assistance information are operating.
  • the user equipment is associated with a CM- CONNECTED state connected to additional network slices with ongoing communications
  • the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to determine, by the radio access network node, to handover the user equipment to a cell associated with a respective frequency band, wherein the one or more network slices identified by the rejection list and the additional network slices with ongoing communications are supported by the cell and the respective frequency band, wherein a selection of the cell and the respective frequency band is at least partially determined based on the configured network slice selection assistance information.
  • the user equipment is associated with a CM-CONNECTED state connected to additional network slices with ongoing communications, and the at least one memory and the computer program code configured to, with the at least one processor, further cause the apparatus at least to cause transmission, by the radio access network node to the user equipment, of an indication comprising a list of network slices that operate within the respective frequency band of the target cell of the handover, wherein the indication is transmitted within the radio resource control reconfiguration request message triggering the handover.
  • the radio access network node erases the list of rejected network slice selection assistance information from a user equipment context configuration upon completion of the handover.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution by at least a processor, to receive, by a radio access network node from a network function of a core network, a user equipment configuration setup comprising instructions for direct core network node selection associated with particular registration requests for one or more particular network slices and comprising also configured network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node to a user equipment, of the user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with the core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the computer program product may be further configured, upon execution by at least the processor, to at least receive, by the radio access network node from the user equipment, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the computer program product may be further configured, upon execution by at least the processor, to at least determining, by the radio access network node based on the network slice selection assistance information, an access and mobility management function at which to direct the registration request, wherein the access and mobility management function supports the network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node, of the registration request to the determined access and mobility management function.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least receiving, by the radio access network node from the access and mobility management function in addition to configured network slice selection assistance information, a rejection list comprising at least one rejected single network slice selection assistance information and direct core network node selection information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least generating, by the radio access network node, a cell reselection priorities list and an associated list of network slice identifiers, that includes and prioritizes any applicable frequency bands where the network slices identified by the list of rejected network slice selection assistance information are operating.
  • the user equipment is associated with a CM-CONNECTED state connected to additional network slices with ongoing communications
  • the computer program product may be further configured, upon execution by at least the processor, to at least determine, by the radio access network node, to handover the user equipment to a cell associated with a respective frequency band, wherein the one or more network slices identified by the rejection list and the additional network slices with ongoing communications are supported by the cell and the respective frequency band, wherein a selection of the cell and the respective frequency band is at least partially determined based on the configured network slice selection assistance information.
  • the user equipment is associated with a CM-CONNECTED state connected to additional network slices with ongoing communications
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the radio access network node to the user equipment, of an indication comprising a list of network slices that operate within the respective frequency band of the target cell of the handover, wherein the indication is transmitted within the radio resource control reconfiguration request message triggering the handover.
  • the radio access network node erases the list of rejected network slice selection assistance information from a user equipment context configuration upon completion of the handover.
  • an apparatus that comprises means for receiving, by a radio access network node from a network function of a core network, a user equipment configuration setup comprising instructions for direct core network node selection associated with particular registration requests for one or more particular network slices and comprising also configured network slice selection assistance information.
  • the apparatus may further comprise means for causing transmission, by the radio access network node to a user equipment, of the user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with the core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the apparatus may further comprise means for receiving, by the radio access network node from the user equipment, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the apparatus may further comprise means for determining, by the radio access network node based on the network slice selection assistance information, an access and mobility management function at which to direct the registration request, wherein the access and mobility management function supports the network slice selection assistance information.
  • the apparatus may further comprise means for causing transmission, by the radio access network node, of the registration request to the determined access and mobility management function.
  • the apparatus may further comprise means for receiving, by the radio access network node from the access and mobility management function in addition to configured network slice selection assistance information, a rejection list comprising at least one rejected single network slice selection assistance information and direct core network node selection information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the apparatus may further comprise means for generating, by the radio access network node, a cell reselection priorities list and an associated list of network slice identifiers, that includes and prioritizes any applicable frequency bands where the network slices identified by the list of rejected network slice selection assistance information are operating.
  • the user equipment is associated with a CM- CONNECTED state connected to additional network slices with ongoing communications
  • the apparatus may further comprise means for determining, by the radio access network node, to handover the user equipment to a cell associated with a respective frequency band, wherein the one or more network slices identified by the rejection list and the additional network slices with ongoing communications are supported by the cell and the respective frequency band, wherein a selection of the cell and the respective frequency band is at least partially determined based on the configured network slice selection assistance information.
  • the user equipment is associated with a CM-CONNECTED state connected to additional network slices with ongoing communications
  • the apparatus may further comprise means for causing transmission, by the radio access network node to the user equipment, of an indication comprising a list of network slices that operate within the respective frequency band of the target cell of the handover, wherein the indication is transmitted within the radio resource control reconfiguration request message triggering the handover.
  • the radio access network node erases the list of rejected network slice selection assistance information from a user equipment context configuration upon completion of the handover.
  • a method that comprises generating, by a network function of a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the method may further comprise causing transmission, by the network function to a radio access network node, of the message.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to generate, by a network function of a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the apparatus may be further caused to at least cause transmission, by the network function to a radio access network node, of the message.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution by at least a processor, to generate, by a network function of a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the network function to a radio access network node, of the message.
  • an apparatus that comprises means for generating, by a network function of a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers, and wherein each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • the apparatus may further comprise means for causing transmission, by the network function to a radio access network node, of the message.
  • a method that comprises receiving, by a user equipment from a radio access network node, a user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with a core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the method may further comprise generating, by the user equipment based on at least the user equipment configuration setup, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the method may further comprise causing transmission, by the user equipment to the radio access network node, of the radio resource control message establishment request.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, by a user equipment from a radio access network node, a user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with a core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the apparatus may be further caused to at least generate, by the user equipment based on at least the user equipment configuration setup, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the apparatus may be further caused to at least cause transmission, by the user equipment to the radio access network node, of the radio resource control message establishment request.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution by at least a processor, to receive, by a user equipment from a radio access network node, a user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with a core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the computer program product may be further configured, upon execution by at least the processor, to at least generate, by the user equipment based on at least the user equipment configuration setup, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the computer program product may be further configured, upon execution by at least the processor, to at least cause transmission, by the user equipment to the radio access network node, of the radio resource control message establishment request.
  • an apparatus that comprises means for receiving, by a user equipment from a radio access network node, a user equipment configuration setup, wherein the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with a core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • the apparatus may further comprise means for generating, by the user equipment based on at least the user equipment configuration setup, a radio resource control message establishment request comprising a registration request and network slice selection assistance information, wherein the radio resource control message establishment request does not contain user equipment identifiers, wherein the user equipment identifiers comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • the apparatus may further comprise means for causing transmission, by the user equipment to the radio access network node, of the radio resource control message establishment request.
  • FIG. 1 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 2 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 3 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 4 illustrates an example computing device for communicating over communication networks with other network entities, according to some embodiments
  • FIG. 5 illustrates an example architecture for a communications network comprising network slices, according to some embodiments
  • FIG. 6 is a flow diagram illustrating the signaling between network entities via a network infrastructure, according to some embodiments.
  • FIG. 7 is a flow diagram illustrating the signaling between network entities via a network infrastructure, according to some embodiments.
  • FIG. 8 is a flow diagram illustrating the signaling between network entities via a network infrastructure, according to some embodiments.
  • FIG. 9 is a flow chart illustrating example operations performed, such as by a communication device or other client device, in accordance with some example embodiments.
  • FIG. 10 is a flow chart illustrating example operations performed, such as by a communication device or other client device, in accordance with some example embodiments;
  • FIG. 11 is a flow chart illustrating example operations performed, such as by a communication device or other client device, in accordance with some example embodiments.
  • FIG. 12 is a flow chart illustrating example operations performed, such as by a communication device or other client device, in accordance with some example embodiments.
  • data can be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with certain embodiments of the present invention.
  • use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims.
  • circuitry also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • circuitry as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
  • node As used herein, the terms “node,” “entity,” “intermediary,” “intermediate entity,” “go-between,” and similar terms can be used interchangeably to refer to computers connected via, or programs running on, a network or plurality of networks capable of data creation, modification, deletion, transmission, receipt, and/or storage in accordance with an example embodiment of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
  • the terms “user equipment,” “user device,” “device,” “apparatus,” “mobile device,” “personal computer,” “laptop computer,” “laptop,” “desktop computer,” “desktop,” “mobile phone,” “tablet,” “smartphone,” “smart device,” “cellphone,” “computing device,” “communication device,” “user communication device,” “terminal,” and similar terms can be used interchangeably to refer to an apparatus, such as may be embodied by a computing device, configured to access a network or plurality of networks for at least the purpose of wired and/or wireless transmission of communication signals in accordance with certain embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.
  • network slice can be used interchangeably to refer to an end to end logical communication network, or portion thereof, within a Public Land Mobile Network (PLMN), Stand-Alone Non-Public Network (SNPN), a Public Network Integrated NPN (PNI-NPN), and/or the like.
  • PLMN Public Land Mobile Network
  • SNPN Stand-Alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • a medium can take many forms, including, but not limited to a non- transitory computer-readable storage medium (e.g., non-volatile media, volatile media), and transmission media.
  • Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves.
  • Non-transitory computer-readable media include a magnetic computer readable medium (e.g., a floppy disk, hard disk, magnetic tape, any other magnetic medium), an optical computer readable medium (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc (DVD), a Blu-Ray disc (BD), the like, or combinations thereof), a random access memory (RAM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), a FLASH-EPROM, or any other non-transitory medium from which a computer can read.
  • a magnetic computer readable medium e.g., a floppy disk, hard disk, magnetic tape, any other magnetic medium
  • an optical computer readable medium e.g., a compact disc read only memory (CD-ROM), a digital versatile disc (DVD), a Blu-Ray disc (BD), the like, or combinations thereof
  • RAM random access memory
  • PROM programmable read only memory
  • EPROM era
  • computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it will be appreciated that where certain embodiments are described to use a computer-readable storage medium, other types of computer-readable mediums can be substituted for or used in addition to the computer- readable storage medium in alternative embodiments.
  • a communication device or terminal can be provided for wireless access via cells, base stations, access points, the like (e.g., wireless transmitter and/or receiver nodes providing access points for a radio access communication system and/or other forms of wired and/or wireless networks), or combinations thereof.
  • wired and/or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G, and/or any other similar or yet to be developed future communication network standards.
  • the present disclosure contemplates that any methods, apparatuses, computer program codes, and any portions or combination thereof can also be implemented with yet undeveloped communication networks and associated standards as would be developed in the future and understood by one skilled in the art in light of the present disclosure.
  • Access points and hence communications there through are typically controlled by at least one appropriate control apparatus so as to enable operation thereof and management of mobile communication devices in communication therewith.
  • a control apparatus for a node can be integrated with, coupled to, and/or otherwise provided for controlling the access points.
  • the control apparatus can be arranged to allow communications between a user equipment and a core network or a network entity of the core network.
  • control apparatus can comprise at least one memory, at least one data processing unit such as a processor or the like, and an input/output interface (e.g., global positioning system receiver/transmitter, keyboard, mouse, touchpad, display, universal serial bus (USB), Bluetooth, ethernet, wired/wireless connections, the like, or combinations thereof).
  • input/output interface e.g., global positioning system receiver/transmitter, keyboard, mouse, touchpad, display, universal serial bus (USB), Bluetooth, ethernet, wired/wireless connections, the like, or combinations thereof.
  • control apparatus via the interface, can be coupled to relevant other components of the access point.
  • the control apparatus can be configured to execute an appropriate software code to provide the control functions. It shall be appreciated that similar components can be provided in a control apparatus provided elsewhere in the network system, for example in a core network entity.
  • the control apparatus can be interconnected with other control entities.
  • the control apparatus and functions can be distributed between several control units.
  • each base station can comprise a control apparatus.
  • Access points and associated controllers can communicate with each other via a fixed line connection and/or via a radio interface.
  • the logical connection between the base station nodes can be provided for example by an X2 interface, an SI interface, a similar interface, or combinations thereof. This interface can be used for example for coordination of operation of the stations and performing reselection or handover operations.
  • the logical communication connection between the initial communication node and the final communication node of the network can comprise a plurality of intermediary nodes. Additionally, any of the nodes can be added to and removed from the logical communication connection as required to establish and maintain a network function communication.
  • the communication device or user equipment can comprise any suitable device capable of at least receiving a communication signal comprising data.
  • the communication signal can be transmitted via a wired connection, a wireless connection, or combinations thereof.
  • the device can be a handheld data processing device equipped with radio receiver, data processing and user interface apparatus.
  • Non-limiting examples include a mobile station (MS) such as a mobile phone or what is known as a ‘smart phone,’ a portable computer such as a laptop or a tablet computer provided with a wireless interface card or other wireless interface facility, personal data assistant (PDA) provided with wireless communication capabilities, or any combinations of these or the like.
  • MS mobile station
  • PDA personal data assistant
  • a communication device e.g., configured for communication with the wireless network or a core network entity, can be exemplified by a handheld or otherwise mobile communication device or user equipment.
  • a mobile communication device can be provided with wireless communication capabilities and appropriate electronic control apparatus for enabling operation thereof.
  • the communication device can be provided with at least one data processing entity, for example a central processing unit and/or a core processor, at least one memory and other possible components such as additional processors and memories for use in software and hardware aided execution of tasks it is designed to perform.
  • the data processing, storage, and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets.
  • Data processing and memory functions provided by the control apparatus of the communication device are configured to cause control and signaling operations in accordance with certain embodiments as described later in this description.
  • a user can control the operation of the communication device by means of a suitable user interface such as touch sensitive display screen or pad and/or a keypad, one of more actuator buttons, voice commands, combinations of these, or the like.
  • a speaker and a microphone are also typically provided.
  • a mobile communication device can comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • a communication device can communicate wirelessly via one or more appropriate apparatuses for receiving and transmitting signals (e.g., global positioning system receiver/transmitter, remote touchpad interface with remote display, Wi-Fi interface, etc.).
  • a radio unit can be connected to the control apparatus of the device.
  • the radio unit can comprise a radio part and associated antenna arrangement.
  • the antenna arrangement can be arranged internally or externally to the communication device.
  • FIGS. 1-3 illustrate various example architectures for a communications network 100 in which the various methods, apparatuses, and computer program products can be carried out and/or used.
  • the communications network 100 can comprise any suitable configuration, number, orientation, positioning, and/or dimensions of components and specialized equipment configured to provide an air interface (e.g., New Radio (NR)) for communication or connection between a User Equipment 102 (UE 102) and a Data Network 116 (DN 116) via a Core Network 101 (CN 101) of the communications network 100.
  • NR New Radio
  • UE 102 User Equipment 102
  • DN 116 Data Network 116
  • CN 101 Core Network 101
  • the UE 102 can be associated with one or more devices associated with one or more network function (NF) service consumers.
  • NF network function
  • a communications network 100 can be provided in which the UE 102 is in operable communication with the Radio Access Network 104 (RAN 104), such as by way of a transmission tower, a base station, an access point, a network node, and/or the like.
  • the RAN 104 can communicate with the CN 101 or a component or entity thereof.
  • the CN 101 can facilitate communication between the UE 102 and the DN 116, such as for sending data, messages, requests, the like, or combinations thereof.
  • the DN 116 or the CN 101 can be in communication with an Application Server or Application Function 112 (AS/AF 112).
  • AS/AF 112 Application Server or Application Function 112
  • the RAN 104, CN 101, DN 116, and/or AS/AF 112 can be associated with a Network Repository Function (NRF), NF service producer, Service Communication Proxy (SCP), Security Edge Protection Proxy (SEPP), Policy Charging Function (PCF), the like, or combinations thereof.
  • NRF Network Repository Function
  • SCP Service Communication Proxy
  • SEPP Security Edge Protection Proxy
  • PCF Policy Charging Function
  • the communications network 100 can comprise a series of connected network devices and specialized hardware that is distributed throughout a service region, state, province, city, or country, and one or more network entities, which can be stored at and/or hosted by one or more of the connected network devices or specialized hardware.
  • the UE 102 can connect to the RAN 104, which can then relay the communications between the UE 102 and the CN 101, the CN 101 being connected to the DN 116, which can be in communication with one or more AS/AF 112.
  • the UE 102 can be in communication with a RAN 104, which can act as a relay between the UE 102 and other components or services of the CN 101.
  • the UE 102 can communicate with the RAN 104, which can in turn communicate with an Access and Mobility Management Function 108 (AMF 108).
  • AMF 108 Access and Mobility Management Function
  • the UE 102 can communicate directly with the AMF 108.
  • the AMF 108 can be in communication with one or more network functions (NFs), such as an Authentication Server Function 120 (AUSF 120), a Network Slice Selection Function 122 (NSSF 122), a Network Repository Function 124 (NRF 124), a Policy Charging Function 114 (PCF 114), a Unified Data Management function 118 (UDM 118), the AS/AF 112, a Session Management Function 110 (SMF 110), and/or the like.
  • NFs network functions
  • AUSF 120 Authentication Server Function 120
  • NSSF 122 Network Slice Selection Function 122
  • NRF 124 Network Repository Function 124
  • PCF 114 Policy Charging Function 114
  • UDM 118 Unified Data Management function 118
  • AS/AF 112 Session Management Function 110
  • SMS 110 Session Management Function 110
  • the SMF 110 can be in communication with one or more User Plane Functions 106 (UPF 106, UPF 106a, UPF 106b, collectively “UPF 106”).
  • UPF 106 User Plane Functions 106
  • the UPF 106 can be in communication with the RAN 104 and the DN 116.
  • the DN 116 can be in communication with a first UPF 106a and the RAN 104 can be in communication with a second UPF 106b, while the SMF 110 is in communication with both the first and second UPFs 106a, b and the first and second UPFs 106a, b are in communication each with the other.
  • the UE 102 can comprise a single-mode or a dual-mode device such that the UE 102 can be connected to one or more RANs 104.
  • the RAN 104 can be configured to implement one or more Radio Access Technologies (RATs), such as Bluetooth, Wi-Fi, and Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), LIE or 5G NR, among others, that can be used to connect the UE 102 to the CN 101.
  • RATs Radio Access Technologies
  • GSM Global System for Mobile Communication
  • UMTS Universal Mobile Telecommunications System
  • LIE Universal Mobile Telecommunications System
  • 5G NR 5G NR
  • the RAN 104 can comprise or be implemented using a chip, such as a silicon chip, in the UE 102 that can be paired with or otherwise recognized by a similar chip in the CN 101, such that the RAN 104 can establish a connection or line of communication between the UE 102 and the CN 101 by identifying and pairing the chip within the UE 102 with the chip within the CN 101.
  • the RAN 104 can implement one or more base stations, towers or the like to communicate between the UE 102 and the AMF 108 of the CN 101.
  • the communications network 100 or components thereof can be configured to communicate with a communication device (e.g., the UE 102) such as a cell phone or the like over multiple different frequency bands, e.g., FR1 (below 6 GHz), FR2 (mm Wave), other suitable frequency bands, sub-bands thereof, and/or the like.
  • a communication device e.g., the UE 102
  • the communications network 100 can comprise or employ massive Multiple Input and Multiple Output (MIMO) antennas.
  • MIMO Multiple Input and Multiple Output
  • the communications network 100 can comprise Multi-User MIMO (MU-MIMO) antennas.
  • MU-MIMO Multi-User MIMO
  • the communications network 100 can employ edge computing whereby the computing servers are communicatively, physically, computationally, and/or temporally closer to the communications device (e.g., UE 102) in order to reduce latency and data traffic congestion.
  • the communications network 100 can employ other technologies, devices, or techniques, such as small cell, low-powered RAN, beamforming of radio waves, Wi-Fi cellular convergence, Non-Orthogonal Multiple Access (NOMA), channel coding, the like, or combinations thereof.
  • technologies, devices, or techniques such as small cell, low-powered RAN, beamforming of radio waves, Wi-Fi cellular convergence, Non-Orthogonal Multiple Access (NOMA), channel coding, the like, or combinations thereof.
  • NOMA Non-Orthogonal Multiple Access
  • the UE 102 can be configured to communicate with the RAN 104 in a N1 interface, e.g., according to a Non-Access Stratum (NAS) protocol.
  • RAN 104 can be configured to communicate with the CN 101 or a component thereof (e.g., the AMF 108) in a N2 interface, e.g., in a control plane between a base station of the RAN 104 and the AMF 108.
  • the RAN 104 can be configured to communicate with the UPF 106 in an N3 interface, e.g., in a user plane.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with other services or network entities within the CN 101 in various different interfaces and/or according to various different protocols.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the AUSF 120 in an Nausf interface or an N12 interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the NSSF 122 in an Nnssf interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the NRF 124 in an Nnrf interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the PCF 114 in an Npcf interface or an N7 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the NWDAF 126 in an Nnwdaf interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the UDM 118 in an Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the AS/AF 112 in an Naf interface.
  • the SMF 110 can be configured to communicate with the UPF 106 in an N4 interface, which can act as a bridge between the control plane and the user plane, such as acting as a conduit for a Protocol Data Unit (PDU) session during which information is transmitted between, e.g., the UE 102 and the CN 101 or components/services thereof.
  • PDU Protocol Data Unit
  • FIGS. 1-3 illustrate various configurations and/or components of an example architecture of the communications network 100, many other systems, system configurations, networks, network entities, and pathways/protocols for communication therein are contemplated and considered within the scope of this present disclosure.
  • the apparatus 200 of an example embodiment can be configured to perform the functions described herein.
  • the apparatus 200 can more generally be embodied by a computing device, such as a server, a personal computer, a computer workstation or other type of computing device including those functioning as a user equipment and/or a component of a wireless network or a wireless local area network.
  • the apparatus of an example embodiment can be configured as shown in FIG. 4 so as to include, be associated with or otherwise be in communication with a processor 202 and a memory device 204 and, in some embodiments, and/or a communication interface 206.
  • the apparatus of an example embodiment may also optionally include a user interface, such as a touch screen, a display, a keypad, the like, or combinations thereof.
  • a user interface such as a touch screen, a display, a keypad, the like, or combinations thereof.
  • the apparatus according to an example embodiment can be configured with a global positioning circuit that comprises a global positioning receiver and/or global positioning transmitter configured for communication with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, the like, or combinations thereof).
  • the global positioning circuit may be configured for the transmission and/or receipt of direct/indirect satellite and/or cell signals in order to determine geolocation data (e.g., latitude, longitude, elevation, altitude, geographic coordinates, the like, or combinations thereof.) for the apparatus and/or another communication device associated with the apparatus or the one or more global navigation satellite systems.
  • geolocation data may comprise a time dimension, such as a time stamp that associates the geolocation data with a respective time (e.g., 01 :00 AM EST, etc.), a respective date (e.g., September 26, 2020, etc.), and/or the like.
  • the time dimension may be configured based on one or more of a time of receipt, generation, transmission, and/or the like (e.g., by the apparatus).
  • geolocation data may be associated with one or more time dimensions.
  • the processor 202 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) can be in communication with the memory device 204 via a bus for passing information among components of the apparatus 200.
  • the memory device can include, for example, one or more volatile and/or non-volatile memories, such as a non-transitory memory device.
  • the memory device can be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that can be retrievable by a machine (e.g., a computing device like the processor).
  • the memory device can be configured to store information, data, content, applications, instructions, the like, or combinations thereof for enabling the apparatus to carry out various functions in accordance with an example embodiment.
  • the memory device could be configured to buffer input data for processing by the processor.
  • the memory device could be configured to store instructions for execution by the processor.
  • the apparatus 200 can, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus can be embodied as a chip or chip set. In other words, the apparatus can comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly can provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus can therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset can constitute means for performing one or more operations for providing the functionalities described herein.
  • a chip or chipset can constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 202 can be embodied in a number of different ways.
  • the processor can be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Micro-Controller Unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor can include one or more processing cores configured to perform independently.
  • a multi-core processor can enable multiprocessing within a single physical package.
  • the processor can include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor 202 can be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor can be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor can represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA, the like, or combinations thereof the processor can be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions can specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed.
  • the processor can be a processor of a specific device (e.g., an encoder and/or a decoder) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein.
  • the processor can include, among other things, a clock, an Arithmetic Logic Unit (ALU) and logic gates configured to support operation of the processor.
  • ALU Arithmetic Logic Unit
  • the communication interface can be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus 200, such as network functions, network repository functions, a base station, an access point, service communication proxies, UE 102, RAN 104, core network services, AS/AF 112, a database or other storage device, the like, or combinations thereof.
  • the communication interface can include, for example, one or more antennas and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface can include the circuitry for interacting with the one or more antennas to cause transmission of signals via the one or more antennas or to handle receipt of signals received via the one or more antennas.
  • the one or more antennas may comprise one or more of a dipole antenna, monopole antenna, helix antenna, loop antenna, waveguide, horn antenna, parabolic reflectors, corner reflectors, dishes, micro strip patch array, convex-plane, concaveplane, convex-convex, concave-concave lenses, the like or combinations thereof.
  • the communication interface can alternatively or also support wired communication.
  • the communication interface can include a communication modem and/or other hardware/software for supporting communication via cable, Digital Subscriber Line (DSL), USB, the like or combinations thereof.
  • a session management function (e.g., SMF 110) can comprise a 5GC session management function for any suitable Control and User Plane Separation (CUPS) architecture, such as for the General Packet Radio Service (GPRS), Gateway GPRS Support Node Control plane function (GGSN-C), Trusted Wireless Access Gateway Control plane function (TWAG-C), Broadband Network Gateway Control and User Plane Separation (BNG- CUPS), N4 interface, Sxa interface, Sxb interface, Sxc interface, Evolved Packet Core (EPC) Serving Gateway Control plane function (SGW-C), EPC Packet Data Network Gateway Control plane function (PGW-C), EPC Traffic Detection Control plane function (TDF-C), the like, or combinations thereof.
  • GPRS General Packet Radio Service
  • GGSN-C Gateway GPRS Support Node Control plane function
  • TWAG-C Trusted Wireless Access Gateway Control plane function
  • BNG- CUPS Broadband Network Gateway Control and User Plane Separation
  • the apparatus 200 can include a processor 202 in communication with a memory 204 and configured to provide signals to and receive signals from a communication interface 206.
  • the communication interface 206 can include a transmitter and a receiver.
  • the processor 202 can be configured to control the functioning of the apparatus 200, at least in part.
  • the processor 202 can be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver.
  • the processor 202 can be configured to control other elements of apparatus 200 by effecting control signaling via electrical leads connecting the processor 202 to the other elements, such as a display or the memory 204.
  • the apparatus 200 can be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like.
  • Signals sent and received by the processor 202 can include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, Wireless Local Access Network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, Asymmetric Digital Subscriber Line (ADSL), Data Over Cable Service Interface Specification (DOCSIS), the like, or combinations thereof.
  • these signals can include speech data, user generated data, user requested data, the like, or combinations thereof.
  • the apparatus 200 and/or a cellular modem therein can be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, Session Initiation Protocol (SIP)), the like, or combinations thereof.
  • the apparatus 200 can be capable of operating in accordance with 2G wireless communication protocols Interim Standard (IS) 136 (IS-136), Time Division Multiple Access (TDMA), GSM, IS-95, Code Division Multiple Access, Code Division Multiple Access (CDMA), the like, or combinations thereof.
  • the apparatus 200 can be capable of operating in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), the like, or combinations thereof.
  • EDGE Enhanced Data GSM Environment
  • the apparatus 200 can be capable of operating in accordance with 3G wireless communication protocols, such as UMTS, Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division- Synchronous Code Division Multiple Access (TD-SCDMA), the like, or combinations thereof.
  • 3G wireless communication protocols such as UMTS, Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division- Synchronous Code Division Multiple Access (TD-SCDMA), the like, or combinations thereof.
  • the NA 200 can be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the like, or combinations thereof.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the apparatus 200 can be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that can be subsequently developed.
  • the apparatus 200 can be capable of operating according to or within the framework of any suitable CUPS architecture, such as for the gateway GGSN-C, TWAG-C, Broadband Network Gateways (BNGs), N4 interface, Sxa interface, Sxb interface, Sxc interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, the like, or combinations thereof.
  • BNGs Broadband Network Gateways
  • N4 interface such as for the gateway GGSN-C, TWAG-C, Broadband Network Gateways (BNGs), N4 interface, Sxa interface, Sxb interface, Sxc interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, the like, or combinations thereof.
  • the apparatus and method may be configured to operate in conjunction with a number of other types of
  • a “computer-readable medium” can be any non- transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 4.
  • the computer-readable medium can comprise a non-transitory computer-readable storage medium that can be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • FIG. 5 illustrates an example communication network 500 that comprises two example network slices.
  • the UE 102 utilizes at least Communication Interface 206 to establish one or more network connections by way of causing transmission and receipt of communication signals between the UE 102 via at least Communication Interface 206 and the Common Network Functions 503, the First Network Slice 501, and/or the Second Network Slice 502.
  • the Communication Interface 206 can connect the UE 102 directly to the First Network Slice 501 and/or the Second Network Slice 502 thus bypassing the Common Network Functions 503.
  • Communication Interface 206 can connect the UE 102 indirectly to the First Network Slice 501 and/or the Second Network Slice 502 by establishing a connection through the Common Network Functions 503 first.
  • UE 102 can connect to a plurality of public and/or private networks and/or a plurality of public and/or private network slices by way of Communication Interface 206.
  • Communication Interface 206 may be communicably connected to one or more of a RAN, cell, gNB, ng-eNB, NodeB, the like, or combinations thereof such that communication signals can be transmitted and received therethrough.
  • the First Network Slice 501 and/or the Second Network Slice 502 may comprise, at least partially, one or more network functions of the Common Network Functions 503.
  • access to the First Network Slice 501 may be controlled and/or serviced by a first AMF and access to the Second Network Slice 502 may be controlled and/or serviced by a second AMF separate from the first AMF.
  • the first AMF of the First Network Slice 501 may be independent (e.g., disjoint/isolated, communicably separated, etc.) from the Second Network Slice 502.
  • the second AMF of the Second Network Slice 502 may be independent (e.g., disjoint/isolated, communicably separated, etc.) from the First Network Slice 501.
  • the Common Network Functions 503 may comprise one or more duplicate network functions (e.g., AMF 108, etc.) that are configured to provide service for one or more network slices.
  • access to the First Network Slice 501 may be controlled and/or serviced by a first AMF (e.g., AMF 108 of the Common Network Functions 503) and access to a plurality of other network slices may be controlled and/or serviced by at least a second AMF of the Common Network Functions 503.
  • a subset of the Common Network Functions 503 may be shared by one or more network slices (e.g., to reduce network resource usage, etc.).
  • a subset of the Common Network Functions 503 may be isolated from one or more network slices (e.g., for security purposes, etc.).
  • a network slice may not share any of the Common Network Functions 503 with one or more other network slices but still comprises a portion of the network architecture (e.g., a shared server, a shared RAN, or the like).
  • the First Network Slice 501 comprises a plurality of network functions including at least Network Repository Function 1 (NRF1) 124a, Policy Charging Function 1 (PCF1) 114a, User Plane Function 1 (UPF1) 106a, and Session Management Function 1 (SMF1) 110a.
  • NRF1 Network Repository Function 1
  • PCF1 Policy Charging Function 1
  • UPF1 User Plane Function 1
  • SMF1 Session Management Function 1
  • the First Network Slice 501 is configured to connect the UE 102 to Data Network 1 (DN1) 116a.
  • the Second Network Slice 502 comprises a plurality of network functions including at least Network Repository Function 2 (NRF2) 124b, Policy Charging Function 2 (PCF2) 114b, User Plane Function 2 (UPF2) 106b, and Session Management Function 2 (SMF2) 110b.
  • NRF2 Network Repository Function 2
  • PCF2 Policy Charging Function 2
  • UPF2 User Plane Function 2
  • SMF2 Session Management Function 2
  • Each of the network functions of the Second Network Slice 502 is independent of the Common Network Functions 503 and the network functions associated with the First Network Slice 501.
  • the Second Network Slice 502 is configured to connect the UE 102 to Data Network 2 (DN2) 116b.
  • the example communication network 500 of FIG. 5 comprises one or more of a Public Land Mobile Network (PLMN), Stand-Alone Non-Public Network (SNPN), a Public Network Integrated NPN (PNI-NPN), and/or the like.
  • PLMN Public Land Mobile Network
  • SNPN Stand-Alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the First Network Slice 501 may be configured, with Common Network Functions 502, as part of a PLMN such that UE 102 can access the First Network Slice 501 without undergoing onboarding procedures or authentication of credentials.
  • the Second Network Slice 502 may be configured as a PNI-NPN which operates with the support of the PLMN, that comprises the First Network Slice 501 and Common Network Functions 502, but further requires that UE 102 belongs to a particular tenant type in order to be eligible to use the Second Network Slice 502. [00121] Moreover, in certain embodiments, to access the Second Network Slice 502 UE 102 will have to undergo an onboarding procedure and/or authentication of credentials that incorporates the credentials associated with UE 102 and one or more Service Level Agreements (SLAs) and/or subscriptions.
  • SLAs Service Level Agreements
  • First Network Slice 501 and/or the Second Network Slice 502 may be configured, in accordance with some embodiments, as a network separate from example communication network 500, rather than as a network slice, such as an SNPN that supports authentication and/or onboarding procedures.
  • a plurality of additional network slices may be incorporated into example communication network 500 with each network slice configured with or without authentication feature requirements, with or without onboarding features for unregistered user equipment, and/or a plurality of network functions (e.g., an NRF, UPF, PCF, SMF, AS/AF, AUSF, DN, etc ).
  • network functions e.g., an NRF, UPF, PCF, SMF, AS/AF, AUSF, DN, etc.
  • FIG. 6 illustrates a flow chart that depicts an example signal sequence 600, for the provision of an initial context setup, between communication devices (e.g., UE 102, a server hosting AMF 108, apparatus 200, etc.) by way of at least a network infrastructure (e.g., communications network 100, 500, or the like).
  • the example network infrastructure utilized for signal sequence 600 comprises at least AMF 108, RAN 104, and UE 102.
  • the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LIE, etc.), and that RAN 104 can comprise one or more 5G radio nodes, such as one or more gNBs or equivalent.
  • the example signal sequence 600 may be implemented utilizing one or more network infrastructures associated with one or more networks (e.g., a PLMN, an SNPN, etc.) via at least a shared RAN.
  • each of the one or more networks comprises one or more network slices (e.g., 501, 502, or the like).
  • the communications network by way of AMF 108 and RAN 104, transmits information about the availability of cells and frequency bands that can serve particular network slices, via the RAN 104, to UE 102 during the initial context setup with AMF 108.
  • the initial context setup between UE 102, RAN 104, and AMF 108 references the initial setup procedures in relation to the establishment of a respective connection and does not take into account any prior contact with the AMF 108, such as in conjunction with the establishment of prior connections or for other purposes other than the establishment of the respective connection.
  • a cell selection/reselection priorities list may alternatively, or additionally be transmitted during initial contact, or communications to establish a connection, between UE 102 and AMF 108, by way of RAN 104, whether initiated by UE 102 or AMF 108.
  • one or more priorities lists may be transmitted to, and/or utilized by, UE 102 during operations wherein UE 102 disconnects from a first network slice, enters an idle mode, and initiates connection operations to a second network slice, via RAN 104.
  • AMF 108, and/or RAN 104 may be configured to continuously or periodically send the cell selection/reselection priorities list to one or more UEs camped on an associated network node.
  • a UE may be determined to be camped on a network in an instance that the UE remains in an idle mode within a cell, associated with the network, such that the UE is ready to initiate a potential dedicated service or is ready to receive an ongoing broadcast service from the network by way of at least a network function.
  • the UE By camping on a cell in an idle mode, or state, the UE is able to receive information pertinent to the camped network (e.g., a cell selection/reselection priorities list, white list, black list, and/or the like) and/or initiate a connection (e.g., via RRC messages, or the like) with the camped network, for example, via at least AMF 108 and RAN 104.
  • information pertinent to the camped network e.g., a cell selection/reselection priorities list, white list, black list, and/or the like
  • a connection e.g., via RRC messages, or the like
  • UE 102 may be configured with camping policies provided by RAN 104.
  • the camping policies may configure UE 102 to camp on cells/nodes of RAN 104 that may serve the greatest possible number of S- NSSAIs of the configured NS SAI.
  • UE 102 may be camped on a plurality of networks via a plurality of cells.
  • UE 102 may request network and/or specific network slice information on-demand and/or in real-time upon receipt of an input signal from a user and/or an application associated with UE 102.
  • UE 102 may request from a first network, without an established connection, a cell selection priorities list, and UE 102 may enter an idle mode with a second network and, thereby, automatically receive a cell reselection priorities list.
  • the respective cell selection/reselection priorities lists comprise a plurality of cells, frequency bands, and network slices (e.g., S-NSSAI, etc.) associated with the first network and the second network respectively.
  • AMF 108 transmits the Application Protocol (AP) Initial Context setup information to RAN 104 for storage and further transmission to UE 102.
  • the AP Initial Context setup information comprises the configured NS SAI for the UE (e.g., network slices, and/or the like) associated with AMF 108.
  • a 5GC determines (e.g., via communication message received from the RAN 104) that UE 102 is transiting to a connected mode, via RAN 104, and, in response, causes transmission of the NGAP
  • Initial Context setup data that comprises the configured NSSAI for UE 102, the setup data is stored, at least partially and/or temporarily, by an NG-RAN node (e.g., at least until it is transmitted onto UE 102).
  • a 5GC receives a new NSSAI request (e.g., RRC message request via RAN, or the like) from UE 102, via RAN 104, and, in response, causes transmission of the NGAP
  • a new NSSAI request e.g., RRC message request via RAN, or the like
  • the setup data is stored, at least partially and/or temporarily, by an NG-RAN node (e.g., at least until it is transmitted onto UE 102).
  • the RRC message 606, or the like may comprise a list of respective S-NSSAI(s) that are not configured to communicate via one or more respective frequency bands and/or cells (i.e., a black list). In some embodiments, the RRC message 606, or the like, may comprise a list of respective S-NSSAI(s) that are configured to communicate via one or more respective frequency bands and/or cells (i.e., a white list).
  • RAN 104 is in the connected phase with UE 102.
  • UE 102 is in the Radio Resource Control (RRC) connected phase/state and is configured to actively send and/or receive data and/or signals with RAN 104 via a node associated therewith.
  • RRC Radio Resource Control
  • RAN 104 causes transmission of the RRC release message to UE 102 to remove UE 102 from the RRC connected phase/state.
  • the RRC release message includes one or more priorities lists that comprise respective network slice information and the respective frequency band(s) and/or cell(s) associated therewith. For example, UE 102 may determine that it requires network functions associated with a network slice not supported by the current RRC connection. UE 102 receives, from RAN 104, the RRC release message and moves from the connected state to the idle mode (e.g., to save power, to switch to a new network slice, etc.).
  • UE 102 further receives, via the RRC release message from RAN 104, the cell frequency priorities list (e.g., a white list, black list, or the like) and can then initiate a new connection with one or more network slices in accordance with the cell frequency priorities list.
  • a cell selection/reselection priorities list shall contain all frequency bands in the local area that allow UE 102 to access one or more S- NSSAI(s) of the configured NSSAI if such a frequency band exists and is supported by one or more cells of RAN 104.
  • the new information provided to UE 102 may be used by UE 102 to determine and/or select the frequency band and/or cell that serves a particular network slice as long as such a frequency band exists in the local area.
  • the local area may comprise one or more of RAN 104, a gNB, an NG-RAN, a PLMN, an SNPN, a geographic location (e.g., town, county, state, country, or the like), a geolocation radius around UE 102 (e.g., determined via a global positioning system, cell triangulation, and/or the like), an area of service, the like, or combinations thereof.
  • RAN 104 e.g., a gNB, an NG-RAN, a PLMN, an SNPN, a geographic location (e.g., town, county, state, country, or the like), a geolocation radius around UE 102 (e.g., determined via a global positioning system, cell triangulation, and/or the like), an area of service, the like, or combinations thereof.
  • a geographic location e.g., town, county, state, country, or the like
  • a geolocation radius around UE 102 e.g., determined via
  • FIG. 7 illustrates a flow chart that depicts an example signal sequence 700, for the provision of RAN assisted network slice selection, between communication devices (e.g., UE 102, a server hosting AMF 108, apparatus 200, etc.) by way of at least a network infrastructure (e.g., communications network 100, 500, or the like).
  • the example network infrastructure utilized for signal sequence 700 comprises at least a First Access and Mobility Management Function (AMF1) 108a, a Second Access and Mobility Management Function (AMF2) 108b, RAN 104, and UE 102.
  • AMF1 First Access and Mobility Management Function
  • AMF2 Second Access and Mobility Management Function
  • the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LTE, etc.), and that RAN 104 can comprise one or more 5G radio nodes, such as one or more gNBs or equivalent.
  • the example signal sequence 700 may be implemented utilizing one or more network infrastructures associated with one or more networks (e.g., a PLMN, an SNPN, etc.) via at least a shared RAN.
  • each of the one or more networks comprises one or more network slices (e.g., 501, 502, or the like).
  • AMF1 108a and AMF 2 108b may be associated with a single network and each serve different network slices of the single network. In other embodiments, AMF1 108a and AMF 2 108b may each be associated with disjoint/isolated networks.
  • AMF1 108a causes transmission of a UE configuration setup message indicating a configured NSSAI including at least a Network Slice 2 for which any subsequent access would require to not include the user equipment identifiers but only the requested NSSAI.
  • the UE configuration setup comprises instructions that if configured UE 102 wants to request and/or establish a new RRC connection using slice 2 among others, via RAN 104, then the request should be without an indication of a user equipment identifier (e.g., S- Temporary Mobile Subscriber Identity (S-TMSI) and/or a Globally Unique Access and Mobility Management Function Identity (GUAM!), or the like).
  • S-TMSI S- Temporary Mobile Subscriber Identity
  • GUIAM Globally Unique Access and Mobility Management Function Identity
  • UE 102 may be camped on one or more networks via RAN 104.
  • UE 102 may request network and/or specific network slice information on-demand and/or in real-time upon receipt of an input signal from a user and/or an application associated with UE 102.
  • one or more AMFs e.g., AMF1 108a, AMF2 108b, or the like
  • one or more AMFs may broadcast a UE configuration setup via one or more RANs to one or more of UEs (e.g., a UE connected to, or camped on, RAN 104 or the like).
  • UE 102 requests new NSSAI.
  • the new NSSAI includes at least an S-NSSAI associated with a second network slice (e.g., Network Slice 2).
  • UE 102 may request, and receive, the new NSSAI by way of RRC messages transmitted to, and received from, at least RAN 104.
  • UE 102 causes transmission of the RRC connection establishment request message to RAN 104.
  • UE 102 via the RRC connection establishment request indicates a first, second, and third network slice (e.g., Network Slice 1, 2, 3) to be served to UE 102 via RAN 104 without identifying a target AMF or core network.
  • UE 102 does not include an S-TMSI, a GUAM!, or other user equipment identifiers via the RRC connection establishment request to the receiving RAN node of RAN 104.
  • the network slices requested by the UE via the RRC connection establishment request may be served by one or more AMFs associated with a network comprising at least the requested network slices.
  • the UE may further specify additional information to at least the RAN node to assist with at least AMF, core network, and/or network slice selection.
  • the UE may include information, in one or more RRC messages to the RAN, that indicates which functionality is required by the UE (e.g., DNS lookup, mapping services, clock/timing services, etc.).
  • the RRC connection establishment request message may further indicate one or more firmware, software, and/or hardware limitations or restrictions of the UE to the RAN, or a node thereof.
  • UE 102 may not be configured to send or receive over a particular frequency band and UE 102 may indicate this limitation to RAN 104.
  • RAN 104 In response to receipt of the RRC connection establishment request message without the user equipment identifier and including the requested NSSAI, at block 708, RAN 104, based on at least its configuration and the received requested NSSAI, selects AMF2 108b to serve at least Network Slice 2 to UE 102.
  • RAN 104, or a node thereof may be configured (e.g., by AMF1 108a, or the like) with frequency band, cell, network slice, network functionality, and/or similar network information (e.g., NSSAI, etc.).
  • RAN 104 may determine based on such configuration information and the RRC connection establishment request including the requested NSSAI, received from UE 102, that AMF2 108b can serve all of the required/requested network functionality to UE 102.
  • the RAN may be caused to initiate such a determination based on the absence of the S-TMSI, the GUAM!, or other user equipment identifiers in the RRC connection establishment request message.
  • the RAN may further determine a network slice, or the like (e.g., an AMF), based on one or more firmware, software, and/or hardware limitations or restrictions of the UE.
  • AMF1 108a may serve all of the same functions as AMF2 108b, however, RAN 104 selects AMF2 108b because AMF1 108a does not support one of the slices requested by UE 102.
  • the network slices e.g., Network Slice 1, 2, 3, etc.
  • the network slices may be duplicate instances of the same network slice.
  • Network Slice 1 may be a standard set of network functions
  • Network Slice 2 may be a high performance set of network functions
  • Network Slice 3 may be a backup to Network Slice 1 and/or Network Slice 2.
  • such standard, high performance, and backup instances may be known to the RAN, or a node thereof, for example, via the RAN’s configuration or determined by the RAN via further communication signaling with one or more AMFs or the like.
  • RAN 104 upon selection of an AMF (e.g., AMF2 108b), by RAN 104, RAN 104 causes transmission of the initial UE message to the selected AMF.
  • the initial UE message can contain a registration request to the selected AMF.
  • the initial UE message may comprise credentials, an onboarding request, and/or the like.
  • UE 102 may indicate a subscription, UE identifier, or the like (e.g., Service Level Agreement (SLA) information, etc.) to RAN 104, via at least the RRC connection establishment request, and this information may be included by RAN 104 in the initial UE message transmitted to AMF2 108b.
  • SLA Service Level Agreement
  • one or more dedicated AMFs can be reserved for serving only one or more particular network slices and, in response, a core network (e.g., a 5GC, etc.) can configure the UE (e.g., UE 102), via the RAN, to not include the user equipment identifier (e.g., S-TMSI, GUAM!, etc.) in an RRC message (e.g., RRC message 5) when it requests a new NSSAI containing one or more of the above particular network slices. This may be configured on a per network slice basis.
  • a core network e.g., a 5GC, etc.
  • RRC message e.g., RRC message 5
  • a 5GC can configure the UE to not include a user equipment identifier in an RRC message 5 transmission during a new NSSAI request operation for one or more respective networks slices (e.g., including Network Slice 2).
  • a 5GC can configure the UE to include an S-TMSI, a GUAM!, or other user equipment identifier in an RRC message 5 transmission during a new NSSAI request operation for one or more other respective networks slices (e.g., including Network Slice 1).
  • the UE may be configured to cause transmission of separate RRC messages for differently configured network slice requests.
  • a first request may be configured, and transmitted, without a user equipment identifier (e.g., for Network Slice 2) and a second request may be configured, and transmitted, with an S-TMSI and/or a GUAM! (e.g., for Network Slice 1).
  • a user equipment identifier e.g., for Network Slice 2
  • a second request may be configured, and transmitted, with an S-TMSI and/or a GUAM! (e.g., for Network Slice 1).
  • signal sequence 700 may comprise, for example, a detection by AMF1 108a which determines that UE 102 has connected to a node of RAN 104 and, in response, causes transmission of, for example, an AP Initial Context setup to UE 102 via RAN 104.
  • the configuration setup received by UE 102 configures UE 102 to only indicate network slices and/or network function requirements to RAN 104 without user equipment identifier during RRC connection establishment communications and, in response, RAN 104 is configured to select an appropriate AMF for UE 102.
  • RAN 104 establishes communications between UE 102 and the selected AMF (e.g., AMF2 108b), UE 102 can be served with the required network functions.
  • FIG. 8 illustrates a flow chart that depicts an example signal sequence 800, for the provision of UE registration with a network slice, at least partially directed by an AMF, between communication devices (e.g., UE 102, a server hosting one or more network functions, apparatus 200, etc.) by way of at least a network infrastructure (e.g., communications network 100, 500, or the like).
  • An example embodiment of signal sequence 800 provides for a registration process associated with a UE to be registered with a band-specific S-NSSAI without using the radio spectrum (e.g., frequency band, cells, etc.) as, at least partially, defined by the AMF for use with the band-specific S-NSSAI.
  • the radio spectrum e.g., frequency band, cells, etc.
  • the example network infrastructure utilized for signal sequence 800 comprises at least UE 102, AMF 108, RAN 104, and NSSF 122.
  • the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LTE, etc.), and that RAN 104 can comprise one or more 5G radio nodes, such as one or more gNBs or equivalent.
  • the example signal sequence 800 may be implemented utilizing one or more network infrastructures associated with one or more networks (e.g., a PLMN, an SNPN, etc.) via at least a shared RAN.
  • each of the one or more networks comprises one or more network slices (e.g., 501, 502, or the like).
  • AMF 108 serves at least one network slice.
  • Example signal sequence 800 begins at block 802 when UE 102 causes transmission, via RAN 104, of an RRC message containing an NAS Registration Request message that at least comprises an indication of a requested NSSAI defined as a Band-specific S-NSSAI for NAS.
  • AMF 108 Upon receipt of the Registration Request message, by AMF 108, at least AMF 108 and NSSF 122 perform the network slice selection operations with respect to an associated network, see block 804.
  • at least some of the network slice selection operations may be performed by one or more other network functions (e.g., AUSF 120, SMF 110, PCF 114, or the like) associated with, for example, communications network 100, 500, or the like.
  • AMF 108 causes transmission of at least an N2 interface message to RAN 104.
  • the N2 interface message can comprise information that defines Allowed NSSAI, one or more Rejected S-NSSAI (e.g., the Band-specific S-NSSAI requested or the like), Configured NSSAI, direct AMF selection information, and/or an NAS message.
  • the NAS message may comprise a Registration Accept message that at least partially defines one or more of an Allowed NSSAI as an enhanced Mobile Broadband (eMBB) S-NSSAI, a Rejected S-NSSAI as the Bandspecific S-NSSAI, Random Access (RA) procedure information, and a reason/cause for the rejection of one or more S-NSSAI (e.g., the Band-specific S-NSSAI is not supported by the RA procedures).
  • eMBB enhanced Mobile Broadband
  • RA Random Access
  • the direct AMF selection information may comprise instructions for the UE 102 and/or the RAN 104 to cause re-transmission of another RRC message containing Registration Request message based on a cell selection/reselection priorities list, or the like, associated with the one or more Rejected S-NSSAI (e.g., the Band-specific S- NSSAI).
  • the one or more Rejected S-NSSAI e.g., the Band-specific S- NSSAI.
  • RAN 104 causes transmission of a Registration Accept message (e.g., via an RRC message, etc.) to UE 102.
  • the Registration Accept message may comprise, at least partially, some of the information associated with the N2 interface message (e.g., block 806).
  • the Registration Accept message may comprise an indication of the Rejected S-NSSAI, the Configured NSSAI, and/or the direct AMF selection information.
  • RAN 104 determines a Radio Resource Management (RRM) policy for managing one or more connections (e.g., a connection with UE 102).
  • RRM Radio Resource Management
  • the RRM policy may involve strategies and/or algorithms for controlling wireless communication parameters associated with one or more RAN nodes.
  • the RRM policy may regulate, via one or more nodes, power transmission, allocation of computing resources (e.g., processor operations, memory, etc.), beamforming, data rates, handover criteria, modulation scheme, error coding schemes, and/or the like.
  • the objective of the RRM policy may be to utilize the limited radiofrequency spectrum resources and radio network infrastructure as efficiently as possible.
  • the RRM policy may be determined, by RAN 104, based on at least information from the N2 interface message (e.g., block 806), for example, the direct AMF selection information. In some embodiments, the RRM policy may be determined, by RAN 104, based on at least information received from UE 102, for example, hardware, firmware, and/or software specifications (e.g., limitations, restrictions, requirements, etc.) associated with UE 102. In some embodiments, the RRM policy can comprise one or more of a radio spectrum, a cell/node identifier, a frequency band, an S-NSSAI, a white list, a black list, or the like.
  • RAN 104 causes transmission, to UE 102, of at least an RRC connection release message that comprises information defining cell, and/or frequency band, reselection priorities (e.g., a cell selection/reselection priorities list, or the like) or alternatively may cause a decision from RAN 104 to trigger handover (RAN Triggered Handover Procedures not shown in this figure).
  • UE 102 determines, at least partially, based on the RRC connection release message information a cell, and/or frequency band, for reselection procedures. In some embodiments, UE 102 may be automatically caused to select a cell, and/or frequency band, for reselection procedures by at least the instructions associated with the RRC connection release message.
  • UE 102 causes transmission, via RAN 104, of a new RRC message containing Registration Request message that at least comprises an indication of a requested NSSAI defined as a Band-specific S-NSSAI for the NAS.
  • the new RRC message containing Registration Request message is at least partially generated by UE 102 based on the cell, and/or frequency band, reselection priorities.
  • the new RRC message containing Registration Request message may comprise a GUAM! to identify the AMF.
  • At least AMF 108 and NSSF 122 Upon receipt of the new Registration Request message, by AMF 108, at least AMF 108 and NSSF 122 perform the network slice selection operations with respect to an associated network and/or the Band-specific S-NSSAI (e.g., the identified network slice), see block 818.
  • the network slice selection operations may be performed by one or more other network functions (e.g., AUSF 120, SMF 110, PCF 114, or the like) associated with, for example, communications network 100, 500, or the like.
  • AMF 108 causes transmission of a Registration Accept message (e.g., via an RRC message, or the like), via RAN 104, to UE 102.
  • the Registration Accept message at least comprises an indication of the Allowed NSSAI, for example, the Band-specific S-NSSAI requested at block 816.
  • UE 102 may be served by the Band-specific S-NSSAI and access network functionality provided thereby.
  • example computing systems can be configured to select a network slice for a UE or at least direct the UE to select a requested network slice in accordance with cell and/or frequency band specific information.
  • an NG-RAN (e.g., of RAN 104) dynamically selects an AMF (e.g., AMF 108) as per the NG-RAN’s configured procedures.
  • the NG-RAN can cause the UE’s state to change from, for example, CM-IDLE to CM-CONNECTED.
  • the NG-RAN may determine to associated the UE context with the Allowed NSSAI, the Configured NSSAI and/or the direct AMF selection information.
  • the AMF 108 and, if necessary, NSSF 122 can perform Network Slice selection in response to AMF 108’s receipt of UE 102’s Registration Request, see at least block 804.
  • the Band-specific S-NSSAI is not defined for the NG-RAN’s configured Tracking Area Identifier (TAI)
  • the AMF 108, and in some embodiments the NSSF 122 can select an eMBB S-NSSAI as the Allowed NSSAI because the eMBB S-NSSAI may be defined as the default Subscribed S-NSSAI.
  • the AMF 108 may be configured to cause transmission, RAN 104, of an N2 interface message to the NG-RAN associated with RAN 104, see at least block 806.
  • the N2 interface message may be configured, if the UE was CM-IDLE, with at least information that defines the Allowed NSSAI, Configured NSSAI, rejected S-NSSAI, and/or any direct AMF selection information.
  • the N2 interface message generated by, at least, AMF 108 can further comprise an NAS message that defines the eMBB S-NSSAI as the Allowed NSSAI and the Band-specific S- NSSAI as the Rejected S-NSSAI based on the configured RA procedures for the AMF 108’s associated network.
  • the AMF 108 can be configured to update the NG-RAN’ s configuration to reflect UE 102’s context with respect to one or more Rejected S-NSSAI.
  • the NG-RAN Upon receipt of the N2 interface message and one or more applicable configuration updates, the NG-RAN causes transmission of at least the NAS message, via a Registration Accept message or the like, to UE 102, see at least block 808. Moreover, the NG-RAN can be configured to determine, based on a configured RRM policy, one or more of a radio spectrum, another RAN cell/node, a frequency band, or the like for one or more S-NSSAI (e.g., the Rejected S-NSSAI, or the like), at least, based on the information received from AMF 108, see at least block 810.
  • S-NSSAI e.g., the Rejected S-NSSAI, or the like
  • the NG-RAN may generate, based on at least the RRM policy, and cause transmission of an RRC Release message to UE 102, see at least block 812.
  • the RRC Release message may include, without limitation, a cell reselection priorities list comprising associated information for frequency bands that only support some network slices as indicated by the configured NSSAI.
  • the cell reselection priorities list may be a backlist or a whitelist.
  • the cell reselection priorities list, or the like may comprise an indication that one or more respective S-NSSAI are not supported by AMF 108 and, therefore, UE 102 can generate a new Registration Request without including a GUAMI, an S-TMSI, or other user equipment identifier.
  • the new RRC message containing Registration Request may include the NSSAI if required.
  • UE 102 is configured with one or more ongoing Protocol Data Unit (PDU) sessions that are configured with a target frequency band (e.g., because the target frequency band also supports the default eMBB network slice, etc.)
  • PDU Protocol Data Unit
  • the NG-RAN, or another portion of RAN 104 can handover UE 102 to a suitable frequency band, or associated cell, directly outside of the configured RA procedures (e.g., based on an RRM policy, or the like).
  • the NG-RAN may remove the one or more Rejected S-NSSAI from UE 102’s context configuration after completion of the handover.
  • TA Timing Advance
  • the procedures associated with block 808 and block 812 may be performed simultaneously.
  • the NG-RAN can be configured to combine the Registration Accept message and the RRC Release messages after making the associated RRM policy determinations, see at least block 808, 810, and 812.
  • UE 102 may be configured to perform a cell reselection procedure, see at least block 814. Moreover, UE 102 may determine that the Tracking Area Identifier (TAI) of the selected cell is outside of the RA and, in response, generates a new Registration Request and includes the Band-specific S-NSSAI as the Requested NS SAI to register with the network slice associated with the Band-specific S- NSSAI, see at least block 816. It should be appreciated that the Band-specific S-NSSAI was previously only rejected for the RA because of existing logic configurations associated with one or more of RAN 104, AMF 108, or the like.
  • TAI Tracking Area Identifier
  • Network slice selection procedures may be performed in response to receipt of the new Registration Request message by AMF 108, see at least block 818.
  • the network slice selection procedure may be performed by AFM 108 and NSSF 122 in accordance with the current network procedures if required (i.e., no configuration updated based on the new Registration Request is required).
  • AMF 108 Upon completion of the network slice selection procedures, AMF 108, at least partially, generates and causes transmission of a Registration Accept message that at least defines the Band-specific S-NSSAI as the Allowed NSSAI, see at least block 820.
  • the PDU Sessions for the eMBB S-NSSAI may be released (e.g. using PDU Session status messages).
  • UE 102 may be configured to generate and cause transmission of another Registration Request that defines the eMBB S-NSSAI as the Requested NSSAI.
  • UE 102 may generate and cause transmission of multiple Registration Requests.
  • FIG. 9 illustrates a flowchart of the operations of an example method 900 performed by an example apparatus 200 which, in some embodiments, may be embodied by a radio access network node, or the like, which, in turn, may include a computer program product comprising a non-transitory computer readable medium storing computer program code executed by, for example, processor 202.
  • apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, by a radio access network node from a core network, a message comprising a configured network slice selection assistance information, wherein the configured network slice selection assistance information comprises one or more network slice identifiers. Additionally each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • apparatus 200 includes means, such as the processor 202 or the like, for additionally determining, by the radio access network node, a cell reselection priorities list comprising a list of frequency bands, further, each respective frequency band of the list of frequency bands may be associated with a plurality of network slice identifiers. Furthermore, the plurality of network slice identifiers comprises a subset of the configured network slice selection assistance information, see block 904. As shown in block 906, apparatus 200 of an example embodiment of method 900 also includes means, such as the processor 202, the communication interface 206 or the like, for causing transmission, by the radio access network node to a user equipment, of the cell reselection priorities list.
  • FIG. 10 illustrates a flowchart of the operations of an example method 1000 performed by an example apparatus 200 which, in some embodiments, may be embodied by a radio access network node, or the like, which, in turn, may include a computer program product comprising a non-transitory computer readable medium storing computer program code executed by, for example, processor 202.
  • apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, by a radio access network node from a network function of a core network, a user equipment configuration setup comprising instructions for direct core network node selection associated with particular registration requests for one or more particular network slices and comprising also configured network slice selection assistance information.
  • apparatus 200 comprises means, such as the processor 202 or the like, for causing transmission, by the radio access network node to a user equipment, of the user equipment configuration setup.
  • the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from the radio resource control message carrying one or more registration requests associated with the core network and to include particular network slice selection assistance information in the radio resource control message carrying one or more registration requests associated with the core network.
  • block 1006 provides for receiving, by the radio access network node from the user equipment, a radio resource control message establishment request comprising a registration request and network slice selection assistance information and the radio resource control message establishment request does not contain user equipment identifiers.
  • the user equipment identifiers may comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • apparatus 200 may additionally include means, such as the processor 202, the communication interface 206 or the like, for determining, by the radio access network node based on the network slice selection assistance information, an access and mobility management function at which to direct the registration request, and the access and mobility management function at least supports the network slice selection assistance information, see the operations of block 1008.
  • apparatus 200 may also include means, such as the processor 202, the communication interface 206 or the like, that are configured for causing transmission, by the radio access network node, of the registration request to the determined access and mobility management function, see block 1010.
  • FIG. 11 illustrates a flowchart of the operations of an example method 1100 performed by an example apparatus 200 which, in some embodiments, may be embodied by one or more servers hosting a core network (e.g., 5GC, etc.), or the like, which, in turn, may include a computer program product comprising a non-transitory computer readable medium storing computer program code executed by, for example, processor 202.
  • apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for generating, by a network function of a core network, a message comprising a configured network slice selection assistance information.
  • the configured network slice selection assistance information comprises one or more network slice identifiers, and each of the one or more network slice identifiers comprise a single network slice selection assistance information.
  • apparatus 200 includes means, such as the processor 202 or the like, for at least causing transmission, by the network function to a radio access network node, of the setup message.
  • FIG. 12 illustrates a flowchart of the operations of an example method 1200 performed by an example apparatus 200 which, in some embodiments, may be embodied by a user equipment, or the like, which, in turn, may include a computer program product comprising a non-transitory computer readable medium storing computer program code executed by, for example, processor 202.
  • An example embodiment of method 1200 begins with block 1202, when an apparatus 200 of this embodiment including means, such as the processor 202, the memory 204, the communication interface 206 or the like, are configured for at least receiving, by a user equipment from a radio access network node, a user equipment configuration setup.
  • the user equipment configuration setup configures the user equipment to at least withhold a user equipment identifier from a radio resource control message carrying one or more registration requests associated with a core network and to include particular network slice selection assistance information in the radio resource control message carrying the one or more registration requests associated with the core network.
  • apparatus 200 includes means, such as the processor 202 or the like, for additionally generating, by the user equipment based on at least the user equipment configuration setup, a radio resource control message establishment request comprising a registration request and network slice selection assistance information.
  • the radio resource control message establishment request does not contain user equipment identifiers, and, in some embodiments, the user equipment identifiers may comprise one or more of an S-Temporary Mobile Subscriber Identifier or a Globally Unique Access and Mobility Management Function Identifier.
  • Block 1206 illustrates, that apparatus 200 of an example embodiment may also include means, such as the processor 202, the communication interface 206 or the like, for causing transmission, by the user equipment to the radio access network node, of the radio resource control message establishment request.
  • any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the function specified in the flowchart blocks.
  • the computer program instructions can also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
  • a computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above.
  • the computer program instructions, such as the computer-readable program code portions need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but can, instead, be embodied by a transitory medium with the computer program instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.
  • blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
  • certain ones of the operations, methods, steps, processes, apparatuses, or the like, above can be modified or further amplified.
  • additional optional operations, methods, steps, processes, hardware, or the like can be included. Modifications, additions, subtractions, inversions, correlations, proportional relationships, disproportional relationships, attenuation and/or amplifications to the operations above can be performed in any order and in any combination. It will also be appreciated that in instances where particular operations, methods, processes, or the like, required particular hardware such hardware may be considered as part of apparatus 200 for any such embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des appareils et des produits-programmes informatiques pour la détermination d'une bande de fréquence et d'un nœud d'accès radio qui prennent en charge un ensemble de tranches de réseau. Un équipement utilisateur peut être configuré pour amener des sélections de tranches de réseau informées à un réseau d'accès radio sur la base d'informations de priorité de cellule et de bande de fréquence. En outre, un réseau d'accès radio peut être configuré pour transmettre des informations de priorité de bande de fréquence et de cellule à l'équipement utilisateur associé à des informations de tranche de réseau. En outre, une fonction de réseau peut configurer des politiques d'un équipement utilisateur pour demander une fonctionnalité de réseau sans inclure des identifiants de tranche de réseau spécifiques. Un réseau d'accès radio peut être configuré pour permettre à un nœud d'accès radio de diriger une demande de fonctionnalité de réseau central, sans identifiants d'équipement utilisateur spécifiques, à une tranche de réseau priorisée par l'intermédiaire d'un nœud priorisé et d'une bande de fréquences.
PCT/EP2021/076675 2020-10-01 2021-09-28 Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence WO2022069481A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063086197P 2020-10-01 2020-10-01
US63/086,197 2020-10-01

Publications (2)

Publication Number Publication Date
WO2022069481A2 true WO2022069481A2 (fr) 2022-04-07
WO2022069481A3 WO2022069481A3 (fr) 2022-05-12

Family

ID=78073918

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/076675 WO2022069481A2 (fr) 2020-10-01 2021-09-28 Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence

Country Status (1)

Country Link
WO (1) WO2022069481A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024033567A1 (fr) * 2022-08-10 2024-02-15 Nokia Technologies Oy Interfonctionnement de mécanismes de resélection de cellule

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766588B (zh) * 2017-06-16 2023-04-07 华为技术有限公司 小区重选方法及相关设备
CN113647148A (zh) * 2019-03-15 2021-11-12 中兴通讯股份有限公司 支持集成有公共网络的非公共网络

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024033567A1 (fr) * 2022-08-10 2024-02-15 Nokia Technologies Oy Interfonctionnement de mécanismes de resélection de cellule

Also Published As

Publication number Publication date
WO2022069481A3 (fr) 2022-05-12

Similar Documents

Publication Publication Date Title
US11564271B2 (en) User equipment category signaling in an LTE-5G configuration
KR20210107739A (ko) 네트워크 액세스 제어 방법, 컴퓨터 판독 가능 매체 및 전자 디바이스
EP3429260B1 (fr) Procédé et système de transmission de données
CN109756951B (zh) 用于网络选择的方法和用户设备
US8874710B2 (en) Access network discovery
US20240188024A1 (en) Methods, apparatuses, and computer program products for providing selection of cells serving network slices for an area
US11924798B2 (en) Method, apparatus, and computer program product for expediting an emergency services initiation
US20220053348A1 (en) Method, apparatus, and computer program product for enhanced data analytics in multiple nwdaf deployments
US20230388769A1 (en) Method, apparatus, and computer program product for service-continuity indication in sidelink user equipment to network relay during path switch
US20230363024A1 (en) Transmission method, transmission apparatus, communication device, and readable storage medium
US20220264283A1 (en) Method, apparatus, and computer program product to facilitate control of terminal timing information within a network
EP3499922B1 (fr) Procédé, dispositif et support de stockage lisible par ordinateur pour appliquer la qos sur la base de mappage de données de plan d'utilisateur
WO2022069481A2 (fr) Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence
TW202007199A (zh) 一種核心網選擇方法及裝置、終端設備、網路設備
US20230143638A1 (en) Method, apparatus, and computer program product for network slice aware public land mobile network selection
WO2022126641A1 (fr) Procédé de communication sans fil, dispositif terminal, premier dispositif de réseau d'accès et élément de réseau
US20230319697A1 (en) Methods, apparatuses, and computer program products for supporting onboarding and authentication of user equipment for networks and network slices
US20240023007A1 (en) Method, apparatus, and computer program product to support multiple slices in case of overlayunderlay networking
US20230319906A1 (en) Methods, apparatuses, and computer program products for supporting simultaneous access to mutally isolated network slices
US20230388386A1 (en) Method, apparatus, and computer program product for enlarging usage of user category within a core network
WO2023123218A1 (fr) Procédé de demande de tranche de réseau, dispositif, support de stockage et produit-programme
WO2023185295A1 (fr) Procédé de communication, dispositif terminal, et dispositif de réseau central
WO2023159351A1 (fr) Procédé et dispositif de communication sans fil
WO2024037512A1 (fr) Procédés et appareils d'accès au réseau, terminal, et dispositif de communication
CN116801227A (zh) 通信方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21786148

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21786148

Country of ref document: EP

Kind code of ref document: A2