METHOD FOR A USER DEVICE CONFIGURED WITH USER CREDENTIALS FOR A PLURALITY OF PUBLIC TERRESTRIAL MOBILE NETWORKS, METHOD FOR A FIRST NETWORK NODE CONFIGURED TO OPERATE ON A FIRST PUBLIC TERRESTRIAL MOBILE NETWORK AND TO MANAGE A USER DEVICE, AND SAID USER DEVICE AND FIRST NETWORK NODE

Abstract

The embodiments include methods for a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMNs). Such methods include, while registered to the first and second PLMNs and in a connected state for the first PLMN, transmitting to a first network node in the first PLMN a first indication that the UE wants to enter a reduced power state for the first PLMN. Such methods include starting a timer after transmitting the first indication, subsequently performing a handover to a second network node in the first PLMN, and performing one or more of the following: transmitting to the second network node a second indication that the UE wants to enter the reduced power state for the first PLMN; and stopping the timer.Other forms of implementation include complementary methods for the first and second network nodes, in addition to UE and network nodes configured to carry out such methods.

Description

27534 INDICATION OF PREFERENCE FOR PERSISTENT RELEASE OF TRANSFER TECHNICAL FIELD This disclosure relates generally to wireless networks and more specifically to techniques for managing user equipment (UE) configured with multiple user subscriptions to different public land mobile networks (PLMN). BACKGROUND Long-Term Evolution (LTE) is a general term for the so-called fourth-generation (4G) radio access technologies developed within the third-generation partnership project (3GPP) and initially standardized in versions 8 (Rel-8) and 9 (Rel-9), also known as Evolved UTRAN (E-UTRAN). LTE targets various licensed frequency bands and is accompanied by improvements in non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes the Evolved Packet Core (EPC). LTE continues to evolve through subsequent versions. A general example architecture of a network comprising LTE and SAE is shown in Figure 1. E-UTRAN 100 includes one or more evolved node Bs (eNBs), such as eNBs 105, 110, and 115, and one or more user equipment (UEs), such as UE 120. As used within the 3GPP standards, “user equipment” or “UE” means any wireless communication device (e.g., smartphone or computing device) that can communicate with network equipment compliant with the 3GPP standard, which includes E-UTRAN, as well as UTRAN and / or GERAN, given that third-generation (3G) and second-generation (2G) 3GPP RANs are commonly referred to as such. As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio carrier control, radio admission control, radio mobility control, scheduling and dynamic allocation of resources to UEs in the uplink and downlink, as well as the security of communications with the UE. These functions reside in the eNBs, such as eNBs 105, 110, and 115. Each eNB can serve a geographic coverage area that includes one or more cells, including cells 106, 111, and 115 served by eNBs 105, 110, and 115. 1890327 of 61 respectively. The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1. The eNBs are also responsible for the E-UTRAN interface with the EPC 130, specifically the S1 interface with the Mobility Management Entity (MME) and the Service Gateway (SGW), which are collectively shown as MME / S-GWs 134 and 138 in Figure 1. In general, the MME / S-GW manages both the overall control of the UE and the data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling protocols (e.g., the control plane) between the UE and the EPC, which are known as non-accessible layer (NAS) protocols. The S-GW manages all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as a local mobility anchor for data carriers when the UE moves between eNBs, such as eNBs 105, 110, and 115. The EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user and subscriber-related information. The HSS 131 can also provide support functions for mobility management, call and session configuration, user authentication, and access authorization. The functions of the HSS 131 may be related to the functions or operations inherited from the Home Position Register (HLR) and the Authentication Center (AuC). The HSS 131 can also communicate with the MME 134 and 138 via their respective S6a interfaces. In some embodiments, HSS 131 can communicate with a user data repository (UDR), labeled EPC-UDR 135 in Figure 1, via a Ud interface. EPC-UDR 135 can store user credentials after they have been encrypted using AuC algorithms. These algorithms are non-standardized (i.e., vendor-specific), so the encrypted credentials stored in EPC-UDR 135 are not accessible to any vendor other than the HSS 131 vendor. Figure 2 illustrates a block diagram of a sample control plane (CP) protocol stack between a UE, an eNB, and an MME. The sample protocol stack includes the physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and radio resource control (RRC) layers between the UE and the eNB. The PHY layer handles how and what features are used to transfer data across transport channels at the LTE radio interface. The MAC layer provides services 1890327 of 61, Data Transfer over Logical Channels, assigns logical channels to PHY transport channels and reallocates PHY resources to support these services. The RLC layer provides error detection and / or correction, concatenation, segmentation and reassembly, and reordering of data transferred to or from upper layers. The PDCP layer provides encryption / decryption and integrity protection for both the CP and the user plane (UP), as well as other UP functions, such as header compression. The example protocol stack also includes non-accessible layer (NAS) signaling between the UE and the MME. The RRC layer controls communication between a UE and an eNB at the radio interface, as well as UE mobility between cells in the E-UTRAN. After a UE is powered on, it will be in the RRC_IDLE state until an RRC connection is established with the network, at which point the UE will transition to the RRC_CONNECTED state (for example, where data transfer can occur). The UE returns to RRC_IDLE after the network connection is released. In the RRC_IDLE state, the UE does not belong to any cell, no RRC context has been established for the UE (for example, in the E-UTRAN), and the UE is out of UL synchronization with the network. Even so, a UE in the RRC_IDLE state is known to the EPC and has an assigned IP address. Additionally, in the RRC_IDLE state, the UE's radio is active on a discontinuous receive (DRX) schedule configured by higher layers. During active DRX periods (also called "on durations"), an RRC_IDLE UE receives system information (SI) transmitted by a service cell, performs measurements of nearby cells to support cell reselection, and monitors a paging channel for EPC pages via an eNB serving the cell in which the UE is camped. A UE must perform a random access (RA) procedure to transition from the RRC_IDLE state to the RRC_CONNECTED state. In the RRC_CONNECTED state, the cell serving the UE is known, and an RRC context is established for the UE in the serving eNB so that the UE and eNB can communicate. For example, a Cellular Radio Network Temporary Identifier (C-RNTI), a UE identity used for signaling between the UE and the network, is configured for a UE in the RRC_CONNECTED state. Currently, the fifth generation (5G) of cellular systems, also called New Radio (NR), is being standardized within the Third Generation Partnership Project (3GPP). NR is being developed for maximum 1890327 of 61 flexibility to support multiple and substantially different use cases, but shares many similarities with fourth-generation LTE. For example, NR uses CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) in the DL and both CP-OFDM and DFT propagation OFDM (DFT-S-OFDM) in the UL. As another example, in the time domain, the NR DL and UL physical resources are organized into equal-sized 1 ms subframes. A subframe is further divided into multiple equal-length slots, where each slot includes multiple OFDM-based symbols. In addition to RRC_IDLE and RRC_CONNECTED, the NR RRC layer also includes an RRC_INACTIVE state with properties similar to the suspended condition in LTE Rel-13. Currently, 3GPP is exploring ways to better support UEs that can manage two or more simultaneous subscriptions to different public land mobile networks (PLMNs), for example, with multiple subscriber identity modules (i.e., Multi-SIM or MUSIM). A single UE with two or more subscriber credentials can act as different UEs depending on which subscription is active at any given time. While some UEs may have some of these capabilities, most operations are not optimized, and there is currently no standardized 3GPP support for multi-SIM. An example scenario is a UE in the RRC_CONNECTED state on a second PLMN (i.e., the one the user subscribes to) that needs to perform operations on a first PLMN, such as listening for paging, acquiring broadcast SIs, reselecting cells, etc. There are two possible procedures the UE can follow in this scenario. The first is known as the “RRC switching procedure without leaving RRC_CONNECTED,” such as when the UE listens for paging on the first PLMN for short periods and then quickly switches back to the second PLMN, while remaining in the RRC_CONNECTED state on the second PLMN during the operation on the first PLMN. SYNTHESIS The second procedure is known as the "RRC switchover procedure to exit RRC_CONNECTED," such as when the UE initiates a service in the first PLMN (for example, responds to paging) and cannot quickly switch back to the second PLMN. This causes the UE to exit the RRC_CONNECTED state in the second PLMN. Various problems, inconveniences, and / or difficulties can arise when the UE exits the RRC_CONNECTED state in the second PLMN in this way. 1890327 of 61 The methods of implementation in this disclosure provide specific improvements to the operation of MUSIM-enabled UEs in wireless networks, such as by facilitating solutions to overcome the example problems summarized above and described in more detail below. The ways of implementing this disclosure include methods (e.g., procedures) for a UE (e.g., a wireless device) configured with user credentials for a plurality of public land mobile networks (PLMN). These example methods may include, while registered to the first and second PLMNs and in a connected state for the first PLMN, transmitting to a first network node in the first PLMN an initial indication that the UE wants to enter a reduced-power state for the first PLMN. These example methods may also include starting a timer after transmitting the initial indication and subsequently performing a handover to a second network node in the first PLMN. These example methods may also include performing one or more of the following: • transmit to the second network node in the first PLMN a second indication that the UE wants to enter the reduced power state for the first PLMN; and • stop the timer. In some implementations, the reduced power state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some implementations, at least one of the first and second indications is included in a UEAssistanceInformation message. In some implementations, these example methods may also include receiving a timer value from the first network node in the first PLMN via an RRCReconfiguration or RRCResume message. The timer is then started at the received timer value. In some implementations, the timer value may be included within a series of nested information elements for a multi-SIM configuration. In some implementations, these example methods may also include entering a reduced-power state for the first PLMN in response to either of the following: timer expiration, or a message received from the second network node while the timer is running. More 1890327 of 61 specifically, the message indicates that the UE should enter the reduced power state for the first PLMN. In some implementations, these example methods may also include receiving a timer value from the second network node while the timer is running, and refraining from resetting the timer based on the timer value received from the second network node. In some embodiments, these example methods may also include, based on the determination that the second network node does not support indications that the UEs want to enter a reduced-power state for the first PLMN, stopping the timer and refraining from entering the reduced-power state. In some embodiments, the determination that the second network node does not support indications that the UEs want to enter a reduced-power state for the first PLMN may be based on one of the following: a message received from the second network node during the handover; or a message received from the second network in response to the second indication. In some embodiments, the handover process may involve receiving a handover command from the second network node. In such embodiments, the transmission of the second indication may depend on the period between the transmission of the first indication and the reception of the handover command being less than a certain threshold. In some embodiments, the first indication is an initial indication that the UE wants to enter a reduced energy state for the first PLMN, and the second indication is a subsequent indication that the UE wants to enter a reduced energy state for the first PLMN. Other embodiments include methods (e.g., procedures) for a first network node (e.g., a base station, eNB, gNB, ng-eNB, engNB, etc.) configured to operate on a first PLMN and to manage a UE configured with user credentials for a plurality of PLMNs. These example methods might include, while the UE is registering with the first PLMN and a second PLMN, and in a connected state for the first PLMN, receiving a first indication from the UE that it wants to enter a reduced-power state for the first PLMN. These example methods might also include sending a request to a second network node in the first PLMN to hand the UE off to the second network node. The request includes a second indication that the UE wants to enter the reduced-power state for the second PLMN. 1890327 of 61 the first PLMN. These example methods can also include receiving a handover request confirmation from the second network node and sending the UE a command to hand over to the second network node. In some implementations, the reduced power state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some implementations, the first indication may be included in a UEAssistanceInformation message. In some implementations, these example methods may also include sending the UE a timer value in an RRCReconfiguration or RRCResume message. In some implementations, the timer value may be included in a series of nested information elements for a multi-SIM configuration. Other embodiments include methods (e.g., procedures) for a second network node (e.g., a base station, eNB, gNB, ng-eNB, engNB, etc.) configured to operate on a first PLMN and to manage a UE configured with user credentials for a plurality of PLMNs. These example methods might include receiving, from a first network node in the first PLMN, a request to hand the UE over to the second network node in the first PLMN. The UE registers with the first PLMN and a second PLMN, and is in a connected state for the first PLMN. These example methods might also include receiving, from the UE or from the first network node in the first PLMN, a second indication that the UE wants to enter the reduced-power state for the first PLMN. These example methods might also include, based on the second indication, determining a time at which the UE expects to enter the reduced-power state for the first PLMN. In some implementations, these example methods may also include sending one or more of the following to the UE before the specified time: a timer value to initialize a timer in the UE, and a message indicating that the UE should enter the reduced power state for the first PLMN. In some implementations, the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some implementations, the second indication can be received from the first network node with the handover request. In other implementations, these example methods can also include sending a 1890327 of 61 confirmation of the transfer request and carry out a transfer procedure with the UE. In such embodiments, the second indication may be received from the UE after the transfer procedure is completed. In some of these embodiments, the second indication may be included in a UEAssistanceInformation message. In some of these embodiments, the implementation of the handover procedure with the UE may include sending a handover command to the UE. In such embodiments, the second indication can be received from the UE depending on whether the period between the following is less than a threshold: the transmission by the UE to the first network node of an initial indication that the UE wants to enter a reduced-power state for the first PLMN, and the UE's receipt of the handover command. In various embodiments, the second indication indicates one of the following: • a remaining time on a timer that is running in the UE, • an initial value for the timer that was set by the first network node, • a time since the UE sent the first network node a first indication that the UE wants to enter the reduced power state for the first PLMN, or • an absolute time at which the UE expects to enter the reduced power state for the first PLMN. In some embodiments, the second network node can indicate to the UE that the second network node supports indications that the UE wants to enter a reduced power state for the first PLMN, based on one of the following: a message sent to the UE during the handover, or a message sent to the UE in response to the second indication received from the UE. Other embodiments include UEs (e.g., wireless devices, IoT devices, etc., or components thereof) and network nodes (e.g., base stations, eNBs, gNBs, ng-eNBs, etc., or components thereof) configured to perform operations corresponding to any of the example methods described herein. Other embodiments include program instructions stored on computer-readable, non-transient media that, when executed by processing circuitry, 1890327 of 61 configure such UE or network nodes to carry out operations corresponding to any of the example methods described herein. These and other implementations described herein can avoid and / or prevent misunderstandings and / or state mismatches between UEs and network nodes after handovers, thus facilitating the correct and efficient operation of UEs and networks. In this way, these implementations can reduce or prevent the loss of user data and / or excessive latency for a UE to receive and respond to network paging, which can occur when such misunderstandings and / or state mismatches arise. These and other objectives, characteristics and advantages of the methods of carrying out this disclosure will become evident after reading the following detailed description in view of the drawings that are briefly described below. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 shows a high-level view of an example LTE network architecture. Figure 2 shows an example configuration of an LTE control plane (CP) protocol stack. Figures 3-4 show high-level views of example 5G / NR network architectures. Figure 5 is a signal flow diagram for an example network-centric technique according to some embodiments of the present disclosure. Figure 6 is a signal flow diagram for an example UE-centered technique in accordance with other embodiments of the present disclosure. Figure 7 is a flowchart for an example procedure for a conditional release of a UE from a first PLMN, according to various forms of implementation of this disclosure. Figure 8 is a flowchart of an example method (e.g., a procedure) for a UE (e.g., a wireless device, IoT device, etc., or components thereof), according to various embodiments of this disclosure. Figure 9 is a flowchart of an example method (e.g., a procedure) for a first network node (e.g., eNB, gNB, ng-eNB, en-gNB, etc., or components thereof), according to various ways of implementing the 1890327 of 61 present disclosure. Figure 10 is a flowchart of an example method (e.g., a procedure) for a second network node (e.g., eNB, gNB, ng-eNB, engNB, etc., or components thereof), according to various embodiments of this disclosure. Figure 11 shows a communication system according to various forms of implementation of this disclosure. Figure 12 shows a UE in accordance with various forms of implementation of this disclosure. Figure 13 shows a network node according to various forms of implementation of this disclosure. Figure 14 shows the central computer system according to various forms of implementation of this disclosure. Figure 15 is a block diagram of a virtualization environment in which functions implemented by some embodiments of this disclosure can be virtualized. Figure 16 illustrates communication between a central computer system, a network node, and a UE through multiple connections, at least one of which is wireless, according to various embodiments of this disclosure. DETAILED DESCRIPTION Some of the embodiments contemplated herein will be described in greater detail below with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the subject matter disclosed herein should not be interpreted as being limited solely to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to persons of intermediate skill. In general, all terms used herein should be interpreted according to their usual meaning in the relevant technical field, unless a different meaning is clearly provided and / or implied from the context in which they are used. All references to an element, apparatus, component, means, stage, etc., should be clearly interpreted as referring to at least one instance of the element, apparatus, component, means, stage, etc., unless explicitly stated otherwise. The steps of any of the methods disclosed herein need not be carried out in the exact order disclosed. 1890327 of 61 unless a step is explicitly described as following or preceding another step and / or where it is implied that one step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, where appropriate. Likewise, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objectives, features, and advantages of the appended embodiments will be apparent from the following description. In addition, the following terms are used throughout the description provided below: • Radio node: As used herein, a “radio node” can be a radio access node or a wireless device. • Radio access node: As used herein, a “radio access node” (or equivalently “radio network node”, “radio access network node”, or “RAN node”) may be any node in a radio access network (RAN) of a cellular communication network that functions to transmit and / or receive signals wirelessly.Some examples of a radio access node include, but are not limited to, a base station (e.g., a new radio (NR) (gNB / en-gNB) base station in a fifth-generation (5G) 3GPP NR network or an enhanced or evolved (eNB / ng-eNB) Node B in a 3GPP LTE network), distributed base station components (e.g., CU and DU), base station user plane and / or control components (e.g., CU-CP, CU-UP), a macro or high-power base station, a low-power base station (e.g., a micro, pico, femto, or home base station, or similar), an integrated access back node, a transmit point, a remote radio unit (RRU or RRH), and a relay node. • Core network node: As used herein, a “core network node” is any type of node in a core network. Examples of a core network node include, for instance, a Mobility Management Entity (MME), a Service Gateway (SGW), a Packet Data Gateway (P-GW), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), and an Exposure Function. 1890327 of 61 service capacity (SCEF), or similar. Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communication network by communicating wirelessly with network nodes and / or other wireless devices. Wireless communication may involve transmitting and / or receiving wireless signals that use electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information through the air.Some examples of a wireless device 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, video game devices or consoles, music storage devices, players, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), mobile-type communication (MTC) devices, Internet of Things (IoT) devices, wireless vehicle-mounted terminal devices, etc.Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short). Network node: As used herein, a “network node” is any node that is part of the radio access network (e.g., a radio access node or equivalent name discussed above) or the core network (e.g., a core network node discussed above) of a cellular communication network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or other network nodes or equipment in the cellular communication network, to enable and / or provide wireless access to the wireless device, and / or to perform other functions (e.g., management) in the cellular communication network. 1890327 of 61 Note that the description herein focuses on a 3GPP cellular communications system and, by definition, often uses 3GPP terminology or terminology similar to 3GPP terminology. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term cell is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells, and, by definition, the concepts described herein apply equally to both cells and beams. Figure 3 illustrates a high-level view of an example 5G network architecture, consisting of a next-generation RAN (NG-RAN 399) and a 5G core (5GC 398). NG-RAN 399 may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, while the gNBs may be connected to each other via one or more Xn interfaces, such as an Xn interface 340 between gNBs 300 and 350 in Figure 3. Each gNB may support frequency-division duplexing (FDD), time-division duplexing (TDD), or a combination of these on the NR interface for the UEs. NG-RAN 399 is divided into layers: a radio network layer (RNL) and a transport network layer (TNL). The NG-RAN architecture—that is, the logical NG-RAN nodes and the interfaces between them—is defined as part of the RNL. The associated TNL protocol and functionality are specified for each NG-RAN interface (NG, Xn, F1). The TNL provides user plane transport services and signaling transport. The logical nodes of NG RAN shown in Figure 3 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 300 in Figure 3 includes gNBCU 310 and gNB-DUs 320 and 330. The CUs (e.g., gNB-CU 310) are logical nodes that host upper-layer protocols and perform various gNB functions, such as controlling the operation of the DUs. Each DU is a logical node that hosts lower-layer protocols and may include, depending on the functional division, various subsets of gNB functions. By definition, each CU and DU may include various circuits necessary to perform its respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power supply circuits. A gNB-CU connects to its associated gNB-DUs via their respective F1 logic interfaces, such as interfaces 322 and 332 shown in Figure 1890327 of 61 3. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB; for example, the F1 interface is not visible beyond the gNB-CU. In the gNB split CU-DU architecture illustrated in Figure 3, DC can be achieved by allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs. Figure 4 shows another high-level view of a sample 5G network architecture, which includes NG-RAN 499 and 5GC 498. As shown in the figure, NG-RAN 499 can include gNBs (e.g., 410a,b) and ng-eNBs (e.g., 420a,b) that are interconnected via their respective Xn interfaces. The gNBs and ng-eNBs are also connected via NG interfaces to 5GC 498, specifically to the Access and Mobility Management Functions (AMF, e.g., 430a,b) via their respective NG-C interfaces and to the User Plane Functions (UPF, e.g., 440a,b) via their respective NG-U interfaces. In addition, AMFs can communicate with one or more policy control functions (PCF, for example, 450a,b) and network exposure functions (NEF, for example, 460a,b). Each gNB can support the NR radio interface, which includes FDD, TDD, or a combination of these. In contrast, each ng-eNB can support the LTE radio interface, but unlike conventional LTE eNBs (e.g., in Figure 1), it connects to the 5GC via the NG interface. Each gNB or ngeNB can serve a geographic coverage area that includes one additional cell, such as cells 411a and 421a-b shown in Figure 4. Depending on the specific cell in which it is located, a UE 405 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. In some implementations, gNBs and ng-eNBs can also use multiple directional beams to provide coverage within their respective cells. Generally, a DL beam is a coverage area of ​​a reference signal (RS) transmitted over the network that can be measured or monitored by a UE. In NR, for example, such an RS can include any of the following, alone or in combination: PBCH synchronization / block signal (SSB), CSI-RS, tertiary reference signals (or any other synchronization signal), positioning RS (PRS), DMRS, phase-tracking reference signals (PTRS), etc. Generally, SSB is available to all UEs regardless of the RRC status, while other RSs (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs. 1890327 out of 61 that have a network connection, i.e., in the RRC_CONNECTED state. As briefly mentioned above, 3GPP is currently exploring ways to better support UEs that can manage two or more simultaneous subscriptions to different public land mobile networks (PLMNs), for example, with multiple subscriber identity modules (i.e., Multi-SIM or MUSIM). A single UE with two or more subscriber credentials can act as different UEs depending on which subscription is active at any given time. While some UEs may have some of these capabilities, most operations are not optimized, and there is currently no standardized 3GPP support for multi-SIM. One potential improvement is a simpler switch between states related to using a first subscription to a first PLMN (with user credentials on a first USIM) and states related to using a second subscription to a second PLMN (with user credentials on a second USIM). This can be particularly important when such states are dependent, for example, CM-Connected on both the first and second PLMNs. Such switching can be straightforward, or even unnecessary, if the UE has the capability to communicate simultaneously with both the first and second PLMNs using the first and second USIMs. This may require at least dual receiver and transmitter chains, frequencies used in both networks that do not interfere with each other, and sufficient radio separation to prevent interference (e.g., intermodulation, IM, effects) within the UE itself. For UEs that cannot simultaneously communicate with two PLMNs in this way, another possible approach is to introduce signaling that allows a UE to signal at least one network that is going out or becoming unreachable for a particular PLMN. An example scenario is a UE in the RRC_CONNECTED state on a second PLMN (i.e., the one the user subscribes to) that needs to perform operations on a first PLMN, such as paging, acquiring transmit SIs, reselecting cells, etc. There are two possible procedures the UE can follow in this scenario. The first is known as the “RRC switchover procedure without exiting RRC_CONNECTED,” such as when the UE listens for paging on the second PLMN for short periods and then quickly switches back to the first PLMN, while remaining in the RRC_CONNECTED state on the first PLMN during the operation on the second PLMN. The second is known as 1890327 of 61 “RRC switch procedure to exit RRC_CONNECTED”, such as when the UE initiates a service on a second PLMN (e.g., responds to paging) and therefore cannot quickly switch back to a first PLMN, causing the UE to exit the RRC_CONNECTED state on the first PLMN. The RAN2 3GPP working group has reached the following agreements on various switching-related issues: • The switching procedure can be used to notify the first PLMN (“network A”) that the UE has priority to exit the RRC_CONNECTED state on network A. • The switching procedure can be used to notify the network A that the UE has a preference to remain in the RRC_CONNECTED state on network A while temporarily switching to the second PLMN (“network B”). • RRC signaling is used for the switching procedure without exiting the RRC_CONNECTED state in network A, allowing the UE to temporarily switch to network B as a baseline. The need for additional MAC signaling is for further study (FFS). • During the switching procedure to exit the state RRC_CONNECTED allows the UE to enter the RRC_IDLE state if it does not receive a response message from the network within a configured time period. This drawback is FFS for the RRC_INACTIVE state. • The access layer (AS)-based solution for network switching includes two stages: Or, if configured, the UE can send an RRC message to exit RRC_CONNECTED for MUSIM purposes, and gNB can release the UE to RRC_IDLE / RRC_INACTIVE. For the RRC switchover procedure to exit RRC_CONNECTED, the UE can be configured with an "exit time period," such that when the exit time period ends, the UE can enter the RRC_IDLE state even without having received an RRCRelease message from the first PLMN (or network B). Furthermore, the UE can autonomously leave the first PLMN during the exit time period after the UE has sent a request to leave that network, even if the first PLMN has not released the UE. 1890327 of 61 end of that period. Even so, there are some situations where these existing arrangements may not work correctly. For example, a UE might send an indication to a first network node (e.g., gNB) that it prefers to be released to RRC_IDLE or RRC_INACTIVE. Subsequently, the UE might be handed off to a second network node during normal mobility operations. However, this release preference information is not transmitted to the second network node, which will not know if or when the UE will leave the first PLMN that includes the first and second network nodes. Accordingly, the implementation methods described herein provide techniques whereby a MUSIM UE, which is simultaneously registered to the first and second PLMNs and has the corresponding first and second USIMs, prefers to leave the first PLMN and connect instead to a second PLMN. The UE can send a release preference indication to a first network node (or source node) in the first PLMN, which then passes the UE to a second network node (or destination node) in the first PLMN. The UE or the first network node can inform the second network node of the UE's release preference, and the second network node can then act on that information. Other implementations also include techniques for the UE when the destination node does not configure the UE release preference indication. Other implementations include techniques for the UE to handle (for example, abort) a planned release procedure after a handover occurs. Although the implementation methods are described in the context of handing off from the source node to the destination node, the underlying principles are also applicable to handing off from a source cell to a destination cell served by a single network node. The implementation methods described herein may provide various benefits, advantages, and / or solutions to the problems described herein. For example, the implementation methods described herein may avoid and / or prevent misunderstandings and / or status mismatches between UEs and service network nodes after handovers, which may facilitate the correct and efficient operation of the network. The methods of implementing this disclosure will now be described in more detail. In this description, the expression “MUSIM EU” will refer to an EU 1890327 of 61 that is simultaneously registered in multiple PLMNs, for example, based on multiple corresponding USIMs that store the respective user credentials. In some cases, the MUSIM UE may be more simply referred to as “UE”. The term “first PLMN” refers to a network in which the MUSIM UE registers and is in a connected or normal power state (e.g., RRC_CONNECTED or a state with similar properties), but for which the MUSIM UE wants to enter a reduced power state (e.g., RRC_INACTIVE, RRC_IDLE, or a state with similar properties). Likewise, the term “second PLMN” refers to another network in which the MUSIM UE registers simultaneously with its registration in the first PLMN. In some implementations (referred to as the “network-centric approach”), the MUSIM UE can transmit a release preference indication to a first network node (or source node) serving the UE. Subsequently, if the first network node has not yet released the UE, it initiates a handover procedure for the UE to a second network node. The first network node sends the second network node an indication of a release preference indication received from the UE. This release preference indication can be sent from the first network node to the second network node in a handover preparation procedure. In some implementations, the release preference indication may not only indicate the UE's preference to leave the first PLMN, but may also include information about when the UE is expected to leave the first PLMN. This can be indicated by stating how much time remains until the UE leaves the first PLMN. Another approach is to indicate how much time has elapsed since the UE sent the first release preference. Yet another approach is to indicate an absolute time when the UE will leave the first PLMN, for example, a specific time of day. Upon receiving this information, the second network node assumes that the UE will leave the first PLMN after the time specified by the first network node. The second network node can release the UE before the specified time; otherwise, both the second network node and the UE have a consistent understanding that the UE can autonomously leave the network after that time. Figure 5 is a signaling diagram for an example network-centric approach according to these embodiments. Specifically, Figure 5 shows the signaling between a UE (510), a first network node (520), and a 1890327 of 61 second network node (530). Initially, the UE sends a release preference indication to the first network node (or source node). The first network node sends a handover readiness message to the second network node. The handover readiness message includes release preference information for the UE, which may include and / or be derived from the release preference indication received from the UE. The second network node then confirms the requested handover, prompting the first network node to send a handover command to the UE. The second network node and the UE then perform the handover procedure, after which the second network node serves the UE. As a specific example, if the UE sent the release preference indication at T=0 and the first network node sent the handover readiness message at T=0.5 seconds, the release preference information can include a time T=0.5, which represents the time since the UE sent the release preference indication to the first network node. In some embodiments, the second network node can subsequently transfer the UE to a third network node. The second network node can send release preference information for the UE. This release preference information sent to the third node can be based on a release preference indication received from the UE by the second network node, or it can be based on the release preference information from the first network node, discussed earlier. The principles of these embodiments can be further extended to additional subsequent transfers. In other embodiments (referred to as the “UE-centric approach”), the MUSIM UE may transmit a release preference indication to a first network node (or source node) serving the UE. Subsequently, if the first network node has not yet released the UE, the first network node initiates a handover procedure for the UE to a second network node. After the handover, the UE sends a second release preference indication to the second network node. Upon receiving this information, the second network node assumes that the UE will leave (i.e., release the connection to) the first PLMN after a time specified by the UE in the release preference indication. The second network node may release the UE before the specified time; if not, both the second network node and the UE have a consistent understanding that the UE may autonomously leave the network after that time. The principles of these embodiments 1890327 of 61 realization can be further extended to additional subsequent transfers from the EU. In some implementations, the release preference indication may not only indicate the UE's preference to leave the first PLMN, but may also include information about when the UE is expected to leave the first PLMN. This can be indicated by stating how much time remains until the UE leaves the first PLMN. Another approach is to indicate how much time has elapsed since the UE sent the first release preference. Yet another approach is to indicate an absolute time when the UE will leave the first PLMN, for example, a specific time of day. Figure 6 is a signal flow diagram for an example UE-centric approach according to these embodiments of the present disclosure. In particular, Figure 6 shows the signaling between a UE (610), a first network node (620), and a second network node (630). Initially, the UE sends a first release preference indication to the first network node (or source node). Although not shown, the first network node may send a handover readiness message to the second network node. The second network node may then confirm the requested handover, prompting the first network node to send a handover command to the UE. The second network node and the UE then perform the handover procedure, after which the second network node serves the UE. Subsequently, the UE sends a second release preference indication to the second network node. This second release preference indication may include a timeframe during which the UE expects to release itself from the first PLMN. A network node may not know whether a particular release preference indication received from the UE is an initial (or first) release preference or a subsequent (e.g., second, third, etc.) release preference indication. In some implementations, a UE can indicate whether a particular release preference indication is an initial or subsequent release preference indication. In other words, the UE can indicate whether it previously sent a release preference indication to another network node (i.e., neither releasing nor being released). The initial / subsequent indication can be a field within the release preference indication. For example, the presence of the field might indicate that it is a subsequent release preference indication, and the absence of the field might indicate that it is a first release preference indication. As discussed earlier, the UE can indicate in the release preference indication the time T at which (or until) the UE expects to exit the 1890327 of 61 first network. In some embodiments, the UE omits the field for time T when it is an initial release preference indication and includes the field (set to a suitable value) if it is a later release preference indication. The second (or third, etc.) network node receiving this information can determine that the UE will leave the first PLMN at the time indicated by the field when it is present and at a predetermined release time (e.g., the exit time period described above) when the field is absent. In other embodiments, the UE may always include a field indicating the time at which (or until) the UE expects to exit the first PLMN. The included field may indicate a predetermined release time when it is an initial release preference indication, and the included field may indicate an actual expected time when it is a later release preference indication. The first network node can forward the release preference indication to a second network node for a handover procedure (for example, in the network-centric approach shown in Figure 5). For instance, this can be included in a message from the first network node to the second network node during the handover preparation procedure. However, there may be a period between the time the handover preparation procedure is initiated (and when the second network node receives the release preference indication from the first network node) and the time the UE receives the handover command. Any release preference indication sent by the UE to the first network node during this period may not be sent / forwarded by the first network node to the second network node. In some implementations, the UE can be configured to send a second release preference indication to the second network node only when the time between sending the first release preference indication to the first network node and receiving a handover is less than a threshold. This threshold can be configured by the network or predetermined, for example, by 3GPP specifications. If the handover occurred a relatively long time (for example, two seconds) after the UE sent the first release preference indication, it is likely that the first network node has already sent some or all of the release preference indications received from the UE during the handover preparation procedure, making the second release preference indication unnecessary. 1890327 of 61 second indication of release preference to the second network node. These principles can be applied to a handover from any source node (e.g., first, second, etc.) to any destination node (e.g., second, third, etc.). Several of the implementations described above refer to how a second network node in the first PLMN can be informed of the time T at which a UE expects to leave the first PLMN. However, the second network node may not always support this function, for example, due to legacy software and / or hardware. In some implementations, when the second network node does not support the release preference indication for the UE, the UE may refrain from leaving the first PLMN at the expected time T. For example, if the UE was a first network node and sent a release preference indication stating T = 5 seconds at t = 0 while being served by the first network node, the UE expects to leave the first PLMN at t = 5 seconds. The UE can then be handed off to a second network node at t = 3 seconds.If the second network node does not support the release preference indication, the UE will not leave the network at time t = 5 seconds. However, if the second network node supports the release preference indication, the UE will leave the first network at time t = 5 seconds. For example, the UE can determine whether the second network node supports the release preference indication by explicitly indicating this in any of the messages received from the second network node during the handover procedure. As another example, in the UE-centric approach, the UE can determine whether the second network node supports the release preference indication based on the second network node's response to the release preference indication sent by the UE. Figure 7 is a flowchart for an example procedure for a conditional release of a UE from a first PLMN, according to various embodiments of this disclosure. Initially, the UE sends a release preference indication to the first network node (or source node). The release preference indication may state that the UE expects to exit the first PLMN (for example, at T = 5 seconds after sending the release preference indication). Subsequently, the UE hands off to the second network node (for example, at t = 3 seconds after sending the release preference indication to the first network node). When the UE determines that the second network node accepts the release preference indication, the UE proceeds to exit the PLMN. 1890327 of 61 first PLMN at T=5 seconds after sending the release preference indication. When the UE determines that the second network node does not support the release preference indication, the UE refrains from leaving the first PLMN at T=5 seconds after sending the release preference indication. In some implementations, after the handover to the second network node (or destination node), the UE can abort a planned autonomous release procedure from the first PLMN that the UE previously indicated to the first network node (or source node). The UE can abort the release based on the occurrence of the handover. For example, the UE might stop a currently running timer (also known as an exit timer or release timer) after the handover, where the timer's expiration would have caused the UE to perform the autonomous release. In such a case, the UE might need to send an additional release preference indication to the second network node after the handover to be released, or to perform an autonomous release procedure after a time specified by the additional release preference indication. In both the network-centric and UE approaches discussed earlier, when the UE is handed off from a first network node to a second network node, the UE can allow a currently running timer (for example, the exit or release timer mentioned earlier), which was started when the UE connected to the first network node, to continue running after the UE connects to the second network node. In other words, the UE should not reset this timer when applying a configuration provided by the second network node after the handover. For example, the second network node can reconfigure the timer value after the handover. However, the UE should not apply the newly configured timer value (for example, to reset the timer), but rather keep its current timer running. If the second network node then moves the UE to RRC_INACTIVE, the UE can store the new timer value provided by the second network node and apply it once its connection is re-established and the UE switches back to RRC_CONNECTED. The embodiments described above can be further illustrated with reference to Figures 8-10, which show example methods (e.g., procedures) for a UE, a first network node, and a second network node, respectively. In other words, various features of the operations The 1890327 of 61 described below correspond to various implementations described above. These example methods can be used together to provide various exemplary benefits and / or advantages. While Figures 8 to 10 show specific blocks in a particular order, the operations of the respective methods can be performed in different orders and can be combined and / or split into blocks with different functionality. Optional blocks or operations are indicated by dashed lines. In particular, Figure 8 shows a flowchart of an example method (e.g., a procedure) for a UE configured with user credentials for a plurality of PLMNs, according to various embodiments of this disclosure. The example method can be implemented by a UE (e.g., a wireless device) as described elsewhere herein. The example method may include operations in block 820, where, while registered to the first and second PLMNs and in a connected state for the first PLMN, the UE may transmit to a first network node in the first PLMN a first indication that the UE wants to enter a reduced-power state for the first PLMN. The example method may also include operations in blocks 830-840, where the UE may start a timer after transmitting the first indication and subsequently perform a handover to a second network node in the first PLMN. The example method may also include operations in block 870, where the UE may perform one or more of the following: • transmit to the second network node in the first PLMN a second indication that the UE wants to enter the reduced power state for the first PLMN; and • stop the timer. In some implementations, the reduced power state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some implementations, at least one of the first and second indications is included in a UEAssistanceInformation message. In some implementations, the example method may also include block 810 operations, where the UE can receive from the first network node in the first PLMN a timer value in an RRCReconfiguration message 1890327 of 61 or an RRCResume message. The timer is started (for example, in block 830) at the received timer value. In some of these embodiments, the timer value can be included in a series of nested information elements for a multi-SIM configuration. In some embodiments In some embodiments, when the UE transmits the indication but does not stop the timer, the second indication indicates one of the following: the time remaining on the output timer, the time elapsed since the UE sent the first indication, or the absolute time when the UE expects to enter the reduced-power state for the first PLMN. In other embodiments, when the UE stops the output timer and transmits the second indication, the second indication indicates one of the following: the first timer value, or the absolute time when the UE expects to enter the reduced-power state for the first PLMN. In some implementations, the example method may also include the operations in block 890, where the UE can enter the reduced-power state for the first PLMN in response to either of the following: timer expiration, and a message received from the second network node while the timer is running. More specifically, the message indicates that the UE should enter the reduced-power state for the first PLMN. In some implementations, the example method may also include the operations in blocks 850-860, where the UE may receive a timer value from the second network node while the timer is running, and refrain from resetting the timer based on the timer value received from the second network node. In some embodiments, the example method may also include the operations in block 880, where, based on the determination that the second network node does not support indications that the UEs want to enter a reduced-power state for the first PLMN, the UE may stop the timer and refrain from entering the reduced-power state. In some embodiments, the determination that the second network node does not support indications that the UEs want to enter a reduced-power state for the first PLMN may be based on one of the following: a message received from the second network node during the handover; or a message received from the second network in response to the second indication (for example, in block 870). In some implementations, the transfer in block 840 may include operations in sub-block 841, where the UE may 1890327 of 61 receive a handover command from the second network node. In such embodiments, the transmission of the second indication (for example, in block 870) may depend on the period between the transmission of the first indication (for example, in block 820) and the reception of the handover command (for example, in block 841) being less than a threshold. In some embodiments, the first indication is an initial indication that the UE intends to enter a reduced-energy state for the first PLMN, and the second indication is a subsequent indication that the UE intends to enter a reduced-energy state for the first PLMN. In some embodiments, the second indication is a subsequent indication by including a field that specifies a time at which the UE expects to enter the reduced-energy state for the first PLMN, while the first indication is an initial indication by omitting this field. In other embodiments, the second indication indicates that it is a later indication by including a field indicating an actual time when the UE expects to enter the reduced power state for the first PLMN, whereas the first indication indicates that it is an initial indication by including a field indicating a predetermined time when the UE expects to enter the reduced power state for the first PLMN. Furthermore, Figure 9 shows a flowchart of an example method (e.g., a procedure) for a first network node configured to operate on a first PLMN and to manage a UE configured with user credentials for a plurality of PLMNs, according to various embodiments of this disclosure. The example method can be implemented by a network node (e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc., or components thereof) as described elsewhere herein. The example method may include operations from block 920, where, while the UE is registered with the first PLMN and a second PLMN, and in a connected state for the first PLMN, the first network node may receive a first indication from the UE that the UE wants to enter a reduced-power state for the first PLMN. The example method may also include operations from block 930, where the first network node may send a request to a second network node in the first PLMN to transfer the UE to the second network node. The request includes a second indication that the UE wants to enter a reduced-power state for the first PLMN. The example method 1890327 of 61 may also include operations of blocks 940-950, where the first network node can receive from the second network node a confirmation of the handover request and send the UE a command to hand over to the second network node. In some implementations, the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some implementations, the example method may also include block 910 operations, where the first network node can send the UE a timer value in an RRCReconfiguration or RRCResume message. In some implementations, the timer value may be included in a series of nested information elements for a multi-SIM configuration. Furthermore, Figure 10 shows a flowchart of an example method (e.g., a procedure) for a second network node configured to operate on a first PLMN and to manage a UE configured with user credentials for a plurality of PLMNs, according to various embodiments of this disclosure. The example method can be implemented by a network node (e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc., or components thereof) as described elsewhere herein. The example method may include operations from block 1010, where the second network node can receive, from a first network node in the first PLMN, a request to transfer the UE to the second network node. The UE is registered in the first PLMN and a second PLMN and is in a connected state for the first PLMN. The example method may also include operations from block 1040, where the second network node can receive, from the UE or from the first network node, a second indication that the UE wants to enter the reduced power state for the first PLMN. The example method can also include operations from block 1050; based on the second indication, the second network node can determine a time when the UE expects to enter the reduced power state for the first PLMN. In some implementations, the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. In some embodiments, the second indication can be received from the first network node with the handover request. In such embodiments, the 1890327 of 61 operations from blocks 1010 and 1040 can be combined into a single operation. In other embodiments, the example method can also include operations in blocks 1020-1030, where the second network node can send the first network node an acknowledgment of the handover request and perform a handover procedure with the UE. In such embodiments, the second indication is received from the UE in block 1040 after the handover procedure is completed. In some of these embodiments, the second indication can be included in a UEAssistanceInformation message. In some of these embodiments, the implementation of the handover procedure with the UE in block 1030 may include the operations of subblock 1031, where the second network node may send a handover command to the UE. In such embodiments, the second indication may be received from the UE depending on whether the period between the following is less than a threshold: the transmission by the UE to the first network node of an initial indication that the UE wishes to enter a reduced-power state for the first PLMN (e.g., as described above with regard to Figures 8-9), and the receipt by the UE of the handover command sent in subblock 1031. In some embodiments, the second indication indicates one of the following: • a remaining time on a timer (e.g., exit timer, release timer, etc.) running on the UE; • an initial value for the timer that was set by the first network node; • a time since the UE sent the first network node a first indication that the UE wants to enter the reduced power state for the first PLMN; or • an absolute time at which the UE expects to enter the reduced power state for the first PLMN. In some implementations, the example method may also include the operations in block 1060, where the second network node may send one or more of the following to the UE before the specified time: a message indicating that the UE should enter the reduced-power state for the first PLMN; and a timer value to start a time on the UE. In some cases, the UE may refrain from applying the timer value, as discussed earlier in relation to Figure 8. 1890327 of 61 In some embodiments, the second network node indicates to the UE that the second network node accepts indications that the UE wants to enter a reduced power state for the first PLMN, based on one of the following: a message sent to the UE during the handover, or a message sent to the UE in response to the second indication received from the UE (for example, in block 1040). In some embodiments, the second indication reveals whether it is an initial indication that the UE intends to enter the reduced-power state for the first PLMN, or a subsequent indication that the UE intends to enter the reduced-power state for the first PLMN. In some embodiments, the second indication is indicated as a subsequent indication by including a field specifying a time at which the UE expects to enter the reduced-power state for the first PLMN, while the second indication is indicated as an initial indication by omitting this field. For example, the field could be the time at which the UE expects to enter the reduced-power state for the first PLMN. In other embodiments, the second indication indicates that it is a later indication by including a field indicating an actual time when the UE expects to enter the reduced power state for the first PLMN, whereas the second indication indicates that it is an initial indication by including a field indicating a predetermined time when the UE expects to enter the reduced power state for the first PLMN. Although various forms of realization are described above in terms of methods, apparatus, devices, computer-readable media, and receivers, the person of the middle-level trade will readily understand that such methods can be incorporated by various combinations of hardware and software into various systems, communication devices, computer devices, control devices, apparatus, non-transient computer-readable media, etc. Figure 11 shows an example of an 1100 communication system according to several embodiments. In this example, the 1100 communication system includes a 1102 telecom network comprising an 1104 access network, such as a radio access network (RAN), and a 1106 core network, which includes one or more 1108 core network nodes. The 1104 access network includes one or more 1110a and 1110b network nodes (one or more of which may be referred to generally as 1110 network nodes), or any other similar 3GPP access node or non-3GPP access point. The 1110 network nodes facilitate the direct or indirect connection of UEs, for example, by connecting UEs 1112a, 1890327 of 61 1112b, 1112c and 1112d (one or more of which may be generally referred to as UE 1112) to the core network 1106 through one or more wireless connections. Examples of wireless communication via a wireless connection include the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductive materials. Furthermore, in various embodiments, the 1100 communication system may include any number of wired or wireless networks, network nodes, UEs, and / or any other component or system that can facilitate or participate in the communication of data and / or signals, whether via cables or wireless connections. The 1100 communication system may include and / or interact with any type of communication, telecommunications, data, cellular, radio network, and / or other similar system. UE 1112s can be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with 1110 network nodes and other communication devices. Similarly, 1110 network nodes are arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 1112s and / or other network nodes or equipment in the 1102 telecommunications network to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management in the 1102 telecommunications network. In the example shown, the core network 1106 connects network nodes 1110 to one or more hosts, such as host 1116. These connections can be direct or indirect, through one or more intermediary networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 1106 includes one or more core network nodes (for example, core network node 1108) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, so the descriptions of these are generally applicable to the corresponding components of core network node 1108.Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF). 1890327 of 61 Authentication Server Function (AUSF), Subscription Identifier Hiding Function (SIDF), Unified Data Management (UDM), Security Perimeter Protection Proxy (SEPP), Network Exposure Function (NEF) and / or User Plane Function (UPF). Host 1116 may be owned or controlled by a service provider other than an operator or provider of the access network 1104 and / or the telecommunications network 1102, and may be operated by or on behalf of the service provider. Host 1116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as the retrieval and compilation of data on various environmental conditions detected by multiple UEs, analytics functionality, social networking, functions for controlling or interacting with remote devices, functions for an alarm and surveillance center, or any other similar function performed by a server. Overall, the 1100 communication system in Figure 11 enables connectivity between UEs, network nodes, and hosts. In this regard, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards including, but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long-Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future-generation standards (e.g., 6G); and wireless local area network (WLAN) standards, such as the 802 standards.11 (WiFi) of the Institute of Electrical and Electronics Engineers (IEEE); and / or any other appropriate wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide area network (LPWAN) standard such as LoRa and Sigfox. In some examples, the 1102 telecommunications network is a cellular network that implements standardized 3GPP features. Consequently, the 1102 telecommunications network can support network slicing to provide different logical networks to different devices connected to it. For example, the 1102 telecommunications network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to others. 1890327 of 61 other EUs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to even more EUs. In some examples, UE 1112 devices can be configured to transmit and / or receive information without direct human interaction. For example, a UE might be designed to transmit information to the 1104 access network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the 1104 access network. Additionally, a UE can be configured to operate in single, multiple, or multiple standard RAT mode. For example, a UE might operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC). In the example, concentrator 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and / or 1112d) and network nodes (e.g., network node 1110b). In some examples, concentrator 1114 may be a controller, router, content and analytics source, or any of the other communication devices described herein with respect to the UEs. For example, concentrator 1114 may be a broadband router that provides access to the core network 1106 for the UEs. As another example, concentrator 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. The commands or instructions may be received from the UEs, network nodes 1110, or via executable code, scripts, processes, or other instructions on concentrator 1114.As another example, the 1114 hub can be a data collector that acts as temporary storage for UE data and, in some implementations, can perform analysis or other data processing. As yet another example, the 1114 hub can be a content source. For instance, for a UE that is a VR headset, display, speaker, or other media delivery device, the 1114 hub can retrieve VR resources, video, audio, or other media or sensor-related data via a network node, which the 1114 hub then provides directly to the UE after performing local processing and / or adding additional local content. In yet another example, the 1114 hub acts as a proxy server or orchestrator for UEs, particularly if one or more of the UEs are low-power IoT devices. The 1114 hub can have a constant / persistent connection or 1890327 of 61 intermittent with network node 1110b. Hub 1114 may also allow a different communication scheme and / or schedule between hub 1114 and the UEs (e.g., UE 1112c and / or 1112d), and between hub 1114 and the core network 1106. In other examples, hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Additionally, hub 1114 may be configured to connect to an M2M service provider via the access network 1104 and / or to another UE via a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1110 while still connected through hub 1114 via a wired or wireless connection.In some embodiments, the 1114 concentrator can be a dedicated concentrator, meaning a concentrator whose primary function is to route communications to / from the UEs to / from the 1110b network node. In other embodiments, the 1114 concentrator can be a non-dedicated concentrator, meaning a device capable of routing communications between the UEs and the 1110b network node, but also capable of operating as a communication start and / or endpoint for certain data channels. Figure 12 shows a UE 1200 according to some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, mobile phone, cell phone, Voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, video game console or device, music storage device, players, handheld device, wireless endpoints, mobile station, tablets, laptop computer, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), wireless vehicle-mounted / integrated or vehicle-mounted device, etc.Other examples include any UE identified by the Third Generation Partnership Project (3GPP), which includes a Narrowband Internet of Things (NB-IoT) UE, a Machine-Type Communication (MTC) UE, and / or an Enhanced MTC (eMTC) UE. A UE can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for communication 1890327 of 61 Sidelink, Dedicated Short Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, a user equipment or UE does not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device intended for sale to and operation by a human user, which may or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended for sale to or operation by a human user, which may be associated with or operated for the benefit of a user (e.g., a smart energy meter). The UE 1200 includes processing circuitry 1202 that is operationally coupled via a bus 1204 to an input / output interface 1206, a power supply 1208, memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain UEs may use all or a subset of the components shown in Figure 12. The level of integration between components may vary from one UE to another. Furthermore, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The 1202 processing circuitry is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute instructions stored as machine-readable computer programs in memory 1210. The 1202 processing circuitry can be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs; general-purpose processors, such as a microprocessor or a digital signal processor (DSP), together with appropriate software; or any combination thereof. For example, the 1202 processing circuitry can include multiple central processing units (CPUs). In the example, the I / O interface 1206 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, and others. 1890327 of 61 output device or any combination thereof. An input device can allow a user to capture information on the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a scroll wheel, a directional pad, a touchpad, a smart card, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to detect user input. For example, a sensor can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use the same type of interface port as an input device.For example, a universal serial bus (USB) port can be used to provide both an input device and an output device. In one embodiment, the 1208 power supply is structured as a battery or battery pack. Other types of power supplies, such as an external power source (e.g., a wall outlet), a photovoltaic device, or a solar cell, can also be used. The 1208 power supply may further include power circuitry to supply power from the 1208 power supply itself and / or an external power source to the various parts of the UE 1200 via input circuitry or an interface such as a power cable. The power supply may, for example, be used to charge the 1208 power supply. The power circuitry may perform any formatting, conversion, or other modification to the power from the 1208 power supply to make the power suitable for the respective components of the UE 1200 to which it is supplied. Memory 1210 can be configured to include memory, such as random access memory (RAM), ROM, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash disk drives, etc. For example, memory 1210 includes one or more application programs 1214, such as an operating system, a web browser application, a widget, a device engine, or other application, and the corresponding data 1216. Memory 1210 can store, for use by UE 1200, 1890327 of 61 any of a variety of different operating systems or combinations of operating systems. The 1210 memory can be configured to include a number of physical disk drives, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, miniature storage drive, pen drive, small pen drive, high-density digital versatile disc (HD-DVD) optical drive, internal hard disk drive, Blu-ray optical drive, holographic digital data storage (HDDS) optical drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random-access memory (SDRAM), external microDIMM SDRAM, smart card memory, such as a tamper-proof module in the form of a universal integrated circuit card (UICC) that includes one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof.The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a SIM card. The 1210 memory can allow the UE 1200 to access instructions, application programs, and the like, stored on transient or non-transient memory media, to download or upload data. A manufactured item, such as one that uses a communication system, can be tangibly incorporated as or within the 1210 memory, which can be or comprise a device-readable storage medium. The processing circuitry 1202 can be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 can comprise one or more communication subsystems and can include or be communicatively coupled to an antenna 1222. The communication interface 1212 can include one or more transceivers used for communication, such as when communicating with one or more remote transceivers of another device capable of wireless communication (for example, another UE or a network node in an access network). Each transceiver can include a transmitter 1218 and / or a receiver 1220 appropriate for providing network communications (for example, optical, electrical, frequency allocations, etc.). In addition, the transmitter 1218 and receiver 1220 can be coupled to one or more antennas (for example, the antenna 1222) and can share circuit components, software, or firmware, or alternatively be implemented separately. In the illustrated form of realization, the communication functions of the The 1890327 of 61 interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networks (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc. Regardless of the sensor type, a UE can output data captured by its sensors via its 1212 communication interface through a wireless connection to a network node. Data captured by the sensors of one UE can be communicated wirelessly to a network node through another UE. The output can be periodic (e.g., once every 15 minutes if reporting the detected temperature), random (e.g., to equalize the reporting load from multiple sensors), triggered by an event (e.g., when humidity is detected and an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, motor, or switch connected to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the states of the actuator, motor, or switch can change. For example, the UE might comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input. A UE, when it takes the form of an Internet of Things (IoT) device, can be a device for use in one or more application domains, where these domains include, but are not limited to, urban wearable technology, extended industrial applications, and healthcare. Examples, but not limited to, such IoT devices include: 1890327 of 61 are a device that is integrated into: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather control device, a vehicle parking control device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable device for tactile augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device,A UE (Engineering Unit) in the form of an IoT device comprises circuitry and / or software depending on the intended application of the IoT device, in addition to other components as described in relation to the UE 1200 shown in Figure 12. As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE can be an M2M device, which, in a 3GPP context, can be called an MTC device. As a particular example, the UE can implement the 3GPP NB-IoT standard. In other cases, a UE can represent a vehicle, such as a car, bus, truck, ship, or airplane, or other equipment capable of monitoring and / or reporting its operational status and other functions associated with its operation. In practice, any number of UEs can be used together for a single use case. For example, a first UE could be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the drone's throttle (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the functionalities described above. 1890327 of 61 example, a UE could comprise the sensor and the actuator, and handle data communication for both the speed sensor and the actuators. Figure 13 shows a 1300 network node according to some embodiments. As used herein, a network node refers to equipment capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node B, evolved Node B (eNB), and gNB). Base stations can be classified according to the amount of coverage they provide (or, in other words, their transmit power level) and, therefore, depending on the coverage area, can be called femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes called remote radio heads (RRHs). Such remote radio units may or may not be integrated with an antenna, such as an integrated radio antenna. The parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include 5G multi-transmit point (multiTRP) access nodes, multi-standard radio equipment (MSR) such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-transmit / multi-cell coordination entities (MCE), operation and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved service mobile location centers (E-SMLC)) and / or minimizing test drives (MDT). The 1300 network node includes a 1302 processing circuitry, a 1304 memory, a 1306 communication interface, and a 1308 power supply. The 1300 network node may be composed of multiple physically separate components (for example, a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may 1890327 of 61 have their own respective components. In certain scenarios where the 1300 network node comprises multiple separate components (for example, BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique pair of NodeB and RNC may, in some cases, be considered a single separate network node. In some embodiments, the 1300 network node may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (for example, a separate 1304 memory for different RATs) and some components may be reused (for example, the same 1310 antenna may be shared by different RATs).The 1300 network node can also include multiple sets of the various components illustrated for different wireless technologies integrated into the 1300 network node, for example, GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-Wave, LoRaWAN, radio-frequency identification (RFID), or Bluetooth wireless technologies. These wireless technologies can be integrated on the same chip, on a different chipset, or on other components within the 1300 network node. The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any computing device, resource, or combination of hardware, software, and / or coded logic suitable and operable to provide, either alone or in conjunction with other network node components 1300, such as memory 1304, the functionality of the network node 1300. In some embodiments, the processing circuitry 1302 includes a system-on-a-chip (SoC). In some embodiments, the processing circuitry 1302 includes one or more of the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on the same chip or chipset, board, or unit. Memory 1304 can comprise any form of memory readable by 1890327 of 61 volatile or non-volatile computer, including, among others, persistent solid-state storage memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk drive), removable storage media (e.g., a flash disk drive, a compact disc (CD), or a digital video disc (DVD)), and / or any other computer-executable and / or device-readable volatile or non-volatile and non-transient memory device that stores information, data, and / or instructions that can be used by the processing circuitry 1302.Memory 1304 can store any suitable instruction, data, or information, including a computer program, software, or application comprising one or more logic, rules, code, tables, and / or other instructions (collectively denoted as the 1304a computer program product) that the 1302 processing circuitry can execute and that the 1300 network node can utilize. Memory 1304 can be used to store any calculations performed by the 1302 processing circuitry and / or any data received through the 1306 communication interface. In some embodiments, the 1302 processing circuitry and memory 1304 are integrated. The communication interface 1306 is used for wired or wireless communication of signals and / or data between a network node, an access network, and / or a UE (Enterprise Unit). As illustrated, the communication interface 1306 comprises ports / terminals 1316 for sending and receiving data, for example, to and from the network via a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318, which can be coupled to the antenna 1310 or, in certain embodiments, to a portion thereof. The radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 can be connected to an antenna 1310 and to the processing circuitry 1302. The radio front-end circuitry can be configured to condition the signals communicated between the antenna 1310 and the processing circuitry 1302.The radio front-end circuitry 1318 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 can convert the digital data into a radio signal with the appropriate bandwidth and channel parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal can then be transmitted via antenna 1310. Similarly, when receiving data, antenna 1310 can collect signals from... 1890327 of 61 radio, which are then converted into digital data by the radio front-end circuitry 1318. The digital data can be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 1300 does not include a separate radio front-end circuitry 1318, but the processing circuitry 1302 includes a radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or part of the RF transceiver circuitry 1312 is part of the communication interface 1306. Still in other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown). Antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 1310 may be coupled to radio front-end circuitry 1318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In certain embodiments, antenna 1310 is separate from network node 1300 and may be connected to network node 1300 via an interface or port. Antenna 1310, communication interface 1306, and / or processing circuitry 1302 can be configured to perform any receive operation and / or certain acquisition operations described herein as being performed by the network node. Any information, data, and / or signal can be received from a UE, another network node, and / or any other network equipment. Similarly, antenna 1310, communication interface 1306, and / or processing circuitry 1302 can be configured to perform any transmit operation described herein as being performed by the network node. Any information, data, and / or signal can be transmitted to a UE, another network node, and / or any other network equipment. The power supply 1308 provides power to the various components of the network node 1300 in a manner appropriate for the respective components (e.g., at the voltage and current level required by each component). The power supply 1308 may further comprise, or be coupled to, power management circuitry to supply the 1890327 of 61 network node 1300 components with power to perform the functionality described herein. For example, the network node 1300 can be connected to an external power source (e.g., the electrical grid, a wall outlet) via an input interface or circuitry, such as an electrical cable, through which the external power source supplies power to the power supply circuitry of the power supply 1308. As a further example, the power supply 1308 can comprise a power source in the form of a battery or battery pack that is connected to or integrated into the power supply circuitry. The battery can provide backup power in the event of a failure of the external power source. The implementations of the 1300 network node may include additional components beyond those shown in Figure 13 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionalities described herein and / or any functionality necessary to support the object described herein. For example, the 1300 network node may include user interface equipment to allow information input to the 1300 network node and to allow information output from the 1300 network node. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the 1300 network node. Figure 14 is a block diagram of a 1400 server, which may be an implementation of the 1116 server in Figure 11, according to several aspects described herein. As used herein, the 1400 host may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-deployed server, a distributed server, a virtual machine, a container, or processing resources in a server cluster. The 1400 host may provide one or more services to one or more UEs. The 1400 host includes a processing circuitry 1402 that is operationally coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power supply 1410, and a memory 1412. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described with respect to the devices in the preceding Figures, such as Figures 12 and 13, so that the descriptions of these are generally applicable to the corresponding components of the 1400 host. 1890327 of 61 Memory 1412 may include one or more software programs, including one or more host application programs 1414 and data 1416, which may include user data, for example, data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Implementations of the host 1400 UE may use only a subset of the components shown or all of them. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (for example, Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (for example, FLAC, Advanced Audio Coding (AAC), MPEG, G).711), including transcoding for multiple different UE classes, types, or implementations (e.g., phones, desktops, portable display systems, front-end display systems). Host application programs 1414 can also provide user authentication and license checks and can periodically report content status, routing, and availability to a central node, such as a device on or at the edge of a core network. Consequently, the server 1400 can select and / or specify a different server for free streaming services for a UE. Host application programs 1414 can support various protocols, such as HTTP Streaming Live (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Adaptive Dynamic Streaming over HTTP (MPEGDASH), etc. Figure 15 is a block diagram illustrating a 1500 virtualization environment in which the functions implemented by certain embodiments can be virtualized. In this context, virtualization means creating virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to any appliance described herein, or components thereof, and relates to an implementation in which at least some of the functionality is implemented as one or more virtual components.Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) deployed in one or more virtual environments hosted by one or more hardware nodes, such as a computing hardware device functioning as a network node, UE, core network node, or host. Furthermore, in the forms of... 1890327 of 61 implementation in which the virtual node does not require radio connectivity (e.g., a central network node or host), then the node can be fully virtualized. The 1502 applications (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein. Hardware 1504 includes processing circuitry, memory that stores software and / or instructions (collectively referred to as the 1504a computer program product) executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, an input / output interface, and so forth. The processing circuitry may run software to instantiate one or more 1506 virtualization layers (also referred to as hypervisors or virtual machine monitors (VMMs)), provide 1508a and 1508b VMs (one or more of which may be generally referred to as a 1508 VM), and / or perform any of the functions, features, and / or benefits described in connection with some embodiment described herein. The 1506 virtualization layer may present a virtual operating platform that appears to be network hardware to the 1508 VMs. The 1508 VMs comprise virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run using a corresponding 1506 virtualization layer. Different implementations of the 1502 virtual appliance instance can be deployed on one or more of the 1508 VMs, and these implementations can be carried out in various ways. Hardware virtualization is sometimes referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment onto industry-standard, high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises. In the context of NFV, a VM 1508 can be a software implementation of a physical machine that runs programs as if they were running on a non-virtualized physical machine. Each VM 1508, and the portion of VM 1504 hardware that runs that VM—whether dedicated hardware and / or hardware shared with other VMs—forms a separate virtual network element. Even within the context of NFV, the virtual network function is 1890327 of 61 responsible for managing specific network functions that run on one or more VM 1508 above hardware 1504 and corresponds to application 1502. Hardware 1504 can be deployed on a standalone network node using generic or specific components. Hardware 1504 can implement some functions through virtualization. Alternatively, hardware 1504 can be part of a larger hardware pool (for example, in a data center or CPE) where many hardware nodes work together and are managed through management and orchestration (1510), which, among other functions, oversees application lifecycle management (1502). In some embodiments, hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which can be coupled to one or more antennas.The radio units can communicate directly with other hardware nodes through one or more suitable network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, certain signals can be provided using a 1512 control system, which can alternatively be used for communication between the hardware nodes and the radio units. Figure 16 shows a communication diagram of a host 1602 communicating through a network node 1604 with a UE 1606 via a partially wireless connection according to several embodiments. Example implementations, according to various embodiments, of the UE (such as UE 1112a in Figure 11 and / or UE 1200 in Figure 12), a network node (such as network node 1110a in Figure 11 and / or network node 1300 in Figure 13), and a host (such as host 1116 in Figure 11 and / or host 1400 in Figure 14) discussed in the preceding paragraphs will be described below with reference to Figure 16. Like the 1400 host, the 1602 host implementations include hardware, such as a communication interface, processing circuitry, and memory. The 1602 host also includes software, which is stored on or accessible by the 1602 host and can be executed by the processing circuitry. The software includes a host application that can be operated to provide a service to a remote user, such as a 1606 UE connected via an over-the-top (OTT) 1650 connection spanning between the 1606 UE and the 1602 host. In providing the service to the remote user, a host application can provide 1890327 of 61 user data transmitted using OTT connection 1650. Network node 1604 includes hardware that allows it to communicate with host 1602 and UE 1606. The connection to 1660 can be direct or pass through a core network (such as core network 1106 in Figure 11) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet. Host 1606 also includes hardware and software, which are stored in or accessible by UE 1606 and can be executed by the UE's processing circuitry. The software includes a client application, such as a web browser or carrier-specific application, which can be used to provide service to a human or non-human user via UE 1606, with support from host 1602. On host 1602, a running host application can communicate with the running client application via OTT connection 1650, which terminates at UE 1606 and host 1602. When providing service to the user, the UE's client application can receive request data from the host application and provide user data in response to the request data. OTT connection 1650 can transfer both the request data and the user data.The UE client application can interact with the user to generate user data that it provides to the host application via the OTT 1650 connection. OTT connection 1650 can be extended via connection 1660 between host 1602 and network node 1604 and via wireless connection 1670 between network node 1604 and UE 1606 to provide a connection between host 1602 and UE 1606. Connection 1660 and wireless connection 1670, over which OTT connection 1650 is provided, have been drawn abstractly to illustrate communication between host 1602 and UE 1606 via network node 1604, without explicit reference to any intermediary devices and the precise routing of messages through these devices. As an example of data transmitted over the OTT connection 1650, in step 1608, host 1602 provides user data, which can be generated by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with host 1602 without explicit human interaction. In step 1610, host 1602 initiates a transmission carrying the user data to UE 1606. Host 1602 can initiate the transmission in response to... 1890327 of 61 A request is transmitted via UE 1606. The request can be generated by human interaction with UE 1606 or by the operation of the client application running on UE 1606. The transmission can pass through network node 1604, in accordance with the embodiments described throughout this disclosure. Accordingly, in step 1612, network node 1604 transmits to UE 1606 the user data that was carried in the transmission initiated by host 1602, in accordance with the embodiments described throughout this disclosure. In step 1614, UE 1606 receives the user data carried in the transmission, which can be carried out by a client application running on UE 1606 associated with the host application running on host 1602. In some examples, UE 1606 runs a client application that provides user data to host 1602. This user data can be provided in response to data received from host 1602. Consequently, in step 1616, UE 1606 can provide user data, which can be done by running the client application. When providing user data, the running client application can also consider user input received from the user through an input / output interface of UE 1606. Regardless of the specific method used to provide the user data, UE 1606 initiates, in step 1618, the transmission of the user data to host 1602 through network node 1604.In step 1620, according to the teachings of the embodiments described throughout this disclosure, network node 1604 receives user data from UE 1606 and initiates the transmission of the received user data to host 1602. In step 1622, host 1602 receives the user data carried in the transmission initiated by UE 1606. One or more of the various implementations improve the performance of OTT services provided to UE 1306 using the OTT connection 1350, where the wireless connection 1370 forms the final segment. More precisely, the implementations described herein can avoid and / or prevent misunderstandings and / or state mismatches between UEs and network nodes after handovers, thus facilitating the correct and efficient operation of UEs and networks. In this way, the implementations can reduce or prevent user data loss and / or excessive latency for a UE receiving and responding to network paging, which can occur when such misunderstandings and / or state mismatches take place. At a high level, the implementations 1890327 of 61 facilitate the more consistent operation of UEs and networks, thereby increasing the value of OTT services provided to UEs over such networks for end users and OTT service providers. In one example, host 1602 can collect and analyze factory status information. As another example, host 1602 can process audio and video data retrieved from a UE for use in map creation. As yet another example, host 1602 can collect and analyze real-time data to help manage traffic congestion (e.g., controlling traffic lights). As another example, host 1602 can store surveillance video uploaded by a UE. As another example, host 1602 can store or control access to multimedia content such as video, audio, VR, or AR, which it can stream, multicast, or unicast to UEs. As other examples, host 1602 can be used for energy pricing, remote monitoring of non-critical electrical loads to balance power generation needs, location services, and presentation services (such as diagram compilation, etc.).based on data collected from remote devices), or any other data collection, retrieval, storage, analysis and / or transmission function. In some examples, a measurement procedure may be provided to monitor data rate, latency, and other factors that one or more embodiments improve. An optional network functionality may also be provided to reconfigure the OTT 1650 connection between the host 1602 and the UE 1606 in response to variations in measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of the host 1602 and / or the UE 1606. In some embodiments, sensors (not shown) may be deployed on or in association with other devices through which the OTT 1650 connection passes. These sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above or by supplying values ​​of other physical quantities from which the software can compute or estimate the monitored quantities.Reconfiguration of the OTT connection 1650 may include message format, relay settings, preferred routing, etc.; the reconfiguration may not affect the operation of the network node 1604. Such procedures and functionalities may be known and implemented in the art. In certain embodiments, measurements may involve the 1890327 of 61 UE proprietary signaling that facilitates measurements of performance, propagation times, latency and the like, by means of host 1602. The measurements can be implemented so that the software causes messages, in particular empty or dummy messages, to be transmitted by means of the OTT connection 1650 while monitoring propagation times, errors, etc. The foregoing merely illustrates the principles of disclosure. Several modifications and alterations to the described embodiments will become apparent to those of intermediate skill in light of the teachings herein. It will therefore be appreciated that those of intermediate skill will be able to devise numerous systems, arrangements, and procedures that, while not explicitly shown or described herein, incorporate the principles of disclosure and may thus fall within its spirit and scope. Several example embodiments may be used together and interchangeably, as will be understood by those of intermediate skill. The term unit, as used herein, may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, solid-state and / or discrete logic devices, computer programs or instructions for carrying out the respective tasks, procedures, calculations, outputs and / or display functions, etc., such as those described herein. Any step, method, feature, function, or benefit disclosed herein may be implemented by means of one or more modules or functional units of one or more virtual appliances. Each virtual appliance may comprise a number of such functional units. These functional units may be implemented through processing circuitry, which may include one or more microprocessors or microcontrollers, in addition to other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, and so forth.The program code stored in memory includes program instructions to execute one or more telecommunications and / or data communications protocols, as well as instructions to carry out one or more of. 1890327 of 61 the techniques described herein. In some implementations, processing circuitry may be used to make the respective functional unit perform the corresponding functions in accordance with one or more embodiments of this disclosure. As described herein, the device and / or apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such a chip or chipset; however, this does not preclude the possibility that a device or apparatus's functionality, instead of being implemented in hardware, may be implemented as a software module, such as a computer program or a computer program product comprising executable portions of software code for execution on a processor. Furthermore, the functionality of a device or apparatus may be implemented by any combination of hardware and software. A device or apparatus may also be considered an assembly of multiple devices and / or apparatuses, whether operating cooperatively or independently of one another.Furthermore, devices and equipment can be deployed in a distributed manner within a system, provided that the functionality of the device or equipment is maintained. These and similar principles are considered to be common knowledge among mid-level professionals in the trade. Furthermore, the functions described herein as being performed by a wireless device or network node can be distributed among a plurality of wireless devices and / or network nodes. In other words, it is understood that the network node and wireless device functions described herein are not limited to being performed by a single physical device and, in fact, can be distributed among several physical devices. Furthermore, certain terms used in this disclosure, including the descriptive report, drawings, and example embodiments thereof, may be used synonymously in certain cases, including, but not limited to, data and information. It should be understood that while these and / or other expressions that may be synonymous with each other may be used synonymously herein, there may be instances where it is intended that such expressions not be used synonymously. In addition, to the extent that prior art knowledge has not been explicitly incorporated by reference herein, it is incorporated herein in its entirety. All cited publications are incorporated herein by reference. 1890327 out of 61 in total. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those normally understood by people of average skill level in the trade to whom this disclosure is addressed. It is further understood that terms used herein should be interpreted in a way that is consistent with their meaning in the context of this specification and the relevant technique, and not in an idealized or overly formal sense, unless expressly defined herein. Furthermore, certain terms used in this disclosure, including the descriptive report and drawings, may be used synonymously in some cases (e.g., data and information). It should be understood that while these terms (and / or other terms that may be synonymous) may be used synonymously herein, there may be instances where such terms are not intended to be used synonymously. The techniques and equipment described herein include, among others, the following listed examples: A1. A method for a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), wherein the method comprises: while registered on the first and second PLMN and connected to a first network node on the first PLMN, transmit to the first network node a first indication that the UE wants to enter a reduced power state for the first PLMN; Start an exit timer after transmitting the first indication; subsequently, perform a handover to a second network node on the first PLMN; and perform one or more of the following: transmit to the second network node a second indication that the UE wants to enter the reduced power state for the first PLMN; and stop the output timer. A2. The method according to embodiment A1, wherein the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. 1890327 of 61 A3. The method according to any of embodiments A1-A2, further comprising receiving a timer value from the first network node in an RRCReconfiguration message or an RRCResume message, wherein the output timer is started at the received timer value. A4. The method according to embodiment A3, wherein the timer value is included in a series of nested information elements for a multi-SIM configuration. A5. The method according to any of embodiments A3-A4, wherein when the UE does not stop the output timer, the second indication indicates one of the following: a time remaining on the output timer, a time since the UE sent the first indication, or an absolute time at which the UE expects to enter the reduced power state for the first PLMN. A6. The method according to any of embodiments A3-A4, wherein when the UE stops the output timer, the second indication indicates one of the following: the timer value or an absolute time at which the UE expects to enter the reduced power state for the first PLMN. A7. The method in accordance with any of embodiments A1-A6, wherein at least one of the first indication and the second indication is included in a UEAssistanceInformation message. A8. The method according to any of embodiments A1-A7, further comprising entering the reduced energy state for the first PLMN in response to any of the following: A message received from the second network node while the exit timer is running, the message indicates that the UE should enter the reduced power state for the first PLMN; and the expiration of the exit timer. A9. The method according to any of embodiments A1-A8, further comprising: Receive a timer value from the second network node while the timer is running, and refrain from resetting the timer based on the timer value received from the second network node. A10. The method according to any of embodiments A1-A9, further comprising, based on the determination that the second network node does not admit indications that the UEs want to enter an energy state 1890327 of 61 reduced for the first PLMN, stop the output timer and refrain from entering the reduced power state. A11. The method according to embodiment A10, wherein the determination that the second network node does not support indications that the UEs want to enter a reduced energy state for the first PLMN is based on one of the following: a message received from the second network node during the handover; or a message received from the second network node in response to the second indication. A12. The method according to any of the embodiments A1-A11, wherein: The implementation of the handover to the second network node involves receiving a handover command from the second network node; and the transmission of the second indication is based on the period between the transmission of the first indication and the reception of the handover command being less than a threshold. A13. The method according to any of embodiments A1-A12, wherein: The first indication is an initial indication that the UE wants to enter a reduced energy state for the first PLMN; and the second indication is a subsequent indication that the UE wants to enter a reduced energy state for the first PLMN. A14. The method according to embodiment A13, wherein: The second indication includes a first field, which indicates that it is a later indication; and the first indication excludes the first field, which indicates that it is an initial indication. A15. The method according to embodiment A14, wherein the first field is a time at which the UE expects to enter the reduced energy state for the first PLMN. A16. The method according to embodiment A13, wherein: The second indication includes a real-time time that the UE expects to enter the reduced power state for the first PLMN, and the first indication includes a predetermined time that the UE expects to enter the reduced power state for the first PLMN. 1890327 of 61 B1. A method for a first network node, of a first public land mobile network (PLMN), to manage a user equipment (UE) configured with user credentials for a plurality of PLMNs, wherein the method comprises: While the UE is registering on the first PLMN and a second PLMN, and connecting to the first network node on the first PLMN, receive from the UE a first indication that the UE wants to enter a reduced power state for the first PLMN; send, to a second network node in the first PLMN, a request to transfer the UE to the second network node, wherein the request includes a second indication that the UE wants to enter the reduced power state for the first PLMN; receive, from the second network node, a confirmation of the handover request; and send, to the UE, a command to hand over to the second network node. B2. The method according to embodiment B1, wherein the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. B3. The method in accordance with any of embodiments B1-B2, further comprising sending to the UE a timer value in an RRCReconfiguration message or an RRCResume message. B4. The method according to embodiment B3, wherein the timer value is included in a series of nested information elements for a multi-SIM configuration. B5. The method in accordance with any of the embodiments B1-B4, wherein the first indication is included in a UEAssistanceInformation message. C1. A method for a second network node, of a first public land mobile network (PLMN), to manage a user equipment (UE) configured with user credentials for a plurality of PLMNs, wherein the method comprises: to receive, from a first network node in the first PLMN, a request to transfer the UE to the second network node, where the UE is registered in the first PLMN and in a second PLMN and connects to the first PLMN through the first network node; to receive, from the UE or from the first network node, a second indication of 1890327 of 61 that the UE wants to enter the reduced energy state for the first PLMN; and based on the second indication, determine a time when the UE expects to enter the reduced energy state for the first PLMN. C2. The method according to embodiment C1, wherein the reduced energy state for the first PLMN is one of the following: RRC_IDLE; RRC_INACTIVE; or RRC_IDLE with stored context. C3. The method in accordance with any of the embodiments A1-A2, wherein the second indication is received from the first network node with the transfer request. C4. The method according to any of embodiments A1-A2, further comprising: send, to the first network node, a confirmation of the handover request; and carry out a handover procedure with the UE, wherein the second indication is received from the UE after completing the handover procedure. C5. The method in accordance with embodiment C4, wherein the second indication is included in a UEAssistanceInformation message. C6. The method according to any of embodiments C4-C5, wherein: Implementing the handover procedure with the UE involves sending a handover command to the UE; and the second indication is received from the UE depending on whether the period between the following is less than a threshold: the previous transmission from the UE of an initial indication to the first network node; and the UE's reception of the handover command. C7. The method according to any of embodiments C1-C6, wherein the second indication indicates one of the following: a remaining time on an output timer that is running on the UE, an initial value for the output timer that was set by the first network node, a time since the UE sent the first network node a first indication that the UE wants to enter the reduced power state 1890327 of 61 for the first PLMN, or an absolute time at which the UE expects to enter the reduced energy state for the first PLMN. C8. The method in accordance with any of the embodiments C1-C7, further comprising sending to the UE, before the specified time, a message indicating that the UE should enter the reduced power state for the first PLMN. C9. The method in accordance with any of embodiments C1-C8, further comprising sending to the UE, before the specified time, a timer value to initialize an output timer in the UE. C10. The method in accordance with any of embodiments C1-C9, wherein the second network node indicates to the UE that it accepts indications that the UEs wish to enter a reduced energy state for the first PLMN based on one of the following: a message sent to the EU during the handover; or a message sent to the EU in response to the second indication received from the EU. C11. The method according to any of embodiments C1-C10, wherein the second indication indicates that it is one of the following: an initial indication that the UE wants to enter the reduced energy state for the first PLMN; or a subsequent request that the UE wants to enter the reduced energy state for the first PLMN. C12. The method according to embodiment C11, wherein: The second indication indicates that it is a subsequent indication depending on whether a first field is included; and the second indication indicates that it is an initial indication depending on whether the first field is included. C13. The method according to embodiment C12, wherein the first field is the time at which the UE expects to enter the reduced energy state for the first PLMN. C14. The method according to embodiment C11, wherein: The second indication indicates that it is a subsequent indication based on the real-time indication at which the UE expects to enter the reduced power state for the first PLMN, and 1890327 of 61 The second indication indicates that it is an initial indication based on the indication of a predetermined time at which the UE expects to enter the reduced power state for the first PLMN. D1. A user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), wherein the method comprises: communication interface circuitry configured to communicate with network nodes in the first and second PLMN; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to carry out operations corresponding to the methods according to any of embodiments A1-A16. D2. A user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), wherein the UE is further configured to carry out operations corresponding to the methods in accordance with any of embodiments A1-A16. D3. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by the processing circuitry of one configured with user credentials for a plurality of public land mobile networks (PLMN), configure the UE to carry out operations corresponding to methods in accordance with any of embodiments A1-A16. D4. A computer program product comprising computer-executable instructions that, when executed by the processing circuitry of one configured with user credentials for a plurality of public land mobile networks (PLMN), configure the UE to carry out operations corresponding to methods in accordance with any of embodiments A1-A16. E1. A first network node, of a first public land mobile network (PLMN), arranged to manage a user equipment (UE) configured with user credentials for a plurality of PLMNs, wherein the first network node comprises: communication interface circuitry configured to communicate with the UE and with a second network node of the first PLMN; and processing circuitry operationally coupled to the circuitry of 1890327 of 61 communication interface, whereby the processing circuitry and the communication interface circuitry are configured to carry out operations corresponding to the methods according to any of the embodiment forms B1-B5. E2. A first network node, of a first public land mobile network (PLMN), arranged to manage a user equipment (UE) configured with user credentials for a plurality of PLMNs, wherein the first network node is further arranged to carry out operations corresponding to the methods in accordance with any of embodiments B1-B5. E3. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by the processing circuitry of a first network node disposed to manage a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), configure the first network node to carry out operations corresponding to the methods in accordance with any of embodiments B1-B5. E4. A computer program product comprising computer-executable instructions that, when executed by the processing circuitry of a first network node arranged to manage a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), configure the first network node to carry out operations corresponding to methods in accordance with any of embodiments B1-B5. F1. A second network node, of a first public land mobile network (PLMN), arranged to manage a user equipment (UE) configured with user credentials for a plurality of PLMNs, wherein the second network node comprises: communication interface circuitry configured to communicate with the UE and with a first network node of the first PLMN; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to carry out operations corresponding to the methods in accordance with any of embodiments C1-C14. F2. A second network node, of a first public land mobile network (PLMN), arranged to manage a user equipment (UE) configured with credentials of 1890327 of 61 user for a plurality of PLMN, wherein the second network node is further arranged to carry out operations corresponding to the methods in accordance with any of the embodiment forms C1-C14. F3. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by the processing circuitry of a second network node disposed to manage a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), configure the second network node to carry out operations corresponding to the methods in accordance with any of embodiments C1-C14. F4. A computer program product comprising computer-executable instructions that, when executed by the processing circuitry of a second network node disposed to manage a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMN), configure the second network node to carry out operations corresponding to methods in accordance with any of embodiments C1-C14. 1890327 of 61 Federico Aulmann - 20219535830 Digitally signed by PORTALTRAM ITES - INPI Date: 2022.07.18 16:27:34 -03:00 Reason: Digitally Signed by the INPI Location: Buenos Aires, Argentina 1890327

Claims

1. A method for a user equipment (UE) configured with user credentials for a plurality of public land mobile networks (PLMNs), characterized in that it comprises: while registered to the first and second PLMNs and in a connected state for the first PLMN, transmitting (820) to a first network node in the first PLMN a first indication that the UE wishes to enter a reduced power state for the first PLMN; starting (830) a timer after transmitting the first indication; subsequently carrying out (840) a handover to a second network node in the first PLMN; and carrying out (870) one or more of the following: transmitting to the second network node in the first PLMN a second indication that the UE wishes to enter the reduced power state for the first PLMN; and stopping the timer. 19 Claims follow