Management and diagnosis of telephonic devices

• US 9,319,511 B2
• Filed: 04/08/2015
• Issued: 04/19/2016
• Est. Priority Date: 06/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Appiah, Madan Mohan R., Chandrasekaran, Subramanian
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US14/681,303
• Publication Number:
  US 20150215448A1
• Time in Patent Office: 377 Days
• Field of Search: 709224-229, 709/247
• US Class Current: 1/1
• CPC Class Codes: H04M 2203/052 software update
• CPC Class Codes: H04M 3/08 Indicating faults in circuits or apparatus
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing
• CPC Class Codes: H04M 3/28 Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor
• CPC Class Codes: H04M 3/42178 by downloading data to substation equipment

Abstract

Systems and methods of managing and diagnosing enterprise telephonic devices are disclosed. A provisioning request can be received from an enterprise telephonic device. The provisioning request can include a domain name system lookup request. An enterprise network address of a device management server can be provided to the enterprise telephonic device. A voice data link can be established with the enterprise telephonic device so as to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices. The device management server can periodically receive heartbeat data from the enterprise telephonic device. The heartbeat can be indicative of a status of at least one functionality of the enterprise telephonic device. The enterprise telephonic device can provide diagnostic logs when requested by the device management server. In addition, the enterprise telephonic device can be configured to periodically request software updates.

Claims

1. A method, comprising:

sending a self-provisioning request from an enterprise telephonic device to a device management server in an enterprise network, the self-provisioning request including a domain name system lookup request and a request to register as an element of the enterprise network;

receiving from the enterprise telephonic device an enterprise network address that permits the enterprise telephonic device to communicate with the device management server;

establishing a voice data link with the enterprise telephonic device so as to permit the enterprise telephonic device to communicate over a data network with at least one endpoint telephonic device; and

transmitting heartbeat data from the enterprise telephonic device to the device management server, the heartbeat data indicative of a status of the enterprise telephonic device, including a voice communication function.

2. The method of claim 1, further comprising sending a diagnostic log if requested by the device management server.

3. The method of claim 1, further comprising sending a diagnostic log from the enterprise telephonic device.

4. The method of claim 1, wherein the domain name system lookup request includes a service record that requests authentication by the device management server.

5. The method of claim 1, wherein establishing the voice data link with the enterprise telephonic device includes receiving a dynamically provisioned IP address corresponding to the enterprise telephonic device.

6. The method of claim 1, further comprising querying an update software database to determine if there are any software updates available.

7. The method of claim 1, further comprising sending diagnostic data in the diagnostic log from the enterprise telephonic device, the device management server to filter the diagnostic data and provide the filtered diagnostic data to an update service for determination as to whether software updates are necessary or available.

8. The method of claim 1, further comprising:

sending, to the device maintenance server, event data associated with an occurrence of an event, the device maintenance server to analyze the heartbeat data and the event data to determine whether there is a voice communication malfunction in the enterprise telephonic device; and

if it is determined that there is a voice communication malfunction in the enterprise telephonic device, sending from the enterprise telephonic device a diagnostic log indicative of the occurrence of the event.

9. The method of claim 8, further comprising filtering diagnostic data in the diagnostic log from the enterprise telephonic device, the filtered diagnostic data to be provided to an update service for determination as to whether software updates are necessary or available.

10. The method of claim 8, further comprising receiving software updates to the enterprise telephonic device if there is a voice communication malfunction in the enterprise telephonic device.

11. The method of claim 8, further comprising checking an update software database to determine whether there are software updates available.

12. An apparatus comprising:

a processing unit;

a communication device;

a memory containing instructions, that when executed by the processing unit, cause the apparatus to;

send a self-provisioning request, to an device management server in an enterprise network via the communication device, from an enterprise telephonic device, wherein the enterprise network does not have previous data associated with the enterprise telephonic device, the self-provisioning request including a domain name system lookup request and a request to register as an element of the enterprise network;

receive an enterprise network address to permit the enterprise telephonic device to communicate with the device management server;

establish a voice data link to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices; and

transmit to the device management server heartbeat data from the enterprise telephonic device, the heartbeat data being indicative of a status of at least one operation of the enterprise telephonic device, including a voice communication function.

13. The apparatus of claim 12, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

send a request to the device management server to determine whether a software update is available, the device management server to request, from an update service that is separate from the device management server, an indication of whether an update service software is available for downloading; and

receive, at the enterprise telephonic device, an indication that a software update is available when the enterprise telephonic device has not previously received the update service software and when the update service provides the indication to the device management service that update service software is available.

14. The apparatus of claim 12, wherein the device management service to request the update service software from the update service when the update service provides the indication to the device management service that update service software is available.

15. The apparatus of claim 12, wherein the device management service to provide the enterprise telephonic device with the update service software from the update service when the update service provides the indication to the device management service that update service software is available.

16. The apparatus of claim 12, wherein the update service software is stored in an update software database.

17. The apparatus of claim 12, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

send, to the device maintenance server, event data corresponding to the enterprise telephonic device and associated with an occurrence of an event, the event data and the heartbeat data being analyzed, at the device maintenance server, to determine whether there is a voice communication malfunction in the enterprise telephonic device; and

send, to the device maintenance server, a diagnostic log indicative of the occurrence of the event when it is determined that there is a voice communication malfunction in the enterprise telephonic device.

18. The apparatus of claim 17, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

store, at a share point server, at least one of the diagnostic log and the update service software.

19. The apparatus of claim 17, wherein at least one of the update service software and the diagnostic log being communicated from the share point server to the device maintenance server.

20. An enterprise network, comprising:

a plurality of enterprise telephonic devices of each is operative to submit a self-provisioning request to a device management server to automatically register as an element of the enterprise network, wherein the enterprise network does not have previous data associated with the enterprise telephonic device and the self-provisioning request includes a domain name system lookup request; and

an enterprise telephone device of the plurality of enterprise telephonic devices operative to receive an enterprise network address permitting communication with the device management server, establish a voice data link to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices, and transmit heartbeat data from the enterprise telephonic device to the device management server, the heartbeat data being indicative of a status of the enterprise telephonic device, including a voice communication function.