System and method to publish information from servers to remote monitor devices

• US 9,413,622 B2
• Filed: 02/24/2015
• Issued: 08/09/2016
• Est. Priority Date: 01/31/2000
• Status: Expired due to Fees

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Clubb, Kenneth John, Sutton, Lyle
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US14/630,052
• Publication Number:
  US 20150312115A1
• Time in Patent Office: 532 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 1/1635 Cumulative acknowledgement, i.e. the acknowledgement message applying to all previous messages
• CPC Class Codes: H04L 2001/0092 Error control systems characterised by the topology of the transmission link
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/5651 : Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/164 : Adaptation or special uses of UDP protocol
• CPC Class Codes: H04L 69/18 : Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 80/00 : Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 80/045 : involving different protocol versions, e.g. MIPv4 and MIPv6

Abstract

To assist in monitoring the intelligent messaging network, a system and method for publishing logging and status information from the servers is provided. A list of available servers accessible for monitoring by persons, devices, and applications via a remote monitor device can be provided. The remote monitor device may forward selected servers from the list of available servers in which they are interested. Also, particular information about the selected servers can be requested. Access to certain servers and information may be restricted to those with authorization. Authorization can be verified by the use of digital certificates. The requested information can then be gathered and provided to authorized persons or devices. Typically, the information includes logging and status information from the servers. The information can be provided as an XML page and viewed using, for example, a standard web browser. Further, if the information is provided to the remote monitor device as an XML page, a standard XML parser may be used to extract particular information from the XML page.

Claims

1. A method of receiving server information, comprising:

authorizing, via a digital certificate, access of a client device to a web page content server;

sending, from a web browser associated with a client device, a request for web page content to the web page content server, the web page content including logging information associated with at least one of a plurality of monitored servers, the logging information comprising at least one of start/stop time information and error information; and

receiving, via a physical receiver associated with the client device, the web page content;

wherein the web page content is parsable to extract particular information about a particular server from the at least one of the plurality of monitored servers.

2. The method of receiving server information according to claim 1, wherein:

the web page content is received, via a physical receiver associated with the client device, according to an access level associated with the digital certificate.

3. The method of receiving server information according to claim 1, wherein:

the request for web page content is transmitted via Transport Control Protocol/Internet Protocol (TCP/IP).

4. The method of receiving server information according to claim 1, further comprising:

receiving, via the physical receiver, the web page content in a compressed form.

5. The method of receiving server information according to claim 1, further comprising:

intercepting, via a proxy Internet Protocol (IP)/port, the request for web page content.

6. The method of receiving server information according to claim 1, further comprising:

unpacking, via a client device side proxy, the web page content into a HyperText Transfer Protocol (HTTP) response; and

sending the HTTP response to the web browser.

7. The method of receiving server information according to claim 6, wherein:

the client device side proxy sits atop a mobile library.

8. The method of receiving server information according to claim 1, further comprising:

accessing a mobile library optimized for an underlying wireless protocol used by the client device.

9. The method of receiving server information according to claim 1, further comprising:

compressing a raw payload of the request for the web page content prior to transmission of the request.

10. A client device to receive server information, comprising:

a web browser that receives authorization, via a digital certificate, to permit access of the client device to a web page content server, and that sends a request for web page content to the web page content server, the web page content including logging information associated with at least one of a plurality of monitored servers, the logging information comprising at least one of start/stop time information and error information; and

a physical receiver associated with the web browser to receive the web page content;

wherein the web page content is parsable to extract particular information about a particular server from the at least one of the plurality of monitored servers.

11. The client device to receive server information according to claim 10, wherein:

the web page content is received, via a physical receiver associated with the client device, according to an access level associated with the digital certificate.

12. The client device to receive server information according to claim 10, wherein:

the request is sent via Transport Control Protocol/Internet Protocol (TCP/IP).

13. The client device to receive server information according to claim 10, wherein:

the physical receiver receives the web page content in a compressed form.

14. The client device to receive server information according to claim 10, further comprising:

a client device side proxy to intercept the request for the web page content via a proxy Internet Protocol (IP)/port.

15. The client device to receive server information according to claim 14, wherein:

the client device side proxy unpacks retrieved information associated with the web page content into an HyperText Transfer Protocol (HTTP) response, and sends the HTTP response to the web browser.

16. The client device to receive server information according to claim 14, wherein:

the client device side proxy sits atop a mobile library.

17. The client device to receive server information according to claim 14, wherein:

the client device side proxy compresses a raw payload of the request for the web page content prior to transmitting the request for web page content.

18. The client device to receive server information according to claim 10, further comprising:

a mobile library optimized for an underlying wireless protocol used by the web browser.