IP Library Granted Patent US 9,264,944
Granted Patent B1
US 9,264,944 · App. 14/792,049 · Granted Feb 16, 2016

SBC-localized handoff

Inventor: James E. Brewer (Chicago, IL)
Assignee: PEERLESS NETWORK, INC.
H04W36/0016H04W8/26H04W40/36
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,264,944
App. No.
14/792,049
Granted
Feb 16, 2016
Kind
B1
Abstract

Systems and methods are provided to facilitate the performance of a Session Border Controller (SBC)-localized handoff. As part of the SBC-localized handoff, a communication device may transmit packets within a data call to an SBC via a first IP address. Subsequently, the communication device may be assigned a second IP address. The communication device may then transmit further packets to the SBC via the second IP address. In response, the SBC may route all traffic within the data call direct to the communication device via the second IP address, regardless of whether the traffic indicates that the traffic should be delivered to the first IP address.

Claims (55)

1. A method comprising:

associating, at a packet network interface, a first communication device, a particular port of a Session Border Controller (SBC, and a first IP address via which the first communication device is accessible;

maintaining, by the packet network interface, a communications session between the first communication device and a second communication device; and

during the maintained communications session:

receiving, at the particular port of the packet network interface, a first packet from the first communication device, the first packet including first content that is to be delivered to the second communication device, and the first packet indicating that the first communication device is accessible via a second IP address;

subsequent to receiving the first packet, receiving, at the SBC from the second communication device, a second packet indicating the first IP address and including second content that is to be delivered to the first communication device; and

routing, by the packet network interface, the content of the second packet to the first communication device by using the second IP address.

2. The method of claim 1 , wherein maintaining the communications session further comprises maintaining a Voice Over Internet Protocol (VoIP) call.

3. The method of claim 1 , further comprising assigning, by the packet network interface, the communications session to the particular port of the packet network interface, and wherein the second packet is routed via the assigned particular port.

4. The method of claim 1 , wherein receiving the second packet comprises receiving the second packet via a private packet network backbone.

5. The method of claim 1 , wherein the first IP address corresponds to a first communications network and the second IP address corresponds to a second communications network.

6. The method of claim 1 , wherein further comprising:

obtaining, by the packet network interface, an identifier indicated by the second packet data;

using the identifier, querying, by the packet network interface, a local call record corresponding to the communication session; and

determining, by the packet network interface, an address at which the local call record indicates that the first communication device is accessible.

7. The method of claim 6 , wherein obtaining the identifier corresponding to the communications session comprises obtaining at least one of: an identifier of the particular port, the first IP address, a Session Initiation Protocol (SIP) Call ID, or a session ID that was established with the communication session.

8. The method of claim 1 , wherein at least one of the first packet and the second packet is formatted in accordance with a real-time traffic protocol (RTP).

9. A system comprising:

a plurality of transceivers adapted to send and receive data corresponding to a data call;

a memory adapted to store non-transitory computer executable instructions; and

one or more processors adapted to interface with the plurality of transceivers, the one or more processors being configured to execute the non-transitory computer executable instructions to cause the system to:

create a local call record corresponding to the data call and indicating a first address via which a communication device servicing the data call is accessible;

while the local call record indicates that the communication device is accessible via the first address, receive, at the plurality of transceivers, first traffic of the data call, the first traffic indicating a second address via which the communication device is accessible and including a first data payload originated by the communication device;

in response to the reception of the first traffic indicating the second address, update the local call record to indicate that the communication device is accessible via the second address and not via the first address;

route the first data payload of the first traffic to a recipient party of the data call;

subsequent to updating the local call record, receive, at the plurality of transceivers, second traffic of the data call, the second traffic indicating the first address of the communication device and including a second data payload to be delivered to the communication device; and

route the second data payload of the second traffic to the communication device using the second address.

10. The system of claim 9 , wherein the data call is included in a plurality of data calls routed by the system, and wherein the non-transitory computer executable instructions are further executable by the one or more processors to cause the system to:

create a respective local record for each data call included in the plurality of data calls;

update the respective local record for the each data call with an indication of a current address of a respective communication device servicing the each data call; and

route traffic of the each data call using the updated, current address.

11. The system of claim 9 , wherein the local call record corresponding to the data call includes an identifier of the data call.

12. The system of claim 11 , wherein the identifier of the data call comprises at least one of: an identifier of a port of the system utilized to route packets to and from the communication device during the data call, the first address corresponding to the communication device, a Session Initiation Protocol (SIP) Call ID, or a session ID.

13. The system of claim 12 wherein the second traffic further includes an indication of the identifier of the data call.

14. The system of claim 9 , wherein a first communications network assigns the communication device the first address and a second communications network assigns the communication device the second address.

15. The system of claim 9 , wherein to update the local call record the non-transitory computer executable instructions are further executable by the one or more processors to cause the system to:

compare a first device identifier indicated by the first traffic to a second device identifier stored in the local call record, wherein the first and second device identifiers comprises at least one of: a Mobile Identification Number (MIN), a Mobile Directory Number (MDN), a pseudo-Electronic Serial Number (pESN), a Mobile Equipment Identified (MEID), an Integrated Circuit Card Identification (ICC ID), an International Mobile Subscriber Identity (IMSI), an International Mobile Station Equipment Identity (IMEI), or an account name; and

verify that the first device identifier matches the second device identifier; and

in response to the verification, storing the second address in the local call record.

16. A method comprising:

receiving, at a Session Border Controller (SBC), a request to establish a communication session between a first communication device and a second communication device, the first communication device corresponding to a first IP address;

assigning, by the SBC, a bearer path port of the SBC to the communication session;

routing, via the SBC and by using the bearer path port, one or more data packets of the communication session to the first communication device using the first IP address;

receiving, at the SBC via the bearer path port, a data packet of the communication session that is to be delivered to the second communication device, the data packet including an indication that the first communication device corresponds to a second IP address; and

responsive to receiving the data packet that is to be delivered to the second communication device, routing, via the SBC and by using the bearer path port, one or more further data packets of the communication session to the first communication device using the second IP address.

17. The method of claim 16 , wherein the data packet that is to be delivered to the second communication device is received from the first communication device at a first point in time, and wherein the method further comprises receiving, at the SBC at a second point in time occurring after the first point in time, an invite message from the first communication device, the invite message comprising an indication of the second IP address.

18. The method of claim 17 , further comprising:

upon receiving the invite message, enabling, by the SBC, one or more advanced call features associated with the communication session, the one or more advanced call features comprising at least one of: hold or transfer.

19. The method of claim 16 , wherein the data packet that is to be delivered to the second communication device is received from the first communication device at a first point in time, and wherein the method further comprises:

receiving, at the SBC at a third point in time occurring after the first point in time, a registration message from the first communication device, the registration message comprising an indication of the second IP address; and

upon receiving the registration message from the first communication device, transmitting, by the SBC, another registration message to a packet-switched network, the another registration message indicating the second IP address.

20. The method of claim 16 , wherein:

the first IP address is assigned to the first communication device by a first wireless network; and

the second IP address is assigned to the first communication device by a second wireless network.

21. The method of claim 16 , wherein routing the one or more further data packets to the first communication device using the second IP address comprises routing one or more further data packets using the second IP address, the one or more further data packets including an indication of the first IP address.

Assignments (8)
SECURITY INTEREST Recorded Jul 17, 2025
From: PEERLESS NETWORK, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 071745/0311 →
RELEASE OF SECURITY INTEREST Recorded Sep 12, 2022
From: FIFTH THIRD BANK, NATIONAL ASSOCIATION (SUCCESSOR TO FIFTH THIRD BANK)
To: PEERLESS NETWORK, INC.; WAVENATION, LLC
Reel/Frame 061065/0390 →
RELEASE BY SECURED PARTY Recorded Jun 7, 2019
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 049409/0091 →
RELEASE OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY Recorded Jun 14, 2018
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 046367/0991 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY Recorded May 31, 2018
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 046276/0677 →
INTELLECTUAL PROPERTY SECURTITY AGREEMENT Recorded May 31, 2018
From: PEERLESS NETWORK, INC.; WAVENATION, LLC
To: FIFTH THIRD BANK
Reel/Frame 046275/0811 →
SECURITY INTEREST Recorded Dec 14, 2016
From: PEERLESS NETWORK, INC.; AIRUS, INC.; AIRUS CLOUD COMMUNICATIONS, LLC; AIRUS VIRGINIA, INC.; PEERLESS ATLANTA DATA CENTER, LLC; PEERLESS CHICAGO DATACENTER, LLC; PEERLESS ENTERPRISE CLOUD SERVICES, LLC; PEERLESS NETWORK OF ALABAMA, LLC; PEERLESS NETWORK OF ARIZONA, LLC; PEERLESS NETWORK OF ARKANSAS, LLC; PEERLESS NETWORK OF CALIFORNIA, LLC; PEERLESS NETWORK OF COLORADO, LLC; PEERLESS NETWORK OF CONNECTICUT, LLC; PEERLESS NETWORK OF DELAWARE, LLC; PEERLESS NETWORK OF FLORIDA, LLC; PEERLESS NETWORK OF GEORGIA, LLC; PEERLESS NETWORK OF HAWAII, LLC; PEERLESS NETWORK OF IDAHO, LLC; PEERLESS NETWORK OF ILLINOIS, LLC; PEERLESS NETWORK OF INDIANA, LLC; PEERLESS NETWORK OF IOWA, LLC; PEERLESS NETWORK OF KANSAS, LLC; PEERLESS NETWORK OF KENTUCKY, LLC; PEERLESS NETWORK OF LOUISIANA, LLC; PEERLESS NETWORK OF MAINE, LLC; PEERLESS NETWORK OF MARYLAND, LLC; PEERLESS NETWORK OF MASSACHUSETTS, LLC; PEERLESS NETWORK OF MICHIGAN, LLC; PEERLESS NETWORK OF MINNESOTA, LLC; PEERLESS NETWORK OF MISSISSIPPI, LLC; PEERLESS NETWORK OF MISSOURI, LLC; PEERLESS NETWORK OF MONTANA, LLC; PEERLESS NETWORK OF NEBRASKA, LLC; PEERLESS NETWORK OF NEVADA, LLC; PEERLESS NETWORK OF NEW HAMPSHIRE, LLC; PEERLESS NETWORK OF NEW JERSEY, LIMITED LIABILITY COMPANY; PEERLESS NETWORK OF NEW MEXICO, LLC; PEERLESS NETWORK OF NEW YORK, LLC; PEERLESS NETWORK OF NORTH CAROLINA, LLC; PEERLESS NETWORK OF NORTH DAKOTA, LLC; PEERLESS NETWORK OF OHIO, LLC; PEERLESS NETWORK OF OKLAHOMA, LLC; PEERLESS NETWORK OF OREGON, LLC; PEERLESS NETWORK OF PENNSYLVANIA, LLC; PEERLESS NETWORK OF RHODE ISLAND, LLC; PEERLESS NETWORK OF SOUTH CAROLINA, LLC; PEERLESS NETWORK OF SOUTH DAKOTA, LLC; PEERLESS NETWORK OF TENNESSEE, LLC; PEERLESS NETWORK OF TEXAS, LLC; PEERLESS NETWORK OF THE DISTRICT OF COLUMBIA, LLC; PEERLESS NETWORK OF UTAH, LLC; PEERLESS NETWORK OF VERMONT, LLC; PEERLESS NETWORK OF VIRGINIA, LLC; PEERLESS NETWORK OF WASHINGTON, LLC; PEERLESS NETWORK OF WEST VIRGINIA, LLC; PEERLESS NETWORK OF WISCONSIN, LLC; PEERLESS NETWORK OF WYOMING, LLC; PEERLESS NETWORK REAL ESTATE HOLDINGS, LLC; WAVENATION, LLC; PEERLESS NETWORK HOLDINGS, INC.
To: MONROE CAPITAL MANAGEMENT ADVISORS, LLC, AS COLLATERAL AGENT
Reel/Frame 040734/0883 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 7, 2015
From: BREWER, JAMES E.
To: PEERLESS NETWORK, INC.
Reel/Frame 036004/0810 →