Video content delivery over wireless access networks with quality of service (QOS) guarantees

A device receives, from a content provider, traffic parameters associated with a video content request received from a fixed user device connected to a wireless access network, and determines, based on the traffic parameters, a trigger for creating a dedicated bearer for the fixed user device in the wireless access network. The device also provides the trigger to the wireless access network, where the wireless access network creates the dedicated bearer for the fixed user device based on the trigger, and the wireless access network assigns quality of service (QoS) parameters, based on the traffic parameters, to video content delivered to the fixed user device.

BACKGROUND

As wireless network data rates improve using third generation (3G), fourth generation (4G), and WiFi technologies, more and more bandwidth-intensive applications are being developed. Video over the Internet is becoming a significant part of Internet traffic with video portals provided by content providers, such as Hulu, YouTube, CNN, etc. Video content is also becoming more popular with applications provided via smart phones (e.g., the Motorola DROID, the iPhone, etc.). Much of the video content provided by such content providers and/or applications is high bit rate content that is not optimized for wireless networks. Furthermore, wireless networks may be utilized as a “last mile solution” (e.g., connection between a customer and a telephone company, cable company, and/or service provider) in remote regions (e.g., rural regions) for the delivery of video content, such as television (TV) content (e.g., TV shows, pay-per-view (PPV) content, video-on-demand (VOD) content, etc.).

Wireless service providers have no control over this off-network video content. For example, wireless service providers cannot provide quality of service (QoS) guarantees to such video content. QoS refers to resource reservation control mechanisms that provide different priorities to different applications, users, and/or traffic (e.g., video content), or guarantees a certain level of performance (e.g., a required bit rate, delay, jitter, packet dropping probability, and/or bit error rate (BER) may be guaranteed) to traffic. If content delivery is not optimized for wireless networks, video content may become a choking point for the wireless networks. This may result in poor user experiences and degraded services (e.g., provided by the wireless networks) for other applications like voice-over-Internet protocol (VoIP).

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Systems and/or methods described herein may provide QoS guarantees to video content delivered to fixed user devices over wireless access networks. The systems and/or methods may extend policy control capabilities of the wireless access network so that policies for QoS delivery are simplified. In one example implementation, the systems and/or methods may receive a video content request from a fixed user device connected to a Long Term Evolution (LTE) access network, and may provide the video content request to a content provider. The systems and/or methods may receive a trigger for creating a dedicated bearer, in the LTE network, based on traffic parameters associated with the video content request, and may create a dedicated bearer for the fixed user device, in the LTE network, based on the trigger. The systems and/or methods may receive video content from the content provider based on the video content request, may assign or provide QoS parameters to the video content based on the traffic parameters, and may provide, to the user device via the LTE network, the video content with the QoS parameters.

In another implementation, for example, the systems and/or methods may receive subscriber profile information for a fixed user device when the user device connects to a LTE network, and may receive a video content request from the fixed user device. The systems and/or methods may provide the video content request to a content provider, may receive video content from the content provider based on the video content request, and may create a dedicated bearer for the fixed user device when the video content matches the subscriber profile information. The systems and/or methods may assign or provide QoS parameters to the video content based on the subscriber profile information, and may provide, to the user device via the LTE network, the video content with the QoS parameters.

As used herein, the terms “customer,” “viewer,” “subscriber,” and/or “user” may be used interchangeably. Also, the terms “customer,” “viewer,” “subscriber,” and/or “user” are intended to be broadly interpreted to include a user device (e.g., a mobile telephone, a personal computer, a set-top box, a television, etc.) or a user of a user device.

FIG. 1is a diagram of an example network100in which systems and/or methods described herein may be implemented. As illustrated, network100may include a user device110, a base station120, a network device130, a policy control function140, a network150, and a video content provider160. Components of network100may interconnect via wired and/or wireless connections. A single user device110, base station120, network device130, policy control function140, network150, and video content provider160have been illustrated inFIG. 1for simplicity. In practice, there may be more user devices110, base stations120, network devices130, policy control functions140, networks150, and/or video content providers160.

User device110may include any device that is capable of communicating with video content provider160via a wireless network (e.g., provided by base station120and/or network device130). For example, user device110may include a mobile computation and/or communication device, such as a radiotelephone, a personal communications system (PCS) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a personal digital assistant (PDA) (e.g., that can include a radiotelephone, a pager, Internet/intranet access, etc.), a wireless device, a smart phone, a laptop computer (e.g., with a wireless air card), a global positioning system (GPS) device, a content recording device (e.g., a camera, a video camera, etc.), etc. In another example, user device110may include a fixed (e.g., provided in a particular location, such as within a customer's home) computation and/or communication device, such as a laptop computer, a personal computer, a tablet computer, a set-top box (STB), a television, a gaming system, etc.

Base station120may include one or more computation and/or communication devices that receive voice and/or data (e.g., video content) from video content provider160(e.g., via network device130) and transmit that voice and/or data to user device110. Base station120may also include one or more devices that receive voice and/or data (e.g., a request for video content) from user device110and transmit that voice and/or data to video content provider160(e.g., via network device130and network150).

Network device130may include one or more data transfer devices, such as a gateway, a router, a switch, a firewall, a network interface card (NIC), a hub, a bridge, a proxy server, an optical add-drop multiplexer (OADM), or some other type of device that processes and/or transfers data. In one example, network device130may include a mobile wireless gateway that provides a convergence point between wireless protocols (e.g., associated with user device110and/or base station120) and IP protocols (e.g., associated with policy control function140, network150, and/or video content provider160). The mobile wireless gateway may route packets (or portions of packets) from a wireless network (e.g., user device110and base station120) to another network (e.g., network150). In one implementation, network device130may receive requests for video content from user device110(e.g., via base station120), and may provide the requests for video content to video content provider160. Network device130may receive the requested video content from video content provider160, may apply QoS parameters or guarantees to the video content, and may provide the video content (e.g., with the guaranteed QoS) to user device110(e.g., via base station120). Further details of network device130are provided below in connection with one or more ofFIGS. 2-5.

In one example, base station120and/or network device130may provide a wireless access network for user device110. The wireless access network, in one implementation, may correspond to a LTE network. The LTE network may include a communications network that connects subscribers (e.g., user device110) to a service provider (e.g., video content provider160). In another implementation, the wireless access network may include a WiFi network or other access networks (e.g., an enhanced high-rate packet data (eHRPD) network or a WiMax network). In another example, the wireless access network may include a radio access network capable of supporting high data rate, low latency, packet optimization, large capacity and coverage, etc.

Policy control function140may include one or more computation or communication devices that may provide policy control decision and flow based charging control functionalities. Policy control function140may provide network control regarding service data flow detection, gating, QoS and flow based charging, etc. Policy control function140may determine how a certain service data flow shall be treated, and may ensure that user plane traffic mapping and treatment is in accordance with a user's subscription profile. In one implementation, policy control function140may receive traffic parameters (e.g., source and destination IP addresses, port over which traffic is carried, protocol over which traffic is carried, average and peak required data rates, etc.) for video content delivery from video content provider160. Policy control function140may trigger creation of a dedicated bearer for user device110(e.g., in the LTE network provided by base station120and/or network device130) based on the received traffic parameters. In another implementation, policy control function140may receive profile information associated with video content subscribers (e.g., users of user devices110), and may provide profile information for a particular subscriber to network device130when the particular subscriber attaches to the LTE network (e.g., provided by base station120and/or network device130). Further details of policy control function140are provided below in connection with one or more ofFIGS. 2-4 and 6.

Network150may include a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network, such as the Public Switched Telephone Network (PSTN), an intranet, the Internet, an optical fiber (or fiber optic)-based network, a cable television network, a satellite television network, or a combination of networks.

Video content provider160may include one or more server devices, or other types of computation or communication devices, that gather, process, search, and/or provide information in a manner described herein. In one implementation, video content provider160may include a computer system, an application, a cable head-end, and/or a broadcasting device capable of providing video content (e.g., VOD content, high definition (HD)-VOD content, TV programming, movies, on-demand services, live television, etc.), commercials, advertisements, instructions, and/or other information.

AlthoughFIG. 1shows example components of network100, in other implementations, network100may contain fewer components, different components, differently arranged components, and/or additional components than those depicted inFIG. 1. Alternatively, or additionally, one or more components of network100may perform one or more other tasks described as being performed by one or more other components of network100.

FIG. 2is a diagram of example components of a device200that may correspond to one of the devices of network100. As illustrated, device200may include a bus210, a processing unit220, a memory230, an input device240, an output device250, and a communication interface260.

Bus210may permit communication among the components of device200. Processing unit220may include one or more processors or microprocessors that interpret and execute instructions. In other implementations, processing unit220may be implemented as or include one or more application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or the like.

Memory230may include a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by processing unit220, a read only memory (ROM) or another type of static storage device that stores static information and instructions for the processing unit220, and/or some other type of magnetic or optical recording medium and its corresponding drive for storing information and/or instructions.

Input device240may include a device that permits an operator to input information to device200, such as a keyboard, a keypad, a mouse, a pen, a microphone, one or more biometric mechanisms, and the like. Output device250may include a device that outputs information to the operator, such as a display, a speaker, etc.

Communication interface260may include any transceiver-like mechanism that enables device200to communicate with other devices and/or systems. For example, communication interface360may include mechanisms for communicating with other devices, such as other devices of network100.

As described herein, device200may perform certain operations in response to processing unit220executing software instructions contained in a computer-readable medium, such as memory230. A computer-readable medium may be defined as a physical or logical memory device. A logical memory device may include memory space within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into memory230from another computer-readable medium or from another device via communication interface260. The software instructions contained in memory230may cause processing unit220to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

AlthoughFIG. 2shows example components of device200, in other implementations, device200may contain fewer components, different components, differently arranged components, or additional components than depicted inFIG. 2. Alternatively, or additionally, one or more components of device200may perform one or more other tasks described as being performed by one or more other components of device200.

FIG. 3is a diagram of example interactions between components of an example portion300of network100. As illustrated, example network portion300may include user device110, base station120, network device130, policy control function140, and video content provider160. User device110, base station120, network device130, policy control function140, and video content provider160may include the features described above in connection with one or more ofFIGS. 1 and 2. Furthermore, user device110depicted inFIG. 3may correspond to a fixed user device, such as a television (TV)110associated with a set-top box (STB)110.

Television110may include a television monitor that is capable of displaying video content, television programming, content provided by STB110, and/or content provided by other devices (e.g., a digital video disk (DVD) player, a video camera, etc., not shown) connected to television110.

STB110may include a device that receives video content (e.g., from video content provider160), and provides the video content to television110or another device. STB110may record video content in a digital format to a disk drive or other memory medium within STB110. In one example implementation, STB110may be incorporated directly within television110and/or may include a digital video recorder (DVR). In another implementation, television/STB110may be replaced with a computing device, such as a personal computer, a laptop computer, a tablet computer, etc.

In one example implementation, user device110(e.g., STB110) may connect to an outdoor broadband unit (not shown) that enables user device110to wirelessly communicate with base station120. The outdoor broadband unit may include a radio frequency (RF) antenna and a LTE module. The RF antenna may include an antenna to transmit and/or receive RF signals over the air. The RF antenna may, for example, receive RF signals from the LTE module and transmit the RF signals over the air. Also, the RF antenna may, for example, receive RF signals over the air and provide them to the LTE module. In one implementation, for example, the LTE module may communicate with base station120to send and/or receive signals from user device110. The LTE module may include communication capability via an air interface. For example, the LTE module may receive broadband signals and/or VoIP signals from base station120(e.g., via the RF antenna) and may transmit broadband signals and/or VoIP signals to base station120(e.g., via the RF antenna). The LTE module may employ frequency division duplex (FDD) and/or time division duplex (TDD) techniques to facilitate downlink and uplink transmissions.

As further shown inFIG. 3, a user (not shown) may utilize user device110to generate a request310for video content to be displayed on user device110. For example, the user may be viewing a menu of VOD content (e.g., via user device110), and may select a video provided by the menu. User device110may wirelessly provide video content request310to base station120, and base station120may forward video content request310to network device130. Network device130may forward video content request310to video content provider160(e.g., via network150, not shown). Video content provider160may receive video content request310from network device130, and may interact with policy control function140to deliver traffic parameters320associated with the video content requested by video content request310(e.g., prior to providing the video content to user device110). For example, video content provider160may provide, to policy control function140, traffic parameters320, such as source and/or destination IP addresses over which the video content will be delivered; a port over which the video content will be delivered; a protocol (e.g., a transmission control protocol (TCP), a user datagram protocol (UDP), a real-time transport protocol (RTP), etc.) over which the video content will be carried; average and peak data rates associated with the video content; etc.

Policy control function140may receive traffic parameters320, and may trigger creation of a dedicated bearer (e.g., based on traffic parameters320) for user device110in the wireless access network provided by base station120and/or network device130, as indicated by reference number330. Video content provider160may search for the requested video content (e.g., provided via video content request310), and may provide the requested video content340to network device130. After creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on traffic parameters320) to video content340in order to create video content (e.g., with the QoS guarantees)350. For example, network device130may provide QoS that guarantees a certain level of performance (e.g., a required bit rate, delay, jitter, packet dropping probability, and/or BER may be guaranteed) for video content340. In another example, as packets associated with video content340arrive at network device130, network device130may mark the packets with QoS parameters.

As further shown inFIG. 3, network device130may provide video content (e.g., with the QoS guarantees)350to base station120. Base station120may provide similar QoS treatment to video content350as provided by network device130(e.g., as described above), and may guarantee an average data rate to video content350. Base station120may provide video content (e.g., with the QoS guarantees)350to user device110(e.g., to STB110). User device110may receive video content350and may display video content350to the user (e.g., via television110).

AlthoughFIG. 3shows example components of network portion300, in other implementations, network portion300may contain fewer components, different components, differently arranged components, and/or additional components than depicted inFIG. 3. Alternatively, or additionally, one or more components of network portion300may perform one or more other tasks described as being performed by one or more other components of network portion300.

FIG. 4is a diagram of example interactions between components of another example portion400of network100. As illustrated, example network portion400may include user device110, base station120, network device130, policy control function140, and video content provider160. User device110, base station120, network device130, policy control function140, and video content provider160may include the features described above in connection with one or more ofFIGS. 1-3. Furthermore, user device110depicted inFIG. 4may correspond to a fixed user device, such as a television (TV)110associated with a STB110. Television110and STB110may include the features described above in connection withFIG. 3.

As shown inFIG. 4, subscriber profile information410may be pre-provisioned in policy control function140(e.g., by video content provider160and/or other sources). Subscriber profile information410may include information associated with subscribers (e.g., users of user devices110) of video content provider160. For example, subscriber profile information410may include traffic parameters320(e.g., source and/or destination IP addresses over which video content will be delivered, a port over which video content will be delivered, a protocol over which video content will be carried, average and peak data rates associated with video content, etc.) associated with subscribers of video content provider160.

As further shown inFIG. 4, a user (not shown) may utilize user device110(e.g., STB110) to attach to the wireless access network (e.g., provided by base station120and/or network device130), as indicated by reference number420. When the user (e.g., via STB110) attaches to the wireless access network, policy control function140may be instructed (e.g., by network device130) to provide profile information430for the specific user to network device130. Specific profile information430may include traffic parameters320(e.g., source and/or destination IP addresses over which video content will be delivered, a port over which video content will be delivered, a protocol over which video content will be carried, average and peak data rates associated with video content, etc.) associated with the user of user device110.

The user may also utilize user device110(e.g., STB110) to generate a request440for video content to be displayed on user device110. For example, the user may be viewing a menu of pay-per-view content (e.g., via user device110), and may select a video provided by the menu. User device110may wirelessly provide video content request440to base station120, and base station120may forward video content request440to network device130. Network device130may forward video content request440to video content provider160(e.g., via network150, not shown). Video content provider160may receive video content request440from network device130, may search for the requested video content (e.g., provided via video content request440), and may provide the requested video content450to network device130.

Network device130may receive video content450(e.g., packets of video content450), and may determine whether packets of video content450match specific profile information430received from policy control function140. When network device130detects a packet of video content450(e.g., as video content450is received) that matches specific profile information430, network device130may trigger creation of a dedicated bearer (e.g., based on specific profile information430) for user device110in the wireless access network provided by base station120and/or network device130, as indicated by reference number460. The dedicated bearer may be created quickly (e.g., in a fraction of a second), and packets of video content450arriving at network device130may be queued until the dedicated bearer is created. If network device130fails to detect a packet of video content450that matches specific profile information430, network device130may optimize resources by not creating the dedicated bearer.

After creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on specific profile information430) to video content450(e.g., to new packets and to queued packets of video content450) in order to create video content (e.g., with the QoS guarantees)470. For example, network device130may provide QoS that guarantees a certain level of performance (e.g., a required bit rate, delay, jitter, packet dropping probability, and/or BER may be guaranteed) for video content450. In another example, as packets associated with video content450arrive at network device130, network device130may mark the packets with QoS parameters.

As further shown inFIG. 4, network device130may provide video content (e.g., with the QoS guarantees)470to base station120. Base station120may provide similar QoS treatment to video content470as provided by network device130(e.g., as described above), and may guarantee an average data rate to video content470. Base station120may provide video content (e.g., with the QoS guarantees)470to user device110(e.g., to STB110). User device110may receive video content470and may display video content470to the user (e.g., via television110).

AlthoughFIG. 4shows example components of network portion400, in other implementations, network portion400may contain fewer components, different components, differently arranged components, and/or additional components than depicted inFIG. 4. Alternatively, or additionally, one or more components of network portion400may perform one or more other tasks described as being performed by one or more other components of network portion400.

FIG. 5is a diagram of example functional components of network device130. In one implementation, the functions described in connection withFIG. 5may be performed by one or more components of device200(FIG. 2). As shown inFIG. 5, network device130may include a video content receiver500, a dedicated bearer creator510, and a QoS marker520.

Video content receiver500may include hardware or a combination of hardware and software that may receive video content request310and/or video content request440from user device110, and may forward video content requests310/440to video content provider160(e.g., via network150). Video content receiver500may also receive video content340and/or video content450from video content provider160, may provide video content340/450to QoS marker520, and may provide video content450to dedicated bearer creator510.

Dedicated bearer creator510may include hardware or a combination of hardware and software that may receive trigger330to create a dedicated bearer (e.g., based on traffic parameters320provided via trigger330) for user device110in the wireless access network provided by base station120and/or network device130. Dedicated bearer creator510may provide trigger330to base station120so that base station120may create the dedicated bearer for user device110. As further shown inFIG. 5, dedicated bearer creator510may receive specific profile information430from policy control function140and video content450from video content provider160, and may determine whether packets of video content450match specific profile information430. When dedicated bearer creator510detects a packet of video content450that matches specific profile information430, dedicated bearer creator510may trigger creation of a dedicated bearer (e.g., based on specific profile information430) for user device110in the wireless access network provided by base station120and/or network device130, as indicated by reference number460. Dedicated bearer creator510may provide trigger330and specific profile information430to QoS marker520.

QoS marker520may include hardware or a combination of hardware and software that may receive trigger330and/or specific profile information430from dedicated bearer creator510, and may receive video content340/450from video content receiver500. In one example, QoS marker520may assign or provide QoS parameters or guarantees (e.g., based on traffic parameters320provided via trigger330) to video content340in order to create video content (e.g., with the QoS guarantees)350. QoS marker520may provide video content (e.g., with the QoS guarantees)350to base station120. In another example, QoS marker520may assign or provide QoS parameters or guarantees (e.g., based on specific profile information430) to video content450(e.g., to new packets and to queued packets of video content450) in order to create video content (e.g., with the QoS guarantees)470. QoS marker520may provide video content (e.g., with the QoS guarantees)470to base station120.

AlthoughFIG. 5shows example functional components of network device130, in other implementations, network device130may contain fewer functional components, different functional components, differently arranged functional components, and/or additional functional components than depicted inFIG. 5. Alternatively, or additionally, one or more functional components of network device130may perform one or more other tasks described as being performed by one or more other functional components of network device130.

FIG. 6is a diagram of example functional components of policy control function140. In one implementation, the functions described in connection withFIG. 6may be performed by one or more components of device200(FIG. 2). As shown inFIG. 6, policy control function140may include a dedicated bearer creator600and a subscriber profile component610.

Dedicated bearer creator600may include hardware or a combination of hardware and software that may receive traffic parameters320from video content provider160. Traffic parameters320may include address information (e.g., source and/or destination IP addresses over which video content will be delivered); port information (e.g., a port over which video content will be delivered); protocol information (e.g., a protocol, such as TCP, UDP, RTP, etc., over which video content will be carried); and data rate information (e.g., average and peak data rates associated with video content). As further shown inFIG. 6, dedicated bearer creator600may generate trigger330for creating a dedicated bearer (e.g., based on traffic parameters320) for user device110in the wireless access network provided by base station120and/or network device130. Dedicated bearer creator600may provide trigger330to network device130.

Subscriber profile component610may include hardware or a combination of hardware and software that may receive subscriber profile information410from, for example, video content provider160. When a specific user (e.g., via user device110) attaches to the wireless access network, subscriber profile component610may provide profile information430for the specific user to network device130. As shown inFIG. 6, specific profile information430may include address information (e.g., source and/or destination IP addresses over which video content will be delivered); port information (e.g., a port over which video content will be delivered); protocol information (e.g., a protocol, such as TCP, UDP, RTP, etc., over which video content will be carried); and data rate information (e.g., average and peak data rates associated with video content) associated with the user of user device110.

AlthoughFIG. 6shows example functional components of policy control function140, in other implementations, policy control function140may contain fewer functional components, different functional components, differently arranged functional components, and/or additional functional components than depicted inFIG. 6. Alternatively, or additionally, one or more functional components of policy control function140may perform one or more other tasks described as being performed by one or more other functional components of policy control function140.

FIGS. 7-10are flow charts of example processes700-1000for providing QoS guarantees to video content delivered to fixed user devices over wireless access networks according to implementations described herein. In one implementation, processes700and800may be performed by policy control function140. In another implementation, some or all of processes700and800may be performed by another device or group of devices, including or excluding policy control function140. In one implementation, processes900and1000may be performed by network device130. In another implementation, some or all of processes900and1000may be performed by another device or group of devices, including or excluding network device130.

As illustrated inFIG. 7, process700may include receiving, from a content provider, traffic parameters associated with a video content request received from a fixed user device connected to a LTE network (block710), and generating a trigger for creating a dedicated bearer in the LTE network based on the traffic parameters (block720). For example, in implementations described above in connection withFIGS. 3 and 6, video content provider160may interact with policy control function140to deliver traffic parameters320associated with the video content requested by video content request310(e.g., prior to providing the video content to user device110). In one example, video content provider160may provide, to policy control function140, traffic parameters320, such as source and/or destination IP addresses over which the video content will be delivered; a port over which the video content will be delivered; a protocol (e.g., a TCP, a UDP, a RTP, etc.) over which the video content will be carried; average and peak data rates associated with the video content; etc. Policy control function140may receive traffic parameters320, and dedicated bearer creator600of policy control function140may generate trigger330for creating a dedicated bearer (e.g., based on traffic parameters320) for user device110in the wireless access network (e.g., provided by base station120and/or network device130).

As further shown inFIG. 7, process700may include providing the trigger to the LTE network, where the LTE network creates the dedicated bearer for the user device based on the trigger and provides QoS treatment to video content delivered to the user device based on the traffic parameters (block730). For example, in implementations described above in connection withFIG. 3, policy control function140may trigger creation of a dedicated bearer (e.g., based on traffic parameters320) for user device110in the wireless access network provided by base station120and/or network device130, as indicated by reference number330. After creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on traffic parameters320) to video content340in order to create video content (e.g., with the QoS guarantees)350. In one example, network device130may provide QoS that guarantees a certain level of performance (e.g., a required bit rate, delay, jitter, packet dropping probability, and/or BER may be guaranteed) for video content340.

As illustrated inFIG. 8, process800may include receiving, from a content provider, profile information associated with video content subscribers (block810). For example, in implementations described above in connection withFIG. 4, subscriber profile information410may be pre-provisioned in policy control function140(e.g., by video content provider160and/or other sources). Subscriber profile information410may include information associated with subscribers (e.g., users of user devices110) of video content provider160. In one example, subscriber profile information410may include traffic parameters320(e.g., source and/or destination IP addresses over which the video content will be delivered, a port over which the video content will be delivered, a protocol over which the video content will be carried, average and peak data rates associated with the video content, etc.) associated with subscribers of video content provider160.

As further shown inFIG. 8, process800may include providing, to a LTE network, particular subscriber information, from the received profile information, when a particular subscriber attaches to the LTE network, where the LTE network provides QoS treatment, based on the particular subscriber profile information, to video content delivered to a fixed user device connected to the LTE network (block820). For example, in implementations described above in connection withFIG. 4, when the user (e.g., via STB110) attaches to the wireless access network, profile information430for the specific user may be provided by policy control function140to network device130. Specific profile information430may include traffic parameters320associated with the user of user device110. Video content provider160may receive video content request440generated by user device110, may search for the requested video content (e.g., provided via video content request440), and may provide the requested video content450to network device130. When network device130detects a packet of video content450that matches specific profile information430, network device130may trigger creation of a dedicated bearer (e.g., based on specific profile information430) for user device110in the wireless access network provided by base station120and/or network device130. After creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on specific profile information430) to video content450(e.g., to new packets and to queued packets of video content450) in order to create video content (e.g., with the QoS guarantees)470. Network device130may provide video content (e.g., with the QoS guarantees)470to base station120, and base station120may provide video content (e.g., with the QoS guarantees)470to user device110(e.g., to STB110).

As illustrated inFIG. 9, process900may include receiving a video content request from a fixed user device connected to a LTE network (block910), and providing the video content request to a content provider (block920). For example, in implementations described above in connection withFIG. 3, a user (not shown) may utilize user device110to generate request310for video content to be displayed on user device110. User device110may wirelessly provide video content request310to base station120, and base station120may forward video content request310to network device130. Network device130may forward video content request310to video content provider160(e.g., via network150, not shown).

As further shown inFIG. 9, process900may include receiving a trigger for creating a dedicated bearer for the user device, in the LTE network, based on traffic parameters associated with the video content request (block930), and creating the dedicated bearer for the user device based on the trigger (block940). For example, in implementations described above in connection withFIG. 5, dedicated bearer creator510of network device130may receive trigger330to create a dedicated bearer (e.g., based on traffic parameters320provided via trigger330) for user device110in the wireless access network provided by base station120and/or network device130. Dedicated bearer creator510may provide trigger330to base station120so that base station120may create the dedicated bearer for user device110.

Returning toFIG. 9, process900may include receiving video content from the content provider based on the video content request (block950), providing QoS treatment to the video content based on the traffic parameters (block960), and providing, to the user device via the LTE network, the video content with the QoS parameters (block970). For example, in implementations described above in connection withFIG. 3, video content provider160may search for the requested video content (e.g., provided via video content request310), and may provide the requested video content340to network device130. After creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on traffic parameters320) to video content340in order to create video content (e.g., with the QoS guarantees)350. Network device130may provide video content (e.g., with the QoS guarantees)350to base station120, and base station120may provide video content (e.g., with the QoS guarantees)350to user device110(e.g., to STB110).

As illustrated inFIG. 10, process1000may include receiving subscriber profile information for a fixed user device when the user device connects to a LTE network (block1010), receiving a video content request from the fixed user device connected to the LTE network (block1020), and providing the video content request to a content provider (block1030). For example, in implementations described above in connection withFIG. 4, when the user (e.g., via STB110) attaches to the wireless access network, profile information430for the specific user may be provided by policy control function140to network device130. The user may also utilize user device110(e.g., STB110) to generate request440for video content to be displayed on user device110. User device110may wirelessly provide video content request440to base station120, and base station120may forward video content request440to network device130. Network device130may forward video content request440to video content provider160(e.g., via network150, not shown).

As further shown inFIG. 10, process1000may include receiving video content from the content provider based on the video content request (block1040), and creating a dedicated bearer for the user device when the video content matches the subscriber profile information (block1050). For example, in implementations described above in connection withFIG. 4, network device130may receive video content450(e.g., packets of video content450), and may determine whether packets of video content450match specific profile information430received from policy control function140. When network device130detects a packet of video content450that matches specific profile information430, network device130may trigger creation of a dedicated bearer (e.g., based on specific profile information430) for user device110in the wireless access network provided by base station120and/or network device130, as indicated by reference number460.

Returning toFIG. 10, process1000may include providing QoS treatment to the video content based on the subscriber profile information (block1060), and providing, to the user device via the LTE network, the video content with the QoS parameters (block1070). For example, in implementations described above in connection withFIG. 4, after creation of the dedicated bearer for user device110, network device130may assign or provide QoS parameters or guarantees (e.g., based on specific profile information430) to video content450(e.g., to new packets and to queued packets of video content450) in order to create video content (e.g., with the QoS guarantees)470. Network device130may provide video content (e.g., with the QoS guarantees)470to base station120, and base station120may provide video content (e.g., with the QoS guarantees)470to user device110(e.g., to STB110).

Systems and/or methods described herein may provide QoS guarantees to video content delivered to fixed user devices over wireless access networks. The systems and/or methods may extend policy control capabilities of the wireless access network so that policies for QoS delivery are simplified.

For example, while series of blocks have been described with regard toFIGS. 7-10, the order of the blocks may be modified in other implementations. Further, non-dependent blocks may be performed in parallel.

Further, certain portions of the invention may be implemented as a “component” that performs one or more functions. These components may include hardware, such as an ASIC or a FPGA, or a combination of hardware and software.