IP Library Granted Patent US 10,778,731
Granted Patent B2
US 10,778,731 · App. 16/147,829 · Granted Sep 15, 2020

Communications methods, apparatus and systems for conserving media resource function resources

Inventors: Ashish Sharma (Bangalore, IN); Nagesh Kumar Bollapalli (Bangalore, IN)
Assignee: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
H04L65/1069H04L45/22H04L65/1006H04L65/1026H04L65/605
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,778,731
App. No.
16/147,829
Granted
Sep 15, 2020
Kind
B2
Abstract

Communications methods, apparatus and systems for conserving Media Resource Function (MRF) resources by identifying streams of sessions, for example, non-real time streams, which can be routed to avoid use of MRF resources. An exemplary embodiment includes receiving by a SBC a session initiation request from a first device directed to a second device for a session including a plurality of streams; establishing a plurality of routes to the second device, said routes including at least a first route and a second route, the first route not including a media content processing entity and the second route including a media content processing entity; identifying from the streams for the session a first set of streams; said first set of streams including one or more streams that do not require media content processing; and routing one or more of the streams of the first set of streams via the first route.

Claims (50)

1. A communications method comprising:

receiving, by a first Session Border Controller (SBC), a first session initiation request from a first device directed to a second device for a session including a plurality of streams, said first session initiation request including information describing the plurality of streams included in the session;

determining, by the first SBC, from the plurality of streams for the session a first set of streams, said first set of streams including one or more streams that do not require media content processing, said determining the first set of streams being based on the information describing the plurality of streams included in the session;

establishing, by the first SBC, a plurality of routes to the second device, said plurality of routes including at least a first route and a second route, the first route not including a media content processing entity and the second route including a media content processing entity that performs transcoding, transrating or transizing on media content, said first and said second routes both including said first SBC and a second SBC; and

routing, by the first SBC, one or more of the streams of the first set of streams of the session to the second device via the first route.

2. The communications method of claim 1 further including routing via the second route, by the first SBC, the streams of the plurality of streams that are not routed to the second device via the first route.

3. The communications method of claim 2 further including:

identifying which of the streams of the plurality of streams included in the session are non-real time application streams; and

wherein said determining from the plurality of streams for the session the first set of streams includes determining that the identified non-real time application streams are streams of said first set of streams.

4. The communications method of claim 3 , wherein said identifying which of the streams of the plurality of streams included in the session are non-real time application streams is based on at least one of a media type, a transport protocol type, or a format type of the stream.

5. The communications method of claim 4 ,

wherein said establishing a plurality of routes to the second device includes sending, from the first SBC to the second SBC without traversing the media content processing entity, a Session Initiation Protocol (SIP) Options request including information corresponding to the streams from the session to be routed via the first route, said information including a call leg session identifier.

6. The communications method of claim 5 , wherein establishing a plurality of routes to the second device further includes:

receiving, at the second SBC, the SIP Options request from the first SBC;

receiving, at the second SBC, a session initiation request from the media content processing entity, said session initiation request including said call leg session identifier and information on the second set of streams;

generating, at the second SBC, a second session initiation request based on the SIP Options request received from the first SBC and the session initiation request received from the media content processing entity, the second session initiation request including information on streams to be routed via the first route and the second route; and

sending from the second SBC the second session initiation request to the second device.

7. The communications method of claim 2 further including determining which of the streams of the plurality of streams included in the session are real-time streams and excluding those streams from the first set of streams.

8. The communications method of claim 2 further including:

identifying which of the streams of the plurality of streams included in the session are Message Session Relay Protocol streams, Binary Floor Control Protocol streams, Far End Camera Control protocol streams and webRTC data challenge streams; and

wherein said determining from the plurality of streams for the session the first set of streams includes determining that the identified Message Session Relay Protocol streams, Binary Floor Control Protocol streams, Far End Camera Control protocol streams and webRTC data challenge streams are streams of said first set of streams.

9. The communications method of claim 1 , wherein the media content processing entity is a Media Resource Function apparatus operating in back-to-back user agent mode.

10. The communications method of claim 9 , wherein the Media Resource Function apparatus does not support processing or pass through of non-real time protocol streams.

11. A communications system comprising:

a first Session Border Controller, said first Session Border Controller (SBC) including one or more processors configured to operate the first SBC to perform the following operations:

receive a first session initiation request from a first device directed to a second device for a session including a plurality of streams, said first session initiation request including information describing the plurality of streams included in the session;

determine from the plurality of streams for the session a first set of streams, said first set of streams including one or more streams that do not require media content processing, said determining the first set of streams being based on the information describing the plurality of streams included in the session;

establish a plurality of routes to the second device, said plurality of routes including at least a first route and a second route, the first route not including a media content processing entity and the second route including a media content processing entity that performs transcoding, transrating or transizing on media content, said first and said second routes both including said first SBC and a second SBC; and

route one or more of the streams of the first set of streams of the session to the second device via the first route.

12. The communications system of claim 11 , wherein said one or more processors is further configured to operate said first SBC to route via the second route the streams of the plurality of streams that are not routed to the second device via the first route, and

wherein said first SBC is a single device that receives the plurality of streams included in the session from the first device.

13. The communications system of claim 12 ,

wherein said one or more processors included in the first SBC are further configured to operate the first SBC to perform the following operation:

identify which of the streams of the plurality of streams included in the session are non-real time application streams; and

wherein said operation to determine from the plurality of streams for the session the first set of streams includes determining that the identified non-real time application streams are streams of said first set of streams.

14. The communications system of claim 13 , wherein said operation to identify which of the streams of the plurality of streams included in the session are non-real time application streams is based on at least one of a media type, a transport protocol type, or a format type of the stream.

15. The communications system of claim 14 ,

wherein said operation to establish a plurality of routes to the second device further includes:

sending, from the first SBC to the second SBC without traversing the media content processing entity, a Session Initiation Protocol (SIP) Options request including information corresponding to the streams from the session to be routed via the first route, said information including a call leg session identifier.

16. The communications system of claim 12 , wherein said operation to determine from the plurality of streams for the session a first set of streams includes identifying which of the streams of the plurality of streams included in the session are real-time streams and excluding those streams from the first set of streams.

17. The communications system of claim 12 ,

wherein said one or more processors included in the first SBC are further configured to operate the first SBC to identify which of the streams of the plurality of streams included in the session are Message Session Relay Protocol streams, Binary Floor Control Protocol streams, Far End Camera Control protocol streams and webRTC data challenge streams; and

wherein said operation to determine from the plurality of streams for the session the first set of streams includes determining that the identified Message Session Relay Protocol streams, Binary Floor Control Protocol streams, Far End Camera Control protocol streams and webRTC data challenge streams are streams of said first set of streams.

18. The communications system of claim 11 , wherein the media content processing entity is a Media Resource Function apparatus operating in back-to-back user agent mode.

19. The communications system of claim 18 , wherein the Media Resource Function apparatus does not support processing or pass through of non-real time protocol streams.

20. A non-transitory computer readable medium having machine executable instructions stored thereon for controlling one or more processors in a first session border controller that operate the first session border controller (SBC), the non-transitory computer readable medium including:

code for controlling said one or more processors to operate the first SBC to receive a first session initiation request from a first device directed to a second device for a session including a plurality of streams, said first session initiation request including information describing the plurality of streams included in the session;

code for controlling the one or more processors to operate the first SBC to determine from the plurality of streams for the session a first set of streams, said first set of streams including one or more streams that do not require media content processing, said determining the first set of streams being based on the information describing the plurality of streams included in the session;

code for controlling the one or more processors to operate the first SBC to establish a plurality of routes to the second device, said plurality of routes including at least a first route and a second route, the first route not including a media content processing entity and the second route including a media content processing entity that performs transcoding, transrating or transizing on media content, said first and said second routes both including said first SBC and a second SBC; and

code for controlling the one or more processors to operate the first SBC to route one or more of the streams of the first set of streams of the session to the second device via the first route.

Assignments (11)
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 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 →
MERGER AND CHANGE OF NAME Recorded Sep 30, 2018
From: SOLSTICE SAPPHIRE, INC.; SONUS NETWORKS, INC.; SONUS NETWORKS, INC.
To: SONUS, INC.
Reel/Frame 047014/0359 →
CHANGE OF NAME Recorded Sep 30, 2018
From: SONUS, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 047167/0314 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2018
From: SHARMA, ASHISH
To: SONUS NETWORKS, INC.
Reel/Frame 047167/0336 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2018
From: BOLLAPALLI, NAGESH KUMAR
To: SONUS NETWORKS, INC.
Reel/Frame 047014/0353 →