Patent Description:
As a UE moves to different geographical locations, it is important to select a given cell to achieve a target communication performance. Some cell-selection procedures consider radio-frequency (RF) carrier priorities, cell cite priorities, quality of a radio link, signal strength, and so forth. Sometimes a network provides cell-selection information to the UE to bias or increase a likelihood of a given cell or type of cell being selected by the user equipment. In some situations, however, this information may cause the UE to select a sub-optimal cell.

3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state (Release <NUM>) specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state.

<NPL> discusses solutions which separate the "(cell selection/reselection) States and state transitions" and RRC state transitions.

<CIT> describes a user equipment configured to operate in an E-UTRAN network.

Techniques and apparatuses are described that enable releasing information to improve cell selection in different resource control states. The techniques and devices described are designed to improve communication performance by triggering the release of dedicated cell-selection information, which may not be appropriate as a user equipment (UE) moves to different geographical locations and transitions to different resource control states. By releasing the dedicated cell-selection information, the UE may be able to select an optimal cell for achieving a target communication performance in different resource control states.

Aspects described below include a UE with a radio-frequency transceiver. The UE also includes a processor and memory system configured to perform any of the methods described.

Apparatuses of and techniques for releasing information to improve cell selection in different resource control states are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:.

This document describes techniques and devices enabling the release of information to improve cell selection in different resource control states. In some situations, a user equipment (UE) may be provided dedicated cell-selection information, which biases or increases a likelihood of a given cell or type of cell being selected by the UE. As the UE moves to different geographical locations, the dedicated cell-selection information may cause the UE to select a sub-optimal cell that does not achieve a target performance. The sub-optimal cell, for example, may lack signal strength, may not utilize a desired radio frequency, and so forth. This dedicated cell-selection information may also be retained as the UE transitions to different resource control states, such as from an inactive state to an idle state. Accordingly, the dedicated cell-selection information may not be appropriately configured for the current state.

The techniques and devices described are designed to improve communication performance by triggering the UE to release the dedicated cell-selection information. The release of the dedicated cell-selection information can occur while the UE is in an inactive state or an idle state. By releasing the dedicated cell-selection information, the UE may be able to select an optimal cell for achieving a target communication performance in different resource control states.

<FIG> illustrates an example environment <NUM> in which parallel beamforming training with coordinated base stations can be implemented. The environment <NUM> includes multiple UEs <NUM>, illustrated as UE <NUM>, UE <NUM>, and UE <NUM>. Each UE <NUM> communicates with one or more base stations <NUM> (illustrated as base stations <NUM>, <NUM>, <NUM>, and <NUM>) through one or more wireless communication links <NUM> (wireless link <NUM>), illustrated as wireless links <NUM> and <NUM>. Although illustrated as a smartphone, the UE <NUM> can be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, a cellular phone, a gaming device, a navigation device, a media device, a laptop computer, a desktop computer, a tablet computer, a smart appliance, a vehicle-based communication system, and the like. The base station <NUM> (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Evolved Node B, ng-eNB, Next Generation Node B, gNode B, gNB, or the like) can be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof.

The base stations <NUM> communicate with the UE <NUM> using the wireless links <NUM> and <NUM>, which may be implemented as any suitable type of wireless link. The wireless link <NUM> and <NUM> can include a downlink of data and control information communicated from the base stations <NUM> to the UE <NUM>, an uplink of other data and control information communicated from the UE <NUM> to the base stations <NUM>, or both. The wireless links <NUM> include one or more wireless links or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Enhanced Long-Term Evolution (eLTE), Fifth-Generation New Radio (5GNR), Fourth-Generation (<NUM>) standard, and so forth. Multiple wireless links <NUM> can be aggregated using carrier aggregation to provide a higher data rate for the UE <NUM>. Multiple wireless links <NUM> from multiple base stations <NUM> can be configured for Coordinated Multipoint (CoMP) communication with the UE <NUM>.

The base stations <NUM> are collectively a Radio Access Network <NUM> (RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, <NUM> NR RAN or NR RAN) that each use a Radio Access Technology (RAT). The RANs <NUM> include a NR RAN <NUM> and an E-UTRAN <NUM>. In <FIG>, core networks <NUM> include a Fifth-Generation Core (5GC) network <NUM> (5GC <NUM>) and an Evolved Packet Core (EPC) network <NUM> (EPC <NUM>), which are different types of core networks. The base stations <NUM> and <NUM> in the NR RAN <NUM> connect to the 5GC <NUM>. The base stations <NUM> and <NUM> in the E-UTRAN <NUM> connect to the EPC <NUM>. Optionally or additionally, the base station <NUM> connects to both the 5GC <NUM> and EPC <NUM> networks.

The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to the 5GC <NUM> using an NG2 interface for control-plane signaling and using an NG3 interface for user-plane data communications. The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to the EPC <NUM> using an S1 interface for control-plane signaling and user-plane data communications. If the base station <NUM> connects to both the 5GC <NUM> and the EPC <NUM>, the base station <NUM> can connect to the 5GC <NUM> using an NG2 interface for control-plane signaling and using an NG3 interface for user-plane data communications, at <NUM>. In addition to connections to core networks <NUM>, the base stations <NUM> can communicate with each other. The base stations <NUM> and <NUM> communicate using an Xn interface at <NUM>, for instance. The base stations <NUM> and <NUM> communicate using an X2 interface at <NUM>. The base stations <NUM> and <NUM> can communicate using an Xn interface at <NUM> to execute a handover procedure.

The 5GC <NUM> includes an Access and Mobility Management Function <NUM> (AMF <NUM>) that provides control-plane functions such as registration and authentication of multiple UE <NUM>, authorization, mobility management, or the like in the 5GNR network. The EPC <NUM> includes a Mobility Management Entity <NUM> (MME <NUM>) that provides control-plane functions such as registration and authentication of multiple UE <NUM>, authorization, mobility management, or the like in the E-UTRAN network. The AMF <NUM> and the MME <NUM> communicate with the base stations <NUM> in the RANs <NUM> and also communicate with multiple UE <NUM> through the base stations <NUM>. Components of the UE <NUM> are further described with respect to <FIG>.

<FIG> illustrates an example device diagram <NUM> of the UE <NUM>. The UE <NUM> can include additional functions and interfaces that are omitted from <FIG> for the sake of clarity. The UE <NUM> includes antennas <NUM>, a radio-frequency (RF) front end <NUM> (RF front end <NUM>), an LTE transceiver <NUM>, and a <NUM> NR transceiver <NUM> for communicating with one or more base stations <NUM> in the RAN <NUM>. The RF front end <NUM> couples or connects the LTE transceiver <NUM> and the <NUM> NR transceiver <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> can include an array of multiple antennas that are configured similar to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to one or more frequency bands defined by the 3GPP LTE and <NUM> NR communication standards and implemented by the LTE transceiver <NUM> and/or the <NUM> NR transceiver <NUM>.

The UE <NUM> also includes one or more processors <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> can be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media excludes propagating signals and the CRM <NUM> includes any suitable memory or storage device, such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data <NUM> of the UE <NUM>. The device data <NUM> includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the UE <NUM>, which are executable by the processor <NUM> to enable user-plane communication, control-plane signaling, and user interaction with the UE <NUM>.

The CRM <NUM> also includes a resource control module <NUM>. Alternately or additionally, the resource control module <NUM> can be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE <NUM>. The resource control module <NUM> can implement a radio resource control (RRC) layer, as described according to different specifications such as eLTE and <NUM> NR. The resource control module <NUM> configures the LTE transceiver <NUM> or the <NUM> NR transceiver <NUM> for the current resource control state <NUM> and performs the cell-selection procedure. In particular, the resource control module <NUM> configures the UE <NUM> to operate according to a particular resource control state <NUM>.

In general, different resource control states <NUM> have different quantities or types of resources available, which may affect power consumption within the UE <NUM>. Example resource control states <NUM> include a connected (e.g., active) state <NUM> and a disconnected state <NUM>. The disconnected state <NUM> includes an inactive state <NUM> and an idle state <NUM> and generally consumes less power relative to the connected state <NUM>. In the connected state <NUM>, the UE <NUM> actively connects to the base station <NUM>. In the inactive state <NUM>, the UE <NUM> suspends connectivity with the base station <NUM> and retains information that enables connectivity with the base station <NUM> to be quickly re-established. In the idle state <NUM>, the UE <NUM> releases the connection with the base station <NUM>. Some of the resource control states <NUM> may be limited to certain radio-access technologies. For example, the inactive state <NUM> may be supported in eLTE and <NUM> NR, but not in <NUM> or other <NUM> standards. Other resource control states may be common or compatible across multiple RATs, such as the connected state <NUM> or the idle state <NUM>. The resource control module <NUM> can at least partially release information to improve cell selection in different resource control states <NUM>, as further described in <FIG>.

<FIG> is an example environment <NUM> in which the UE <NUM> releases information to improve cell selection in different resource control states. In the example environment <NUM>, the UE <NUM> and the base station <NUM> communicate over the wireless link <NUM> of <FIG>. Different situations can cause the UE <NUM> to transition between different resource control states <NUM>, as described in further detail below. In either the inactive state <NUM> or the idle state <NUM>, the UE <NUM> can perform a cell-selection procedure, which is further described with respect to a map <NUM> shown at the bottom of <FIG>.

The map <NUM> illustrates the UE <NUM> as being physically located between multiple base stations <NUM>, <NUM>, and <NUM> (e.g., cell sites). Consider that the UE <NUM> is in the connected state <NUM> and previously established a connection with the base station <NUM>. The base station <NUM> uses a RAT that supports the inactive state <NUM>, such as eLTE or <NUM> NG. The base station <NUM> can be, for example, a gNB, a ng-eNB connected with 5GC <NUM> as shown in <FIG>, or an eNB connected with 5GC <NUM>.

The base station <NUM> transmits a request message <NUM> to the UE <NUM>, which directs the UE <NUM> to transition from the connected state <NUM> to the inactive state <NUM>. The request message <NUM> can include, for example, a radio resource control (RRC) release message (e.g., an RRCRelease message) according to the eLTE or <NUM> NR standards. The request message <NUM> includes dedicated cell-selection information <NUM>, which influences a cell-selection procedure performed by the UE <NUM>. The cell-selection information <NUM> may include at least one of the following: cell-selection or cell-reselection priority information (e.g., idleModeMobilityControlInfo or cellReselectionPriorities in eLTE or <NUM> NR standards), depriority information (e.g., deprioritisationReq in eLTE or <NUM> NR standards), or cell-redirection information. In some cases, the dedicated cell-selection information <NUM> may also include a timer to indicate a duration (e.g., a given time frame) for which the dedicated cell-selection information <NUM> is to be used by the UE <NUM> for cell-selection procedures. Upon expiration of the timer, the dedicated cell-selection information <NUM> may be released by the UE <NUM>.

As the UE <NUM> moves to a different geographical location while in the inactive state <NUM>, such as towards the base station <NUM>, the UE <NUM> may perform a cell-selection procedure to select or determine another cell (e.g., another base station <NUM>). The cell-selection procedure may also be referred to as a cell-reselection procedure, which enables the UE <NUM> to change or switch to a different base station <NUM>. The dedicated cell-selection information <NUM> provided by the request message <NUM>, however, can influence the cell-selection procedure and bias the UE <NUM> towards selecting a base station <NUM> that supports the inactive state <NUM>. In some cases, the selected base station <NUM> does not correspond to an optimal cell that provides a target communication performance due to the dedicated cell-selection information <NUM>.

Consider a case in which the base station <NUM> does not support the inactive state <NUM> (e.g., supports technologies other than eLTE and <NUM> NR) while the base station <NUM> supports the inactive state <NUM>. The base station <NUM> provides, for example, a Node B cell, a ng-eNB cell connected with EPC <NUM> as shown in <FIG>, a Global System for Mobile Communication (GSM) cell, or a code-division multiple-access (CDMA) cell. The base station <NUM>, on the other hand, provides a 5GC cell (e.g., a gNB cell or an ng-eNB cell connected with 5GC <NUM>) or an eLTE cell. In this example, the dedicated cell-selection information <NUM> increases a priority of the base station <NUM>, which increases a probability that the base station <NUM> is selected even if the base station <NUM> provides a higher signal strength or utilizes a higher priority frequency relative to the base station <NUM>.

To enable the optimal cell (e.g., the base station <NUM>) to be selected instead, the UE <NUM> releases the dedicated cell-selection information <NUM> in the inactive state <NUM>. The dedicated cell-selection information <NUM> can be released, for example, after a first cell-selection procedure is performed in the inactive state <NUM> or responsive to the first cell-selection procedure selecting a cell that supports technologies other than eLTE and <NUM> NR while in the inactive state <NUM>. By releasing the dedicated cell-selection information <NUM>, a following cell-selection procedure does not utilize the dedicated cell-selection information <NUM> and is therefore more likely to select the optimal cell. In some cases, the UE <NUM> may release the dedicated cell-selection information <NUM> before a timer associated with the dedicated cell-selection information <NUM> expires or if the timer is halted or stopped (e.g., such as responsive to processing a public LAN mobile network (PLMN) selection request or responsive to transitioning to the idle state <NUM>).

The UE <NUM> transitions from the inactive state <NUM> to the idle state <NUM> upon receipt of a paging message <NUM> from the base station <NUM>. If the paging message <NUM> includes identifier information (e.g., ue-Identity included in the PagingRecord) that matches an identifier allocated to the UE <NUM>, the UE <NUM> transitions to the idle state <NUM>. The paging message <NUM> can be a core-network (CN) paging message. Although cells that did not support the inactive state <NUM> may support the idle state <NUM>, the dedicated cell-selection information <NUM> can continue to decrease a likelihood of the UE <NUM> from selecting these cells if the information has not been released. To enable unbiased cell selection in the idle state <NUM>, the UE <NUM> releases the dedicated cell-selection information <NUM> prior to or after transitioning to the idle state <NUM>. After the dedicated cell-selection information <NUM> is released, the UE <NUM> uses common cell-selection information from a system information message during a future cell-selection procedure.

<FIG> and <FIG> depict example methods <NUM> and <NUM> of a UE <NUM> for releasing information to improve cell selection in different resource control states. Methods <NUM> and <NUM> are shown as sets of operations (or acts) performed but not necessarily limited to the order or combinations in which the operations are illustrated. Further, any of one or more of the operations may be repeated, combined, reorganized, skipped, or linked to provide a wide array of additional and/or alternate methods. In portions of the following discussion, reference may be made to environments <NUM> and <NUM> of <FIG> and <FIG> and entities detailed in <FIG>, reference to which is made for example only. The techniques are not limited to performance by one entity or multiple entities operating on one device.

At <NUM> in <FIG>, the UE receives a request message that includes dedicated cell-selection information. For example, the UE <NUM> receives the request message <NUM> of <FIG>, which is transmitted by the base station <NUM>. The request message <NUM> includes the dedicated cell-selection information <NUM>. Different types of dedicated cell-selection information <NUM> includes cell-selection priority information or cell-reselection priority information (e.g., idleModeMobilityControlInfo or cellReselectionPriorities), depriority information, (e.g., deprioritisationReq), cell-redirection information, a timer, or a combination thereof. The request message <NUM> can be an RRCRelease message.

At <NUM>, the UE transitions to an inactive state based on the request message to suspend a connection to a current cell. For example, the resource control module <NUM> of <FIG> causes the UE <NUM> to transition to the inactive state <NUM> from the connected state <NUM>. The inactive state <NUM> is a type of resource control state <NUM> that suspends the connection to the current cell (e.g., to the base station <NUM>). In some cases the current cell is a gNB cell, a ng-enB cell connected with 5GC <NUM>, or an eNB connected with the 5GC <NUM>.

At <NUM>, the UE performs a cell-selection procedure using the dedicated cell-selection information to select an alternative cell. The resource control module <NUM>, for example, performs the cell-selection procedure using the dedicated cell-selection information <NUM> to select another cell or another base station <NUM>. In some situations, the cell-selection procedure may re-select the current cell.

At <NUM>, the UE releases the dedicated cell-selection information responsive to the alternative cell comprising an inter-radio access technology (inter-RAT) cell that does not support the inactive state. For example, the resource control module <NUM> releases the dedicated cell-selection information <NUM> if the alternative cell is a Node B cell, a ng-eNB cell connected with EPC <NUM>, a GSM cell, or a CDMA cell. In other words, the alternative cell does not use or support the eLTE or <NUM> NR standards. By releasing the dedicated cell-selection information <NUM>, the resource control module <NUM> can perform a subsequent cell-selection procedure that is independent of (e.g., doesn't rely upon) the dedicated cell-selection information <NUM>. In some cases, the resource control module <NUM> utilizes common cell-selection information provided by a system information message to perform the subsequent cell-selection procedure.

At <NUM> in <FIG>, the UE receives a request message that includes dedicated cell-selection information, as described above at <NUM> in <FIG>.

At <NUM>, the UE transitions to an inactive state based on the request message to suspend a connection to a current cell. For example, the resource control module <NUM> causes the UE <NUM> to transition to the inactive state <NUM> based on the request message <NUM> of <FIG>, as described above at <NUM> in <FIG>.

At <NUM>, the UE transitions from the inactive state to an idle state to release the connection to the current cell. The transitioning from the inactive state to the idle state includes releasing the dedicated cell-selection information prior to performing a subsequent cell-selection procedure. For example, the resource control module <NUM> causes the UE <NUM> to transition from the inactive state <NUM> to the idle state <NUM>. The idle state <NUM> is a type of resource control state <NUM> that causes the connection to the current cell or current base station <NUM> to be released.

In some cases, the resource control module <NUM> transitions to the idle state <NUM> responsive to receiving a paging message <NUM>. At <NUM>, the UE processes the paging message. For example, the UE <NUM> processes the paging message <NUM> and the resource control module <NUM> transitions to the idle state <NUM> responsive to processing the paging message <NUM>.

As part of transitioning from the inactive state to the idle state, the resource control module <NUM> releases the dedicated cell-selection information <NUM> prior to performing the subsequent cell-selection procedure. The dedicated cell-selection information <NUM> can be released while the UE <NUM> is in the inactive state <NUM> or the idle state <NUM>. By releasing the dedicated cell-selection information <NUM>, the resource control module <NUM> can perform the subsequent cell-selection procedure without using the dedicated cell-selection information <NUM>, which may be applicable while the resource control module <NUM> is in the idle state <NUM>.

<FIG> depicts an example method <NUM> of a UE <NUM> for utilizing different dedicated cell-selection information for different resource control states. Method <NUM> is shown as a set of operations (or acts) performed but not necessarily limited to the order or combinations in which the operations are illustrated. Further, any of one or more of the operations may be repeated, combined, reorganized, skipped, or linked to provide a wide array of additional and/or alternate methods. In portions of the following discussion, reference may be made to environments <NUM> and <NUM> of <FIG> and <FIG> and entities detailed in <FIG>, reference to which is made for example only. The techniques are not limited to performance by one entity or multiple entities operating on one device.

At <NUM>, the UE receives a request message that includes first dedicated cell-selection information and second dedicated cell-selection information. For example, the UE <NUM> receives the request message <NUM> of <FIG>. The request message <NUM> includes at least two dedicated cell-selection information <NUM>, which are associated with different resource control states <NUM>. Consider that the first dedicated cell-selection information <NUM> is associated with the inactive state <NUM> and the second dedicated cell-selection information <NUM> is associated with the idle state <NUM>.

At <NUM>, the UE transitions to an inactive state based on the request message. The inactive state causes a connection to a current cell to be suspended. Similar to <NUM> of <FIG>, the resource control module <NUM> of <FIG> causes the UE <NUM> to transition to the inactive state <NUM>. The inactive state <NUM> causes a connection to a current cell or base station <NUM> to be suspended.

At <NUM>, the UE performs a first cell-selection procedure in the inactive state using the first dedicated cell-selection information. For example, the resource control module <NUM> performs the first cell-selection procedure using the first dedicated cell-selection information <NUM>. In some cases, the first dedicated cell-selection information <NUM> is released responsive to performing the first cell-selection procedure, as described at <NUM> in <FIG>. If the first dedicated cell-selection information <NUM> is not released after the first cell-selection procedure is performed, the first dedicated cell-selection information <NUM> can be used again in a subsequent cell-selection procedure performed in the inactive state <NUM>.

At <NUM>, the UE transitions to an idle state from the inactive state. The idle state causes the connection to the alternative cell to be released. For example, the resource control module <NUM> causes the UE <NUM> to transition from the inactive state <NUM> to the idle state <NUM>, as described at <NUM> in <FIG>.

At <NUM>, the UE performs a second cell-selection procedure in the idle state using the second dedicated cell-selection information to select an additional cell. For example, the resource control module <NUM> performs the second cell-selection procedure using the second dedicated cell-selection information <NUM>. Because the second dedicated cell-selection information <NUM> is unique to the idle state <NUM>, the second dedicated cell-selection information <NUM> enables the cell-selection procedure to select an optimal cell to achieve a target performance.

<FIG> depicts an example method <NUM> of a UE <NUM> for releasing information to improve cell selection in different resource control states. Method <NUM> is shown as a set of operations (or acts) performed but not necessarily limited to the order or combinations in which the operations are illustrated. Further, any of one or more of the operations may be repeated, combined, reorganized, skipped, or linked to provide a wide array of additional and/or alternate methods. In portions of the following discussion, reference may be made to environments <NUM> and <NUM> of <FIG> and <FIG> and entities detailed in <FIG>, reference to which is made for example only. The techniques are not limited to performance by one entity or multiple entities operating on one device.

At <NUM>, the UE stores dedicated cell-selection information. For example, the UE <NUM> stores the dedicated cell-selection information <NUM> of <FIG>. In some cases, the UE <NUM> receives the dedicated cell-selection information <NUM> from the request message <NUM> of <FIG>, which is described above at <NUM> in <FIG>.

At <NUM>, the UE operates in an inactive state to suspend a connection to a current cell. For example, the resource control module <NUM> causes the UE <NUM> to operate in the inactive state <NUM> to suspend the connection to a current cell. In some cases, the resource control module <NUM> suspends the connection responsive to the UE <NUM> receiving the request message <NUM>.

The UE performs at least one action of a set of actions, which includes the actions described at <NUM>, <NUM>, and <NUM>. At <NUM>, the UE performs a cell-selection procedure in the inactive state that selects another cell. The other cell is associated with a core network that does not support the inactive state. For example, the resource control module <NUM> performs a cell-selection procedure in the inactive state <NUM> that selects another cell that is associated with a core network that does not support the inactive state <NUM>, such as the EPC <NUM>. In some cases, the UE <NUM> transitions from the inactive state <NUM> to the idle state <NUM> responsive to the selection of the other cell.

At <NUM>, the UE processes a paging message. For example, the UE <NUM> processes the paging message <NUM> of <FIG>. The paging message <NUM> directs the UE <NUM> to transition from the inactive state <NUM> to the idle state <NUM>.

At <NUM>, the UE transitions from the inactive state to an idle state to release the connection to the current cell. For example, the UE <NUM> transitions from the inactive state <NUM> to the idle state <NUM>.

Claim 1:
A method performed by a user equipment (<NUM>), the method comprising:
receiving, from a base station (<NUM>, <NUM>, <NUM>, <NUM>), IdleModeMobilityControlInfo for the user equipment (<NUM>) to use for cell reselection;
storing the IdleModeMobilityControlInfo;
operating in an inactive state (<NUM>) to suspend a radio resource control, RRC, connection to a first cell;
processing a paging message (<NUM>), the paging message directing the user equipment to transition from the inactive state to an idle state (<NUM>); and
responsive to processing the paging message, releasing the IdleModeMobilityControlInfo.