System and method for providing network support services and premises gateway support infrastructure

• US 10,630,501 B2
• Filed: 03/29/2019
• Issued: 04/21/2020
• Est. Priority Date: 12/29/2006
• Status: Active Grant

• Current Assignee: Prodea Automation LLC (f/k/a Kip Prod P1) (FIG LLC (d/b/a Fortress Investment Group LLC))
• Original Assignee: Prodea Automation LLC (f/k/a Kip Prod P1) (FIG LLC (d/b/a Fortress Investment Group LLC))
• Inventors: Ansari, Amir, Cowgill, George A., Nicholls, Leon A., Ramayya, Jude P., Masina, Ramprakash, McQuarters, Alvin R., Raissyan, Atousa
• Primary Examiner(s): Nguyen, Minh Chau
• Application Number:
  US16/370,126
• Publication Number:
  US 20190245714A1
• Time in Patent Office: 389 Days
• Field of Search: 709225
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: G06F 16/64 Browsing; Visualisation therefor generation of a list or set of audio data G06F16/638
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G08B 13/19656 Network used to communicate with a camera, e.g. WAN, LAN, Internet
• CPC Class Codes: G10L 15/22 Procedures used during a speech recognition process, e.g. man-machine dialogue
• CPC Class Codes: G10L 2015/223 Execution procedure of a spoken command
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2807 Exchanging configuration information on appliance services in a home automation network arrangements for maintenance or administration involving network analysis for automatically determining the actual topology of a network H04L41/12; hardware or software tools for network management using graphical user interfaces H04L41/22; address allocation H04L61/50
• CPC Class Codes: H04L 12/2812 describing content present in a home automation network, e.g. audio video content retrieval from the Internet G06F16/95
• CPC Class Codes: H04L 12/2814 Exchanging control software or macros for controlling appliance services in a home automation network arrangements for maintenance or administration involving configuration of the network and network elements H04L41/08
• CPC Class Codes: H04L 12/2818 from a device located outside both the home and the home network access arrangements H04L12/2856; for remote control or remote monitoring of applications H04L67/025; arrangements for transmitting signals characterised by the use of a wireless eletrical link G08C17/00; telephonic communication systems adapted for combination with remote control systems H04M11/007
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2012/2849 Audio/video appliances
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 47/80 Actions related to the user profile or the type of traffic
• CPC Class Codes: H04L 47/83 : based on usage prediction
• CPC Class Codes: H04L 49/25 : Routing or path finding in a switch fabric
• CPC Class Codes: H04L 51/04 : Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 61/4552 : Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 63/02 : for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/06 : for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/102 : Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/1101 : Session protocols
• CPC Class Codes: H04L 65/1108 : Web based protocols, e.g. webRTC
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/104 : Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/125 : involving control of end-device applications over a network
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04L 69/325 : in the network layer [OSI layer 3], e.g. X.25 H04L69/16 takes precedence
• CPC Class Codes: H04N 21/00 : Selective content distribution, e.g. interactive television or video on demand [VOD] real-time bi-directional transmission of motion video data H04N7/14 ; broadcast or conference over packet switching networks H04L12/18
• CPC Class Codes: H04N 21/40 : Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
• CPC Class Codes: H04N 7/181 : for receiving images from a plurality of remote sources
• CPC Class Codes: H04W 12/00 : Security arrangements; Authentication; Protecting privacy or anonymity
• CPC Class Codes: H04W 12/033 : of the user plane, e.g. user's traffic
• CPC Class Codes: H04W 12/0431 : Key distribution or pre-distribution; Key agreement
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/065 : Continuous authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 12/35 : Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: Y10S 370/911 : Bridge, e.g. brouter, bus extender

Abstract

A service management system communicates via wide area network with gateway devices located at respective user premises. The service management system remotely manages delivery of application services, which can be voice controlled, by a gateway, e.g. by selectively activating/deactivating service logic modules in the gateway. The service management system also may selectively provide secure communications and exchange of information among gateway devices and among associated endpoint devices. An exemplary service management system includes a router connected to the network and one or more computer platforms, for implementing management functions. Examples of the functions include a connection manager for controlling system communications with the gateway devices, an authentication manager for authenticating each gateway device and controlling the connection manager and a subscription manager for managing applications services and/or features offered by the gateway devices. A service manager, controlled by the subscription manager, distributes service specific configuration data to authenticated gateway devices.

Claims

1. A management device for operation at a user premises with at least a first endpoint device and a second endpoint device, the management device comprising:

a network interface that communicates with a remote manager;

at least one interface configured to wirelessly communicate, via a local mesh wireless network, with the first endpoint device and/or the second endpoint device;

at least one processor; and

memory coupled to the at least one processor and having programming that causes the management device to perform operations including;

receiving data from the first endpoint device,

storing the received data to enable reporting of the received data for viewing via a user device,

managing one or more home automation functions of at least one of the first or second endpoint devices based on the received data, and

managing one or more software updates by receiving software via the network interface, storing the received software, and sending the received software to at least one of the first or second endpoint devices that implements the software.

2. The management device of claim 1, wherein the operations further include providing access to the stored received data to the remote manager.

3. The management device of claim 1, wherein the operations further include causing the received data to be sent for delivery to the remote manager to enable viewing of at least a portion of the received endpoint data on the second endpoint device connected to the local wireless network after endpoint authentication of the second endpoint device.

4. The management device of claim 1, wherein the operations further include causing the received endpoint data to be sent for delivery to the remote manager to enable viewing of at least a portion of the received endpoint data via the user device.

5. The management device of claim 1, wherein the operations include managing one or more services from a third-party service provider to control operation of the first endpoint device and/or second endpoint device.

6. The management device of claim 1, wherein the first endpoint device includes at least one of a television, a lamp, and/or a sensor.

7. The management device of claim 1, wherein the network interface communicates with a router device.

8. The management device of claim 1, wherein the operations further include enabling the management device to be remotely managed by the remote manager.

9. The management device of claim 1, wherein the operations include storing billing data, alarm data, and/or statistical information.

10. The management device of claim 1, wherein the remote manager provides viewing of the received data locally stored at the user premises.

11. The management device of claim 1, wherein the remote manager provides one or more of:

subscription controls;

authorization to use services;

alarm management;

remote diagnostic support;

billing collection and management;

software updates;

location services;

voice calling services;

media streaming services;

data backup services;

file sharing services, or any combination thereof.

12. The management device of claim 1, wherein the storing the received data comprises storing the received data in one or more of:

a hard drive, flash memory, RAM or another operational memory, or a message queue.

13. The management device of claim 1, wherein the storing the received software comprises storing the received data in one or more of:

a hard drive, flash memory, RAM or another operational memory, or a message queue.

14. The management device of claim 1, wherein the managing the one or more home automation functions is in response to voice controls from a user.

15. The management device of claim 1,

wherein the managing the one or more home automation functions is in response to voice controls from a user;

and

wherein the voice controls are enacted according to functionality provided by the one or more software updates.

16. The management device of claim 1, wherein the managing the one or more home automation functions is in response to voice controls from a user provided via an always on application service.

17. The management device of claim 1, wherein the managing the one or more home automation functions of at least one of the first or second endpoint devices includes coordinating information exchange among the first and second endpoint devices.

18. The management device of claim 1, wherein the managing the one or more home automation functions of at least one of the first or second endpoint devices includes coordinating information exchange, among the first and second endpoint devices, without use of wide area network.

19. The management device of claim 1, wherein the managing the one or more home automation functions is based on information received from a remote system to authorize or manage execution of a service on the management device.

20. The management device of claim 1, wherein the managing the one or more home automation functions includes activating or deactivating modules on the management device based on information received from a remote system to authorize or manage execution of a service on the management device.

21. The management device of claim 1, wherein the managing the one or more home automation functions includes allocating device resources including one or more of processor cycles, application memory, storage memory, bandwidth, or any combination thereof.

22. The management device of claim 1, wherein the managing the one or more home automation functions includes the management device providing a remote system access at least the first endpoint device.

23. The management device of claim 1,

wherein the managing the one or more software updates includes receiving the software based on a registry, at a remote device, that records endpoint devices and/or services registered in relation to the management device;

and

wherein the software is selected for delivery to the management device based on the registry.

24. The management device of claim 1, wherein the managing the one or more software updates includes receiving the software based on a registry that records endpoint devices and/or services registered in relation to the management device.

25. The management device of claim 1, wherein the managing the one or more software updates includes receiving the software based on a registry that records the firmware version of endpoint devices registered in relation to the management device.

26. The management device of claim 1, wherein the first endpoint device includes at least one of a monitoring sensor, audio equipment, or video survilleince equipment.

27. A mesh network management device for operation at a user premises, comprising:

at least one processor; and

memory coupled to the at least one processor and containing programming to perform operations including;

communicating, via at least one local wireless network, with a first endpoint device and a second endpoint device to provide information related to at least one of availability, integrity, quality, or performance of the first endpoint device and/or the second endpoint device, wherein one or both of the first and second endpoint devices is configured to be controlled by a user device in communication with the mesh network management device,

receiving software for the first endpoint device,

sending, via the at least one local wireless network, at least a portion of the received software to the first endpoint device,

receiving data from the first endpoint device that is implementing the received software,

storing the received data,

causing the data to be sent from the mesh network management device at the user premises to a remote manager, and

enabling viewing of operational information related to the first endpoint device via the user device, after authentication of the user device such that the user device is capable of secured management of operation of the first endpoint device or another endpoint device connected to the local wireless network.

28. The mesh network management device of claim 27, wherein the user device is the second endpoint device.

29. The mesh network management device of claim 27, wherein the user device and the second endpoint device are different devices.

30. The mesh network management device of claim 27, wherein the operations further include communicating, via a wide area network, with the remote manager, which is located external to the user premises.

31. The mesh network management device of claim 27, wherein the operations further include generating operational information based on operation of the first endpoint device and sending the operational information to the remote manager.

32. The mesh network management device of claim 27, wherein the communicating with the first endpoint device is further via at least one of a wired Ethernet connection, a Z wave connection, or a USB connection.

33. The mesh network management device of claim 27, wherein the operations further include generating one or more reports based on event data from the first endpoint device and/or statistical information for the endpoint device.

34. The mesh network management device of claim 27, wherein the mesh network management device is operable to provide a parental control including at least URL filtering.

35. The mesh network management device of claim 27, wherein the software includes a firmware update.

36. The mesh network management device of claim 27, wherein the user device is in communication with the mesh network management device via a local network or via a cloud service.

37. The mesh network management device of claim 27, wherein the received software is a software update and the first endpoint device is implementing the software update by having installed the software update.

38. The mesh network management device of claim 27, wherein storing the received data comprises storing the received data in flash or RAM memory.

39. The mesh network management device of claim 27, wherein the secured management of operation of the first endpoint device or another endpoint device is accomplished via one or more of:

encrypted communication between the mesh network management device and the first endpoint device and/or other endpoint device;

restricted access to settings or functions of the first endpoint device and/or other endpoint device;

requiring authentication prior to allowing access to operations and/or data from the first endpoint device and/or other endpoint device;

use of a communication protocol that provides security features;

or

any combination thereof.

40. The mesh network management device of claim 27, wherein the user device is a television and the operations further include providing a user interface on the television with menus for controlling the aspects of the mesh network management device.

41. The mesh network management device of claim 27, wherein the operations further include:

retrieving and installing, in the mesh network management device, one or more software modules that enable communication with and/or control over the first endpoint device and the second endpoint device.

42. The mesh network management device of claim 27, wherein the operations further include:

automatically identifying the first endpoint device; and

in response to the automatic identification of the first endpoint device, retrieving and installing, in the mesh network management device, one or more software modules that enable communication with and/or control over the first endpoint device and the second endpoint device.

43. The mesh network management device of claim 27, wherein the operational information is provided on a user interface of the user device which includes options to select services, associated with particular service providers, to enable or disable on the mesh network management device.

44. The mesh network management device of claim 27, wherein the received data includes configuration data specifying, for the first endpoint device, one or more of:

supported formats, supported bit rates, a type of controller, or any combination thereof.

45. The mesh network management device of claim 27,

wherein the receiving the software includes automatically receiving a software update for the first endpoint device;

and

wherein the sending the at least the portion of the received software update to the first endpoint device causes the software update to be automatically installed in the first endpoint device.

46. The mesh network management device of claim 27,

wherein the receiving the software includes receiving a software update for the first endpoint device in response to a user authorization to update the first endpoint device;

and

wherein the sending the at least the portion of the received software update to the first endpoint device causes the software update to be automatically installed in the first endpoint device.

47. The mesh network management device of claim 27,

wherein the receiving the software includes receiving a software update for the first endpoint device;

and

wherein the sending the at least the portion of the received software update to the first endpoint device causes the software update to be automatically installed, in response to a determination that installing the software update will not interrupt other gateway functions or services, in the first endpoint device.

48. The mesh network management device of claim 27, wherein the operations further include the mesh network management device performing one or more tests on the software implemented on the first endpoint device.

49. The mesh network management device of claim 27, wherein the operations further include

the mesh network management device performing one or more tests on the software implemented on the first endpoint device;

and

in response to at least some of the one or more tests failing, rolling back the first endpoint device to not be implementing the software.

50. The mesh network management device of claim 27, wherein the software received for the first endpoint device is received based on the mesh network management device being associated with a particular geographical region.

51. The mesh network management device of claim 27, wherein the information related to at least one of availability, integrity, quality, or performance of the first endpoint device and/or the second endpoint device comprises an identification of the first endpoint device which is used by the mesh network management device to automatically discover and configure the first endpoint device for control by the mesh network management device.

52. The mesh network management device of claim 27,

wherein the information related to at least one of availability, integrity, quality, or performance of the first endpoint device and/or the second endpoint device comprises an identification of the first endpoint device which is used by the mesh network management device to discover and configure the first endpoint device for control by the mesh network management device;

and

wherein the configuring the first endpoint device for control by the mesh network management device is based on user input for configuring the first endpoint device such that the configuration of the first endpoint device causes the first endpoint device to securely communicates via the local network.

53. The mesh network management device of claim 27, wherein the mesh network management device stores authentication information that is dependent on A) a hardware configuration of the mesh network management device and/or B) identifications of one or more devices connected to the mesh network management device.

54. The mesh network management device of claim 27, wherein the operations further comprise storing multiple service keys, wherein each service key corresponds to a service authenticated on the mesh network management device and wherein one or more of the multiple services keys can be replaced or renewed by the corresponding service.

55. The mesh network management device of claim 27, wherein the sending at least a portion of the received software to the first endpoint device is performed according to a previously established software update schedule.

56. The mesh network management device of claim 27, wherein the operations further comprise automatically receiving and installing a firmware update for the mesh network management device.

57. A management device for operation at a user premises, the management device comprising:

an endpoint interface configured for communication via at least one local wireless network at the user premises;

at least one processor in communication with the endpoint interface and/or the network interface; and

a storage device communicatively coupled to the at least one processor and containing instructions that, when executed, cause the management device to perform operations including—

communicating, via a network interface, with a remote server,

receiving, via the network interface, a software update from the remote server,

sending, via the at least one local wireless network, the software update to at least one of first or second endpoint devices,

receiving, via the at least one local wireless network, endpoint data from the first endpoint device,

coordinating, via the at least one local wireless network, operation of endpoint devices at the user premises based on the received endpoint data associated with the first endpoint device and/or the second endpoint device, and

causing received endpoint data information to be sent for delivery to the remote server, via the network interface, for enabling viewing of the endpoint data information on a user device that provides secured management of operation of the first endpoint device and/or second endpoint device.

58. The management device of claim 57, wherein the storage device stores operational data related to availability, status, integrity, quality, and/or performance of the first endpoint device and/or other endpoint devices.

59. The management device of claim 57, wherein the communicating, via the network interface, with the remote server is performed using the endpoint interface.

60. The management device of claim 57, wherein the communicating, via the network interface, with the remote server is performed without using the endpoint interface.

61. The management device of claim 57, wherein the coordinating operation of endpoint devices at the user premises based on the received endpoint data comprises sharing data between devices other than the management device and setting up and managing communication sessions between the devices other than the management device.

62. The management device of claim 57, wherein the secured management of operation of the first endpoint device and/or second endpoint device is accomplished via encrypted communication between the management device and the first endpoint device and/or the second endpoint device.

63. The management device of claim 57, wherein the endpoint data information comprises one or more of:

information specifying an internal state of an endpoint device, information gathered by an endpoint device in relation to a status of the user premises, information gathered by an endpoint device in relation to another device at the user premises, information gathered by an endpoint device in relation to a device remote from the user premises, or any combination thereof.

64. The management device of claim 57, wherein the secured management of operation of the first endpoint device and/or second endpoint device is accomplished via restricting access to settings or functions of the first endpoint device and/or second endpoint device.

65. The management device of claim 57, wherein the secured management of operation of the first endpoint device and/or second endpoint device is accomplished via requiring authentication prior to allowing access to operations and/or data from the first endpoint device and/or second endpoint device.

66. The management device of claim 57, wherein the secured management of operation of the first endpoint device and/or second endpoint device is accomplished via use of a communication protocol that provides security features.

67. A method, performed at a user premises in relation to at least a first endpoint device and a second endpoint device, the method comprising:

using a network interface to communicate with a remote manager;

wirelessly communicating, via a local wireless network, with the first endpoint device and/or the second endpoint device;

receiving data from the first endpoint device;

storing the received data to enable reporting of the received data for viewing via a user device;

managing one or more home automation functions of at least one of the first or second endpoint devices based on the received data; and

managing one or more software updates by receiving software via the network interface and sending the received software to at least one of the first or second endpoint devices that installs the software.

68. The method of claim 67,

wherein the managing the one or more home automation functions is in response to voice controls from a user;

and

wherein the voice controls are enacted according to functionality provided by the one or more software updates.

69. The method of claim 67, wherein the managing the one or more home automation functions is in response to voice controls from a user provided via an always on application service.

70. The method of claim 67, wherein the managing the one or more home automation functions of at least one of the first or second endpoint devices includes coordinating information exchange, among the first and second endpoint devices, without use of wide area network.

71. The method of claim 67,

wherein the managing the one or more software updates includes receiving the software based on a registry, at a remote device, that records endpoint devices and/or services registered in relation to an identifier for a device that performs the method;

and

wherein the software is selected for delivery to the device that performs the method based on the registry.

72. A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations at a user premises, the operations comprising:

communicating, via at least one local wireless network, with a first endpoint device and a second endpoint device to provide information related to at least one of availability, integrity, quality, or performance of the first endpoint device and/or the second endpoint device, one or both of the first and second endpoint devices being configured to be controlled by a user device in communication with the computing system;

receiving software for the first endpoint device;

sending, via the at least one local wireless network, at least a portion of the received software to the first endpoint device;

receiving, from the first endpoint device that has implemented the received software, data;

causing the data to be sent from the user premises to a remote manager; and

enabling viewing of operational information related to the first endpoint device via the user device, after authentication of the user device, such that the user device is capable of secured management of operation of the first endpoint device or another endpoint device connected to the local wireless network.

73. The computer-readable storage medium of claim 72, wherein the operations further include:

automatically identifying the first endpoint device; and

in response to the automatic identification of the first endpoint device, retrieving and installing, in the computing system, one or more software modules that enable communication with and/or control over the first endpoint device and/or the second endpoint device.

74. The computer-readable storage medium of claim 72, wherein the operational information is provided on a user interface of the user device which includes options to select services, associated with particular service providers, to enable or disable on the computing system.

75. The computer-readable storage medium of claim 72, wherein the software received for the first endpoint device is received based on the computing system being associated with a particular geographical region.

76. The computer-readable storage medium claim 72, wherein the secured management of operation of the first endpoint device or another endpoint device is accomplished via one or more of:

encrypted communication between the computing system and the first endpoint device and/or other endpoint device;

restricted access to settings or functions of the first endpoint device and/or other endpoint device;

requiring authentication prior to allowing access to operations and/or data from the first endpoint device and/or other endpoint device;

use of a communication protocol that provides security features;

or

any combination thereof.

77. The computer-readable storage medium of claim 72, wherein multiple interfaces are installed on the computing system that correspond to different ones of multiple endpoint devices with which the computing system is in communication and wherein the operations further comprise moving information between the multiple endpoint devices using the multiple interfaces.