Flexible secure network data transfer and messaging

• US 20030037147A1
• Filed: 08/01/2001
• Published: 02/20/2003
• Est. Priority Date: 08/01/2001
• Status: Active Grant

• Current Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Original Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Inventors: Martinez, Martin, Matsubayashi, Don Hideyasu, Sodhi, Ajit Singh, Muto, Steve Yasuhiro
• Granted Patent: US 7,543,067 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention is directed to the use of a messaging component for sharing a common network communication channel by a plurality of threads of execution. The messaging component receiving a message and forwarding the message to one or more of the threads using information in a payload portion of the message, which is compared with supplied registration information. In addition, according to the present invention, messaging and job components may be used by each of a plurality of execution threads to negotiate a manner of transferring data between two network computers, wherein the job component proposes a manner of transfer, which is communicated using the messaging component to a receiving a computer. The proposed manner of transfer may be accepted or rejected by the receiving computer. An alternative manner of transfer may be proposed, where another manner of transfer is found to be unacceptable.

Claims

1. In a network, a method of using a messaging component and a single network communication channel for sending and receiving messages by a plurality of threads of execution executing on a network computer, the method comprising:

establishing, on the network computer, a network communication channel for use by the messaging component, the network connection having a network address;

supplying registration information associated with each of the plurality of execution threads executing on the network computer;

receiving a message at the network computer by the messaging component, the message containing the network address of the messaging component, the message further containing a payload portion for identifying one or more of the execution threads;

the messaging component comparing the contents of the payload portion with the registration information for each of the plurality of execution threads; and

forwarding the received message to the one or more execution threads based on the results of the comparison.

2. A method according to claim 1, further comprising the step of:

transmitting another message originating from any of the plurality of execution threads executing on the network computer via the messaging component.

3. A method according to claim 2, wherein the other message includes a payload portion for identifying one or more of the execution threads executing on another network computer.

4. A method according to claim 1, wherein the network is a digital cable network and the network computer is a set-top box.

5. A method according to claim 1, wherein the network is a digital cable network and the network computer is a cable head end.

6. A method according to claim 1, wherein the registration information comprises an identifier and a message interest for each of the plurality of execution threads.

7. A method according to claim 6, wherein the message interest comprises a message type either alone or in combination with a message ticket.

8. A method according to claim 7, wherein the message ticket comprises a unique identifier for use in identifying a specific execution thread.

9. A method according to claim 1, wherein another network computer has a messaging component, and wherein any of a plurality of execution threads that execute on the other network computer communicate via the other messaging component.

10. A method according to claim 1, wherein the network address of the messaging component comprises a socket identifier.

11. A method according to claim 1, wherein the network address of the messaging component comprises a MAC address.

12. A method according to claim 1, wherein the network address of the messaging component comprises a Network Access Service Point (NSAP) address.

26. An apparatus for using a messaging component by a plurality of messaging threads, said apparatus comprising means for performing the functions specified in any of claims 1 to 10.

27. An apparatus comprising:

a program memory for storing process steps executable to perform a method according to any of claims 1 to 10; and

a processor for executing the process steps stored in said program memory.

28. Computer-executable process steps stored on a computer readable medium, said computer-executable process steps for using a messaging component by a plurality of threads of execution, said computer-executable process steps comprising process steps executable to perform a method according to any of claims 1 to 10.

13. A method of communicating between a set-top box and a cable head end via a digital cable network, the method comprising:

establishing a common network communication channel on one or the other or both the set-top box and the cable head end, wherein the common network communication channel is shared by a plurality of applications, or execution subprocesses thereof, to send and receive messages via the digital network.

14. In a network computer that executes a messaging component and a plurality of execution threads, a method of determining a manner of transferring data to a recipient network computer, the messaging component having a network address and configured to receive and send network messages for the plurality of execution threads, the method comprising:

receiving a request from one of the execution threads to transfer data to the recipient network computer, the request including at least one requirement for carrying out the request;

based at least in part on the received requirement, determining a proposed manner of transfer;

transmitting, using the messaging component, a start message to the recipient network computer, the start message including the proposed manner of transfer;

in response to a rejection of the proposed manner of transfer, determining whether an alternative manner of transfer is available; and

responding, using the messaging component, to the rejection with an alternative manner of transfer where one is available.

15. A method according to claim 14, further comprising the steps of:

determining, by the recipient network computer, whether or not the proposed manner of transfer is acceptable; and

transmitting, to the network computer, a response message which indicates an outcome of the determining step.

16. A method according to claim 15, wherein the start message is a portion of a payload of a network message, the payload includes a ticket portion that identifies a network address of the recipient network computer, the method further comprising the steps of:

creating a socket with an associated port on the recipient network computer, where it is determined that either the proposed or the alternative manner of transfer is acceptable; and

transmitting an indication of the port as part of a payload portion of the response message.

17. A method according to claim 15, wherein the recipient network computer comprises a recipient messaging component, at least one execution thread which is an intended recipient of the data transfer, and a job component, and wherein the recipient messaging component forwards the proposed manner of transfer to the job component to determine whether or not the proposed manner of transfer is acceptable and to transmit, to the network computer via the recipient messaging component, a response message which indicates whether or not the proposed manner of transfer is acceptable.

18. A method according to claim 17, further comprising:

receiving, by the job component, the data transfer via the associated port, and notifying the at least one recipient thread.

19. A method according to claim 18, wherein the data is transferred via shared memory for access to the at least one recipient thread.

20. A method according to claim 14, wherein the proposed manner of transfer indicates a “

by-reference”

delivery mode, the method further comprising;

accessing a network server referenced in the start message, wherein the determining step determines whether accessing the network server is successful.

21. A method according to claim 14, wherein the proposed manner of transfer indicates a “

direct”

delivery mode using a specified network protocol, the step of determining, by the recipient network computer, whether the proposed manner of transfer is acceptable further comprising;

determining whether the specified network protocol is supported on the recipient network computer.

22. A method according to claim 21, wherein the step of transmitting a response message further comprising the step of:

transmitting an indication of a port to which the data transfer is to be directed as part of a payload portion of the response message.

23. An apparatus for determining a manner of transferring data, said apparatus comprising means for performing the functions specified in any of claims 14 to 22.

24. An apparatus comprising:

a program memory for storing process steps executable to perform a method according to any of claims 14 to 22; and

a processor for executing the process steps stored in said program memory.

25. Computer-executable process steps stored on a computer readable medium, said computer-executable process steps for determining a manner of transferring data, said computer-executable process steps comprising process steps executable to perform a method according to any of claims 14 to 22.