Patent Application
20170202004
The present disclosure relates to resource scheduling for a wireless communications network. Specifically, the present disclosure relates to resource scheduling for a wireless communications network in order to ensure one or more transfers of data content are completed before a specified transfer deadline.
Wireless communications networks continue to provide access to an increasing number of resources and services. In many cases, a resource or service may demand a minimum quality of service (QoS) in order to deliver a desirable user experience. For example, real-time multimedia applications such as audio streaming, video streaming, and voice over internet protocol (VoIP) communications may demand a relatively high QoS in order to avoid delays in the delivery of content, which may be highly disruptive to an end user. Generally, radio resources in a wireless communications network are allocated via the establishment of one or more radio access bearers (RABs) between a radio access node and a wireless communications device. Each RAB is assigned certain QoS parameters, which are used by a scheduler in the radio access node to ensure that a minimum QoS is delivered for traffic over the RAB.
In an LTE network, one or more evolved RABs (E-RABs) may be established in what is known as an attach procedure, as illustrated in the call flow diagram shown in
A create session response is then sent from the P-GW 18 to the S-GW 16, which contains the QoS information for the requested resource or service and an IP address for the UE 10 (step 116). The create session response is forwarded from the S-GW 16 to the MME 14 (step 118). If the QoS parameters for the create session response indicate that a guaranteed bitrate (GBR) E-RAB is to be established, the MME 14 together with the eNB 12 may then perform admission control to determine if the necessary resources are present to establish a bearer with the required QoS. If the necessary resources are available, and/or if the QoS parameters for the bearer indicate that a non-GBR bearer is to be established, an attach accept message is sent from the MME 14 to the eNB 12 and the S-GW 16 (step 120). The attach message is forwarded from the eNB 12 to the UE 10 (step 122). In response to the attach message, the UE 10 sends and acknowledgement message (step 124), at which point in time an E-RAB is established between the UE 10 and the P-GW 18. Additional messages may then be exchanged between one or more network nodes in the LTE network order to complete the attach process.
The QoS parameters for the E-RAB are generally indicated by a QoS class identifier (QCI), which may define a resource type (GBR or non-GBR), a priority, a packet delay budget (PDB), a packet error loss rate (PELR), a guaranteed uplink/downlink bitrate, and a maximum uplink/downlink bitrate for the E-RAB. Generally, a QCI represents a preconfigured QoS for a wide range of resources and/or services that may be accessed via a particular E-RAB. Based on one or more of the QoS parameters in a QCI for a particular E-RAB, radio resources in a wireless communications network are scheduled. One common scheduling strategy known as delay-based scheduling involves increasing the priority of a packet as the time the packet has spent in a scheduling queue starts to approach the specified PDB for traffic on the E-RAB. While effective in some applications, a delay-based scheduling strategy based on the QoS parameters discussed above is not well suited to transfers of data content that must be finished before a certain transfer deadline. Further, such a delay-based scheduling strategy is generally over-aggressive, often scheduling radio resources unnecessarily and therefore overburdening a wireless communications network.
Accordingly, there is a present need for a scheduling strategy capable of ensuring that one or more transfers of data content can complete before a transfer deadline, while simultaneously increasing the efficiency of radio resource allocation in a wireless communications network.
Systems and methods related to resource scheduling for a wireless communications network in order to ensure one or more transfers of data content are completed before a specified transfer deadline are disclosed. In one embodiment, a method of operating a radio access node for a wireless communications network includes the steps of obtaining a minimum transfer bitrate for a transfer of data content between the radio access node and a wireless communications device, and scheduling one or more radio resources for the transfer of the data content based on the minimum transfer bitrate. The minimum transfer bitrate is calculated based on a total volume of the data content and a transfer deadline for the transfer of the data content. By using the minimum transfer bitrate to schedule one or more radio resources for the transfer of the data content, the transfer of the data content can be completed before the transfer deadline. Further, by calculating the minimum transfer bitrate based on the data volume and the transfer deadline, the efficiency of radio resource allocation for the transfer of the data content can be increased.
In one embodiment, an updated minimum transfer bitrate is obtained, and one or more radio resources for the transfer of the data content are scheduled based on the updated minimum transfer bitrate. The updated minimum transfer bitrate is calculated based on an estimate of the remaining portion of the total volume of the data content to be transferred and the transfer deadline for the transfer of the data content. By scheduling one or more radio resources for the transfer of the data content based on the updated minimum transfer bitrate, the efficiency of radio resource allocation for the transfer of the data content can be increased, while simultaneously ensuring that the transfer of the data content is completed before the transfer deadline.
In one embodiment, obtaining the minimum transfer bitrate includes receiving the minimum transfer bitrate from a network node in a core network associated with the radio access node.
In one embodiment, obtaining the minimum transfer bitrate includes receiving the total volume of the data content and the transfer deadline from a network node in a core network associated with the radio access node, and calculating the minimum transfer bitrate based on the total volume of the data content and the transfer deadline.
In one embodiment, the radio access node is an evolved node B (eNB), and the associated core network is an evolved packet core (EPC) network.
In one embodiment, a method of operating a core network associated with a wireless communications network includes the steps of obtaining a total volume of data content for a transfer of the data between a radio access node and a wireless communications device in the wireless communications network, obtaining a transfer deadline for the transfer of the data content, calculating a minimum transfer bitrate for the transfer of the data content based on the total volume of the data content and the transfer deadline, and communicating the minimum transfer bitrate to the radio access node in the wireless communications network.
In one embodiment, a method of operating a core network associated with a wireless communications network includes the steps of obtaining a total volume of data content for a transfer of the data content between a radio access node and a wireless communications device in the wireless communications network, obtaining a transfer deadline for the transfer of the data content, and communicating the total volume of the data content and the transfer deadline to the radio access node.
Those skilled in the art will appreciate the scope of the present disclosure and realize additional aspects thereof after reading the following detailed description of the embodiments in association with the accompanying drawing figures.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
The S-GW 36 is connected to the E-UTRAN 26 via an S1-U data connection. The MME 38 is connected to the E-UTRAN 26 via an S1-MME control connection. The S-GW 36 and the MME 38 are connected to one another via an S11 control connection. The S-GW 36 and the P-GW 40 are connected to one another via an S5 data connection. The P-GW 40 and the PCRF 42 are connected to one another via a Gx control connection. The P-GW 40 is connected to the PDN 30, and thus the AF 44, via an SGi data connection. Finally, the PCRF 42 is connected to the PDN 30, and thus the AF 44, via an Rx control connection, and is connected to the S-GW 36 via a Gxc control connection. Notably, the Rx control connection may be between the AF 44 and the PCRF 42, e.g., via the PDN 30.
The S-GW 36 serves as the main node responsible for connecting the E-UTRAN 26 to the EPC network 28 and acts as a mobility anchor for the UE 34 as the UE 34 moves between eNBs 32 in the E-UTRAN 26. The MME 38 is responsible for managing bearers, handling UE 34 transitions, and performing authentication of the UE 34. The P-GW 40 connects the EPC network 28 to the PDN 30 and performs such functions as allocating IP addresses and enforcing QoS rules provided by the PCRF 42. The PCRF 42 is generally responsible for QoS handling and charging.
As discussed above, a particular resource or service may demand a minimum quality of service (QoS) in order to deliver a desirable user experience in the LTE communications network 24. In particular, it may be desirable for a transfer of data content associated with a resource or service to complete before a specified transfer deadline. Conventional delay-based scheduling strategies rely on one or more QoS parameters in a QoS class identifier (QCI), which are not individually tailored to a particular transfer of data content. Such a generalization of QoS parameters is unsuited to ensuring that one or more transfers of data content are completed before a transfer deadline, and further may result in the inefficient allocation of radio resources in a wireless communications network due to the unnecessary scheduling and/or prioritization of radio resources for a requested resource and/or service. Specifically, a delay-based scheduling strategy generally only looks at each packet of a larger set of data content to determine if the QoS parameters have been met, and is incapable of viewing the overall context of the transfer of the data content. Further, delay-based scheduling is based on the generalized QoS parameters discussed above, and is thus not tailored to any specific transfer of data content. Accordingly, a delay-based scheduling strategy may fail to ensure that a transfer of data content is completed before a transfer deadline, and further result in sub-optimal use of radio resources. Additionally, current E-RAB setup procedures establish a single QoS, which is used for the life of the E-RAB. As a result, different transfers of data content using the same E-RAB must use the same QoS parameters, which once again may result in sub-optimal use of radio resources for the same reasons discussed above.
Next, a minimum transfer bitrate for the transfer of the data is calculated (step 204). Notably, the minimum transfer bitrate is calculated based on the total volume of the data content and the transfer deadline. In one embodiment, the minimum transfer bitrate is calculated by dividing the total volume of the data content by the amount of time until the transfer deadline occurs. Calculating the minimum transfer bitrate based on the total volume of the data content and the transfer deadline results in an accurate measurement of the radio resources that should be dedicated to the transfer of the data content in order to ensure that the transfer of the data content is completed before the transfer deadline, which may subsequently be used to efficiently allocate radio resources for the transfer of the data content. Finally, the minimum transfer bitrate is communicated to the radio access node (step 206).
Communicating the minimum transfer bitrate to the radio access node may occur in a variety of ways. In one embodiment, the minimum transfer bitrate is communicated to the radio access node via one or more in-band messages. As discussed herein, in-band messages refer to messages sent alongside data associated with requested resources and/or services. For example, in-band messages may refer to messages sent via the data connections S1-U, S5, and/or SGi, shown in
Communicating the minimum transfer bitrate to the radio access node via one or more out-of-band control messages may include sending the minimum transfer bitrate in an information element (IE) included in an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message. While not essential, details of the INITIAL CONTEXT SETUP REQUEST, the E-RAB SETUP, the E-RAB MODIFY, and the HANDOVER REQUEST messages are discussed in 3GPP Technical Specification 36.413, version 12.1.0, sections 8.2-8.4, which are herein incorporated by reference in their entirety. Notably, an INITIAL CONTEXT SETUP REQUEST, an E-RAB SETUP, an E-RAB MODIFY, and a HANDOVER REQUEST message may include a guaranteed bitrate (GBR) quality of service (QoS) information IE, which can be used to communicate the minimum transfer bitrate. Accordingly, communicating the minimum transfer bitrate may include communicating the minimum transfer bitrate in a GBR QoS information IE included in one of an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message.
While not essential, details of the GBR QoS Information IE are discussed in 3GPP Technical Specification 36.413, version 12.1.0, section 9.2.1.18, which is herein incorporated by reference in its entirety. Generally, a GBR QoS Information IE is used to communicate configuration parameters for the establishment of GBR E-RABs, which are subsequently used by an eNB in an admission control process to determine whether or not resources exist for the establishment of the particular E-RAB. In other words, messages relating to the establishment of non-GBR E-RABs generally do not include a GBR QoS Information IE. In some embodiments, the present disclosure proposes to use the GBR QoS Information IE to communicate the minimum transfer bitrate regardless of whether the particular E-RAB used for the transfer of the data content is a GBR E-RAB or a non-GBR E-RAB.
Next, one or more radio resources for the transfer of the data content are scheduled by the radio access node based on the minimum transfer bitrate (step 302). By using the minimum transfer bitrate to schedule one or more radio resources in the radio access node, the transfer of the data content may be completed before the transfer deadline, while improving the efficiency of radio resource usage in the radio access node.
In order to ensure that the transfer of the data content is completed before the transfer deadline and that radio resources are efficiently allocated in the radio access node, it may be desirable to update the minimum transfer bitrate during the course of the transfer of the data content. This process may be used to update the minimum transfer rate obtained in the process of
Next, one or more radio resources for the transfer of the data content are scheduled by the radio access node based on the updated minimum transfer bitrate (step 402). By using the updated minimum transfer bitrate to schedule one or more radio resources in the radio access node, the transfer of data content may be completed before the transfer deadline, while improving the efficiency of radio resource usage in the radio access node by allowing the radio access node to allocate the resources not needed to fulfill the minimum transfer bitrate to other services.
As discussed above, the parameters included in a GBR QoS Information IE are generally used to perform admission control for the establishment of GBR E-RABs; however, in some embodiments, the present disclosure proposes using the GBR QoS Information IE to communicate a minimum transfer bitrate for a transfer of data content regardless of whether the particular E-RAB used for the transfer of the data content is a GBR E-RAB or a non-GBR E-RAB. Accordingly,
A minimum transfer bitrate for a transfer of data content is then obtained by the radio access node (step 502). In one embodiment, the minimum transfer bitrate for the transfer of the data content is obtained by extracting the minimum transfer bitrate from a GBR QoS Information IE in the E-RAB control message, as discussed above. The radio access node then checks if the E-RAB control message indicates that a GBR E-RAB is to be established or modified for the transfer of the data content (step 504). If a GBR E-RAB is indicated, an admission control procedure is performed by the radio access node, in which the radio access node checks if it has the necessary radio resources to provide the desired QoS parameters for the E-RAB (step 506). If the admission control process indicates that the radio access node has the available resources for the E-RAB, one or more radio resources for the transfer of the data content are scheduled based on the minimum transfer bitrate (step 508). If the admission control process indicates that the radio access node does not have the available resources for the E-RAB, the E-RAB is either terminated or not modified, and the process ends. As discussed above, the present disclosure proposes using a GBR QoS Information IE to communicate the minimum transfer bitrate for the transfer of the data content regardless of whether the E-RAB for the transfer of the data content is a GBR E-RAB or a non-GBR E-RAB. Accordingly, even if the radio access node determines that the E-RAB to be established or modified for the transfer of the data content is indicated as a non-GBR E-RAB, the minimum transfer bitrate extracted from the GBR QoS Information IE is still used to schedule one or more radio resources for the transfer of the data content (step 510).
The eNB 32 forwards the request for the transfer of the data content to the S-GW 36 (step 602), which in turn forwards the request to the P-GW 40 (step 604). The P-GW 40 then forwards the request for the transfer of the data content to the AF 44 (step 606). In one embodiment, the AF 44 is a caching node for a content delivery network (CDN). Accordingly, the AF 44 may include a cache of the requested data content (e.g., resulting from a pre-fetch procedure or a previous request for transfer of the data content). The AF 44 then determines if the transfer of the data content should be prioritized (step 608). In one embodiment, determining if the transfer of the data content should be prioritized includes checking one or more preconfigured QoS recommendations for the requested data content, and determining if the data content should be transferred before a transfer deadline in order to ensure a desirable user experience. If the transfer of the data content should not be prioritized, the LTE communications network 24 may proceed to operate normally.
If the transfer of the data content should be prioritized, a total volume of the data content is obtained by the AF 44 (step 610). Since the AF 44 may include a cache of the requested data content as discussed above, the AF 44 may already know the total volume of the data content based on the total size of the cache associated with the data content. In one embodiment, the total volume of the data content is obtained by accessing historical information regarding one or more previous transfers of the data content. However, any suitable technique may be used to obtain the total volume of the data content locally at the AF 44 or to obtain the total volume of the data content from, e.g., another network node. A transfer deadline for the transfer of the data content is also obtained by the AF 44 (step 612). The transfer deadline may be based on the particular data content requested by the UE 34, as different resources and/or services may require a different QoS in order to maintain a desirable user experience. In one embodiment, the transfer deadline is determined based upon one or more preconfigured QoS recommendations for a particular resource and/or service, which are stored by the AF 44.
A minimum transfer bitrate for the transfer of the data content is then calculated based on the total volume of the data content and the transfer deadline (step 614). In one embodiment, the minimum transfer bitrate for the transfer of the data content is calculated by dividing the total volume of the data content by the amount of time remaining until the transfer deadline. As discussed above, calculating the minimum transfer bitrate in this way results in an accurate measurement of the radio resources that should be dedicated to the transfer of the data content in order to ensure that the transfer of the data content is completed before the transfer deadline, which may subsequently be used to efficiently allocate radio resources for the transfer of the data content. The minimum transfer bitrate is then communicated from the AF 44 to the PCRF 42 (step 616). In one embodiment, the minimum transfer bitrate is communicated from the AF 44 to the PCRF 42 via a GBR QoS Information IE, such as in an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message, as discussed in detail above. Since, the GBR QoS IE is already well defined for LTE communications networks, using the GBR QoS Information IE may provide a convenient way to communicate the minimum transfer bitrate between the various network nodes.
The PCRF 42 then forwards the minimum transfer bitrate to the S-GW 36 (step 618), which in turn forwards the minimum transfer bitrate to the MME 38 (step 620). The MME 38 forwards the minimum transfer bitrate to the eNB 32 (step 622). The eNB 32 then schedules one or more radio resources for the transfer of the data content based on the minimum transfer bitrate (step 624). As discussed above, using the minimum transfer bitrate to schedule one or more radio resources for the transfer of the data content allows for a more efficient allocation of radio resources when compared to conventional methods. The data content is then transferred from the AF 44 to the P-GW 40 (step 626), from the P-GW 40 to the S-GW 36 (step 628), from the S-GW 36 to the eNB 32 (step 630), and finally from the eNB 32 to the UE 34 (step 632).
Throughout the transfer of the data content, it may become apparent, for example, due to changes in network conditions, that the minimum transfer bitrate is either too slow or too fast. If the minimum transfer bitrate is too slow, the transfer of the data content will not finish before the transfer deadline, thereby degrading the quality of the user experience for the particular resource and/or service the data content is associated with. If the minimum transfer bitrate is too fast, the efficiency of radio resource allocation in the E-UTRAN 26 may suffer. Accordingly, it may be desirable to update the minimum transfer bitrate one or more times throughout the transfer of the data content.
The updated minimum transfer bitrate is then communicated from the AF 44 to the PCRF 42 (step 704), from the PCRF 42 to the S-GW 36 (step 706), from the S-GW 36 to the MME 38 (step 708), and from the MME 38 to the eNB 32 (step 710). As discussed above, the updated minimum transfer bitrate may also be communicated in a GBR QoS Information IE. Since the E-RAB for the transfer of the data content is already established at this point in time, the GBR QoS Information IE may be communicated in an E-RAB MODIFY message. The eNB 32 then schedules one or more radio resources for the transfer of the data content based on the updated minimum transfer bitrate (step 712). Finally, the data content is transferred from the AF 44 to the P-GW 40 (step 714), from the P-GW 40 to the S-GW 36 (step 716), from the S-GW 36 to the eNB 32 (step 718), and from the eNB 32 to the UE 34 (step 720).
Updating the minimum transfer bitrate throughout the transfer of the data content ensures that the data content will be transferred to the UE 34 before the transfer deadline. Further, updating the minimum transfer bitrate throughout the transfer of the data content results in the efficient allocation of radio resources in the E-UTRAN 26, because periodically updating the minimum transfer bitrate prevents overscheduling of radio resources for the transfer of the data content.
In the embodiments discussed above, a minimum transfer bitrate for a transfer of data content is calculated by a core network node in a core network associated with a wireless communications network, and communicated to a radio access node in the wireless communications network. In some embodiments, however, it may be desirable to calculate the minimum transfer bitrate at the radio access node itself. Accordingly,
As discussed above, communicating the total volume of the data content and the transfer deadline to the radio access node may occur in a variety of ways. In one embodiment, the total volume of the data content and the transfer deadline are communicated to the radio access node via one or more in-band messages. In an additional embodiment, the total volume of the data content and the transfer deadline are communicated to the radio access node via one or more out-of-band control messages, for example, by a GBR QoS Information IE in an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message. In other embodiments, the total volume of the data content and the transfer deadline are communicated to the radio access node via proprietary signaling.
Next, the radio access node obtains a transfer deadline for the transfer of the data content (step 1002). Once again, the transfer deadline may be obtained by extracting the transfer deadline from a GBR QoS Information IE within an INITIAL CONTEXT SETUP REQUEST, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message received from an associated core network node, such as the core network node discussed with respect to
The radio access node then calculates a minimum transfer bitrate for the transfer of the data content based on the total volume of the data content and the transfer deadline (step 1004). In one embodiment, the minimum transfer bitrate is calculated by dividing the total volume of the data content by the time remaining until the transfer deadline. Calculating the minimum transfer bitrate based on the total volume of the data content and the transfer deadline allows an accurate measurement of the radio resources that should be dedicated to the transfer of the data content in order to ensure that the transfer of the data content is completed before the transfer deadline to be obtained. Finally, the radio access node schedules one or more radio resources for the transfer of the data content based on the minimum transfer bitrate (step 1006). Using the minimum transfer bitrate to schedule one or more radio resources for the transfer of the data content results in efficient allocation of radio resources in the wireless communications network.
As discussed above, it may be desirable to update the minimum transfer bitrate during the course of the transfer of the data content. Accordingly,
The radio access node then calculates an updated minimum transfer bitrate for the transfer of the data content based on the remaining portion of the total volume of the data content to be transferred and the transfer deadline (step 1102). In one embodiment, calculating the updated minimum transfer bitrate for the transfer of the data content includes dividing the remaining portion of the total volume of the data content to be transferred by the amount of time remaining until the transfer deadline. Finally, one or more radio resources for the transfer of the data content are scheduled by the radio access node based on the updated minimum transfer bitrate (step 1104). By using the updated minimum transfer bitrate to schedule one or more radio resources in the radio access node, the transfer of data content may be completed before the transfer deadline, while improving the efficiency of radio resource usage in the radio access node by allowing the radio access node to dynamically change the minimum transfer bitrate based on network conditions.
If the transfer of the data content should be prioritized, a total volume of the data content is obtained by the AF 44 (step 1210). Since the AF 44 may include a cache of the requested data content as discussed above, the AF 44 may already know the total volume of the data content based on the size of the cache associated with the data content. In one embodiment, the total volume of the data content is obtained by accessing historical information about one or more previous transfers of the data content. A transfer deadline for the transfer of the data content is then obtained by the AF 44 (step 1212). The transfer deadline may be based on the particular data content requested by the UE 34, as different resources and/or services may require different QoS in order to maintain a desirable user experience. The total volume of the data content and the transfer deadline are then communicated from the AF 44 to the PCRF 42 (step 1214). In one embodiment, the total volume of the data content and the transfer deadline are communicated from the AF 44 to the PCRF 42 via a GBR QoS Information IE, such as in an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message, as discussed in detail above. The total volume of the data content and the transfer deadline are then forwarded form the PCRF 42 to the S-GW 36 (step 1216), from the S-GW 36 to the MME 38 (step 1218), and from the MME 38 to the eNB 32 (step 1220).
The eNB 32 then calculates a minimum transfer bitrate for the transfer of the data content based on the total volume of the data content and the transfer deadline (step 1222). Calculating the minimum transfer bitrate for the transfer of the data content may include dividing the total volume of the data content by the time remaining until the transfer deadline. Based on the minimum transfer bitrate, the eNB 32 schedules one or more radio resources for the transfer of the data content (step 1224). As discussed above, using the minimum transfer bitrate to schedule one or more radio resources for the transfer of the data content allows for a more efficient allocation of radio resources when compared to conventional methods. The data content is then transferred from the AF 44 to the P-GW 40 (step 1226), from the P-GW 40 to the S-GW 36 (step 1228), from the S-GW 36 to the eNB 32 (step 1230), and finally from the eNB 32 to the UE 34 (step 1232).
As discussed above, it may become apparent during the transfer of the data content, for example, due to changes in network conditions, that the minimum transfer bitrate is either too slow or too fast. Accordingly, it is desirable to update the minimum transfer bitrate one or more times throughout the transfer of the data content.
The eNB 32 then calculates an updated minimum transfer bitrate based on the remaining portion of the total volume of the data content to be transferred (step 1310). In one embodiment, the updated minimum transfer bitrate may be calculated by dividing the remaining portion of the total volume of the data to be transferred by the time remaining until the transfer deadline. The eNB 32 then schedules one or more radio resources for the transfer of the data content based on the updated minimum transfer bitrate (step 1312). Finally, the data content is transferred from the AF 44 to the P-GW 40 (step 1314), from the P-GW 40 to the S-GW 36 (step 1316), from the S-GW 36 to the eNB 32 (step 1318), and from the eNB 32 to the UE 34 (step 1320).
Updating the minimum transfer bitrate throughout the transfer of the data content ensures that the data content will be transferred to the UE 34 before the transfer deadline. Further, updating the minimum transfer bitrate throughout the transfer of the data content results in the efficient allocation of radio resources in the E-UTRAN 26.
As discussed above, the core network node in the core network associated with the wireless communications network may be a caching node for a CDN, the basic functionality of which is described in the call flow diagram shown in
A requesting device 50 then makes a DNS query for the pre-fetched data content (e.g., www.cp.com) to a local DNS server 52 (step 1402). The Local DNS server 52 then forwards the DNS query to a DNS server associated with the requested data content 54 (step 1404). The DNS server associated with the requested data content 54 then provides a DNS reply to the local DNS server 52, which includes a canonical name reference (CNAME) directing to a DNS server associated with the CDN (CDN DNS) 56 (step 1406). The local DNS server 52 then makes an additional DNS query to the CDN DNS 56 (step 1408). The CDN DNS 56 replies to the local DNS server 52 with an IP address for an optimal content delivery server, for example, a CDN caching node 46 (step 1410), which is then forwarded from the local DNS server 52 to the requesting device 50 (step 1412). The requesting device 50 then uses the IP address of the CDN caching node 46 to request a desired data content from the CDN caching node 46 (step 1414). In one embodiment, the request is a hypertext transport protocol (HTTP) GET request, however, any suitable request format may be used without departing form the principles of the present disclosure. The CDN caching node 46 then replies to the response by delivering the requested data content to the requesting device 50.
Because a CDN caching node is aware of the total volume of data content for a particular requested resource and/or service, and because a CDN caching node may be familiar with one or more desired QoS parameters for a particular requested resource and/or service, a CDN caching node may be suited to perform one or more operations of the methods described above. Accordingly,
The UE 34 then initiates a request for a transfer of the data content (step 1502). In one embodiment, the request is an HTTP GET request for one or more resources associated with the website discussed above. The request is then forwarded from the eNB 32 to the S-GW 36 (step 1504), from the S-GW 36 to the P-GW 40 (step 1506), and from the P-GW 40 to the CDN caching node 58 (step 1508). The CDN caching node 58 then obtains a minimum transfer bitrate for the transfer of the data content (step 1510). In one embodiment, the minimum transfer bitrate is calculated based on a total data volume of the data content and a transfer deadline for the transfer of the data content, as discussed above. The minimum transfer bitrate is then communicated from the CDN caching node 58 to the PCRF 42 (step 1512), from the PCRF 42 to the S-GW 36 (step 1514), from the S-GW 36 to the MME 38 (step 1516), and from the MME 38 to the eNB 32 (step 1518). In one embodiment, the minimum transfer bitrate is communicated in the LTE communications network 24 via a GBR QoS Information IE, such as within an INITIAL CONTEXT SETUP, an E-RAB SETUP, an E-RAB MODIFY, or a HANDOVER REQUEST message, as discussed above.
The eNB 32 then schedules one or more radio resources for the transfer of the data content (step 1520). As discussed above, using the minimum transfer bitrate to schedule one or more radio resources for the transfer of the data content allows for a more efficient allocation of radio resources when compared to conventional methods. Finally, the data content is transferred from the CDN caching node 58 to the P-GW 40 (step 1522), from the P-GW 40 to the S-GW 36 (step 1524), from the S-GW 36 to the eNB 32 (step 1526), and from the eNB 32 to the UE 34 (step 1528).
In the embodiments discussed above, various operations are described in a number of discrete steps, which appear in a particular order. However, the present disclosure is not so limited. The various operations described above in any of the embodiments may be further broken down into additional steps, or may be combined together into a single discrete step. Further, the various operations need not be performed in the order of presentation unless explicitly stated otherwise.
In one embodiment, a computer program including instructions, which, when executed by at least one processor, cause the at least one processor to carry out the functionality of the radio access node 62 according to any one of the embodiments described herein is provided. In one embodiment, a carrier containing the aforementioned computer program product is provided. The carrier may be one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable storage medium such as the memory 66).
In one embodiment, a computer program including instructions, which, when executed by at least one processor, cause the at least one processor to carry out the functionality of the core network node 74 according to any one of the embodiments described herein is provided. In one embodiment, a carrier containing the aforementioned computer program product is provided. The carrier may be one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable storage medium such as the memory 78).
The following acronyms are used throughout this disclosure.
Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2014/062638 | 6/26/2014 | WO | 00 |
