WO2018084844A1

WO2018084844A1 - Quality of service management

Info

Publication number: WO2018084844A1
Application number: PCT/US2016/060320
Authority: WO
Inventors: John Harris; Yang Shen
Original assignee: Nokia Technologies Oy; Nokia Usa Inc.
Priority date: 2016-11-03
Filing date: 2016-11-03
Publication date: 2018-05-11

Abstract

Various communication systems may benefit from an improved quality of service management. For example, communication systems can benefit from a more dynamic quality of service management at the user equipment. A method, in certain embodiments, may include enforcing at a user equipment an initial self-imposed quality of service limitation. The method may also include determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service limitation. In addition, the method may include transmitting a notification of the temporary quality of service level to a network entity.

Description

TITLE:

QUALITY OF SERVICE MANAGEMENT

BACKGROUND:

Field:

[0001] Various communication systems may benefit from an improved quality of service management. For example, communication systems can benefit from a more dynamic quality of service management at the user equipment.

Description of the Related Art:

[0002] The use of software based applications has become ubiquitous among users of smartphones and other user devices. Each individual software based application may demand a different quality of service (QoS) level in accordance with the service being offered by the application. The increasing use of software based applications has also led to an increased consumer expectation of QoS reliability.

[0003] In Third Generation Partnership Project (3 GPP) Universal Mobile Telecommunications System (UMTS) technology, such as Third Generation (3G), Long Term Evolution (LTE), or LTE advanced (LTE-A), a policy and charging rules function (PCRF) may be used for QoS management. When the PCRF is triggered by a network event detected by the UE to modify the QoS level, significant delays and/or overhead is required for each modification. These significant delays and/or overhead will hinder the user device from achieving the proper QoS levels used by various software based applications.

SUMMARY:

[0004] A method, in certain embodiments, may include enforcing at a user equipment an initial self-imposed quality of service level. The method may also include determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level. In addition, the method may include transmitting a notification of the temporary quality of service level to a network entity.

[0005] According to certain embodiments, an apparatus may include at least one memory including computer program code, and at least one processor. The at least one memory and the computer program code may be configured, with the at least one processor, at least to enforce at a user equipment an initial self-imposed quality of service level. The at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to determine at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level. In addition, the at least one memory and the computer program code may be configured, with the at least one processor, at least to transmit a notification of the temporary quality of service level to a network entity.

[0006] An apparatus, in certain embodiments, may include means for enforcing at a user equipment an initial self-imposed quality of service level. The apparatus also includes means for determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level. In addition, the apparatus may include means for transmitting a notification of the temporary quality of service level to a network entity.

[0007] According to certain embodiments, a non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process. The process may include enforcing at a user equipment an initial self-imposed quality of service level. The process may also include determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level. In addition, the process may include transmitting a notification of the temporary quality of service level to a network entity.

[0008] According to certain embodiments, a computer program product encoding instructions for performing a process according to a method including enforcing at a user equipment an initial self-imposed quality of service level. The method may also include determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level. In addition, the method may include transmitting a notification of the temporary quality of service level to a network entity.

[0009] A method, in certain embodiments, may include detecting at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment. The method may also include determining at the network entity whether or not to constrain the detected temporary quality of service level.

[0010] According to certain embodiments, an apparatus may include at least one memory including computer program code, and at least one processor. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to detect at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment. The at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to determine at the network entity whether or not to constrain the detected temporary quality of service level.

[0011] An apparatus, in certain embodiments, may include means for detecting at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment. The apparatus may also include means for determining at the network entity whether or not to constrain the detected temporary quality of service level.

[0012] According to certain embodiments, a non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process. The process may include detecting at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment. The process may also include determining at the network entity whether or not to constrain the detected temporary quality of service level.

[0013] According to certain embodiments, a computer program product encoding instructions for performing a process according to a method including detecting at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment. The method may also determining at the network entity whether or not to constrain the detected temporary quality of service level.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0014] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0015] Figure 1 illustrates a system according to certain embodiments.

[0016] Figure 2 illustrates a flow diagram according to certain embodiments.

[0017] Figure 3 illustrates a flow diagram according to certain embodiments.

[0018] Figure 4 illustrates a system according to certain embodiments.

DETAILED DESCRIPTION:

[0019] Certain embodiments may allow for a near instantaneous and efficient modification of QoS levels at a user equipment as authorized by the network, thereby avoiding any significant delays and overhead. In particular, in some embodiments the user equipment (UE), or the software based applications that operate on the processor and memory of the UE, may demand a brief or intermittent increase in QoS levels. The brief or intermittent increase in QoS level may be within an upper limit of a QoS level authorized by the network. Once the increased QoS level is no longer be needed, for example after the expiration of a fixed time period, the QoS level may be restored to an initial QoS level. The embodiments described below therefore allow for self-managed dynamic QoS modifications at the UE.

[0020] In certain embodiment, a network entity, for example a PCRF, may impose a high maximum QoS limit on the UE. The UE may then self-impose an initial QoS level for uplink and/or downlink transmissions, which may be lower than the maximum QoS limit. The UE may in some embodiments self-impose a limited bit rate or QoS level on the uplink by utilizing a "leaky bucket" approach. In a "leaky bucket" approach, the UE may only allow for up to a maximum number of uplink data to be transmitted during each given time interval.

[0021] For example, in an embodiment involving an infinite or full buffer scenario, the UE may only allow for 1 megabit (Mb) per second of data to reach the UE uplink transmission input buffer. In such an embodiment, a buffer status report (BSR) may not report to the network the additional data which has not yet reached the UE uplink transmission input buffer, because it exceeds the allotted 1 Mb per second. The UE may only be able to transmit uplink data which has already been placed in the uplink transmission input buffer.

[0022] In another embodiment, the UE or the UE OS may self-impose a limited QoS level or bit rate on the downlink by limiting the amount of downlink data which may be requested during each time interval. For example, in an embodiment that involves streaming video applications, the UE or UE OS may constrain the bit rate of the video being downloaded to no more than 1 Mb per second. The UE or UE OS may therefore not request a higher bit rate, and instead request a less compressed version of the bit rate, which may result in the average downlink bit rate not exceeding 1 Mb per second over a given time interval.

[0023] In other words, the UE may self-impose an initial QoS level, such that the UE may only request a QoS level equal to or lower than the initial QoS level or rate, or use features associated with the initial QoS level. When a UE wishes to perform an operation that may utilize a higher QoS level than the self-imposed initial QoS level, the UE may temporarily remove the self-imposed limitation, and allow for a temporary higher level QoS. Both the initial QoS level and the temporary higher QoS level may be lower than the maximum QoS limit imposed by the network. Upon determining that the higher temporary QoS level, the UE may instantaneously change the bit rate limitation, and can subsequently notify the network of the temporary higher QoS level and/or for how long the use of the temporary higher QoS level may last.

[0024] The UE may in some embodiments immediately or instantaneously begin to utilize the higher QoS. The UE may then send a notification or a request to the network, informing the network of the higher QoS. The notification or request, however, may be sent to the network in parallel or subsequent to the immediate use of the higher QoS level by the UE. The network entity receiving the notification may then continue to enforce the same higher QoS level, which is now being used by the UE for downlink traffic.

[0025] In some embodiments, the UE may not notify the network entity of the QoS modification. In those embodiments, the network entity may detect the QoS modification without any notification from the UE. The network entity may then determine to constraint or suppress the modification when the UE is deemed to have performed an operation that may not be compliant.

[0026] This higher level of QoS or a higher bit rate may in some embodiments only be used for a finite period of time. The period of time may be determined by the UE itself or by the network, based on various factors. For example, the period of time may be determined at least by an amount of money the user of the UE may be willing to pay for the higher QoS level. Network operators, in some embodiments, may impose a variety of policies to determine how much the UE will pay for the higher QoS level. The policies may vary depending on the application, location, enterprise, and/or a subscription of the user equipment. In some embodiments the user of the UE may be asked to authorize a higher QoS level before the modification may be implemented.

[0027] Figure 1 illustrates a system according to certain embodiments. The system in Figure 1 includes both a user equipment 110, such as a mobile device or a smartphone, and a network entity 150, such as a base station of a policy control function. An operating system of the UE (UE OS) 120 and a modem 140 may also be included in UE 110. UE OS 120 may allow for the use of various software based applications and may house the transport control protocol (TCP). In some embodiments, modem 140 maybe an LTE modem.

[0028] UE function 130 may be placed between UE OS 120 and modem 140, and may be used to regulate the QoS level of UE 110. In some other embodiments, UE function 130 may be located in any other location of UE 110, including in UE OS 120 or modem 140. UE function 130 may also be referred to as the "leaky bucket" or bit rate throttling function. Although the "leaky bucket" is illustrated as being located in the UE, are least one "leaky bucket" may also be located in the network. Different traffic types, such as voice or video, maybe divided into different leaky buckets using logical channel groups (LCG). The UE may dynamically change the parameters of UE function 130 to temporarily boost the bit rate or the aggregate maximum bit rate (AMBR) of UE 110.

[0029] In certain embodiments, the UE OS may control the self-imposed QoS limitation, for example, a self-imposed AMBR. UE function 130 used to limit the QoS level may be placed between the UE OS and the Physical layer, as shown in Figure 1. During an uplink transmission, the UE function may be placed between the physical layer and the next higher layers on the downlink. During a downlink transmission, on the other hand, the TCP for example may be used to limit downloads, between the server and the UE. In other embodiments, the UE may directly indicate the buffer level of the UE to the software based application over an application programming interface (API). The UE OS may therefore be used to increase or reduce the QoS level of the UE during uplink and/or downlink transmissions.

[0030] As discussed above, a subscription management function, such as a home subscriber server (HSS), or a policy control function, such as a PCRF, may determine higher AMBR or QoS levels than the UE utilizes. The UE may then self-impose an initial QoS level that is below the higher AMBR or QoS level determined by the subscription management function or the policy control function. When the UE wants to temporarily use a higher QoS level than the self-imposed initial QoS level, the UE may temporarily remove the self-imposed QoS level, and begin using a higher AMBR. Although the temporary QoS level may be higher than the self-imposed QoS level, the temporary QoS level may be less than the QoS level determined by the subscription management function or policy control function. In some embodiments, the UE may send a notification or request to the policy control function asking permission to use the temporary higher QoS level. The policy control function may then authorize the use of the higher QoS level to accommodate the request. Before the request is authorized, in some embodiments the user of the UE may be asked to acknowledge the modification in the QoS level.

[0031] In certain embodiments, some UEs that are deemed to be trusted by the network and may partake in an expedited QoS management. Determining whether or not a UE is trusted may depend in part on the UE type or on past behavior of the UE. In expedited QoS management, UE type parameters may be defined in the subscription data. The subscription data management function, such as a HSS, may grant or authorize a higher UE QoS level for the UE sessions with certain UE types. In this expedited QoS management, an acknowledgment from the user of the UE may not be needed.

[0032] The UE, in some embodiments, can notify the policy control function of a start or stop time of the temporary higher QoS level through some network entities, such as a control plane function. The use of the higher QoS level may be charged to the user of the UE. In other words, the time interval in which the temporary QoS level is in use may be billed to the customer. For example, each byte transferred might deduct a certain number of bytes, such as two bytes, from a monthly byte allotment of the user.

[0033] The UE OS can in certain embodiments utilize knowledge of other subscribers and/or applications to determine the initial QoS limit, as well as the temporary higher QoS limit. For example, in a multi-subscription network environment, the UE OS may know that other users within a subscription group are nearby and/or are currently inactive. The UE OS may then determine whether to lower or to increase the QoS limitations based on the number of nearby and/or currently active users. If only a small number of users that is currently active, the initial QoS level at the UE may be lower than when a large number of users may be active.

[0034] In some embodiments, UEs may be tested and/or certified as complying with a certain UMTS standard. For example, a UE may be tested by the network and certified as being LTE compliant. The determination of whether a UE complies with a certain standard may be based on the device type. The device type may be determined at least from the international mobile equipment identification and software version number (IMEISV). The network entity testing for compliance may have access to a list of IMEISVs that indicates whether or not a given device may be compliant with a standard. The network may reject QoS modifications from UEs that are not compliant with a given standard.

[0035] The network entity may determine to constrain the temporary quality of service level at the UE. For example, the network may find that the UE is not compliant and/or that the network is experiencing a level of congestion that may be deemed high by the network entity. In other words, the network entity stops authorizing the UE for the temporary higher QoS usage. Existing network-based throttling mechanisms may also be used by the network entity to monitor the UE function 130 parameters used by UE 110.

[0036] Figure 2 illustrates a flow diagram according to certain embodiments. In particular, Figure 2 illustrates a method or process that may be performed by the UE to manage QoS level. The UE may be authorized by the network to self-manage or self-impose QoS levels. The network provides the UE with an upper limit or a maximum QoS limitation that the UE cannot exceed without requesting permission from the network. In step 210, the user equipment may enforce an initial self-imposing QoS level. In other words, the UE may self-impose an initial QoS level, such that the UE may only request the initial QoS level, or uses features associated with the initial QoS level. The initial self-imposing QoS level may be lower than the QoS level set by the network when self-management of the QoS level is not authorized. In other embodiments, the UE may determine the initial self-imposing QoS level.

[0037] In step 220, the UE may determine at the UE to utilize a temporary QoS level that is higher than the initial self-imposed QoS level. Both the temporary QoS level and the initial self-imposing QoS limitation may be authorized by the network entity during a packet data network (PDN) connection establishment. In some embodiments, the initial self-imposing QoS limitation and/or the temporary QoS level are lower than the maximum QoS level determined by the network entity. In other embodiments, however, the UE may request the network entity for authorization to temporarily exceed the maximum QoS level. Upon determining to utilize a temporary QoS level that is higher than the initial self-imposed QoS, the UE may immediately or instantaneously begin utilizing the higher QoS level. Immediately or instantaneously may refer to the first period in time after step 220 that it would be possible for the UE hardware to begin utilizing the higher QoS level.

[0038] In step 230, the UE may transmit a notification of the temporary QoS level to a network entity. The notification may be transmitted either in parallel or subsequent to the UE beginning to use the higher QoS level. In some embodiments, the UE may determine a time interval for using the temporary QoS level, and include the determined time interval in the sent notification or in a subsequent notification. In other embodiments, however, the UE may not send a notification, and the network entity may detect the change in QoS level without the notification. The UE may also inform the network of the start and/or stop times of the higher QoS levels. This information may be used by the network to determine a charge, for example in the form of a financial payment, to be imposed on the user of the UE for using the higher QoS level or bit rate level. As discussed above, the QoS levels may be a bit rate such as an aggregate maximum bit rate limitation. The limitation may apply for both uplink and/or downlink transmissions.

[0039] In some embodiments, the UE may have a guaranteed bit rate. When the UE has a guaranteed bit rate, for example a bit rate of 1 Mb per second, the network may guarantee that the UE will receive 1 Mb per second, even during intervals where there are variations in network congestion, and/or variations in UE signal strength. In contrast to a guaranteed bit rate, a UE having best effort services may observe a range of bit rates, none of which may be guaranteed. In embodiments involving a guaranteed bit rate, however, the UE may be guaranteed a bit rate of 1 Mb per second. The UE may also be authorized to self-manage the bit rate or QoS level so that the UE may instantaneously utilize a guaranteed bit rate up to 2 Mb per second.

[0040] For example, the UE may self-impose a limit that it may not perform a transfer faster than the guaranteed 1 Mb per second bit rate. However, during a shorter time interval when the UE, UE OS, or software based application operating on the UE hardware, may require a higher bit rate, the self-imposed limitation may change or modify such that the UE may allow itself to utilize 2 Mb per second. Within the network, the scheduler may prioritize scheduling the UE such that the UE may be guaranteed at least 2 Mb per second if the UE generates or utilizes 2 Mb per second. During the time periods in which the UE enforces the initial self-imposed QoS level, the UE may only generate 1 Mb per second, and the network may schedule 1 Mb per second.

[0041] In certain embodiments, upon determining that a higher temporary QoS level is needed, as shown in step 220, the user of the UE may be asked to authorize the use of the higher temporary QoS. The user may be notified or made aware through the UE itself that a higher charge will be assessed for the use of the higher temporary QoS level.

[0042] As shown in step 230, the UE transmits a notification to the network entity regarding the temporary QoS level. The transmission may occur in parallel to the UE beginning to use the higher QoS level. In other embodiments, the transmission may occur subsequent to the UE beginning to use the higher QoS level. The notification may be transmitted at least to any network entity included in the charging system, a policy control function, an entitlement server, or an application server. In other embodiments, the UE may transmit a request to the network entity to authorize an increased maximum QoS level. The UE may instantaneously, or nearly instantaneously, change the bit rate limitation from the initial QoS level to the higher temporary QoS level. The UE may then report to the network entity the start and/or stop time of the temporary higher QoS limit. The UE may also transmit a subsequent notification to restore the initial self-imposed QoS limitation.

[0043] Figure 3 illustrates a flow diagram according to certain embodiments. In particular, Figure 3 illustrates a network entity, such as a policy control function, a charging system, an entitlement server, or an application server that utilizes QoS management. In step 310, the network entity may determine a maximum QoS limit or an upper bit rate for the UE. The maximum QoS limit may be higher, in some embodiments, than both the initial self-imposed QoS level at the UE and the higher temporary QoS level determined by the UE. In other words, the network provides the UE with a higher AMBR or guaranteed bit rate (GBR) than those self-imposed or determined by the UE. The UE, therefore, may limit itself to a maximum bit rate less than the AMBR or GBR determined by the network entity.

[0044] In step 320, the network entity may detect a temporary QoS level that is higher than a self-imposed initial QoS level at the UE. In some embodiments, the UE may determine that it may want to exceed the initial QoS level and use a higher temporary QoS level. In such embodiments, the UE may send a request to the network entity for the temporary QoS level. The network entity may then determine whether or not to grant the temporary higher QoS level. In other embodiments, the UE may determine to use a higher QoS level, and may request the network entity of the higher QoS level. In other embodiments, the UE may merely notify the network entity of the higher QoS level, without explicitly requesting the network entity for permission. The notification by the UE may be sent to the network entity in parallel or subsequent to the initial utilization of the higher QoS level by the UE.

[0045] In step 330, the network entity may determine whether to constrain the temporary QoS level at the UE. In other words, in certain embodiments the network entity may determine to prevent the UE from using a temporary QoS level, while in other embodiments the network entity may authorize or not interfere with the use of a temporary QoS level. For example, when the UE may not be compliant with a standard or when the network experiences a high level of congestion, the network entity may constrain the QoS level used by the UE. In some embodiments, the network entity may configure the UE so that the initial QoS level and the temporary QoS may have the same value. [0046] The network entity may in certain embodiments monitor the UE QoS level or bit rate. For example, the network entity may use a pair of leaky buckets, one being larger than the other, that may both be located inside the network. The network entity may use the pair of leaky buckets to monitor for events in which UE traffic spills out of the network's smaller leaky bucket in to the second larger network leaky bucket. For example, a UE may be considered to not exceed 2 Mb per second, as long as during any given 15 second interval the total number of bits provided does not exceed 15 2 Mb per second, where the bucket size would be 30 Mbs in this case. The network can enforce a particular bit rate by utilizing a leaky bucket where overflow from that leaky bucket may be discarded or dropped.

[0047] In certain embodiments, the UE may utilize a 1 Mb per second leaky bucket, and the network may employ another 1 Mb per second leaky bucket in the network. In such an embodiment, the network may not see any overflow out of the network-based 1 Mb per second leaky bucket because the uplink and downlink buckets have the same QoS level. On the other hand, in certain embodiments in which the UE may not be trustworthy, or during intervals where the UE has authorized the use of the higher 2 Mb per second QoS level, and the UE utilizes a 2 Mb per second leaky bucket, a network-based 1 Mb per second leaky bucket may consistently overflow. The estimate of the trustworthiness of the UE may depend in part on the UE type or on past behavior of the UE. Based upon the overflow of the bucket, the network may notice that the UE is using a higher QoS level than initially authorized by the network or that the UE initially self-imposed.

[0048] In certain embodiments, multiple leaky buckets may be utilized. For example, uplink traffic arriving from the UE may first enter a 2 Mb per second leaky bucket, and then after it exits that bucket it may enter a 1 Mb per second leaky bucket. If the bits overflow out of the 2 Mb per second leaky bucket, the network may become aware that the UE may be allowing more than 2 Mb per second, which is a higher QoS level than was initially authorized by the network or initially self-imposed by the UE. If the first 2 MB per second bucket does not overflow, but the second 1 Mb per second leaky bucket does overflow, the network can become aware that the UE is utilizing more than 1 Mb per second but less than 2 Mb per second.

[0049] In other words, even when the network entity does not receive a notification from the UE regarding a modification of QoS levels, the network may be able to detect the use of higher temporary QoS levels by monitoring the leaky buckets. If the network entity then determines that the UE is non-compliant, the UE may prevent the UE from utilizing the modified QoS level, as shown in step 330.

[0050] In step 340, the network entity may define a charging rate based on the notification. The charging rate assessed to the user of the UE may at least partially depend upon the duration of the higher temporary QoS limitation and/or the number of bytes used by the UE. In some embodiments, in which the bit rate limitation imposed by the QoS pertains to a GBR service, the higher guaranteed bit rate may be authorized by the subscription data management function or the policy control function for a particular bearer or flow. The UE OS may then self-impose a bit rate to be higher or lower than the guaranteed bit rate on the bearer or flow, depending at least on an agreed upon QoS policy.

[0051] In certain embodiments, the network may utilize a monitoring approach to determine the bit rate being utilized by the UE. In such embodiments, the network may enforce a higher maximum bit rate than the bit rate used by the UE. If the bit rate used by the UE exceeds the initial bit rate used by the UE, the UE may be expected to pay for, and to authorize, the higher bit rate. When the UE decides to authorize use of the higher bit rate, it can nearly instantaneously begin using the higher level QoS temporarily. The UE may then notify the network entity about the use of the higher QoS level. In certain embodiments, the network entity may disable or constrain the higher QoS level, and may enforce a QoS level as determined by the network entity. [0052] Figure 4 illustrates a system according to certain embodiments. It should be understood that each signal or block in Figures 1, 2, and 3 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry. In one embodiment, a system may include several devices, such as, for example, network entity 420 or UE 410. The system may include more than one UE 410 and more one network node 420. The network entity may be a policy control function, for example a PCRF, a charging system, an entitlement service, an application server data center, a network node, a server, a host, and/or any other access or network node.

[0053] Each of these devices may include at least one processor or control unit or module, respectively indicated as 411 and 421. At least one memory may be provided in each device, and indicated as 412 and 422, respectively. The memory may include computer program instructions or computer code contained therein. One or more transceiver 413 and 423 may be provided, and each device may also include an antenna, respectively illustrated as 414 and 424. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided. For example, network entity 420 and UE 410 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 414 and 424 may illustrate any form of communication hardware, without being limited to merely an antenna.

[0054] Transceivers 413 and 423 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception. The transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example. The operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case. One possible use is to make a network node deliver local content. One or more functionalities may also be implemented as virtual application(s) in software that can run on a server.

[0055] A user device or user equipment 410 may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.

[0056] In some embodiments, an apparatus, such as a network entity, may include means for carrying out embodiments described above in relation to Figures 2 and 3. In certain embodiments, at least one memory including computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform any of the processes described herein.

[0057] Processors 411 and 421 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0058] For firmware or software, the implementation may include modules or unit of at least one chip set (for example, procedures, functions, and so on). Memories 412 and 422 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate therefrom. Furthermore, the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language. The memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider. The memory may be fixed or removable.

[0059] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as network entity 420 or UE 410, to perform any of the processes described above (see, for example, Figures 1, 2, and 3). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein. Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments may be performed entirely in hardware.

[0060] Furthermore, although Figure 4 illustrates a system including a network entity 420 and UE 410, certain embodiments may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein. For example, multiple user equipment devices and multiple network entities may be present, as may other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an network entity, such as a relay node. The UE 410 may likewise be provided with a variety of configurations for communication other than communication network entity 420. For example, the UE 410 may be configured for device-to-device, machine-to-machine, or vehicle-to-vehicle communication.

[0061] Certain embodiments can provide a method, apparatus, means for, or a computer product for QoS management. Some embodiments allow for an instantaneous change of the QoS provided to the UE in a dynamic and low-cost manner. The UE may utilize a variety of inputs to adjust the QoS level, which may leverage a broader set of criteria that may be available to the UE OS, but may not be as easily available to the network entity. The above embodiments may also provide a better or more efficient user experience for the UE, subscriber, or the network or operator that achieves significant improvements to the functioning of a network and/or to the functioning of the different network entities within the network.

[0062] The features, structures, or characteristics of certain embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases "certain embodiments," "some embodiments," "other embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearance of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language, throughout this specification does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0063] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention.

[0064] Partial Glossary

[0065] UE user equipment

[0066] UE OS user equipment operating system

[0067] TCP transport control protocol

[0068] LCG logical channel groups

[0069] AMBR aggregate maximum bit rate

[0070] API application programming interface

[0071] HSS home subscriber server

[0072] QoS quality of service

[0073] PCRF policy and charging rules function

[0074] SGW serving gateway

[0075] PGW packet data network gateway

[0076] PDN packet data network

[0077] IMEISV identification and software version number

[0078] GBR guaranteed bit rate

Claims

WE CLAIM:

1. A method comprising:

enforcing at a user equipment an initial self-imposed quality of service level; determining at the user equipment to utilize a temporary quality of service level that is higher than the initial self-imposed quality of service level; and

transmitting a notification of the temporary quality of service level to a network entity.

2. The method according to claim 1, wherein the enforcing of the initial self-imposed quality of service level at the user equipment comprises at least one of only requesting a quality of service rate equal to or lower than the initial self-imposed quality of service level, or only using features associated with a quality of service rate equal to or lower than the initial self-imposed quality of service level.

3. The method according to claim 1, further comprising:

utilizing the temporary quality of service level prior to at least one of the transmitting of the notification to the network entity or receiving a response from the network entity confirming the use of the temporary quality service level.

4. The method according to claims 1, further comprising: determining a time interval for using the temporary quality of service level; and

transmitting the time interval in the notification or in a subsequent notification.

5. The method according to claim 1, wherein an operating system of the user equipment determines the initial self-imposed quality of service level.

6. The method according to claim 1, wherein at least one of the initial quality of service level or the temporary quality of service level is an aggregate maximum bit rate or a guaranteed bit rate.

7. The method according to claim 1, wherein the initial quality of service and the temporary quality of service level relates to uplink or downlink.

8. The method according to claim 1, wherein the temporary quality of service level is granted by the network entity at least in part based on a type of the user equipment.

9. The method according to claim 1, wherein the network entity is a policy control function.

10. The method according to claim 1, further comprising:

transmitting the notification to at least one of a charging system, an entitlement server, or an application server.

11. The method according to claim 1, further comprising:

transmitting another notification to restore the initial self-imposed quality of service limitation.

12. The method according to claim 1, wherein the notification is transmitted through at least one of a mobility management entity, a serving gateway, or a packet data network gateway.

13. The method according to claim 1, further comprising:

determining the at the user equipment to utilize the temporary quality of service level based at least on one other device in the network.

14. The method according to claim 1, wherein the self-imposed initial quality of service level is employed between the operating system of the user equipment and a physical layer on an uplink.

15. The method according to claim 1, wherein the self-imposed initial quality of service level is employed between a physical layer and a next higher layer on a downlink.

16. A method comprising:

detecting at a network entity that a temporary quality of service level that is higher than a self-imposed initial quality of service level is being used by a user equipment; and

determining at the network entity whether or not to constrain the detected temporary quality of service level.

17. The method according to claim 16, further comprising:

determining at network entity a maximum quality of service limit for a user equipment, wherein the maximum quality of service limit is higher than the temporary quality of service level and the self-imposed initial quality of service level.

18. The method according to claim 16, further comprising: at least one of receiving a notification at the network entity from the user equipment or sending a response to the user equipment confirming the use of the temporary quality service level, subsequent to the temporary quality of service level being utilized by the user equipment.

19. The method according to claim 16, further comprising:

receiving at the network entity from the user equipment a request for the temporary quality of service level; and

granting the requested temporary higher quality of service level.

20. The method according to claim 16, wherein the determination to constrain the temporary quality of service level is based at least on network congestion or the user equipment not being compliant.

21. The method according to claim 16, further comprising:

monitoring the temporary quality of service level of the user equipment at network entity.

22. The method according to claim 16, further comprising:

defining at the network entity a charging rate for the user equipment based on the detected temporary quality of service level.

23. The method according to claim 16, further comprising:

receiving a notification from the user equipment that the temporary quality of service is being used.

24. An apparatus, comprising:

at least one memory comprising computer program code;

at least one processor;

wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to perform a process according to any of claims 1-23.

25. An apparatus comprising means for performing a process according to any of claims 1-23.

26. A non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process according to any of claims 1-23.

27. A computer program product encoding instructions for performing a process according to any of claims 1-23.