Abstract: A system performs threat protection for real-time communications (“RTC”). The system receives, by a signaling engine of a gateway, a request of a client according to a protocol, where the request has successfully traversed one or more security devices between the client and the gateway. The system determines, by a protocol handler corresponding to the protocol, whether the request includes a threat. When the request includes the threat, the system indicates the threat to the one or more security devices, and when the request does not include the threat, the system sends the request to an application server at the gateway.

Abstract: A method for retrieving data from a telecommunications network includes receiving a request at a view for the subscriber data from a telecommunications application, where the subscriber data resides on multiple data sources. The method includes sending the request to each data source coupled to the view and receiving the subscriber data from the data sources coupled to the view. The method further includes merging the subscriber data into a single data record and returning the merged data record to the telecommunications application.

Abstract: A system provides a media relay for real-time communications (“RTC”). The system receives, by a signaling server, a first signaling message from a first client including one or more first candidate transport addresses of the first client. The system generates a modified first signaling message by inserting a transport address of a relay server into the first signaling message, and transmits the modified first signaling message to a second client. Then, the system receives a second signaling message from the second client including one or more second candidate transport addresses of the second client. The system generates a modified second signaling message by inserting the transport address of the relay server into the second signaling message, and transmits the modified second signaling message to the first client.

Abstract: A system performs client wake up for real-time communications (“RTC”). The system closes a connection between a gateway and an RTC application of a device. The RTC application enters a sleeping mode when the connection to the gateway is closed. After closing the connection, the system receives a message intended for the RTC application. The system requests a push notification server to wake up the RTC application, reconnects the gateway with the RTC application, and delivers the message to the RTC application.

Abstract: A system performs threat protection for real-time communications (“RTC”). The system receives, by a signaling engine of a gateway, a request of a client according to a protocol, where the request has successfully traversed one or more security devices between the client and the gateway. The system determines, by a protocol handler corresponding to the protocol, whether the request includes a threat.

Abstract: A system provides a media relay for real-time communications (“RTC”). The system receives, by a signaling server, a first signaling message from a first client including one or more first candidate transport addresses of the first client. The system generates a modified first signaling message by inserting a transport address of a relay server into the first signaling message, and transmits the modified first signaling message to a second client. Then, the system receives a second signaling message from the second client including one or more second candidate transport addresses of the second client. The system generates a modified second signaling message by inserting the transport address of the relay server into the second signaling message, and transmits the modified second signaling message to the first client.

Abstract: A method for retrieving data from a telecommunications network includes receiving a request at a view for the subscriber data from a telecommunications application, where the subscriber data resides on multiple data sources. The method includes sending the request to each data source coupled to the view and receiving the subscriber data from the data sources coupled to the view. The method further includes merging the subscriber data into a single data record and returning the merged data record to the telecommunications application.

Abstract: A system performs client wake up for real-time communications (“RTC”). The system closes a connection between a gateway and an RTC application of a device. The RTC application enters a sleeping mode when the connection to the gateway is closed. After closing the connection, the system receives a message intended for the RTC application. The system requests a push notification server to wake up the RTC application, reconnects the gateway with the RTC application, and delivers the message to the RTC application.

Abstract: A system performs authentication for real-time communications (RTC). The system receives a request from a browser application for web authentication of a user. The system then performs the web authentication by a security provider by reaching a first resource, where the security provider determines a security principal for the user. Subsequently, the system executes a security Groovy script to obtain an identity mapping from a second resource different than the first resource, where the identity mapping maps the security principal to an Internet Protocol (IP) Multimedia Subsystem (IMS) identity. The system then provides the identity mapping to a runtime Groovy script.

Abstract: A system performs authentication for real-time communications (RTC). The system receives a request from a browser application for web authentication of a user. The system then performs the web authentication by a security provider by reaching a first resource, where the security provider determines a security principal for the user. Subsequently, the system executes a security Groovy script to obtain an identity mapping from a second resource different than the first resource, where the identity mapping maps the security principal to an Internet Protocol (IP) Multimedia Subsystem (IMS) identity. The system then provides the identity mapping to a runtime Groovy script.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for controlling access to telecommunications resources implementing a legacy protocol based upon a policy. These mechanisms and methods for controlling access to legacy protocols based upon a policy can enable embodiments to control access by third party created and other applications to network resources implementing legacy telecommunications protocols. The ability of embodiments to control access by third party created and other applications to network resources can enable network providers to provide greater access to network resources without compromising security of other users. Embodiments may further provide the ability to interface with legacy push protocols, multimedia message protocols and short message peer-to-peer protocols.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for controlling access to telecommunications resources implementing a legacy protocol based upon a policy. These mechanisms and methods for controlling access to legacy protocols based upon a policy can enable embodiments to control access by third party created and other applications to network resources implementing legacy telecommunications protocols. The ability of embodiments to control access by third party created and other applications to network resources can enable network providers to provide greater access to network resources without compromising security of other users. Embodiments may further provide the ability to interface with legacy push protocols, multimedia message protocols and short message peer-to-peer protocols.

Abstract: A network gateway application is described that provides throttling, prioritization and traffic shaping for incoming requests from client applications. A request is received by a plug-in manager component of the gateway application. The plug-in manager can then invoke the budget service in order to determine a current available budget for the request. The budget can be computed according to a service level agreement for the service provider, application or network node. The requests can be of high or low priority. If the budget is greater than a specified priority threshold value, the low priority requests can be denied, while the high priority requests can be processed as long as there is some available budget left. If the budget for the request has reached the restricted level, the request can be denied and optionally enqueued to a traffic shaping queue to be processed at a later time.

Abstract: A network gateway application is described that provides throttling, prioritization and traffic shaping for incoming requests from client applications. A request is received by a plug-in manager component of the gateway application. The plug-in manager can then invoke the budget service in order to determine a current available budget for the request. The budget can be computed according to a service level agreement for the service provider, application or network node. The requests can be of high or low priority. If the budget is greater than a specified priority threshold value, the low priority requests can be denied, while the high priority requests can be processed as long as there is some available budget left. If the budget for the request has reached the restricted level, the request can be denied and optionally enqueued to a traffic shaping queue to be processed at a later time.