IP Library Granted Patent US 10,944,680
Granted Patent B2
US 10,944,680 · App. 15/803,435 · Granted Mar 9, 2021

Communications methods and apparatus

Inventors: Ashish Sharma (Bangalore, IN); Nagesh Kumar Bollapalli (Bangalore, IN); Siddharth Gahlaut (Westford, MA)
Assignee: Ribbon Communications Operating Company, Inc.
H04L47/2441H04L41/0896H04L43/087H04L43/0829H04L45/302H04L43/0852H04L43/0888H04L45/38H04L45/64H04L47/2483
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 10,944,680
App. No.
15/803,435
Granted
Mar 9, 2021
Kind
B2
Abstract

The present invention relates to communications methods, apparatus and systems for collecting metrics and/or traffic routing using SDN principles. In an exemplary method embodiment, the method includes the steps of: operating a SBC to: (i) receive a session initiation signal used to initiate a first media session; (ii) send to an SDN controller session identification information identifying a first RTCP packet stream corresponding to the first media session and causing said SDN controller to control a first open flow switch to establish an entry in a table to cause the first open flow switch to send a copy of the RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards the intended first RTCP packet stream destination.

Claims (67)

1. A communications method, the method comprising:

receiving, by a session border controller (SBC), a session initiation signal used to initiate a first media session; and

sending, by the SBC to a Software Defined Network (SDN) controller, session identification information identifying a first Real-time Transport Control Protocol (RTCP) packet stream corresponding to the first media session and causing said SDN controller to control a first open flow switch to establish an entry in a first table to cause the first open flow switch to send a copy of RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

2. The communications method of claim 1 , further comprising:

generating, by the SDN controller, an entry in a group table of the first open flow switch, said entry in the group table including RTCP packet stream identification information identifying the first RTCP packet stream and an address of the SBC to which the copy of the RTCP packets corresponding to the first RTCP packet stream are to be forwarded, said group table being a different table than said first table, said first table being a flow table, said entry in the first flow table being a flow table entry.

3. The communications method of claim 2 , further comprising:

forwarding, by the first open flow switch, the copy of the RTCP packets corresponding to the first RTCP packet stream corresponding to the first media session to the SBC using the SBC address included in the group table as a destination address.

4. The communications method of claim 3 , further comprising:

receiving, by the SBC, the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream corresponding to the first media session from the first open flow switch;

identifying, by the SBC, that said received forwarded copy of the RTCP packets correspond to said first RTCP packet stream based on an SBC Internet Protocol (IP) address port pair of the SBC at which the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream is received or from information contained in the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream;

analyzing, at the SBC, the received forwarded copy of the RTCP packets to determine one or more Quality of Service (QoS) metrics; and

communicating, by the SBC, network control information to said SDN controller.

5. The communications method of claim 4 , wherein the one or more Quality of Service metrics includes at least one of the following: R-Factor, network-packet loss, or packets discarded due to jitter.

6. The communications method of claim 4 , further comprising:

receiving, by the SDN controller, said network control information;

analyzing, by the SDN controller, said network control information; and

when said SDN controller determines that a condition has been satisfied, operating the SDN controller to: i) indicate to the first open flow switch a new priority level for Real-time Transport Protocol packets of the first media session, ii) control at least one switch to alter a path for the first media session, or iii) control at least one switch to alter a path for a second media session to alleviate a detected Quality of Service problem based on said received network control information; and

wherein said at least one switch includes at least the first open flow switch or an additional switch.

7. The communications method of claim 6 , further comprising:

determining, by the SDN controller, network routing paths in response to new media session requests which optimize network bandwidth utilization based on the received network control information.

8. The communications method of claim 4 , further comprising:

storing or logging, by the SBC, RTCP information determined, by the SBC, from said received RTCP packets into one or more Call Data Records.

9. The communications method of claim 4 , further comprising:

communicating, by the SBC, QoS information to a routing engine for use in making future network routing decisions, said QoS information being based on said QoS metrics.

10. The communications method of claim 1 , wherein the SBC is a signaling SBC (S-SBC).

11. The communications method of claim 1 , wherein said first table is a flow table.

12. The communications method of claim 11 ,

wherein said entry in said first table includes a group identifier (ID) identifying a group table entry in a group table of the first open flow switch, said group table entry being established with or prior to said entry in said first table.

13. A communications system comprising:

a first open flow switch;

a Software Defined Network (SDN) controller; and

a session border controller (SBC), said SBC including:

memory; and

a processor that controls the SBC to:

receive a session initiation signal used to initiate a first media session; and

send to the SDN controller session identification information identifying a first Real-time Transport Control Protocol (RTCP) packet stream corresponding to the first media session and causing said SDN controller to control the first open flow switch to establish an entry in a first table to cause the first open flow switch to send a copy of RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

14. The communications system of claim 13 , wherein said SDN controller includes a processor, wherein said processor in the SDN controller controls the operation of the SDN controller to generate an entry in a group table of the first open flow switch, said entry in the group table including RTCP packet stream identification information identifying the first RTCP packet stream and an address of the SBC to which the copy of the RTCP packets corresponding to the first RTCP packet stream are to be forwarded, said group table being a different table than said first table, said first table being a flow table, said entry in the first flow table being a flow table entry.

15. The communications system of claim 14 , wherein:

the first open flow switch forwards the copy of the RTCP packets corresponding to the first RTCP packet stream corresponding to the first media session to the SBC using the SBC address included in the group table as a destination address.

16. The communications system of claim 15 , wherein said processor in said SBC further controls the SBC to:

receive the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream of the first media session from the first open flow switch;

identify that said received forwarded copy of the RTCP packets correspond to said first RTCP packet stream based on an SBC Internet Protocol (IP) address port pair of the SBC at which the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream is received or from information contained in the forwarded copy of the RTCP packets corresponding to the first RTCP packet stream;

analyze the received forwarded copy of the RTCP packets to determine one or more Quality of Service (QoS) metrics; and

communicate network control information to said SDN controller.

17. The communications system of claim 16 , wherein the one or more Quality of Service metrics includes at least one of the following: R-Factor, network-packet loss, or packets discarded due to jitter.

18. The communications system of claim 16 , wherein said processor in the SDN controller controls the SDN controller to:

receive said network control information;

analyze said network control information; and

when said SDN controller determines that a condition has been satisfied controls the SDN controller to: i) indicate to the first open flow switch a new priority level for Real-time Transport Protocol packets of the first media session, ii) control at least one switch to alter a path for the first media session, or iii) control at least one switch to alter a path for a second media session to alleviate a detected Quality of Service problem based on said received network control information; and

wherein said at least one switch includes at least the first open flow switch or an additional switch.

19. The communications system of claim 18 , wherein said processor included in said SDN controller further controls the SDN controller to determine network routing paths in response to new media session requests which optimize network bandwidth utilization based on the received network control information.

20. The communications system of claim 16 , wherein said processor included in said SBC further controls the SBC to store or log RTCP information determined from said received RTCP packets into one or more Call Data Records in the memory of the SBC or in a storage device.

21. The communications system of claim 16 , wherein said processor included in said SBC further controls the SBC to communicate QoS information to a routing engine for use in making future network routing decisions, said QoS information being based on said QoS metrics.

22. The communications system of claim 13 , wherein the SBC is a signaling SBC (S-SBC).

23. A non-transitory computer readable medium including computer executable instructions which when executed by one or more processors of a session border controller (SBC) cause the SBC to perform the steps of:

receiving a session initiation signal used to initiate a first media session; and

sending to a Software Defined Network (SDN) controller session identification information identifying a first Real-time Transport Control Protocol (RTCP) packet stream corresponding to the first media session and causing said SDN controller to control a first open flow switch to establish an entry in a table to cause the first open flow switch to send a copy of the RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

24. A communications method, the method comprising:

receiving, by a session border controller (SBC), a session initiation signal used to initiate a first media session; and

sending, by the SBC to a Software Defined Network (SDN) controller, session identification information identifying a first Real-time Transport Control Protocol (RTCP) packet stream corresponding to the first media session and causing said SDN controller to control a first open flow switch to establish a flow entry in a flow table to match a group identifier (ID) maintained in a group table to cause the first open flow switch to send a copy of RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

25. The communications method of claim 24 , further comprising:

generating, by the SDN controller, a group entry in the group table, said group entry in the group table is identified by said group ID and includes RTCP packet stream identification information identifying the first RTCP packet stream and an address of the SBC to which the copy of the RTCP packets corresponding to the first RTCP packet stream are to be forwarded.

26. A communications method, the method comprising:

receiving, by a session border controller (SBC), a session initiation signal used to initiate a first media session; and

sending, by the SBC to a Software Defined Network (SDN) controller, session identification information identifying a first Real-time Transport Control Protocol (RTCP) packet stream corresponding to the first media session and causing said SDN controller to control a first programmable switch to establish an entry in a table to cause the first programmable switch to send a copy of RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

27. The communications method of claim 26 ,

wherein said entry in said table includes instructions for generating the copy of the RTCP packets and sending the copy of RTCP packets corresponding to the first RTCP packet stream to the SBC while also communicating the RTCP packets corresponding to the first RTCP packet stream towards an intended first RTCP packet stream destination.

Assignments (12)
SHORT-FORM PATENTS SECURITY AGREEMENT Recorded Sep 5, 2024
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 068857/0290 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
TERMINATION AND RELEASE OF FIRST SUPPLEMENT OT PATENT SECURITY AGREEMENT AT R/F 049035/0939 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058740/0265 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
CORRECTIVE ASSIGNMENT TO CORRECT THE SCHEDULE PREVIOUSLY RECORDED ON REEL 049035 FRAME 0939. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST SUPPLEMENT TO PATENT SECURITY AGREEMENT. Recorded Aug 22, 2019
From: GENBAND US LLC; RIBBON COMMUNICATIONS OPERATING COMPANY, INC., FORMERLY KNOWN AS SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 050705/0001 →
FIRST SUPPLEMENT TO SECURITY AGREEMENT Recorded Apr 30, 2019
From: GENBAND US LLC; RIBBON COMMUNICATIONS OPERATING COMPANY, INC., FORMERLY KNOWN AS SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 049035/0939 →
CHANGE OF NAME Recorded Jan 16, 2019
From: SONUS NETWORKS, INC.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 048078/0036 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
CHANGE OF NAME Recorded Dec 24, 2017
From: SONUS, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 044957/0213 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 19, 2017
From: SHARMA, ASHISH; BOLLAPALLI, NAGESH KUMAR
To: SONUS, INC.
Reel/Frame 044483/0855 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 19, 2017
From: GAHLAUT, SIDDHARTH
To: SONUS, INC.
Reel/Frame 044169/0622 →