Internet of things event management systems and methods

Patent metadata

Field	Value
Publication number	US-11356350-B2
Application number	US-202117183887-A
Country	US
Kind code	B2
Filing date	Feb 24, 2021
Priority date	Aug 29, 2013
Publication date	Jun 7, 2022
Grant date	Jun 7, 2022

Abstract

Internet of Things (IoT) event objects can be tailored to specific device types and capabilities. An IoT event object can use a flexible definition of an event that can be reconfigured. An IoT event object allows for the ability to set different triggering conditions and priorities. Individual event definitions can be extended to create more complex events. A Notification Handler supports sending a request or command in response to an event that requires action.

First claim

What is claimed is:

1. A method implemented by a service supporting service capabilities through a set of application programming interfaces (APIs) in a network, the method comprising:
defining an event object, wherein the event object comprises one or more event expressions, wherein each of the one or more event expressions comprises one or more conditions and information indicative of one or more actions to perform when the one or more conditions are met,
wherein each of the one or more conditions uses a value from at least one resource in the network and comprises one or more of: an operand, an operator, or a threshold value,
wherein the event object is stored at the service and comprises a state value that indicates how the event is to be evaluated, and
wherein the service uses the defined event object to monitor an event; and

based on determining that the event has met the one or more conditions, performing an action of the one or more actions defined in the event object.

2. The method of claim 1 , wherein the event object comprises a trigger condition that indicates how to obtain resource data for the one or more event expressions.

3. The method of claim 1 , wherein the event object comprises a trigger priority that indicates when to obtain resource data for other resources for the one or more event expressions after the value from the at least one resource is obtained and at least partially meets the one or more conditions of the one or more event expressions.

4. The method of claim 1 , wherein the event object comprises object information that indicates event functionalities supported by the service.

5. The method of claim 1 , wherein the service is implemented in at least one of: a server, gateway, or other node of the network.

6. The method of claim 1 , wherein the at least one resource is located outside the service.

7. The method of claim 1 , wherein the one or more event expressions are dynamically created by an application outside the service.

8. A device comprising a processor and a memory storing computer executable instructions which when executed by the processor cause the device to perform functions of an instance of a service of a communication network, the service supports service capabilities through a set of application programming interfaces (APIs), and to:
define an event object, wherein the event object comprises one or more event expressions, wherein each of the one or more event expressions comprises one or more conditions and information indicative of one or more actions to perform when the one or more conditions are met,
wherein each of the one or more conditions uses a value from at least one resource in the network and comprises one or more of: an operand, an operator, or a threshold value,
wherein the event object is stored at the service and comprises a state value that indicates how the event is to be evaluated, and
wherein the service uses the defined event object to monitor an event; and

based on determining that the event has met the one or more conditions, perform an action of the one or more actions defined in the event object.

9. The device of claim 8 , wherein the event object comprises a trigger condition that indicates how to obtain resource data for the one or more event expressions.

10. The device of claim 8 , wherein the event object comprises a trigger priority that indicates when to obtain resource data for other resources for the one or more event expressions after the value from the at least one resource is obtained and at least partially meets the one or more conditions of the one or more event expressions.

11. The device of claim 8 , wherein the event object comprises object information that indicates event functionalities supported by the service.

12. The device of claim 8 , wherein the service is implemented in at least one of: a server, gateway, or other node of the network.

13. The device of claim 8 , wherein the at least one resource is located outside the service.

14. The device of claim 8 , wherein the one or more event expressions are dynamically created by an application outside the service.

15. The method of claim 1 , wherein the service is provided in a service layer located on top of network protocol stacks for IoT services.

16. The method of claim 15 , wherein the service layer is defined according to ETSI/oneM2M standards.

17. The method of claim 1 , wherein the at least one resource is a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods.

18. The device of claim 8 , wherein the service is provided in a service layer located on top of network protocol stacks for IoT services.

19. The device of claim 18 , wherein the service layer is defined according to ETSI/oneM2M standards.

20. The device of claim 8 , wherein the at least one resource is a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods.

Assignees

• Convida Wireless LLC

Inventors

• Ly Quang
• Dong Lijun
• Seed Dale N
• Rahman Shamim Akbar

Classifications

• H04L67/125 Primary

  involving control of end-device applications over a network · CPC title

• H04L43/0876 Primary

  Network utilisation, e.g. volume of load or congestion level · CPC title

• H04W4/38

  for collecting sensor information · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• H04L67/55

  Push-based network services · CPC title