Path switching procedure for device-to-device communication

• US 9,756,497 B2
• Filed: 12/13/2013
• Issued: 09/05/2017
• Est. Priority Date: 02/22/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Stojanovski, Alexandre, Venkatachalam, Muthaiah, Johnsson, Kerstin
• Primary Examiner(s): Han, Clemence
• Application Number:
  US14/762,764
• Publication Number:
  US 20150359033A1
• Time in Patent Office: 1,362 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 2101/677 Multiple interfaces, e.g. multihomed nodes
• CPC Class Codes: H04L 27/2614 Peak power aspects
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2525 Translation at a client
• CPC Class Codes: H04L 61/2539 Hiding addresses; Keeping addresses anonymous
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/2592 using tunnelling or encapsulation
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/06 Testing, supervising or monitoring using simulated traffic
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0289 Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/12 using signalling between network elements
• CPC Class Codes: H04W 36/0088 Scheduling hand-off measurements
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/244 : using a network of reference devices, e.g. beaconing
• CPC Class Codes: H04W 48/08 : Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/028 : switching on or off only a part of the equipment circuit blocks
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 74/002 : Transmission of channel access control information
• CPC Class Codes: H04W 74/02 : Hybrid access
• CPC Class Codes: H04W 74/04 : Scheduled access hybrid access H04W74/02
• CPC Class Codes: H04W 74/08 : Non-scheduled access, e.g. ALOHA hybrid access H04W74/02
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/23 : Manipulation of direct-mode connections
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 8/005 : Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Session continuity may be maintained when communication devices transition from communicating through network infrastructure (e.g., through a cellular network) to direct mode communications (e.g., a communication path directly between two communication devices). For example, in switching from an infrastructure mode communication path to a direct mode communication path, a method may include: determining a public-facing address corresponding to the infrastructure path; replacing, for a packet that is to be transmitted over the direct mode communication path to a second communication device, a source address field of the packet with the determined public-facing address; and encapsulating the packet with source and destination address fields corresponding to the first and second communication device through the direct mode communication path respectively.

Claims

1. A communication device that maintains session continuity, for applications executing in the communication device, in switching from an infrastructure mode communication path to a direct mode communication path, the communication device comprising:

a non-transitory computer readable medium containing program instructions; and

one or more processors, to execute the program instructions to;

determine a public-facing address corresponding to the infrastructure path of the communication device;

replace, for a packet that is to be transmitted over the direct mode communication path to a second communication device, a source address field of the packet with the determined public-facing address;

encapsulate the packet with source and destination address fields corresponding to the communication device and the second communication device, respectively, through the direct mode communication path; and

transmit the encapsulated packet to the direct mode communication path.

2. The communication device of claim 1, wherein the one or more processors are further to execute the program instructions to:

decapsulate packets received over the direct mode communication path from the second communication device, the decapsulation including replacing destination address fields of the packets with a private address of the communication device in the infrastructure path; and

provide the decapsulated packets to an application layer of the communication device.

3. The communication device of claim 1, wherein the source address field of the packet that is to be transmitted over the direct mode communication path is initially created by the communication device as an address corresponding to the infrastructure path of the communication device.

4. The communication device of claim 1, wherein the replaced source address field of the packet includes a public-facing address that refers to a private address of the communication device in the infrastructure path.

5. The communication device of claim 1, wherein the public-facing address and the source address each include an Internet Protocol (IP) address and a port number.

6. The communication device of claim 1, wherein the one or more processors, when determining the public-facing address, are further to:

query a Port Control Protocol (PCP) server, a Session Traversal Utilities for Network Address Translation (STUN) server, or a Traversal Using Relays around Network Address Translation (TURN) server.

7. The communication device of claim 1, wherein the direct mode communication path includes wireless communications based on Institute of Electrical and Electronics Engineers (IEEE) 802.11-based wireless communication standards or based on 3rd Generation Partnership Project (3GPP) standards.

8. The communication device of claim 7, wherein communications over the infrastructure mode communication path includes communications based on cellular wireless communication standards.

9. A communication device to maintain session continuity, for applications executing in the communication device, in switching from a direct mode communication path to an infrastructure communication path, the communication device including:

a non-transitory computer readable medium containing program instructions; and

one or more processors, to execute the program instructions to;

determine a public-facing address corresponding to the infrastructure path of the communication device;

transmit, over the direct mode communication path and to a second communication device, the public-facing address;

receive, over the infrastructure path, an encapsulated packet from the second communication device;

decapsulate the received encapsulated packet to obtain a packet that includes addressing information corresponding to the direct mode communication path; and

provide the decapsulated packet to an application layer of the communication device.

10. The communication device of claim 9, wherein the one or more processors are further to execute the program instructions to:

receive, from the second communication device and over the direct mode communication path, a public-facing address corresponding to the infrastructure communication path of the second communication device.

11. The communication device of claim 9, wherein the one or more processors are further to execute the program instructions to:

encapsulate, by the communication device, packets that are to be delivered to the second communication device, the encapsulation being based on the public-facing address corresponding to the second communication device; and

transmit, by the communication device and over the infrastructure path, the encapsulated packets.

12. The communication device of claim 9, wherein the public-facing address includes an Internet Protocol (IP) address and a port number.

13. The communication device of claim 9, wherein when determining the public-facing address, the one or more processors are further to:

query a Port Control Protocol (PCP) server, a Session Traversal Utilities for Network Address Translation (STUN) server, or a Traversal Using Relays around Network Address Translation (TURN) server.

14. The communication device of claim 9, wherein the direct mode communication path includes wireless communications based on Institute of Electrical and Electronics Engineers (IEEE) 802.11-based wireless communication standards or based on 3rd Generation Partnership Project (3GPP) standards.

15. User equipment (UE) comprising:

a memory to store instructions; and

at least one processor to execute the instructions stored by the memory to;

connect with a second UE, using a communication session formed over an infrastructure path; and

switch communication paths, with the second UE, from the infrastructure path to a direct wireless communication path to the second UE, the switching being performed transparently to an application layer process that is executing at the UE and that is communicating with the second UE, wherein the at least one processor, when switching communication paths is to further execute the instructions stored by the memory to;

replace, for a packet that is to be transmitted over the direct wireless communication path to the second UE, a source address field of the packet with a public-facing address of the UE in the infrastructure path;

encapsulate the packet with source and destination address fields corresponding to the UE and the second UE, respectively, through the direct wireless communication path; and

transmit the encapsulated packet over the direct wireless communication path.

16. The UE of claim 15, wherein the at least one processor is to further execute the instructions stored by the memory to:

decapsulate packets received over the direct wireless communication path from the second UE, the decapsulation including replacing destination address fields of the packets with a private address of the communication device in the infrastructure path; and

provide the decapsulated packets to an application layer of the communication device.

17. A method for maintaining session continuity, for applications executing in a communication device, in switching from an infrastructure mode communication path to a direct mode communication path, the method comprising:

determining, by the communication device, a public-facing address corresponding to the infrastructure path of the communication device;

replacing, by the communication device and for a packet that is to be transmitted over the direct mode communication path to a second communication device, a source address field of the packet with the determined public-facing address;

encapsulating, by the communication device, the packet with source and destination address fields corresponding to the communication device and the second communication device, respectively, through the direct mode communication path; and

transmitting the encapsulated packet to the direct mode communication path.

18. The method of claim 17, further comprising:

decapsulating, by the communication device, packets received over the direct mode communication path from the second communication device, the decapsulation including replacing destination address fields of the packets with a private address of the communication device in the infrastructure path; and

providing the decapsulated packets to an application layer of the communication device.

19. The method of claim 17, wherein the source address field of the packet that is to be transmitted over the direct mode communication path is initially created by the communication device as an address corresponding to the infrastructure path of the communication device.

20. The method of claim 17, wherein the replaced source address field of the packet includes a public-facing address that refers to a private address of the communication device in the infrastructure path.

21. The method of claim 17, wherein the public-facing address and the source address each include an Internet Protocol (IP) address and a port number.

22. The method of claim 17, wherein the determining the public-facing address includes:

querying a Port Control Protocol (PCP) server, a Session Traversal Utilities for Network Address Translation (STUN) server, or a Traversal Using Relays around Network Address Translation (TURN) server.

23. The method of claim 17, wherein the direct mode communication path includes wireless communications based on Institute of Electrical and Electronics Engineers (IEEE) 802.11-based wireless communication standards or based on 3rd Generation Partnership Project (3GPP) standards.

24. The method of claim 23, wherein communications over the infrastructure mode communication path includes communications based on cellular wireless communication standards.