Address and port number abstraction when setting up a connection between at least two computational devices

• US 20070168551A1
• Filed: 02/28/2005
• Published: 07/19/2007
• Est. Priority Date: 03/02/2004
• Status: Abandoned Application

• Current Assignee: Koninklijke Philips N.V.
• Original Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Inventors: Eisink, Jurjen
• Application Number:
  US10/598,227
• Publication Number:
  US 20070168551A1
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• 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/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168

Abstract

The invention relates to a method, computational devices, a system of computational devices and computer program products for abstracting address and port number usage for an application running on first and second devices. The system comprises a first device (10) that receives a request for binding of a socket to a service from the application in said first device, obtains a service name, generates a resource record (26) comprising a binding between a port number and the service name, creates a socket and binds it to the port number, and sends the record to a resolving unit (22) associated with the first device, and a second device (16) that receives a request for a connection from the application in said second device, sends a query regarding the service name to the resolving unit, and receives an address and port number associated with the first device as response to the query.

Claims

1. Method of abstracting address and port number usage for an application (30) running on at least a first (10) and a second (16) device and comprising, in the first device, the steps of:

receiving a request for binding of a socket to a service from the application in said first device, (step 50),

obtaining an application specific service name to be used for a connection between the devices, (step 51),

generating a resource record (26) comprising a binding between at least a port number (PX2) of said first device on the one hand and the application specific service name on the other hand, (step 52),

creating a socket and binding it to the port number, (step 53), and

ordering the sending of the resource record to an associated local name and service resolving unit (22), (step 54), such that the resource record can be stored in the name and service resolving unit in order to allow the application running in the second device to obtain an address and port number associated with the first device for use for a connection through sending a query to the name and service resolving unit about the application specific service name of the first device.

2. Method according to claim 1, wherein the resource record also comprises a binding between a locatable device name and an address (AX) of the first device.

3. Method according to claim 1, further comprising the step of ordering the sending of at least the application specific service name to the second device for allowing the set up of the additional connection.

4. Method according to claim 3, wherein the step of ordering the sending comprises ordering the sending also of a device name of the first device.

5. Method according to claim 1, wherein the step of obtaining a service name comprises receiving the service name from the application running in the device.

6. Method according to claim 1, wherein the step of obtaining a service name comprises generating a service name to be used.

7. Method according to claim 6, further comprising the step of returning the generated service name to the application.

8. Method according to claim 1, further comprising the step of ordering removal of the resource record from the associated name and service resolving unit once the connection is no longer needed, (step 70).

9. Method according to claim 1, wherein the service name includes protocol information.

10. Method according to claim 1, further comprising, in the second device, the steps of:

receiving a request for a connection to the application in the first device from the application in the second device, (step 59),

ordering the sending of a query regarding at least said application specific service name of the first device intended for the name and service resolving unit associated with the first device, (step 60), and

receiving address and port number information associated with the first device as a result of the query, such that the connection can be set up using the received address and port number, (step 67).

11. First computational device (10) for abstracting address and port number usage for an application (30) running on at least the first and a second (16) device, comprising:

a socket layer engine (32) arranged to;

receive a request for binding of a socket to a service from the application in said first device,

obtain an application specific service name to be used for a connection between the devices,

generate a resource record (26) comprising a binding between at least an own port number (PX2) on the one hand and the application specific service name on the other hand,

create a socket and bind it to the port number, and

order the sending of the resource record to a local name and service resolving unit (22) associated with the first device, such that the resource record can be stored in the name and service resolving unit, for allowing the application in the second device to obtain an address and port number associated with the first device for use in communication by means of a query regarding at least the application specific service name of the first device.

12. Computational device according to claim 11, wherein the resource record also comprises a binding between a locatable device name and an address (AX) of the first device.

13. Computational device according to claim 11, wherein the socket layer engine is further arranged to order the sending of at least the application specific service name to the second device for allowing the set up of the connection.

14. Computational device according to claim 13, wherein the socket layer engine is also arranged to order the sending of the device name of the first device.

15. Computational device according to claim 11, wherein the socket layer engine is further arranged to, in obtaining a service name, receive the service name from the application running in the device.

16. Computational device according to claim 11, wherein the socket layer engine is further arranged to, in obtaining a service name, generate a service name to be used.

17. Computational device according to claim 16, wherein the socket layer engine is further arranged to return the generated service name to the application.

18. Computational device according to claim 11, wherein the socket layer engine is further arranged to order the removal of the resource record from the name and service resolving unit once the additional connection is no longer needed.

19. Computational device according to claim 11, wherein the service name includes protocol information.

20. Second computational device (16) for abstracting address and port number usage for an application (30) running on at least a first (10) and the second device and comprising:

a socket layer engine (32) arranged to;

receive a request for a connection from the application in said second device,

order the sending of a query regarding at least an application specific service name associated with the first device to a name and service resolving unit (22) associated with the first device, which name and service resolving unit has a resource record (26) comprising a binding between an address (AX) and a port number (PX2) of said first device on the one hand and at least the application specific service name on the other hand, and

receive an address and port number associated with the first device as a response to the query for use in setting up a connection, such that the connection can be set up using the received address and port number.

21. System of computational devices for abstracting address and port number usage for an application (30) running on at least a first (10) and a second (16) device and comprising:

said first computational device having a socket layer engine (32) arranged to;

receive a request for binding of a socket to a service from the application in said first device,

obtain an application specific service name to be used for a connection between the devices,

generate a resource record comprising a binding between at least an own port number (PX2) of the first device on the one hand and the application specific service name on the other hand,

create a socket and bind it to the port number, and

order the sending of the resource record to a local name and service resolving unit (22) associated with the first device, such that the resource record can be stored in the name and service resolving unit,

said second computational device having a socket layer engine (32) arranged to;

receive a request for a connection from the application in said second device,

order the sending of a query regarding the application specific service name associated with the first device to the name and service resolving unit associated with the first device, and

receive an address and port number associated with the first device for use in setting up a connection as a response to the query, such that the connection can be set up using the received address and port number.

22. Computer program product (72) to be used on a first computational device (10) for abstracting address and port number usage for an application (30) running on at least the first and a second (16) device, said computer program product having:

computer program code, to make the first device execute, when said program code is loaded in the first device;

receive a request for binding of a socket to a service from the application in said first device,

obtain an application specific service name to be used for a connection between the devices,

generate a resource record (26) comprising a binding between at least a port number (PX2) of said first device on the one hand and the application specific service name on the other hand,

create the socket and bind it to the port number, and

order the sending of the resource record to a local name and service resolving unit (22) associated with the first device, such that the resource record can be stored in the name and service resolving unit for allowing the application in the second device to obtain an address and port number associated with the first device for use for setting up a connection by means of a query regarding the device name and application specific service name of the first device.

23. Computer program product (72) to be used on a second computational device (16) for abstracting address and port number usage for an application (30) running on at least a first (10) and the second device, said computer program product having:

computer program code, to make the second device execute, when said program code is loaded in the second device;

receive a request for a connection from an application (30) in said second device,

order the sending of a query regarding at least an application specific service name associated with the first device to a name and service resolving unit (22) associated with the first device, which name and service resolving unit has a resource record (26) comprising a binding between an address (AX) and a port number (PX2) of said first device on the one hand and the application specific service name on the other hand, and

receive an address and port number associated with the first device for use in setting up a connection as a response to the query, such that the connection can be set up using the received address and port number as well as an own address (AY) and port number.