METHOD OF NETWORK-BASED STEERING OF A MOBILE DEVICE POSITIONED IN AN AREA HAVING PREFERRED AND NON-PREFERRED OVERLAPPING NETWORK COVERAGE

Abstract

A method for steering a mobile device to a preferred network, such as a Private LTE network or a 5G network, in a scenario in which the coverage area of the preferred network overlaps the coverage area of a non-preferred network. A preferred network list is provisioned into a SIM/eSIM module at the mobile device side. The steering application is hosted at the home network and periodically triggers the home network to request from the visited network a set of values for attributes associated with a current location of the mobile device. Based on these values, the steering application determines whether the mobile device is within the coverage area of the preferred network and, if so, directs the home network to send a cancel location request to the non-preferred visited network, thereby triggering the mobile device to attach to the preferred network.

Claims

1. A method of steering a mobile device to a preferred telecommunications network having a geographical coverage area overlapping with a non-preferred Visited Public Land Mobile Network (VPLMN), wherein the mobile device is initially attached to the non-referred VPLMN, the method comprising: sending a first message to the non-preferred VPLMN, the first message including a request for a current location of the mobile device; receiving from the non-preferred VPLMN a first response to the first message, the first response having a set of attribute values associated with the current location of the mobile device; accessing a set of prestored attribute values defining the geographical coverage area of the preferred network; comparing the set of attribute values associated with the current location of the mobile device received from the non-preferred VPLMN against the set of prestored attribute values to determine whether the current location of the mobile device is within the geographical coverage area of the preferred telecommunications network; responsive to determining that the current location of the mobile device is within the geographical coverage area of the preferred telecommunications network, sending a first command to the non-preferred VPLMN directing the non-preferred VPLMN to discontinue attachment of the mobile device thereto; wherein, responsive to the mobile device becoming detached from the non-preferred VPLMN, the mobile device is configured to perform a network selection procedure, thereby requesting to attach to the preferred telecommunication network.

2. The method of claim 1, wherein the first message, the first command, or both are sent from a Home Public Land Mobile Network (HPLMN) associated with the mobile device.

3. The method of claim 2, wherein the first message is sent from a network node selected from a group consisting of a Home Location Register (HLR), a Home Subscriber Server (HSS), and a Unified Data Management (UDM) node.

4. The method of claim 2, wherein the first message is triggered by a steering application hosted at the HPLMN.

5. The method of claim 2, wherein a steering application hosted at the HPLMN determines whether the current location of the mobile device is within the geographical coverage area of the preferred telecommunications network.

6. The method of claim 2, wherein the first command is triggered by a steering application hosted at the HPLMN.

7. The method of claim 1, wherein the first message is an Insert Subscriber Data Request (IDR) message, a Provide Subscriber Information request message, or a Namf_Location Service message.

8. The method of claim 1, wherein the first command is a Mobile Application Part (MAP) Cancel-Location message, a Diameter Cancel-Location-Request, or a Nudm Deregistration Notification message.

9. The method of claim 1, wherein the set of attribute values associated with the current location of the mobile device is selected from a group consisting of a longitude, a latitude, a mobile country code (MCC), a mobile network code (MNC), a cell identification, an adjacent cell information, a radio signal quality, and a radio signal strength.

10. The method of claim 1, wherein the preferred telecommunications network is a 5G network, a private 5G network, or a private Long-Term Evolution (LTE) network.

11. The method of claim 1, wherein responsive to determining that the current location of the mobile device is outside the geographical coverage area of the preferred telecommunications network, calculating an expected time of arrival at which the mobile device is projected to arrive into the geographical coverage area of the preferred telecommunications network and sending a second message to the non-preferred VPLMN at the expected time of arrival, the second message requesting a second set of attribute values associated with an updated location of the mobile device.

12. The method of claim 1, wherein the set of attribute values associated with the current location of the mobile device is received via a Signaling System No. 7 (SS7) protocol, a Diameter protocol, a General Packet Radio Service Tunneling Protocol (GTP), a Hypertext Transfer Protocol/2 (HTTP/2), or Transmission Control Protocol/Internet Protocol (TCP/IP).

13. The method of claim 1, wherein the mobile device is provisioned with a list of preferred telecommunications networks, and wherein responsive to the mobile device being detached from the non-preferred VPLMN, the mobile device is configured to perform a network selection procedure based on the list of preferred telecommunications networks.

14. A method of steering a mobile device to a preferred telecommunications network having a geographical coverage area overlapping with a non-preferred Visited Public Land Mobile Network (VPLMN), wherein the mobile device is initially attached to the non-referred VPLMN, the method comprising: providing a steering application hosted on a Home Public Land Mobile Network (HPLMN) associated with the mobile device; triggering, by the steering application, the HPLMN to send a first message to the non-preferred VPLMN, the first message including a request for a current location of the mobile device; receiving from the non-preferred VPLMN a first response to the first message, the first response having a set of attribute values associated with the current location of the mobile device; accessing a set of prestored attribute values defining the geographical coverage area of the preferred network; comparing, by the steering application, the set of attribute values associated with the current location of the mobile device received from the non-preferred VPLMN against the set of prestored attribute values to determine whether the current location of the mobile device is within the geographical coverage area of the preferred telecommunications network; responsive to determining that the current location of the mobile device is within the geographical coverage area of the preferred telecommunications network, triggering, by the steering application, the HPLMN to send a first command to the non-preferred VPLMN, wherein the first command directs the non-preferred VPLMN to discontinue attachment of the mobile device thereto; wherein, responsive to the mobile device becoming detached from the non-preferred VPLMN, the mobile device is configured to perform a network selection procedure, thereby requesting to attach to the preferred telecommunication network.

15. The method of claim 14, wherein the first message is sent from a network node selected from a group consisting of a Home Location Register (HLR), a Home Subscriber Server (HSS), and a Unified Data Management (UDM) node.

16. The method of claim 1, wherein the first message is an Insert Subscriber Data Request (IDR) message, a Provide Subscriber Information request message, or a Namf_Location Service message.

17. The method of claim 1, wherein the first command is a Mobile Application Part (MAP) Cancel-Location message, a Diameter Cancel-Location-Request, or a Nudm Deregistration Notification message.

18. The method of claim 1, wherein the set of attribute values associated with the current location of the mobile device is selected from a group consisting of a longitude, a latitude, a mobile country code (MCC), a mobile network code (MNC), a cell identification, an adjacent cell information, a radio signal quality, and a radio signal strength.

19. The method of claim 1, wherein the preferred telecommunications network is a 5G network, a private 5G network, or a private Long-Term Evolution (LTE) network.

20. The method of claim 1, wherein responsive to determining that the current location of the mobile device is outside the geographical coverage area of the preferred telecommunications network, calculating an expected time of arrival at which the mobile device is projected to arrive into the geographical coverage area of the preferred telecommunications network and sending a second message to the non-preferred VPLMN at the expected time of arrival, the second message requesting an updated location of the mobile device.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] For a fuller understanding of the invention, reference should be made to the following detailed disclosure, taken in connection with the accompanying drawings, in which:

[0018] FIG. 1A is a block diagram schematically depicting an exemplary network architecture for a scenario in which the non-preferred network is a 3G network, the preferred network is a Private LTE network, and the home network is a 3G network.

[0019] FIG. 1B is a block diagram schematically depicting an exemplary network architecture for a scenario in which the non-preferred network is an LTE network, the preferred network is a Private LTE network, and the home network is an LTE network.

[0020] FIG. 1C is a block diagram schematically depicting an exemplary network architecture for a scenario in which the non-preferred network is a 5G network, the preferred network is a Private 5G network, and the home network is a 5G network.

[0021] FIG. 2 is a diagram depicting an exemplary Insert Subscriber Data Request (IDR) with an EPS-Location-Information flag and an Insert Subscriber Data Answer (IDA) message.

[0022] FIG. 3 is a flowchart depicting exemplary steps for identifying an overlapping coverage area of the non-preferred VPLMN and Private LTE/5G network coverage.

[0023] FIG. 4 is a data model of the Cell-ID database records that can be used to determine the location of the mobile device.

[0024] FIG. 5 is a flowchart depicting the steps of configuring a home network according to an embodiment of the invention.

[0025] FIG. 6 is a flowchart depicting the steps of a steering procedure according to an embodiment of the invention.

[0026] FIG. 7 is a flowchart depicting the steps of determining a time at which to request updated location attribute values for the new location of the mobile device.

[0027] FIG. 8 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device is attached to a non-preferred LTE network and is outside of the geographic region where a Private LTE network has overlapping coverage.

[0028] FIG. 9 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device moves from an area covered exclusively by a non-preferred LTE network into a location in which both the non-preferred LTE network and the preferred Private LTE network have overlapping coverage, and the steering application steers the mobile device toward the preferred Private LTE network.

[0029] FIG. 10 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device is attached to a non-preferred 3G network and is outside of the geographic region where a Private LTE network has overlapping coverage.

[0030] FIG. 11 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device moves from an area covered exclusively by a non-preferred 3G network into a location in which both the non-preferred 3G network and the preferred Private LTE network have overlapping coverage, and the steering application steers the mobile device toward the preferred Private LTE network.

[0031] FIG. 12 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device is attached to a non-preferred public 5G network and is outside of the geographic region where a Private 5G network has overlapping coverage.

[0032] FIG. 13 is a signaling flow diagram depicting the message flow for the scenario in which the mobile device moves from an area covered exclusively by a non-preferred public 5G network into a location in which both the non-preferred 5G network and the preferred Private 5G network have overlapping coverage, and the steering application steers the mobile device toward the preferred Private 5G network.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0033] Embodiments of the present invention pertain to a method and a system for improving mobile network steering and traffic routing efficiency in geographic locations where the coverage area of a Private Long-Term-Evolution (LTE) network/5G network overlaps the coverage area of a Public Land Mobile Network (PLMN), such a 3G or 4G network.

[0034] FIGS. 1A-1C depict scenarios in which a mobile device 12 is initially positioned in a first geographic area in which only a non-preferred Visited Public Land Mobile Network (VPLMN) 14 has coverage. Thus, initially, mobile device 12 is attached to non-preferred VPLMN 14. FIG. 1A depicts a scenario in which VPLMN 14 is a 3G network. VPLMN 14 has at least the following nodes: NodeB 16, a Mobile Switching Center (MSC) 18, and a Serving General Packet Radio Service (GPRS) Support Node (SGSN) 20. FIG. 1B depicts a scenario in which VPLMN 14 is an LTE network. In this scenario, instead of NodeB 16, MSC 18 and SGSN 20, VPLMN 14 has the following nodes: evolved-NodeB (eNodeB) 22, a Mobility Management Entity (MME) 24 and Serving Gateway (SGW) 26, respectively. Next, FIG. 1C depicts a scenario in which VPLMN 14 is a 5G network. In this scenario, VPLMN 14 has the following nodes: gNodeB 28, AMF 30, and SMF 32. Other types of mobile networks also fall within the scope of this invention.

[0035] FIGS. 1A-1C depict that mobile device 12 changes its location from a first geographic area covered exclusively by a non-preferred VPLMN 14 to a second geographic area in which both VPLMN 14 and a preferred mobile network 34 have overlapping coverage. FIGS. 1A and 1B depict scenarios in which preferred mobile network 34 is a Private LTE network. FIGS. 1A and 1B depict that the Private LTE Network has the following nodes: eNodeB 36, MME 38, and SGW 40. Next, FIG. 1C depicts a scenario in which preferred mobile network 34 is a Private 5G network, having the following nodes gNodeB 42, AMF 45, and SMF 46. These scenarios are exemplary and the principles of the present invention disclosed herein can be used to steer mobile device 12 from any non-preferred VPLMN 14 to any preferred mobile network 34, when mobile device 12 enters a location in which both non-preferred VPLMN 14 and preferred mobile network 34 have coverage.

[0036] Continuing reference to FIGS. 1A-1C, mobile device 12 is a subscriber of Home Network 42. In the exemplary scenario depicted in FIG. 1A, Home Network 42 is a 3G network, having the following nodes: Home Location Register (HLR) 44 and Gateway GPRS Support Node (GGSN) 46. When mobile device 12 is attached to VPLMN 14, HLR 44 is communicatively coupled to MSC 18 and GGSN 46 is communicatively coupled to SGW 20. FIG. 1B depicts the scenario in which Home Network 42 is an LTE network, having the following nodes: Home Subscriber Server (HSS) 48 and Packet Gateway (PGW) 50. In this scenario, HSS 48 is communicatively coupled to MME 24 and PGW 50 is communicatively coupled to SGW 26. In the exemplary scenario depicted in FIG. 1C, Home Network 42 is a 5G network, having the following nodes: Unified Data Management (UDM) 52 and User Plane Function (UPF) 54. In this scenario, UDM 52 is communicatively coupled with AMF 30, and UPF 52 is communicatively coupled to SMF 32 of VPLMN 14.

[0037] FIG. 1A-1C further depict a steering application—referred to herein as a Network Steering Engine (NSE) 54—deployed in Home Network 42. FIGS. 1A-1C depict that NSE 54 is configured to communicate with HLR 44/HSS 48/UDM 52. NSE 54 runs on the home network side and interfaces with HLR 44/HSS 48/UDM 52 to periodically query the current Cell-ID from MSC 18/MME 24/AMF 30 of VPLMN 14. In an embodiment, NSE 54 maintains information pertaining to overlapping coverage areas of non-preferred VPLMN 14 and preferred network 34 to optimize the query frequency for current Cell-ID. Additionally, NSE 54 can be configured to calculate distances between a current location of mobile device 12 and locations in which preferred network 34 has coverage. NSE 54 can be further configured to detect or predict when mobile device 12 will arrive into a coverage area of preferred network 34.

[0038] After NSE 54 determines that mobile device 12 is located within the geographic area having preferred network 34 coverage, NSE 54 triggers HLR 44/HSS 48/UDM 52 to send a command to MSC 18/MME 24/AMF 30 of VPLMN 14 to discontinue attachment of mobile device 12 to VPLMN 14. In response to this command, non-preferred VPLMN 14 detaches mobile device 12 from its network. This detachment causes mobile device 12 to perform a network selection procedure based on a predefined list of preferred networks, which can be provisioned on a Subscriber Identity Module (SIM) card or a virtual SIM module (eSIM). Mobile device 12 will then trigger the attach procedure to a preferred network 34. As explained in more detail below, a protection technique can be implemented to avoid out-of-service scenario, if mobile device 12 continues to attach to the same non-preferred VPLMN 14.

[0039] To obtain a current location of mobile device 12, NSE 54 triggers HLR 44/HSS 48/UDM 52 of Home Network 42 to send a message to MSC 18/MME 24/AMF 30 of VPLMN 14 requesting a set of a set of values for attributes associated with the current location of mobile device 12. In the scenario in which the non-preferred VPLMN 14 is an LTE network, attribute values associated with the current location of mobile device 12 can be requested using an Insert Subscriber Data Request (IDR) having an EPS Location Information Request flag, as depicted in FIG. 2. VPLMN 14 is configured to reply to the IDR with an Insert Subscriber Data Answer (IDA) message having a set of attribute values corresponding to the current geographic location of the mobile device. The set of attribute values reported by VPLMN 14 can be used to determine whether mobile device 12 is within the coverage area of the preferred network 34 in the manner described below.

[0040] FIG. 3 provides a flowchart outlining examplary steps for identifying geographic areas having overlapping coverage of non-preferred VPLMN 14 and preferred network 34. In step 102, NSE 54 can be configured to maintain Cell-IDs of cellular towers, GPS coordinates, and location database for various non-preferred VPLMNs 14. In step 104, NSE 54 can be configured to maintain the cellular towers Cell-IDs, GPS coordinates, and location database for various preferred networks 34. In step 106, using these values, NSE 54 can generate geofence records around the boundary of preferred network 34 cellular radio coverage with corresponding GPS coordinates. In step 108, NSE 54 identifies nearby VPLMN 14 Cell-IDs by calculating the distances against the geofence data. Next, in step 110, NSE 54 ranks the nearby VPLMN 14 Cell-IDs based on the calculated distances. In step 112, NSE 54 generates geofence records around the boundary of those VPLMN 14 Cell-IDs that are the nearest to the boundaries of network area coverage of a preferred network 34. In step 114, NSE 54 identifies the overlapped area on the geofencing of VPLMN 14 and network coverage area of a preferred network 34.

[0041] FIG. 4 depicts a data model of the Cell-ID database records that can be used to establish the geofencing of VPLMN 14 and preferred network 34 (Private LTE/5G Network) area coverage. As disclosed above and depicted in FIGS. 1A-1C, NSE 54 is hosted on the home-network side and interfaces with HLR 44/HSS 48/UDM 52. NSE 54 leverages the connection between HLR 44/HSS 48/UDM 52 of Home Network 42 and MSC 18/MME 24/AMF 30 of VPLMN 14 to obtain a set of attribute values associated with the current location of mobile device 12. As depicted in FIG. 4, these values may include one or more of the following: a longitude, a latitude, a MCC, MNC, cell identification, adjacent cell information, radio signal quality, and radio signal strength.

[0042] FIG. 5 depicts examplary steps for receiving the attribute values corresponding to the current location of mobile device 12. In step 202, NSE 54 directs HLR 44/HSS 48 of Home Network 42 to request EPS Location Info in the IDR sent to VPLMN 14 based on IMSI (or IMSI range) associated with mobile device 12. Alternatively, or in addition to, in step 204, NSE 54 can direct Home Network 42 to request EPS Location Info in the IDR when NSE 54 determines that mobile device 12 may be within or approaching a location in which non-preferred VPLMN 14 has coverage overlap coverage with a preferred network 34 (Private LTE/5G Network). Next, in step 206, HLR 44/HSS 48 of Home Network 42 notifies NSE 54 upon receiving EPS Location Info in the IDA. Alternatively, or in addition to, in step 208, NSE 54 can be configured to receive Location Info associated with the current location of mobile device 12 via MAP-PROVIDE-SUBSCRIBER-INFO message, in case VPLMN 14 is a 3G network.

[0043] FIG. 6 depicts the steps of a steering procedure for mobile device 12 roaming in non-preferred VPLMN 14, which is a public LTE network (this scenario is depicted in FIG. 1B). The method begins with step 302, in which HHS 48 of Home Network 42 receives a Diameter Update Location Request (ULR) message from VPLMN 14. In step 304, HSS 48 responds with a Update Location Answer (ULA) message. Next, in step 306, HSS 48 sends an Insert Subscriber Data Request (IDR) message to MME 24 of VPLMN 14. The IDR message has an EPS Location Info Request flag turned on. In step 308, HSS 48 receives Insert Subscriber Data Answer (IDA) from MME 24 of VPLMN 14. The IDA includes a set of values in the EPS-Location-Information field.

[0044] Next, in step 310, HSS 48 notifies NSE 54 of the EPS-Location-Information values and corresponding IMSI of mobile device 12. In step 312, NSE 54 compares the EPS-Location-Information against the precalculated geofencing data and distance with preferred network 34. In step 314, based on this analysis, NSE 54 determines whether the current location of mobile device 12 is within the coverage area of preferred network 34. If the mobile device is outside of the coverage area of preferred network 34, NSE 54 will trigger HSS 48 to initiate another IDR message to MME 24 of VPLMN 14 after a predefined time period lapses.

[0045] However, if NSE 54 determines that mobile device 12 is within the coverage area of preferred network 34, the method proceeds to step 318. In step 318, NSE 54 triggers HSS 48 to initiate Cancel Location procedure to VPLMN 14. This command causes VPLMN 14 to drop network connection with mobile device 12. In step 320, after being detached from non-preferred VPLMN 14, mobile device 12 performs network scanning procedure to identify an available network to which mobile device 12 can reattach based on a predefined list of preferred networks. Mobile device 12 performs network scanning and attaches to an available network based on the preference list, thus triggering a new ULR from MME 38 of preferred network 34 to HSS 48 of Home Network 42.

[0046] In step 322, NSE 54 determines whether the new ULR originated from preferred network 34. If so, then in step 324, HSS 48 completes the ULR procedure. At this point mobile device 12 has been successfully steered to a preferred network 34 from a non-preferred VPLMN 14.

[0047] Otherwise, if the new ULR originated from another or the same non-preferred VPLMN 14, the method proceeds to step 326. In step 326, it will be determined whether the reject response counter for the network has reached the threshold for a predefined time period—meaning that mobile device 12 has attempted to reattach to the non-preferred VPLMN 14 multiple times. If the threshold number of reattach attempts has not yet been reached, in step 328, HSS 48 increases the reject counter and sends a reject response to the new ULR, thereby causing mobile device to again rescan for available networks.

[0048] Otherwise, if the number of the network attach attempts has reached the predefined threshold, HSS 588 will accept the ULR request in step 330, even if that request originated from a non-preferred VPLMN 14. In these circumstances, the Private LTE/5G network services of preferred network 34 may not be available and, therefore, mobile device 12 will be allowed to attach to non-preferred VPLMN 14 to avoid service interruption. In step 332, HSS 48 will notify NSE 54 of the unsuccessful steering result. NSE 54 will continue to monitor for a next suitable opportunity to request an updated set of value attributes associated with the updated location of mobile device 12.

[0049] FIG. 7 depicts examplary steps for determining when the location information is to be requested from non-preferred VPLMN 14 while mobile device 12 is attached thereto. In step 402, NSE 54 calculates the distance between the current attached Cell-ID and the nearest boundary of network coverage of preferred network 34. In step 404, NSE 54 maintains the decision table of the intervals for requesting location information of mobile device 12 from VPLMN 14. The time intervals can be based on the distance to the nearest boundary of a preferred network 34 and the current location area of mobile device 12. In step 406, NSE 54 selects a time interval (e.g. T1) for the next request for Location Information via an IDR message. The time intervals can be different in different geographic areas according to the density of cellular towers within each area. In step 408, NSE 54 can also maintain the historical time information regarding the time when mobile device 12 has successfully attached to preferred network 34 in the past. In step 410, NSE 54 calculates the time interval (T2) to request for next location information based on the historic behavior of mobile device 12. In step 412, NSE 54 compares the T1 and T2 values and selects the earliest of the two as the time for triggering the next request for location information from VPLMN 14.

[0050] FIGS. 8-10 provide examplary signaling flow diagrams for a scenario in which non-preferred VPLMN 14 is an LTE network, preferred network 34 is a Private LTE Network, and Home Network 42 is also an LTE network. Initially, mobile device 12 is positioned at a location that only has coverage area of non-preferred VPLMN 14. In step 502, mobile device 12 requests to attach to VPLMN 14, and MME 24 of VPLMN 14 sends a ULR to HSS 48 of Home Network 42. In step 504, HSS 48 responds to MME 24 with a ULA message. In step 506, HSS 48 sends an IDR with EPS Location Information Request flag to MME 24. In step 508, MME 24 responds to HSS 48 with an IDA, which includes a set of values for attributes associated with the current location of mobile device 12. In step 510, HSS 48 sends these attribute values to NSE 54.

[0051] In step 512, NSE 54 determines whether preferred network 34 has coverage in the geographic area in which mobile device 12 is currently located. If NSE 54 determines that the current location of mobile device 12 is not within the coverage area of preferred network 34, then NSE 54 will calculate a distance to the nearest location in which preferred network 34 has coverage and will set a timer for time T1, at which mobile device 12 is expected to arrive into a location in which preferred network 34 has coverage. In step 514, upon expiration of the timer T1, NSE 54 triggers a request for Location Information to HSS 48. In step 516, HSS 48 sends another IDR with EPS Location Information Request flag to MME 24, and, in step 518 MME 24 responds with an IDA having updated values for attributes associated with the new current location of mobile device 12. This process is repeated until NSE 54 determines that mobile device 12 has entered coverage area of a preferred network 34.

[0052] FIG. 9 depicts that mobile device 12 has moved to a location in which non-preferred VPLMN 14 and preferred network 34 have overlapping coverage areas. Initially, mobile device 12 is attached to VPLMN 14. In step 602, HSS 48 sends an IDR with EPS Location Information Request flag to MME 24. In step 604, MME 24 responds with an IDA message, which includes a set of values for attributes associated with the current location of mobile device 12. In step 606, HSS 48 sends these values to NSE 54. In step 608, NSE 54 determines that mobile device 12 is within the coverage area of preferred network 34 and, therefore, a Cancel Location Request (CLR) to VPLMN 14 should be triggered. In step 610, NSE 54 sends a command to HSS 48 to send a CLR to MME 24. In step 612, HSS 48 sends a CLR message to MME 24, causing non-preferred VPLMN 14 to detach mobile device 12 from its network. In step 614, MME 24 sends a Cancel Location Answer (CLA) to HSS 48.

[0053] At this point, mobile device 12 will begin to scan for an available network to become attached to. If mobile device 12 attempts to reconnect to non-preferred VPLMN 14, MME 24 will send a ULR message to HSS 48 in step 616. HSS 48 is configured to deny this request and, in step 618, HSS 48 will respond to MME 24 with an Update Location Reject message. Mobile device 12 will continue to try to attach to another available network.

[0054] In step 620, mobile device 12 attaches to preferred network 34. In step 622, MME 38 of preferred network 34 sends a ULR message to HSS 48. HSS 48 will determine that the ULR came from preferred network 34 and will respond with a ULA message in step 624. At this point, mobile device 12 has been successfully steered to preferred network 34. In step 626, HSS 48 will notify NSE 54 to cancel any remaining timers for requesting location information of mobile device 12.

[0055] FIGS. 10-11 depict signaling diagrams for a scenario in which non-preferred VPLMN 14 is a 3G network, preferred network 34 is a Private LTE Network, and Home Network 42 is a 3G network. FIGS. 12-13 depict signaling diagrams for a scenario in which non-preferred VPLMN 14 is a 5G network, preferred network 34 is a Private 5G Network, and Home Network 42 is also a 5G network. The signaling flows for all three scenarios are analogous, although message types exchanged between VPLMN 14, Home Network 42, and preferred network 34 are different. In FIGS. 10-11, Home Network 42 obtains values associated with location of mobile device 12 by sending a MAP Provide Subscriber Info Request message to MSC 18 of VPLMN 14 and receiving a MAP Provide Subscriber Info Response message from MSC 18 of VPLMN 14 containing a set of values for attributes associated with the current location of mobile device 12.

[0056] In FIGS. 12-13, UDM 52 of Home Network 42 accomplishes the task of obtaining attribute values associated with the current location of mobile device 12 by sending Namf Provide Location Info Request message to AMF 30 of VPLMN 14 and receiving Namf Provide Location Response therefrom. To direct VPLMN 14 to detach mobile device 12 when mobile device 12 arrives to a location in which preferred network 34 has coverage, UDM 52 of Home Network 42 sends Nudm UECM Deregistration Notification to AMF 30 of VPLMN 14. Finally, when mobile device 12 attaches to preferred network 34, AMF 45 of preferred network 34 sends Nudm UECM Registration message to UDM 52, to which UDM 52 responds with Nudm UECM Registration Acknowledgement message. Although, scenarios depicted in FIGS. 8-9, 10-11, and 12-13 pertain to different network types, the method of steering mobile device 12 from non-preferred VPLMN 14 to preferred network 34 remains fundamentally unchanged.

TABLE-US-00001 Definitions Name Expansion Definition/Description MME Mobile Unique server in each Mobile Network(4G) to keep Management track of Mobile device and periodically updates HSS Entity MSC Mobile-Services Mobile-Switching Service Center - Unique Server in Switching Center each Mobile network (2G/3G) to keep track of device location and updates HLR/HSS. SGSN Serving GPRS Serving Data Support Node in the cellular network Support Node to keep track of device location for data service. PGW Packet Data PGW interfaces the mobile device to external PDN Network(PDN) networks for Data service. Gateway HLR/HSS Home Location HLR/HSS contains Subscriber information with Register/Home subscription Data and MME that is currently serving Subscriber the Mobile device System UDM Unified Data UDM manages the device subscription profile Management similar to HLR/HSS AMF Access and Interfaces device with UDM Mobility Management function SMF Session Performs Data session control function Management Function UPF User Plane Interfaces device to Data networks at User plane Function (similar to PGW in LTE) Location Location Location Information - Location Area - Location area Information - Information - covered by MME/MSC within Mobile Network LA Location Area Location Location Global Cell Id (MCCMNC + LAC + CI) - Uniquely Information - Information - identifies each cell of Mobile Network operator GCI Global Cell-Id

[0057] Hardware and Software Infrastructure Examples

[0058] The various techniques described herein can be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and system described herein, or certain aspects or portions thereof, can take the form of program code (i.e., instructions) embodied in tangible media, such as hard drives, solid state drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computing device, the machine becomes an apparatus for practicing the invention. In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The program(s) can be implemented in assembly or machine language, if desired. In any case, the language can be a compiled or interpreted language, and combined with hardware implementations.

[0059] The invention can also be practiced via communications embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, or the like, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates to invoke the functionality of the invention. Additionally, any storage techniques used in connection with the invention can be a combination of hardware and software.

[0060] The advantages set forth above, and those made apparent from the foregoing disclosure, are efficiently attained. Since certain changes may be made in the above construction without departing from the scope of the invention, it is intended that all matters contained in the foregoing disclosure or shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.