Patent Description:
A communication system can be seen as a facility that enables communication sessions between two or more entities such as user equipment, 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 (<NUM> 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, <NUM> 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, <NUM> 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 (<NUM>), third generation (<NUM>), fourth generation (<NUM>), Long Term Evolution (LTE), and fifth generation (<NUM>) standards. The <NUM> 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. The <NUM> network system allows for the support of network slices, which are end to end logical networks which support a certain set of NFs. In other words, a network slice is a logical network that provides specific network capabilities and network characteristics. Across a <NUM> network, comprising a plurality of network slices, 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. An S-NSSAI is used by the user equipment for selecting and accessing the PLMN that the S-NSSAI is associated with.

The term "roaming" refers to a wireless telecommunication practice of using a mobile device, or other user equipment, associated with a particular telecommunication provider on another provider's network. Roaming typically occurs while a user is traveling abroad or out of range of their respective provider's network. While user equipment is roaming, subscription to an end to end network slice requires the serving PLMN to support the features that are associated to that network slice. The current 3GPP practice for roaming users is to define a set of preferred PLMNs for a certain country for when the user equipment is roaming. Telecommunication providers may have agreements in place between each other allowing for greater financial, or other, benefits making the use of preferred PLMNs, whenever possible, more appealing for use by roaming user equipment. The preferred PLMNs list can be configure and stored on the user equipment for <NUM> network communications using the Steering of Roaming (SoR) procedure defined in 3GPP Technical Specification (TS) <NUM> and <NUM>. The option of SoR allows the user equipment's home telecommunication provider to provide the listing of preferred PLMNs for selecting foreign hosting PLMNs.

The problem arises that network slices, which are identified by respective S-NSSAIs, and associated preferred PLMNs in a particular country may not support the features required by roaming user equipment. As such the functionality of the user equipment maybe hindered and the resulting experience of the user negatively impacted. SA2: "<NPL>) discloses that preferred PLMNs may not be necessarily capable to provide all the network slices and that the UE would have to attempt to select PLMNs with no awareness as to whether a PLMN supports an S-NSSAI until the NSSAI is allowed in the PLMN.

"<NPL> discloses procedures for the selection and registration on PPLMNS Techniques for PLMN selection, based on selector lists provision by the operator and the user. <CIT> discloses techniques for enabling network slices for a PDU session over non-3GPP access by obtaining security gateway records via DNS by receiving a DNS record indicating gateways of PLMNS in the DNS response. If the UE is registered to access a PLMN which is not included in the records obtained from the DNS then the UE first selects a PLMN based on the prioritized list and then verifies with the security gateway to determine if it supports the requested network slice. If the gateway does not support the connectivity method of the UE or the gateway does not support the requested network slice, then the UE rechecks for another PLMN in the prioritized list. <CIT> discloses providing a preferred network list including a number of prioritized PLMNs that may be considered when selecting a PLMN and a list of SNSSAIs supported by each PLMN. The UE may initiate deregistration when the network does not support a desired S-NSSAI and will perform PLMN selection based on the preferred network list. The UE searches for a new network to register with that supports the new service.

Aspects of the present invention are set out in the claims.

Having thus described embodiments of the disclosure in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:.

Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, various embodiments of the invention can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term "or" is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms "illustrative" and "exemplary" are used to be examples with no indication of quality level. As used herein, the terms "data," "content," "information," and similar terms can be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention.

Additionally, as used herein, the term '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. As a further example, as used herein, the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term '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.

Additionally, 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 embodiments 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.

Additionally, as used herein, 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," "communication device," "user communication device," "terminal," and similar terms can be used interchangeably to refer to computers configured to access a network or plurality of networks for at least the purpose of wired or wireless transmission of communication signals in accordance with embodiments 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.

Additionally, as used herein, the terms "network slice," "slice," "network portion," and similar terms can be used interchangeably to refer to an end to end logical communication network within a PLMN.

Additionally, as used herein, the terms "required feature," "user equipment feature," "UE equipment," "network slice," "desired feature," "slice feature," "network function feature," "network feature," and similar terms can be used interchangeably to refer to a process, or portion of a process, carried out by the user equipment over a network which necessitates communication between the user equipment and a particular network slice.

As defined herein, a "computer-readable storage medium," which refers to a non-transitory physical storage medium (e.g., volatile or non-volatile memory device), can be differentiated from a "computer-readable transmission medium," which refers to an electromagnetic signal. Such 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. Examples of 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, or the like), 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. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it will be appreciated that where 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.

In the following, certain embodiments are explained with reference to communication devices capable of communication via a wired and/or wireless network and communication systems serving such communication devices. Before explaining in detail the exemplifying embodiments, certain general principles of a wired and/or wireless communication system, access systems thereof, and communication devices are briefly explained with reference to <FIG> to assist in understanding the technology underlying the described examples.

According to some embodiments, a communication device or terminal can be provided for wireless access via cells, base stations, access points or 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). Such wired and/or wireless networks include, but are not limited to, networks configured to conform to <NUM>, <NUM>, <NUM>, LTE, <NUM>, and 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. In some embodiments, a control apparatus for a node can be integrated with, coupled to, and/or otherwise provided for controlling the access points. In some embodiments, 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. For this purpose, the 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. Via the interface, the control apparatus 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. In some embodiments, each base station can comprise a control apparatus. In alternative embodiments, two or more base stations can share 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, an S1, and/or the like interface. 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 on 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 some combination thereof. For example, 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. Further examples include wearable wireless devices such as those integrated with watches or smart watches, eyewear, helmets, hats, clothing, earpieces with wireless connectivity, jewelry and so on, universal serial bus (USB) sticks with wireless capabilities, modem data cards, machine type devices or any combinations of these or the like.

In some embodiments, 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 UE). A mobile communication device can be provided with wireless communication capabilities and appropriate electronic control apparatus for enabling operation thereof. Thus, 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. Furthermore, 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.

In some embodiments, a communication device can communicate wirelessly via appropriate apparatus for receiving and transmitting signals. In some embodiments, 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.

<FIG> illustrate various example architectures for a communications network <NUM> in which the various methods, apparatuses, and computer program products can be carried out and/or used. In some embodiments, the communications network <NUM> 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 <NUM> (UE <NUM>) and a data network <NUM> (DN <NUM>) via a core network <NUM> (CN <NUM>) of the communications network <NUM>. The UE <NUM> can be associated with one or more devices associated with one or more NF service consumers. As illustrated in <FIG>, a communications network <NUM> can be provided in which the UE <NUM> is in operable communication with the RAN <NUM>, such as by way of a transmission tower, a base station, an access point, a network node, and/or the like. In some embodiments, the RAN <NUM> can communicate with the CN <NUM> or a component or entity thereof. In some embodiments, the CN <NUM> can facilitate communication between the UE <NUM> and the DN <NUM>, such as for sending data, messages, requests, and/or the like. In some embodiments, the DN <NUM> or the CN <NUM> can be in communication with an application server or application function <NUM> (AS/AF <NUM>). The RAN <NUM>, CN <NUM>, DN <NUM>, and/or AS/AF <NUM> can be associated with an NRF, NF service producer, SCP, SEPP, PCF, the like, or any combination thereof.

In the context of a <NUM> network, such as illustrated in <FIG> and <FIG>, the communications network <NUM> 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. In some embodiments, the UE <NUM> can connect to the RAN <NUM>, which can then relay the communications between the UE <NUM> and the CN <NUM>, the CN <NUM> being connected to the DN <NUM>, which can be in communication with one or more AS/AF <NUM>. In some embodiments, the UE <NUM> can be in communication with a radio access network <NUM> (RAN <NUM>), which can act as a relay between the UE <NUM> and other components or services of the CN <NUM>. For instance, in some embodiments, the UE <NUM> can communicate with the RAN <NUM>, which can in turn communicate with an Access and Mobility Management Function <NUM> (AMF <NUM>). In other instance or embodiments, the UE <NUM> can communicate directly with the AMF <NUM>. In some embodiments, the AMF <NUM> can be in communication with one or more network functions (NFs), such as an Authentication Server Function <NUM> (AUSF <NUM>), a Network Slice Selection Function <NUM> (NSSF <NUM>), a Network Repository Function <NUM> (NRF <NUM>), a Policy Charging Function <NUM> (PCF <NUM>), a Network Data Analytics Function <NUM> (NWDAF <NUM>), a Unified Data Management function <NUM> (UDM <NUM>), the AS/AF <NUM>, a Session Management Function <NUM> (SMF <NUM>), and/or the like.

In some embodiments, the SMF <NUM> can be in communication with one or more User Plane Functions <NUM> (UPF <NUM>, UPF 106a, UPF 106b, collectively "UPF <NUM>"). By way of example only, in some embodiments, the UPF <NUM> can be in communication with the RAN <NUM> and the DN <NUM>. In other embodiments, the DN <NUM> can be in communication with a first UPF 106a and the RAN <NUM> can be in communication with a second UPF 106b, while the SMF <NUM> 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.

In some embodiments, the UE <NUM> can comprise a single-mode or a dual-mode device such that the UE <NUM> can be connected to one or more RANs <NUM>. In some embodiments, the RAN <NUM> can be configured to implement one or more Radio Access Technologies (RATs), such as Bluetooth, Wi-Fi, and GSM, UMTS, LTE or <NUM> NR, among others, that can be used to connect the UE <NUM> to the CN <NUM>. In some embodiments, the RAN <NUM> can comprise or be implemented using a chip, such as a silicon chip, in the UE <NUM> that can be paired with or otherwise recognized by a similar chip in the CN <NUM>, such that the RAN <NUM> can establish a connection or line of communication between the UE <NUM> and the CN <NUM> by identifying and pairing the chip within the UE <NUM> with the chip within the CN <NUM>. In some embodiments, the RAN <NUM> can implement one or more base stations, towers or the like to communicate between the UE <NUM> and the AMF <NUM> of the CN <NUM>.

In some embodiments, the communications network <NUM> or components thereof (e.g., base stations, towers, etc.) can be configured to communicate with a communication device (e.g., the UE <NUM>) such as a cell phone or the like over multiple different frequency bands, e.g., FR1 (below <NUM>), FR2 (mm Wave), other suitable frequency bands, sub-bands thereof, and/or the like. In some embodiments, the communications network <NUM> can comprise or employ massive multiple input and multiple output (massive MIMO) antennas. In some embodiments, the communications network <NUM> can comprise multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communications network <NUM> can employ edge computing whereby the computing servers are communicatively, physically, computationally, and/or temporally closer to the communications device (e.g., UE <NUM>) in order to reduce latency and data traffic congestion. In some embodiments, the communications network <NUM> can employ other technologies, devices, or techniques, such as small cell, low-powered RAN, beamforming of radio waves, WIFI-cellular convergence, non-orthogonal multiple access (NOMA), channel coding, and the like.

As illustrated in <FIG>, the UE <NUM> can be configured to communicate with the RAN <NUM> in a N1 interface, e.g., according to a non-access stratum (NAS) protocol. In some embodiments, RAN <NUM> can be configured to communicate with the CN <NUM> or a component thereof (e.g., the AMF <NUM>) in a N2 interface, e.g., in a control plane between a base station of the RAN <NUM> and the AMF <NUM>. In some embodiments, the RAN <NUM> can be configured to communicate with the UPF <NUM> in a N3 interface, e.g., in a user plane. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with other services or network entities within the CN <NUM> in various different interfaces and/or according to various different protocols. For instance, in some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the AUSF <NUM> in a Nausf interface or an N12 interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the NSSF <NUM> in a Nnssf interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the NRF <NUM> in a Nnrf interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the PCF <NUM> in a Npcf interface or an N7 interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the NWDAF <NUM> in a Nnwdaf interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the UDM <NUM> in a Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF <NUM> and/or the SMF <NUM> can be configured to communicate with the AS/AF <NUM> in a Naf interface. In some embodiments, the SMF <NUM> can be configured to communicate with the UPF <NUM> in a 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 <NUM> and the CN <NUM> or components/services thereof.

It will be appreciated that certain example embodiments described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and/or otherwise incorporates aspects of a fifth-generation (<NUM>) architecture. While <FIG> illustrate various configurations and/or components of an example architecture of the communications network <NUM>, 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.

While the methods, devices/apparatuses, and computer program products/codes described herein are described within the context of a fifth-generation core network (5GC) and system, such as illustrated in <FIG> and described hereinabove, the described methods, devices, and computer program products can nevertheless be applied in a broader context within any suitable telecommunications system, network, standard, and/or protocol. It will be appreciated that the described methods, devices, and computer program products can further be applied to yet undeveloped future networks and systems as would be apparent to one skilled in the art in light of the present disclosure.

Turning now to <FIG>, examples of an apparatus that may be embodied by the user equipment or by a network entity, such as server or other computing device are depicted in accordance with an example embodiment of the present disclosure. As described below in conjunction with the flowcharts and block diagrams of <FIG>, <FIG>, <FIG>, <FIG>, and <FIG>, the apparatus <NUM> of an example embodiment can be configured to perform the functions described herein. In any instance, the apparatus <NUM> 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. Regardless of the manner in which the apparatus <NUM> is embodied, the apparatus of an example embodiment can be configured as shown in <FIG> so as to include, be associated with or otherwise be in communication with a processor <NUM> and a memory device <NUM> and, in some embodiments, and/or a communication interface <NUM>. Although not illustrated, the apparatus of an example embodiment may also optionally include a user interface, such as a touch screen, a display, a keypad or the like.

The processor <NUM> (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) can be in communication with the memory device <NUM> via a bus for passing information among components of the apparatus <NUM>. The memory device can include, for example, one or more volatile and/or non-volatile memories, such as a non-transitory memory device. In other words, for example, 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, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.

The apparatus <NUM> 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.

The processor <NUM> can be embodied in a number of different ways. For example, 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 ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, 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. Additionally or alternatively, the processor can include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

In an example embodiment, the processor <NUM> can be configured to execute instructions stored in the memory device <NUM> 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 or the like, 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. However, in some cases, 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.

In embodiments that include a communication interface <NUM>, 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 <NUM>, such as NF, NRF, a base station, an access point, SCP, UE <NUM>, radio access network, core network services, an application server/function, a database or other storage device, etc. In this regard, the communication interface can include, for example, an antenna (or multiple 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 antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface can alternatively or also support wired communication. As such, for example, the communication interface can include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. In some embodiments, a session management function can comprise a 5GC session management function for any suitable control and user plane separation (CUPS) architecture, such as for the gateway GPRS support node (GGSN-C), TWAG-C, BNG-CUPS, N4, Sxa, Sxb, Sxc, evolved packet core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, and/or the like.

As illustrated, the apparatus <NUM> can include a processor <NUM> in communication with a memory <NUM> and configured to provide signals to and receive signals from a communication interface <NUM>. In some embodiments, the communication interface <NUM> can include a transmitter and a receiver. In some embodiments, the processor <NUM> can be configured to control the functioning of the apparatus <NUM>, at least in part. In some embodiments, the processor <NUM> can be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, the processor <NUM> can be configured to control other elements of apparatus <NUM> by effecting control signaling via electrical leads connecting the processor <NUM> to the other elements, such as a display or the memory <NUM>.

The apparatus <NUM> 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 <NUM> 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) <NUM>, <NUM>, <NUM>, ADSL, DOCSIS, and/or the like. In addition, these signals can include speech data, user generated data, user requested data, and/or the like.

For example, the apparatus <NUM> and/or a cellular modem therein can be capable of operating in accordance with various first generation (<NUM>) communication protocols, second generation (<NUM> or <NUM>) communication protocols, third-generation (<NUM>) communication protocols, fourth-generation (<NUM>) communication protocols, fifth-generation (<NUM>) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP) and/or the like. For example, the apparatus <NUM> can be capable of operating in accordance with <NUM> wireless communication protocols IS-<NUM>, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-<NUM>, Code Division Multiple Access, CDMA, and/or the like. In addition, for example, the apparatus <NUM> can be capable of operating in accordance with <NUM> wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus <NUM> can be capable of operating in accordance with <NUM> wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access <NUM> (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The NA <NUM> can be additionally capable of operating in accordance with <NUM> wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus <NUM> can be capable of operating in accordance with <NUM> wireless communication protocols, such as LTE Advanced, <NUM>, and/or the like as well as similar wireless communication protocols that can be subsequently developed. In some embodiments, the apparatus <NUM> can be capable of operating according to or within the framework of any suitable CUPS architecture, such as for the gateway GPRS support node (GGSN-C), trusted wireless access gateway (TWAG-C), broadband network gateways (BNGs), N4, Sxa, Sxb, Sxc, evolved packet core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, and/or the like. Indeed, although described herein in conjunction with operation with a <NUM> system, the apparatus and method may be configured to operate in conjunction with a number of other types of systems including systems hereinafter developed and implemented.

Some of the embodiments disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware can reside on memory <NUM>, the processor <NUM>, or electronic components, for example. In some example embodiments, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, 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>, 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> illustrates a communication interface between UE <NUM> and associated PLMNs. As illustrated UE <NUM> is configured by a HPLMN <NUM> with a network slice aware PLMN exception list <NUM> and a preferred PLMN list <NUM>. In some embodiments, the network slice aware PLMN exception list <NUM> and the preferred PLMN list <NUM> may be provided by SoR or by similar mechanisms to the SoR including OTA, offline USIM provisioning methods, or UE provisioning methods. The network slice aware PLMN exception list <NUM> and the preferred PLMN list <NUM> may each include one or more VPLMNs. Additionally, for each VPLMN in the network slice aware PLMN exception list <NUM>, the network slice aware PLMN exception list may also identify locations, such as countries, in which the preferred PLMN list <NUM> is ineffective for the respective VPLMN. The UE <NUM> utilizes the network slice aware PLMN exception list <NUM> and the preferred PLMN list <NUM> to establish connections with a plurality of VPLMNs <NUM> at different points in time. In this regard, the UE <NUM> selects and establishes connections with at least one VPLMN of the plurality of Preferred VPLMNs <NUM> and Non-Preferred VPLMNs <NUM> based on the preferred PLMN list <NUM> and/or the network slice aware PLMN exception list <NUM> respectively. Additionally, by way of example, the UE <NUM> can select and establish a first connection with one of the Preferred VPLMNs <NUM> as identified by the preferred PLMN list <NUM>. In accordance with an example embodiment, the UE <NUM> then determines a need or desire to utilize a NF not supported by the selected preferred VPLMN. Next, the UE <NUM> of this example embodiment disconnects from the first preferred VPLMN and further selects and establishes a second connection with one of the Non-Preferred VPLMNs <NUM> as identified by the network slice aware PLMN exception list <NUM>, which does support the NF that is needed or desired. Subsequently, the UE <NUM> then determines the NF not supported by the preferred VPLMN is no longer required and disconnects from the non-preferred VPLMN and reestablishes the connection to the preferred VPLMN or to another VPLMN on the Preferred PLMN list.

It will be appreciated that the UE <NUM> of an example embodiment prioritizes the Preferred VPLMNs <NUM> over the Non-Preferred VPLMNs <NUM> when establishing and maintaining network connections unless a particular need or desire arises which can only be facilitated by a particular non-preferred VPLMN. It will also be appreciated that under certain circumstances (e.g., travel through a remote region) the UE <NUM> may only have access to either the Preferred VPLMNs <NUM> or the Non-Preferred VPLMNs <NUM>. Further, among the Preferred VPLMNs <NUM> identified by the preferred PLMN list <NUM> the HPLMN can configure the preferred PLMN list <NUM> to prioritize the preferred VPLMNs. Thus, upon selecting a Preferred VPLMN from the preferred PLMN list, the UE may select a Preferred VPLMN based upon the priority of the Preferred VPLMNs. Additionally, among the Non-Preferred VPLMNs <NUM> identified by the network slice aware PLMN exception list <NUM> the HPLMN can configure the preferred PLMN list <NUM> to prioritize the non-preferred VPLMNs. Thus, upon selecting a Non-Preferred VPLMN from the network slice aware PLMN exception list, the UE may select a Non-Preferred VPLMN based upon the priority of the Non-Preferred VPLMNs. Prioritization of VPLMNs can be done by applying weighted values to characteristics of each VPLMN including a cost, signal strength, NF support/compatibility, quality of service, the like, or any combination thereof. The UE <NUM> can be further configured to prioritize characteristics based on predefined preferences established, for example, by the HPLMN or the user of the UE <NUM>. In an instance where characteristics are not prioritized, a user of the UE <NUM> can be presented with available VPLMN options and at least some of their associated characteristics, such that the user of the UE <NUM> can manually select or prioritize the available VPLMNs on a regional basis.

<FIG> illustrates an example communication network comprising two network slices. The UE <NUM> utilizes Communication Interface <NUM> to establish a plurality of network communications. Communication Interface <NUM> can connect the UE <NUM> to the Common Network Functions <NUM>, the First Network Slice <NUM>, or the Second Network Slice <NUM>. It will be appreciated that Communication Interface <NUM> can connect the UE <NUM> directly to either network slice thus bypassing the Common Network Functions <NUM>. Additionally, it will be appreciated that Communication Interface <NUM> can connect the UE <NUM> indirectly to either network slice by establishing a connection through the Common Network Functions <NUM>. The First Network Slice <NUM> comprises a plurality of NFs including at least NRF1 124a, PCF1 114a, UPF1 106a, and SMF1 110a, wherein each of the NFs of the First Network Slice <NUM> are independent of the Common Network Functions <NUM> and the NFs of the Second Network Slice <NUM>. Further, the First Network Slice <NUM> is configured to connect the UE <NUM> to DN1 116a. The Second Network Slice <NUM> comprises a plurality of NFs including at least NRF2 124b, PCF2 114b, UPF2 106b, and SMF2 110b, wherein each of the NFs of the Second Network Slice <NUM> are independent of the Common Network Functions <NUM> and the NFs of the First Network Slice <NUM>. Further, the Second Network Slice <NUM> is configured to connect the UE <NUM> to DN2 116b.

<FIG> illustrates a flow diagram of the operations of an example method <NUM> performed by the apparatus <NUM> embodied by UE <NUM> in conjunction with the Preferred PLMN List <NUM>, the Network Slice Aware PLMN Exception List <NUM>, and the UE's HPLMN <NUM>. In some embodiments, the apparatus <NUM> embodied by the UE <NUM> carries out the process elements of method <NUM> by execution of a related computer program product comprising computer program code. As shown in block <NUM>, the UE <NUM> is configured by the HPLMN <NUM> with the Preferred PLMN List <NUM> and the Network Slice Aware PLMN Exception List <NUM> each comprising one or more respective PLMN IDs as identified by a respective S-NSSAI. The apparatus <NUM> embodied by the UE <NUM> may be configured to store the Preferred PLMN List <NUM> and the Network Slice Aware PLMN Exception List <NUM> in memory <NUM> or otherwise in a database or other memory device accessible to the processor <NUM>. As shown in block <NUM>, the UE <NUM> is located in a country, such as may be identified by a Mobile Country Code (MCC), and identifies one or more S-NSSAIs in the Network Slice Aware PLMN Exception List <NUM> pointing to PLMN IDs not in the Preferred PLMN List <NUM>. It will be appreciated that the applicable MCC of a country can be identified by the UE <NUM> by way of a global positioning mechanism (e.g., Global Positioning System (GPS), Global Navigation Satellite System (GNSS), or the like), identification information transmitted to UE <NUM> by the VPLMNs, NSSAI, and/or S-NSSAI, user inputs through a user interface of UE <NUM>, the like, or any combination thereof.

As shown in block <NUM>, the apparatus <NUM> of the UE <NUM> is configured to select to use only S-NSSAIs and associated VPLMNs not in the Network Slice Aware PLMN Exception List <NUM>. In other words, the apparatus <NUM> of the UE <NUM> is configured to select to use only S-NSSAIs and associated VPLMNs on the Preferred PLMN List <NUM>. As shown in block <NUM>, the apparatus embodied by the UE <NUM> is configured to select a VPLMN in the Preferred PLMN List <NUM>, as configured by the HPLMN <NUM>. As shown in block <NUM>, the UE <NUM> needs or desires to use a function that is not supported by the VPLMN that has been selected from the Preferred PLMN list or by any of the other VPLMNs of the Preferred PLMN list, but that is supported by at least one VPLMN that is in the Network Slice Aware PLMN Exception List <NUM>, as configured by the HPLMN <NUM>. As shown in block <NUM>, the apparatus <NUM> embodied by the UE <NUM> is configured to select a VPLMN in the Network Slice Aware PLMN Exception List <NUM> of VPLMNs that is capable of performed the function that is required or desired.

Subsequently, as shown in block <NUM>, the UE <NUM> no longer needs or desires to use the function that is not supported by the VPLMNs of the Preferred PLMN List <NUM> and that triggered the switch to a VPLMN from the Network Slice Aware PLMN Exception List <NUM>. As shown in block <NUM>, the apparatus <NUM> embodied by the UE <NUM> is then configured to select a VPLMN in the Preferred PLMN List <NUM> configured by the HPLMN <NUM> and to switch communications from the VPLMN in the Network Slice Aware PLMN Exception List to the selected VPLMN from the Preferred PLMN List <NUM>.

<FIG> illustrates a flowchart of the operations of an example method <NUM> performed by an example apparatus <NUM>, wherein the apparatus <NUM> of an example embodiment is configured to perform the process of method <NUM> by execution of a related computer program product comprising computer program code. As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, the memory <NUM> or the like, for storing a Preferred PLMN List <NUM>, such as may be configured and provided by a HPLMN <NUM>. As shown in block <NUM>, apparatus <NUM> also includes means, such as the processor <NUM>, the memory <NUM> or the like, for storing a Network Slice Aware PLMN Exception List <NUM>, such as may also be configured and provided by a HPLMN <NUM>.

As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, the communication interface <NUM> or the like, for determining a present location and/or Mobile Country Code (MCC), such as based on available network data and/or Global Position Satellite (GPS) data. As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM> or the like, for selecting to use only VPLMNs in the Preferred PLMN List <NUM>. In this regard, the apparatus <NUM>, such as the processor <NUM>, may be configured to select to use VPLMNs in the Preferred PLMN List <NUM> and not VPLMNs in the Network Slice Aware PLMN Exception List <NUM>. As shown in block <NUM>, apparatus <NUM> also includes means, such as the processor <NUM>, the communication interface <NUM> or the like, for determining availability of at least one VPLMN listed in the Preferred PLMN List <NUM>. From among the available VPLMN(s) that are listed in the Preferred PLMN List <NUM> and as shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, for selecting a VPLMN that is in the Preferred PLMN List <NUM> and that is accessible at the present location and to then begin communications with the selected VPLMN. In an instance in which a plurality of VPLMNs of the Preferred PLMN List <NUM> are available, the apparatus <NUM>, such as the processor <NUM>, may be configured to select a particular VPLMN in any of various different manners. For example, an order of precedence may have been established for the VPLMNs of the Preferred PLMN List <NUM> such that the apparatus <NUM>, such as the processor <NUM>, selects the particular PLMN based upon the order of precedence. In this regard, the VPLMNs may also have been weighted according to a predefined criteria with the order of precedence taking into account the weighting of the VPLMNs. Alternatively, the apparatus <NUM>, such as the processor <NUM>, may be configured to select the VPLMN of the Preferred PLMN List <NUM> that includes the largest number of NFs in the present location. Regardless of the manner in which the particular PLMN of the Preferred PLMN List <NUM> is selected, the apparatus <NUM>, such as the processor <NUM>, is configured to then establish communications and interact with the particular PLMN. In still other embodiments, such as in an instance in which the other methods fail to identify a single VPLMN for selection, a user of the UE <NUM> may be informed, such as via a user interface, as of the options with respect to the VPLMNs and may be requested to select the VPLMN to be utilized. As used herein, a user of the UE <NUM> may be a person or may be automated, such as via an application programming interface (API).

As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM> or the like, for subsequently determining that at least one VPLMN that is in the Network Slice Aware PLMN Exception List <NUM> is required for use of a particular network function or UE feature which requires a certain network slice to be used. In this regard, the apparatus <NUM> such as the processor <NUM>, is configured to determine that the particular network function or feature is not provided or supported by the particular VPLMN of the Preferred PLMN List <NUM> with which the UE is currently in communication and, in some embodiments, that the particular network function or feature is also not provided or supported by any other VPLMN of the Preferred PLMN List. In this instance, the apparatus <NUM>, such as the processor <NUM>, is configured to consider the functions or features supported by the VPLMNs of the Network Slice Aware PLMN Exception List <NUM> and to identify one or more VPLMNs of the Network Slice Aware PLMN Exception List <NUM> that do support the function or feature that is needed or desired by the UE <NUM>.

As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, the communications interface <NUM> or the like, for selecting a VPLMN in the Network Slice Aware PLMN Exception List <NUM> that is compatible with, that is that supports or provides, the particular network function or UE feature which requires a certain network slice to be used. In an instance in which a plurality of VPLMNs of the Network Slice Aware PLMN Exception List <NUM> are available, the apparatus <NUM>, such as the processor <NUM>, may be configured to select a particular VPLMN in any of various different manners. For example, an order of precedence may have been established for the VPLMNs of the Network Slice Aware PLMN Exception List <NUM> such that the apparatus <NUM>, such as the processor <NUM>, selects the particular PLMN based upon the order of precedence. Alternatively, the apparatus <NUM>, such as the processor <NUM>, may be configured to select the VPLMN of the Network Slice Aware PLMN Exception List <NUM> that includes the largest number of NFs in the present location. Regardless of the manner in which the particular PLMN of the Network Slice Aware PLMN Exception List <NUM> is selected, the apparatus <NUM>, such as the processor <NUM>, is configured to then establish communications and interact with the particular PLMN.

As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM> or the like, for determining that the particular network function or feature that is not supported by the VPLMNs of the Preferred PLMN List <NUM> and that triggered the switch to a VPLMN from the Network Slice Aware PLMN Exception List <NUM> is no longer required or desired by the UE <NUM>. Since the particular network function or feature is no longer required or desired and as shown in block <NUM>, apparatus <NUM> also includes means, such as the processor <NUM> or the like, for correspondingly determining that none of the at least one VPLMN that is in the Network Slice Aware PLMN Exception List <NUM> and that was previously selected to provide the particular network function or feature is also no longer required. As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, the communication interface <NUM> or the like, for selecting a VPLMN that is in the Preferred PLMN List <NUM> and that is available at the present location. The VPLMN that is selected from the Preferred PLMN List <NUM> may be the same VPLMN that was previously selected and utilized prior to the switch to a VPLMN from the Network Slice Aware PLMN Exception List <NUM>. Alternatively, the VPLMN that is selected from the Preferred PLMN List <NUM> may be a different VPLMN from that which was previously selected. In this instance, the VPLMN that is selected from the Preferred PLMN List <NUM> may be selected based on an order of precedence, based on a number of NFs supported or otherwise as described above.

By way of a further example, <FIG> illustrates a flowchart of the operations of the claimed method <NUM> performed by an example apparatus <NUM> which, in one embodiment, may be embodied by a computer program product comprising computer program code executed by processor <NUM>. As shown in block <NUM>, apparatus <NUM> of this example embodiment incudes means, such as the processor <NUM>, the memory <NUM>, the communication interface <NUM> or the like, for receiving the Network Slice Aware PLMN Exceptions List <NUM> and the Preferred PLMN List <NUM>, such as from a HPLMN <NUM>. As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM>, the communication interface <NUM> or the like, for determining that the UE <NUM> is in a location with one or more VPLMNs that are included in the Network Slice Aware PLMN Exceptions List <NUM>. As shown in block <NUM>, apparatus <NUM> includes means, such as the processor <NUM> or the like, for determining to utilize, at least initially, only VPLMNs that are not associated with the Network Slice Aware PLMN Exceptions List <NUM> but that are, instead, associated with the Preferred PLMN List <NUM>. As shown in block <NUM>, apparatus <NUM> also includes means, such as processor <NUM> or the like, for selecting a VPLMN associated with a Preferred PLMN List <NUM>, such as described above. The UE <NUM> that embodies the apparatus <NUM> then communicates via and interacts with the selected VPLMN.

As shown in block <NUM>, apparatus <NUM> incudes means, such as the processor <NUM>, for identifying a network slice not supported by the selected VPLMN, in order to provide network support for at least one feature that the UE <NUM> or a user of the UE is attempting to utilize which is not supported by the currently selected network slice. As shown in block <NUM>, apparatus <NUM> including means, such as the processor <NUM> or the like, for selecting another VPLMN that supports the network slice. If the UE feature were supported by another VPLMN of the Preferred PLMN list <NUM>, the other VPLMN could be selected from the Preferred PLMN List. In this example embodiment, however, no VPLMN of the Preferred PLMN List <NUM> supports the UE feature such that the other VPLMN that supports the UE feature is not associated with the Preferred PLMN List <NUM>, but is, instead, associated with a Network Slice Aware PLMN Exceptions List <NUM>, or another VPLMN associated with the preferred PLMN list which supports the network slice. The UE <NUM> that embodies the apparatus <NUM> then ceases its connection to the VPLMN that was previously selected from the Preferred PLMN List <NUM> and, instead, communicates via and interacts with the selected VPLMN from the Network Slice Aware PLMN Exceptions List <NUM>.

As shown in block <NUM>, apparatus <NUM> also includes means, such as the processor <NUM> or the like, for determining that the identified network slice supported by a selected VPLMN that is associated with a network slice aware PLMN exceptions list is no longer required or desired. In this instance and as shown in block <NUM>, apparatus <NUM> includes means for transferring a connection from the selected VPLMN from the Network Slice Aware PLMN Exceptions List <NUM> to a VPLMN from the Preferred PLMN List <NUM>. As described above, the VPLMN from the Preferred PLMN List <NUM> to which the connected is transferred may be the same VPLMN that was previously selected from the Preferred PLMN List or a different VPLMN. In an example embodiment, the apparatus <NUM>, such as the processor <NUM>, is configured to transfer the connection during an idle time of the user equipment. In an example embodiment, the idle time of the user equipment is a predefined length of time in which the user equipment is not sending or receiving any communication signals utilizing the selected VPLMN from the Network Slice Aware PLMN Exceptions List <NUM> or the Preferred PLMN List <NUM>.

Upon request by the UE <NUM> for a network function not supported by the current network slice of the current VPLMN, the UE <NUM> determines that the network slice is incompatible with the requested network function. The UE <NUM> further determines that the current VPLMN is also incompatible with the requested network function on any other network slices associated with the current VPLMN.

In an example embodiment in which the VPLMN that is supporting the UE <NUM> is or becomes incompatible with a required or desired network function and in an instance in which the apparatus <NUM>, such as the processor <NUM>, is not configured to immediately select a different VPLMN from the Network Slice Aware PLMN Exceptions List <NUM>, the apparatus <NUM>, such as the processor <NUM>, as embodied as the UE <NUM> may be configured to first select and test the other respective preferred PLMNs of the Preferred PLMNs List <NUM> to determine if they are compatible with the required or desired network slice. If a preferred PLMN is compatible, support for the UE <NUM> may be transferred to the other preferred PLMN. In an instance in which none of the respective preferred PLMNs of the Preferred PLMNs List <NUM> are compatible with the required or desired network slice, then the apparatus <NUM>, such as the processor <NUM>, of this example embodiment may be configured to select and test the respective PLMNs from the Network Slice Aware PLMN Exceptions List <NUM> for compatibility with the required or desired network slice and, if a respective PLMN is compatible, will then select the respective PLMN from the Network Slice Aware PLMN Exceptions List <NUM> to support the UE <NUM>.

In an example embodiment, the UE <NUM> can collect PLMN identities, access technologies, and/or S-NSSAIs broadcasts by way of a plurality of access networks. In order to make this available, access networks are enhanced to broadcast one or more S-NSSAIs supported by the access network. If there exist one or more network slices that the UE <NUM> needs to make use of, the UE <NUM> excludes these network slices from the network selection candidates, for example, any PLMN identity, access technology, the like, or combination thereof which does not support the S-NSSAI(s).

As described above, the referenced flowcharts of methods that can be carried out by an apparatus according to related computer program products comprising computer program code. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above can be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above can be stored by a memory device, e.g., <NUM>, of an apparatus, e.g., <NUM>, employing an embodiment of the present invention and executed by processor, e.g., <NUM>, of the apparatus. As will be appreciated, 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. In other embodiments, 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.

In some embodiments, certain ones of the operations, methods, steps, processes, or the like, above can be modified or further amplified. Furthermore, in some embodiments, additional optional operations, methods, steps, processes, 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, steps, processes, or the like, required particular hardware such hardware should be considered as part of apparatus <NUM> for any such embodiment. For example, as described above where a GPS is used to determine the location of apparatus <NUM> such appropriate GPS modules and hardware should be considered integral to apparatus <NUM>.

Claim 1:
A user equipment, UE, (<NUM>) comprising:
means for selecting a Visited Public Land Mobile Network, VPLMN, (<NUM>) associated with a preferred Public Land Mobile Network, PLMN, list (<NUM>) configured by a Home Public Land Mobile Network, HPLMN, (<NUM>);
means for identifying a network slice not supported by the selected VPLMN; and
means for receiving a network slice aware PLMN exceptions list (<NUM>) from the HPLMN;
means for selecting another VPLMN (<NUM>) that supports the network slice, wherein the another VPLMN is not associated with the preferred PLMN list but is associated with the network slice aware PLMN exceptions list, only when no VPLMN in the preferred PLMN list supports the network slice;
means for determining that the identified network slice supported by the another VPLMN that is associated with the network slice aware PLMN exceptions list is no longer required; and
means for selecting a VPLMN associated with the preferred PLMN list during a next idle time of user equipment if the user equipment is currently connected and transferring data on the another VPLMN.