# US 11,444,794 B2 · Internet of things device connectivity real time notification > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,444,794 B2 - Document ID: US11444794B2 - Status: Granted - Kind: B2 - Application number: 16/839,791 - Filed: 2020-04-03 - Published: 2021-10-07 - Granted: 2022-09-13 - Earliest claimed: 2020-04-03 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Rachel Ward; Ning Zhang; Carl Wang; Brian Matthew White - Web page: https://patentgrep.com/patent/US11444794B2 ## CPC - H04L 12/1818: {Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties} - H04L 65/1063: Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42) - H04L 65/1016: IP multimedia subsystem [IMS] - H04L 65/1069: Session establishment or de-establishment - H04L 65/1073: Registration or de-registration - H04L 65/1104: Session initiation protocol [SIP] - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - H04W 68/02: Arrangements for increasing efficiency of notification or paging channel - H04L 51/222: using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area - Y04S 40/18: Network protocols supporting networked applications, e.g. including control of end-device applications over a network - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - Y04S: SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS ## Abstract A device may include a memory storing instructions and processor configured to execute the instructions to maintain an Internet of Things (IoT) device database that stores, for an IoT device in the IoT device database, an application server device list that includes one or more application server devices that are to be notified when the IoT device is determined to be in an awake state. The processor may be further configured to receive a first indication from a first application server device that the IoT device is in an awake state; access the IoT device database to identify a second application server device associated with the IoT device; and send a second indication to the second application server device that the IoT device is in the awake state based on the received first indication from the first application server device. ## Claims ### Claim 1 A method comprising: maintaining, by a computer device, an Internet of Things (IoT) device database that stores, for an IoT device, an application server device list that identifies a plurality of application server devices that are to be notified when the IoT device changes from a sleep state to an awake state; receiving, by the computer device, a first indication from a first application server device that the IoT device has entered an awake state; sending, by the computer device and without receiving input from a user, an instruction to the first application server device to instruct the IoT device to remain in the awake state, in response to receiving the first indication from the first application server device that the IoT device is in the awake state; accessing, by the computer device, the IoT device database to identify a second application server device associated with the IoT device, wherein the second application server device is different from the first application server device; and sending, by the computer device, a second indication to the second application server device that the IoT device is in the awake state based on the received first indication from the first application server device. ### Claim 2 (depends on 1) The method of claim 1, further comprising: establishing a communication channel with the second application server device; receiving, from the second application server device, a registration request for the IoT device, wherein the registration request indicates that the second application server device is to be notified when the IoT device enters an awake state; and updating the application server device list for the IoT device in the IoT device database based on the received registration request. ### Claim 3 (depends on 2) The method of claim 2, further comprising: sending an instruction to the second application server device to send a message to the computer device when the second application server device receives a message from the IoT device indicating that the IoT device has entered the awake state; and monitoring the established communication channel for messages relating to the IoT device. ### Claim 4 (depends on 1) The method of claim 1, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake for a particular time period. ### Claim 5 (depends on 1) The method of claim 1, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake until a message is received from the second application server device. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving, from a third application server device, a registration request, wherein the registration request indicates that the third application server device is to receive updates relating to particular IoT devices; and updating the IoT device database based on the received registration request. ### Claim 7 (depends on 6) The method of claim 6, further comprising: sending an update to the third application server device, wherein the update includes information indicating that the IoT device is in the awake state, based on the received first indication from the first application server device. ### Claim 8 (depends on 1) The method of claim 1, further comprising: receiving a request from a third application server device inquiring as to whether the IoT device is in the awake state; and sending a message to the third application server device indicating whether the IoT device is in the awake state, in response to receiving the request from the third application server device. ### Claim 9 (depends on 1) The method of claim 1, wherein the second application server device includes a Firmware-Over-The-Air (FOTA) device. ### Claim 10 A device comprising: a memory storing instructions; and a processor configured to execute the instructions to: maintain an Internet of Things (IoT) device database that stores, for an IoT device in the IoT device database, an application server device list that identifies a plurality of application server devices that are to be notified when the IoT device is determined to be in an awake state; receive a first indication from a first application server device that the IoT device is in an awake state; send, without receiving input from a user, an instruction to the first application server device to instruct the IoT device to remain in the awake state, in response to receiving the first indication from the first application server device that the IoT device is in the awake state; access the IoT device database to identify a second application server device associated with the IoT device, wherein the second application server device is different from the first application server device; and send a second indication to the second application server device that the IoT device is in the awake state based on the received first indication from the first application server device. ### Claim 11 (depends on 10) The device of claim 10, wherein the processor is further configured to: establish a communication channel with the second application server device; receive, from the second application server device, a registration request for the IoT device, wherein the registration request indicates that the second application server device is to be notified when the IoT device enters an awake state; and update the application server device list for the IoT device in the IoT device database based on the received registration request. ### Claim 12 (depends on 11) The device of claim 11, wherein the processor is further configured to: send an instruction to the second application server device to send a message to the computer device when the second application server device receives a message from the IoT device indicating that the IoT device has entered the awake state; and monitor the established communication channel for messages relating to the IoT device. ### Claim 13 (depends on 10) The device of claim 10, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake for a particular time period. ### Claim 14 (depends on 10) The device of claim 10, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake until receiving a message from the second application server device. ### Claim 15 (depends on 10) The device of claim 10, wherein the processor is further configured to: receive, from a third application server device, a registration request, wherein the registration request indicates that the third application server device is to receive updates relating to particular IoT devices; update the IoT device database based on the received registration request; and send an update to the third application server device, wherein the update includes information indicating that the IoT device is in the awake state, based on the received first indication from the first application server device. ### Claim 16 (depends on 10) The device of claim 10, wherein the processor is further configured to: receive a request from a third application server device inquiring as to whether the IoT device is in the awake state; and send a message to the third application server device indicating whether the IoT device is in the awake state, in response to receiving the request from the third application server device. ### Claim 17 (depends on 10) The device of claim 10, wherein the second application server device includes a Firmware-Over-The-Air (FOTA) device. ### Claim 18 A non-transitory computer-readable memory device storing instructions executable by a processor, the non-transitory computer-readable memory device comprising: one or more instructions to maintain an Internet of Things (IoT) device database that stores, for an IoT device in the IoT device database, an application server device list that identifies a plurality of application server devices that are to be notified when the IoT device is determined to be in an awake state; one or more instructions to receive a first indication from a first application server device that the IoT device is in an awake state; one or more instructions to send, without receiving input from a user, an instruction to the first application server device to instruct the IoT device to remain in the awake state, in response to receiving the first indication from the first application server device that the IoT device is in the awake state; one or more instructions to access the IoT device database to identify a second application server device associated with the IoT device, wherein the second application server device is different from the first application server device; and one or more instructions to send a second indication to the second application server device that the IoT device is in the awake state based on the received first indication from the first application server device. ### Claim 19 (depends on 18) The non-transitory computer-readable memory device of claim 18, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake for a particular time period. ### Claim 20 (depends on 18) The non-transitory computer-readable memory device of claim 18, wherein the instruction to the first application server device includes an instruction to instruct the IoT device to remain awake until receiving a message from the second application server device.