Communication device

• US 9,537,927 B2
• Filed: 11/01/2013
• Issued: 01/03/2017
• Est. Priority Date: 11/02/2012
• Status: Active Grant

• Current Assignee: Brother Kogyo Kabushiki Kaisha
• Original Assignee: Brother Kogyo Kabushiki Kaisha
• Inventors: Matsuda, Munehisa
• Primary Examiner(s): Meky, Moustafa M
• Assistant Examiner(s): Hurst, Andrea
• Application Number:
  US14/069,644
• Publication Number:
  US 20140129674A1
• Time in Patent Office: 1,159 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 3/1211 Improving printing performance
• CPC Class Codes: G06F 3/1236 Connection management
• CPC Class Codes: G06F 3/1284 Local printer device
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: 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
• CPC Class Codes: H04L 67/143 Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

A communication device may communicate with a data processing device via a communication line. The data processing device may include client applications configured to execute communications by using multisession communication. The communication device may establish a session with a specific client application among the client applications via the communication line, and receive an HTTP request from the specific client application. The communication device may transmit an HTTP response to the specific client application via the established session. The transmission may include transmitting first disconnection instruction information to the data processing device in a case where the communication line used to receive the HTTP request is a line that is not capable of the multisession communication. The first disconnection instruction information may be information for causing the data processing device to disconnect the established session after transmitting the HTTP response.

Claims

1. A communication device comprising:

a network interface for communicating with a data processing device via a communication line, the data processing device including one or more client applications that execute communications by using multisession communication;

a processor coupled to the network interface; and

a memory storing computer-readable instructions that, when executed by the processor, cause the communication device to perform;

establishing a session with a specific client application among the one or more client applications via the communication line;

receiving an HTTP request from the specific client application via the established session; and

transmitting an HTTP response to the specific client application via the established session,

the HTTP response being a response to the HTTP request received in the receiving,

the HTTP response including an HTTP header containing first information,

the first information being information for causing the data processing device to retain the established session even after transmitting of the HTTP response ends and to use the retained session in a second request and subsequent requests, and

the first information being information corresponding to Keep-Alive in accordance with an HTTP standard,

wherein the transmitting the HTTP response includes;

rewriting the first information in a case where the communication line used to receive the HTTP request is a Universal Serial Bus (USB),

the rewritten first information being information for causing the data processing device to disconnect the established session after transmitting the HTTP response to the specific client application via the established session,

the rewritten first information being information corresponding to Close in accordance with the HTTP standard; and

not rewriting the first information in a case where the communication line used to receive the HTTP request is a line that is not the Universal Serial Bus and is capable of the multisession communication.

2. The communication device according to claim 1, wherein

the network interface includes a USB interface, and

the computer-readable instructions further cause the communication device to perform:

determining that the communication line used to receive the HTTP request is the Universal Serial Bus when the HTTP request is received via the USB interface.

3. The communication device according to claim 2, wherein

the computer-readable instructions further cause the communication device to perform:

rewriting content of a message to close a connection in the case where the communication line used to receive the HTTP request is a line that is not capable of the multisession communication, and

the message is a message specified in the HTTP header of the HTTP response and relating to the connection.

4. The communication device according to claim 1, wherein

the transmitting the HTTP response includes transmitting the HTTP response to the specific client application without transmitting the rewritten first information to the data processing device, in a case where a content type included in the HTTP header included in the HTTP response indicates HTML and the HTTP response is a response with content to write a web page.

5. The communication device according to claim 1, wherein

the transmitting the HTTP response includes transmitting second information to the data processing device in a case where the session established with the specific client application is retained and the HTTP request is not received for a predetermined period of time, and

the second information is information for causing the data processing device to disconnect the established session.

6. The communication device according to claim 1, wherein

the network interface includes a Bluetooth interface, and

the computer-readable instructions further cause the communication device to perform:

determining that the communication line used to receive the HTTP request is capable of the multisession communication when the HTTP request is received via the Bluetooth interface.

7. The communication device according to claim 1, wherein

the computer-readable instructions comprise a web server and a proxy,

the specific client application is a web browser,

the receiving includes creating a socket between the proxy and the web server,

the transmitting the HTTP response includes transmitting the rewritten first information to the data processing device and eliminating the created socket,

the computer-readable instructions further cause the communication device to perform:

determining whether or not the HTTP request has been received during a Keep-Alive duration, the Keep-Alive duration being started from when the socket was created in the creating; and

eliminating the created socket without transmitting the rewritten first information to the data processing device, when it is determined that the HTTP request is not received during the Keep-Alive duration in the determining.

8. The communication device according to claim 1, wherein

the receiving the HTTP request includes receiving the HTTP request from each of the one or more client applications via one endpoint among a plurality of endpoints included in the USB.

9. A non-transitory computer-readable storage medium storing computer-readable instructions for a communication device,

the communication device comprising:

a network interface for communicating with a data processing device via a communication line, the data processing device including one or more client applications that execute communications by using multisession communication;

a processor coupled to the network interface; and

a memory,

wherein the computer-readable instructions, when executed by the processor, cause the communication device to perform;

establishing a session with a specific client application among the one or more client applications via the communication line;

receiving an HTTP request from the specific client application via the established session; and

transmitting an HTTP response to the specific client application via the established session,

the HTTP response being a response to the HTTP request received in the receiving,

the HTTP response including an HTTP header containing first information,

the first information being information for causing the data processing device to retain the established session even after transmitting of the HTTP response ends and to use the retained session in a second request and subsequent requests, and

the first information being information corresponding to Keep-Alive in accordance with an HTTP standard,

wherein the transmitting the HTTP response includes;

rewriting the first information in a case where the communication line used to receive the HTTP request is a Universal Serial Bus (USB),

the rewritten first information being information for causing the data processing device to disconnect the established session after transmitting the HTTP response to the specific client application via the established session,

the rewritten first information being information corresponding to Close in accordance with the HTTP standard; and

not rewriting the first information in a case where the communication line used to receive the HTTP request is a line that is not the Universal Serial Bus and is capable of the multisession communication.

10. The non-transitory computer-readable storage medium according to claim 9, wherein

the network interface includes a USB interface, and

the computer-readable instructions further cause the communication device to perform:

determining that the communication line used to receive the HTTP request is the Universal Serial Bus when the HTTP request is received via the USB interface.

11. The non-transitory computer-readable storage medium according to claim 10, wherein

the computer-readable instructions further cause the communication device to perform:

rewriting content of a message to close a connection in the case where the communication line used to receive the HTTP request is a line that is not capable of the multisession communication, and

the message is a message specified in the HTTP header of the HTTP response and relating to the connection.

12. The non-transitory computer-readable storage medium according to claim 9, wherein

the transmitting the HTTP response includes transmitting the HTTP response to the specific client application without transmitting the rewritten first information to the data processing device, in a case where a content type included in the HTTP header included in the HTTP response indicates HTML and the HTTP response is a response with content to write a web page.

13. The non-transitory computer-readable storage medium according to claim 9, wherein

the transmitting the HTTP response includes transmitting second information to the data processing device in a case where the session established with the specific client application is retained and the HTTP request is not received for a predetermined period of time, and

the second information is information for causing the data processing device to disconnect the established session.

14. The non-transitory computer-readable storage medium according to claim 9, wherein

the network interface includes a Bluetooth interface, and

the computer-readable instructions further cause the communication device to perform:

determining that the communication line used to receive the HTTP request is capable of the multisession communication when the HTTP request is received via the Bluetooth interface.

15. The non-transitory computer-readable storage medium according to claim 9, wherein

the computer-readable instructions comprise a web server and a proxy,

the specific client application is a web browser,

the receiving includes creating a socket between the proxy and the web server,

the transmitting the HTTP response includes transmitting the rewritten first information to the data processing device and eliminating the created socket,

the computer-readable instructions further cause the communication device to perform:

determining whether or not the HTTP request has been received during a Keep-Alive duration, the Keep-Alive duration being started from when the socket was created in the creating; and

eliminating the created socket without transmitting the rewritten first information to the data processing device, when it is determined that the HTTP request is not received during the Keep-Alive duration in the determining.

16. The non-transitory computer-readable storage medium according to claim 9, wherein

the receiving the HTTP request includes receiving the HTTP request from each of the one or more client applications via one endpoint among a plurality of endpoints included in the USB.