# US 10,873,983 B1 · Method and device for selecting a network mode for an internet of things device

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,873,983 B1
- Document ID: US10873983B1
- Status: Granted
- Kind: B1
- Application number: 16/511,636
- Filed: 2019-07-15
- Granted: 2020-12-22
- Earliest claimed: 2019-07-15
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Sudhir Patel; Jeremy Nacer; Sachin Kamat; David G. Greiner; Nanjun Qian; Ye Huang; Jin Yang
- Web page: https://patentgrep.com/patent/US10873983B1

## CPC

- H04W 76/14: Direct-mode setup
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 8/005: {Discovery of network devices, e.g. terminals}
- H04W 48/16: Discovering, processing access restriction or access information
- H04W 52/0241: {where no transmission is received, e.g. out of range of the transmitter}
- H04W 52/0258: {controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day}
- H04W 88/02: Terminal devices
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

An Internet of Things (IoT) device may receive a network configuration profile including one or more parameters relating to a scan interval and a mode priority of the IoT device indicating a priority for a first IoT network over a second IoT network. The IoT device may scan for an availability of the first IoT network. Based on determining that the first IoT network is unavailable, the IoT device may scan for an availability of the second IoT network. Based on determining that the second IoT network is available, the IoT device may initiate a network connection with the second IoT network. While connected to the second IoT network, the IoT device may scan for the availability of the first IoT network. Based on determining that the first IoT network is available, the IoT device may initiate a network connection with the first IoT network.

## Claims

### Claim 1

A method, comprising:
receiving, by an Internet of Things (IoT) device and from an IoT control device, a network configuration profile,
wherein the network configuration profile includes one or more parameters relating to a mode priority and a scan interval of the IoT device, and
wherein the mode priority indicates a priority for a first IoT network over a second IoT network;
scanning, by the IoT device, for an availability of the first IoT network;
scanning, by the IoT device and based on determining that the first IoT network is unavailable, for an availability of the second IoT network;
initiating, by the IoT device and based on determining that the second IoT network is available, a network connection with the second IoT network;
scanning, by the IoT device, while the IoT device is connected to the second IoT network, and after the scan interval, for the availability of the first IoT network; and
initiating, by the IoT device and based on determining that the first IoT network is available, a network connection with the first IoT network.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first IoT network and the second IoT network correspond to a common network operator.

### Claim 3 (depends on 1)

The method of claim 1, wherein the network configuration profile includes one or more parameters relating to a power save duration and a scan duration of the IoT device,
wherein the power save duration corresponds to a duration of a power save mode of operation,
wherein the scan duration corresponds to a duration for scanning for the availability of the first IoT network and the availability of the second IoT network, and
wherein the power save mode of operation is initiated based on determining that the first IoT network is unavailable and the second IoT network is unavailable for the scan duration.

### Claim 4 (depends on 1)

The method of claim 1, wherein the network configuration profile includes one or more parameters relating to an exception to the mode priority of the IoT device,
wherein the exception corresponds to a device management session, and
wherein the device management session disables the mode priority, and maintains the one of the network connection with the first IoT network or the network connection with the second IoT network for a duration of the device management session.

### Claim 5 (depends on 1)

The method of claim 1, wherein the mode priority indicates a priority for one or more of a Long-Term Evolution (LTE) category M1 network, a 5G category M1 network, an LTE category Narrow Band-Internet of Things (NB-IoT) network, a 5G category NB-IoT network, a 3G network, or a 2G Global System for Mobile Communications (GSM) network.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
scanning, based on determining that the first IoT network is unavailable, for the availability of the second IoT network;
initiating, based on determining that the second IoT network is unavailable, a power save mode of operation for a power save duration,
wherein the network configuration profile includes one or more parameters relating to the power save duration of the IoT device; and
scanning, after the power save duration, for the availability of the first IoT network and the availability of the second IoT network.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
detecting initiation of a device management session,
wherein the network configuration profile includes one or more parameters relating to an exception to the mode priority for the device management session;
disabling, based on determining that the device management session was initiated, the mode priority; and
maintaining one of the network connection with the first IoT network or the network connection with the second IoT network for a duration of the device management session.

### Claim 8

An IoT device, comprising:
one or more memories; and
one or more processors, communicatively coupled to the one or more memories, to:
receive a network configuration profile,
wherein the network configuration profile includes one or more parameters relating to a mode priority and a scan interval of the IoT device, and
wherein the mode priority indicates a priority for a first IoT network over a second IoT network;
cause a first network connection to be established with the first IoT network;
detect a loss of the first network connection with the first IoT network;
scan, based on detecting the loss of the first network connection with the first IoT network, for an availability of the first IoT network;
scan, based on determining that the first IoT network is unavailable, for an availability of the second IoT network;
cause, based on determining that the second IoT network is available, a second network connection to be established with the second IoT network;
scan, after the scan interval and while the IoT device is connected to the second IoT network, for the availability of the first IoT network; and
cause, based on determining that the first IoT network is available, the first network connection to be established with the first IoT network.

### Claim 9 (depends on 8)

The IoT device of claim 8, wherein the network configuration profile includes one or more parameters relating to a power save duration and a scan duration of the IoT device,
wherein the power save duration corresponds to a duration of a power save mode of operation,
wherein the scan duration corresponds to a duration for scanning for the availability of the first IoT network and the availability of the second IoT network, and
wherein the power save mode of operation is initiated based on determining that the first IoT network is unavailable and the second IoT network is unavailable for the scan duration.

### Claim 10 (depends on 8)

The IoT device of claim 8, wherein the one or more processors, when receiving the network configuration profile, are to:
receive the network configuration profile from an IoT control device,
wherein one or more of the mode priority or the scan interval are configurable via a client device in communication with the IoT control device, and
wherein the first IoT network and the second IoT network correspond to a common network operator.

### Claim 11 (depends on 8)

The IoT device of claim 8, wherein the one or more processors, when scanning for the availability of the second IoT network, are to:
scan for the availability of the second IoT network; and
scan, based on determining that the second IoT network is unavailable, for the availability of the first IoT network and the availability of the second IoT network.

### Claim 12 (depends on 8)

The IoT device of claim 8, wherein the one or more processors are further to:
scan, based on determining that the first IoT network is unavailable and the second IoT network is unavailable, for an availability of a third IoT network,
wherein the mode priority indicates a priority for one of the first IoT network or the second IoT network over the third IoT network;
cause, based on determining that the third IoT network is available, a third network connection to be established with the third IoT network;
scan, after the scan interval and while the IoT device is connected to the third IoT network, for one or more of the availability of the first IoT network or the availability of the second IoT network; and
cause, based on determining that one or more of the first IoT network or the second IoT network is available, one of the first network connection or the second network connection to be established.

### Claim 13 (depends on 8)

The IoT device of claim 8, wherein the one or more processors are further to:
scan, based on determining that the first IoT network is unavailable, for the availability of the second IoT network; and
initiate, based on determining that the first IoT network is unavailable and the second IoT network is unavailable for a scan duration, a power save mode of operation for a power save duration,
wherein the network configuration profile includes one or more parameters relating to the power save duration of the IoT device, and
wherein the scan duration corresponds to a duration for scanning for the availability of the first IoT network and the availability of the second IoT network.

### Claim 14 (depends on 8)

The IoT device of claim 8, wherein the one or more processors are further to:
detect initiation of a device management session,
wherein the network configuration profile includes one or more parameters relating to an exception to the mode priority for the device management session;
disable, based on determining that the device management session was initiated, the mode priority; and
maintain one of the first network connection or the second network connection for a duration of the device management session.

### Claim 15

A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive a network configuration profile of an Internet of Things (IoT) device,
wherein the network configuration profile includes one or more parameters relating to a mode priority and a scan interval of the IoT device, and
wherein the mode priority indicates a priority for a first IoT network over a second IoT network and a third IoT network, and a priority for the second IoT network over the third IoT network;
scan for an availability of the first IoT network;
scan, based on determining that the first IoT network is unavailable, for an availability of the second IoT network;
scan, based on determining that the second IoT network is unavailable, for the availability of the first IoT network and the availability of the second IoT network;
scan, based on determining that the first IoT network is unavailable and the second IoT network is unavailable, for an availability of the third IoT network;
cause, based on determining that the third IoT network is available, a network connection to be established with the third IoT network;
scan, after the scan interval and while the network connection with the third IoT network exists, for the availability of the first IoT network; and
cause, based on determining that the first IoT network is available, a network connection to be established with the first IoT network.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the network configuration profile includes one or more parameters relating to a power save duration and a scan duration of the IoT device,
wherein the power save duration corresponds to a duration of a power save mode of operation,
wherein the scan duration corresponds to a duration for scanning for the availability of the first IoT network, the availability of the second IoT network, and the availability of the third IoT network, and
wherein the power save mode of operation is initiated based on determining that the first IoT network is unavailable, the second IoT network is unavailable, and the third IoT network is unavailable for the scan duration.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the mode priority indicates a priority for one or more of a Long-Term Evolution (LTE) category M1 network, a 5G category M1 network, an LTE category Narrow Band-Internet of Things (NB-IoT) network, a 5G category NB-IoT network, a 3G network, or a 2G Global System for Mobile Communications (GSM) network.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the one or more processors to receive the network configuration profile, cause the one or more processors to:
receive the network configuration profile from an IoT control device,
wherein one or more of the mode priority or the scan interval are configurable via a client device in communication with the IoT control device, and
wherein the first IoT network and the second IoT network correspond to a common network operator.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
initiate, based on determining that the first IoT network is unavailable, the second IoT network is unavailable, and the third IoT network is unavailable for a scan duration, a power save mode of operation for a power save duration,
wherein the network configuration profile includes one or more parameters relating to the power save duration of the IoT device;
wherein the scan duration corresponds to a duration for scanning for the availability of the first IoT network, the availability of the second IoT network, and the availability of the third IoT network, and
scan, after the power save duration, for the availability of the first IoT network, the availability of the second IoT network, and the availability of the third IoT network.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
detect initiation of a device management session,
wherein the network configuration profile includes one or more parameters relating to an exception to the mode priority for the device management session;
disable, based on determining that the device management session was initiated, the mode priority; and
maintain one of a network connection with the first IoT network, a network connection with the second IoT network, or the network connection with the third IoT network for a duration of the device management session.