The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Dec. 28, 2010
Filed:
Aug. 28, 2006
Kaushik P. Biswas, San Jose, CA (US);
Vinay Jayant Pande, San Jose, CA (US);
Jayesh Chokshi, Cupertino, CA (US);
Siva S. Jayasenan, Cupertino, CA (US);
Vikas Butaney, Los Altos, CA (US);
Kaushik P. Biswas, San Jose, CA (US);
Vinay Jayant Pande, San Jose, CA (US);
Jayesh Chokshi, Cupertino, CA (US);
Siva S. Jayasenan, Cupertino, CA (US);
Vikas Butaney, Los Altos, CA (US);
Cisco Technology, Inc., San Jose, CA (US);
Abstract
Disclosed are apparatus and methods for managing session data in a session border controller (SBC), where the session data is sent from a first node, such as a first phone, to a second node, such as a registrar or second phone. In general, embodiments of the present invention support SBC functionality by managing sessions through the SBC without implementing a terminate and regenerate of the sessions, but rather by intercepting packets destined to the second node and efficiently handling such functionality in the forwarding-path. Also in deployments where the endnodes require NAT (network address translation), mechanisms are provided in the SBC to perform NAT on the addresses embedded in the payload of the session data. In other aspects, mechanisms for keeping the sessions or NAT entries alive are facilitated at the SBC, even when an endnode has a expiration time that differs an expiration time of another device, such as a registar device. Other embodiments allow the actual media packets to flow through the SBC (e.g., for security, accounting, etc) while allowing two endnodes to utilize a same private address or domain.