US 12,604,166 B2Grant

Method and system for dynamic APN selection

Issue Date:2026-04-14

•18 Claims

•7 Drawing Sheets

Abstract

A method for updating communication parameters on a mobile device, the method including sending a communication from the mobile device to a server, the communication including a location of the mobile device; receiving at the mobile device, responsive to the communication, a new communication parameter; reconfiguring the mobile device with the new communication parameter; and sending a second communication from the mobile device to the server, the second communication using the new communication parameter.

Metadata

Assignee

Malikie Innovations Limited

Inventors

Jason Wayne Jantzi
Scott Leonard Dill
Jesse William Bennett
Mark Edward Reaume
Mahendra Fuleshwar Prasad
Alexander Karl Levato
Yu Gao

Application Information

Application Number:US 18/639,602

Filing Date:2024-04-18

Priority Date:2017-10-11

Art Unit:2478

Classifications

IPC:

H04W4/70H04L41/0813H04L43/0811H04L67/00H04L67/02H04L67/12H04W52/02H04W84/00H04W84/18H04W88/10

Patent Drawings (7 sheets)

Description

Cross-Reference to Related Applications

[0001] The present application is a continuation of U.S. patent application Ser. No. 18/193,164 filed Mar. 30, 2023 by Jason Wayne Jantizi, et al. entitled, “Method and System for Dynamic APN Selection”, which is a continuation of U.S. patent application Ser. No. 17/175,019 filed Feb. 12, 2021, now U.S. Pat. No. 11,647,369, which is a continuation of U.S. patent application Ser. No. 15/730,447 filed Oct. 11, 2017, now U.S. Pat. No. 10,952,052, all of which are incorporated by reference herein as if reproduced in their entireties.

Field of the Disclosure

[0002] The present disclosure relates to network connectivity, and in particular relates to latency for network connectivity.

Background

[0003] Internet of Things (IoT) devices, such as vehicle monitoring devices, periodically need to connect to a network element such as a server or cloud service and provide reports. Traditionally, devices connect to the network in the same way, no matter where they are located.

[0004] However, call setup when a device is roaming can introduce significant latency. This in turn means that a modem or communications subsystem on the mobile device needs to be awake for long periods of time.

[0005] The communications subsystem on a mobile device can use significant power resources. For power limited IoT devices, having a communications subsystem operating for long periods of time can significantly drain power resources, thereby reducing the useful life of the IoT device.

Brief Description of the Drawings

[0006] The present disclosure will be better understood with reference to the drawings, in which:

[0007] FIG. 1 is a block diagram of an example sensor apparatus for use with the embodiments of the present disclosure;

[0008] FIG. 2 is a block diagram showing an example environment for a sensor apparatus in accordance with the embodiments of the present disclosure;

[0009] FIG. 3 is a block diagram showing exemplary network architecture;

[0010] FIG. 4 is a data flow diagram showing a mobile device receiving and configuring a new access point name from a server;

[0011] FIG. 5 is a data flow diagram showing a mobile device receiving and configuring a new subscriber identity from a server

[0012] FIG. 6 is a block diagram of an example computing device capable of being used in accordance with the embodiments of the present disclosure.

Detailed Description of the Drawings

[0013] The present disclosure provides a method for updating communication parameters on a mobile device, the method comprising: sending a communication from the mobile device to a server, the communication including a location of the mobile device; receiving at the mobile device, responsive to the communication, a new communication parameter; reconfiguring the mobile device with the new communication parameter; and sending a second communication from the mobile device to the server, the second communication using the new communication parameter.

[0014] The present disclosure further provides a mobile device comprising: a processor; and a communications subsystem, wherein the mobile device is configured to: send a communication from the mobile device to a server, the communication including a location of the mobile device; receive at the mobile device, responsive to the communication, a new communication parameter; reconfigure the mobile device with the new communication parameter; and send a second communication from the mobile device to the server, the second communication using the new communication parameter.

[0015] The present disclosure further provides a computer readable medium for storing instruction code, which, when executed by a processor of a mobile device, cause the mobile device to: send a communication from the mobile device to a server, the communication including a location of the mobile device; receive at the mobile device, responsive to the communication, a new communication parameter; reconfigure the mobile device with the new communication parameter; and send a second communication from the mobile device to the server, the second communication using the new communication parameter.

[0016] The embodiments of the present disclosure are described below using a sensor apparatus within a vehicle monitoring system as an example. However, the present disclosure is not limited to use for vehicles, and the embodiments can be used in other scenarios, including for any mobile device that is roaming in different cellular networks.

[0017] In vehicle operations, sensor systems may be included on the vehicle and have a plurality of sensor apparatuses operating remotely from a central monitoring station to provide remote sensor data to a management or monitoring hub. For example, one sensor system involves fleet management or cargo management systems. In fleet management or cargo management systems, sensors may be placed on a trailer, shipping container or similar product to provide a central station with information regarding the container. Such information may include, but is not limited to, information concerning the current location of the trailer or shipping container, the temperature inside the shipping container or trailer, operational parameters such as tire pressure or engine temperature, that the doors on the shipping container or trailer are closed, whether a sudden acceleration or deceleration event has occurred, the tilt angle of the trailer or shipping container, among other data.

[0018] In other embodiments the sensor apparatus may be secured to a vehicle itself. As used herein, the term vehicle can include any motorized vehicle such as a truck, tractor, car, boat, motorcycle, snow machine, among others, and can further include a trailer, shipping container or other such cargo moving container, whether attached to a motorized vehicle or not.

[0019] In accordance with the embodiments described herein, a sensor apparatus may be any apparatus that is capable of providing data or information from sensors associated with the sensor apparatus to a central monitoring or control station. Sensors associated with the sensor apparatus may either be physically part of the sensor apparatus, for example a built-in global positioning system (GPS) chipset, or may be associated with the sensor apparatus through short range wired or wireless communications. For example, a tire pressure monitor may provide information through a Bluetooth™ Low Energy (BLE) signal from the tire to the sensor apparatus. In other cases, a camera may be part of the sensor apparatus or may communicate with a sensor apparatus through wired or wireless technologies. Other examples of sensors are possible.

[0020] A central monitoring station may be any server or combination of servers that are remote from the sensor apparatus. The central monitoring station can receive data from a plurality of sensor apparatuses.

[0021] One sensor apparatus is shown with regard to FIG. 1. The sensor apparatus of FIG. 1 is however merely an example and other mobile devices could equally be used in accordance with the embodiments of the present disclosure.

[0022] Reference is now made to FIG. 1, which shows an example sensor apparatus 110. Sensor apparatus 110 can be any computing device or network node. Such computing device or network node may include any type of electronic device, including but not limited to, mobile devices such as smartphones or cellular telephones. Examples can further include fixed or mobile devices, such as internet of things devices, endpoints, home automation devices, medical equipment in hospital or home environments, inventory tracking devices, environmental monitoring devices, energy management devices, infrastructure management devices, vehicles or devices for vehicles, fixed electronic devices, among others.

[0023] Sensor apparatus 110 comprises a processor 120 and at least one communications subsystem 130, where the processor 120 and communications subsystem 130 cooperate to perform the methods of the embodiments described herein. Communications subsystem 130 may, in some embodiments, comprise multiple subsystems, for example for different radio technologies.

[0024] Communications subsystem 130 allows sensor apparatus 110 to communicate with other devices or network elements. Communications subsystem 130 may use one or more of a variety of communications types, including but not limited to cellular, satellite, Bluetooth™, Bluetooth™ Low Energy, Wi-Fi, wireless local area network (WLAN), near field communications (NFC), ZigBee, wired connections such as Ethernet or fiber, among other options.

[0025] As such, a communications subsystem 130 for wireless communications will typically have one or more receivers and transmitters, as well as associated components such as one or more antenna elements, local oscillators (LOs), and may include a processing module such as a digital signal processor (DSP). As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem 130 will be dependent upon the communication network or communication technology on which the sensor apparatus is intended to operate.

[0026] If communications subsystem 130 operates over a cellular connection, a subscriber identity module (SIM) 132 may be provided to allow such communication. SIM 132 may be a physical card or may be virtual. In some embodiments SIM 132 may also be referred to as a universal subscriber identity module (USIM), as merely an identity module (IM), or as an embedded Universal Integrated Circuit Card (eUICC), among other options.

[0027] Processor 120 generally controls the overall operation of the sensor apparatus 110 and is configured to execute programmable logic, which may be stored, along with data, using memory 140. Memory 140 can be any tangible, non-transitory computer readable storage medium, including but not limited to optical (e.g., CD, DVD, etc.), magnetic (e.g., tape), flash drive, hard drive, or other memory known in the art.

[0028] Alternatively, or in addition to memory 140, sensor apparatus 110 may access data or programmable logic from an external storage medium, for example through communications subsystem 130.

[0029] In the embodiment of FIG. 1, sensor apparatus 110 may utilize a plurality of sensors, which may either be part of sensor apparatus 110 in some embodiments or may communicate with sensor apparatus 110 in other embodiments. For internal sensors, processor 120 may receive input from a sensor subsystem 150.

[0030] Examples of sensors in the embodiment of FIG. 1 include a positioning sensor 151, a vibration sensor 152, a temperature sensor 153, one or more image sensors 154, accelerometer 155, light sensors 156, gyroscopic sensors 157, and other sensors 158. Other sensors may be any sensor that is capable of reading or obtaining data that may be useful for sensor apparatus 110. However, the sensors shown in the embodiment of FIG. 1 are merely examples, and in other embodiments different sensors or a subset of sensors shown in FIG. 1 may be used.

[0031] Further, in some embodiments, sensor apparatus 110 may act as a gateway, and may communicate with other sensor apparatuses (not shown) on the trailer, where the other sensor apparatuses may act as hubs for a subset of the sensors on the vehicle or trailer.

[0032] Communications between the various elements of sensor apparatus 110 may be through an internal bus 160 in one embodiment. However, other forms of communication are possible.

[0033] Sensor apparatus 110 may be affixed to any fixed or portable platform. For example, sensor apparatus 110 may be affixed to shipping containers, truck trailers, truck cabs in one embodiment. In other embodiments, sensor apparatus 110 may be affixed to any vehicle, including motor vehicles (e.g., automobiles, cars, trucks, buses, motorcycles, etc.), aircraft (e.g., airplanes, unmanned aerial vehicles, unmanned aircraft systems, drones, helicopters, etc.), spacecraft (e.g., spaceplanes, space shuttles, space capsules, space stations, satellites, etc.), watercraft (e.g., ships, boats, hovercraft, submarines, etc.), railed vehicles (e.g., trains and trams, etc.), and other types of vehicles including any combinations of any of the foregoing, whether currently existing or after arising, among others.

[0034] In other cases, sensor apparatus 110 could be carried by a user.

[0035] In other cases, sensor apparatus 110 may be affixed to stationary objects including buildings, lamp posts, fences, cranes, among other options.

[0036] Such sensor apparatus 110 may be a power limited device. For example sensor apparatus 110 could be a battery operated device that can be affixed to a shipping container or trailer in some embodiments. Other limited power sources could include any limited power supply, such as a small generator or dynamo, a fuel cell, solar power, among other options.

[0037] In other embodiments, sensor apparatus 110 may utilize external power, for example from the engine of a tractor pulling the trailer, from a land power source for example on a plugged in recreational vehicle or from a building power supply, among other options.

[0038] External power may further allow for recharging of batteries to allow the sensor apparatus 110 to then operate in a power limited mode again. Recharging methods may also include other power sources, such as, but not limited to, solar, electromagnetic, acoustic or vibration charging.

[0039] The sensor apparatus from FIG. 1 may be used in a variety of environments. One example environment in which the sensor apparatus may be used is shown with regard to FIG. 2.

[0040] Referring to FIG. 2, three sensor apparatuses, namely sensor apparatus 210, sensor apparatus 212, and sensor apparatus 214 are provided.

[0041] In the example of FIG. 2, sensor apparatus 210 may communicate through a cellular base station 220 or through an access point 222. Access point 222 may be any wireless communication access point. For example, access point 222 may be a WiFi router or a private router network. Also, a private router network may have a path from the APN to a server, and may reduce network latency based on a location of the sensor apparatus in some embodiments.

[0042] Further, in some embodiments, sensor apparatus 210 could communicate through a wired access point such as Ethernet or fiber, among other options.

[0043] The communication may then proceed over a wide area network such as Internet 230 and proceed to servers 240 or 242.

[0044] Similarly, sensor apparatus 212 and sensor apparatus 214 may communicate with servers 240 or server 242 through one or both of the base station 220 or access point 222, among other options for such communication.

[0045] In other embodiments, any one of sensors 210, 212 or 214 may communicate through satellite communication technology. This, for example, may be useful if the sensor apparatus is travelling to areas that are outside of cellular coverage or access point coverage.

[0046] In other embodiments, sensor apparatus 212 may be out of range of access point 222, and may communicate with sensor apparatus 210 to allow sensor apparatus 210 to act as a relay for communications.

[0047] Communication between sensor apparatus 210 and server 240 may be one directional or bidirectional. Thus, in one embodiment sensor apparatus 210 may provide information to server 240 but server 240 does not respond. In other cases, server 240 may issue commands to sensor apparatus 210 but data may be stored internally on sensor apparatus 210 until the sensor apparatus arrives at a particular location. In other cases, two-way communication may exist between sensor apparatus 210 and server 240.

[0048] A server, central server, processing service, endpoint, Uniform Resource Identifier (URI), Uniform Resource Locator (URL), back-end, and/or processing system may be used interchangeably in the descriptions herein. The server functionality typically represents data processing/reporting that are not closely tied to the location of movable image capture apparatuses 210, 212, 214, etc. For example, the server may be located essentially anywhere so long as it has network access to communicate with image capture apparatuses 210, 212, 214, etc.

[0049] Server 240 may, for example, be a fleet management centralized monitoring station. In this case, server 240 may receive information from sensor apparatuses associated with various trailers or cargo containers, providing information such as the location of such cargo containers, the temperature within such cargo containers, system information such as tire pressure or vibration sensor readings, any unusual events including sudden decelerations, temperature warnings when the temperature is either too high or too low, among other data. The server 240 may compile such information and store it for future reference. It may further alert an operator. For example, a sudden deceleration event may indicate that a trailer may have been in an accident and the operator may need to call emergency services and potentially dispatch another tractor to the location.

[0050] In other embodiments, server 240 may be a facilities management server, and direct loading and unloading of goods to vehicles in particular bays of the facility.

[0051] Other examples of functionality for server 240 are possible.

[0052] In the embodiment of FIG. 2, servers 240 and 242 may further have access to third-party information or information from other servers within the network. For example, a data services provider 250 may provide information to server 240. Similarly, a data repository or database 260 may also provide information to server 240.

[0053] For example, data services provider 250 may be a subscription based service used by server 240 to obtain current road and weather conditions.

[0054] Data repository or database 260 may for example provide information such as image data associated with a particular location, aerial maps, low latency access point names, virtual SIM information, or other such information.

[0055] The types of information provided by data service provider 250 or the data repository or database 260 is not limited to the above examples and the information provided could be any data useful to server 240.

[0056] In some embodiments, information from data service provider 250 or the data repository from database 260 can be provided to one or more of sensor apparatuses 210, 212, or 214 or processing at those sensor apparatuses.

[0057] If sensor apparatus 110, 210, 212 or 214 communicate through a cellular network, one example of a network for such communication is shown with regard to FIG. 3.

[0058] FIG. 3 shows a block diagram of a communication system 300 which includes a device 302 which communicates through a wireless communication network.

[0059] Device 302 communicates wirelessly with one of multiple access points such as Node Bs 306 in Universal Terrestrial Radio Access Network (UTRAN) 320 or with evolved Node B (eNB) 308 in evolved UTRAN (EUTRAN) 322. Each Node B 306 or eNB 308 is responsible for air interface processing and some radio resource management functions. Further, Node B 306 provides functionality similar to a Base Transceiver Station in a GSM/GPRS networks.

[0060] The wireless link shown in communication system 300 of FIG. 3 represents one or more different channels, typically different radio frequency (RF) channels, and associated protocols used between the wireless network and device 302. A Uu air interface 304 is used between device 302 and Node B 306.

[0061] Those skilled in art will appreciate that a wireless network in actual practice may include hundreds of cells depending upon desired overall expanse of network coverage. All pertinent network components may be connected by multiple switches and routers (not shown), controlled by multiple network controllers.

[0062] Each Node B 306 communicates with a radio network controller (RNC) 310. The RNC 310 is responsible for control of the radio resources in its area. One RNC 310 controls multiple Node Bs 306.

[0063] The RNC 310 in UMTS networks provides functions equivalent to the Base Station Controller (BSC) functions in GSM/GPRS networks. However, an RNC 310 includes more intelligence including, for example, autonomous handovers management without involving MSCs and SGSNs.

[0064] For eNB 308, RNC functionality may be included in the eNB.

[0065] The interface used between Node B 306 and RNC 310 is an Iub interface 309. An NBAP (Node B application part) signaling protocol is primarily used.

[0066] UTRAN 320 comprises the RNC 310, Node B 306, the Uu air interface 304, and Iub interface 309.

[0067] Circuit switched traffic is routed to Mobile Switching Centre (MSC) 330. MSC 330 is the computer that places the calls, and takes and receives data from the subscriber or from PSTN (not shown).

[0068] Traffic between RNC 310 and MSC 330 uses the Iu-CS interface 328. Iu-CS interface 328 is the circuit-switched connection for carrying (typically) voice traffic and signaling between UTRAN 320 and the core voice network. The main signaling protocol used is RANAP (Radio Access Network Application Part). The RANAP protocol is used in UMTS signaling between the Core Network, which can be a MSC 330 or SGSN 350 (defined in more detail below) and UTRAN 320.

[0069] For all devices 302 registered with a network operator, permanent data (such as a user's profile) as well as temporary data (such as current location) are stored in a home location registry (HLR) 338.

[0070] A Visitor Location Register (VLR) 336 of MSC 330 is responsible for a group of location areas and stores the data of those mobile stations that are currently in its area of responsibility.

[0071] Packet data is routed through Service GPRS Support Node (SGSN) 350. SGSN 350 is the gateway between the RNC and the core network in a LTE/GPRS/UMTS network and is responsible for the delivery of data packets from and to the UEs within its geographical service area. Iu-PS interface 348 is used between the RNC 310 and SGSN 350, and is the packet-switched connection for carrying (typically) data traffic and signaling between the UTRAN 320 and the core data network. The main signaling protocol used is RANAP (described above).

[0072] The SGSN 350 communicates with the Gateway GPRS Support Node (GGSN) 360. GGSN 360 provides the interface between the UMTS/GPRS network and other networks such as the Internet or private networks. GGSN 360 is connected to a public data network PDN 362 over a Gi interface.

[0073] For EUTRAN operations (for example for Long Term Evolution (LTE) operation), EUTRAN 322 comprises eNB 308, the Uu air interface 305, and an S1 interface 324.

[0074] eNB 308 communicates with an Evolved Packet Core (EPC), which in part comprises a Mobility Management Entity (MME) 370, Serving Gateway (S-GW) 372 and Packet Data Network (PDN) Gateway (P-GW) 376.

[0075] MME 370 controls operation of device 302 through signaling messages and a Home Subscriber Server (HSS).

[0076] S-GW 372 acts as a router and forwards data to the P-GW 376 over and S5/S8 interface 374. Communication between MME 370 and S-GW 372 uses an S11 interface 371.

[0077] P-GW 376 provides the interface between the LTE network and other networks such as the Internet or private networks. P-GW 376 is connected to a public data network PDN 362 over an SGi interface.

[0078] Those skilled in art will appreciate that wireless network may be connected to other systems, possibly including other networks, not explicitly shown in FIG. 3.

[0079] Further, while FIG. 3 discusses UMTS and other 3G systems, and LTE and other 4G systems, the present disclosure could equally be used with other networks such as 5G systems.

[0080] When a device 302 roams to a network outside of the home network of such device, the device may use an Access Point Name (APN) as the communication interface between the device and the GGSN 360 or P-GW 376. The APN is a gateway between different public networks such as the Global System for Mobile Communications (GSM), the GSM Packet Radio Service (GPRS), 3G or 4G and the public Internet.

[0081] Generally, even if the device 302 roams to another network, it will still use the gateway from its home network.

[0082] In accordance with one embodiment of the present disclosure, the APN settings on a device 302 may be changed dynamically through communications with a server or cloud service to improve overall system performance. In particular, in accordance with the embodiments described herein, location based information may be used to save network connectivity costs. Such costs include power or current drain costs, as well as overall network connectivity overhead. A mobile device, such as a sensor apparatus, may know its location both when it is in a dynamic or moving state and when it is in a static or fixed state. Further, in some embodiments, data may only be accepted in response to messages sent from the sensor apparatus.

[0083] Therefore, in accordance with the present disclosure, information can be used to reduce the cellular connectivity cost overhead and power in order to optimize communications.

[0084] Specifically, in one embodiment the server can make a determination for a new access point name for the sensor apparatus and communicate such access point name to the sensor apparatus. Thereafter, on a subsequent reporting cycle, the sensor apparatus may change its APN settings, which may allow packets to be routed on a preferred link that has a lower latency or overhead. Such routing would improve the battery or power performance of the sensor apparatus.

[0085] Reference is now made to FIG. 4. In the embodiment of FIG. 4, a mobile device 410 such as a sensor apparatus communicates with a server 412.

[0086] As seen at block 420, the mobile device 410 may wake up. In one embodiment, the wake up may be periodic based on a threshold time between sensor reporting events. In other embodiments, the waking up of the mobile device 410 at block 420 may be based on an event occurring. For example, if a high impact event is detected at the mobile device then the mobile device may wake at block 420.

[0087] A process at the mobile device 410 then proceeds to block 422 in which the device obtains its current location using an onboard Global Navigation Satellite System (GNSS), such as a Global Positioning System (GPS).

[0088] The device may then perform a server update, as shown by arrow 430. The device may provide the server with information regarding the mobile device 410. For example, the update at arrow 430 may include a unique identifier for the update packet. It may further contain information such as the device GPS location, sensor data such as tire pressure, fluid temperatures, among other options. The server update at block 430 utilizes an APN previously configured at mobile device 410.

[0089] Server 412 may be a cloud service or other server such as those described in FIG. 1. Server 412 receives the server update at arrow 430 and may extract the location from the update message.

[0090] The server 412 may then process the message and, among its functionality, may consider the APN and location of the mobile device 410. The server 412 may use a search, for example using a database associated with server 412, to find the best APN for the sensor apparatus given its current location. The database may further use other information such as historic data to optimize the APN for reduced latency. Such search for an optimized APN is for example, shown in block 440 of the FIG. 4.

[0091] In particular, in one embodiment server 412 may receive information from a plurality of mobile devices regarding network conditions and delays experienced by the mobile devices. For example, the information may be conveyed to the server in a server update message 430, or may be conveyed in other messages.

[0092] For example, in one embodiment information from each mobile device may include statistics such as, but not limited to, the radio signal strength indicator (RSSI), mobile country code (MCC), mobile network code (MNC), location area code (LAC), absolute radiofrequency channel number (ARFCN), cell ID, available radio access technologies, circuit-switched (CS) and packet switched (PS) registration time, packet data protocol (PDP) request time, whether the mobile is roaming or not roaming, a time to network acquisition, a total network session time duration, among other options. However, in some embodiments a subset of the above may be utilized. In other embodiments, other information may also be provided by the mobile devices to server 412.

[0093] The server may then use statistics received from one or more mobile devices to create a profile for a particular location in order to determine an optimized APN for the location. The profile may be created, for example, using a learning algorithm which updates a look-up table accessible by server 412. In some embodiments, the lookup table can be periodically updated with new information to ensure optimized APN selection.

[0094] The use of historic data may in some cases benefit from having many mobile devices use a route, or the same route be used by the same mobile device multiple times. In this case, more data can be used to make the determination of the optimized APN.

[0095] In other embodiments, instead of, or in addition to, historic data, RSSI coverage maps from mobile network operators may be used to find an optimized APN. Specifically, such coverage maps are provided by the mobile network operators and can assist a server 412 to determine which locations should be using which APNs.

[0096] Server 412 may then provide the optimized APN that was found at block 440 back to mobile device 410, as shown by arrow 450. For example, the new APN may be embedded into a profile message that is sent at arrow 450.

[0097] The mobile device 410 receives the message at arrow 450 and may store the information prior to going into a sleep state, as shown by block 460.

[0098] The next wake state is shown by block 462, at which point the device may configure the communications subsystem with the new APN, as shown by block 464. The configuration of the new APN may involve changing the communication settings at mobile device 410.

[0099] The configuration at block 464 may further include, in some embodiments, the mobile device 410 reconfiguring its packet data connection settings using the new APN. After the configuration at block 464, the mobile device 410 may then use the new APN for communication.

[0100] The process at the mobile device may then proceed to block 466 in which location information is found.

[0101] A mobile device 410 may then perform a server update with server 412, shown by arrow 470, utilizing the new APN that was received in the message at arrow 450. Such new APN generally will result in reduced set up latency and thus battery savings at sensor apparatus 410.

[0102] In a other embodiments, instead of updating the APN, other communication parameters may be updated. Thus, in one embodiment, a further communication parameter that may be updated is the subscriber identity at the sensor apparatus.

[0103] Specifically, reference is now made to FIG. 5. In the embodiment of FIG. 5, a mobile device 510 such as a sensor apparatus communicates with a server 512.

[0104] The mobile device 510 may wake up at block 520. Such wake up may be periodic or based on events at the mobile device.

[0105] From block 520 the process at the mobile device may then proceed to block 522 in which the current location of the mobile device is obtained.

[0106] The mobile device 510 may then perform a server update, shown by the message at arrow 530. Such server update may include the current location of the mobile device 510.

[0107] Server 512 receives the update message at arrow 530 and may find an optimized subscriber identity for the sensor apparatus at block 540. Such subscriber identity may be based on the current location of the mobile device.

[0108] In particular, in one embodiment server 512 may receive information from a plurality of mobile devices regarding network conditions and delays experienced by the mobile devices. For example, the information may be conveyed to the server in a server update message 530, or may be conveyed in other messages.

[0109] For example, in one embodiment information from each mobile device may include statistics such as, but not limited to, the radio signal strength indicator (RSSI), mobile country code (MCC), mobile network code (MNC), location area code (LAC), absolute radiofrequency channel number (ARFCN), cell ID, available radio access technologies, circuit-switched (CS) and packet switched (PS) registration time, packet data protocol (PDP) request time, whether the mobile is roaming or not roaming, a time to network acquisition, a total network session time duration, among other options. However, in some embodiments a subset of the above may be utilized. In other embodiments, other information may also be provided by the mobile devices to server 512.

[0110] The server may then use statistics received from one or more mobile devices to create a profile for a particular location in order to determine an optimized SIM profile for the location. The profile may be created, for example, using a learning algorithm which updates a look-up table accessible by server 512. In some embodiments, the lookup table can be periodically updated with new information to ensure optimized SIM profile selection.

[0111] The use of historic data may in some cases benefit from having many mobile devices use a route, or the same route be used by the same mobile device multiple times. In this case, more data can be used to make the determination of the optimized SIM profile.

[0112] In other embodiments, instead of, or in addition to, historic data, RSSI coverage maps from mobile network operators may be used to find an optimized SIM profile. Specifically, such coverage maps are provided by the mobile network operators and can assist a server 512 to determine which locations should be using which SIM profiles.

[0113] Once the subscriber identity is obtained, the subscriber identity may be returned in a profile message shown at arrow 550 back to mobile device 510. In one embodiment, APN profiles may be associated with the SIM profile and may be stored at the mobile device 510. In this way, the stored APN profile may be used to perform a server update after a SIM profile change.

[0114] On receipt of the message at arrow 550, mobile device 510 stores the subscriber identity information and may then go into a sleep state, shown by block 560.

[0115] The mobile device may then wake at block 562.

[0116] Based on the information received in the message at arrow 550, the mobile device 510 may then configure a new SIM at block 564. As will be appreciated by those in the art, the configuration of the SIM may include virtually replacing the subscriber identity at the communications subsystem in order to use the new subscriber identity for future communications.

[0117] Once the configuration is finished at block 564, the mobile device 510 may then find its location at block 566 and then perform a server update shown by arrow 570 utilizing the new SIM.

[0118] Based on the above, packets can be routed to a preferred low latency links using either an updated APN or updated subscriber identity which is received as a new communication parameter from a server between communication cycles. This allows packets to be routed to a preferred link that is lower latency and overhead and therefore improves the battery life on the sensor apparatus.

[0119] A server such as servers 412 or 512 may be any network node. For example, one simplified server that may perform the embodiments described above is provided with regards to FIG. 6.

[0120] In FIG. 6, server 610 includes a processor 620 and a communications subsystem 630, where the processor 620 and communications subsystem 630 cooperate to perform the methods of the embodiments described herein.

[0121] The processor 620 is configured to execute programmable logic, which may be stored, along with data, on the server 610, and is shown in the example of FIG. 6 as memory 640. The memory 640 can be any tangible, non-transitory computer readable storage medium, such as optical (e.g., CD, DVD, etc.), magnetic (e.g., tape), flash drive, hard drive, or other memory known in the art. In one embodiment, processor 620 may also be implemented entirely in hardware and not require any stored program to execute logic functions.

[0122] Alternatively, or in addition to the memory 640, the server 610 may access data or programmable logic from an external storage medium, for example through the communications subsystem 630.

[0123] The communications subsystem 630 allows the server 610 to communicate with other devices or network elements.

[0124] Communications between the various elements of the server 610 may be through an internal bus 660 in one embodiment. However, other forms of communication are possible.

[0125] The embodiments described herein are examples of structures, systems or methods having elements corresponding to elements of the techniques of this application. This written description may enable those skilled in the art to make and use embodiments having alternative elements that likewise correspond to the elements of the techniques of this application. The intended scope of the techniques of this application thus includes other structures, systems or methods that do not differ from the techniques of this application as described herein, and further includes other structures, systems or methods with insubstantial differences from the techniques of this application as described herein.

[0126] While operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be employed. Moreover, the separation of various system components in the implementation descried above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a signal software product or packaged into multiple software products. In some cases, functions may be performed entirely in hardware and such a solution may be the functional equivalent of a software solution

[0127] Also, techniques, systems, subsystems, and methods described and illustrated in the various implementations as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and may be made.

[0128] While the above detailed description has shown, described, and pointed out the fundamental novel features of the disclosure as applied to various implementations, it will be understood that various omissions, substitutions, and changes in the form and details of the system illustrated may be made by those skilled in the art. In addition, the order of method steps is not implied by the order they appear in the claims.

[0129] When messages are sent to/from an electronic device, such operations may not be immediate or from the server directly. They may be synchronously or asynchronously delivered, from a server or other computing system infrastructure supporting the devices/methods/systems described herein. The foregoing steps may include, in whole or in part, synchronous/asynchronous communications to/from the device/infrastructure. Moreover, communication from the electronic device may be to one or more endpoints on a network. These endpoints may be serviced by a server, a distributed computing system, a stream processor, etc. Content Delivery Networks (CDNs) may also provide may provide communication to an electronic device. For example, rather than a typical server response, the server may also provision or indicate a data for content delivery network (CDN) to await download by the electronic device at a later time, such as a subsequent activity of electronic device. Thus, data may be sent directly from the server, or other infrastructure, such as a distributed infrastructure, or a CDN, as part of or separate from the system.

[0130] Typically, storage mediums can include any or some combination of the following: a semiconductor memory device such as a dynamic or static random access memory (a DRAM or SRAM), an erasable and programmable read-only memory (EPROM), an electrically erasable and programmable read-only memory (EEPROM) and flash memory; a magnetic disk such as a fixed, floppy and removable disk; another magnetic medium including tape; an optical medium such as a compact disk (CD) or a digital video disk (DVD); or another type of storage device. Note that the instructions discussed above can be provided on one computer-readable or machine-readable storage medium, or alternatively, can be provided on multiple computer-readable or machine-readable storage media distributed in a large system having possibly plural nodes. Such computer-readable or machine-readable storage medium or media is (are) considered to be part of an article (or article of manufacture). An article or article of manufacture can refer to any manufactured single component or multiple components. The storage medium or media can be located either in the machine running the machine-readable instructions, or located at a remote site from which machine-readable instructions can be downloaded over a network for execution.

[0131] In the foregoing description, numerous details are set forth to provide an understanding of the subject disclosed herein. However, implementations may be practiced without some of these details. Other implementations may include modifications and variations from the details discussed above. It is intended that the appended claims cover such modifications and variations.

Claims

The invention claimed is:

1. A method for updating communication parameters on a device, the method comprising:

waking up the device at a periodic time;

upon waking up, transmitting sensor data from sensors associated to the device to a server, the transmitting comprising sending a location of the device;

receiving at the device, responsive to the transmitting, a new communication parameter;

after receiving the new communication parameter, entering a sleep state at the device;

virtually replacing a subscriber identity associated with the device with a new subscriber identity based on the new communication parameter; and

sending a second communication from the device to the server, the second communication using the new communication parameter, wherein the second communication includes the location of the device and the new communication parameter is associated with the new subscriber identity determined based on the location of the device.

2. The method of claim 1, wherein the device is a sensor apparatus associated with a vehicle.

3. The method of claim 2, wherein the communication comprises a periodic server update.

4. The method of claim 1, wherein access point name profiles are associated with the new subscriber identity.

5. The method of claim 4, wherein the access point name profiles are stored at the device.

6. The method of claim 4, wherein the access point name profiles are used to perform a server update upon replacing the subscriber identity with the new subscriber identity.

7. The method of claim 1, wherein the device is a mobile device.

8. The method of claim 1, wherein the entering of the sleep state at the device comprises the device entering the sleep state or a module of the device entering the sleep state.

9. A device comprising:

a processor; and

a communications subsystem,

wherein the device is configured to:

wake up the device at a periodic time;

upon waking up, transmit sensor data from sensors associated to the device to a server, the transmitting comprising sending a location of the device;

receive at the device, responsive to the transmitting, a new communication parameter;

after receiving the new communication parameter, enter a sleep state;

virtually replace a subscriber identity associated with the device with a new subscriber identity based on the new communication parameter; and

send a second communication from the device to the server, the second communication using the new communication parameter, wherein the second communication includes the location of the device and the new communication parameter is associated with the new subscriber identity determined based on the location of the device.

10. The device of claim 9, wherein the device is a sensor apparatus associated with a vehicle.

11. The device of claim 10, wherein the communication comprises a periodic server update.

12. The device of claim 9, wherein access point name profiles are associated with the new subscriber identity.

13. The device of claim 12, wherein the access point name profiles are stored at the device.

14. The device of claim 12, wherein the access point name profiles are used to perform a server update upon replacing the subscriber identity with the new subscriber identity.

15. The device of claim 9, wherein the sleep state comprises the mobile device being asleep or a module of the mobile device being asleep.

16. A non-transitory computer readable medium for storing instruction code, which, when executed by a processor of a device, cause the device to:

wake up the device at a periodic time;

upon waking up, transmit sensor data from sensors associated to the device to a server, the transmitting comprising sending a location of the device;

receive at the device, responsive to the transmitting, a new communication parameter;

after receiving the new communication parameter, enter a sleep state;

virtually replace a subscriber identity associated with the device with a new subscriber identity based on the new communication parameter; and

17. The non-transitory computer readable medium of claim 16, wherein the device is a sensor apparatus associated with a vehicle.

18. The non-transitory computer readable medium of claim 16, wherein the sleep state comprises the mobile device being asleep or a module of the mobile device being asleep.

Patent Citations (45)

Patent	Date	Inventor	Cited By
US10952052(B2)	2021-03-01	Jantzi et al.	Applicant
US11647369(B2)	2023-05-01	Jantzi et al.	Applicant
US11991611(B2)	2024-05-01	Jantzi et al.	Applicant
US2006/0271517(A1)	2006-11-01	Deloach, Jr.	Applicant
US2007/0213050(A1)	2007-09-01	Jiang	Examiner
US2008/0076419(A1)	2008-03-01	Khetawat et al.	Applicant
US2008/0186882(A1)	2008-08-01	Scherzer et al.	Applicant
US2009/0298467(A1)	2009-12-01	Zohar	Examiner
US2011/0039518(A1)	2011-02-01	Maria	Applicant
US2011/0122858(A1)	2011-05-01	Yashiro et al.	Applicant
US2013/0002483(A1)	2013-01-01	Rowitch et al.	Applicant
US2013/0023284(A1)	2013-01-01	Stanger	Applicant
US2013/0039337(A1)	2013-02-01	Hwang et al.	Applicant
US2013/0185421(A1)	2013-07-01	Yang	Applicant
US2013/0281085(A1)	2013-10-01	Sen	Examiner
US2014/0010185(A1)	2014-01-01	Morita et al.	Applicant
US2014/0112328(A1)	2014-04-01	Wang	Applicant
US2015/0004997(A1)	2015-01-01	Gao et al.	Applicant
US2015/0081884(A1)	2015-03-01	Maguire et al.	Applicant
US2015/0195364(A1)	2015-07-01	Petersen et al.	Applicant
US2015/0195760(A1)	2015-07-01	Sanz et al.	Applicant
US2015/0201322(A1)	2015-07-01	Kim et al.	Applicant
US2015/0304437(A1)	2015-10-01	Vaccari et al.	Applicant
US2015/0347999(A1)	2015-12-01	Lau	Examiner
US2016/0014692(A1)	2016-01-01	Kim et al.	Applicant
US2016/0192263(A1)	2016-06-01	Zembutsu et al.	Applicant
US2016/0198404(A1)	2016-07-01	Tsiatsis et al.	Applicant
US2016/0295544(A1)	2016-10-01	Jiang et al.	Applicant
US2017/0078156(A1)	2017-03-01	Lazarescu et al.	Applicant
US2017/0111315(A1)	2017-04-01	Long	Applicant
US2017/0180929(A1)	2017-06-01	Cavendish	Examiner
US2017/0180963(A1)	2017-06-01	Cavendish et al.	Applicant
US2017/0265100(A1)	2017-09-01	Ryu et al.	Applicant
US2017/0289788(A1)	2017-10-01	Lalwaney	Applicant
US2017/0353452(A1)	2017-12-01	Wang	Applicant
US2018/0103413(A1)	2018-04-01	Hosey	Examiner
US2018/0109433(A1)	2018-04-01	Nagaraj et al.	Applicant
US2018/0167906(A1)	2018-06-01	Chellamani et al.	Applicant
US2018/0248787(A1)	2018-08-01	Rajagopal et al.	Applicant
US2021/0152976(A1)	2021-05-01	Daoura et al.	Applicant
US2023/0020832(A1)	2023-01-01	Hotchkiss et al.	Applicant
US2023/0201517(A1)	2023-06-01	Rizkalla	Applicant
CA2793439(C)	2013-08-01		Applicant
WO2008046264(A1)	2008-04-01		Applicant
WO2011024030(A1)	2011-03-01		Applicant

Non-Patent Literature (20)

Office Action dated Nov. 27, 2018; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 11 pages.Applicant
Final Office Action dated Apr. 2, 2019; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 10 pages.Applicant
Advisory Action dated Jun. 18, 2019; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 5 pages.Applicant
Office Action dated Jul. 15, 2019; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 17 pages.Applicant
Final Office Action dated Oct. 24, 2019; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 12 pages.Applicant
Advisory Action dated Jan. 13, 2020; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 5 pages.Applicant
Office Action dated Apr. 20, 2020; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 13 pages.Applicant
Final Office Action dated Aug. 25, 2020; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 15 pages.Applicant
Notice of Allowance dated Nov. 12, 2020; U.S. Appl. No. 15/730,447, filed Oct. 11, 2017; 13 pages.Applicant
Office Action dated Aug. 31, 2022; U.S. Appl. No. 17/175,019, filed Feb. 12, 2021; 24 pages.Applicant
Final Office Action dated Dec. 8, 2022; U.S. Appl. No. 17/175,019, filed Feb. 12, 2021; 15 pages.Applicant
Notice of Allowance dated Feb. 23, 2023; U.S. Appl. No. 17/175,019, filed Feb. 12, 2021; 8 pages.Applicant
Office Action dated Oct. 11, 2023; U.S. Appl. No. 18/193,164, filed Mar. 30, 2023; 21 pages.Applicant
Notice of Allowance dated Jan. 30, 2024; U.S. Appl. No. 18/193,164, filed Mar. 30, 2023; 8 pages.Applicant
Canadian Office Action; Application No. 3,018,503; Sep. 25, 2023; 4 pages.Applicant
European Partial Search Report; Application No. 18198151.5; Feb. 28, 2019; 15 pages.Applicant
European Extended Search Report; Application No. 18198151.5; Jun. 12, 2019; 12 pages.Applicant
European Examination Report; Application No. 18198151.5; Dec. 8, 2020; 7 pages.Applicant
European Examination Report; Application No. 18198151.5; Jun. 25, 2021; 6 pages.Applicant
European Examination Report; Application No. 18198151.5; May 14, 2024; 12 pages.Applicant

Abstract