Improved real-time call performance during dynamic interface handover

Abstract

A user equipment (UE) configured to determine that the UE has an active call via a macro cellular network, where the UE includes a macro cellular network subscriber identity module (SIM) associated with the macro cellular network; determining that the UE has entered a geo-fenced area associated with the private cellular network; determining a first signal quality of the macro cellular network based on the first signal measurement of the macro cellular network; and omitting enabling a private cellular network SIM associated with the private cellular network when the first signal quality of the macro cellular network satisfies a predetermined threshold, or enabling a private cellular network SIM associated with the private cellular network when the signal quality of the macro cellular network does not satisfy the predetermined threshold.

Description

Background Technology

[0001] Modern user equipment (UEs) may encounter an increasing number of network deployments as they move across geographical areas. A UE may have multiple subscriber identity modules (SIMs) associated with various types of networks, such as macro networks deployed by mobile network operators (MNOs) and private networks such as citizen broadband radio service (CBRS) networks deployed by MNOs or other private entities. Additionally, Voice over Wi-Fi (VoWiFI) introduces further complexity to UE data handover. UEs that fail to perform seamless data handover between these various network types will experience data interruptions, leading to poor user experience and dropped calls. Improvements to data handover (i.e., transfer of data) are needed in this area. Summary of the Invention

[0002] Some exemplary embodiments relate to an apparatus for a user equipment (UE) having processing circuitry configured to: determine that the UE has an active call via a macrocell network, wherein the UE includes a macrocell network subscriber identity module (SIM) associated with the macrocell network; determine that the UE has entered a geofence area associated with a private cellular network; determine a first signal quality of the macrocell network based on a first signal measurement of the macrocell network; and, when the first signal quality of the macrocell network meets a predetermined threshold, omit enabling the private cellular network SIM associated with the private cellular network, or enable the private cellular network SIM associated with the private cellular network when the signal quality of the macrocell network does not meet the predetermined threshold.

[0003] Other exemplary embodiments relate to an apparatus for a user equipment (UE) having processing circuitry configured to: determine that the UE has an active call via a private cellular network, wherein the UE has a private cellular network subscriber identity module (SIM) associated with the private cellular network and a macro cellular network SIM associated with a macro cellular network, wherein the macro cellular network SIM is enabled and non-service; determine that the UE has exited a geofenced area associated with the private cellular network; perform signal measurements of the macro cellular network and the private cellular network; and perform a cellular data hand-out from the private cellular network to the macro cellular network based on the signal measurements, wherein the private cellular network SIM remains enabled after the cellular data hand-out.

[0004] A further exemplary embodiment relates to an apparatus for a user equipment (UE) supplied with cellular data by a private cellular network, the apparatus having processing circuitry configured to: determine an upcoming calendar event associated with a voice call; predict that the UE will leave the coverage area of ​​the private cellular network before the voice call ends; determine, based on signal measurements of a macrocell network, that the signal quality of the macrocell network meets a predefined threshold; and switch the UE from being supplied with cellular data by the private cellular network to being supplied with cellular data by the macrocell network based on the prediction that the UE will leave the coverage area of ​​the private cellular network and the signal measurements of the macrocell network.

[0005] Additional exemplary embodiments relate to an apparatus for a user equipment (UE) having processing circuitry configured to: when the UE is connected to a first cellular network, determine that the UE is preparing to participate in a voice call; determine the overhead associated with the UE performing the voice call on a second cellular network; determine a first signal quality associated with the first cellular network; determine a second signal quality associated with the second cellular network; and select either the first cellular network or the second cellular network to perform the voice call based on the first signal quality, the second signal quality, and the overhead, wherein when the second cellular network is selected, the UE switches to the second cellular network before connecting to the voice call. Attached Figure Description

[0006] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0007] Figure 2 Exemplary UEs according to various exemplary implementations are shown.

[0008] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0009] Figure 4 A first user mobility scenario is illustrated according to various exemplary implementations.

[0010] Figure 5 A second geofence diagram is shown according to various exemplary implementation schemes.

[0011] Figure 6 A first method for delaying data switching upon entering a geofence is illustrated according to various exemplary embodiments.

[0012] Figure 7 A second method for delaying data switching when exiting a geofence is illustrated, according to various exemplary embodiments.

[0013] Figure 8 A third method for delayed data switching based on signal strength hand-in / hand-out is shown according to various exemplary embodiments.

[0014] Figure 9 Methods that can be performed when the UE terminates an active call and a delayed handover is used, according to various exemplary embodiments, are shown.

[0015] Figure 10 Methods for preemptive cut-out according to various exemplary embodiments are shown.

[0016] Figure 11 Methods for recovering operation from incorrect predictive cuts are shown according to various exemplary embodiments.

[0017] Figure 12 The call flow for preemptive handover is illustrated according to various exemplary embodiments.

[0018] Figure 13 The call flow for timely handover is illustrated according to various exemplary implementations. Detailed Implementation

[0019] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein the same elements are given the same reference numerals. The exemplary embodiments relate to improved UE behavior for various mobility scenarios.

[0020] Exemplary embodiments are described with reference to user equipment (UE). However, references to the UE are provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0021] Exemplary implementations are also described with reference to macro networks as 5G New Radio (NR) networks. However, it should be understood that exemplary implementations can also be implemented in other types of macro networks, including but not limited to LTE networks, future evolutions of cellular protocols (e.g., 5G Advanced, 6G networks), or any other type of network.

[0022] Exemplary implementations are also described with reference to private or enterprise networks as Citizens Broadband Radio Service (CBRS) networks. However, it should be understood that exemplary implementations can also be implemented in other types of private or enterprise networks, such as mobile virtual network operator (MVNO) networks or geographically defined cellular networks comprised of one or more macro networks.

[0023] Throughout this description, the terms "cut-out" and "cut-in" will be used. In the following description, the term "cut-out" refers to a scenario where the UE switches from a private or enterprise network (e.g., a CBRS network) to a macro network. Similarly, the term "cut-in" refers to a scenario where the UE switches from a macro network to a private or enterprise network.

[0024] Throughout this disclosure, it will be described that the UE may be in an active call. An active call should be understood as either a voice call or a data call.

[0025] When a UE switches from one type of network (e.g., from a macro network to a private network or vice versa), data interruptions may occur for various reasons. These reasons include, but are not limited to: enabling the Enterprise Subscriber Identity Module (SIM) when entering a geofence, permanent Dual SIM Dual Standby (DSDS) handover to an Enterprise SIM, handover out to a macro SIM, handover in to an Enterprise SIM, and permanent DSDS handover to a macro SIM when exiting a geofence. These scenarios are further described below.

[0026] A typical DSDS UE has a separate protocol stack associated with each SIM on the UE. For example, a UE might have a SIM associated with a macro network and a SIM associated with an enterprise network. A typical DSDS implementation uses a shared radio frequency (RF) chain shared between the two protocol stacks. Additionally, a radio time-division scheduler handles time-division operations between the two protocol stacks. This implementation is prone to data pauses when the scheduler switches the UE from one protocol stack to another. The following will be discussed in relation to... Figure 4 and Figure 5 Provide a further description of the causal relationship of the data pause.

[0027] Exemplary implementations describe enhanced operations and logic for UE behavior in various mobility scenarios, including entering and leaving geographic areas associated with enterprise networks. Exemplary implementations provide a method for a UE to determine when to switch from a macro cellular network to an enterprise cellular network and vice versa.

[0028] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is illustrated. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device (including connected vehicles), etc. It should also be understood that a practical network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only one example of a UE 110 is provided.

[0029] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is 5G NR Radio Access Network (RAN) 120. However, it should be understood that UE 110 can also communicate with other types of networks (e.g., 5G cloud RAN, next-generation RAN (NG-RAN), legacy cellular networks, etc.), and UE 110 can also communicate with the network via a wired connection. Referring to an exemplary implementation, UE 110 can establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NR RAN 120.

[0030] 5G NR RAN 120 can be part of a cellular network that can be deployed by a network operator (e.g., Verizon, AT&T, T-Mobile, etc.). RAN 120 can include cells or base stations configured to transmit and receive services from UEs equipped with appropriate cellular chipsets. In this example, 5G NR RAN 120 includes gNB 120A. However, the reference to gNB is provided merely for illustrative purposes, and any appropriate base station or cell can be deployed (e.g., Node B, eNodeB, HeNB, eNB, gNB, gNodeB, macro cell, micro cell, small cell, femtocell, etc.).

[0031] Those skilled in the art will understand that any relevant procedures can be performed for UE 110 to connect to 5G NR RAN 120. For example, as described above, 5G NR RAN 120 can be associated with a specific network operator where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR RAN 120, UE 110 can send the corresponding credential information to associate with 5G NR RAN 120. More specifically, UE 110 can be associated with a specific cell (e.g., gNB 120A).

[0032] Network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 manages traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a collection of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 in communicating with various networks.

[0033] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory layout 210, display device 215, input / output (I / O) device 220, transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing limited power, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, sensors for detecting the status of UE 110, etc.

[0034] Processor 205 may be configured to execute multiple engines of UE 110. For example, an engine may include handover engine 235 for performing operations related to determining networking conditions, predicting handover and handover, and performing handover operations based on that determination.

[0035] The engines described above, as applications (e.g., programs) executed by processor 205, are merely exemplary. The functionality associated with these engines may also be represented as separate, combined components of UE 110, or as modular components coupled to UE 110, such as integrated circuits with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is split between two or more processors, such as a baseband processor and an application processor. Exemplary implementations may be implemented according to any of these or other configurations of the UE.

[0036] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling a user to input data. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen).

[0037] Transceiver 225 may be a hardware component configured to establish a connection with 5G-NR RAN 120. Therefore, transceiver 225 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information used to implement any of the methods described herein. Processor 205 may be operatively coupled to transceiver 225 and configured to receive signals from and / or transmit signals to transceiver 225. Processor 205 may be configured to encode and / or decode signals (e.g., signaling from a base station in the network) for use in implementing any of the methods described herein.

[0038] Figure 3 An exemplary base station 300 according to various exemplary embodiments is shown. Base station 300 may represent any other access node that gNB 120A or UE 110 can use to establish connections and manage network operations.

[0039] Base station 300 may include processor 305, memory arrangement 310, input / output (I / O) devices 315, transceiver 320, and other components 325. These other components 325 may include, for example, audio input devices, audio output devices, batteries, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices and / or power sources, etc.

[0040] The processor 305 may be configured to execute multiple engines of the base station 300. For example, an engine may include a handover engine 330 for performing operations related to receiving SIM registration messages from the UE 110.

[0041] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300.

[0042] Transceiver 320 may be a hardware component configured to exchange data with UE 110 and any other UE in network arrangement 100. Transceiver 320 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Therefore, transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs. Transceiver 320 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information used to implement any of the methods described herein. Processor 305 may be operatively coupled to transceiver 320 and configured to receive signals from and / or transmit signals to transceiver 320. Processor 305 may be configured to encode and / or decode signals (e.g., signaling from a UE) for use in implementing any of the methods described herein.

[0043] Figure 4 A first user mobility scenario 400 according to various exemplary embodiments is illustrated. User mobility scenario 400 illustrates a simplified scenario of a UE (e.g., UE 110) entering or leaving a geofenced area associated with an enterprise network 406. Macro network 410 can be understood to cover the immediate area outside (at least) geofence 404. Macro network may also cover the area inside geofence 404. In this example, UE 110 may include a macro SIM associated with (e.g., deployed by an MNO) macro network 410 and an enterprise SIM associated with enterprise network 406.

[0044] In scenario 402, UE 110 moves from a first location to a second location. In the first scenario, UE 110 moves from a first location outside geofence 404 to a second location inside geofence 404. In the second scenario, UE 110 moves from a first location inside geofence 404 to a second location outside geofence 404. Geofence 404 defines the edge of enterprise deployment 406. It is not required that geofence 404 coincide with the exact boundary of the enterprise network 406 signal. For example, geofence 404 may be smaller or larger than the total area where UE 110 can communicate with enterprise network 406.

[0045] In the first scenario, when entering an area within geofence 404, UE 110 can switch its data services from macro network 410 to enterprise network 406. This can also be referred to as a cut-in.

[0046] In the second scenario, when leaving the area within geofence 404, UE 110 can switch its data services from enterprise network 406 to macro network 406. This can also be referred to as a cut-out.

[0047] Figure 5A first user mobility scenario 500 according to various exemplary implementations is illustrated. Similar to... Figure 4 UE110 is characterized by both macro SIM and enterprise SIM. UE110 can be understood as initially being served by macro network 512. In some scenarios, geofence 502 may be larger than the coverage area of ​​enterprise network 506. This can be a problem because UE110 may attempt to switch over when entering the area of ​​geofence 502, but the signal conditions of enterprise network 506 may be worse than those of the already served macro network 512. This may lead to data interruptions and a poor user experience. Enterprise edge coverage area 504 can be understood as an area where it is advantageous to switch UE110 from macro network 512 to enterprise network 506.

[0048] In the scenario shown in geofence diagram 500, UE 110 can enter geofence 502, but will not immediately perform a handover to enterprise network 506. Instead, UE 110 can continue to perform signal measurements on enterprise network 506 and can perform handover 510 only based on signal quality meeting a predetermined threshold. A similar scenario may occur in reverse when UE 110 moves out of the coverage area of ​​enterprise network 506 but remains within geofence 502. When the signal of enterprise network 506 deteriorates with increasing radius from the enterprise deployment center, UE 110 can switch to macro network 512 via handover based on signal measurements on macro network 512 meeting a predetermined threshold.

[0049] In the scenario described above, UE 110 may experience data pauses for various reasons. The following provides some examples of why data pauses might occur. This is not an exhaustive list of reasons for data pauses, but merely some exemplary causes; that is, exemplary implementations can address issues related to data pauses occurring for different reasons.

[0050] When entering a geofence, UE 110 may experience data interruptions because enabling Enterprise SIM may reduce radio resources available for macro SIMs that are still in service, potentially leading to packet loss. Enabling Enterprise SIM may also cause UE 110 to perform additional scanning and signaling, requiring additional radio resources. Additionally, data interruptions may occur because UE 110's IP address changes during data handover, and real-time applications need time to adapt to the new IP address.

[0051] When exiting a geofence, the UE 110 may experience data pauses because disabling the enterprise SIM may result in an update to the macro SIM capability. This could cause baseband protocol signaling, which could lead to data packet pauses. Additionally, data pauses may occur because the UE 110's IP address changes during data handover, and real-time applications require time to adapt to the new IP address.

[0052] When UE 110 is within a geofence but before switching to the enterprise network, data pauses may occur due to the change in the IP address at UE 110, and incoming outdated packets from the previous network (e.g., the macro network) may cause signaling pauses on the enterprise network.

[0053] In other examples, when UE 110 switches from dual-SIM mode to single-SIM mode, UE 110 may initiate a Tracking Area Update (TAU), which may use resources and cause data interruption.

[0054] In summary, data interruptions may occur when a UE changes from single-SIM mode to dual-SIM mode, when the enterprise network geofence is larger than the coverage area of ​​a given cell, when an application adapts to a new IP address, or when outdated downlink packets arrive from a previously served network.

[0055] Exemplary implementations address issues related to data interruptions by providing various ways to switch between macro networks and private networks (e.g., hand-in or hand-out) and / or between various macro networks when the UE is equipped with more than one SIM.

[0056] In a first aspect of the exemplary implementation, this document discloses operations and logic for deferring data handover. Deferred data handover aims to maintain live calls on the current network for as long as possible, which can lead to improved call holding and an improved user experience by avoiding unnecessary data interruptions associated with handovers of cellular data from a first network to a second network (e.g., from a macro network to an enterprise network or vice versa).

[0057] Figure 6 A first method 600 for deferring data handover upon entering a geofence, according to various exemplary embodiments, is illustrated. As described above, typically when UE 110 enters a geofence associated with an enterprise network and UE 110 is equipped with a SIM for the enterprise network, the UE will perform a handover and switch to the enterprise network. However, as will be described in more detail below, exemplary embodiments provide a way to defer the handover to the enterprise network to avoid a poor user experience due to data interruptions associated with the handover. Reference will be made to... Figure 5 To describe the UE 110 in the scenario Figure 6 The method. However, it should be understood that UE 110 can also be in Figure 4 In the scenario or in any other scenario associated with entering a geofenced area.

[0058] As shown in 601, Figure 6 An example could be a scenario where UE 110 is currently connected to a macro network and is making an active call via the macro network. In 604, UE 110 can enter an enterprise geofence; for example, UE 110 enters geofence 502, as... Figure 5 As shown. When UE 110 enters a geofence, UE 110 can determine whether the call is still active. For example, UE 110 can determine whether the call is still active based on identifiers such as certain application programming interfaces (APIs) being used by the application, the application category, and the business pattern consistent with the call. In this example, it can be assumed that the call remains active when UE 110 enters the geofence.

[0059] In step 606, UE 110 determines the macro network signal quality. This determination can use any number of techniques, such as signal strength, link quality, cell load, etc., to evaluate the quality of the macro network connection. If the macro network connection is determined to be good (e.g., the macro network signal quality meets one or more predetermined thresholds related to signal quality), UE 110 remains on the macro network to continue the active call. This can be understood as "postponing" the handover to the enterprise network (e.g., UE 110 does not connect to the enterprise network in step 608). This can be advantageous in avoiding data interruptions that may occur during data handover from the macro network to the enterprise network, which could impact the user experience of the active call.

[0060] Although Figure 6 The example shows UE 110 determining the macro network signal quality in a single step in step 606, but when UE 110 is within a geofence, connected to a macro network, and participating in an active call, UE 110 will continuously check the macro network signal quality. Although in Figure 6 Not shown, but when the active call ends, UE 110 can switch to the enterprise network, for example, by performing a handover. At this time, UE 110 can interrupt the determination of the signal quality of the macro network.

[0061] Returning to 606, it can be assumed that while the call is still active, UE 110 determines that the macro network signal quality is poor (e.g., the macro network signal quality does not meet one or more predetermined thresholds related to signal quality). When this occurs, in 610, UE 110 can enable the enterprise SIM. In 612, UE 110 registers the enterprise SIM with the enterprise network.

[0062] In section 614, UE 110 determines whether to recommend a cellular data handover from the macro network to the enterprise network based on a comparison of measurements of macro network signal quality and enterprise network signal quality. This comparison assesses many factors, such as signal strength, link quality, and cell load. This assessment does not need to be based on the same metrics and thresholds used for the determination in section 606. Furthermore, although this is described as a comparison, section 614 can be made based on the signal quality of either the macro network or the enterprise network without comparing the signal quality of the other network.

[0063] If it is determined that 614 does not recommend switching to the enterprise network, then UE 110 remains on the macro network. Similarly, this evaluation may be underway while UE 110 is within a geofence and remains connected to the macro network. If it is determined that 614 recommends switching to the enterprise network, the method proceeds to 616, and UE 110 switches its cellular data to the enterprise SIM.

[0064] exist Figure 6 Various means of calculating and evaluating connectivity quality are possible throughout this disclosure. Those skilled in the art will recognize that predetermined quality thresholds can be defined by the original equipment manufacturer (OEM), MNO, and / or other operators. In other words, the quality thresholds and associated evaluation criteria do not need to be any specific values. These are left to the operators to implement.

[0065] Figure 7 A second method 700 for deferring data handover upon exiting a geofence, according to various exemplary embodiments, is illustrated. As described above, typically when UE 110 exits a geofence associated with an enterprise network, UE 110 will perform a handover and switch to a macro network. As will be described in more detail below, exemplary embodiments provide a way to defer disabling the enterprise's SIM to avoid a poor user experience due to data interruptions associated with UE 110 switching from dual-SIM mode to single-SIM mode. Reference will be made to... Figure 4 The second scenario describes UE 110 (e.g., UE 110 exits geofence 404). Figure 7 The method. However, it should be understood that UE 110 can also be in Figure 5 In the scenario of leaving the geofenced area or in any other scenario associated with leaving the geofenced area.

[0066] As shown in 701, Figure 7 An example could be a scenario where UE 110 is currently connected to an enterprise network and is making an active call over that network. In 704, UE 110 leaves the enterprise geofence, for example, UE 110 leaves geofence 404, as... Figure 4As shown. When UE 110 leaves the geofence, UE 110 can determine whether the call is still active. The above describes an example of how UE 110 determines whether a call is still active. In this example, it can be assumed that the call remains active when UE 110 leaves the geofence.

[0067] In some scenarios, even at geofence boundaries, the enterprise network can still provide feasible connectivity to UE 110. Therefore, in 706, UE 110 determines whether to recommend a cellular data handover (e.g., handover) from the enterprise network to the macro network. Similar to Reference Figure 6 The determination 614 described herein may include a comparison of measurements of macro network signal quality and enterprise network signal quality. This comparison may assess many factors, such as signal strength, link quality, and cell load. Similarly, although this is described as a comparison, determination 706 may be made based on the signal quality of the macro network or the enterprise network without requiring a comparison with the signal quality of another network.

[0068] Based on the comparison in 706, if UE 110 determines that a handover is not recommended, then UE 110 remains on the enterprise network and continues active calls. If UE 110 determines that a handover is recommended, the method proceeds to 708, and UE 110 switches cellular data to a macro SIM.

[0069] In 710, even though cellular data is switched to a macro network, UE 110 does not disable the enterprise SIM; for example, UE 110 remains in dual-SIM mode. As described above, if the enterprise SIM is disabled, UE 110 can switch from dual-SIM to single-SIM mode, resulting in UE 110 initiating a TAU. Resources used for TAUs can cause data interruptions for active calls switching to a macro network. By not disabling the enterprise SIM when a handover to a macro network has occurred, UE 110 avoids initiating a TAU while the call is active, thereby preventing data interruptions associated with TAUs. When the call is no longer active, UE 110 can then switch to single-SIM mode.

[0070] Figure 8A third method 800 for delayed data handover based on signal strength ingress / outgress, according to various exemplary embodiments, is illustrated. Enterprise networks may not always be perfectly consistent. Various coverage holes may exist within a given enterprise geofence. When UE 110 enters such a coverage hole, signal quality may degrade rapidly, causing data interruptions. In some cases, the macro network may still cover these enterprise network coverage holes. However, when UE 110 moves within the coverage area of ​​the enterprise network and encounters such a coverage hole, UE 110 may continuously handover between the macro network and the enterprise network, or vice versa. These continuous handovers may cause data interruptions due to the various reasons described above. Method 800 provides a way to avoid continuous handovers in such scenarios.

[0071] In step 801, UE 110 is in an active call. If UE 110 is transmitting data using an enterprise network, the method proceeds to step 802. If UE 110 is transmitting data on a macro network, the method proceeds to step 804. In both steps 802 and 804, the method then proceeds to step 806 and assesses the network quality of the active (e.g., data service) network.

[0072] If UE 110 has cellular data using an enterprise SIM and assessment 806 indicates a recommended handover (e.g., the signal quality of the enterprise network does not meet one or more thresholds), then UE 110 proceeds to 808. This could happen, for example, because UE 110 has encountered a coverage hole in the enterprise network.

[0073] In 808, UE 110 uses a macro SIM to switch to cellular data. In some implementations, UE 110 may not disable the enterprise SIM after this operation, for example, similar to the reference above. Figure 7 The described operation is 710.

[0074] If UE 110 has cellular data using macro SIM and evaluation 806 indicates a recommended handover, the method proceeds to 810.

[0075] In step 810, UE 110 determines the macro network signal quality. If the determined quality is poor (e.g., the macro network signal quality does not meet one or more predetermined thresholds related to signal quality), UE 110 proceeds to step 812 and switches cellular data to the enterprise SIM. If the determined quality is good (e.g., the macro network signal quality meets one or more predetermined thresholds related to signal quality), UE 110 proceeds to step 814 and maintains the call / data on the macro network.

[0076] Therefore, in this example, when the call remains active, UE 110 can continue to use the macro network within the coverage area of ​​the enterprise network.

[0077] Figure 9 A method 900, according to various exemplary embodiments, is shown that can be executed when a UE terminates an active call and a delayed data handover is used. As described above with reference to methods 600 to 800, a delayed data handover is implemented when the UE 110 has an active call. Figure 9 Method 900 provides operations that the UE can perform when a call is no longer active.

[0078] In step 901, UE 110 determines that the call (e.g., any of the active calls described in reference methods 600 to 800 above) is no longer active. In step 902, UE 110 determines whether UE 110 is inside or outside the enterprise geofence. As described in the examples above, the type of delayed data handover may depend on whether UE 110 is inside or outside the enterprise geofence.

[0079] If it is determined that UE 110 is outside the enterprise geofence, the method proceeds to 904 and disables the enterprise SIM. This operation assumes that a previously postponed data handover operation (e.g., Figure 7 During operation 710, disabling the enterprise SIM was suppressed. This disabling of the enterprise SIM may conserve battery power for the UE 110. In 906, the UE 110 switches cellular data to the macro SIM. As described above, there may be scenarios where the enterprise SIM is enabled but the UE 110 has previously switched cellular data to the macro SIM. If this is the case, the UE 110 can skip operation 906 because it has already been performed during the delayed data handover.

[0080] If it is determined that UE 110 is inside the enterprise geofence, the method proceeds to 908, where UE 110 determines whether the enterprise SIM is enabled. If the enterprise SIM is not enabled, then in 910, UE 110 enables the enterprise SIM. As described in some examples above, even if UE 110 is inside the geofence of the enterprise network, enabling the enterprise SIM may have been deferred to avoid data interruptions when calls are active. In 912, UE 110 registers the enterprise SIM with that network.

[0081] If it is determined in 908 that the enterprise SIM is enabled, or after 912, the method proceeds to 914, where UE 110 determines, for example, based on the signal quality of the macro network, whether a cellular data handover (e.g., a handover) from the macro network to the enterprise network is recommended. If a handover is not recommended based on 914, UE 110 remains on the macro network. If a handover is recommended based on 914, the method proceeds to 916, and UE 110 switches the cellular data to the enterprise SIM.

[0082] In a second aspect of the exemplary implementation, this document discloses operations and logic for preemptive data handover. Preemptive data handover (e.g., handover out) to overlapping macrocells can be performed based on a predicted interface handover with associated data pauses / dropped calls that a call (e.g., a Voice over Internet Protocol (VoIP) call) may undergo.

[0083] Figure 10 A method 1000 for preemptive cut-out according to various exemplary embodiments is shown. Throughout method 1000, if any determination 1004, 1006, 1008, 1010, 1012, and 1014 are negative (i.e., no), method 1000 returns to 1002. These "no" determinations will not be described further.

[0084] In 1002, the cellular data on UE 110 is currently using an enterprise SIM on an enterprise network.

[0085] In step 1004, UE 110 determines whether a calendar event exists for the scheduled voice call (e.g., a VoIP call). If a calendar event exists for the scheduled voice call, UE 110 proceeds to step 1006. In step 1006, UE 110 predicts whether a routine is likely to occur during the scheduled voice call. For example, the call may be scheduled from 4:30 PM to 5:30 PM. UE 110 understands that the user typically travels around 5:00 PM. In such a scenario, UE 110 can predict that the user will travel during the voice call.

[0086] If a predicted routine trip exists during a voice call, the method proceeds to 1008, where UE 110 determines whether its current location matches the predicted trip start point. For example, UE 110's current location could be the user's workplace location.

[0087] If UE 110 determines that its current location matches the predicted trip start point, the method proceeds to 1010, where UE 110 determines whether the current location is a significant location. A significant location can be any location where UE 110 is frequently located (e.g., home or workplace). A significant location can also be selected by the user.

[0088] If UE 110 determines that the current location is important, the method proceeds to 1012, where UE 110 determines whether the macro network interface is expensive (e.g., the signaling cost of handover is zero / low).

[0089] If UE 110 determines that the macro network interface is cheap, the method proceeds to 1014, where UE 110 determines whether the macro network has good signal quality. This determination may be based on UE 110's measurements of the macro network.

[0090] If UE 110 determines that the macro network has good signal quality, the method proceeds to 1016, where UE 110 performs a preemptive handover from the enterprise network to the macro network.

[0091] The predictive handover shown in method 1000 may be incorrect (e.g., UE 110 determines "yes" when the definitive answer is "no"). In such a scenario, various recovery operations are possible. For example, a predetermined time interval may be used at any point (before, during, and after) the operation shown in method 1000. In some implementations, after the predetermined timer expires, UE 110 may check whether the calendar invitation has been deleted or canceled. If the user has not yet started the predicted commute, or if the predicted call terminates, UE 110 may determine that preemptive handover is not necessary and remain on the enterprise network.

[0092] Figure 11 A method 1100 for recovering operation from an incorrect predictive handover, according to various exemplary embodiments, is shown. In 1102, UE 110 has preemptively performed a handover from the enterprise network to the macro network (e.g., following method 1000).

[0093] Following step 1102, UE 110 performs operations 1104, 1106, and 1108. These operations 1102, 1106, and 1108 can occur in any order and may also occur simultaneously. In step 1104, UE 110 determines whether a voice call calendar event has been canceled or rescheduled. In step 1106, UE 110 determines whether a routine has not started (e.g., based on accelerometer / gyroscope data, geolocation data, vehicle connectivity, etc.). In step 1108, UE 110 determines whether the voice call that caused the preemptive handover has been terminated.

[0094] If the answers to all of 1104, 1106, and 1108 are negative, the method terminates because UE 110 determines that the preemptive handover prediction is likely correct. Conversely, if the answer to any of 1104, 1106, and 1108 is yes, UE 110 determines that the preemptive handover prediction is likely incorrect. In this case, the method proceeds to 1110.

[0095] In 1110, the UE starts a hysteresis timer. The length of the timer can vary depending on the specific implementation by the operator and original equipment manufacturer (OEM). In 1111, the hysteresis timer expires.

[0096] In step 1112, UE 110 re-evaluates the interface selection. This can be interpreted as UE 110 understanding that the timer has expired and that further recovery operations can be performed. In some variations, UE 110 can proceed directly from operation 1111 to operation 1114.

[0097] In step 1114, it is determined whether UE 110 is inside the enterprise network geofence. If UE 110 is inside the enterprise network geofence, the method proceeds to step 1116, where UE 110 determines the strength of the enterprise network signal based on signal measurements.

[0098] If the enterprise network signal is strong, the method proceeds to step 1118, where UE 110 performs a handover to the enterprise network, thereby correcting an incorrect preemptive handover. If the enterprise network signal is weak, UE 110 can remain on the macro network.

[0099] Figure 12 A call flow 1200 for preemptive handover is illustrated according to various exemplary embodiments. Call flow 1200 can be understood as further describing operations associated with preemptive handover, as described with respect to method 1000.

[0100] Call flow 1200 includes calendar application 1202. Calendar application 1202 may be an application or service on UE 110 that can be accessed or modified by a user or a third-party entity. Calendar application 1202 may have multiple entries for the user, which may include time, date, and location.

[0101] Call flow 1200 includes core routine 1204. Core routine 1204 can be understood as stored information related to the mobility pattern of UE 110. For example, core routine 1204 may know that the user typically enters the vehicle at a certain time of day for a certain duration and typically arrives at a certain location (e.g., commuting to work).

[0102] Call flow 1206 includes motion input 1206. Motion input 1206 can be derived from various sensors of UE 110, such as gyroscopes, accelerometers, geolocation sensors (such as GPS and GLONASS), altimeters, barometers, etc. In some variants, motion input 1206 can also be derived from biometric data such as heart rate, skin temperature, and blood oxygen levels. Motion input 1206 can be used as input for generating core routine 1204.

[0103] The call process 1200 also includes a map 1206, which can be understood to include both the current location of the UE 110 and the scheduled location in the calendar application 1202.

[0104] Call flow 1200 includes a call start / handout predictor 1210 (hereinafter referred to as the "predictor"). The predictor 1210 can be understood as an engine executed by the UE 110 (e.g., a routine or function of the handover engine 235). The predictor 1210 evaluates the calendar 1202, core routine 1204, motion input 1206, and map 1208 to determine whether a preemptive handout should occur.

[0105] Call flow 1200 includes a macro network signal estimator 1212 (hereinafter referred to as the "estimator"). The estimator 1212 can be understood as a routine or function performed by the handover engine 235 based on signal measurements of the UE 110.

[0106] Call flow 1200 includes interface overhead 1214, which can be understood as information from the macro network interface indicating whether there will be signaling costs to the user if a handover occurs.

[0107] Call flow 1200 includes interface 1216, which can be understood as the SIM functionality of UE 110, including the serving data network. In call flow 1200, interface 1216 will be the macro network.

[0108] In 1218, predictor 1210 sends a calendar event request to calendar 1202.

[0109] In 1220, calendar 1202 sends a calendar event response to predictor 1210. Response 1220 may include the time and date associated with the scheduled event.

[0110] In 1222, predictor 1210 sends a routine information request to core routine 1204.

[0111] In 1224, core routine 1204 sends a routine information response, including core routine information, to predictor 1210.

[0112] In 1226, motion input 1206 transmits motion state information updates to predictor 1210, including relevant motion data for handing over prediction.

[0113] In 1228, the predictor 1210 sends a current location request to the map function 1208.

[0114] In 1230, the map function 1208 transmits the current location response, including the current geographic location of the UE, to the predictor 1210.

[0115] In 1232, the predictor 1210 sends an interface overhead request to the interface overhead function 1214.

[0116] In 1234, the interface overhead function 1214 transmits an interface overhead response to the predictor 1210, including information about whether the macro network will exceed a predetermined overhead threshold.

[0117] In 1236, predictor 1210 sends a signal information request to macro-network signal estimator function 1212.

[0118] In 1238, the macro network signal estimator function 1212 transmits signal information response, including macro network signal measurements, to the predictor 1210.

[0119] In 1240, predictor 1210 sends an update interface to MNO request to interface 1216.

[0120] In 1242, interface 1216 sends an update interface to MNO response to predictor 1210.

[0121] In a third aspect of the exemplary implementation, operations and logic for timely forced handover are disclosed. In some cases, predictive handover may be inaccurate. In some scenarios, it may be desirable to use a timer to force a handover upon detection of a call. Outgoing call detection is direct and can occur via monitoring the VoIP application that initiates the call. Outgoing calls can be buffered, and interface switching can occur before the call is initiated. Incoming call detection for forced handover can utilize buffering of incoming Session Initiation Protocol (SIP) invitations.

[0122] Figure 13 A call flow 1300 for timely handover is shown according to various exemplary embodiments.

[0123] Call flow 1300 is characterized by call state 1302, which is the function of UE 110 to know incoming and outgoing calls.

[0124] Call 1300 is characterized by a handover controller 1304, which is the function of determining and controlling handover and handover of UE 110.

[0125] Call 1300 is characterized by an MNO signal quality estimator 1306, which is essentially similar to the macro network signal estimator 1212.

[0126] Call 1300 is characterized by interface overhead function 1308, which is substantially similar to interface overhead function 1214.

[0127] Call 1300 is characterized by interface selector 1310, which is a function of UE 110 to control which interface (e.g., macro network or enterprise network) UE 110 is currently using.

[0128] In 1312, the call status function 1302 transmits incoming / outgoing call indications to the cut-out controller 1304.

[0129] In 1314, UE 110 waits during the setup delay time 1314. The setup delay time can be a predetermined length of time allocated for operator implementation. In some variations, the setup delay time can vary based on date, UE location, UE battery status, and network conditions. In other variations, the setup delay time is static.

[0130] In 1316, the cutout controller 1304 sends an interface overhead request to the MNO signal quality estimator 1316.

[0131] In 1318, the MNO signal quality estimator 1306 sends an interface overhead response to the cut-out controller 1304, indicating whether the macro network is expensive or cheap.

[0132] In 1320, the cut-out controller 1304 sends a signal information request to the signal quality estimator 1306. The signal information request includes queries for one or more of RSRP, RSRQ, and Link Quality Metric (LQM).

[0133] In 1322, the signal quality estimator 1306 transmits a signal information response, including one or more of RSRP, RSRQ, and LQM, to the cut-out controller 1304.

[0134] In step 1324, the switchout controller 1304 sends an update interface to MNO request to the interface selector 1310.

[0135] In 1326, the interface selector 1310 sends an update interface to the MNO response to the cut-out controller 1304, indicating that the current interface is now a macro network.

[0136] When a UE operates with two macro network SIMs, additional factors and measurements can be used to determine when to perform a data handover. UE 110 can compare the Reference Received Power (RSRP) and Reference Received Quality (RSRQ) (e.g., signal strength) of the two macro networks. UE 110 can compare the uplink / downlink block error rate (BLER) and network permission (e.g., link quality) of the two macro networks. UE 110 can also compare the reported network congestion (e.g., cell load) of the two macro networks. Various methods can be used to compare signal strength, link quality, and cell load when determining how and when to perform a data handover between macro networks.

[0137] Example In a first embodiment, a method performed by a user equipment (UE) includes: determining that the UE has an active call via a macrocell network, wherein the UE includes a macrocell network subscriber identity module (SIM) associated with the macrocell network; determining that the UE has entered a geofence area associated with a private cellular network; determining a first signal quality of the macrocell network based on a first signal measurement of the macrocell network; and omitting the activation of the private cellular network SIM associated with the private cellular network when the first signal quality of the macrocell network meets a predetermined threshold, or activating the private cellular network SIM associated with the private cellular network when the signal quality of the macrocell network does not meet the predetermined threshold.

[0138] In a second embodiment, according to the method of the first embodiment, the method further includes: determining that the active call has ended; enabling the private cellular network SIM based on the end of the active call; performing a registration process for the private cellular network SIM using the private cellular network; determining a second signal quality of the macro cellular network; and performing a cellular data cut-in from the macro cellular network to the private cellular network based on the second signal measurement.

[0139] In a third embodiment, according to the method of the first embodiment, when the signal quality of the macrocell network does not meet the predetermined threshold, the method further includes: performing a registration process for the SIM of the private cellular network using the private cellular network; determining a second signal quality of the macrocell network based on a second signal measurement; and performing a cellular data transfer from the macrocell network to the private cellular network based on the second signal measurement.

[0140] In the fourth embodiment, according to the method of the first embodiment, the determination that the UE has an active call is based on the following: (i) the application programming interface (API) associated with the application hosting the active call, (ii) the application category associated with the application hosting the active call, or (iii) the service pattern generated by the application hosting the active call.

[0141] In the fifth embodiment, according to the method of the first embodiment, the first signal quality includes signal strength, link quality, or cell load.

[0142] In a sixth embodiment, a processor is configured to perform any one of the methods described according to the first to fifth embodiments.

[0143] In a seventh embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a macro cellular network and a private cellular network; and a processor communicatively coupled to the transceiver and configured to perform any one of the methods described in the first to fifth embodiments.

[0144] In an eighth embodiment, a method performed by a user equipment (UE) includes: determining that the UE has an active call via a private cellular network, wherein the UE has a private cellular network subscriber identity module (SIM) associated with the private cellular network and a macro cellular network SIM associated with a macro cellular network, wherein the macro cellular network SIM is enabled and non-service; determining that the UE has exited a geofence area associated with the private cellular network; performing signal measurements of the macro cellular network and the private cellular network; and performing a cellular data handover from the private cellular network to the macro cellular network based on the signal measurements, wherein the private cellular network SIM remains enabled after the cellular data handover.

[0145] In the ninth embodiment, according to the method of the eighth embodiment, the determination that the UE has an active call is based on: (i) the application programming interface (API) associated with the application hosting the active call, (ii) the application category associated with the application hosting the active call, or (iii) the service pattern generated by the application hosting the active call.

[0146] In the tenth embodiment, according to the method of the eighth embodiment, the method further includes: determining that the active call has ended; and disabling the private cellular network SIM based on the end of the active call.

[0147] In the eleventh embodiment, a processor is configured to perform any one of the methods described according to the eighth to tenth embodiments.

[0148] In a twelfth embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a macro cellular network and a private cellular network; and a processor communicatively coupled to the transceiver and configured to perform any one of the methods described according to embodiments eight through ten.

[0149] In a thirteenth embodiment, a method performed by a user equipment (UE) that is supplied with cellular data by a private cellular network includes: determining an upcoming calendar event associated with a voice call; predicting that the UE will leave the coverage area of ​​the private cellular network before the voice call ends; determining, based on signal measurements of a macrocell network, that the signal quality of the macrocell network meets a predefined threshold; and switching the UE from being supplied with cellular data by the private cellular network to being supplied with cellular data by the macrocell network based on the prediction that the UE will leave the coverage area of ​​the private cellular network and the signal measurements of the macrocell network.

[0150] In the fourteenth embodiment, according to the method of the thirteenth embodiment, the prediction that the UE will leave the coverage area of ​​the private cellular network is based on determining a predicted trip associated with the upcoming calendar event.

[0151] In the fifteenth embodiment, according to the method of the fourteenth embodiment, the prediction that the UE will leave the coverage area of ​​the private cellular network is based on determining that the current UE location matches the starting point of the predicted journey and determining that the current UE location matches a predefined important location.

[0152] In the sixteenth embodiment, according to the method of the fourteenth embodiment, the prediction that the UE will leave the coverage area of ​​the private cellular network is based on determining the predicted trip based on learning the UE's mobility patterns.

[0153] In the seventeenth embodiment, according to the method of the thirteenth embodiment, the handover is further based on the macro cellular network overhead being lower than a predefined overhead threshold.

[0154] In the eighteenth embodiment, the method according to the thirteenth embodiment further includes determining at least one of the following: (i) the call associated with the upcoming calendar event has been cancelled; (ii) the predicted trip during the upcoming calendar event has not occurred; or (iii) the call associated with the upcoming calendar event has been terminated; determining that the UE is inside a geofence associated with the private cellular network; performing a signal measurement of the private cellular network; and switching the UE from cellular data supplied by the macro cellular network to cellular data supplied by the private cellular network.

[0155] In the nineteenth embodiment, according to the method of the eighteenth embodiment, the method further includes starting a timer with a predetermined duration, wherein the signal measurement of the private cellular network and the evaluation of handover to the private network are not performed before the timer expires.

[0156] In the twentieth embodiment, according to the method of the thirteenth embodiment, the call includes a Voice over Internet Protocol (VoIP) call.

[0157] In the twenty-first embodiment, a processor is configured to perform any one of the methods described according to the thirteenth to the twentieth embodiments.

[0158] In the twenty-second embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a macro cellular network and a private cellular network; and a processor communicatively coupled to the transceiver and configured to perform any one of the methods described according to the thirteenth to the twentieth embodiments.

[0159] In a twenty-third embodiment, a method performed by a user equipment (UE) includes: when the UE is connected to a first cellular network, determining that the UE is preparing to participate in a voice call; determining the overhead associated with the UE performing the voice call on a second cellular network; determining a first signal quality associated with the first cellular network; determining a second signal quality associated with the second cellular network; and selecting either the first cellular network or the second cellular network to perform the voice call based on the first signal quality, the second signal quality, and the overhead, wherein when the second cellular network is selected, the user switches to the second cellular network before connecting to the voice call.

[0160] In the twenty-fourth embodiment, the method described in the twenty-third embodiment is used, wherein the first cellular network is a private cellular network and the second cellular network is a macro cellular network.

[0161] In the twenty-fifth embodiment, according to the method of the twenty-third embodiment, the first signal quality includes the reference signal received power (RSRP), reference signal received quality (RSRQ), uplink block error rate (BLER), downlink BLER, or network permission of the first cellular network.

[0162] In the twenty-sixth embodiment, according to the method of the twenty-third embodiment, the second cellular network is selected at least when the overhead is below a predefined overhead threshold.

[0163] In the twenty-seventh embodiment, a processor is configured to perform any one of the methods described according to the twenty-third to twenty-sixth embodiments.

[0164] In the twenty-eighth embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a first cellular network and a second cellular network; and a processor communicatively coupled to the transceiver and configured to perform any one of the methods described according to the twenty-third to twenty-sixth embodiments.

[0165] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Exemplary embodiments of the methods described above may be embodied as programs containing lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0166] Although this application describes various embodiments that have different features in various combinations, those skilled in the art will understand that any feature of one embodiment can be combined with features of other embodiments in any way that is not expressly denied or that is not functionally or logically inconsistent with the operation of the device or the specified function of the disclosed embodiment.

[0167] As described above, one aspect of this technology involves collecting and using data from specific and lawful sources to improve the delivery of inspirational or other content that may be of interest to users. This disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify specific individuals. Such personal information data may include demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other personal information.

[0168] This disclosure recognizes that the use of such personal information data in the techniques of this invention can benefit users. For example, personal information data can be used to deliver targeted content that a user may be interested in based on their preferences. Therefore, using such personal information data allows users greater control over the content delivered. Furthermore, this disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used according to user preferences to provide insights into their overall health status, or it can be used as positive feedback for individuals using technology to pursue health goals.

[0169] This disclosure anticipates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, it is expected that such entities will implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or governmental requirements for protecting user privacy. Such information regarding the use of personal data should be highlighted and easily accessible to users, and should be updated as the collection and / or use of data changes. Users' personal information should be collected only for lawful use. Furthermore, such collection / sharing should only occur after receiving user consent or other lawful grounds provided for in applicable law. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to personal information data comply with the privacy policies and procedures of other entities. Moreover, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information data collected and / or accessed, and made applicable to applicable laws and standards, including jurisdiction-specific considerations that may be applied to impose higher standards. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0170] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, in the case of advertising delivery services, the inventive technology can be configured to allow users to opt-in or opt-out at any time during or after service registration to participate in the collection of personal information data. In another example, users can choose not to provide emotion-related data for a targeted content delivery service. Furthermore, users can choose to limit the duration for which emotion-related data is retained, or completely prevent the development of underlying emotional states. In addition to providing opt-in and opt-out options, this disclosure also contemplates providing notifications related to access to or use of personal information. For example, users can be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0171] Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by restricting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods (such as differentiated privacy).

[0172] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not become inoperable due to the absence of all or part of such personal information data. For example, content can be selected and delivered to the user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content disposed solely on the user's device or other non-personal information available for content delivery services.

[0173] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover modifications and variations thereof, provided they fall within the scope of the appended claims and their equivalents.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising processing circuitry configured to: It is determined that the UE has an active call via a macrocell network, wherein the UE includes a macrocell network subscriber identity module (SIM) associated with the macrocell network. It is determined that the UE has entered a geofenced area associated with a private cellular network; The first signal quality of the macrocell network is determined based on the first signal measurement of the macrocell network. as well as When the first signal quality of the macrocell network meets a predetermined threshold, the activation of the private cellular network SIM associated with the private cellular network is omitted. or When the signal quality of the macrocell network does not meet a predetermined threshold, the private cellular network SIM associated with the private cellular network is activated.

2. The apparatus of claim 1, wherein the processing circuit is further configured to: It has been determined that the active call has ended; The private cellular network SIM is activated based on the termination of the active call. The registration process for the SIM card of the private cellular network is performed using the private cellular network; Determine the second signal quality of the macrocell network; as well as Cellular data transfer from the macrocell network to the private cell network is performed based on a second signal measurement.

3. The apparatus of claim 1, wherein when the signal quality of the macrocell network does not meet the predetermined threshold, the processing circuit is further configured to: The registration process for the SIM card of the private cellular network is performed using the private cellular network; The second signal quality of the macrocell network is determined based on a second signal measurement; and Cellular data transfer from the macrocell network to the private cell network is performed based on the second signal measurement.

4. The apparatus of claim 1, wherein determining that the UE has an active call is based on: (i) an application programming interface (API) associated with the application hosting the active call, (ii) an application category associated with the application hosting the active call, or (iii) a service pattern generated by the application hosting the active call.

5. The apparatus of claim 1, wherein the first signal quality includes signal strength, link quality, or cell load.

6. An apparatus for a user equipment (UE), the apparatus comprising processing circuitry configured to: It is determined that the UE has active calls via a private cellular network, wherein the UE has a private cellular network subscriber identity module (SIM) associated with the private cellular network and a macro cellular network SIM associated with a macro cellular network, wherein the macro cellular network SIM is enabled and is non-service; Determine that the UE has exited the geofence area associated with the private cellular network; Perform signal measurements on the macrocell network and the private cell network; as well as Cellular data handover from the private cellular network to the macro cellular network is performed based on the signal measurements, wherein the private cellular network SIM remains enabled after the cellular data handover.

7. The apparatus of claim 6, wherein determining that the UE has an active call is based on: (i) an application programming interface (API) associated with the application hosting the active call, (ii) an application category associated with the application hosting the active call, or (iii) a service pattern generated by the application hosting the active call.

8. The apparatus of claim 6, wherein the processing circuit is further configured to: It has been determined that the active call has ended; The private cellular network SIM is disabled based on the termination of the active call.

9. An apparatus for a user equipment (UE) that supplies cellular data from a private cellular network, the apparatus comprising processing circuitry configured to: Identify upcoming calendar events associated with the voice call; It is predicted that the UE will leave the coverage area of ​​the private cellular network before the voice call ends; The signal quality of the macrocell network is determined to meet a predefined threshold based on signal measurements of the macrocell network. as well as The UE is switched from cellular data supplied by the private cellular network to cellular data supplied by the macro cellular network based on the prediction that the UE will leave the coverage area of ​​the private cellular network and the signal measurement of the macro cellular network.

10. The apparatus of claim 9, wherein the processing circuitry is configured to predict that the UE will leave the coverage area of ​​the private cellular network based on the following operation: Determine the predicted itinerary associated with the upcoming calendar event.

11. The apparatus of claim 10, wherein the processing circuitry is configured to predict that the UE will leave the coverage area of ​​the private cellular network based on the following operation: Determine if the current UE location matches the start point of the predicted journey; and Determine if the current UE location matches a predefined important location.

12. The apparatus of claim 10, wherein the processing circuitry is configured to predict that the UE will leave the coverage area of ​​the private cellular network based on the following operation: Predicted trips are determined based on learning the UE's mobility patterns.

13. The apparatus of claim 9, wherein the handover is further based on the macrocell network overhead being below a predefined overhead threshold.

14. The apparatus of claim 9, wherein the processing circuit is further configured to: Determine at least one of the following: (i) the call associated with the upcoming calendar event has been cancelled; (ii) the predicted trip during the upcoming calendar event has not occurred; or (iii) the call associated with the upcoming calendar event has been terminated. Determine that the UE is inside a geofence associated with the private cellular network; Perform signal measurements on the private cellular network; as well as The UE is switched from receiving cellular data from the macro cellular network to receiving cellular data from the private cellular network.

15. The apparatus of claim 14, wherein the processing circuit is further configured to: A timer with a predetermined duration is started, wherein the signal measurement of the private cellular network and the evaluation of handover to the private network are not performed before the timer expires.

16. The apparatus of claim 9, wherein the call comprises a Voice over Internet Protocol (VoIP) call.

17. An apparatus for a user equipment (UE), the apparatus comprising processing circuitry configured to: When the UE connects to the first cellular network, it is determined that the UE is preparing to participate in a voice call; Determine the overhead associated with the UE performing the voice call on the second cellular network; Determine the first signal quality associated with the first cellular network; Determine the second signal quality associated with the second cellular network; as well as The voice call is performed by selecting either the first cellular network or the second cellular network based on the first signal quality, the second signal quality, and the overhead. When the second cellular network is selected, the UE switches to the second cellular network before connecting to the voice call.

18. The apparatus of claim 17, wherein the first cellular network is a private cellular network and the second cellular network is a macro cellular network.

19. The apparatus of claim 17, wherein the first signal quality includes the reference signal received power (RSRP), reference signal received quality (RSRQ), uplink block error rate (BLER), downlink BLER, or network permission of the first cellular network.

20. The apparatus of claim 17, wherein the second cellular network is selected at least when the overhead is below a predefined overhead threshold.

Images