Frequency or Radio Access Technology (RAT) selection based on slice availability

Abstract

To provide a radio access network (RAN) node and a method for frequency or radio access technology (RAT) selection on the basis of slice availability.SOLUTION: In a telecommunications network 300, a RAN node 312 receives, from access and mobility management (AMF) 304 within a core network 302, a message 316 including an index to a RAT / frequency selection priority configured on the basis of subscription information and a network slice allowed for user equipment (UE) 314, determines UE-specific cell reselection priority for controlling idle mode camping and / or directing the UE 314 to a preferred frequency layer or radio access type (RAT) according to the received index, and provides unique cell reselection priority to the UE 314.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application No. 62 / 565,022, filed Sep. 28, 2017, the disclosure of which is incorporated herein by reference in its entirety. Technical Field 5th Generation (5G), 5G Core Network (5GC), New Radio (NR), Next Generation (NG), Authentication Management Function (AMF), Network Slicing. [Background technology]

[0002] It has been agreed in the 3rd Generation Partnership Project (3GPP) to support network slicing for the Fifth Generation (5G) Core Network (5GC) and Next Generation (NG) Radio Access Networks (RAN), including both Long Term Evolution (LTE) and New Radio (NR) Radio Access Technologies (RATs). In this document, the following terminology is used:

[0003] Service: A service provided to an entity on a telecommunications network. Exemplary services include end user services and business services. Services may be provided by the network operator or by a third party.

[0004] Service Instance: An instantiation of a service on a telecommunications network. A network may have zero or more service instances, which may be of different types, the same type, or several of the above.

[0005] Network Slice: A complete logical network providing telecommunication services and network capabilities, including Access Network (AN) and Core Network (CN) capabilities. An AN may be common to multiple network slices. Network slices may support different functions and / or have different network function optimizations.

[0006] Network Slice Instance (NSI): A collection of network functions and resources for performing these network functions that form a complete instantiated logical network to meet the specific network characteristics required by one or more service instances. An NSI may be fully or partially, logically and / or physically separated from another NSI. Resources include physical and logical resources. An NSI may be composed of sub-network instances that may be shared by multiple NSIs. An NSI may be specified by a network slice blueprint. Instance-specific policies and configurations are required when creating an NSI. Example network characteristics include, but are not limited to, ultra-low latency, ultra-reliability, etc.

[0007] Network Slice Selection Assistance Information (NSSAI): Information consisting of a set of parameters provided by a user equipment (UE) to the network to select a set of RAN and CN portions of the NSI for the UE. This information includes a Slice Service Type (SST) for each slice that the UE is authorized to access, and may also include a Slice Differentiator (SD).

[0008] RAT / Frequency Selection Priority (RFSP) Index: Mapped by the RAN to a locally defined configuration to apply a specific Radio Resource Management (RRM) strategy. The RFSP index may be used by the RAN to derive a UE-specific cell reselection priority to control idle mode camping and to decide to redirect active mode UEs to a different frequency tier or RAT. The RFSP index is UE-specific and applies to all radio bearers.

[0009] Network slicing is described for example in 3GPP Technical Specification (TS) 23.799. Network slicing enables operators to create customized networks to offer optimized solutions for different market scenarios demanding diverse requirements in the areas of functionality, performance and isolation for example.

[0010] The network slicing concept is shown in Figure 1. As shown in Figure 1, the network slicing concept consists of three layers: 1) service instance layer 110, 2) NSI layer 112, and 3) resource layer 114.

[0011] The service instance layer 110 represents the services (end user services or business services) to be supported. Each service is represented by a service instance 116. In the embodiment shown in FIG. 1, there are five service instances, labeled 116-1 through 116-5, which may be collectively or individually referred to as service instances 116. Typically, services may be provided by the network operator or by a third party. Along these lines, the service instances 116 may represent either operator services or third party provided services.

[0012] A network operator uses a network slice blueprint to create an NSI 118. In the embodiment shown in FIG. 1, there are four NSIs, labeled 118-1 through 118-4, which may be collectively or individually referred to as an NSI 118. The NSI 118 provides the network characteristics required by the service instance 116. The NSI 118 may be shared across multiple service instances 116 offered by the network operator. It has not yet been standardized whether sharing of the NSI 118 across service instances 116 offered by different third parties needs to be supported.

[0013] An NSI 118 may be configured with zero, one, or multiple subnetwork instances 120. In the embodiment shown in FIG. 1, there are six subnetwork instances, labeled 120-1 through 120-6, which may be collectively or individually referred to as subnetwork instances 120 and may be shared by other NSIs 118. For example, in the embodiment shown in FIG. 1, subnetwork instance 120-4 is shared by NSIs 118-3 and 118-4. Similarly, subnetwork blueprints are used to create subnetwork instances 120 to form a collection of network functions that run on physical / logical resources 122.

[0014] NSI 118: A collection of network functions and resources 122 for executing these network functions, forming a complete instantiated logical network to meet the specific network characteristics required by the service instance 116. An NSI 118 may be fully or partially logically and / or physically separated from another NSI 118 . Resources 122 include physical and logical resources, and NSIs 118 may be configured in sub-network instances 120, which may be shared by multiple NSIs 118 as a special case. NSIs 118 are defined by network slice blueprints. ● When creating an NSI 118, instance-specific policies and configurations are required. ● Examples of network characteristics are ultra-low latency, ultra-reliability, etc.

[0015] The list below contains the current status of agreements on network slicing: ● A network slice is a complete logical network (providing telecommunication services and network functions) including AN and CN components. It is up to the 3GPP RAN Working Group (WG) to decide if a RAN is sliced. An AN may be common to multiple NSIs 118. The NSIs 118 may differ in the features and network function optimization use cases supported. A network may deploy multiple NSIs 118 offering the exact same optimizations and features that are dedicated to different groups of UEs, for example when offering different services with different commitments and / or may be customer-dedicated. The UE may provide an NSSAI consisting of a set of parameters to the network to select a set of RAN and CN portions of the NSI 118 for the UE. If the network deploys network slicing, it may use the UE provided NSSAI to select the network slice. Additionally, the UE capabilities and UE subscription data may be used. ● A UE may simultaneously access multiple slices over one RAN. In such cases, these slices share some control plane functions such as the Authentication Management Function (AMF) and the NSI Selection Function (NSISF). These common functions are collectively identified as the Common Control Network Function (CCNF). ● The CN portion of the NSI that serves the UE is selected by the CN and not by the RAN. ● The UE may force the network to change the set of network slices in use by submitting a new NSSAI value in a Mobility Management (MM) procedure. The final decision is up to the network.

[0016] The network can change the set of network slices used by the UE based on local policy, subscription changes, and / or UE mobility by providing a notification of the accepted NSSAI change to the UE, which then triggers a UE-initiated MM procedure involving Radio Resource Control (RRC) and Non-Access Stratum (NAS) signaling the new value of the new accepted NSSAI provided by the network.

[0017] A change in the set of slices used by the UE (whether UE initiated or network initiated) may result in a CCNF change subject to operator policy. The scenarios, as well as which MM procedures to use when such a UE-triggered network slice change is used, should be determined during the normative phase. Changing the set of network slices accessible by the UE may result in the termination of ongoing Protocol Data Unit (PDU) sessions with the original set of network slices if these slices are no longer used (possibly some slices are still retained). The network subscription data contains information about which slices the UE is authorized to access. The information in the subscription contains both SST and SD information for each slice the UE is authorized to access (SD information is present if applicable to the slice). This is also the Session Management NSSAI (SM-NSSAI) for the slice. The subscription data contains information about whether the slice is the default slice (i.e., the UE should use this slice when the UE is attached to the network). The CN should use the default NSSAI when the UE is initially attached to the network without providing an NSSAI. This NSSAI consists of the SM-NSSAI value stored in the UE subscription information along with a flag indication to be considered as the default slice to determine the default initial network slice serving the UE.

[0018] Furthermore, it is agreed in 3GPP TS 23.501 that the set of network slices for a UE may be changed at any time while the UE is registered to the network and may be initiated by the network or by the UE under certain conditions described below. In this release of this specification, it is assumed that the registration area assigned to the UE by the AMF has the same kind of support for network slicing.

[0019] As can be seen from the above agreement, a UE is assigned a registration area. A registration area contains a collection of Tracking Areas (TAs) consisting of one or more cells. The entire registration area should support the network slice to which the UE is connected. This means that the same slice is supported by all cells in the UE registration area.

[0020] At the 3GPP RAN2 #99 meeting, the topic of how to handle UE cell and frequency selection in relation to slicing was discussed. Below is an excerpt from the meeting report R2-1709158: P2a: According to the 3GPP SA2 group, the maximum number of slices per UE is 8. ● Agreement: o RAN2 understands that a network slice has a RAN part and a CN part. There is no concept of a RAN slice separate from a network slice. RAN2 targets that a RAN solution for network slicing must be able to support a large number of slices (e.g., hundreds of slices). The number of slices supported in parallel by a UE is 8. o From the UE perspective, the UE can be configured to support the requirements of the supported slices (e.g. by appropriate configuration of different Data Radio Bearers (DRBs) for different PDU sessions). For intra-frequency cell reselection, the UE always tries to camp on the best cell. ○ We do not support additional functionality for Random Access Channel (RACH) resource separation / differentiated processing with respect to slicing for 3GPP Release (Rel) 15. ● Working assumptions: Regarding the need for slicing, a proper configuration of dedicated priorities provided by the new radio base station (gNB) can be used to control which frequencies the UE camps on (i.e. reusing the same mechanisms as in LTE) (checking if the gNB has knowledge of all slices the UE is registered on)

[0021] The background to the above discussion was the topic that different cells or frequency layers may have different support for network slicing. In this case, the question is: "How does a UE registered to a slice select a frequency or cell that supports that slice?" This topic was discussed for example in Ericsson's contribution R2-1707799, Slice Availability Ericsson, submitted to the conference. Below is an excerpt from R2-1707799: ● As understood by 3GPP TS group SA2 / RAN3, slice availability is consistent across UE registration areas, although not all slices are expected to be available throughout the network. This means that if a slice is available in one NR or LTE cell, it is at least available in all cells belonging to the same CN Tracking Area. This means that changes to slice availability can be handled when the UE performs a CN level registration area change. This is also the current understanding of 3GPP TS 23.501 section 5.15, where slice availability and connectivity is handled at the NAS level. ● The open question addressed by RAN2 is whether slice availability should be provided to the UE, and if so, how slice availability should be provided to the UE. ● The following main arguments are made as to why slice availability should not be explicitly provided as part of the system information, but should be handled between the UE and the CN (using NAS signalling). o Scalability. If the solution allows for adding hundreds of slices in the future, using broadcasting would be beneficial as it would not scale to these levels due to unnecessary overhead. o Future proofing: new slices, slice types or features may be added in the future, leading to future updates. For this reason it is clearly beneficial to resort to dedicated signaling to handle slice availability which makes it easier to add new features in the future that only affect UEs and networks that support these features. Optimization. Lack of knowledge in the RAN and UE about subscription, service and slice information leading to sub-optimal cell / RAT / frequency selection. Broadcasting slice availability may lead to the UE selecting a sub-optimal cell to camp on when it can receive service from a different slice with similar performance to the original slice based on subscription information available in the CN or operator policies. o Consistent UE behavior. Broadcasting slice availability assumes that the UE uses this information to control the RAT / frequency / cell selection by itself. This may lead to inconsistent UE behavior, making it difficult for operators to introduce new features, frequency tiers, etc. It would be better if the existing slice-agnostic network-controlled RAT / frequency / cell mechanisms are also reused to handle slice availability based on operator policies.

[0022] The meeting adopted the principle of using dedicated priorities. Below is a snippet from the minutes of the above meeting: ● Open problems identified include how the gNB should have knowledge of slices so that it can assign UE frequency (and RAT) priorities.

[0023] 3GPP TS 23.501: Radio Resource Management Functions is also working to define RFSP. The following is an excerpt from 3GPP TS 23.501: ● To support radio resource management in the RAN, the AMF provides the parameter “Index to RAT / Frequency Selection Priority” (RFSP index) to the RAN via N2. ● The RFSP index is mapped by the RAN to a locally defined configuration to apply a specific RRM strategy. ● The RFSP index is UE specific and applies to all radio bearers. ● Examples of how this parameter may be used by the RAN: o Derive UE specific cell reselection priority to control idle mode camping. o Deciding to redirect an active mode UE to a different frequency layer or RAT. - The AMF receives the subscribed RFP indexes (eg during the registration procedure). For non-roaming subscribers, the AMF selects the RFP index in use according to one of the following procedures, depending on the operator configuration: The RFSP index in use is the same as the subscribed RFSP index. o The AMF selects the RFSP index in use based on the UE related context information available to the AMF including the subscribed RFSP indexes, the locally configured operator policies and the UE usage preferences if received during the registration procedure (see 3GPP TS 23.502). ● One example of how the AMF can use the "UE Usage Preferences" is to select an RFSP value that forces idle mode camping on Evolved Universal Terrestrial Radio Access (E-UTRA) for UEs operating in a "voice-centric" manner when voice over NR is not supported in a particular registration area, which contains NR cells. ● For roaming subscribers, the AMF may alternatively select the RFSP index in use based on visited network policies, but taking into account input from the Home Public Land Mobile Network (HPLMN) (e.g. pre-configured RFSP index value per HPLMN, or a single RFSP index value used for all roamers independent of the HPLMN). ● The RFSP index in use is also transferred from the source to the target RAN node when Xn or N2 is used for intra-NG RAN handover. ● The AMF stores the received subscribed RFSP index value and the RFSP index value in use. During the registration update procedure, the AMF may update the RFSP index value in use (e.g. if UE related context information in the AMF has changed, the AMF may need to update the RFSP index value in use). When the RFSP index value in use changes, the AMF provides the updated RFSP index value immediately to the RAN node by modifying the existing UE context or by establishing a new UE context in the RAN, or by being configured to include the updated RFSP index value in use in the downlink NAS transport message if no user plane establishment is required. During the inter-AMF mobility procedure, the source AMF forwards both RFSP index values ​​to the target AMF. The target AMF may replace the received RFSP index value in use with a new RFSP index value in use based on the operator's policies and the UE related context information available in the target AMF. Problems with existing solutions

[0024] One problem with existing solutions is that the gNB does not have knowledge of all slices that the UE is registered on, but needs to know this information in order to assign a dedicated priority to the UE that can be used to control which frequency the UE camps on in scenarios where not all frequency bands support the same slices.

[0025] In other words, the problem is how to assign dedicated priorities to UEs that can be used to control the cells, frequencies, and RATs on which the UEs camp or communicate in scenarios where not all frequency bands or RATs support the same slices. Summary of the Invention

[0026] To address the above challenges, the following solutions are presented.

[0027] According to one aspect, a Core Network (CN) node is configured to communicate with a Radio Access Network (RAN) node, the CN node comprising a processing circuit configured to determine information for Radio Access Technology (RAT) and / or frequency selection and transmit the determined information to the RAN node, the processing circuit being further configured to determine the determined information based on knowledge of a network slice, and the processing circuit being further configured to transmit the knowledge of a network slice together with the determined information to the RAN node.

[0028] In some embodiments, the CN node comprises one of an Authentication Management Function (AMF), a Session Management Function (SMF), a Mobility Management Entity (MME), or a Home Subscriber Server (HSS).

[0029] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information.

[0030] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0031] In some embodiments, the index parameter includes a RAT and / or a Frequency Selection Priority (RFSP) index.

[0032] In some embodiments, the knowledge of network slices is provided to the CN node from a user equipment (UE), a RAN node, or another node.

[0033] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0034] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0035] According to another aspect, a method is implemented in a core network (CN) node, the method comprising: determining information for RAT and / or frequency selection; and transmitting the determined information to a RAN node, wherein determining the information includes determining the information based on knowledge of a network slice, and transmitting the determined information further includes transmitting the knowledge of a network slice to the RAN node together with the determined information.

[0036] In some embodiments, the CN node comprises one of an AMF, an SMF, an MME, or an HSS.

[0037] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, active slices for the UE, slices to which the UE is registered or connected, and / or slices that the UE is authorized to access based on subscription information.

[0038] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0039] In some embodiments, the index parameter comprises an RFS index.

[0040] In some embodiments, the knowledge of network slices is provided to the CN node from a UE, a RAN node, or another node.

[0041] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0042] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0043] According to another aspect, a RAN node is configured to communicate with a UE, the RAN node comprising: a radio interface; and a processing circuit configured to: receive information for RAT and / or frequency selection; use the received information to determine a UE specific cell reselection priority for controlling idle mode camping and / or active mode mobility; and provide the UE specific cell reselection priority to the UE, characterized in at least one of: the received information for RAT and / or frequency selection is determined based on knowledge of a network slice; and the received information for RAT and / or frequency selection further comprises the knowledge of a network slice, and the processing circuit is further configured to use the knowledge of a network slice while determining the UE specific cell reselection priority.

[0044] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, active slices for the UE, slices to which the UE is registered or connected, and / or slices that the UE is authorized to access based on subscription information.

[0045] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0046] In some embodiments, the index parameter comprises an RFSP index.

[0047] In some embodiments, the processing circuitry is further configured to receive the knowledge of a network slice from the UE, a RAN node, or another node.

[0048] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0049] In some embodiments, the information for the RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0050] In some embodiments, the RAN node comprises an enhanced or evolved Node B (eNB) or a new radio base station (gNB).

[0051] According to another aspect, a method is implemented in a RAN node, the method comprising: receiving information for RAT and / or frequency selection; using the received information to determine a UE specific cell reselection priority for controlling idle mode camping and / or active mode mobility; and providing the UE specific cell reselection priority to the UE, characterized in at least one of: the received information for RAT and / or frequency selection is determined based on knowledge of a network slice; and the received information for RAT and / or frequency selection further comprises the knowledge of a network slice, and using the received information to determine the UE specific cell reselection priority further comprises using the knowledge of a network slice to determine a UE specific cell reselection priority.

[0052] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, active slices for the UE, slices to which the UE is registered or connected, and / or slices that the UE is authorized to access based on subscription information.

[0053] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0054] In some embodiments, the index parameter comprises an RFSP index.

[0055] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0056] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0057] According to another aspect, a communication system including a host computer comprises a processing circuit configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a UE, the cellular network comprising a CN node having a processing circuit, the processing circuit of the CN node configured to determine information for RAT and / or frequency selection and transmit the determined information to a RAN node, the processing circuit of the CN node further configured to determine the determined information based on knowledge of a network slice, and the processing circuit of the CN node further configured to transmit the knowledge of a network slice to the RAN node together with the determined information.

[0058] In some embodiments, the system further comprises the RAN node.

[0059] In some embodiments, the system further includes the UE, the UE configured to communicate with the RAN node.

[0060] In some embodiments, the processing circuitry of the host computer is configured to execute a host application thereby providing the user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0061] In some embodiments, the CN node comprises one of an AMF, an SMF, an MME, or an HSS.

[0062] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, active slices for the UE, slices to which the UE is registered or connected, and / or slices that the UE is authorized to access based on subscription information.

[0063] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0064] In some embodiments, the index parameter comprises an RFSP index.

[0065] In some embodiments, the knowledge of network slices is provided to the CN node from a UE, a RAN node, or another node.

[0066] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0067] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0068] In some embodiments, a method is implemented in a communications system including a host computer, a CN node, a RAN node, and a UE, the method comprising: providing user data at the host computer; and initiating a transmission at the host computer to convey the user data to the UE over a cellular network including the CN node, the CN node determining information for RAT and / or frequency selection based on knowledge of a network slice and transmitting the information to the RAN node, the CN node determining the information based on knowledge of a network slice, and the CN node transmitting the knowledge of a network slice to the RAN node together with the determined information.

[0069] In some embodiments, the CN node comprises one of an AMF, an SMF, an MME, or an HSS.

[0070] In some embodiments, the knowledge of network slices includes knowledge of availability of network slices in the network, active slices for the UE, slices to which the UE is registered or connected, and / or slices that the UE is authorized to access based on subscription information.

[0071] In some embodiments, the information for RAT and / or frequency selection includes an index parameter.

[0072] In some embodiments, the index parameter comprises an RFS index.

[0073] In some embodiments, the knowledge of network slices is provided to the CN from a UE, a RAN node, or another node.

[0074] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0075] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0076] According to another aspect, a communication system including a host computer comprises a processing circuit configured to provide user data to a user equipment and a processing interface configured to forward the user data to a cellular network for transmission to a UE, the cellular network including a RAN node having a radio interface and a processing circuit, the processing circuit of the RAN node configured to determine information for RAT and / or frequency selection, use the received information to determine a UE specific cell reselection priority for controlling idle mode camping and / or active mode mobility, and provide the UE specific cell reselection priority to the UE, characterized in at least one of: the received information for RAT and / or frequency selection is determined based on knowledge of a network slice; and the received information for RAT and / or frequency selection further includes the knowledge of a network slice, and the processing circuit of the RAN is further configured to use the knowledge of a network slice while determining a UE specific cell reselection priority.

[0077] In some embodiments, the RAN node includes an eNB or a gNB.

[0078] In some embodiments, the RAN node is configured to receive the information from a CN node for providing the information.

[0079] In some embodiments, the CN node comprises one of an AMF, an SMF, an MME, or an HSS.

[0080] In some embodiments, the system further includes the CN node.

[0081] In some embodiments, the RAN node is configured to receive the information from the UE for providing the information.

[0082] In some embodiments, the system further includes the UE, the UE configured to communicate with the RAN node.

[0083] In some embodiments, the processing circuitry of the host computer is configured to execute a host application thereby providing the user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0084] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0085] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection.

[0086] According to another aspect, a method is implemented in a communication system including a host computer, a RAN node, and a UE, the method comprising: providing, at the host computer, user data; and initiating, at the host computer, a transmission conveying the user data to the UE via a cellular network including the RAN node, the RAN node receiving information for RAT and / or frequency selection, using the received information to determine a UE specific cell reselection priority for controlling idle mode camping and / or active mode mobility, and providing the UE specific cell reselection priority, the received information for RAT and / or frequency selection being determined based on knowledge of a network slice; and the received information for RAT and / or frequency selection further comprising the knowledge of a network slice, and the RAN using the knowledge of a network slice while determining the UE specific cell reselection priority.

[0087] In some embodiments, the user data is provided at the host computer by executing a host application, and the method further comprises executing, at the UE, a client application associated with the host application.

[0088] In some embodiments, the information for RAT and / or frequency selection includes information used to control the frequency on which the UE is camped.

[0089] In some embodiments, the information for RAT and / or frequency selection includes information used to configure frequency priorities for idle mode reselection. [Brief description of the drawings]

[0090] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure.

[0091] [Figure 1] Demonstrates the network slicing concept.

[0092] [Diagram 2] , [Diagram 3] 1 illustrates a schematic diagram of a wireless telecommunications network according to some embodiments.

[0093] [Figure 4] 1 illustrates a user equipment (UE) according to some embodiments.

[0094] [Diagram 5] 1 illustrates a virtualization environment in accordance with some embodiments.

[0095] [Figure 6] 1 illustrates a telecommunications network connected to a host computer through an intermediate network according to some embodiments.

[0096] [Figure 7] FIG. 1 is a generalized block diagram of a host computer in communication with a UE over a partial wireless connection via a base station or other Radio Access Network (RAN) node, in accordance with some embodiments.

[0097] [Figure 8] , [Figure 9] , [Figure 10] , [Figure 11] 1 is a flowchart illustrating a method implemented in a communications system including a host computer, a base station or other RAN node, and a UE, according to some embodiments.

[0098] [Figure 12]1 illustrates a virtualization device according to some embodiments.

[0099] [Figure 13] 1 is a flowchart illustrating a method implemented in a RAN node according to some embodiments.

[0100] [Figure 14] 1 is a flowchart illustrating a method implemented in a core network (CN) node according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0101] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes for practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of the present disclosure.

[0102] Different cells or frequency layers may have different support for network slicing. One issue is how a User Equipment (UE) registered to a slice selects a frequency or cell that supports that slice. Although not all slices are expected to be available in the entire network, slice availability should be configured over the UE registration area. For this reason, information about slice availability should be provided to the UE using dedicated signaling, e.g., a Radio Access Technology (RAT) / Frequency Selection Priority (RFSP) index.

[0103] One problem is that the Radio Access Network (RAN) does not necessarily have knowledge of which slice the UE is currently registered in, which slice the UE is currently connected to, or which slice the UE is allowed to access based on the subscription information, but this information is available to some Core Network (CN) entities such as the Authentication Management Function (AMF), Mobility Management Entity (MME), or Session Management Function (SMF).

[0104] To address the problem of how to assign dedicated priorities to UEs that can be used to control the cells, frequencies, and RATs on which the UE camps or communicates in scenarios where not all frequency bands or RATs support the same slices, embodiments of the present disclosure include methods and systems for RAT or frequency selection based on network slice availability.

[0105] In some embodiments, the selection takes into account information such as, but not limited to, availability of network slices in the network (e.g., in the UE registration area), active network slices for the UE, network slices to which the UE is registered or connected, and network slices to which the UE is authorized to access, for example, based on subscription information. In one embodiment, the selection includes selecting an RFSP index value.

[0106] FIG. 2 illustrates one embodiment of a wireless network according to various aspects described herein. Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described in connection with a wireless network, such as the exemplary wireless network illustrated in FIG. 2. For simplicity, the wireless network of FIG. 2 illustrates only network 206, network nodes 260 and 260b, and wireless devices (WDs) 210, 210b, and 210c. In practice, the wireless network may further include any additional elements suitable for supporting communications between wireless devices or between wireless devices and other communication devices, such as landlines, service providers, or any other network nodes or end devices. Of the illustrated components, network nodes 260 and WDs 210 are illustrated with additional details. The wireless network may provide communications and other types of services to one or more wireless devices to facilitate the wireless devices' access to and / or use of services provided by or via the wireless network.

[0107] A wireless network may include and / or interact with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communications standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable second generation (2G), third generation (3G), fourth generation (4G), or fifth generation (5G) standards, wireless local area network (WLAN) standards such as the IEEE 802.11 standard, and / or any other suitable wireless communications standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, ZWave, and / or ZigBee standards.

[0108] Network 206 may include one or more backhaul networks, CNs, Internet Protocol (IP) networks, Public Switched Telephone Networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices. Network node 260 and WD 210 comprise various components, which are described in more detail below. These components work together to provide the functionality of a network node and / or wireless device, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in communication of data and / or signals, whether via wired or wireless connections.

[0109] As used herein, a network node refers to a device configured and / or operable to communicate, directly or indirectly, with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (e.g., radio base stations, Node Bs, evolved or enhanced Node Bs (eNBs) and New Radio (NR) base stations (gNBs)). Base stations may be classified based on the amount of coverage they provide (or, in other words, their transmit power levels) and may then be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may also be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment, such as an MSR base station, a network controller, such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a CN node (e.g., a mobile switching center (MSC), MME), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile center (E-SMLC)), and / or a minimization and drive test (MDT).As another example, a network node may be a virtual network node, as described in further detail below, but more generally, a network node may represent any suitable device (or group of devices) configured, arranged, and / or operable to enable and / or provide wireless devices with access to a wireless network and / or to provide some service to wireless devices that have accessed the wireless network.

[0110] In FIG. 2, network node 260 includes processing circuitry 270, device readable medium 280, interface 290, auxiliary equipment 284, power source 286, power circuitry 287, and antenna 262. Although network node 260 shown in the exemplary wireless network of FIG. 2 may represent a device including the illustrated combination of hardware components, other embodiments may include network nodes having different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Additionally, although the components of network node 260 are depicted as a single box disposed within a larger box or nested within multiple boxes, in reality the network node may include multiple different physical components that make up a single illustrated component (e.g., device readable medium 280 may include multiple separate hard drives and multiple random access memory (RAM) modules).

[0111] Similarly, network node 260 may be comprised of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In certain scenarios where network node 260 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among multiple network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node, in some cases. In some embodiments, network node 260 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate device-readable media 280 for different RATs) and some components may be reused (e.g., the same antenna 262 may be shared by the RATs). Network node 260 may also include multiple collections of the various illustrated components for different wireless technologies integrated into network node 260, such as, for example, GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or collections of chips and other components within network node 260.

[0112] Processing circuitry 270 is configured to perform any determining, calculating, or similar operations (e.g., a particular acquisition operation) described herein as being provided by a network node. These operations performed by processing circuitry 270 may include, for example, processing the information obtained by processing circuitry 270 by transforming the obtained information into other information, comparing the obtained or transformed information to information stored in the network node, and / or performing one or more operations based on the obtained or transformed information and making a determination as a result of such processing.

[0113] Processing circuitry 270 may comprise one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable, alone or in conjunction with other network node 260 components, such as device readable medium 280, to provide network node 260 functionality. For example, processing circuitry 270 may execute instructions stored on device readable medium 280 or in memory within processing circuitry 270. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, processing circuitry 270 may include a system on a chip (SOC).

[0114] In some embodiments, processing circuitry 270 may include one or more of radio frequency (RF) transceiver circuitry 272 and baseband processing circuitry 274. In some embodiments, RF transceiver circuitry 272 and baseband processing circuitry 274 may be on separate chips (or collection of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of RF transceiver circuitry 272 and baseband processing circuitry 274 may be on the same chip or collection of chips, board, or unit.

[0115] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 270 executing instructions stored on the device-readable medium 280 or memory within the processing circuitry 270. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 270 without executing instructions stored on a separate or distinct device-readable medium, such as in a hardwired manner. In any of these embodiments, the processing circuitry 270 may be configured to perform the described functionality, whether or not it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are not limited to the processing circuitry 270 alone or other components of the network node 260, but may be enjoyed by the network node 260 as a whole, and / or by end users and the wireless network as a whole.

[0116] The device readable medium 280 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuitry 270. The device readable medium 280 may store any suitable instructions, data, or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuitry 270 and utilized by the network node 260. The device readable medium 280 may be used to store any operations performed by the processing circuitry 270 and / or any data received via the interface 290. In some embodiments, the processing circuitry 270 and the device-readable medium 280 may be considered to be integrated.

[0117] The interface 290 is used for wired or wireless communication of signaling and / or data between the network node 260, the network 206, and / or the WD 210. As shown, the interface 290 includes one or more port terminals 294 for transmitting and receiving data to and from the network 206, for example, via a wired connection. The interface 290 also includes a radio front-end circuit 292, which may be coupled to the antenna 262, or in certain embodiments, a portion of the antenna 262. The radio front-end circuit 292 includes a filter 298 and an amplifier 296. The radio front-end circuit 292 may be connected to the antenna 262 and the processing circuit 270. The radio front-end circuit may be configured to condition signals communicated between the antenna 262 and the processing circuit 270. The radio front-end circuit 292 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 292 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 298 and / or amplifiers 296. The radio signal may then be transmitted via the antenna 262. Similarly, in receiving data, the antenna 262 collects the radio signal, which is then converted into digital data by the radio front-end circuitry 292. The digital data may be passed to the processing circuitry 270. In other embodiments, the interface may include different components and / or different combinations of components.

[0118] In certain alternative embodiments, network node 260 may not include a separate radio front-end circuit 292, and instead, processing circuitry 270 may include radio front-end circuitry and may be connected to antenna 262 without a separate radio front-end circuitry 292. Similarly, in some embodiments, all or some of RF transceiver circuitry 272 may be considered part of interface 290. In yet other embodiments, interface 290 may include one or more ports or terminals 294, radio front-end circuitry 292, and RF transceiver circuitry 272 as part of a radio unit (not shown), and interface 290 may communicate with baseband processing circuitry 274 that is part of a digital unit (not shown).

[0119] Antenna 262 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 262 may be coupled to radio front-end circuitry 292 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In some embodiments, antenna 262 may comprise one or more omni-directional sector or panel antennas operable to transmit / receive wireless signals between 2 GHz and 66 GHz, for example. An omni-directional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices within a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively line-of-sight manner. In some examples, the use of more than one antenna may be referred to as multiple-input multiple-output (MIMO). In certain embodiments, antenna 262 may be separate from network node 260 and may be connectable to network node 260 via an interface or port.

[0120] The antenna 262, the interface 290, and / or the processing circuitry 270 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 262, the interface 290, and / or the processing circuitry 270 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0121] The power circuitry 287 may comprise or be coupled to a power management circuitry and is configured to provide power to the components of the network node 260 to perform the functions described herein. The power supply circuitry 287 may receive power from a power source 286. The power source 286 and / or the power circuitry 287 may be configured to provide power to the various components of the network node 260 in a form suitable for each component (e.g., at the voltage and current levels required by each component). The power source 286 may be included in the power circuitry 287 and / or the network node 260 or may be external thereto. For example, the network node 260 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuitry 287. As a further example, the power source 286 may include a power source in the form of a battery or battery pack connected to or integrated with the power circuitry 287. In the event of a failure of the external power source, backup power may be provided from the battery. Other types of power sources, such as photovoltaic devices, may also be used.

[0122] Alternate embodiments of network node 260 may include additional components beyond those shown in Figure 2 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 260 may include user interface devices that allow for the input of information into network node 260 and the output of information from network node 260. This may enable a user to perform diagnostics, maintenance, repair, and other management functions on network node 260.

[0123] As used herein, a WD refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably with UE herein. Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3rd Generation Partnership Project (3GPP) standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), and in this case may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node. In this case, the WD may be a machine-to-machine (M2M) device, which in the 3GPP context may be referred to as a machine-type communication (MTC) device.As one particular example, the WD may be a UE implementing the 3GPP Narrowband IoT (NB-IoT) standard. Particular examples of such machines or devices are metering devices such as sensors, power meters, industrial machines, or home or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment that can monitor and / or report its operating status or other functions related to its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the WD described above may be mobile, in which case it may be referred to as a mobile device or mobile terminal.

[0124] As shown, WD 210 includes antenna 211, interface 214, processing circuitry 220, device readable medium 230, user interface equipment 232, auxiliary equipment 234, power source 236, and power circuitry 237. WD 210 may include multiple collections of one or more of the illustrated components for different wireless technologies supported by WD 210, such as GSM, WCDMA, LTE, NR, WiFi, WiMax, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chip or collection of chips as other components within WD 210.

[0125] Antenna 211 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 214. In certain alternative embodiments, antenna 211 may be separate from WD 210 and may be connectable to WD 210 via an interface or port. Antenna 211, interface 214, and / or processing circuitry 220 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuitry and / or antenna 211 may be considered an interface.

[0126] As shown, the interface 214 includes a radio front-end circuit 212 and an antenna 211. The radio front-end circuit 212 includes one or more filters 218 and an amplifier 216. The radio front-end circuit 212 is connected to the antenna 211 and the processing circuit 220 and configured to condition signals communicated between the antenna 211 and the processing circuit 220. The radio front-end circuit 212 may be coupled to or part of the antenna 211. In some embodiments, the WD 210 may not include a separate radio front-end circuit 212, rather the processing circuit 220 may include a radio front-end circuit and may be connected to the antenna 211. Similarly, in some embodiments, some or all of the RF transceiver circuit 222 may be considered part of the interface 214. The radio front-end circuit 212 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 212 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 218 and / or amplifiers 216. The wireless signal may then be transmitted via antenna 211. Similarly, when receiving data, antenna 211 may collect a wireless signal which is then converted to digital data by wireless front-end circuitry 212. The digital data may be passed to processing circuitry 220. In other embodiments, the interface may include different components and / or different combinations of components.

[0127] The processing circuitry 220 may comprise one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic operable, alone or in conjunction with other WD210 components, such as the device readable medium 230, to provide WD210 functionality. Such functionality may include providing any of the various wireless features or advantages described herein. For example, the processing circuitry 220 may execute instructions stored on the device readable medium 230 or memory within the processing circuitry 220 to provide functionality disclosed herein.

[0128] As shown, the processing circuitry 220 includes one or more of the RF transceiver circuitry 222, the baseband processing circuitry 224, and the application processing circuitry 226. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In certain embodiments, the processing circuitry 220 of the WD 210 may comprise a SOC. In some embodiments, the RF transceiver circuitry 222, the baseband processing circuitry 224, and the application processing circuitry 226 may be on separate chips or a collection of chips. In alternative embodiments, some or all of the baseband processing circuitry 224 and the application processing circuitry 226 may be combined into one chip or a collection of chips, and the RF transceiver circuitry 222 may be on a separate chip or a collection of chips. In further alternative embodiments, some or all of the RF transceiver circuitry 222 and the baseband processing circuitry 224 may be on the same chip or a collection of chips, and the application processing circuitry 226 may be on a separate chip or a collection of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 222, the baseband processing circuitry 224, and the application processing circuitry 226 may be combined within the same chip or collection of chips. In some embodiments, the RF transceiver circuitry 222 may be part of the interface 214. The RF transceiver circuitry 222 may condition the RF signal for the processing circuitry 220.

[0129] In certain embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 220 executing instructions stored on the device readable medium 230, which in certain embodiments may be a computer readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 220 without executing instructions stored on a separate or distinct device readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuitry 220 may be configured to perform the described functionality, whether or not it executes instructions stored on a device readable storage medium. Benefits provided by such functionality are not limited to the processing circuitry 220 alone or other components of the WD 210, but are enjoyed by the WD 210 as a whole, and / or by end users and the wireless network as a whole.

[0130] Processing circuitry 220 may be configured to perform any determination, calculation, or similar operation described herein as being performed by a WD (e.g., a particular acquisition operation). These operations as performed by processing circuitry 220 may include processing the information acquired by processing circuitry 220, for example, by transforming the acquired information to other information, comparing the acquired or transformed information to information stored by WD 210, and / or performing one or more operations based on the acquired or transformed information and making a determination as a result of such processing.

[0131] The device-readable medium 230 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuitry 220. The device-readable medium 230 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., hard disks), removable storage media (e.g., CDs or DVDs), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 220. In some embodiments, the processing circuitry 220 and the device-readable medium 230 may be considered to be integrated.

[0132] The user interface equipment 232 may provide components that allow a human user to interact with the WD 210. Such interaction may be in many forms, such as visual, auditory, tactile. The user interface equipment 232 may be operable to generate output to the user and to allow the user to provide input to the WD 210. The type of interaction may vary depending on the type of user interface equipment 232 installed on the WD 210. For example, if the WD 210 is a smartphone, the interaction may be via a touch screen, if the WD 210 is a smart meter, the interaction may be via a screen that provides usage (e.g., number of gallons used), or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface equipment 232 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface equipment 232 is configured to allow input of information to the WD 210 and is coupled to the processing circuitry 220 to allow the processing circuitry 220 to process the input information. The user interface devices 232 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a universal serial bus (USB) port, or other input circuitry. The user interface devices 232 are also configured to enable output of information from the WD 210 and to enable the processing circuitry 220 to output information from the WD 210. The user interface devices 232 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. The WD 210 may communicate with an end user and / or a wireless network using one or more input / output interfaces, devices, and circuits of the user interface devices 232 and may benefit from the functionality described herein.

[0133] Ancillary equipment 234 is operable to provide more specific functions that may not generally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and types of components of ancillary equipment 234 may vary depending on the embodiment and / or scenario.

[0134] The power source 236 may be in the form of a battery or battery pack in some embodiments. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell, may also be used. The WD 210 may further comprise a power circuit 237 for directing power from the power source 236 to various portions of the WD 210 that require power from the power source 236 and for performing any of the functions described or illustrated herein. The power circuit 237 may comprise a power management circuit in certain embodiments. The power circuit 237 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 210 may be connectable to the external power source (such as an electrical outlet) via an interface such as an input circuit or a power cable. The power circuit 237 may also be operable in certain embodiments to direct power from the external power source to the power source 236. This may be for example, for charging the power source 236. The power circuit 237 may perform any formatting, conversion, or other modification of the power from the power source 236 to make it suitable for the respective components of the WD 210 being powered.

[0135] FIG. 3 illustrates an embodiment of a wireless network according to various aspects described herein. In FIG. 3, a simplified telecommunications network 300 includes a CN 302 that includes various CN nodes. In the embodiment illustrated in FIG. 3, the network 300 includes an AMF 304, an SMF 306, an MME 308, and a Home Subscriber Service (HSS) 310, although it should be understood that other types of nodes and collections of nodes are contemplated by the subject matter described herein. The CN 302 provides connectivity between these CN nodes and a RAN node 312 that is serving a wireless device 314, which may also be referred to herein as a WD 314 or a UE 314.

[0136] According to one aspect, a CN function is provided for setting (or selecting, calculating, determining, etc.) index parameters for RAT and frequency selection based on slice knowledge associated with the UE. The index parameters may be provided to the RAN node 312 to be used for RAT or frequency selection for inactive or idle or active UEs. In the embodiment shown in FIG. 3, the RAN node 312 receives information 316 from a node in the CN 302. The information 316 may comprise index parameters, subscription information, and / or slice information. In one embodiment, the index parameter may include an RFSP index. In some embodiments, the selected RFSP index value is communicated to the RAN, which can then set UE-specific cell reselection priorities to control idle mode camping, for example, to ensure that the UE camps on a frequency layer or RAT that supports the slice to which the UE is connected. This solution may also be used to control active mode (e.g., handover) mobility to direct the UE to a preferred frequency layer or RAT that supports the UE slice.

[0137] The RAN node 312, which may be, for example, an eNB / gNB, can then configure a "UE specific cell reselection priority" to control idle mode camping, for example to ensure that the UE 314 camps on a frequency layer or RAT that supports the slice to which the UE 314 is connected. The solution can also be used to control active mode (e.g., handover) mobility to steer the UE to a preferred frequency layer or RAT that supports the UE slice.

[0138] According to another aspect, the RAN node 312 performs a mapping to a mobility policy for UE active or idle mobility based on the index parameter and slice and / or subscription information provided by the CN node. In these embodiments, the RAN 312 performs a mapping to a "UE specific cell reselection priority" based on the index parameter and slice and / or subscription information provided by the CN. In some embodiments, this information may be combined with or based on knowledge of subscription related information or other information (e.g., gold / silver / bronze subscription, public safety subscription, etc.) to set the value of the index parameter.

[0139] In one embodiment, the CN node that sets the index parameter includes an AMF 304, an SMF 308, or an MME 308 node. ● The availability of network slices in the network (e.g. in the UE registration area); ● UE active slices, the slice to which the UE is registered or connected, and ● The slices that the UE is allowed to access, e.g. based on subscription information; It is set / selected / calculated / determined, etc., based on knowledge of one or more of the following:

[0140] The selection process may be performed by or with the help of several network entities, in which case some or all of the information 316 may be sent by the AMF 304, the SMF 306, the MME 308, the HSS 310, or other CN nodes. For example, in an embodiment where only slices that the UE 314 is authorized to access based on subscription information are considered for assigning an RFSP, it is possible to directly select the RAT and / or frequency based on slice information in the HSS 310 or other subscription database.

[0141] In embodiments where other more dynamic information, such as active or registered slices, is taken into account, it is possible to select the RAT and / or frequency based on information available to the AMF 304 and / or SMF 306. In these embodiments, the AMF 304 or SMF 306 may select the RFSP index based on UE-related context information available to the AMF, including, for example, subscribed RFSP indexes, locally configured operator policies, and UE usage settings.

[0142] In alternative embodiments, different network entities may perform different parts of the selection process. For example, in one embodiment, some information may be provided by the HSS 310 (e.g., the set of valid RFSPs) and other information may be provided by the AMF 304 (e.g., the AMF 304 selects one of the valid RFSPs based on the slice information).

[0143] In an alternative embodiment of the solution, the CN provides the RAN node 312 with both information about the RFSP and information about which slices, e.g., network slice availability in the network (e.g., in the UE registration area), active slices for the UE, slices to which the UE is registered or connected, and slices that the UE is allowed to access based on subscription information. In this embodiment, the RAN node 312 may perform a final mapping between the RFSP and slice information to determine a "UE-specific cell reselection priority" to control idle mode camping or to control active mode (e.g., handover) mobility to steer the UE to a preferred frequency layer or RAT that supports the UE slice.

[0144] As mentioned above, according to the SA2 / RAN3 understanding, slice availability will be consistent across the UE registration area, although not all slices are expected to be available throughout the network. This means that if a slice is available in one NR or LTE cell, it will at least be available in all cells belonging to the same CN tracking area. This means that any changes to slice availability can be handled when the UE performs a CN level registration area change. This is also the current understanding of 3GPP TS 23.501 section 5.15, where availability and connectivity to slices is handled at the Non-Access Stratum (NAS) level.

[0145] A consequence of this agreement related to slice availability on different frequency layers is that different frequency layers cannot be part of the same CN tracking area if they do not support the same slice. However, this is acceptable if the network supports multiple frequency layers with different slice support, since the network can configure the UE with different registration areas (Tracking Area (TA) lists) depending on whether the UE is connected to slices supported on multiple frequency layers or to slices supported on a single frequency layer. In the latter case, the UE needs to perform a CN registration area update when changing frequency layers, and in the former case, no update is required.

[0146] Changing the current SA2 / RAN3 assumptions that allow for different slice availability within a CN tracking / registration area would lead to significant issues such as a UE being unable to be reached for service but not knowing about it, or the UE responding to paging in an area where it cannot be served.

[0147] In one embodiment, SA2 / RAN3 agreement regarding consistent slice and service support within a UE registration area is maintained, in such an embodiment, different frequency layers supporting different slices need to be assigned different CN Tracking Areas.

[0148] Networks are expected to support a large number of slices. This makes it inefficient to provide input regarding slice availability on the system information for frequency selection, instead solutions have to resort to dedicated means. Currently, in LTE, there is support for dedicated frequency prioritization based on subscription information using idleModebilityControlInfo (specified in 3GPP TS36.331). The RAN knows the UE subscription information from the subscriber profile ID (ID) for the RFSP (see 3GPP TS36.413). The mapping between these parameters is up to the local RAN configuration (see 3GPP TS36.300).

[0149] For 5GC, SA2 introduced the concept of RFSP information, which seems to have a similar purpose as the Subscriber Profile ID for RAT / frequency priority in LTE / Evolved Packed Core (EPC). Given that 5GC has knowledge of which slice the UE is connected to, as well as which slices the UE may connect to, it should be possible to set the RFSP based on this knowledge, thus allowing the RAN node 312 to set idleModeMobilityControlInfo. Alternatively, it would be possible for the gNB to set idleModebilityControlInfo alone, based on a combination of the RFSP and knowledge of which slice the UE 314 was connected to at the time of release. The RAN node 312 would know this, since the slice information is included in the 3GPP TS38.413 PDU Session Resource Setup Request.

[0150] In one embodiment, the CN may configure the RFSP taking into account slice information, as this minimizes the impact on the RAN and leads to consistent processing of all service / slice information. The CN needs to have knowledge of the UE slice information anyway when allocating the UE registration area.

[0151] In case a UE is assigned to multiple slices, the frequency prioritization needs to take this into account. In our view, this should be possible since the CN has knowledge of the slices supported and can set the RFSP according to which slice is most preferred or have a specific RFSP value for a combination of slices. We consider it to be a rare case that the slices supported by a single UE do not have a common frequency layer that supports all slices. In one embodiment, the RAN should map the RFSP to the configured idleModeMobilityControlInfo, which is independent if the RFSP is set due to slicing or other subscription related information.

[0152] In one embodiment, slice availability should not be broadcast and used for UE-based RAT, frequency, or cell selection. Instead, it is sufficient to use the network control mechanisms agreed upon in RAN2#99 to support limited slice availability.

[0153] FIG. 4 illustrates one embodiment of a UE according to various aspects described herein. As used herein, a UE does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may or may not be associated with a particular human user, or may not be associated initially. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. UE 400 may be any UE identified by 3GPP, including an NB-IoT UE, an MTC UE, and / or an evolved MTC (eMTC) UE. As illustrated in FIG. 4, UE 400 is one example of a WD configured to communicate according to one or more communications standards promulgated by 3GPP, such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As mentioned above, the terms WD and UE may be used interchangeably, so while Figure 4 is a UE, the components described herein are equally applicable to a WD and vice versa.

[0154] In FIG. 4, UE 400 includes a processing circuit 401 operatively coupled to an input / output interface 405, an RF interface 409, a network connection interface 411, memory 415 including RAM 417, ROM 419, and storage medium 421, a communication subsystem 431, a power source 413, and / or any other components, or any combination thereof. Storage medium 421 includes an operating system 423, application programs 425, and data 427. In other embodiments, storage medium 421 may include other similar types of information. A given UE may utilize all of the components shown in FIG. 4, or only a subset of the components. The level of integration between components may vary from UE to UE. Additionally, a given UE may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, and the like.

[0155] In FIG. 4, processing circuitry 401 may be configured to process computer instructions and data. Processing circuitry 401 may be configured to implement any sequential state machine that operates to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more stored programs, a general purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, processing circuitry 401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0156] In the illustrated embodiment, the input / output interface 405 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 400 may be configured to use an output device via the input / output interface 405. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 400. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 400 may be configured to use an input device via the input / output interface 405 to allow a user to capture information into the UE 400. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0157] In FIG. 4, the RF interface 409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 411 may be configured to provide a communication interface to a network 443a. The network 443a may include a wired and / or wireless network such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 443a may include a Wi-Fi network. The network connection interface 411 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols such as Ethernet, Transport Control Protocol TCP / IP, Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), and the like. The network connection interface 411 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or may be implemented separately.

[0158] The RAM 417 may be configured to interface to the processing circuit 401 via the bus 402 to provide storage or caching of data or computer instructions during execution of software programs such as the operating system, application programs, and device drivers. The ROM 419 may be configured to provide computer instructions or data to the processing circuit 401. For example, the ROM 419 may be configured to store unchanging low-level system code or data for basic system functions such as basic input / output (I / O), start-up, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, storage medium 421 may be configured to include an operating system 423, an application program 425, such as a web browser application, a widget or gadget engine or another application, and data files 427. Storage medium 421 may store any of a variety of operating systems or combinations of operating systems for use by UE 400.

[0159] The storage medium 421 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density DVD (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-ray optical disk drive, a Holographic Digital Data Storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module (SIM) or a removable user identity module (RUIM), other memory, or any combination of these. The storage medium 421 may enable the UE 400 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. Products such as those utilizing a communication system may be tangibly embodied in the storage medium 421, which may comprise a device-readable medium.

[0160] In FIG. 4, the processing circuit 401 may be configured to communicate with the network 443b using the communication subsystem 431. The network 443a and the network 443b may be the same network or different networks. The communication subsystem 431 may be configured to include one or more transceivers used to communicate with the network 443b. For example, the communication subsystem 431 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or a base station of a RAN, according to one or more communication protocols, such as IEEE 802.4, Code Division Multiple Access (CDMA), WCDMA, GSM, LTE, Universal Terrestrial Access Network (UTRAN), WiMax, etc. Each transceiver may include a transmitter 433 and / or a receiver 435 to respectively implement transmitter or receiver functions (e.g., frequency allocation, etc.) appropriate for the RAN link. Additionally, the transmitter 433 and receiver 435 of each transceiver may share circuit components, software, or firmware or may be implemented separately.

[0161] In the illustrated embodiment, the communication capabilities of the communication subsystem 431 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, short-range communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 431 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 443b may include wired and / or wireless networks, such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, other similar networks, or any combination thereof. For example, the network 443b may be a cellular network, a Wi-Fi network, and / or a short-range network. The power source 413 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 400.

[0162] The features, advantages, and / or functions described herein may be implemented in one of the components of the UE 400 or may be distributed across multiple components of the UE 400. Furthermore, the features, advantages, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 431 may be configured to include any of the components described herein. Furthermore, the processing circuitry 401 may be configured to communicate with any of such components via the bus 402. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuitry 401, perform the corresponding functions described herein. In another example, the functions of any of such components may be distributed between the processing circuitry 401 and the communication subsystem 431. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware. Cloud Implementation

[0163] In one embodiment, the mapping of slice information to RFSP may be performed at the node being virtualized.

[0164] 5 is a schematic block diagram illustrating a virtualization environment 500 in which functionality implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage, and networking resources. As used herein, virtualization may apply to a node (e.g., a virtualized base station or a virtualized radio access network node) or device (e.g., a UE, a wireless device, or any other type of communication device) or component thereof, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0165] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented within one or more virtual environments 500 hosted by one or more of the hardware nodes 530. Additionally, in embodiments where the virtual node is not a wireless access network node or does not require wireless connectivity (e.g., a CN node), the network node may be fully virtualized.

[0166] The functionality may be implemented by one or more applications 520 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of the embodiments disclosed herein. The applications 520 execute in a virtualization environment 500 that provides hardware 530 with processing circuitry 560 and memory 590. The memory 590 includes instructions 595 executable by the processing circuitry 560 such that the applications 520 are operable to provide one or more of the features, advantages, and / or functions disclosed herein.

[0167] The virtualization environment 500 includes a general-purpose or special-purpose network hardware device 530 that includes a collection of one or more processors or processing circuitry 560, which may be a commercial off-the-shelf (COTS) processor, a dedicated application specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 590-1, which may be a non-persistent memory for temporarily storing instructions 595 or software executed by the processing circuitry 560. Each hardware device may include one or more network interface controllers (NICs) 570, also known as network interface cards, that include a physical network interface 580. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 590-2 that stores software 595 and / or instructions executable by the processing circuitry 560. Software 595 may include any type of software, including software for instantiating one or more virtualization layers 550 (also referred to as a hypervisor), software for running virtual machines 540, as well as software that enables the implementation of the functions, features and / or advantages described in association with some of the embodiments described herein.

[0168] The virtual machines 540 may include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by a corresponding virtualization layer 550 or hypervisor. Different embodiments of an instance of a virtual device 520 may be implemented in one or more of the virtual machines 540, and the implementations may be done in different ways. In operation, the processing circuitry 560 executes software 595 to instantiate a hypervisor or virtualization layer 550, which may also be referred to as a virtual machine monitor (VMM). The virtualization layer 550 may present a virtual operating platform to the virtual machines 540 that appears as networking hardware.

[0169] 5, the hardware 530 may be a standalone network node with generic or specific components. The hardware 530 may include an antenna 5225 and may implement some functionality via virtualization. Alternatively, the hardware 530 may be part of a larger cluster of hardware (e.g., in a data center or CPE) where many hardware nodes work together and are managed via a Management and Orchestration (MANO) 5100 that oversees, among other things, the lifecycle management of the application 520.

[0170] Hardware virtualization occurs in several contexts, referred to as network functions virtualization (NFV), which may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches and storage that may be located in data centers, as well as customer premises equipment.

[0171] In the context of NFV, a virtual machine 540 may be a software implementation of a physical machine that executes programs as if they were running on a physical, non-virtualized machine. Each virtual machine 540, and the portion of hardware 530 on which it runs, forms a separate Virtual Network Element (VNE), be it hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of the virtual machines 540.

[0172] Still in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running on one or more virtual machines 540 on the hardware networking infrastructure 530 and corresponds to application 520 in FIG. 5.

[0173] In some embodiments, one or more radio units 5200, each including one or more transmitters 5220 and one or more receivers 5210, may be coupled to one or more antennas 5225. The radio units 5200 may communicate directly with the hardware node 530 via one or more suitable network interfaces, or may be used in combination with virtual components to provide radio functionality to the virtual node, such as a radio access network node or base station.

[0174] In some embodiments, some signaling may be accomplished using a control system 5230 which may alternatively be used for communication between the hardware nodes 530 and the wireless unit 5200. Over-the-Top (OTT) on Network Slices

[0175] FIG. 6 illustrates one embodiment of a communication system according to various aspects described herein. Referring to FIG. 6, according to one embodiment, the communication system includes a telecommunication network 610, such as a 3GPP-type cellular network, comprising an access network 611, such as a radio access network, and a CN 614. The access network 611 comprises a number of base stations 612a, 612b, 612c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 613a, 613b, 613c. Each base station 612a, 612b, 612c is connectable to the CN 614 via a wired or wireless connection 615. A first UE 691 located within the coverage area 613c is configured to wirelessly connect to or be paged by a corresponding base station 612c. A second UE 692 within the coverage area 613a is wirelessly connectable to a corresponding base station 612a. Although multiple UEs 691, 692 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is within the coverage area or is connected to a corresponding base station 612.

[0176] The telecommunications network 610 is itself connected to a host computer 630, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or processing resources in a server farm. The host computer 630 may be under the ownership or control of the service provider, or may be operated by or on behalf of the service provider. The connections 621 and 622 between the telecommunications network 610 and the host computer 630 may extend directly from the CN 614 to the host computer 630, or may go through an optional intermediate network 620. The intermediate network 620 may be a combination of one or more of a public, private, or hosted network, and the intermediate network 620 may be a backbone network or the Internet, if any, and in particular the intermediate network 620 may include two or more sub-networks (not shown).

[0177] The communication system of FIG. 6 as a whole enables a connection between the connected UEs 691, 692 and the host computer 630. The connection may be described as an OTT connection 650. The host computer 630 and the connected UEs 691, 692 are configured to communicate data and / or signaling over the OTT connection 650 using the access network 611, the CN 614, any intermediate network 620, and possible further infrastructure (not shown) as intermediaries. The OTT connection 650 may be transparent in the sense that the participating communication devices through which the OTT 650 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 612 may not and does not need to be informed about the past routing of incoming downlink communications with data originating from the host computer 630 to be forwarded (e.g., handed over) to the connected UE 691. Similarly, the base station 612 does not need to be aware of the future routing of outgoing uplink communications from the UE 691 to the host computer 630.

[0178] FIG. 7 illustrates another embodiment of a communication system according to various aspects described herein. According to an embodiment, an example implementation of the UE, base station, and host computer described in the preceding paragraphs is now described with reference to FIG. 7. In the communication system 700, the host computer 710 includes hardware 715 including a communication interface 716 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 700. The host computer 710 further includes a processing circuit 718 that may have storage and / or processing capabilities. In particular, the processing circuit 718 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 710 further includes software 711, which is stored in or accessible to the host computer 710 and executable by the processing circuit 718. The software 711 includes a host application 712. The host application 712 may be operable to provide services to a remote user, such as a UE 730, that connects via an OTT connection 750 that terminates at the host computer 710. In providing services to the remote user, the host application 712 may provide user data that is transmitted using the OTT connection 750.

[0179] The communication system 700 further includes a base station 720 provided in a remote communication system and including hardware 725 enabling communication with a host computer 710 and a UE 730. The hardware 725 may include a communication interface 726 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 700, as well as a radio interface 727 for setting up and maintaining at least a wireless connection 770 with a UE 730 located in a coverage area (not shown in FIG. 7) served by the base station 720. The communication interface 726 may be configured to facilitate a connection 760 to the host computer 710. The connection 760 may be direct, may pass through a CN (not shown in FIG. 7) of the telecommunication system, and / or may pass through one or more intermediate networks outside the telecommunication system. In the illustrated embodiment, the hardware 725 of the base station 720 further includes a processing circuit 728, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Additionally, base station 720 includes software 721 that is either stored internally or accessible via an external connection.

[0180] The communication system 700 further includes the UE 730 already mentioned. This hardware 735 may include a radio interface 737 configured to set up and maintain a wireless connection 770 with a base station serving the coverage area in which the UE 730 is currently located. The hardware 735 of the UE 730 further includes a processing circuit 738, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 730 further includes software 731, which may be stored or accessible within the UE 730 and executable by the processing circuit 738. The software 731 includes a client application 732. The client application 732 may be operable to provide services to a human or non-human user via the UE 730 with the support of the host computer 710. In the host computer 710, an executing host application 712 may communicate with an executing client application 732 via the UE 730 and an OTT connection 750 that terminates at the host computer 710. In providing a service to a user, the client application 732 may receive request data from the host application 712 and provide user data in response to the request data. The OTT connection 750 may transport both the request data and the user data. The client application 732 may interact with the user and generate the user data that it provides.

[0181] It should be noted that the host computer 710, base station 720, and UE 730 shown in Figure 7 may be similar to or identical to the host computer 630, one of the base stations 612a, 612b, 612c, and one of the UEs 691, 692, respectively, of Figure 6. That is, the internal operation of these entities may be as shown in Figure 7, and independently, the surrounding network topology may be that of Figure 6.

[0182] 7, the OTT connection 750 is depicted abstractly to illustrate communication between the host computer 710 and the UE 730 via the base station 720, without explicitly referencing any intermediate devices or the exact routing of messages through these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 730, or from the service provider operating the host computer 710, or both. The network infrastructure may further decide to dynamically change the routing while the OTT connection 750 is active (e.g., based on load balancing considerations or network reconfiguration).

[0183] The wireless connection 770 between the UE 730 and the base station 720 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 730 using the OTT connection 750 of which the wireless connection 770 forms the final segment. More precisely, the teachings of these embodiments may improve network slice selection, thereby providing benefits such as uninterrupted OTT services.

[0184] Measurement procedures may be provided for purposes of monitoring data rates, latencies, and other factors that one or more embodiments improve upon. Additionally, there may be optional network functionality for reconfiguring the OTT connection 750 between the host computer 710 and the UE 730 in response to variations in the measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 750 may be implemented in the software 711 and hardware 715 of the host computer 710, or in the software 731 and hardware 735 of the UE 730, or both. In an embodiment, sensors (not shown) may be deployed in or associated with the communications devices through which the OTT connection 750 passes, and the sensors may participate in the measurement procedures by providing values ​​for the monitored quantities exemplified above, or by providing values ​​for other physical quantities for which the software 711, 731 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 750 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 720, and this may be unknown or unperceived by the base station 720. Such procedures and functions are known in the art and may be practiced. In one embodiment, the measurements may include proprietary UE signaling to facilitate host computer 710 measurements of throughput, propagation time, latency, etc. The measurements may be performed by having the OTT connection 750 send messages, particularly empty or "dummy" messages, while software 711 and 731 monitor propagation times, errors, etc.

[0185] FIG. 8 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a UE, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 6 and FIG. 7. To simplify the disclosure, only drawing references to FIG. 8 are included in this section. In step 810, the host computer provides user data. In sub-step 811 of step 810, which may be optional, the host computer provides the user data by executing a host application. In step 820, the host computer initiates a transmission conveying the user data to the UE. In step 830, which may be optional, the base station transmits the user data conveyed in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 840, which may be optional, the UE executes a client application associated with the host application executed by the host computer.

[0186] FIG. 9 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a UE, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 6 and FIG. 7. To simplify this disclosure, only drawing references to FIG. 9 are included in this section. In step 910 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 920, the host computer initiates a transmission conveying the user data to the UE. The transmission may be passed through the base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 930, which may be optional, the UE receives the user data conveyed in the transmission.

[0187] FIG. 10 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 6 and FIG. 7. To simplify the disclosure, only drawing references to FIG. 10 are included in this section. In step 1010, which may be optional, the UE receives input data provided by the host computer. Additionally or alternatively, in step 1020, the UE provides user data. In sub-step 1021 of step 1020, which may be optional, the UE provides the user data by executing a client application. In sub-step 1011 of step 1010, which may be optional, the UE executes a client application that provides user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from a user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 1030, which may be optional. In step 1040 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0188] FIG. 11 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 6 and FIG. 7. To simplify the disclosure, only drawing references to FIG. 11 are included in this section. In step 1110 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1120 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1130 (which may be optional), the host computer receives the user data conveyed in the transmission initiated by the base station.

[0189] 12 shows a schematic block diagram of an apparatus 1200 in a wireless network (e.g., the wireless network shown in FIG. 2). The apparatus may be implemented in a wireless device, a base station, or a network node (e.g., the wireless device 210 or the network node 260 shown in FIG. 2, or the base station 720 shown in FIG. 7). The apparatus 1200 is operable to perform example processes or methods disclosed herein. It should also be understood that the processes or methods disclosed herein are not necessarily performed solely by the apparatus 1200. At least some operations of the method may be performed by one or more other entities.

[0190] The virtual device 1200 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include DSPs, dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes, in some embodiments, program instructions for implementing one or more telecommunications and / or data communication protocols, as well as instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause various units within the device to perform corresponding functions according to one or more embodiments of the present disclosure.

[0191] As illustrated in FIG. 12, the apparatus 1200 includes one or more of a receiving unit 1202, a determining unit 1204, and a transmitting unit 1206. In one embodiment, the apparatus 1200 may implement a function of a base station, in which case the receiving unit 1202 may receive information for radio access technology (RAT) and / or frequency selection based on knowledge of a network slice, and the transmitting unit 1206 may provide the information to the UE. In another embodiment, the apparatus 1200 may implement a function of a CN node, in which case the determining unit 1204 may determine information for radio access technology (RAT) and / or frequency selection based on knowledge of a network slice, and the transmitting unit 1206 may transmit the information to the base station.

[0192] The term unit may have its conventional meaning in the art of electronic equipment, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for performing a discrete task, procedure, computation, output, and / or display function, etc., as described herein.

[0193] 13 is a flow chart illustrating a method implemented in a base station according to some embodiments. In the embodiment shown in FIG. 13, the method includes receiving information for RAT and / or frequency selection, which may or may not be determined based on knowledge of a network slice and may optionally include knowledge of a network slice (step 1300), using the received information (with or without knowledge of the network slice) to determine a UE-specific cell reselection priority for controlling idle mode camping and / or active mode mobility (step 1302), and providing the UE-specific cell reselection priority to a UE (step 1304).

[0194] Figure 14 is a flow chart illustrating a method implemented in a CN node according to some embodiments. In the embodiment shown in Figure 14, the method includes determining information for RAT and / or frequency selection, which may or may not be determined based on knowledge of a network slice (step 1400), and transmitting this information (which may optionally also include knowledge of the network slice) to a RAN node (step 1402).

[0195] For example, in one embodiment, the CN node may consider network slice knowledge when determining information for RAT and / or frequency selection and transmit only the determined information to the RAN node. In another embodiment, the CN node may determine information for RAT and / or frequency selection without considering network slice knowledge and instead choose to transmit the network slice knowledge to the RAN node together with the information determined by the CN node, letting the RAN node make its own decision based on the information determined by the CN node and the network slice knowledge. In yet another embodiment, the CN node may consider network slice knowledge while determining information for RAT and / or frequency selection, but may transmit the network slice knowledge information to the RAN node anyway together with the information determined by the CN node, in which case both the CN node and the RAN node consider network slice knowledge while making their respective decisions. Advantages of the proposed solution

[0196] The advantage of the solution when the CN performs the mapping between UE slices and index parameters such as RFSP index itself is that the RAN or RAN node does not need to know why a particular UE is assigned to a particular index parameter: the RAN or RAN node only needs to know which UE-specific cell frequency RAT reselection priority should be applied for a given RFSP index.

[0197] This solution can be used for both IDLE (UE triggered) and ACTIVE (network controlled) mobility.

[0198] The CN may also take into account (other) subscription-based information in setting the RFSP index, which allows having a cell / frequency selection policy that is consistent with both slice information and other subscription-related policies, which would be difficult in a RAN-based solution since the RAN does not know much about subscription information.

[0199] The advantage of the alternative embodiment where the CN provides slice information to the RAN together with the RFSP index is that in this case information related to registered and supported slices as well as active slices for the UE becomes available at the RAN, solving some of the above mentioned drawbacks like lack of knowledge of subscription information. Numbered embodiments

[0200] Without being limiting, some exemplary embodiments of the present disclosure are provided below. 1. A base station configured to communicate with a UE, the base station comprising: a radio interface; and processing circuitry configured to receive information for RAT and / or frequency selection based on knowledge of a network slice, and to provide the information to the UE. 2. In the base station of embodiment 1, the knowledge of network slices includes knowledge of an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information, the base station. 3. The base station of embodiment 1 or 2, wherein the information for RAT and / or frequency selection includes an index parameter. 4. A base station according to embodiment 3, wherein the index parameter includes a RAT and / or an RFSP index. 5. A base station as described in any one of embodiments 1 to 4, wherein the base station is configured to receive the knowledge of a network slice from the UE, a RAN node, or another node. 6. A communications system including a host computer having a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a UE, the cellular network comprising a base station having a radio interface and processing circuitry, the processing circuitry of the base station configured to receive information for RAT and / or frequency selection based on knowledge of a network slice and to provide the information to the UE. 7. A communications system as described in embodiment 6, wherein the base station is configured to receive the information from a CN node for supplying the information. 8. A communication system as described in embodiment 6 or 7, further comprising the CN node. 9. A communications system as claimed in any one of claims 6 to 8, wherein the base station is arranged to receive said information from a UE node for providing said information. 10. A communication system as described in any one of embodiments 6 to 8, further comprising the UE, the UE being configured to communicate with the base station. 11. A communications system as claimed in any one of claims 6 to 10, wherein the processing circuitry of the host computer is configured to execute a host application thereby providing the user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application. 12. A CN node configured to communicate with a base station, the CN node comprising processing circuitry configured to determine information for RAT and / or frequency selection based on knowledge of a network slice and to transmit the information to the base station. 13. A CN node as described in embodiment 12, wherein the CN node includes one of an AMF, an SMF, an MME, or an HSS. 14. A CN node as described in embodiment 12 or 13, wherein the knowledge of network slices includes knowledge of an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information. 15. A CN node as described in any one of embodiments 12 to 14, wherein the information for RAT and / or frequency selection includes an index parameter. 16. The CN node of embodiment 15, wherein the index parameter includes an RFSP index. 17. A CN node as described in any one of embodiments 12 to 16, wherein the knowledge of network slices is provided to the CN from a UE, a RAN node, or another node. 18. A communications system including a host computer having processing circuitry configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a UE, the cellular network comprising a CN node having processing circuitry, the processing circuitry of the CN node configured to determine information for RAT and / or frequency selection based on knowledge of a network slice and to transmit the information to the base station. 19. The communication system of embodiment 18, further comprising the base station. 20. A communication system as described in embodiment 18 or 19, further comprising the UE, the UE being configured to communicate with the base station. 21. A communications system as described in any one of embodiments 18 to 20, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data, and the UE is provided with processing circuitry configured to execute a client application associated with the host application. 22. A communications system as described in any one of embodiments 18 to 21, wherein the CN node includes one of an AMF, an SMF, an MME, or an HSS. 23. A communications system as described in any one of embodiments 18 to 22, wherein the knowledge of network slices includes knowledge of an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information. 24. A communications system as described in any one of embodiments 18 to 23, wherein the information for RAT and / or frequency selection includes an index parameter. 25. A communication system as described in embodiment 24, wherein the index parameter includes an RFSP index. 26. A communications system as described in any one of embodiments 18 to 25, wherein the knowledge of network slices is provided to the CN node from a UE, a RAN node, or another node. 27. A method implemented in a base station, the method comprising: receiving information for RAT and / or frequency selection based on knowledge of a network slice; and providing the information to the UE. 28. The method of embodiment 27, wherein the information for RAT and / or frequency selection includes an index parameter. 29. The method of embodiment 28, wherein the index parameter comprises an RFSP index. 30. A method implemented in a communications system including a host computer, a base station, and a UE, comprising: providing user data at the host computer; and initiating a transmission at the host computer to convey the user data to the UE via a cellular network comprising the base station, wherein the base station receives information for RAT and / or frequency selection based on knowledge of a network slice and provides the information to the UE. 31. A method as described in embodiment 30, wherein the user data is provided in the host computer by executing a host application, and the method further comprises executing, in the UE, the client application associated with the host application. 32. A method implemented in a CN node, the method comprising determining information for RAT and / or frequency selection based on knowledge of a network slice, and transmitting the information to the base station. 33. A method as described in embodiment 32, wherein the knowledge of network slices includes knowledge of an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information. 34. The method of embodiment 32 or 33, wherein the information for RAT and / or frequency selection includes an index parameter. 35. The method of embodiment 34, wherein the index parameters include a RAT and / or an RFSP index. 36. A method implemented in a communications system including a host computer, a CN node, a base station, and a UE, the method comprising: providing user data at the host computer; and initiating a transmission at the host computer to convey the user data to the UE via a cellular network including the CN node, the CN node determining information for RAT and / or frequency selection based on knowledge of a network slice, and transmitting the information to the base station. 37. A method as described in embodiment 39, wherein the knowledge of network slices includes knowledge of an active slice for the UE, a slice to which the UE is registered or connected, and / or a slice to which the UE is authorized to access based on subscription information. 38. The method of embodiment 36 or 37, wherein the information for RAT and / or frequency selection includes an index parameter. 39. The method of embodiment 38, wherein the index parameters include a RAT and / or an RFSP index.

[0201] In this disclosure, at least some of the following abbreviations may be used. In case of discrepancies between the abbreviations, how it is used above shall prevail. If listed multiple times below, the first listing shall prevail over any subsequent listings. ● 2G 2nd Generation ● 3G 3rd generation ● 3GPP 3rd Generation Partnership Project ● 4G 4th generation ● 5G (fifth generation) ● 5GC 5th Generation Core Network ● AC alternating current - AMF authentication management function ● AN Access Network ● AP Access Point ● ASIC Application Specific Integrated Circuit ATM Asynchronous Transfer Mode ● BSC Base Station Control Unit ● BTS wireless base station ● CCNF Common Control Network Function ● CD Compact Disc ● CDMA Code Division Multiple Access ● CN Core Network ● COTS Commercially On-the-Shelf ● CPE (Customer Premises Equipment) ● CPU Central Processing Unit ● D2D Device to Device ● DAS Distributed Antenna System ●DC Direct current ● DIMM Dual In-line Memory Module ● DRB Data Radio Bearer ● DSP Digital Signal Processor ● DVD Digital Video Disc ● EEPROM Electrically Erasable Programmable Read-Only Memory ● eMTC Advanced Machine Type Communication ● eNB Enhanced or evolved Node B ● EPC Evolved Packet Core ● EPROM Erasable Programmable Read Only Memory ● E-SMLC Evolved Serving Mobile Location Center ● E-UTRA Evolved Universal Terrestrial Radio Access ● gNB New Radio Base Station ● GPS Global Positioning System ● GSM Global System for Mobile Communications ● HDDS Holographic Digital Data Storage Device ● HD-DVD High Density Digital Video Disc ● HPLMN Home Public Land Mobile Network ● HSS Home Subscriber Server ID Identifier ● I / O Input / Output ● IoT Internet of Things ● IP Internet Protocol ● LAN Local Area Network ● LEE Laptop Built-in Devices ● LME laptop-equipped devices ● LTE Long Term Evolution ● M2M Machine to Machine ● MANO Management and Orchestration ● MCE Multi-cell / multicast coordination entity ● MDT minimization and drive test ● MIMO Multiple Input Multiple Output ● MM Mobility Management ● MME Mobility Management Entity ● MSC Mobile Switching Center ● MSR Multi Standard Radio ● MTC Machine Type Communication ● NAS non-access layer ● NB Node B ● NB-IoT Narrowband Internet of Things ● NFV Network Function Virtualization ●NG next generation ● NG-RAN Next Generation Radio Access Network ● NIC Network Interface Controller ● NR New Radio ● NSI Network Slice Instance ● NSISF Network slice instance selection function ● NSSAI Network Slice Selection Support Information ● O&M operation & maintenance ● OSS Business Support System ● OTT (Over the Top) ● PDA (Personal Digital Assistant) ● PDU Protocol Data Unit ● PROM Programmable Read-Only Memory ● PSTN Public Switched Telephone Network ● RACH Random Access Channel ● RAID (Redundant Array of Independent Disks) ● RAM Random Access Memory ● RAN Radio Access Network ● RAN2 3GPP Technical Specification Group for Radio Layer 2 and Radio Layer 3: Radio Interface Architecture ● RAT Radio Access Technology ● Release RF Radio Frequency ● RFSP RAT / Frequency Selection Priority ● RNC Radio Network Controller ● ROM Read Only Memory ● RRC Radio Resource Control ● RRH Remote Radio Head ● RRM Radio Resource Management ● RRU Remote Radio Unit ● RUIM Removable User Identity Module ● SA2 3GPP Technical Specification Group for Service and System Aspects: Architecture ● SD slice differentiator ● SDRAM Synchronous Dynamic Random Access Memory ● SIM Subscriber Identity Module - SMF session management function ● SM-NSSAI Session Management Network Slice Selection Assistance Information ● SOC System on Chip ● SON Self-organizing Network ● SONET Synchronous Optical Network ● SST Slice Service Type ● TA Tracking Area TCP Transmission Control Protocol ● TS Technical Specifications UE User Equipment ● UMTS Universal Mobile Telecommunications System ● USB Universal Serial Bus ● UTRAN Universal Terrestrial Radio Access Network ● V2I Vehicle to Infrastructure ● V2V Vehicle to Vehicle ● V2X Vehicle to Everything ● VMM Virtual Machine Monitor VNE Virtual Network Element VNF Virtual Network Function ● VoIP Voice over Internet Protocol ● WAN Wide Area Network ● WCDMA Wideband Code Division Multiple Access ● WD Wireless Devices ● WG Working Group ● WiMax Global Interoperability for Microwave Access ● WLAN Wireless Local Area Network Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are deemed to be within the scope of the concepts disclosed herein.

Claims

1. 1. A Radio Access Network (RAN) node configured to communicate with a User Equipment (UE), the RAN node comprising: A wireless interface; A processing circuit, receiving a message from an access and mobility management in a core network, the message including an index to a RAT / frequency selection priority that is set based on subscription information and a network slice allowed for a user equipment (UE); using the received index for determining a UE-specific cell reselection priority for controlling idle mode camping and / or steering the UE to a preferred frequency layer or radio access type (RAT) according to the allowed network slice for the UE used to set the received index; providing the UE with the UE specific cell reselection priority; and a processing circuit configured to: A RAN node comprising:

2. 2. The RAN node of claim 1, wherein the index into RAT / frequency selection priority is set further based on knowledge of the network slice in which the UE is registered.

3. 2. The RAN node of claim 1, wherein the index into RAT / frequency selection priority is set further based on knowledge of availability of network slices in the RAN.

4. 2. The RAN node of claim 1, wherein the RAN node comprises an enhanced or evolved Node B (eNB) or a new radio base station (gNB).

5. 1. A method implemented in a Radio Access Network (RAN) node, the method comprising: receiving a message from an access and mobility management in a core network, the message including an index to a RAT / frequency selection priority that is set based on subscription information and a network slice allowed for a user equipment (UE); using the received index for determining a UE-specific cell reselection priority for controlling idle mode camping and / or steering the UE to a preferred frequency layer or radio access type (RAT) according to the allowed network slice for the UE used to set the received index; providing the UE with the UE specific cell reselection priority; The method comprising:

6. A method as described in claim 5, wherein the index into RAT / frequency selection priority is set further based on knowledge of the network slice in which the UE is registered.

7. 6. The method of claim 5, wherein the index into RAT / frequency selection priority is set further based on knowledge of availability of network slices in the RAN.

Images