Patent Description:
In wireless communication systems that are standardized by the Third Generation Partnership Project (3GPP) systems, such as New Radio (NR) (also known as "<NUM>") and Long Term Evolution (LTE), when a WD is in IDLE mode and/or INACTIVE mode, the WD is still associated with a cell, even though not actively communicating with that cell. The WD is said to be "camping" on the cell.

As the WD moves around, the WD may need to change which cell it is camping on. Such mobility is controlled by the network nodes using thresholds and priorities which the network nodes provide to the WD. The network nodes can provide such thresholds and priorities, hereinafter referred to as parameters, to the WD. These parameters might indicate, for example, how much better another cell must be than the current cell in order for the WD to move to that other cell. Also, the network node provides priorities to the WD which indicate, for example, which frequency the WD shall prefer to be camping on.

The network node can provide parameters to the WD via broadcast signaling or by dedicated signaling. The WD applies the broadcast parameters, unless the WD has been provided with dedicated priorities, or in other words: the WD may prioritize dedicated signaling over broadcast signaling.

One motivation for dedicated signaling is that the network, via network nodes, can load balance; the network can influence how many WDs prioritize a certain frequency, hence, distributing the WDs among different cells. Note that even though the WD is not generating any traffic when the WD is in IDLE/INACTIVE mode, the WDs will cause a load when the WD requests access to enter CONNECTED mode. So, if all WDs camp on the same cell carrier or frequency, they would all end up connecting to that cell when they eventually enter CONNECTED mode. This may cause an overload situation. Hence the network can make sure, using dedicated priorities, that some WDs camp on a first frequency, while other WDs camp on another frequency.

Some features may only be supported by certain cells, e.g., network nodes, in the network. 3GPP studies have considered that certain network slices are only supported on certain frequencies, or at least, that operators may prefer traffic associated with a certain slice on a certain frequency. For example, suppose an operator in a certain region wants to offer connectivity to a certain slice S1 only on frequency F1, whereas services on another slice S2 can be served on any frequency or on frequency F2. This situation may not be homogeneous throughout the network, so in one area it may be as described, whereas in another area, e.g., indoor, an operator may have different preferences and may want to serve slice S2 preferably with another frequency, e.g., F3. Currently, there is no easy way of signaling to the WD that dedicated priorities can change throughout a core network (CN) registration area. Nor is there any way of signaling to the WD that different slices may be associated with different frequency priorities. For example, if a WD is registered to two different slices and these two different slices are such that the operator prefers them to be served on different frequencies, there is currently no way of signaling this to the WD. <CIT> discloses a method performed by a radio network node for handling mobility of a wireless device in a communication network, which communication network comprises partitioned sets of functionalities wherein each set of functionalities belongs to a network slice, and wherein a set of functionalities is separated from other sets of functionalities out of a total set of functionalities in the communication network.

<CIT>discloses a wireless communication method comprising: after a first network device obtains a policy set identifier (PSI) parameter of a terminal device, the first network device determines whether to update policy information of the terminal device.

<CIT>discloses a core network function for determining information for RAT and/or frequency selection based on knowledge of network slices and providing that information to a RAN node, which may provide that information to a UE.

There is a need for a solution that can provide information to the WD such that idle or inactive mode mobility (cell selection and reselection) can be done in such a way that a WD follows frequency priorities that are valid for certain specific cells, areas and slices.

Some embodiments advantageously provide methods, network nodes and wireless devices for network guided wireless device (WD) cell reselection. Aspects of the invention are set out in the independent claims appended hereto.

A method in a WD for receiving and maintaining IDLE/INACTIVE mode mobility parameters is provided, where the WD may be:.

A method in a network node for maintaining IDLE/INACTIVE mode mobility parameters is provided, where the network may be:.

The certain set of parameters are typically frequency priorities that are associated with a specific WD class or a specific slice.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to network guided wireless device (WD) cell reselection. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

As used herein, the term "legacy signaling", "legacy fields" and similar terms refers to signaling and fields which are defined in an existing version of a specification. For example, if a field is defined in a version <NUM> of the New Radio/Long Term Evolution (NR/LTE) specifications, then a field which is defined in 3GPP Release <NUM> (Rel-<NUM>) of those specifications would be considered a legacy field and signaling using this field would be considered legacy signaling.

Embodiments provide network guided wireless device (WD) cell reselection. According to one aspect, a network broadcasts multiple sets of parameters for WDs to use when performing mobility among cells when the WDs are in IDLE mode and/or INACTIVE mode. In current NR/LTE specifications, the network sends a single set of such parameters as described above. These parameters include priorities. A WD which is in IDLE mode or INACTIVE mode applies these priorities to determine on which cell and/or frequency the WD is to camp. However, in embodiments described below, the network node would provide multiple sets of parameters and an indication used by the WD to select and apply a particular one of the sets of parameters depending on certain conditions as explained below.

The solution enables specific WD groups to be associated with an "identity", e.g., a class or a slice association and with this classification or association be able to control what different frequency priority indications the WD is using for different slices in different parts of the network. Thus, different groups of WDs may be configured to apply different parameters for IDLE/INACTIVE mode mobility. In other words, different parameters may be applied to different groups of WDs based on different criteria determined by the network. In particular, a WD may not necessarily be of a certain category, or a certain type, but it may temporarily be registered to a certain slice and from that registration, the WD may associate different parameter sets to certain slices and to the WD's idle mode mobility procedure.

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The core network node <NUM> may have an operations, administration and maintenance (OAM) node <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

A network node <NUM> may be configured to include an index mapper <NUM> which is configured to map an index to a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one priority used to configure the WD to select one of a network slice, frequency and service. The network node <NUM> may be configured to select an index indicating a set of parameters of that include at least one priority, the selecting being based at least in part on one of a registered slice and a service. A wireless device <NUM> may be configured to include a selector <NUM> which is configured to select a set of cell reselection parameters associated with a network slice or service based on the registered slices. The WD <NUM> may be configured to select a frequency priority from the set of parameters indicated by the obtained indication, the obtained indication corresponding to a prioritized slice.

The host application <NUM> may be operable to provide a service to a remote user, such as a WD <NUM> connecting via an OTT connection <NUM> terminating at the WD <NUM> and the host computer <NUM>. The "user data" may be data and information described herein as implementing the described functionality. In one embodiment, the host computer <NUM> may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry <NUM> of the host computer <NUM> may enable the host computer <NUM> to observe, monitor, control, transmit to and/or receive from the network node <NUM> and or the wireless device <NUM>.

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include index mapper <NUM> which is configured to map an index to a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one priority used to configure the WD to select one of a network slice, frequency and service. The processing circuitry may be configured to select an index indicating a set of parameters of that include at least one priority, the selecting being based at least in part on one of a registered slice and a service.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include selector <NUM> which is configured to select one of a network slice, frequency and service, based at least in part on a priority included in the set of parameters. The processing circuitry <NUM> may be configured to select a frequency priority from the set of parameters indicated by the obtained indication, the obtained indication corresponding to a prioritized slice.

Although <FIG> and <FIG> show various "units" such as index mapper <NUM> and selector <NUM> as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG> and <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S100). In an optional substep of the first step, the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM> (Block S102). In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S104). In an optional third step, the network node <NUM> transmits to the WD <NUM> the user data which was carried in the transmission that the host computer <NUM> initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD <NUM> executes a client application, such as, for example, the client application <NUM>, associated with the host application <NUM> executed by the host computer <NUM> (Block S108).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S1 <NUM>). In an optional substep (not shown) the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM>. In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S112). In an optional third step, the WD <NUM> receives the user data carried in the transmission (Block S114).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, the WD <NUM> receives input data provided by the host computer <NUM> (Block S116). In an optional substep of the first step, the WD <NUM> executes the client application <NUM>, which provides the user data in reaction to the received input data provided by the host computer <NUM> (Block S118). Additionally or alternatively, in an optional second step, the WD <NUM> provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application <NUM> (Block S122). In providing the user data, the executed client application <NUM> may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD <NUM> may initiate, in an optional third substep, transmission of the user data to the host computer <NUM> (Block S124). In a fourth step of the method, the host computer <NUM> receives the user data transmitted from the WD <NUM>, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node <NUM> receives user data from the WD <NUM> (Block S128). In an optional second step, the network node <NUM> initiates transmission of the received user data to the host computer <NUM> (Block S130). In a third step, the host computer <NUM> receives the user data carried in the transmission initiated by the network node <NUM> (Block S132).

<FIG> is a flowchart of an exemplary process in a network node <NUM> for network guided wireless device (WD) cell reselection. One or more blocks described herein may be performed by one or more elements of network node <NUM> such as by one or more of processing circuitry <NUM> (including the index mapper <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Network node <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to transmit to the WD, an index indicating a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one priority, the index used to configure the WD to select a frequency priority based at least in part on the index (Block S <NUM>).

<FIG> is a flowchart of an exemplary process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device <NUM> such as by one or more of processing circuitry <NUM> (including the selector <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Wireless device <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> is configured to obtain an indication of a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one priority, the index used to configure the WD to select a frequency priority based at least in part on the index (Block S136). The process also includes selecting one of a network slice, frequency and service, based at least in part on a threshold included in the set of parameters (Block S138).

<FIG> is a flowchart of another example process for network guided WD cell reselection. One or more blocks described herein may be performed by one or more elements of network node <NUM> such as by one or more of processing circuitry <NUM> (including the index mapper <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Network node <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to select an index indicating a set of parameters of a plurality of sets of parameters, a set of parameters including at least one priority, the selecting being based at least in part on one of a registered slice and a service, the index usable to configure at least one WD of a first group of WDs to select a frequency priority based at least in part on the selected index (Block S140). The process also includes transmitting the selected index to the at least one WD of the first group of WDs (Block S142).

<FIG> is a flowchart of another example process in a WD for network guided WD cell reselection. One or more blocks described herein may be performed by one or more elements of wireless device <NUM> such as by one or more of processing circuitry <NUM> (including the selector <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Wireless device <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> is configured to obtain an indication of a set of parameters of a plurality of sets of parameters, a set of parameters including at least one index and at least one frequency priority (Block S144). The process further includes selecting a frequency priority from the set of parameters indicated by the obtained indication, the obtained indication corresponding to a prioritized slice (Block S146).

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for network guided wireless device (WD) cell reselection.

As mentioned above, the network node <NUM> may configure the WD <NUM> with multiple sets of parameters, and may subsequently indicate a particular set to be applied by the WD <NUM>. Different sets of parameters may be identified by a certain identifier (in the example ASN. <NUM> implementation, this is provided as WDCategoryIndex). For example, an index which may be an integer value may be signaled by the network node <NUM> to the WD <NUM>. Different sets of parameters may be identified by a new field or an existing field.

If the signaling supports multiple additional (i.e., in addition to the legacy/known parameters) sets of parameters, the additional sets may be provided in a list. In this case, an explicit identifier may not be assigned to the to the sets in the list. Instead, a set may be indicated implicitly based on where in the list the set appears. For example, the first set in the list may be associated with an index <NUM> (or <NUM>), the second with an index <NUM> (or <NUM>), and so on. For example, parameters in existing fields may be associated with an index <NUM> (or <NUM>).

One set of parameters may be considered to be a default set of parameters. The default parameters may be those parameters sent in existing signaling.

Below is an example showing how multiple sets can be implemented in 3GPP Technical Standard (TS) <NUM> v15. The changes to existing code are shown with underlined, bold text. Some irrelevant parts of existing code are omitted. A similar set of changes is applicable for system information block <NUM> (SIB4), inter-frequency reselection parameters and SIBS, and inter-radio access technology (RAT) reselection parameters.

SIB2 contains cell re-selection information common for intra-frequency, inter-frequency and/or inter-RAT cell re-selection, (i.e., applicable for more than one type of cell re-selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighboring cell related information. <IMG>
<IMG>
<IMG>
<IMG>.

As an extension to the above, in one embodiment, the network does not broadcast WDCategoryIndex, but rather, associates CellReselectionPriority indications with different slices or services. Thus, instead of considering the type of WD <NUM> and WD <NUM> capabilities, the frequency priority that is valid for a WD <NUM> at a certain point in time is steered by what slice a WD <NUM> is registered to, or alternatively, what service a WD <NUM> wants to utilize.

An example of such a broadcast is provided below:
<IMG>
<IMG>
<IMG>
<IMG>
<IMG>.

Another alternative to an addition would be to add an index not to a slice, but to a service instead:
<IMG>.

Thus, with the coding set forth above, it is possible to broadcast different frequency priorities dependent on different services or different slices. A WD <NUM> can then, independent of WD <NUM> category, select a single frequency priority that is applicable for a specific service.

In some situations, the network, such as via network node <NUM>, may broadcast both WD <NUM> category priorities, WD <NUM> slice priorities and WD <NUM> service priorities. In such situations, a WD <NUM> may determine if cellReselectionPriorities are different, and if so, which to follow. According to one aspect, the frequencyPriorities that relate to wireless device category or wireless device type have a highest priority. Priorities related to a slice may have a second highest priority and priorities related to service may have a third highest priority. In other exemplary embodiments, the service takes precedence.

In some embodiments, the network node <NUM> configures a WD <NUM> to use a particular set, among multiple sets, of cell (re)selection parameters the WD <NUM> is to consider. This may be accomplished by sending from the network node <NUM> to the WD <NUM> a parameter set indication.

The parameter set indication may be indicated with dedicated signaling from the network to the WD <NUM>. For example, the parameter set indication, signaled in a message which is used to move the WD <NUM> from CONNECTED mode to an IDLE/INACTIVE mode, such as an RRCRelease-message, may be used to send the parameter set indication.

Below is an example showing how such an indication can be implemented in 3GPP TS <NUM> v15. The change is shown with underlined and bold text. For this example, irrelevant parts of existing code are omitted.

The RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection. <IMG>
<IMG>
<IMG>.

In some embodiments, the cellReselectionParameterSetIndex can also be extended to include indications that point toward specific slices or services, as in the example below. In this example, in the RRCRelease message, the network indicates the cellReselectionParameterSetIndex associated to a given slice. The network could provide different cellReselectionParameterSetIndex for different slice as part of the cellReselectionSliceParameterSet list. The network could provide the same cellReselectionParameterSetIndex for more than one slice. <IMG>
<IMG>
<IMG>.

According to the above example, the next generation radio access network (NG-RAN) node would have information about the registered slices from the access and mobility management function (AMF), communicated, e.g., in the initial context setup request message. In some embodiments, the AMF includes this information at the time of initial context setup request message and in some other embodiments, the radio access network (RAN) node can request this information from the core network on an as-needed basis. In some other embodiments, the RAN node can receive this information from the operation, administration and maintenance (OAM) function.

The indication could be an integer value and point to the index of parameters. See above where it is described how the network node <NUM> may indicate a certain set of parameters by an index.

If the WD <NUM> has not received any indication from the network, such as via network node <NUM>, regarding which parameter set the WD <NUM> is to apply, the WD <NUM> may apply a default set of parameters. The default set of parameters may be indicated as a first or any predetermined index e.g., indicating a slice list, service list or WD <NUM> category/type list.

The parameter set indication may indicate or include multiple parameter sets. The network, such as via network node <NUM>, may indicate to the WD <NUM> that the WD <NUM> is to apply either parameter set <NUM> or parameter set <NUM>, for example. The WD <NUM> may be configured to apply any of parameter set <NUM> or parameter set <NUM>, and the WD <NUM> may select one of these if they are found. In some embodiments, the WD <NUM> could make such a selection based on what slice is prioritized in idle or inactive mode selection. For example, a WD <NUM> may apply idle/inactive mode frequency priority parameters that relate to a slice or a service that is considered more time-critical than another service or slice. For example, a WD <NUM> may select ultrareliable low latency communication (URLLC)-slice-related frequency priorities instead of mobile broad band (MBB)-slice-related frequency priorities in situations when it is registered to both such slices. This selection may occur when use of the URLLC slice is more time-critical.

In some embodiments, a WD <NUM> may choose to prioritize the MBB slice and follow the frequency priorities of that slice, since the use of MBB may be <NUM> times more frequent than use of URLLC. Also, use of the URLLC slice may be associated with a controlled startup and is not time-critical in an initial step. There could be various aspects that determine what slice, frequency, and/or service to prioritize when the WD <NUM> has a choice.

In some embodiments, the parameter set indications are associated with a priority. For example, a parameter set <NUM> may be given higher priority than parameter set <NUM>. Then, the WD <NUM> will apply parameter set <NUM> if available, otherwise the WD <NUM> will apply parameter set <NUM>. If none of the indicated parameter sets are found by the WD <NUM>, the WD <NUM> may revert to selecting an alternative parameter set.

If the WD <NUM> has received a parameter set indication but the corresponding parameter set is not detected, the WD <NUM> may apply a backup parameter set. The backup parameter set may be selected to be, for example:.

In one embodiment, the WD <NUM> may discard the parameter set indication upon certain events, examples of which may include:.

When the WD <NUM> is said to "discard" the parameter set indication, the WD <NUM> may actually discard the value (e.g., by removing it from a memory), or it can consider the value no longer valid or applicable.

Based on the above methods, the network, such as via network node <NUM>, can control which parameter set a certain WD <NUM> applies, considering one or more of the following:.

When the WD <NUM> is registered to more than one slice, or when the WD <NUM> is registered to the network in such a way that a selection of different services may become relevant for access, then according to one aspect, the WD <NUM> can determine which way it should prioritize a slice, frequency, and/or service. Based on the above methods, the network node <NUM> can control which parameter set a certain WD <NUM> is to apply. The network, such as via network node <NUM>, may select which parameter set a certain WD <NUM> is to apply considering one or more of the following:.

In one embodiment, a central node of the network, (e.g., an OAM network node) determines the indices used for the different parameter sets. This may be seen as the central node that is coordinating the indices to use for the different parameter sets. The result of such coordination is then indicated to other network nodes <NUM>, e.g., gNBs, in the network. The coordination may be such that all nodes in a certain area (e.g., a set of cells, set of Tracking Areas, set of RAN Areas, etc.) use the same index for a certain set of parameters. Alternatively, or in addition, the coordination may be such that a certain index is used for the particular type of devices.

From a slicing perspective, some embodiments offer the possibility to provide a frequency prioritization in a registration area where an operator has different preferences for the use of a specific slice.

In the example architecture of <FIG>, the network node <NUM> (NN), gNB1 broadcasts a certain set of frequencies for use of slice <NUM>, whereas another cell broadcasts another set of frequencies for use of slice <NUM>. If a WD <NUM> is coming from an area where f3 was used for slice <NUM>, the WD <NUM> would switch to f1 if it was entering an area served by gNB1, whereas it would switch to f2 if it was entering an area served by the network node <NUM> (NN), gNB2. This would be possible by associating an index with the slice to which the WD <NUM> is registered, and by broadcasting frequency priorities that are valid in a certain area for this index. The index can, as described above, map either to a slice or to a service.

In one explicit example, an OAM network node determines that parameter sets for EN-DC will have index <NUM>, and that is indicated to network nodes (gNBs) such that all network nodes (gNBs) use the same index for their EN-DC parameters, if any. The OAM network node may only provide such indication to network nodes which support a certain feature, in some embodiments. For example, if there is a parameter set for a feature X, then the central node, e.g., the OAM network node, may only indicate to the other network nodes (gNBs) which actually support feature X which index the parameters for feature X should use.

In some embodiments, the coordination between configurations and indices is done in a distributed manner between network nodes <NUM>, such as gNBs. The source network node indicates to other network nodes s in the tracking area how the indices are used when releasing the WD <NUM>.

<FIG> is a flowchart of an exemplary process performed in the WD <NUM> according to some embodiments. A WD <NUM> is registering to two slices (Block S210). It may, in a release message, receive two index values, one for slice <NUM> and one for slice <NUM>. These index values may be associated with broadcast system information (with the same index) and from this, the WD <NUM> may be able to know and follow varying frequency priorities in different cells it may reselect (Block S230). As the WD <NUM> cannot follow different priorities at the same time, there may be rules for how the WD <NUM> should select one set. In the example of <FIG>, in Block S240, the WD <NUM> prioritizes slice <NUM>. In Block S250, the WD <NUM> reselects according to frequency priorities for slice <NUM>. In Block S260, slice <NUM> triggers an activity and the WD <NUM> would select access on the frequency indicated by the frequency priorities for slice <NUM>.

When a WD <NUM> is reselecting another cell, it may read the information on frequency priority that is sent from that cell simply by following the index indication provided by the network in Block S220.

<FIG> is a flowchart of an exemplary process performed in the network node <NUM>, such as a gNB, according to an example embodiment. The network node <NUM> (e.g., gNB) broadcasts parameters according to what slices are supported in the cell. In this example, index <NUM> and index <NUM> are given (Block S310). These two indexes map to two different slices, slice <NUM> and slice <NUM>. It can also be that index <NUM> maps to several different slices and index <NUM> maps to other slices, or only one slice. In some embodiments, the network node <NUM> receives information indicating to which slices the WD <NUM> is registered (Block S320). This may make it possible for the network node <NUM> to transmit information to the WD <NUM> about frequency priorities it should follow for the different slices. This information is conveyed to the WD <NUM> in a release message (Block S330).

Some aspects may be implemented in the radio resource control (RRC) protocol of NR. Hence some parts may be implemented in a cloud, i.e., in one or more locations accessible via the Internet.

According to one aspect, a network node <NUM> configured to communicate with a plurality of wireless devices (WD) is provided. The network node <NUM> includes processing circuitry <NUM> configured to select an index indicating a set of parameters of a plurality of sets of parameters, a set of parameters including at least one priority, the selecting being based at least in part on one of a registered slice and a service, the index usable to configure at least one WD <NUM> of a first group of WDs <NUM> to select a frequency priority based at least in part on the selected index. The network node <NUM> includes a radio interface <NUM> in communication with the processing circuitry <NUM>, the radio interface <NUM> configured to transmit the selected index to the at least one WD <NUM> of the first group of WDs <NUM>.

According to this aspect, in some embodiments, the radio interface <NUM> is further configured to broadcast the plurality of sets of parameters to multiple wireless devices. In some embodiments, the radio interface is configured to unicast the plurality of sets of parameters to a particular one of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, each set of parameters of the plurality of sets of parameters corresponds to a different one of a registered slice or a service. In some embodiments, one set of parameters of the plurality of sets of parameters is a default set of parameters. In some embodiments, the processing circuitry <NUM> is further configured to select multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters; and the radio interface is further configured to transmit the selected multiple indices to the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, a priority in a set of parameters directs the at least one WD <NUM> of the first group of WDs <NUM> to prioritize one slice or service over another slice or service. In some embodiments, the selecting is further based on a capability of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, the selecting is further based on a mobility state of a particular one of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, the processing circuitry <NUM> is further configured to select multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters; and the radio interface is further configured to transmit each selected one of the multiple indices to a different group of WDs <NUM>.

According to another aspect, a method in a network node <NUM> configured to communicate with a plurality of wireless devices (WD) is provided. The method includes selecting, via the processing circuitry <NUM>. an index indicating a set of parameters of a plurality of sets of parameters, a set of parameters including at least one priority, the selecting being based at least in part on one of a registered slice and a service, the index usable to configure at least one WD <NUM> of a first group of WDs <NUM> to select a frequency priority based at least in part on the selected index; and transmitting, via the radio interface <NUM> the selected index to the at least one WD <NUM> of the first group of WDs <NUM>.

According to this aspect, in some embodiments, the method also includes broadcasting via the radio interface <NUM> the plurality of sets of parameters to multiple wireless devices. In some embodiments, the method includes unicasting the plurality of sets of parameters to a particular one of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, each set of parameters of the plurality of sets of parameters corresponds to a different one of a registered slice or a service. In some embodiments, one set of parameters of the plurality of sets of parameters is a default set of parameters. In some embodiments, the method includes selecting, via the processing circuitry <NUM>, multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters; and transmitting, via the radio interface <NUM>, the selected multiple indices to the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, a priority in a set of parameters directs the at least one WD <NUM> of the first group of WDs <NUM> to prioritize one slice or service over another slice or service. In some embodiments, the selecting is further based on a capability of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, the selecting is further based on a mobility state of a particular one of the at least one WD <NUM> of the first group of WDs <NUM>. In some embodiments, the method includes selecting, via the processing circuitry <NUM> multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters; and transmitting, via the radio interface <NUM>, each selected one of the multiple indices to a different group of WDs <NUM>.

According to yet another aspect, a WD <NUM> is configured to communicate with a network node <NUM>. The WD <NUM> includes processing circuitry <NUM> configured to: obtain an indication of a set of parameters of a plurality of sets of parameters, a set of parameters including at least one index and at least one frequency priority; and select a frequency priority from the set of parameters indicated by the obtained indication, the obtained indication corresponding to a prioritized slice.

According to this aspect, in some embodiments, the indication is obtained from the network node <NUM>. In some embodiments, when no indication is obtained from the network node <NUM>, the indication is one of a default indication and a random indication obtained from a memory of the WD <NUM>. In some embodiments, the processing circuitry <NUM> is further configured to register the WD <NUM> to the corresponding prioritized slice. In some embodiments, the processing circuitry <NUM> is further configured to access a cell according to the selected frequency priority when reinitiating communication associated with the corresponding prioritized slice. In some embodiments, the processing circuitry <NUM> is further configured to: obtain multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters, and select a set of parameters among the sets of parameters indicated by the multiple indices, the selecting being based at least in part on a comparison of frequency priorities of different sets of parameters indicated by the multiple indices. In some embodiments, the processing circuitry <NUM> is further configured to discard, ignore or deem as invalid, the obtained indication upon an occurrence of at least one of: the WD <NUM> lacking a capability for the prioritized slice; a timer expiring; the indicated set of parameters being unavailable at the WD <NUM>; the WD <NUM> changing to an IDLE state; the WD <NUM> changing a mobility state; and the WD <NUM> deregistering from the prioritized slice. In some embodiments, the WD <NUM> further includes a radio interface <NUM> configured to receive the obtained indication from the network node <NUM> on a broadcast channel. In some embodiments, the WD <NUM> further includes a radio interface <NUM> configured to receive the plurality of sets of parameters from the network node <NUM>. In some embodiments, the obtained indication is received from the network node <NUM> in an RRCRelease message usable to move the WD <NUM> from one state to another state.

According to another embodiments, a method in a wireless device <NUM> includes: obtaining an indication of a set of parameters of a plurality of sets of parameters, a set of parameters including at least one index and at least one frequency priority; and selecting a frequency priority from the set of parameters indicated by the obtained indication, the obtained indication corresponding to a prioritized slice.

According to this aspect, in some embodiments, the indication is obtained from the network node <NUM>. In some embodiments, when no indication is obtained from the network node <NUM>, the indication is one of a default indication and a random indication obtained from a memory <NUM> of the WD <NUM>. In some embodiments, the method also includes registering the WD <NUM> to the corresponding prioritized slice. In some embodiments, the method also includes accessing a cell according to the selected frequency priority when reinitiating communication associated with the corresponding prioritized slice. In some embodiments, the method further includes obtaining multiple indices, each index of the multiple indices indicating a different set of parameters of the plurality of sets of parameters, and selecting a set of parameters among the sets of parameters indicated by the multiple indices, the selecting being based at least in part on a comparison of frequency priorities of different sets of parameters indicated by the multiple indices. According to this aspect, in some embodiments, the method also includes, via the processing circuitry <NUM>, discarding, ignoring or deeming as invalid, the obtained indication upon an occurrence of at least one of: the WD <NUM> lacking a capability for the prioritized slice; a timer expiring; the indicated set of parameters being unavailable at the WD <NUM>; the WD <NUM> changing to an IDLE state; the WD <NUM> changing a mobility state; and the WD <NUM> deregistering from the prioritized slice. In some embodiments, the method also includes receiving the via the radio interface <NUM>, obtained indication from the network node <NUM> on a broadcast channel. In some embodiments, the method also includes receiving, via the radio interface <NUM>, the plurality of sets of parameters from the network node <NUM>. In some embodiments, the obtained indication is received from the network node <NUM> in an RRCRelease message usable to move the WD <NUM> from one state to another state.

According to one aspect, a network node <NUM> is configured to communicate with a wireless device (WD). The network node <NUM> includes a radio interface <NUM> and/or processing circuitry <NUM> configured to transmit to the WD <NUM>, an index indicating a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one threshold and at least one priority, the index used to configure the WD <NUM> to select a frequency priority based at least in part on the index.

According to this aspect, in some embodiments, the index is one of a set of indices received from a central node in communication with the network node <NUM> and other network nodes. In some embodiments, the network node <NUM> selects the index based on a registered slice or service.

According to another aspect, a method implemented in a network node <NUM> in communication with a wireless device, WD <NUM>, includes transmitting to the WD <NUM>, an index indicating a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one threshold and at least one priority, the index used to configure the WD <NUM> to select a frequency priority based at least in part on the index.

According to yet another aspect, a WD <NUM> configured to communicate with a network node <NUM>, includes a radio interface <NUM> and/or processing circuitry <NUM> configured to: obtain an indication of a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one threshold and at least one priority, the index used to configure the WD <NUM> to select a frequency priority based at least in part on the index. ; and select one of a network slice, frequency and service, based at least in part on a threshold included in the set of parameters.

According to this aspect, in some embodiments, the indication is obtained from the network node <NUM>. In some embodiments, when no indication is obtained from the network node <NUM>, the WD <NUM> obtains a default indication of a set of parameters from a memory of the WD <NUM>. In some embodiments, the indication indicates more than one set from which the WD <NUM> chooses based at least in part on whether an indicated set is stored in a memory of the WD <NUM>.

According to another aspect, a method implemented in a wireless device includes obtaining an indication of a set of parameters of a plurality of sets of parameters, the parameters in a set including at least one threshold and at least one priority, the index used to configure the WD <NUM> to select a frequency priority based at least in part on the index. The method further includes selecting one of a network slice, frequency and service, based at least in part on a threshold included in the set of parameters.

Claim 1:
A network node (<NUM>) configured to communicate with a plurality of wireless devices, WD (<NUM>), the network node (<NUM>) comprising:
processing circuitry configured to select an index indicating a set of parameters of a plurality of sets of parameters, a set of parameters including at least one frequency priority, the selecting being based at least in part on one of a registered slice and a service, the index usable to configure at least one WD (<NUM>) of a first group of WDs (<NUM>) to select a frequency priority based at least in part on the selected index; and
a radio interface in communication with the processing circuitry, the radio interface configured to transmit the selected index to the at least one WD (<NUM>) of the first group of WDs (<NUM>).