US10171532B2 - Methods and systems for detection and classification of multimedia content in secured transactions - Google Patents
Methods and systems for detection and classification of multimedia content in secured transactions Download PDFInfo
- Publication number
- US10171532B2 US10171532B2 US14/503,274 US201414503274A US10171532B2 US 10171532 B2 US10171532 B2 US 10171532B2 US 201414503274 A US201414503274 A US 201414503274A US 10171532 B2 US10171532 B2 US 10171532B2
- Authority
- US
- United States
- Prior art keywords
- multimedia
- server
- multimedia content
- transactions
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/752—Media network packet handling adapting media to network capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- H04L65/1006—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H04L65/605—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/765—Media network packet handling intermediate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H04L67/32—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- Traffic Management is a broad concept and includes techniques such as throttling of low priority traffic, blocking or time shifting certain types of traffic, and traffic optimization. Optimization of web and video traffic is a key component in the array of traffic management techniques used by wireless operators. Web traffic refers to traditional web site browsing, and video traffic refers to watching videos over the Internet—between the two, web and video traffic account for more than 80% of the data traffic in typical cellular wireless networks.
- FIG. 1 is a block diagram of an exemplary network system, consistent with embodiments of the present disclosure.
- FIG. 2 is a block diagram illustrating an embodiment of an exemplary multimedia detector and classifier, consistent with embodiments of the present disclosure.
- FIG. 3 is a diagram of an exemplary message flow between a client and a server, consistent with embodiments of the present disclosure.
- FIG. 4A is a block diagram illustrating exemplary client requests, consistent with embodiments of the present disclosure.
- FIG. 4B is a block diagram illustrating an exemplary multimedia session, consistent with embodiments of the present disclosure.
- FIG. 5 is a flowchart representing an exemplary method for detecting presence of multimedia content data in secured transactions, consistent with embodiments of the present disclosure.
- FIG. 6 is a flowchart representing an exemplary method for determining a domain name requested by a specific terminal based on the one or more handshake messages, consistent with embodiments of the present disclosure.
- FIG. 7 is a flowchart representing an exemplary method for classifying multimedia content in a plurality of transactions, consistent with embodiments of the present disclosure.
- Network congestion or overload conditions in networks are often localized both in time and space and affect only a small set of users at any given time. This can be caused by the topology of communication systems.
- the system can have a tree-like topology, with a router or a gateway being the root of the tree and the mobile base stations being the leaves.
- This tree-like topology is similar across cellular technologies including Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS) adopting Wideband Code Division Multiple Access (W-CDMA) radio access technology, CDMA2000, Worldwide Interoperability for Microwave Access (WiMax) and Long Term Evolution (LTE).
- GSM Global System for Mobile Communication
- UMTS Universal Mobile Telecommunications System
- W-CDMA Wideband Code Division Multiple Access
- CDMA2000 Code Division Multiple Access
- WiMax Worldwide Interoperability for Microwave Access
- LTE Long Term Evolution
- the impact of network overload conditions depends on the level of aggregation in the network where that overload condition occurs. For example, an overload condition at a base station level affects only those users who are connected to that base station. Therefore, in some embodiments, the adaptive traffic management identifies the aggregation level at which an overload condition occurs and then applies traffic management techniques in a holistic fashion across only those users that are affected by the overload condition.
- Adaptive traffic management is an approach wherein traffic management techniques such as web and video optimization can be applied selectively based on monitoring key indicators that have an impact on the Quality of Experience (QoE) of users or subscribers. Applying optimization can involve detecting the presence of multimedia content in secured or unsecured transactions and classifying multimedia content in the transactions.
- a subscriber can be a mobile terminal user who subscribes to a wireless or cellular network service. While the subscriber refers to the mobile terminal user here, future references to subscriber can also refer to a terminal that is used by the subscriber, or refer to a client device used by the subscriber.
- FIG. 1 is a block diagram of an exemplary network system.
- Exemplary communication system 100 can be any type of system that transmits data packets over a network.
- the exemplary communication system 100 can include one or more networks transmitting data packets across wired or wireless networks to terminals (terminals not shown in FIG. 1 ).
- the exemplary communication system 100 can have network architectures of, for example, a GSM network, a UMTS network that adopts Wideband Code Division Multiple Access (W-CDMA) radio access technology, a CDMA2000 network, and a WiMax network.
- GSM Global System for Mobile communications
- UMTS that adopts Wideband Code Division Multiple Access
- CDMA2000 Code Division Multiple Access
- WiMax Worldwide Interoperability for Microwave Access
- the exemplary communication system 100 can include, among other things, one or more networks 101 , 102 , 103 (A-D), one or more controllers 104 (A-D), one or more serving nodes 105 (A-B), one or more base stations 106 (A-D)- 109 (A-D), a router 110 , a gateway 120 , and one or more adaptive traffic managers 130 (A-C).
- the network topology of the exemplary communication system 100 can have a tree-like topology with gateway 120 being the tree's root node and base stations 106 - 109 being the leaves.
- Router 110 is a device that is capable of forwarding data packets between networks, creating an overlay internetwork. Router 110 can be connected to two or more data lines from different networks. When a data packet comes in on one of the lines, router 110 can determine the ultimate destination of the data packet and direct the packet to the next network on its journey. In other words, router 110 can perform “traffic directing” functions. In the exemplary embodiment shown in FIG. 1 , router 110 communicates with network 102 and gateway 120 . Router 110 directs traffic from the network 102 to the gateway 120 and vice versa.
- Network 101 can be any combination of radio network, wide area networks (WANs), local area networks (LANs), or wireless networks suitable for packet-type communications, such as Internet communications.
- network 101 can be a General Packet Radio Service (GPRS) core network, which provides mobility management, session management and transport for Internet Protocol packet services in GSM and W-CDMA networks.
- GPRS General Packet Radio Service
- the exemplary network 101 can include, among other things, a gateway 120 , and one or more serving nodes 105 (A-B).
- Gateway 120 is a device that converts formatted data provided in one type of network to a particular format required for another type of network.
- Gateway 120 may be a server, a router, a firewall server, a host, or a proxy server.
- Gateway 120 has the ability to transform the signals received from router 110 into a signal that network 101 can understand and vice versa.
- Gateway 120 may be capable of processing webpage, image, audio, video, and T.120 transmissions alone or in any combination, and is capable of full duplex media translations.
- gateway 120 can be a Gateway GPRS Support Node (GGSN) that supports interworking between the GPRS network and external packet switched networks, like the Internet and X.25 networks.
- GGSN Gateway GPRS Support Node
- Serving nodes 105 are devices that deliver data packets from gateway 120 to a corresponding network 103 within its geographical service area and vice versa.
- a serving node 105 can be a server, a router, a firewall server, a host, or a proxy server.
- a serving node 105 can also have functions including packet routing and transfer, mobility management (attach/detach and location management), logical link management, network accessing mediation and authentication, and charging functions.
- a serving node 105 can be a Serving GPRS Support Node (SGSN).
- SGSN Serving GPRS Support Node
- SGSN can have location register, which stores location information, e.g., current cell, current visitor location (VLR) and user profiles, e.g., International Mobile Subscriber Identity (IMSI), and addresses used in the packet data network, of all GPRS users registered with this SGSN.
- location information e.g., current cell, current visitor location (VLR) and user profiles, e.g., International Mobile Subscriber Identity (IMSI), and addresses used in the packet data network, of all GPRS users registered with this SGSN.
- VLR current visitor location
- IMSI International Mobile Subscriber Identity
- Network 102 can include any combination of wide area networks (WANs), local area networks (LANs), or wireless networks suitable for packet-type communications.
- network 102 can be, for example, Internet and X.25 networks.
- Network 102 can communicate data packet with network 101 with or without router 110 .
- Networks 103 can include any radio transceiver networks within a GSM or UMTS network or any other wireless networks suitable for packet-type communications.
- the Radio Access Network (RAN) or Backhaul area of network 103 can have a ring topology.
- network 103 can be a RAN in a GSM system or a Backhaul area of a UMTS system.
- the exemplary network 103 can include, among other things, base stations 106 - 109 (e.g., base transceiver stations (BTSs) or Node-Bs), and one or more controllers 104 (A-C) (e.g., base-station controllers (BSCs) or radio network controllers (RNCs)).
- BTS/Node-B 106 - 109 communicate with BSC/RNC 104 (A-C), which are responsible for allocation of radio channels and handoffs as users move from one cell to another.
- the BSC/RNC 104 (A-C) in turn communicate to serving nodes 105 , which manage mobility of users as well as provide other functions such as mediating access to the network and charging.
- adaptive traffic manager 130 can be deployed at one or more locations within communication system 100 , including various locations within network 101 and 103 .
- adaptive traffic manager 130 can be located at gateway 120 , at controller 104 , at one or more base stations 106 - 109 , or any other locations.
- Adaptive traffic manager 130 can be either a standalone network element or can be integrated into existing network elements such as gateway 120 , controllers 104 , and base stations 106 - 109 .
- Adaptive traffic manager 130 can continuously monitor several parameters of communication system 100 . The parameters can be used to generate traffic management rules. The traffic management rules are generated dynamically and change in real-time based on the monitored parameters.
- adaptive traffic manager 130 can include a multimedia detector and classifier 220 (shown in FIG. 2 ) for detecting the presence of multimedia contents in secured or unsecured transactions and for classifying the multimedia content in secured or unsecured transactions. Multimedia detector and classifier 220 is described in more detail below.
- traffic management techniques can be implemented on a proxy device (e.g., adaptive traffic manager 130 ) that is located somewhere between a content server and client devices (e.g., mobile terminals).
- the proxy device can determine the type of content requested by a mobile terminal (e.g., video content) and apply optimization techniques.
- the content providers can transmit content using unsecured or secured communication protocols such as Hypertext Transfer Protocol Secure (HTTPS), Transport Layer Security (TLS), and Secure Sockets Layer (SSL) protocols.
- HTTPS Hypertext Transfer Protocol Secure
- TLS Transport Layer Security
- SSL Secure Sockets Layer
- the proxy device can determine the type of content being transmitted in both unsecured and secured transactions using client requests and server responses. In secured transactions, the client requests and server responses are encrypted and therefore may not be accessible by the proxy device.
- ABR protocols adaptive bit rate protocols
- HLS HTTP live streaming
- DASH dynamic adaptive streaming over HTTP
- smooth streaming examples of PD protocols
- FLV flash video file and Mpeg-4 (MP4) file downloads over HTTP.
- multiple quality levels e.g., video resolutions 1080p, 720p, etc.
- the multimedia quality level requested by the client device cannot be changed after the initial selection at the beginning of transmission.
- the multimedia quality level requested by the client device can be changed to reflect fluctuations in the available network bandwidth between the server and the client device. Therefore, ABR protocols typically provide a better user experience because the highest available quality level can be selected based on the available network bandwidth.
- SPC streaming policy control
- PD protocols or ABR protocols are used for the transmission.
- multimedia session reporting can also require distinguishing between PD protocols or ABR protocols.
- Streaming policy control can be any traffic management technique that manages data flow or controls congestion associated with streaming of multimedia data across a network, such as the Internet.
- SPC can allow streaming of the multimedia data to more effectively share bandwidths with other network traffics.
- SPC can also improves smoothness in streaming and provide decreased and more predictable latency.
- FIG. 2 is a block diagram illustrating an embodiment of an exemplary multimedia detector and classifier 220 .
- multimedia detector and classifier 220 can be integrated with adaptive traffic manager 130 .
- multimedia detector and classifier 220 can be integrated into other existing network elements such as gateway 120 , controllers 104 , and/or one or more base stations 106 - 109 .
- Multimedia detector and classifier 220 can also be a standalone network element located at gateway 120 , controller 104 , one or more base stations 106 - 109 , or any other proper locations.
- adaptive traffic manager 130 can include, among other things, a traffic processing and policy enforcement unit 222 and multimedia detector and classifier 220 .
- Adaptive traffic manager 130 can have one or more processors and at least one memory for storing program instructions.
- the processor(s) can be a single or multiple microprocessors, field programmable gate arrays (FPGAs), or digital signal processors (DSPs) capable of executing particular sets of instructions.
- Computer-readable instructions can be stored on a tangible non-transitory computer-readable medium, such as a flexible disk, a hard disk, a CD-ROM (compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital versatile disk-read only memory), a DVD RAM (digital versatile disk-random access memory), or a semiconductor memory.
- a tangible non-transitory computer-readable medium such as a flexible disk, a hard disk, a CD-ROM (compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital versatile disk-read only memory), a DVD RAM (digital versatile disk-random access memory), or a semiconductor memory.
- the methods can be implemented in hardware components or combinations of hardware and software such as, for example, ASICs or one or more computer.
- Adaptive traffic manager 130 can obtain external data 201 for processing.
- External data 201 can include network probes, Remote Authentication Dial-In User Service (RADIUS), Policy Charging and Rules Function (PCRF), and Subscriber Profile Repository (SPR).
- Adaptive traffic manager 130 can also communicate with one or more terminals (e.g., client 210 ) and server 260 , either directly or indirectly.
- terminals e.g., client 210
- server 260 either directly or indirectly.
- Traffic processing and policy enforcement (TPPE) unit 222 is a lower stack in the processing stack of adaptive traffic manager 130 .
- TPPE unit 222 can receive multimedia content, which can include video and/or web data, and provide the multimedia content to other elements and/or modules in adaptive traffic manager 130 .
- the multimedia content can be stored in a data storage device (e.g., data storage 234 ) that is local to or remote from adaptive traffic manager 130 .
- TPPE unit 222 is responsible for routing traffic between client 210 and the server 260 .
- TPPE unit 222 can also implement traffic management techniques including blocking, rate limiting, lossless and lossy data compression, and other traffic optimization techniques.
- TPPE unit 222 can be a software program and/or a hardware device.
- Multimedia detector and classifier 220 can include, among other things, a multimedia detector 224 , a transaction boundaries detector 226 , a multimedia session generator 228 , a multimedia classifier 230 , and a data storage 234 .
- Multimedia detector 224 can detect the presence of multimedia content in secured transactions, such as SSL/TLS transactions. In some embodiments, multimedia detector 224 can acquire one or more handshake messages associated with the secured transactions for transmitting multimedia content between client 210 and server 260 .
- a secured connection can include a plurality of secured transactions for transmitting multimedia content. For example, multimedia content (e.g., a video clip or session) can be transmitted over several HTTP transactions and can use one or more transmission control protocols (TCP) connections. After establishing the TCP connection, if the multimedia content are required to be encrypted, one or more secure tunnels between client 210 and server 260 can be established using SSL or TLS protocols. After the establishing of the secure tunnels, all transactions between client 210 and server 260 are encrypted and thus secured.
- TCP transmission control protocols
- FIG. 3 is a diagram of an exemplary message flow between a client device (e.g., client 210 ) and a server (e.g., server 260 ).
- client 210 can send a client hello message 302 when client 210 first connects to server 260 .
- client 210 can also send client hello message 302 in response to a hello request (not shown) or on its own initiative to renegotiate the security parameters in an existing connection.
- Client hello message 302 can include information such as the highest SSL or TLS protocol versions client 210 supports, application-layer protocol negotiation (ALPN) indicating a list of supported application protocols, next protocol negotiation extension (NPN) protocols, a random number, a list of suggested cipher suites for negotiating the security settings, a session identification (ID), and a server name indication (SNI).
- ALPN application-layer protocol negotiation
- NPN next protocol negotiation extension
- SNI server name indication
- Server hello message 304 can include the SSL or TLS protocol version that server 260 selects, a random number that is independently generated from the random number in client hello message 302 , a session ID corresponding to the session in the current connection, a cipher suite selected by server 260 , and selected ALPN and NPN protocols.
- Server 260 can also send a server certificate message 306 to client 210 .
- server 260 sends certificate message 306 if the agreed-upon key exchange method uses certificates for authentication.
- Server certificate message 306 can include one or more certificates, which can have certificate's public key.
- the certificate's public key can include a subject field identifying the entity (e.g., Google) associated with the public key stored in the subject public key field.
- a subject name associated with the entity can be identified in the subject field and/or the subject-alt-name (SAN) field.
- Server certificate message 306 can also include a common name field.
- a common name can be composed of host and domain names (e.g., www.youtube.com). In some embodiments, the common name can be the same as or similar to the web address that client 210 requests to access when establishing a secured connection.
- server 260 can also send a server key exchange message 308 .
- server 260 sends server key exchange message 308 if server certificate message 306 does not contain enough data to allow client 210 to exchange a premaster secret.
- Server key exchange message 308 can provide cryptographic information to allow client 210 to communicate the premaster secret (e.g., a Diffie-Hellman public key with which client 210 can complete a key exchange).
- server 260 can also send a certificate request message 310 to request a certificate from client 210 .
- server key exchange message 308 and certificate request message 310 are optional.
- server 260 After server 260 sends certificate request message 310 , it can send server hello done message 312 to client 210 , indicating the end of server hello message 304 and associated messages 306 - 310 . After sending server hello done message 312 , server 260 waits for a response from client 210 .
- client 210 can respond with client certificate message 314 , client key exchange message 316 , and certificate verify message 318 .
- Client 210 sends client certificate message 314 if server 260 requested a certificate, and provides the client certificate to server 260 .
- Client key exchange message 316 follows client certificate message 314 .
- the premaster secret can be established by direct transmission of the RSA-encrypted secret or by the transmission of Diffie-Hellman parameters that will allow each side to agree upon the same premaster secret.
- client 210 can also send certificate verify message 318 to provide explicit verification of a client certificate.
- certificate verify message 318 can be sent following a client certificate that has signing capability (e.g., all certificates except those containing fixed Diffie-Hellman parameters).
- client 210 sends message 314 - 318 , it sends client finished message 320 , indicating the end of client handshake messages.
- server 260 sends a server finished message, indicating the end of server handshake messages.
- multimedia detector 224 can acquire handshake messages 302 , 304 , and 306 or copies of handshake messages 302 , 304 , and 306 (together referred to as handshake messages 302 , 304 , and 306 ), and can determine a domain name requested by client 210 based on the acquired handshake messages.
- multimedia detector 224 can parse client hello message 302 .
- client hello message 302 can include information such as the highest SSL or TLS protocol version client 210 supports, application-layer protocol negotiation (ALPN) indicating a list of supported application protocols, next protocol negotiation extension (NPN) protocols, a random number, a list of suggested cipher suites, a session identification (ID), and a server name indication (SNI).
- APN application-layer protocol negotiation
- NPN next protocol negotiation extension
- SNI server name indication
- the SNI field provides an identification of the destination host requested by client 210 . Therefore, determining the availability of the SNI field can enable multimedia detector 224 to detect the presence of multimedia content in the secured transactions. Under the SSL or TLS protocol, including the SNI field in client hello message 302 can be optional. Therefore, if multimedia detector 224 determines that an SNI field is available, it can acquire a domain name (e.g., youtube.com) using the SNI field. Multimedia detector 224 can detect the presence of the multimedia content in the secured transactions based at least in part on the determined domain name. For example, if the domain name in the SNI field indicates the identification of the destination host is youtube.com, it is likely that the multimedia content (e.g., a YouTube video) is present in the secured transactions.
- a domain name e.g., youtube.com
- the SNI field can be used for detecting the presence of the multimedia content when multiple destination hosts share a common Internet Protocol (IP) address.
- IP Internet Protocol
- multiple virtual hosts or services can be executed on a shared physical computing infrastructure (e.g., a shared physical server).
- multimedia detector 224 can parse server certificate message 306 to determine whether a subject-alt-name (SAN) field is available in server certificate message 306 .
- SAN subject-alt-name
- the SAN field enables identifying of the entity (e.g., Google Inc.) associated with the public key.
- multimedia detector 224 can further determine whether the number of entries associated with the SAN field equals one. For example, multimedia detector 224 can determine that the SAN field has more than one entry, indicating multiple entities may be associated with the public key (e.g., subsidiaries or partners of Google Inc.). In some embodiments, if the number of entries associated with the SAN field is greater than one, multimedia detector 224 may not be able to determine the identity of the entity, and the associated domain name based on the SAN field entries. Multimedia detector 224 can thus provide, for example, a “null” signal, indicating the failure of detecting the presence of multimedia content in the secured transactions.
- multimedia detector 224 can acquire the domain name associated with the identity of the entity based on the SAN field, and therefore can detect the presence of the multimedia content in the secured transactions based at least in part on the determined domain name. In some embodiments, multimedia detector 224 may still detect the presence of the multimedia content even if the number of entries associated with the SAN field is greater than one. For example, if multimedia detector 224 determines that a substantial number of multiple entries in the SAN field identify entities supplying multimedia content, multimedia detector 224 can determine the domain names. Based on the determination of domain names, multimedia detector 224 can detect the presence of multimedia content. It is appreciated that multimedia detector 224 can detect the presence of multimedia content based on the entries in the SAN field in any desired manner.
- multimedia detector 224 can determine whether a common name field is available in server certificate message 306 .
- a common name can be composed of host and domain name (e.g., www.youtube.com).
- the common name can be the same as the web address that client 210 requests to access when establishing a secured connection. If multimedia detector 224 determines that a common name field is available, it can acquire the domain name based on the determined common name field.
- multimedia detector 224 may not be able to determine a domain name based on the common name field, and thus can provide, for example, a “null” signal, indicating the failure of detecting presence of multimedia content in one or more secured transactions.
- the detection of the presence of the multimedia content can be used for providing one or more traffic management optimization for the multimedia content data to client 210 . For example, if multimedia detector 224 detects that multimedia content is present in the secured transaction, additional network bandwidth can be allocated to client 210 .
- traffic management optimization can be applied to multiple client devices (e.g., multiple terminals within a same local area network), a subscriber, multiple subscribers, a specific client device, or a particular mobile application or applications installed on the specific client device (e.g., a YouTube application installed on a mobile terminal).
- the detection of the multimedia content can also be used for reporting the multimedia content. For example, the detection of the multimedia content can be used to report the presence of the multimedia content in a deep packet inspection (DPI) application.
- DPI deep packet inspection
- multimedia detector and classifier 220 can also classify the multimedia content in the secured or unsecured transactions.
- the protocols can be, for example, the progressive download (PD) protocols and the adaptive bit rate (ABR) protocols.
- ABR protocols differ from the PD protocols in several aspects, including, for example, the behavior at the beginning of the transmission of the multimedia content.
- client 210 under the ABR protocols, during the beginning of the transmission (e.g., a few seconds), client 210 can estimate the channel bandwidth and dynamically change the quality level of the multimedia content.
- client 210 can request to increase quality level (e.g., to 720p) in subsequent messages it sends to server 260 .
- client 210 can request to decrease the quality level (e.g., to 720p) in subsequent messages it sent to server 260 .
- the number of transactions (which can include client-requests and server responses) during the beginning period of transmitting the multimedia content can be greater than the number of transactions under the PD protocols.
- client 210 does not request to change the quality level and therefore the multimedia content is transmitted from server 260 using a single quality level.
- the number of transactions in the transmission under the PD protocols can be smaller (e.g., one transaction) than the number of transactions in the transmission under the ABR protocols.
- TPPE unit 222 can acquire one or more transactions between client 210 and server 260 .
- the one or more transactions can include one or more requests from client 210 and one or more corresponding responses from server 260 .
- Multimedia detector and classifier 220 can include transaction boundaries detector 226 .
- transaction boundaries detector 226 can detect transaction boundaries associated with the transactions.
- transaction boundaries detector 226 can be configured to initially treat the transactions as containing multimedia content and proceed to detect transaction boundaries.
- Transactions can include a plurality of client requests and corresponding server responses.
- a single TCP connection can carry one or more transactions such as HTTP transactions.
- Transaction boundaries detector 226 can detect the boundaries between adjacent client requests and adjacent server responses.
- FIG. 4A is a block diagram 420 illustrating an exemplary plurality of client request objects 422 A, 422 B, 422 C (collectively called client request objects 422 ) representing client requests.
- client request objects 422 To generate client request objects 422 , transaction boundaries detector 226 can acquire request data included in the one or more client requests and obtain one or more request times (e.g., t 0 , t 1 , t 2 , t 3 , . . . t n ) associated with acquiring the request data associated with the one or more client requests.
- Client request objects are also referred to as request objects.
- Server response objects are also referred to as response objects.
- transaction boundaries detector 226 can generate request objects representing the client requests and response objects representing the server response.
- the request object and the response object can be any record, pointer, or data structure stored on a hardware and/or software-based data storage device, for example, data storage 234 .
- the contents of the request and response objects can be stored as records or indexes in a single data structure or the contents of each request and response objects can be recorded in a separate transaction list data structure.
- transaction boundaries detector 226 can record the initial request time when the client request object is generated (e.g., t 0 or when the client request represented by client request object 422 A initiates).
- transaction boundaries detector 226 can acquire the first request data (e.g., via a client socket of adaptive traffic manager 130 ) and record the number of bytes of the first request data and a timestamp (e.g., at time t 1 ) indicating when the first request data is sent or acquired.
- transaction boundaries detector 226 can acquire these subsequent request data (e.g., via a client socket of adaptive traffic manager 130 ) and record the number of bytes in the subsequent request data and timestamps (e.g., at time t 2 , t 3 , . . . t n ) indicating when the subsequent request data is sent or acquired.
- transaction boundaries detector 226 can record the initial response time when the response object (not shown) is generated.
- transaction boundaries detector 226 can acquire the first response data (e.g., via a server socket of adaptive traffic manager 130 ) and record the number of bytes of the first response data and a timestamp indicating when the first response data is sent or acquired. If server 260 sends subsequent response data associated with the same server response, transaction boundaries detector 226 can acquire the subsequent response data (e.g., via server socket of adaptive traffic manager 130 ). Transaction boundaries detector 226 can record the number of bytes in the subsequent response data and timestamps indicating when the subsequent response data are sent or acquired.
- transaction boundaries detector 226 can determine the transaction boundaries based on the times associated with the acquiring of the request data and a transaction threshold idle time. In some embodiments, transaction boundaries detector 226 can make this determination based on a timer having a preconfigured transaction threshold idle time (e.g., 2 seconds). The timer can be restarted after adaptive traffic manager 130 receives, via a client socket, request data associated with the same client request.
- transaction boundaries detector 226 determines that client 210 has not sent any subsequent request data associated with the same client request for a time that is equal to or greater than the transaction threshold idle time, or that that client 210 has been idle for at least the transaction threshold idle time, transaction boundaries detector 226 can mark the corresponding client request object (e.g., client request object 422 A) as closed. If a request object is marked as closed, transaction boundaries detector 226 records the stop time (e.g., t n ) in the client request object and determines that the request portion of the current transaction has ended.
- client request object e.g., client request object 422 A
- transaction boundaries detector 226 determines that client 210 has been idle for at least the transaction threshold idle time (e.g., 2 seconds) after client 210 sends data at time t n , it can mark client request object 422 A as closed. If transaction boundaries detector 226 acquires any subsequent data from client 210 , it can associate the data with a new client request object 422 B.
- the transaction threshold idle time e.g. 2 seconds
- a transaction ends after the corresponding TCP connection is closed.
- TCP connection can be closed after additional messages are exchanged between client 210 and server 260 in a teardown sequence.
- a transaction ends after a subsequent client request is acquired by transaction boundaries detector 226 , indicating the beginning of a subsequent transaction.
- multimedia detector and classifier 220 can include multimedia session generator 228 .
- Multimedia session generator 228 can generate a multimedia session based on the detected transaction boundaries.
- a multimedia session can represent, for example, one or more single video clip, one or more episodes, one or more full-length movie, or any videos provided at a multimedia website (e.g., YouTube).
- client 210 can request multiple multimedia contents (e.g., two movies). If client 210 plays the multiple multimedia contents continuously in a period of time, the multiple multimedia contents can be represented in a single multimedia session.
- the multiple multimedia contents represented by a multimedia session can have idle time intervals between the consecutive multimedia contents (e.g., the time for switching from a first movie to an immediately subsequent movie).
- the idle time intervals can be less than a predefined session threshold idle time. For example, if the idle time interval between two consecutive videos is less than a session threshold idle time (e.g., thirty seconds), multimedia session generator 228 can determine that the two videos can be represented in one multimedia session.
- a session threshold idle time e.g. thirty seconds
- multimedia session generator 228 can generate a multimedia session object, which can represent a multimedia session.
- a multimedia session object can be any record, pointer, or data structure stored on a hardware and/or software-based data storage device, for example, data storage 234 .
- the contents of the multimedia session object can be stored as records or indexes in a single data structure or the contents of each multimedia session object can be recorded in a separate transaction list data structure.
- multimedia session generator 228 can associate the request objects and any corresponding response objects with the corresponding multimedia session object.
- a multimedia session object can be associated with one or more client request objects and more than one server-response object.
- FIG. 4B is a block diagram illustrating an exemplary multimedia session object 440 associated with multiple client request objects 442 A, 442 B, . . . 442 N, and multiple server response objects 444 A, 444 B, . . . 444 N.
- multimedia session generator 228 can associate the client request objects and any corresponding server response object with the corresponding multimedia session object. Therefore, the multimedia session object can provide an indication of a number of transactions for communicating the multimedia content associated with a multimedia session between client 210 and server 260 .
- the idle time interval between the consecutive multimedia contents is less than a predefined session threshold idle time. If the idle time interval between two consecutive multimedia contents (e.g., two adjacent videos) exceeds the session threshold idle time, multimedia session generator 228 can generate two multimedia sessions objects corresponding to the two consecutive multimedia contents. For example, if the idle time interval between two adjacent videos exceeds thirty seconds, multimedia session generator 228 can treat the two videos as two separate multimedia sessions and generated two corresponding multimedia session objects.
- one or more client request objects and/or one or more server response objects can be associated with a multimedia session object representing the multimedia session. For example, client request objects representing the client requests sent during a particular multimedia session and server response objects representing the server responses to those client requests can be associated with the multimedia session object corresponding to the particular multimedia session.
- multimedia session generator 228 can associate the multimedia session objects representing corresponding multimedia sessions with a look-up table.
- the look-up table can be searchable based on a client/source IP address, a server/destination IP address, or a concatenation of the client/source and server/destination IP addresses.
- Multimedia session generator 228 can also retrieve the multimedia session object from the look-up table before classifying the multimedia content in the corresponding multimedia session.
- multimedia detector and classifier 220 can also include a multimedia classifier 230 .
- multimedia classifier 230 can classify the multimedia content contained in a multimedia session as communicating under progressive download (PD) protocols or adaptive bit rate (ABR) protocols.
- PD progressive download
- ABR adaptive bit rate
- multimedia classifier 230 can retrieve a particular multimedia session object from a look-up table, and determine the number of client request objects and/or the number of server responses objects associated with the particular multimedia session.
- the number of client request/server response objects represents the number of client requests/server responses associated with the multimedia session.
- Multimedia classifier 230 can determine the relation of the number of client requests with respect to a threshold number of client-requests.
- multimedia classifier 230 can compare the number of client request objects (e.g., five) with a predefined threshold number (e.g., 1). If the number of client request objects for the multimedia session is greater than the predefined threshold number, multimedia classifier 230 can classify the multimedia content of the multimedia session object as communicating under ABR protocols. If the number of client requests is less than or equal to the predefined threshold number, multimedia classifier 230 can classify the multimedia content of the multimedia session object as communicating under PD protocols. It is appreciated that multimedia classifier 230 can also classify the multimedia content of the multimedia session object as being communicated under any other type of protocols.
- a predefined threshold number e.g., 1
- multimedia classifier 230 can classify the multimedia content in a multimedia session at a preconfigured time point after the multimedia session begins (e.g., at 10 seconds after the beginning of transmission).
- the preconfigured time period allows multimedia session generator to associate client requests and/or server responses with the multimedia session for a certain amount of time for classification purposes.
- a multimedia session may end before the preconfigured time period lapses. If, after the multimedia session ends, the number of client requests associated with the multimedia session is greater than the predefined threshold number of client requests, multimedia classifier 230 can classify the multimedia content of the multimedia session object as communicating under ABR protocols, or can indicate a failure to classify. If, after the multimedia session ends, the number of client requests is less than or equal to the predefined threshold number of client requests, multimedia classifier 230 may not be able to classify the multimedia content and can indicate a failure to classify.
- the classification of multimedia content can be used for applying one or more traffic management optimization techniques to the multimedia content to client 210 .
- TPPE unit 222 can enable or disable streaming policy control (SPC).
- SPC can be enabled at the beginning of transmitting a multimedia session, regardless of whether the multimedia content in the multimedia session is transmitted under ABR protocols or PD protocols. If, after a preconfigured period of time, multimedia detector and classifier 220 classifies the multimedia content as communicating under ABR protocols, SPC can be continually enabled. If, after the preconfigured period of time, multimedia detector and classifier 220 classifies the multimedia content as communicating under PD protocols, SPC can be disabled.
- SPC can be disabled at the beginning of transmitting a multimedia session, regardless of whether the multimedia content data is transmitted under ABR protocols or PD protocols. If, after a preconfigured period of time, multimedia detector and classifier 220 classifies the multimedia content as communicating under ABR protocols, SPC can be enabled. If, after a preconfigured period of time, multimedia detector and classifier 220 classifies the multimedia content as communicating under PD protocols, SPC can be continually disabled.
- TPPE unit 222 can apply traffic management optimization, such as SPC, to multiple clients, (e.g., multiple terminals within a same local area network), a subscriber, multiple subscribers, a specific terminal, or a particular mobile applications executing on the specific terminal.
- TPPE unit 222 can also apply SPC at the connection level. For example, if there are two connections, TPPE unit 222 can apply SPC separately to each individual connection. In some embodiments, TPPE unit 222 can apply SPC to an individual multimedia session.
- adaptive traffic manager 130 uses secured transactions and encrypted multimedia content data as examples, it is appreciated that the above description can also be applied to unsecured transactions and unencrypted multimedia content data.
- FIG. 5 is a flowchart representing an exemplary method 500 for detecting the presence of multimedia content data in secured transactions.
- Method 500 can be performed by an adaptive traffic manager (e.g., adaptive traffic manager 130 ).
- the adaptive traffic manager can acquire (step 504 ) one or more handshake messages associated with the secured transactions.
- the acquisition of the one or more handshake messages can be performed by a traffic processor (e.g., TPPE unit 222 ) of the adaptive traffic manager.
- the traffic processor is a lower stack in the processing stack of the adaptive traffic manager.
- the traffic processor can receive multimedia content, which can include video and/or web data, and provide the multimedia content to other elements and/or modules in the adaptive traffic manager.
- the multimedia content can be stored in a data storage device (e.g., data storage 234 ) that is local to or remote from the adaptive traffic manager.
- the traffic processor is responsible for routing traffic between the client (e.g., client 210 ) and the server (e.g., server 260 ).
- the traffic processor can also implement traffic management techniques including blocking, rate limiting, lossless and lossy data compression, and other traffic optimization techniques.
- the traffic processor can be a software program and/or a hardware device.
- the adaptive traffic manager can determine (step 506 ) a domain name requested by a specific terminal based on the one or more handshake messages.
- the determination of the domain name can be performed by a multimedia detector and classifier (e.g., the multimedia detector and classifier 220 ) of the adaptive traffic manager.
- a multimedia detector and classifier e.g., the multimedia detector and classifier 220
- An exemplary determination flowchart is further described in FIG. 6 (below).
- the adaptive traffic manager can also detect (step 508 ) the presence of the multimedia content data in the secured transactions based at least in part on the determined domain name.
- the detection step can be performed by the multimedia detector and classifier.
- the detection of the presence of the multimedia content can be used for providing one or more traffic management optimization for the multimedia content data to the client. For example, if the multimedia detector and classifier detects that multimedia content is present in the transaction, additional network bandwidth can be allocated to the client.
- traffic management optimization can be applied to multiple client devices (e.g., multiple terminals within a same local area network), a subscriber, multiple subscribers, a specific client device, or a particular mobile application or applications installed on the specific client device (e.g., a YouTube application installed on a mobile terminal).
- client devices e.g., multiple terminals within a same local area network
- subscriber e.g., multiple subscribers
- subscribers e.g., multiple subscribers
- a specific client device e.g., a particular mobile application or applications installed on the specific client device
- a particular mobile application or applications installed on the specific client device e.g., a YouTube application installed on a mobile terminal.
- method 500 can proceed to an end 510 .
- Method 500 can also be repeated any desired number of times for detecting the presence of multimedia content in one or more secured transactions.
- FIG. 6 is a flowchart representing an exemplary method 600 for determining a domain name requested by a specific terminal based on the one or more handshake messages.
- Method 600 can be performed by an adaptive traffic manager (e.g., adaptive traffic manager 130 ), and more particularly by a multimedia detector and classifier (e.g., the multimedia detector and classifier 220 ) of the adaptive traffic manager. While method 600 is described as being performed by the multimedia detector and classifier, it is appreciated that other components of adaptive traffic manager or other devices can be involved.
- the multimedia detector and classifier can parse (step 604 ) a client hello message.
- the client hello message can include information such as the highest SSL or TLS protocol version the client supports, ALPN indicating a list of supported application protocols, NPN protocols, a random number, a list of suggested cipher suites, a session ID, and a server name indication (SNI).
- the multimedia detector and classifier can determine (step 606 ) whether the SNI field is available based on the parsed fields in the client hello message.
- the SNI field provides an identification of the destination host requested by the client. Therefore, determining the availability of the SNI field can enable the multimedia detector and classifier to detect the presence of multimedia content in the secured transactions.
- the multimedia detector and classifier determines that an SNI field is available, it can acquire (step 608 ) a domain name (e.g., youtube.com) using the SNI field.
- the adaptive traffic manager can detect (step 508 ) the presence of the multimedia content in the secured transactions based at least in part on the determined domain name. For example, if the domain name in the SNI field indicates the identification of the destination host is youtube.com, it is likely that the multimedia content (e.g., a YouTube video) is present in the secured transactions.
- the SNI field can be used for detecting presence of the multimedia content when multiple destination hosts share a common IP address.
- multiple virtual hosts or services can be executed on a shared physical computing infrastructure (e.g., a shared physical server).
- the multimedia detector and classifier can parse (step 610 ) a server certificate message to determine (step 612 ) whether a subject-alt-name (SAN) field is available in the server certificate message.
- SAN subject-alt-name
- the SAN field can enable the identifying of the entity (e.g., Google Inc.) associated with the public key.
- the multimedia detector and classifier can further determine (step 614 ) whether the number of entries associated with the SAN field equals one. For example, the multimedia detector and classifier can determine that the SAN field has one or more entries, indicating multiple entities may be associated with the public key (e.g., subsidiaries or partners of a Google Inc.). In some embodiments, if the number of entries associated with the SAN field is greater than one, the multimedia detector and classifier may not be able to determine the identity of the entity, and the associated domain name based on the SAN field entries.
- the multimedia detector and classifier can thus provide (step 616 ), for example, a “null” signal, indicating the failure of detecting presence of multimedia content in the secured transactions. If the number of entries associated with the SAN field equals one, the multimedia detector and classifier can acquire (step 618 ) the domain name associated with the identity of the entity based on the SAN field, and therefore the adaptive traffic manager can detect (step 508 of FIG. 5 ) the presence of the multimedia content in the secured transactions based at least in part on the determined domain name. In some embodiments, the adaptive traffic manager may still detect the presence of the multimedia content even if the number of entries associated with the SAN field is greater than one.
- the multimedia detector and classifier of the adaptive traffic manager determines that a substantial number of multiple entries in the SAN field identify entities supplying multimedia content
- the multimedia detector and classifier can determine the domain names. Based on the determined domain names, the multimedia detector and classifier can detect the presence of multimedia content. It is appreciated that the multimedia detector and classifier can detect the presence of multimedia content based on the entries in the SAN field in any desired manner.
- the multimedia detector and classifier can determine (step 620 ) whether a common name field is available in the server certificate message.
- a common name can be composed of host and domain name (e.g., www.youtube.com). In some embodiments, the common name can be the same as the web address that the client requests to access when establishing a secured connection. If the multimedia detector and classifier determines that a common name field is available, it can acquire (step 622 ) the domain name based on the determined common name field.
- the multimedia detector and classifier may not be able to determine a domain name based on the common name field, and thus can provide (step 616 ), for example, a “null” signal, indicating the failure of detecting presence of multimedia content in one or more secured transactions.
- method 600 can proceed to an end 630 .
- Method 600 can also be repeated any desired number of times for detecting presence of multimedia content in one or more secured transactions.
- FIG. 7 is a flowchart representing an exemplary method 700 for classifying multimedia content in a plurality of secured transactions.
- Method 700 can be performed by an adaptive traffic manager (e.g., adaptive traffic manager 130 ), and more particularly by a multimedia detector and classifier (e.g., the multimedia detector and classifier 220 ) of the adaptive traffic manager. While method 700 is described as being performed by the multimedia detector and classifier, it is appreciated that other components of adaptive traffic manager or other devices can be involved.
- the adaptive traffic manager can acquire one or more transactions between a client device (e.g., client 210 ) and a server device (e.g., server 260 ).
- the one or more transactions can include one or more requests from the client and one or more corresponding responses from the server.
- the multimedia detector and classifier can detect (step 706 ) transaction boundaries associated with one or more transactions.
- the one or more transactions can include one or more client requests and one or more server responses.
- the multimedia detector and classifier can acquire request data included in the one or more client requests represented by client request objects, and obtain one or more request times associated with acquiring the request data included in the one or more client requests.
- the multimedia detector and classifier can generate request objects representing the client requests and response objects representing the server response.
- the request object and the response object can be any record, pointer, or data structure stored on a hardware and/or software-based data storage device (e.g, data storage 234 ).
- the contents of the request and response objects can be stored as records or indexes in a single data structure or the contents of each request and response objects can be recorded in a separate transaction list data structure.
- the multimedia detector and classifier can record the initial request time when the first client request object is generated.
- the multimedia detector and classifier can acquire the first request data and record the number of bytes of the first request data and a timestamp indicating when the first request data is sent or acquired. If the client sends subsequent request data associated with the same client request represented by the first client request object, the multimedia detector and classifier can acquire this subsequent request data and record the number of bytes in the subsequent request data and timestamps indicating when the subsequent request data is sent or acquired.
- the multimedia detector and classifier can record the initial response time when the response object is generated.
- the multimedia detector and classifier can acquire the first response data and record the number of bytes of the first response data and a timestamp indicating when the first response data is sent or acquired. If the server sends subsequent response data associated with the same server response, the multimedia detector and classifier can acquire the subsequent response data. The multimedia detector and classifier can record the number of bytes in the subsequent response data and timestamps indicating when the subsequent response data are sent or acquired.
- the multimedia detector and classifier can determine the transaction boundaries based on the times associated with the acquiring of the request data and a transaction threshold idle time.
- the multimedia detector and classifier can provide a timer having a preconfigured transaction threshold idle time (e.g., 2 seconds). The timer can be restarted after adaptive traffic manager 130 receives, via a client socket, request data associated with the same client request. If the multimedia detector and classifier determines that the client has not sent any subsequent request data associated with the same client request for a time that is equal to or greater than the transaction threshold idle time, or that that the client has been idle for at least the transaction threshold idle time, the multimedia detector and classifier can mark the first client request object as closed. If a client request object is marked as closed, the multimedia detector and classifier records the stop time in the client request object and determines that the request portion of the current transaction is ended.
- a preconfigured transaction threshold idle time e.g. 2 seconds
- a transaction ends after the corresponding TCP connection is closed.
- a TCP connection can be closed after additional messages are exchanged between the client and the server in a teardown sequence.
- a transaction ends after a subsequent client request is acquired by the multimedia detector and classifier, indicating the beginning of a subsequent transaction.
- the multimedia detector and classifier can generate (step 708 ) a multimedia session object based on the detected boundaries.
- the multimedia session object can provide an indication of the number of transactions for communicating the multimedia content associated with a multimedia session between the client and the server.
- the multimedia detector and classifier can generate a multimedia session object representing the multimedia session.
- the multimedia session object can be any record, pointer, or data structure stored on a hardware and/or software-based data storage device (e.g, data storage 234 ).
- the multimedia detector and classifier can associate the request objects and any corresponding response objects with the corresponding multimedia session object.
- a multimedia session object can be associated with more than one client request objects and more than one corresponding server-response objects. For example, if during a particular multimedia session, the multimedia detector and classifier generates a plurality of (e.g., five) client requests objects and a plurality of corresponding server response objects (e.g., five), the multimedia detector and classifier can associate the client requests objects and/or corresponding server response object with the corresponding multimedia session object. Therefore, the multimedia session, represented by the multimedia session object, can provide indication of the number of client requests and/or the number of corresponding server responses for communicating the multimedia content associated with the multimedia session.
- the idle time interval between the consecutive multimedia contents is less than a predefined session threshold idle time. If the idle time interval between two consecutive multimedia contents (e.g., two adjacent videos) exceeds the session threshold idle time, the multimedia detector and classifier can generate two multimedia sessions corresponding to the two consecutive multimedia contents. For example, if the idle time interval between two adjacent videos exceeds thirty seconds, the multimedia detector and classifier can treat the two videos as two separate multimedia sessions, and generate two multimedia session objects.
- the multimedia detector and classifier can associate the multimedia session objects representing corresponding multimedia sessions with a look-up table.
- the look-up table can be searchable based on a client/source IP address and/or a server/destination IP address, or a concatenation of the client/source and server/destination IP addresses.
- the multimedia detector and classifier can also retrieve the multimedia session object from the look-up table before classifying the multimedia content in the corresponding multimedia session.
- the multimedia detector and classifier can classify (step 710 ) the multimedia content based on the number of transactions indicated by the multimedia session object.
- the multimedia detector and classifier can classify the multimedia content contained in a multimedia session as communicating under progressive download (PD) protocols or adaptive bit rate (ABR) protocols.
- PD progressive download
- ABR adaptive bit rate
- the multimedia detector and classifier can retrieve a particular multimedia session object from a look-up table, and determine the number of client request objects and/or the number of corresponding server responses objects associated with the particular multimedia session.
- the number of client request/server response objects represents the number of client requests/server responses associated with the multimedia session.
- the multimedia detector and classifier can determine the relation of the number of client requests with respect to a threshold number of client requests.
- the multimedia detector and classifier can compare the number of client request objects (e.g., five) with a predefined threshold number (e.g., 1). If the number of client request objects is greater than the predefined threshold number, the multimedia detector and classifier can classify the multimedia content as communicating under ABR protocols. If the number of client requests is less than or equal to the predefined threshold number, the multimedia detector and classifier can classify the multimedia content as communicating under PD protocols. It is appreciated that the multimedia detector and classifier can also classify the multimedia content as communicating under any other type of protocols.
- the multimedia detector and classifier can classify the multimedia content in a multimedia session at a preconfigured time point after the multimedia session begins (e.g., at 10 seconds after the beginning of transmission).
- the preconfigured time period allows a multimedia session generator (e.g., multimedia session generator 228 ) to associate client requests and/or server responses with the multimedia session for a certain amount of time for classification purposes.
- a multimedia session may end before the preconfigured time period lapses. If, after the multimedia session ends, the number of client requests associated with the multimedia session is greater than the predefined threshold number of client requests, the multimedia detector and classifier can classify the multimedia content as communicating under ABR protocols, or can indicate a failure to classify. If, after the multimedia session ends, the number of client requests is less than or equal to the predefined threshold number of client requests, the multimedia detector and classifier may not be able to classify the multimedia content and can indicate a failure to classify.
- method 700 can proceed to an end 720 .
- Method 700 can also be repeated any desired number of times for designating any number of established associations as persisting associations.
- an element e.g., adaptive traffic manager or multimedia detector and classifier
- the processor(s) can be a single or multiple microprocessors, field programmable gate arrays (FPGAs), or digital signal processors (DSPs) capable of executing particular sets of instructions.
- FPGAs field programmable gate arrays
- DSPs digital signal processors
- Computer-readable instructions can be stored on a tangible non-transitory computer-readable medium, such as a flexible disk, a hard disk, a CD-ROM (compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital versatile disk-read only memory), a DVD RAM (digital versatile disk-random access memory), or a semiconductor memory.
- a tangible non-transitory computer-readable medium such as a flexible disk, a hard disk, a CD-ROM (compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital versatile disk-read only memory), a DVD RAM (digital versatile disk-random access memory), or a semiconductor memory.
- the methods can be implemented in hardware components or combinations of hardware and software such as, for example, ASICs and/or special purpose computers.
Abstract
Description
Claims (48)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/503,274 US10171532B2 (en) | 2014-09-30 | 2014-09-30 | Methods and systems for detection and classification of multimedia content in secured transactions |
PCT/US2015/053047 WO2016054116A1 (en) | 2014-09-30 | 2015-09-29 | Methods and systems for detection and classification of multimedia content in secured transactions |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/503,274 US10171532B2 (en) | 2014-09-30 | 2014-09-30 | Methods and systems for detection and classification of multimedia content in secured transactions |
Publications (2)
Publication Number | Publication Date |
---|---|
US20160094602A1 US20160094602A1 (en) | 2016-03-31 |
US10171532B2 true US10171532B2 (en) | 2019-01-01 |
Family
ID=54330876
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/503,274 Active 2035-09-08 US10171532B2 (en) | 2014-09-30 | 2014-09-30 | Methods and systems for detection and classification of multimedia content in secured transactions |
Country Status (2)
Country | Link |
---|---|
US (1) | US10171532B2 (en) |
WO (1) | WO2016054116A1 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10291589B1 (en) * | 2014-12-12 | 2019-05-14 | Amazon Technologies, Inc. | Session-based access control determinations |
US9787643B2 (en) * | 2015-01-30 | 2017-10-10 | Facebook, Inc. | Transport layer security latency mitigation |
US9756106B2 (en) | 2015-02-13 | 2017-09-05 | Citrix Systems, Inc. | Methods and systems for estimating quality of experience (QoE) parameters of secured transactions |
US10021221B2 (en) | 2015-02-24 | 2018-07-10 | Citrix Systems, Inc. | Methods and systems for detection and classification of multimedia content in secured transactions using pattern matching |
WO2018010959A1 (en) * | 2016-07-15 | 2018-01-18 | Deutsche Telekom Ag | Method for detecting and/or identifying data streams within a telecommunications network; system, telecommunications network, and content server entity for detecting and/or identifying data streams within a telecommunications network, program and computer program product |
EP3550771A4 (en) * | 2016-11-30 | 2019-12-18 | Nec Corporation | Communication device, communication method, and program |
US10545940B2 (en) * | 2017-02-22 | 2020-01-28 | Red Hat, Inc. | Supporting secure layer extensions for communication protocols |
US11132509B1 (en) * | 2018-12-03 | 2021-09-28 | Amazon Technologies, Inc. | Utilization of natural language understanding (NLU) models |
WO2024003583A1 (en) * | 2022-06-28 | 2024-01-04 | Citrix Systems,Inc | Optimizing selection of zero trust network access cloud edge nodes for internal application delivery |
Citations (79)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5870562A (en) * | 1997-03-24 | 1999-02-09 | Pfn, Inc. | Universal domain routing and publication control system |
US6026430A (en) * | 1997-03-24 | 2000-02-15 | Butman; Ronald A. | Dynamic client registry apparatus and method |
US20010032878A1 (en) * | 2000-02-09 | 2001-10-25 | Tsiounis Yiannis S. | Method and system for making anonymous electronic payments on the world wide web |
US20020033844A1 (en) * | 1998-10-01 | 2002-03-21 | Levy Kenneth L. | Content sensitive connected content |
US20020069278A1 (en) * | 2000-12-05 | 2002-06-06 | Forsloew Jan | Network-based mobile workgroup system |
US20030018753A1 (en) * | 2001-07-18 | 2003-01-23 | Ryuken Seki | Remote control proxy method and apparatus |
US20030032391A1 (en) * | 2001-08-09 | 2003-02-13 | Craig Schweinhart | Low latency handling of transmission control protocol messages in a broadband satellite communications system |
US20030081783A1 (en) * | 2001-10-23 | 2003-05-01 | Adusumilli Koteshwerrao S. | Selecting a security format conversion for wired and wireless devices |
US20030105630A1 (en) | 2001-11-30 | 2003-06-05 | Macginitie Andrew | Performance gauge for a distributed speech recognition system |
US20030174670A1 (en) * | 2002-03-14 | 2003-09-18 | Mar Jack K. | Packet-based mobile network |
US20040078573A1 (en) * | 2002-07-10 | 2004-04-22 | Shinako Matsuyama | Remote access system, remote access method, and remote access program |
US20040093419A1 (en) * | 2002-10-23 | 2004-05-13 | Weihl William E. | Method and system for secure content delivery |
US20040165603A1 (en) * | 2002-10-16 | 2004-08-26 | D'angelo Leo A. | Enhancing messaging services using translation gateways |
US20040210756A1 (en) * | 2003-04-15 | 2004-10-21 | Microsoft Corporation | Pass-thru for client authentication |
US20040255115A1 (en) * | 2000-06-27 | 2004-12-16 | Microsoft Corporation | Method and system for binding enhanced software features to a persona |
US20050097087A1 (en) * | 2003-11-03 | 2005-05-05 | Punaganti Venkata Murali K. | System and method for providing a unified framework for service discovery |
US20050273592A1 (en) | 2004-05-20 | 2005-12-08 | International Business Machines Corporation | System, method and program for protecting communication |
US20060031368A1 (en) * | 2004-06-16 | 2006-02-09 | Decone Ian D | Presence management in a push to talk system |
US20060106836A1 (en) * | 2002-06-07 | 2006-05-18 | Madoka Masugi | Data processing system, data processing device, data processing method, and computer program |
US7103008B2 (en) * | 2001-07-02 | 2006-09-05 | Conexant, Inc. | Communications system using rings architecture |
US20070073837A1 (en) * | 2005-05-24 | 2007-03-29 | Johnson-Mccormick David B | Online multimedia file distribution system and method |
US20070288621A1 (en) * | 2006-05-11 | 2007-12-13 | Veerabhadra Gundu | Methods for managing presence information in a real-time communications network |
US20080062863A1 (en) * | 2006-09-12 | 2008-03-13 | Qualcomm Incorporated | Transaction timeout handling in communication session management |
US20080222734A1 (en) * | 2000-11-13 | 2008-09-11 | Redlich Ron M | Security System with Extraction, Reconstruction and Secure Recovery and Storage of Data |
US20080294556A1 (en) * | 2007-05-24 | 2008-11-27 | Jim Anderson | Mobile commerce service |
US20090077383A1 (en) * | 2007-08-06 | 2009-03-19 | De Monseignat Bernard | System and method for authentication, data transfer, and protection against phishing |
US20090098886A1 (en) * | 2007-10-16 | 2009-04-16 | Nokia Corporation | System and method for providing presence notifications based upon watcher status |
US20090104954A1 (en) * | 2006-04-13 | 2009-04-23 | Igt | Methods and systems for tracking an event of an externally controlled interface |
US20090147772A1 (en) * | 2006-10-02 | 2009-06-11 | Prasad Rao | Systems and methods for providing presence information in communication |
US20090172129A1 (en) * | 2007-12-28 | 2009-07-02 | Cellspin Soft Inc. | Automatic Multimedia Upload For Publishing Data And Multimedia Content |
US20090241159A1 (en) * | 2008-03-18 | 2009-09-24 | Avaya Technology Llc | Open cable application platform set-top box (stb) personal profiles and communications applications |
US20090248494A1 (en) * | 2008-04-01 | 2009-10-01 | Certona Corporation | System and method for collecting and targeting visitor behavior |
US20090310805A1 (en) * | 2008-06-14 | 2009-12-17 | Michael Petroff | Hearing aid with anti-occlusion effect techniques and ultra-low frequency response |
US20100017218A1 (en) * | 2008-07-21 | 2010-01-21 | Uab "Ieec" | Business method for domain name and trade mark assigning and marketing |
US20100094984A1 (en) * | 2008-10-13 | 2010-04-15 | International Business Machines Corporation | Method for optmizing a presence enabled managed service |
US20100123727A1 (en) * | 2008-11-18 | 2010-05-20 | Kwa Seh W | Techniques to control self refresh display functionality |
US7792910B2 (en) * | 2005-08-31 | 2010-09-07 | Oki Data Corporation | Apparatus for sending image data by electronic mail |
US20100259386A1 (en) * | 2009-04-09 | 2010-10-14 | International Business Machines Corporation | System and methods for locating mobile devices using location and presence information |
US20110029985A1 (en) * | 2009-07-31 | 2011-02-03 | Nokia Corporation | Method and apparatus for coordinating resource access |
US20110082924A1 (en) | 2009-10-06 | 2011-04-07 | Openwave Systems Inc. | Managing network traffic by editing a manifest file |
US7933290B2 (en) * | 2004-03-30 | 2011-04-26 | Nokia Corporation | System and method for comprehensive service translation |
US20110113106A1 (en) * | 2008-01-28 | 2011-05-12 | Mikael Klein | Throttle on presence |
US20110119388A1 (en) * | 2009-11-16 | 2011-05-19 | International Business Machines Corporation | Optimization of Multimedia Service Over an IMS Network |
US20110243553A1 (en) * | 2010-03-31 | 2011-10-06 | Incnetworks, Inc. | Method, computer program, and algorithm for computing network service value pricing based on communication service experiences delivered to consumers and merchants over a smart multi-services (sms) communication network |
US20120017253A1 (en) * | 2010-07-15 | 2012-01-19 | At&T Intellectual Property I, L.P. | Apparatus and method for providing services using a services gateway |
US20120084423A1 (en) | 2010-10-04 | 2012-04-05 | Openwave Systems Inc. | Method and system for domain based dynamic traffic steering |
US20120179752A1 (en) * | 2010-09-10 | 2012-07-12 | Visible Technologies, Inc. | Systems and methods for consumer-generated media reputation management |
US8239266B1 (en) * | 2011-11-29 | 2012-08-07 | Google Inc. | Targeting based on intent or presence |
US8326920B1 (en) * | 2010-02-08 | 2012-12-04 | Google Inc. | Connection sharing |
US8327128B1 (en) * | 2011-07-28 | 2012-12-04 | Cloudflare, Inc. | Supporting secure sessions in a cloud-based proxy service |
US8392980B1 (en) * | 2008-08-22 | 2013-03-05 | Avaya Inc. | Trusted host list for TLS sessions |
US20130139164A1 (en) * | 2011-11-28 | 2013-05-30 | Sap Ag | Business Process Optimization |
US20130144785A1 (en) * | 2011-03-29 | 2013-06-06 | Igor Karpenko | Social network payment authentication apparatuses, methods and systems |
US20130198511A1 (en) | 2012-01-27 | 2013-08-01 | Microsoft Corporation | Implicit ssl certificate management without server name indication (sni) |
US20130203433A1 (en) * | 2012-02-03 | 2013-08-08 | Seven Networks, Inc. | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
US20130312054A1 (en) * | 2012-05-17 | 2013-11-21 | Cisco Technology, Inc. | Transport Layer Security Traffic Control Using Service Name Identification |
US8671069B2 (en) * | 2008-12-22 | 2014-03-11 | The Trustees Of Columbia University, In The City Of New York | Rapid image annotation via brain state decoding and visual pattern mining |
US20140115100A1 (en) * | 2011-01-31 | 2014-04-24 | Alcatel Lucent | Video packet scheduling method for multimedia streaming |
EP2725757A1 (en) | 2012-10-29 | 2014-04-30 | Alcatel Lucent | TLS protocol extension |
US8761363B2 (en) * | 2001-02-27 | 2014-06-24 | Verizon Data Services Llc | Methods and systems for automatic forwarding of communications to a preferred device |
US8782722B1 (en) * | 2013-04-05 | 2014-07-15 | Wowza Media Systems, LLC | Decoding of closed captions at a media server |
US20140269269A1 (en) | 2013-03-15 | 2014-09-18 | Movik Networks, Inc. | System and Methods for Estimation and Improvement of User, Service and Network QOE Metrics |
US20140283106A1 (en) * | 2013-03-14 | 2014-09-18 | Donuts Inc. | Domain protected marks list based techniques for managing domain name registrations |
US20150016253A1 (en) | 2013-07-11 | 2015-01-15 | Viasat, Inc. | Source-aware network shaping |
US20150026127A1 (en) * | 2013-07-19 | 2015-01-22 | Sears Brands L.L.C. | Method and system for migrating data between systems without downtime |
US20150100507A1 (en) * | 2013-07-09 | 2015-04-09 | Benoit Levac | Domain protected marks list service |
US20150288617A1 (en) * | 2014-04-07 | 2015-10-08 | Ericsson Television Inc. | Merging multicast abr and unicast abr with progressive download abr in a customer premises device within the same video delivery pipe |
US9191284B2 (en) * | 2010-10-28 | 2015-11-17 | Avvasi Inc. | Methods and apparatus for providing a media stream quality signal |
US9215424B2 (en) * | 2007-04-02 | 2015-12-15 | British Telecommunications Public Limited Company | Content delivery |
US20150382166A1 (en) * | 2013-02-12 | 2015-12-31 | Streamwide | Transmission of a multimedia message doubled with the transmission of a text message |
US20160028607A1 (en) * | 2014-07-27 | 2016-01-28 | Vasona Networks Inc. | Identifying services provided over secured connections using dns caching |
US20160088322A1 (en) | 2014-09-22 | 2016-03-24 | Arris Enterprises, Inc. | Video Quality of Experience Based on Video Quality Estimation |
US9311499B2 (en) * | 2000-11-13 | 2016-04-12 | Ron M. Redlich | Data security system and with territorial, geographic and triggering event protocol |
US9325765B2 (en) * | 2012-12-05 | 2016-04-26 | Industrial Technology Research Institute | Multimedia stream buffer and output method and multimedia stream buffer module |
US20160219332A1 (en) * | 2013-09-20 | 2016-07-28 | Interdigital Patent Holdings, Inc. | Verification of ad impressions in user-adaptive multimedia delivery framework |
US20160241626A1 (en) | 2015-02-13 | 2016-08-18 | Citrix Systems, Inc | METHODS AND SYSTEMS FOR ESTIMATING QUALITY OF EXPERIENCE (QoE) PARAMETERS OF SECURED TRANSACTIONS |
US9426049B1 (en) * | 2013-01-07 | 2016-08-23 | Zettics, Inc. | Domain name resolution |
US20160248684A1 (en) | 2015-02-24 | 2016-08-25 | Citrix Systems, Inc. | Methods and systems for detection and classification of multimedia content in secured transactions using pattern matching |
US9843554B2 (en) * | 2012-02-15 | 2017-12-12 | F5 Networks, Inc. | Methods for dynamic DNS implementation and systems thereof |
-
2014
- 2014-09-30 US US14/503,274 patent/US10171532B2/en active Active
-
2015
- 2015-09-29 WO PCT/US2015/053047 patent/WO2016054116A1/en active Application Filing
Patent Citations (79)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6026430A (en) * | 1997-03-24 | 2000-02-15 | Butman; Ronald A. | Dynamic client registry apparatus and method |
US5870562A (en) * | 1997-03-24 | 1999-02-09 | Pfn, Inc. | Universal domain routing and publication control system |
US20020033844A1 (en) * | 1998-10-01 | 2002-03-21 | Levy Kenneth L. | Content sensitive connected content |
US20010032878A1 (en) * | 2000-02-09 | 2001-10-25 | Tsiounis Yiannis S. | Method and system for making anonymous electronic payments on the world wide web |
US20040255115A1 (en) * | 2000-06-27 | 2004-12-16 | Microsoft Corporation | Method and system for binding enhanced software features to a persona |
US9311499B2 (en) * | 2000-11-13 | 2016-04-12 | Ron M. Redlich | Data security system and with territorial, geographic and triggering event protocol |
US20080222734A1 (en) * | 2000-11-13 | 2008-09-11 | Redlich Ron M | Security System with Extraction, Reconstruction and Secure Recovery and Storage of Data |
US20020069278A1 (en) * | 2000-12-05 | 2002-06-06 | Forsloew Jan | Network-based mobile workgroup system |
US8761363B2 (en) * | 2001-02-27 | 2014-06-24 | Verizon Data Services Llc | Methods and systems for automatic forwarding of communications to a preferred device |
US7103008B2 (en) * | 2001-07-02 | 2006-09-05 | Conexant, Inc. | Communications system using rings architecture |
US20030018753A1 (en) * | 2001-07-18 | 2003-01-23 | Ryuken Seki | Remote control proxy method and apparatus |
US20030032391A1 (en) * | 2001-08-09 | 2003-02-13 | Craig Schweinhart | Low latency handling of transmission control protocol messages in a broadband satellite communications system |
US20030081783A1 (en) * | 2001-10-23 | 2003-05-01 | Adusumilli Koteshwerrao S. | Selecting a security format conversion for wired and wireless devices |
US20030105630A1 (en) | 2001-11-30 | 2003-06-05 | Macginitie Andrew | Performance gauge for a distributed speech recognition system |
US20030174670A1 (en) * | 2002-03-14 | 2003-09-18 | Mar Jack K. | Packet-based mobile network |
US20060106836A1 (en) * | 2002-06-07 | 2006-05-18 | Madoka Masugi | Data processing system, data processing device, data processing method, and computer program |
US20040078573A1 (en) * | 2002-07-10 | 2004-04-22 | Shinako Matsuyama | Remote access system, remote access method, and remote access program |
US20040165603A1 (en) * | 2002-10-16 | 2004-08-26 | D'angelo Leo A. | Enhancing messaging services using translation gateways |
US20040093419A1 (en) * | 2002-10-23 | 2004-05-13 | Weihl William E. | Method and system for secure content delivery |
US20040210756A1 (en) * | 2003-04-15 | 2004-10-21 | Microsoft Corporation | Pass-thru for client authentication |
US20050097087A1 (en) * | 2003-11-03 | 2005-05-05 | Punaganti Venkata Murali K. | System and method for providing a unified framework for service discovery |
US7933290B2 (en) * | 2004-03-30 | 2011-04-26 | Nokia Corporation | System and method for comprehensive service translation |
US20050273592A1 (en) | 2004-05-20 | 2005-12-08 | International Business Machines Corporation | System, method and program for protecting communication |
US20060031368A1 (en) * | 2004-06-16 | 2006-02-09 | Decone Ian D | Presence management in a push to talk system |
US20070073837A1 (en) * | 2005-05-24 | 2007-03-29 | Johnson-Mccormick David B | Online multimedia file distribution system and method |
US7792910B2 (en) * | 2005-08-31 | 2010-09-07 | Oki Data Corporation | Apparatus for sending image data by electronic mail |
US20090104954A1 (en) * | 2006-04-13 | 2009-04-23 | Igt | Methods and systems for tracking an event of an externally controlled interface |
US20070288621A1 (en) * | 2006-05-11 | 2007-12-13 | Veerabhadra Gundu | Methods for managing presence information in a real-time communications network |
US20080062863A1 (en) * | 2006-09-12 | 2008-03-13 | Qualcomm Incorporated | Transaction timeout handling in communication session management |
US20090147772A1 (en) * | 2006-10-02 | 2009-06-11 | Prasad Rao | Systems and methods for providing presence information in communication |
US9215424B2 (en) * | 2007-04-02 | 2015-12-15 | British Telecommunications Public Limited Company | Content delivery |
US20080294556A1 (en) * | 2007-05-24 | 2008-11-27 | Jim Anderson | Mobile commerce service |
US20090077383A1 (en) * | 2007-08-06 | 2009-03-19 | De Monseignat Bernard | System and method for authentication, data transfer, and protection against phishing |
US20090098886A1 (en) * | 2007-10-16 | 2009-04-16 | Nokia Corporation | System and method for providing presence notifications based upon watcher status |
US20090172129A1 (en) * | 2007-12-28 | 2009-07-02 | Cellspin Soft Inc. | Automatic Multimedia Upload For Publishing Data And Multimedia Content |
US20110113106A1 (en) * | 2008-01-28 | 2011-05-12 | Mikael Klein | Throttle on presence |
US20090241159A1 (en) * | 2008-03-18 | 2009-09-24 | Avaya Technology Llc | Open cable application platform set-top box (stb) personal profiles and communications applications |
US20090248494A1 (en) * | 2008-04-01 | 2009-10-01 | Certona Corporation | System and method for collecting and targeting visitor behavior |
US20090310805A1 (en) * | 2008-06-14 | 2009-12-17 | Michael Petroff | Hearing aid with anti-occlusion effect techniques and ultra-low frequency response |
US20100017218A1 (en) * | 2008-07-21 | 2010-01-21 | Uab "Ieec" | Business method for domain name and trade mark assigning and marketing |
US8392980B1 (en) * | 2008-08-22 | 2013-03-05 | Avaya Inc. | Trusted host list for TLS sessions |
US20100094984A1 (en) * | 2008-10-13 | 2010-04-15 | International Business Machines Corporation | Method for optmizing a presence enabled managed service |
US20100123727A1 (en) * | 2008-11-18 | 2010-05-20 | Kwa Seh W | Techniques to control self refresh display functionality |
US8671069B2 (en) * | 2008-12-22 | 2014-03-11 | The Trustees Of Columbia University, In The City Of New York | Rapid image annotation via brain state decoding and visual pattern mining |
US20100259386A1 (en) * | 2009-04-09 | 2010-10-14 | International Business Machines Corporation | System and methods for locating mobile devices using location and presence information |
US20110029985A1 (en) * | 2009-07-31 | 2011-02-03 | Nokia Corporation | Method and apparatus for coordinating resource access |
US20110082924A1 (en) | 2009-10-06 | 2011-04-07 | Openwave Systems Inc. | Managing network traffic by editing a manifest file |
US20110119388A1 (en) * | 2009-11-16 | 2011-05-19 | International Business Machines Corporation | Optimization of Multimedia Service Over an IMS Network |
US8326920B1 (en) * | 2010-02-08 | 2012-12-04 | Google Inc. | Connection sharing |
US20110243553A1 (en) * | 2010-03-31 | 2011-10-06 | Incnetworks, Inc. | Method, computer program, and algorithm for computing network service value pricing based on communication service experiences delivered to consumers and merchants over a smart multi-services (sms) communication network |
US20120017253A1 (en) * | 2010-07-15 | 2012-01-19 | At&T Intellectual Property I, L.P. | Apparatus and method for providing services using a services gateway |
US20120179752A1 (en) * | 2010-09-10 | 2012-07-12 | Visible Technologies, Inc. | Systems and methods for consumer-generated media reputation management |
US20120084423A1 (en) | 2010-10-04 | 2012-04-05 | Openwave Systems Inc. | Method and system for domain based dynamic traffic steering |
US9191284B2 (en) * | 2010-10-28 | 2015-11-17 | Avvasi Inc. | Methods and apparatus for providing a media stream quality signal |
US20140115100A1 (en) * | 2011-01-31 | 2014-04-24 | Alcatel Lucent | Video packet scheduling method for multimedia streaming |
US20130144785A1 (en) * | 2011-03-29 | 2013-06-06 | Igor Karpenko | Social network payment authentication apparatuses, methods and systems |
US8327128B1 (en) * | 2011-07-28 | 2012-12-04 | Cloudflare, Inc. | Supporting secure sessions in a cloud-based proxy service |
US20130139164A1 (en) * | 2011-11-28 | 2013-05-30 | Sap Ag | Business Process Optimization |
US8239266B1 (en) * | 2011-11-29 | 2012-08-07 | Google Inc. | Targeting based on intent or presence |
US20130198511A1 (en) | 2012-01-27 | 2013-08-01 | Microsoft Corporation | Implicit ssl certificate management without server name indication (sni) |
US20130203433A1 (en) * | 2012-02-03 | 2013-08-08 | Seven Networks, Inc. | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
US9843554B2 (en) * | 2012-02-15 | 2017-12-12 | F5 Networks, Inc. | Methods for dynamic DNS implementation and systems thereof |
US20130312054A1 (en) * | 2012-05-17 | 2013-11-21 | Cisco Technology, Inc. | Transport Layer Security Traffic Control Using Service Name Identification |
EP2725757A1 (en) | 2012-10-29 | 2014-04-30 | Alcatel Lucent | TLS protocol extension |
US9325765B2 (en) * | 2012-12-05 | 2016-04-26 | Industrial Technology Research Institute | Multimedia stream buffer and output method and multimedia stream buffer module |
US9426049B1 (en) * | 2013-01-07 | 2016-08-23 | Zettics, Inc. | Domain name resolution |
US20150382166A1 (en) * | 2013-02-12 | 2015-12-31 | Streamwide | Transmission of a multimedia message doubled with the transmission of a text message |
US20140283106A1 (en) * | 2013-03-14 | 2014-09-18 | Donuts Inc. | Domain protected marks list based techniques for managing domain name registrations |
US20140269269A1 (en) | 2013-03-15 | 2014-09-18 | Movik Networks, Inc. | System and Methods for Estimation and Improvement of User, Service and Network QOE Metrics |
US8782722B1 (en) * | 2013-04-05 | 2014-07-15 | Wowza Media Systems, LLC | Decoding of closed captions at a media server |
US20150100507A1 (en) * | 2013-07-09 | 2015-04-09 | Benoit Levac | Domain protected marks list service |
US20150016253A1 (en) | 2013-07-11 | 2015-01-15 | Viasat, Inc. | Source-aware network shaping |
US20150026127A1 (en) * | 2013-07-19 | 2015-01-22 | Sears Brands L.L.C. | Method and system for migrating data between systems without downtime |
US20160219332A1 (en) * | 2013-09-20 | 2016-07-28 | Interdigital Patent Holdings, Inc. | Verification of ad impressions in user-adaptive multimedia delivery framework |
US20150288617A1 (en) * | 2014-04-07 | 2015-10-08 | Ericsson Television Inc. | Merging multicast abr and unicast abr with progressive download abr in a customer premises device within the same video delivery pipe |
US20160028607A1 (en) * | 2014-07-27 | 2016-01-28 | Vasona Networks Inc. | Identifying services provided over secured connections using dns caching |
US20160088322A1 (en) | 2014-09-22 | 2016-03-24 | Arris Enterprises, Inc. | Video Quality of Experience Based on Video Quality Estimation |
US20160241626A1 (en) | 2015-02-13 | 2016-08-18 | Citrix Systems, Inc | METHODS AND SYSTEMS FOR ESTIMATING QUALITY OF EXPERIENCE (QoE) PARAMETERS OF SECURED TRANSACTIONS |
US20160248684A1 (en) | 2015-02-24 | 2016-08-25 | Citrix Systems, Inc. | Methods and systems for detection and classification of multimedia content in secured transactions using pattern matching |
Non-Patent Citations (17)
Title |
---|
Bestavros et al., "Performance Evaluation of Two-Shadow Speculative Concurrency Control", 1993. * |
Blake-Wilson et al., "Transport Layer Security (TLS) Extensions", RFC 3546, 2003. * |
Crocker, "Standard for the format of ARPA Internet Text Messages", RFC 0822, 1982 (Year: 1982). * |
Davidowicz, "Domain Name System (DNS) Security", 1999 (Year: 1999). * |
De Capitani et al., "Data and Applications Security XVII Status and Prospects", 2003 (Year: 2003). * |
Dierks et al., "The TLS Protocol Version 1.0", RFC 2246, 1999. * |
Dierks et al., "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, 2008. * |
Eastlake, "Domain Name System Security Extensions", RFC2535, 1999 (Year: 1999). * |
International Search Report and Written Opinion issued in PCT/US2015/053047 dated Feb. 25, 2016; 17 pages. |
McKinley, "SSL and TLS: A Beginners Guide", 2003. * |
Mockapetris, "Domain Names-Concepts and Facilities", RFC 1034, 1987 (Year: 1987). * |
Mockapetris, "Domain Names—Concepts and Facilities", RFC 1034, 1987 (Year: 1987). * |
Paleologu et al., "International Journal on Advances in Systems and Measurements", 2011 (Year: 2011). * |
Pinkas et al., "Delegated Path Validation and Delegated Path Discovery Protocol Requirements", RFC 3379, 2002 (Year: 2002). * |
Santession, "Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name", RFC4985, 2007 (Year: 2007). * |
Wikipedia, "Domain Name System Security Extensions", 2018 (Year: 2018). * |
Wikipedia, "Transport Layer Security", 2017. * |
Also Published As
Publication number | Publication date |
---|---|
WO2016054116A1 (en) | 2016-04-07 |
US20160094602A1 (en) | 2016-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10171532B2 (en) | Methods and systems for detection and classification of multimedia content in secured transactions | |
US20230231939A1 (en) | Methods and systems for detection and classification of multimedia content in secured transactions using pattern matching | |
US9521060B2 (en) | Identifying services provided over secured connections using DNS caching | |
US10715576B2 (en) | Methods and systems for estimating quality of experience (QoE) parameters of secured transactions | |
US20150334094A1 (en) | Distributed computing service platform for mobile network traffic | |
US9307450B2 (en) | Method and apparatus for content caching in a wireless communication network | |
US10353962B2 (en) | Method and system for bitrate management | |
KR101981285B1 (en) | Contents delivery service system using contents identification, apparatus therefor and contents delivery service method thereof | |
US20160255047A1 (en) | Methods and systems for determining domain names and organization names associated with participants involved in secured sessions | |
US10541929B2 (en) | PCC control of HTTP adaptive bit rate video streaming protocols | |
US20180048514A1 (en) | Mechanism to support operator assisted parental control | |
KR102034785B1 (en) | Coordinated packet delivery of encrypted session | |
US11902336B2 (en) | Interception of high-throughput data traffic | |
US10129785B2 (en) | Method and apparatus for processing media traffic in mobile communication system | |
US11540026B2 (en) | Data relay apparatus, method, delivery system, and program | |
US9825923B2 (en) | Secure radio information transfer over mobile radio bearer | |
US9723499B2 (en) | Optimizer selection in wireless networks | |
WO2011110010A1 (en) | Method, apparatus and communication system for transmitting contents | |
WO2018068262A1 (en) | Video code rate acquisition method, apparatus, and network side device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CITRIX SYSTEMS, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FUH, HSIEHYU;CHOH, EDWARD WAI HONG;PARTHASARATHY, KANNAN;REEL/FRAME:033954/0188 Effective date: 20140930 |
|
AS | Assignment |
Owner name: BYTEMOBILE, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CITRIX SYSTEMS, INC.;REEL/FRAME:035440/0599 Effective date: 20150402 |
|
AS | Assignment |
Owner name: CITRIX SYSTEMS, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BYTEMOBILE, INC.;REEL/FRAME:037289/0606 Effective date: 20151119 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: BYTEMOBILE INNOVATIONS, LLC, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CITRIX SYSTEMS, INC.;REEL/FRAME:059087/0052 Effective date: 20220214 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: OPTIMORPHIX, INC., MINNESOTA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BYTEMOBILE INNOVATIONS, LLC;REEL/FRAME:064054/0247 Effective date: 20230410 |