PEER-TO-PEER COMMUNICATION BETWEEN DIFFERENT TYPES OF INTERNET HOSTS

• US 20090248800A1
• Filed: 03/31/2008
• Published: 10/01/2009
• Est. Priority Date: 03/31/2008
• Status: Active Grant

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Wang, Y.T., Chu, Thomas P., Feather, Frank
• Granted Patent: US 7,720,976 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 2101/659 Internet protocol version 6 [IPv6] addresses
• CPC Class Codes: H04L 2101/677 Multiple interfaces, e.g. multihomed nodes
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/5076 Update or notification mechanisms, e.g. DynDNS
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

In one embodiment, a method for processing, at an enhanced Session Initiation Protocol (SIP) proxy (e-proxy), (1) a SIP INVITE message to a first user at an IPv4/IPv6 dual-stack (DS) host, connected to an IPv6 network, from a second user at an IPv4 host, connected to an IPv4 network. The e-proxy receives the SIP INVITE message from the IPv4 network. When the e-proxy determines that Dual Stack Transition Mechanism (DSTM) service is required, the e-proxy obtains a temporary IPv4 address for the DS host, finds a suitable tunnel end-point (TEP), and sends a corresponding, but modified, INVITE message to the DS host. The modified INVITE message body includes invocation of DSTM service, the temporary IPv4 address, the TEP'"'"'s IPv6 address, and the IPv4 host'"'"'s IPv4 address. The e-proxy sends a BIND message to the TEP to bind the DS host'"'"'s IPv6 address to the temporary IPv4 address for proper tunneling.

Claims

1. A method (e.g., FIG. 7) for processing signaling protocol (SP) messages, the method comprising:

(1) receiving an SP invite message addressed to one of;

(i) a first user hosted at a first host (e.g., 602) connected to a first network (e.g., 605) using a first network addressing protocol (FNAP) (e.g., IPv6), the SP invite message addressed from a second user hosted at a second host (e.g., 603) connected to a second network (e.g., 608), different from the first network, using a second network addressing protocol (SNAP) (e.g., IPv4), different from the FNAP; and

(ii) the second user, the SP invite message addressed from the first user, wherein;

(a) the first host has an FNAP address (e.g., A);

(b) the second host has an SNAP address (e.g., B); and

(c) the SP invite message invites the addressed-to user to set up a communication session with the addressed-from user, the communication session comprising transmission of bearer traffic packets;

(2) determining that a protocol interworking mechanism (e.g., DSTM) for the communication session needs to be invoked;

(3) if a temporary SNAP address is not already associated with the first host'"'"'s FNAP address, then;

(i) obtaining a temporary SNAP address (e.g., D) to associate with a cross-border transport module (CBTM) (e.g., 604), wherein the CBTM has an FNAP address (e.g., C) and is adapted to convert bearer traffic packets of the communication session between FNAP-compatible format and SNAP-compatible format; and

(ii) instructing the CBTM to associate the temporary SNAP address with the first host'"'"'s FNAP address; and

(4) forwarding to the addressed-to host a corresponding modified SP invite message that provides at least one of the FNAP address of the CBTM and the temporary SNAP address.

2. The method of claim 1, wherein:

the receiving step comprises receiving an SP invite message from the first user addressed to the second user; and

the corresponding modified SP invite message to the second user provides the temporary SNAP address and does not provide the FNAP address of the CBTM.

3. The method of claim 1, wherein:

the receiving step comprises receiving an SP invite message from the second user addressed to the first user; and

the corresponding modified SP invite message provides the FNAP address of the CBTM.

4. The method of claim 1, wherein, during the communication session:

(i) the first host addresses FNAP-format bearer traffic packets of the communication session to the FNAP address of the CBTM;

(ii) the second host addresses SNAP-format bearer traffic packets of the communication session to the temporary SNAP address; and

(iii) the CBTM converts;

(a) FNAP-format bearer traffic packets of the communication session addressed from the first host and addressed to the CBTM into SNAP-format bearer traffic packets addressed to the second host and addressed from the temporary SNAP address; and

(b) SNAP-format bearer traffic packets of the communication session addressed from the second host and addressed to the temporary SNAP address into FNAP-format bearer traffic addressed to the first host and addressed from the CBTM.

5. The method of claim 4, wherein the CBTM converts bearer traffic packets by tunneling, wherein the CBTM is a Tunnel End-Point (TEP) that, during the communication session:

encapsulates SNAP-format bearer traffic packets (e.g., 901) from the second host to generate FNAP-format bearer traffic packets (e.g., 901′

) for delivery to the first host; and

decapsulates FNAP-format bearer traffic packets (e.g., 902) from the first host to extract SNAP-format bearer traffic packets (e.g., 902′

) for delivery to the second host.

6. The method of claim 5, wherein the step of instructing the TEP to associate the temporary SNAP address with the first host'"'"'s FNAP address comprises sending, to the TEP, a binding message comprising the temporary SNAP address and the first host'"'"'s FNAP address.

7. The method of claim 5, wherein:

the receiving step comprises receiving an SP invite message from the second user addressed to the first user; and

the corresponding modified SP invite message to the first user provides;

the FNAP address of the CBTM;

the temporary SNAP address;

the SNAP address of the second host; and

an invocation of the protocol interworking mechanism.

8. The method of claim 4, wherein the CBTM is a translation end-point (TrEP) that, during the communication session:

translates SNAP-format bearer traffic packets from the second host and addressed to the TrEP into FNAP-format bearer traffic packets addressed to the first host; and

translates FNAP-format bearer traffic packets from the first host and addressed to the TrEP into SNAP-format bearer traffic packets addressed to the second host.

9. The method of claim 1, further comprising:

(5) receiving a corresponding SP okay message from the addressed-to user; and

(6) forwarding, to the addressed-from user, a corresponding modified SP okay message that provides at least one of the FNAP address of the CBTM and the temporary SNAP address.

10. The method of claim 9, wherein:

the CBTM is a tunneling end-point (TEP);

the SP invite is addressed to the second user;

the corresponding modified SP invite message to the second user provides the temporary SNAP address;

the corresponding SP okay message is addressed to the first user; and

the corresponding modified SP okay message to the first user provides;

the FNAP address of the CBTM;

the temporary SNAP address;

the SNAP address of the second host; and

an invocation of the protocol interworking mechanism.

11. The method of claim 9, wherein determining that a protocol interworking mechanism for the communication session needs to be invoked:

is performed after receiving the corresponding SP okay message; and

depends on the contents of the corresponding SP okay message.

12. The method of claim 1, wherein the corresponding modified SP invite message to the addressed-to user provides the temporary SNAP address in a required SP invite message body section and provides the FNAP address of the CBTM in an optional SP invite message body section.

13. The method of claim 1, wherein:

the signaling protocol (SP) is Session Initiation Protocol (SIP);

the SP invite message is a SIP INVITE message;

instructing the CBTM is performed using a BIND message;

the FNAP is IPv6;

the SNAP is IPv4; and

the communication session is a peer-to-peer (P2P) communication session.

14. The method of claim 1, wherein if a temporary SNAP address is already associated with the first host'"'"'s FNAP address, then:

(i) obtaining a different temporary SNAP address to associate with the CBTM; and

(ii) instructing the CBTM to associate the different temporary SNAP address with the first host'"'"'s FNAP address.

15. An enhanced signaling protocol (SP) proxy (e.g., 601) adapted to:

(1) receive an SP invite message addressed to one of;

(i) a first user hosted at a first host (e.g., 602) connected to a first network (e.g., 605) using a first network addressing protocol (FNAP) (e.g., IPv6), the SP invite message addressed from a second user hosted at a second host (e.g., 603) connected to a second network (e.g., 608), different from the first network, using a second network addressing protocol (SNAP) (e.g., IPv4), different from the FNAP; and

(ii) the second user, the SP invite message addressed from the first user, wherein;

(a) the first host has an FNAP address (e.g., A);

(b) the second host has an SNAP address (e.g., B); and

(c) the SP invite message invites the addressed-to user to set up a communication session with the addressed-from user, the communication session comprising transmission of bearer traffic packets;

(2) determine that a protocol interworking mechanism (e.g., DSTM) for the communication session needs to be invoked;

(3) if a temporary SNAP address is not already associated with the first host'"'"'s FNAP address, then;

(i) obtain a temporary SNAP address (e.g., D) to associate with a cross-border transport module (CBTM) (e.g., 604), wherein the CBTM has an FNAP address (e.g., C) and is adapted to convert bearer traffic packets of the communication session between FNAP-compatible format and SNAP-compatible format; and

(ii) instruct the CBTM to associate the temporary SNAP address with the first host'"'"'s FNAP address; and

(4) forward to the addressed-to host a corresponding modified SP invite message that provides at least one of the FNAP address of the CBTM and the temporary SNAP address.

16. The enhanced SP proxy of claim 15, wherein the enhanced SP proxy and the CBTM are connected to each other and to the first and second networks.

17. The enhanced SP proxy of claim 15, wherein the enhanced SP proxy is further adapted to:

(5) receive a corresponding SP okay message from the addressed-to user; and

(6) forward, to the addressed-from user, a corresponding modified SP okay message that provides at least one of the FNAP address of the CBTM and the temporary SNAP address.

18. The enhanced SP proxy of claim 15, wherein the CBTM is a Tunnel End-Point (TEP) adapted to:

encapsulate SNAP-format bearer traffic packets from the second host to generate FNAP-format bearer traffic packets for delivery to the first host; and

decapsulate FNAP-format bearer traffic packets from the first host to extract SNAP-format bearer traffic packets for delivery to the second host.

19. The enhanced SP proxy of claim 15, wherein the CBTM is a Translation End-Point (TrEP) adapted to:

translate SNAP-format bearer traffic packets from the second host and addressed to the TrEP into FNAP-format bearer traffic packets addressed to the first host; and

translate FNAP-format bearer traffic packets from the first host and addressed to the TrEP into SNAP-format bearer traffic packets addressed to the second host.

20. The enhanced SP proxy of claim 15, wherein:

the signaling protocol (SP) is Session Initiation Protocol (SIP);

the enhanced SP proxy is an e-proxy;

the SP invite message is a SIP INVITE message;

instructing the CBTM is performed using a BIND message;

the FNAP is IPv6;

the SNAP is IPv4; and

the communication session is a peer-to-peer (P2P) communication session.

21. A first host (e.g., 602) connected to a first network (e.g., 605) using a first network addressing protocol (FNAP) (e.g., IPv6), the first host adapted to:

(1) receive from an e-proxy a modified SP invite message, wherein;

the modified SP invite message is generated by the e-proxy from a corresponding first SP invite message addressed to a first user hosted at the first host;

the first SP invite message is addressed from a second user hosted at a second host (e.g., 603) connected to a second network (e.g., 608), different from the first network;

the second network uses a second network addressing protocol (SNAP) (e.g., IPv4), different from the FNAP;

each of the first SP invite message and the corresponding modified SP message has an invitation for the first user to set up a communication session with the second user;

the communication session comprises transmission of bearer traffic packets;

the first host has an FNAP address (e.g., A);

the second host has an SNAP address (e.g., B);

the modified SP invite message provides an FNAP address of a cross-border transport module (CBTM) (e.g., 604) and a temporary SNAP address associated with the first host'"'"'s FNAP address; and

the CBTM is adapted to convert bearer traffic packets of the communication session between FNAP-compatible format and SNAP-compatible format;

(2) use a protocol interworking mechanism (e.g., DSTM) for the communication session in response to an invocation by the e-proxy, in the modified SP invite message, to use the protocol interworking mechanism; and

(3) use the FNAP address of the CBTM and the temporary SNAP address in generating outgoing bearer traffic packets for the communication session.