WO2013082798A1

WO2013082798A1 - System and method for high bit rate quality of service in a umts network

Info

Publication number: WO2013082798A1
Application number: PCT/CN2011/083741
Authority: WO
Inventors: Xipeng Zhu; Francesco Pica
Original assignee: Qualcomm Incorporated
Priority date: 2011-12-09
Filing date: 2011-12-09
Publication date: 2013-06-13

Abstract

In one aspect, the disclosure provides for the utilization of an EPS QoS parameter in a PDP context for a UMTS network. Another aspect of the disclosure provides for the utilization of an aggregate maximum bit rate (AMBR) parameter, rather than the conventional maximum bit rate (MBR) parameter, of a QoS profile, for restricting the bit rate corresponding to a PDP context in a UMTS network.

Description

SYSTEM AND METHOD FOR HIGH BIT RATE QUALITY OF SERVICE IN A

UMTS NETWORK

BACKGROUND

Field

[0001] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to a QoS profile supporting increased data rates.

Background

[0002] Wireless communication networks are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on. Such networks, which are usually multiple access networks, support communications for multiple users by sharing the available network resources. One example of such a network is the UMTS Terrestrial Radio Access Network (UTRAN). The UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). The UMTS, which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division- Synchronous Code Division Multiple Access (TD-SCDMA). The UMTS also supports enhanced 3G data communications protocols, such as High Speed Packet Access (HSPA), which provides higher data transfer speeds and capacity to associated UMTS networks.

[0003] As the demand for mobile broadband access continues to increase, research and development continue to advance the UMTS technologies not only to meet the growing demand for mobile broadband access, but to advance and enhance the user experience with mobile communications. SUMMARY

[0004] In one aspect, the disclosure provides for the utilization of an EPS QoS parameter in a PDP context for a UMTS network.

[0005] Another aspect of the disclosure provides for the utilization of an aggregate maximum bit rate (AMBR) parameter, rather than the conventional maximum bit rate (MBR) parameter, of a QoS profile, for restricting the bit rate corresponding to a PDP context in a UMTS network.

[0006] These and other aspects of the invention will become more fully understood uDon a review of the detailed descriotion. which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a block diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0008] FIG. 2 is a conceptual diagram illustrating an example of a radio protocol architecture for a UMTS network.

[0009] FIG. 3 is a conceptual diagram illustrating an example of an access network.

[0010] FIG. 4 is a block diagram conceptually illustrating an example of a UMTS telecommunications system.

[0011] FIG. 5 is a block diagram conceptually illustrating an example of a UMTS telecommunications sytem with an enhanced packet core.

[0012] FIG. 6 is a flow chart illustrating a process for wireless communication utilizing a QoS parameter.

[0013] FIG. 7 is a flow chart illustrating a process for wireless communication in a

UMTS network utilizing an aggregate maximum bit rate parameter.

DETAILED DESCRIPTION

[0014] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0015] In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.

[0016] One or more processors in the processing system may execute software.

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium. The computer-readable medium may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer. The computer-readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system. The computer-readable medium may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0017] FIG. 1 is a conceptual diagram illustrating an example of a hardware implementation for an apparatus 100 employing a processing system 114. In this exarrmle. the orocessine svstem 114 mav be irrmlemented with a bus architecture, represented generally by the bus 102. The bus 102 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 114 and the overall design constraints. The bus 102 links together various circuits including one or more processors, represented generally by the processor 104, a memory 105, and computer-readable media, represented generally by the computer-readable medium 106. The bus 102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface 108 provides an interface between the bus 102 and a transceiver 110. The transceiver 110 provides a means for communicating with various other apparatus over a transmission medium. Depending upon the nature of the apparatus, a user interface 112 (e.g., keypad, display, speaker, microphone, joystick) may also be provided.

[0018] The processor 104 is responsible for managing the bus 102 and general processing, including the execution of software stored on the computer-readable medium 106. The software, when executed by the processor 104, causes the processing system 114 to perform the various functions described infra for any particular apparatus. The computer-readable medium 106 may also be used for storing data that is manipulated by the processor 104 when executing software.

[0019] In a wireless telecommunication system, the radio protocol architecture between a mobile device and a cellular network may take on various forms depending on the particular application. An example for a 3GPP UMTS system will now be presented with reference to FIG. 2, illustrating an example of the signaling protocol stack. The UMTS signaling protocol stack is divided into an Access Stratum (AS) and a Non-Access Stratum (NAS). The NAS architecture is divided into Circuit Switched and Packet Switched protocols.

[0020] The Access Stratum architecture for the UE and Node B includes a user plane and a control plane. Here, the user plane or data plane carries user traffic, while the control plane carries control information, i.e., signaling. The AS is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 is the lowest layer and irrmlements various ohv _J sical lav _J er signal orocessing functions. Lav _J er 1 will be referred to herein as the physical layer 206. The data link layer, called Layer 2 (L2 layer) 208 is above the physical layer 206 and is responsible for the link between the UE and Node B over the physical layer 206.

[0021] At Layer 3, the RRC layer 216 handles the control plane signaling between the UE and the Node B. RRC layer 216 includes a number of functional entities for routing higher layer messages, handling broadcast and paging functions, establishing and configuring radio bearers, etc.

[0022] In the illustrated air interface, the L2 layer 208 is split into sublayers. In the control plane, the L2 layer 208 includes two sublayers: a medium access control (MAC) sublayer 210 and a radio link control (RLC) sublayer 212. In the user plane, the L2 layer 208 additionally includes a packet data convergence protocol (PDCP) sublayer 214. Although not shown, the UE may have several upper layers above the L2 layer 208 including a network layer (e.g., IP layer) that is terminated at a PDN gateway on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc.).

[0023] The PDCP sublayer 214 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 214 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between Node Bs.

[0024] The RLC sublayer 212 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to a hybrid automatic repeat request (HARQ).

[0025] The MAC sublayer 210 provides multiplexing between logical and transport channels. The MAC sublayer 210 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 210 is also responsible for HARQ operations.

[0026] The various concepts presented throughout this disclosure may be irrmlemented across a broad varietv of telecommunication svstems. network architectures, and communication standards. Referring to Fig. 3, by way of example and without limitation, a simplified access network 300 in a UMTS Terrestrial Radio Access Network (UTRAN) architecture, which may utilize HSPA, is illustrated. The system includes multiple cellular regions (cells), including cells 302, 304, and 306, each of which may include one or more sectors. Cells may be defined geographically, e.g., by coverage area, and/or may be defined in accordance with a frequency, scrambling code, etc. That is, the illustrated geographically-defined cells 302, 304, and 306 may each be further divided into a plurality of cells, e.g., by utilizing different scrambling codes. For example, cell 304a may utilize a first scrambling code, and cell 304b, while in the same geographic region and served by the same Node B 344, may be distinguished by utilizing a second scrambling code.

[0027] In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. For example, in cell 302, antenna groups 312, 314, and 316 may each correspond to a different sector. In cell 304, antenna groups 318, 320, and 322 each correspond to a different sector. In cell 306, antenna groups 324, 326, and 328 each correspond to a different sector.

[0028] The cells 302, 304 and 306 may include several UEs that may be in communication with one or more sectors of each cell 302, 304 or 306. For example, UEs 330 and 332 may be in communication with Node B 342, UEs 334 and 336 may be in communication with Node B 344, and UEs 338 and 340 may be in communication with Node B 346. Here, each Node B 342, 344, 346 is configured to provide an access point to a core network 404 (see FIG. 4) for all the UEs 330, 332, 334, 336, 338, 340 in the respective cells 302, 304, and 306.

[0029] Referring now to FIG. 4, by wa}f of example and without limitation, various aspects of the present disclosure are illustrated with reference to a Universal Mobile Telecommunications System (UMTS) system 400. FIG. 5 is a block diagram illustrating a UMTS system 500 that is similar to the system 400 illustrated in FIG. 4 but with certain enhancements for compliance with standards for the evolved oacket svstem fEPSL in oarticular. oertainine to the evolved oacket core fEPG

404-2. A UMTS network includes three interacting domains: a Core Network (CN) 404, a UMTS Terrestrial Radio Access Network (UTRAN) 402, and User Equipment (UE) 410. In this example, the UTRAN 402 may provide various wireless services including telephony, video, data, messaging, broadcasts, and/or other services. The UTRAN 402 may include a plurality of Radio Network Subsystems (RNSs) such as an RNS 407, each controlled by a respective Radio Network Controller (RNC) such as an RNC 406. Here, the UTRAN 402 may include any number of RNCs 406 and RNSs 407 in addition to the illustrated RNCs 406 and RNSs 407. The RNC 406 is an apparatus responsible for, among other things, assigning, reconfiguring and releasing radio resources within the RNS 407. The RNC 406 may be interconnected to other RNCs 406 in the UTRAN 402 through various types of interfaces such as a direct physical connection, a virtual network, or the like, using any suitable transport network. In some examples an Iur interface may be utilized for communication between RNCs 406.

[0030] Communication between a UE 410 and a Node B 408 may utilize any suitable air interface, referred to in UMTS as a Uu interface. In one example, the Uu interface may employ a W-CDMA frequency division duplex system, a TD-SCDMA time division duplex system, or any other suitable system.

[0031] The geographic region covered by the RNS 407 may be divided into a number of cells, with a radio transceiver apparatus serving each cell. A radio transceiver apparatus is commonly referred to as a Node B in UMTS applications, but may also be referred to by those skilled in the art as a base station (BS), a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), or some other suitable terminology. For clarity, three Node Bs 408 are shown in each RNS 407; however, the RNSs 407 may include any number of wireless Node Bs. The Node Bs 408 provide wireless access points to a core network (CN) 404 for any number of mobile apparatuses. Examples of a mobile apparatus include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a notebook, a netbook, a smartbook, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS) device, a multimedia device, a video device, a digital audio olaver fe.g.. MP3 olaver). a camera, a game console, or anv other similar functioning device. The mobile apparatus is commonly referred to as user equipment (UE) in UMTS applications, but may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. In a UMTS system, the UE 410 may further include a universal subscriber identity module (USIM) 411, which contains a user's subscription information to a network. For illustrative purposes, one UE 410 is shown in communication with a number of the Node Bs 408. The downlink (DL), also called the forward link, refers to the communication link from a Node B 408 to a UE 410, and the uplink (UL), also called the reverse link, refers to the communication link from a UE 410 to a Node B 408.

[0032] The CN 404 interfaces with one or more access networks, such as the

UTRAN 402, utilizing one or more Iu interfaces. As shown, the CN 404 is a GSM core network. However, as those skilled in the art will recognize, the various concepts presented throughout this disclosure may be implemented in a RAN, or other suitable access network, to provide UEs with access to types of CNs other than GSM networks.

[0033] The illustrated CN 404 includes a circuit-switched (CS) domain and a packet-switched (PS) domain. Some of the circuit-switched elements are a Mobile services Switching Centre (MSC), a Visitor Location Register (VLR), and a Gateway MSC (GMSC). Packet-switched elements include a Serving GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN). Some network elements, like EIR, HLR, VLR and AuC may be shared by both of the circuit-switched and packet- switched domains.

[0034] In the illustrated example, the core network 404 supports circuit-switched services with a MSC 412 and a GMSC 414. In some applications, the GMSC 414 may be referred to as a media gateway (MGW). One or more RNCs, such as the RNC 406, may be connected to the MSC 412. The MSC 412 is an apparatus that controls call setuD. call routine, and UE mobilit _Jv functions. The MSC 412 also includes a visitor location register (VLR) that contains subscriber-related information for the duration that a UE is in the coverage area of the MSC 412. The GMSC 414 provides a gateway through the MSC 412 for the UE to access a circuit-switched network 416. The GMSC 414 includes a home location register (HLR) 415 containing subscriber data, such as the data reflecting the details of the services to which a particular user has subscribed. The HLR is also associated with an authentication center (AuC) that contains subscriber-specific authentication data. When a call is received for a particular UE, the GMSC 414 queries the HLR 415 to determine the UE's location and forwards the call to the particular MSC serving that location. In some examples, a home subscriber server (HSS) 415-2 may be utilized instead of, or in addition to, the HLR 415-1, such as in a network configured for E-UTRA. Communication with the HLR 415 or the HSS may utilize an S6d or G4 interface in some examples.

[0035] The illustrated CN 404 also supports packet-data services with a serving

GPRS support node (SGSN) 418 and a gateway GPRS support node (GGSN) 420. GPRS, which stands for General Packet Radio Service, is designed to provide packet-data services at speeds higher than those available with standard circuit- switched data services. The GGSN 420 provides a connection for the UTRAN 402 to a packet-based network 422. The packet-based network 422 may be the Internet, a private data network, or some other suitable packet-based network. The primary function of the GGSN 420 is to provide the UEs 410 with packet-based network connectivity. Data packets may be transferred between the GGSN 420 and the UEs 410 through the SGSN 418, which performs primarily the same functions in the packet-based domain as the MSC 412 performs in the circuit-switched domain. Here, a Gn/Gp interface may be utilized between the GGSN 420 and the SGSN 418. Further, the GGSN 420, or, in a networ k that includes E-UTRA support, a PGW, may utilize a Gi/SGi interface.

[0036] Of course, as deployed systems continue to improve and E-UTRA networks begin to operate alongside UTRA networks, some or part of the CN 404 may be augmented or replaced with other components such as one or more mobility management entities (MMEs), a Serving Gateway (SGW) 420-2a, and a PDN Gatewav fPGWI 420-2b. Those of ordinarv skill in the art will corrmrehend that the interconnections between the UTRA components and the E-UTRA components may utilize the same or other communication interfaces, and any suitable interface may be utilized within the scope of the present disclosure. For example, interfaces between various nodes such as the SGSN 418 and an MME may include the Gn/Gp interface; an S16 interface; an S3 interface; or an S4 interface.

[0037] In networks that include E-UTRA support, Policy and Charging Control (PCC) may affect the handling of user services relating to the QoS. Here, PCC interfaces affected by QoS may include a Gx interface and an Rx interface.

[0038] The UMTS air interface Uu may be a spread spectrum Direct-Sequence Code

Division Multiple Access (DS-CDMA) system. The spread spectrum DS-CDMA spreads user data through multiplication by a sequence of pseudorandom bits called chips. The W-CDMA air interface for UMTS is based on such DS-CDMA technology and additionally calls for a frequency division duplexing (FDD). FDD uses a different carrier frequency for the uplink (UL) and downlink (DL) between a Node B 408 and a UE 210. Another air interface for UMTS that utilizes DS-CDMA, and uses time division duplexing (TDD), is the TD-SCDMA air interface. Those skilled in the art will recognize that although various examples described herein may refer to a W-CDMA air interface, the underlying principles are equally applicable to a TD-SCDMA air interface.

[0039] A high speed packet access (HSPA) air interface includes a series of enhancements to the 3G/W-CDMA air interface, facilitating greater throughput and reduced latency. Among other modifications over prior releases, HSPA utilizes hybrid automatic repeat request (HARQ), shared channel transmission, and adaptive modulation and coding. The standards that define HSPA include HSDPA (high speed downlink packet access) and HSUPA (high speed uplink packet access, also referred to as enhanced uplink, or EUL).

[0040] Additional communication interfaces that may be deployed in the communication system may include charging interfaces such as Ga, Rf, Bp, and Ro interfaces.

[0041] In a UMTS system, a packet data protocol (PDP) context generally provides a oacket data connection, orovidine a oacket data connection between the UE and the network for the exchange of IP packets. That is, when a UE establishes a packet-switched connection, it may activate a PDP context. The PDP context includes various parameters, including quality of service (QoS) parameters negotiated between the UE and the network.

[0042] Release 8 of the 3GPP standards for UMTS introduced dual cell HSDPA (DC-

HSDPA), which enables a UE to aggregate dual adjacent 5-MHz downlink carriers transmitted by a node B. The dual carrier approach provides higher downlink data rates and better efficiency at multicarrier sites. Generally, DC-HSDPA utilizes a primary carrier and a secondary carrier, where the primary carrier provides the channels for downlink data transmission and the channels for uplink data transmission, and the secondary carrier provides a second set of HS-PDSCHs and HS-SCCHs for downlink communication. Here, the primary carrier is generally the best serving HS-DSCH cell according to the UE measurements of E_c/Io-

[0043] Further enhancements have enabled three- and four-carrier aggregation in

HSDPA networks. More recently, with the publication of Release 11 of the 3GPP standards, eight carriers may be utilized in the downlink (8C-HSDPA). With this increase in carriers, downlink data rates can peak at up to 336 Mbps at the physical layer. With future enhancements in the pipeline as well, peak data rates are projected to continue to increase even above this level.

[0044] However, as seen in Appendix A, in Release 11 specifications (3GPP TS

24.008 Vll.0.0 clause 10.5.6.5) the maximum bit rate for the downlink in upper layer protocols for UMTS is 256 Mbps. That is, the QoS information element as currently defined for UMTS cannot support a bit rate higher than 256 Mbps. Thus, the peak data rate of each PDP context might be restricted to remain within 256 Mbps, and a UMTS system may be incapable of fully leveraging the 336 Mbps physical layer capability.

[0045] Several approaches may be taken to address this issue. For example, a straightforward approach might be simply to increase the maximum bit rate (MBR) and/or the Guaranteed Bit Rate (GBR) according to the UMTS QoS profile, to a number capable of accommodating the increased bit rate. For example, the range for the MBR/GBR for the QoS profile for UMTS might be extended to a range such as 0 to 1000 Mbps.

[0046] While this approach might be the most intuitive, it has several drawbacks.

For example, the functionality of a large number of entities in the 3GPP system utilize this aspect of the QoS profile, and changing the MBR/GBR impacts nearly all of these entities. For example, increasing the MBR/GBR would impact the NAS interfaces, the inter-SGSN/MME interfaces such as the Gn/Gp, the HLR/HSS interfaces such as the Gr, the PCC interfaces such as the Gx, the GGSN/PGW interfaces such as the Gi, and the charging interfaces such as the Ga, Rf, Bp, and Ro. Further, increasing the MBR/GBR would impact UMTS entities including the UE, the RNC, the Node B, the SGSN, GGSN, PGW, HLR/HSS, CGF, and the PCRF.

[0047] Thus, in accordance with an aspect of the present disclosure, a different approach may reduce the impacted interfaces or entities in the UMTS system.

[0048] For example, some aspects of the present disclosure may utilize the QoS for the evolved packet system (EPS). That is, 3GPP LTE standards utilize a QoS profile capable of supporting the higher bit rate achieved with 8C-HSDPA and beyond. Further, the S4 interface, which might be utilized by the SGSN 418 or the MME, can support the EPS QoS. Thus, the UTRAN may be coupled to the EPC (e.g., utilizing the S4-SGSN) to utilize the EPS QoS.

[0049] When utilizing the EPS QoS, the UE 410 may send both the UMTS QoS and the EPS QoS to the SGSN 418. In this case, the legacy UMTS SGSN may ignore the EPS QoS, and serve the UE 410 according to the UMTS QoS. Further, in a scenario including the S4-SGSN, this node understands the UMTS QoS, and thus there may be no issue when a legacy UE is utilized in the Release- 11 core network. [0050] Here, the network may use both the UMTS QoS and the EPS QoS in all the

NAS messages which have QoS information element. This means the UE 410 may receive a NAS message with both EPS QoS and UMTS QoS from the SGSN. Here, if the UE understands the EPS QoS IE, it may use the EPS QoS and optionally ignore the UMTS QoS. Otherwise, the UE may ignore the EPS QoS IE and uses the UMTS QoS IE.

[0051] With this approach, the UE 410 may be impacted, e.g., due to changes in the

NAS interface. Here, while the NAS interfaces would be impacted with this change, as well as entities including the UE 410, the RNC 406, the S4-SGSN, this is fewer impacted entities than might otherwise be impacted by simply increasing the MBR/GBR. For example, because the evolved packet core (EPC) for UMTS has been supported since Release 8 of the 3GPP standards, with this approach, upgrades to the network can generally be avoided other than the above-discussed impact to the SGSN. Further, because this approach harmonizes the QoS policy between UMTS and EPS, inter-RAT mobility may be improved.

[0052] In accordance with another aspect of the present disclosure, the MBR parameter of the QoS profile for UMTS may simply be ignored, and the aggregate maximum bit rate (AMBR), introduced to UMTS in Release 9 standards, may be utilized instead to restrict the bit rate of non-GBR bearers.

[0053] That is, the maximum bit rate ( MBR) is a mandatory parameter in the QoS profile of each PDP context, utilized to restrict the maximum bit rate of the corresponding PDP context. In the uplink direction, the MBR is enforced by the UE 410 and the RNC 406; and in the downlink direction, the MBR is enforced in the GGSN 420, and optionally, in the SGSN 418 and RNC 406. Further, the MBR is typically set to the maximum physical layer speed in the HLR/HSS 415 for the UE 410 to fully utilize the physical layer capability.

[0054] However, the MBR is not supported in EPS for non-GBR bearers. Rather, the

AMBR is utilized to restrict the aggregate bit rate of non-GBR bearers.

[0055] By utilizing the AMBR, there is generally no impact to any interface protocol in the UMTS system. That is, the message format (e.g., abstract syntax notation one ASN.l scripts) generally need not be changed. However, there may be an impact to some of the entities in the network, including the RNC 406, the SGSN 418, and the GGSN/PGW 420, which may be upgraded to ignore the MBR parameter. The impact to the UE depends on the implementation, since currently most UEs do not enforce the MBR parameter.

[0056] That is, in QoS enforcement, when the AMBR is available the QoS related entities (e.g. UE, RNC, SGSN, GGSN/PGW) may ignore the MBR parameter. According to current standards, after a PDP context is established, in user data transmission, the packets above the MBR are generally dropped. However, in accordance with this aspect of the present disclosure, after a PDP context is established, in user data transmission, the related entities should not oolice user plane packets according to the MBR.

[0057] This approach generally achieves the same QoS capabilities as available to the EPS QoS, in that the EPS system similarly utilizes the AMBR.

[0058] Several aspects of a telecommunications system have been presented with reference to a 3GPP W-CDMA system. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0059] By way of example, various aspects may be extended to other UMTS systems such as TD-SCDMA and TD-CDMA. Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0060] It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. A ohrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for."

Appendix A

Extract from 3GPP TS 24.008 v 11.0.0

Core Network Protocols; Stage 3 (Release 11)

10.5.6.5 Quality of service

The purpose of the quality of service information element is to specify the QoS parameters for a PDP context.

The QoS IE is defined to allow backward compatibility to earlier version of Session

Management Protocol.

The quality of service is a type 4 information element with a minimum length of 14 octets and a maximum length of 18 octets. The QoS requested by the MS shall be encoded both in the QoS attributes specified in octets 3-5 and in the QoS attributes specified in octets 6-14.

In the MS to network direction and in the network to MS direction the following applies:

- Octets 15-18 are optional. If octet 15 is included, then octet 16 shall also be included, and octets 17 and 18 may be included.

- If octet 17 is included, then octet 18 shall also be included.

- A QoS IE received without octets 6-18, without octets 14-18, without octets 15-18, or without octets 17-18 shall be accepted by the receiving entity.

NOTE: This behavior is required for interworking with entities supporting an earlier version of the protocol, or when the Maximum bit rate for downlink or for downlink and uplink is negotiated to a value lower than 8700 kbps.

The quality of service information element is coded as shown in figure 10.5.138/3GPP TS 24.008 and table 10.5.156/3GPP TS 24.008.

Quality of sen/ice IEI

Length of quality of service IE

0 0 Delay Reliability

spare class class

Peak 0 Precedence

throughput spare class

0 0 Mean

spare throughput

Traffic Class Delivery order Delivery of erroneous

SDU

Maximum SDU size

Maximum bit rate for uplink

Maximum bit rate for downlink

Rp<;irli ial RFR SDI I prrnr ratio

Transfer delay Traffic Handling

priority

Guaranteed bit rate for uplink

Guaranteed bit rate for downlink

0 0 SignalSource Statistics Descriptor

spare ling

Indication

Maximum bit rate for downlink (extended)

Guaranteed bit rate for downlink (extended)

Maximum bit rate for uplink (extended)

Guaranteed bit rate for uplink (extended)

Figure 10.5.138/3GPP TS 24.008: Quality of service information element

Table 10.5.156/3GPP TS 24.008: Quality of service information element

Reliability class, octet 3 (see 3GPP TS 23.107 [81 ])

Bits

3 2 1

In MS to network direction:

0 0 0 Subscribed reliability class

In network to MS direction:

0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 1 Unused. If received, it shall be interpreted as '010' (Note)

0 1 0 Unacknowledged GTP; Acknowledged LLC and RLC, Protected data

0 1 1 Unacknowledged GTP and LLC; Acknowledged RLC, Protected data

1 0 0 Unacknowledged GTP, LLC, and RLC, Protected data

1 0 1 Unacknowledged GTP, LLC, and RLC, Unprotected data

1 1 1 Reserved

Aii other values are interpreted as Unacknowledged GTP and LLC; Acknowledged RLC, Protected data in this version of the protocol.

NOTE: this value was allocated in earlier versions of the protocol.

Delay class, octet 3 (see 3GPP TS 22.060 [73] and 3GPP TS 23.107 [81 ])

Bits

6 5 4

In MS to network direction:

0 0 0 Subscribed delay class

In network to MS direction:

0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 1 Delay class 1

0 1 0 Delay class 2

0 1 1 Delay class 3

1 0 0 Delay class 4 (best effort)

1 1 1 Reserved

All other values are interpreted as Delay class 4 (best effort) in this version

of the protocol.

Bit 7 and 8 of octet 3 are spare and shall be coded all 0.

Precedence class, octet 4 (see 3GPP TS 23.107 [81 ])

Bits

3 2 1

In MS to network direction:

0 0 0 Subscribed precedence

In network to MS direction:

0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 1 High priority

0 1 0 Normal priority

0 1 1 Low priority

1 1 1 Reserved

All other values are interpreted as Normal priority in this version of the protocol.

Bit 4 of octet 4 is spare and shall be coded as 0.

Peak throughput, octet 4 (see 3GPP TS 23.107 [81 ])

This field is the binary representation of the Peak Throughput Class (1 to 9). The corresponding peak throughput to each peak throughput class is indicated.

Bits

8 7 6 5

In MS to network direction:

0 0 0 0 Subscribed peak throughput

In network to MS direction:

0 0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 0 1 Up to 1 000 octet/s

0 0 1 0 Up to 2 000 octet/s

0 0 1 1 Up to 4 000 octet/s

0 1 0 0 Up to 8 000 octet/s

0 1 0 1 Up to 16 000 octet/s

0 1 1 0 Up to 32 000 octet/s

0 1 1 1 Up to 64 000 octet/s

1 0 0 0 Up to 128 000 octet/s

1 0 0 1 Up to 256 000 octet/s

1 1 1 1 Reserved

All other values are interpreted as Up to 1 000 octet/s in this

version of the protocol.

Mean throughput, octet 5 (see 3GPP TS 23.107 [81 ])

This field is the binary representation of the Mean Throughput Class (1 to 18; mean throughput class 30 is reserved and 31 is best effort). The corresponding mean throughput to each mean throughput class is indicated.

Bits

5 4 3 2 1 In MS to network direction:

0 0 0 0 0 Subscribed mean throughput

In network to MS direction:

0 0 0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 0 0 1 100 octet/h

0 0 0 1 0 200 octet/h

0 0 0 1 1 500 octet/h

0 0 1 0 0 1 000 octet/h

0 0 1 0 1 2 000 octet/h

0 0 1 1 0 5 000 octet/h

0 0 1 1 1 10 000 octet/h

0 1 0 0 0 20 000 octet/h

0 1 0 0 1 50 000 octet/h

0 1 0 1 0 100 000 octet/h

0 1 0 1 1 200 000 octet/h

0 1 1 0 0 500 000 octet/h

0 1 1 0 1 1 000 000 octet/h

0 1 1 1 0 2 000 000 octet/h

0 1 1 1 1 5 000 000 octet/h

1 0 0 0 0 10 000 000 octet/h

1 0 0 0 1 20 000 000 octet/h

1 0 0 1 0 50 000 000 octet/h

1 1 1 1 0 Reserved

1 1 1 1 1 Best effort

The value Best effort indicates that throughput shall be made available to the MS on a per need and availability basis.

All other values are interpreted as Best effort in this

version of the protocol.

Bits 8 to 6 of octet 5 are spare and shall be coded all 0.

Delivery of erroneous SDUs, octet 6 (see 3GPP TS 23.107 [81 ])

Bits

3 2 1

In MS to network direction:

0 0 0 Subscribed delivery of erroneous SDUs

In network to MS direction:

0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 1 No detect ('-')

0 1 0 Erroneous SDUs are delivered ('yes')

0 1 1 Erroneous SDUs are not delivered ('no')

1 1 1 Reserved

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of this protocol.

The MS shall consider all other values as reserved.

Delivery order, octet 6 (see 3GPP TS 23.107 [81 ])

Bits

5 4 3

In MS to network direction:

0 0 Subscribed delivery order

In network to MS direction:

0 0 Reserved

In MS to network direction and in network to MS direction:

0 1 With delivery order ('yes')

1 0 Without delivery order ('no')

Traffic class, octet 6 (see 3GPP TS 23.107 [81])

Bits

876

In MS to network direction:

000 Subscribed traffic class

In network to MS direction:

000 Reserved

In MS to network direction and in network to MS direction:

001 Conversational class

010 Streaming class

01 1 Interactive class

100 Background class

1 1 1 Reserved

The MS shall consider all other values as reserved.

Maximum SDU size, octet 7 (see 3GPP TS 23.107 [81])

In MS to network direction:

00000000 Subscribed maximum SDU size

1 1 1 1 1 1 1 1 Reserved

In network to MS direction:

00000000 Reserved

1 1 1 1 1 1 1 1 Reserved

In MS to network direction and in network to MS direction:

For values in the range 00000001 to 10010110 the Maximum SDU size value is binary coded in 8 bits, using a granularity of 10 octets, giving a range of values from 10 octets to 1500 octets.

Values above 10010110 are as below:

100101 1 1 1502 octets

1001 1000 1510 octets

1001 1001 1520 octets

The MS shall consider all other values as reserved.

Maximum bit rate for uplink, octet 8

Bits

87654321

In MS to network direction:

00000000 Subscribed maximum bit rate for uplink

In network to MS direction:

00000000 Reserved

In MS to network direction and in network to MS direction:

00000001 The maximum bit rate is binary coded in 8 bits, using a granularity of 1 kbps

001 1 1 1 1 1 giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.

01000000 The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits -01000000) * 8 kbps)

01 1 1 1 1 1 1 giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. 10000000 The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits -10000000) * 64 kbps)

1 1 1 1 1 1 10 giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.

1 1 1 1 1 1 1 1 0kbps

If the sending entity wants to indicate a Maximum bit rate for uplink higher than 8640 kbps, it shall set octet 8 to "11111110", i.e.8640 kbps, and shall encode the value for the Maximum bit rate in octet 17.

Maximum bit rate for downlink, octet 9 (see 3GPP TS 23.107 [81])

Coding is identical to that of Maximum bit rate for uplink.

If the sending entity wants to indicate a Maximum bit rate for downlink higher than 8640 kbps, it shall set octet 9 to "11111110", i.e.8640 kbps, and shall encode the value for the Maximum bit rate in octet 15.

In this version of the protocol, for messages specified in the present document, the sending entity shall not request 0 kbps for both the Maximum bitrate for downlink and the Maximum bitrate for uplink at the same time. Any entity receiving a request for 0 kbps in both the Maximum bitrate for downlink and the Maximum bitrate for uplink shall consider that as a syntactical error (see clause 8).

Residual Bit Error Rate (BER), octet 10 (see 3GPP TS 23.107 [81])

Bits

8765

In MS to network direction:

0000 Subscribed residual BER

In network to MS direction:

0000 Reserved

In MS to network direction and in network to MS direction:

The Residual BER value consists of 4 bits. The range is from 5*10^"2 to 6*10

0001 5*10^"2

0010 1*10^"2

001 1 5*10^"3

0100 4*10^"3

0101 1*10^"3

01 10 1*10^"4

01 1 1 1*10^"5

1000 1*10^"6

1001 6*10^"8

1 1 1 1 Reserved

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

The MS shall consider all other values as reserved.

SDU error ratio, octet 10 (see 3GPP TS 23.107 [81])

Bits

4321

In MS to network direction:

0000 Subscribed SDU error ratio

In network to MS direction:

0000 Reserved

In MS to network direction and in network to MS direction:

The SDU error ratio value consists of 4 bits. The range is is from 1*10^"1 to 1* 0^"6.

0001 1*10^"2

0010 7*10^"3

001 1 1*10^"3

0100 1*10^"4 0 1 0 1 1Ί0^"5

0 1 1 0 1Ί0^"6

0 1 1 1 1Ί0^"1

1 1 1 1 Reserved

The MS shall consider all other values as reserved.

Traffic handling priority, octet 1 1 (see 3GPP TS 23.107 [81 ])

Bits

2 1

In MS to network direction:

0 0 Subscribed traffic handling priority

In network to MS direction:

0 0 Reserved

In MS to network direction and in network to MS direction:

0 1 Priority level 1

1 0 Priority level 2

1 1 Priority level 3

The Traffic handling priority value is ignored if the Traffic Class is Conversational class, Streaming class or Background class.

Transfer delay, octet 1 1 (See 3GPP TS 23.107 [81])

Bits

8 7 6 5 4 3

In MS to network direction:

0 0 0 0 0 0 Subscribed transfer delay

In network to MS direction:

0 0 0 0 0 0 Reserved

In MS to network direction and in network to MS direction:

0 0 0 0 0 1 The Transfer delay is binary coded in 6 bits, using a granularity of 10 ms

0 0 1 1 1 1 giving a range of values from 10 ms to 150 ms in 10 ms increments

0 1 0 0 0 0 The transfer delay is 200 ms + ((the binary coded value in 6 bits - 010000) * 50 ms)

0 1 1 1 1 1 giving a range of values from 200 ms to 950 ms in 50ms increments

1 0 0 0 0 0 The transfer delay is 1000 ms + ((the binary coded value in 6 bits - 100000) * 100 ms)

1 1 1 1 1 0 giving a range of values from 1000 ms to 4000 ms in 100ms increments

1 1 1 1 1 1 Reserved

The Transfer delay value is ignored if the Traffic Class is Interactive class or Background class.

Guaranteed bit rate for uplink, octet 12 (See 3GPP TS 23.107 [81 ])

Coding is identical to that of Maximum bit rate for uplink.

If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 8640 kbps, it shall set octet 12 to "1 1 11 1 1 10", i.e. 8640 kbps, and shall encode the value for the Guaranteed bit rate in octet 18.

The Guaranteed bit rate for uplink value is ignored if the Traffic Class is Interactive class or Background class, or Maximum bit rate for uplink is set to 0 kbps.

Guaranteed bit rate for downlink, octet 13(See 3GPP TS 23.107 [81 ]) Coding is identical to that of Maximum bit rate for uplink.

If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 8640 kbps, it shall set octet 13 to "1 1 11 1 1 10", i.e. 8640 kbps, and shall encode the value for the Guaranteed bit rate in octet 16.

The Guaranteed bit rate for downlink value is ignored if the Traffic Class is Interactive class or Background class, or Maximum bit rate for downlink is set to 0 kbps.

Source Statistics Descriptor, octet 14 (see 3GPP TS 23.107 [81 ])

Bits

4 3 2 1

In MS to network direction

0 0 0 0 unknown

0 0 0 1 speech

The network shall consider all other values as unknown,

in network to MS direction

Bits 4 to 1 of octet 14 are spare and shall be coded all 0.

The Source Statistics Descriptor value is ignored if the Traffic Class is Interactive class or Background class.

Signalling Indication, octet 14 (see 3GPP TS 23.107 [81 ])

Bit

5

In MS to network direction and in network to MS direction:

0 Not optimised for signalling traffic

1 Optimised for signalling traffic

If set to Ί ' the QoS of the PDP context is optimised for signalling

The Signalling Indication value is ignored if the Traffic Class is Conversational class, Streaming class or Background class.

Bits 8 to 6 of octet 14 are spare and shall be coded all 0.

Maximum bit rate for downlink (extended), octet 15

Bits

8 7 6 5 4 3 2 1

In MS to network direction and in network to MS direction:

0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 9.

For all other values: Ignore the value indicated by the

Maximum bit rate for downlink in octet 9

and use the following value:

0 0 0 0 0 0 0 1 The maximum bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps), 0 1 0 0 1 0 1 0 giving a range of values from 8700 kbps

to 16000 kbps in 100 kbps increments.

0 1 0 0 1 0 1 1 The maximum bit rate is 16 Mbps + ((the binary coded value in 8 bits - 01001010) * 1 Mbps),

1 0 1 1 1 0 1 0 giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.

1 0 1 1 1 0 1 1 The maximum bit rate is 128 Mbps + ((the binary coded value in 8 bits - 1011 1010) * 2 Mbps),

1 1 1 1 1 0 1 0 giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.

The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. Guaranteed bit rate for downlink (extended), octet 16

Bits

8 7 6 5 4 3 2 1

In MS to network direction and in network to MS direction:

0 0 0 0 0 0 0 0 Use the value indicated by the Guaranteed bit rate for downlink in octet 13.

For all other values: Ignore the value indicated by the

Guaranteed bit rate for downlink in octet 9

and use the following value:

0 0 0 0 0 0 0 1 The guaranteed bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps), 0 1 0 0 1 0 1 0 giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments.

0 1 0 0 1 0 1 1 The guaranteed bit rate is 16 Mlbps + ((the binary coded value in 8 bits - 01001010) * 1 Mbps),

1 0 1 1 1 0 1 1 The guaranteed bit rate is 128 Mbps + ((the binary coded value in 8 bits - 101 1 1010) * 2 Mbps),

The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol.

Maximum bit rate for uplink (extended), octet 17

This field is an extension of the Maximum bit rate for uplink in octet 8. The coding is identical to that of the Maximum bit rate for downlink (extended).

Guaranteed bit rate for uplink (extended), octet 18

This field is an extension of the Guaranteed bit rate for uplink in octet 12. The coding is identical to that of the Guaranteed bit rate for downlink (extended).

The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. 

Background

Issues:

- Rll 8C-HSDPA supports 336Mbps DL peak rate. However, UMTS QoS (section 10.5.6.5 of 24.008) cannot support bit rate higher than 256Mbps

QoS (MBR/GBR) related interfaces.

- NAS

- UTRAN Interfaces: lu, lur, lub

• Note: RAN colleague confirmed lu, lur, lub interfaces already support 1000Mbps

- SGSN/MME interfaces

• Gn/Gp (Gn-SGSN ^ SGSN/MME/GGSN/PGW)

I

• S3 (S4-SGSN -->MME)

• S4 (S4-SGSN ^->SGW)

- HLR/HSS interfaces: S6d, Gr

- PCC interfaces: Gx, Rx

- GGSN/PGW Interfaces: Gi/SGi

- Charging Interfaces: Ga, Rf, Bp, Ro

Solution Options

- Option A: Extending MBR/GBR

- Option B: EPS QoS

- Option C: Ignoring MBR in UMTS QoS profile

• Note: APN-AMBR and UE-AMBR already support 1000Mbps. AMBR was extended to UMTS in R9

Option A: Extending MBR/G BR/AM BR

Straight forward solution: extending MBR/GBR to higher bit rate range, e.g. up to 1000Mbps

Impacted Interfaces:

- Inter SGSN/MME interfaces

• G n/Gp (Gn-SGSN - - SGS N/M M E/G GS N/PGW)

- HLR/HSS interfaces: Gr

- PCC interfa

- GGSN/PGW Interfaces:

- Cha rging I nterfaces: Ga, Rf, Bp, Ro?

Impacted Entities

- U E, RNC, NodeB, G n-SGSN, S4-SGSN/M M E, GGSN/PGW, HLR/HSS,

CRF, AAA, CGF, Billing system, OCS?

Option B: EPS QoS

^• Using EPS QoS for UMTS

- S4-SGSN is thought to be part of EPC and hence support EPS QoS

- connect UTRAN to EPC (S4-SGSN)

^• Impacted Interfaces

- NAS

^• Impacted Entities

- UE, RNC, S4-SGSN, PCRF

Option C: Ignoring MBR

Proposal

- Ignore the MBR parameter in QoS profile

- Use AMBR (APN-AMBR and UE-AMBR) to restrict the bit rate of non-GBR bearers

• Note: AMBR was introduced to UMTS in R9

MBR

- A mandatory parameter in QoS profile of each PDP context to restrict the maximum bit rate of the PDP context

• UL MBR is enforced in UE and RNC

• DL MBR is enforced in GGSN and optionally in SGSN, RNC

- Usually set to the maximum PHY speed in HLR to for UE to fully use the PHY capability. This makes MBR almost useless

• E.g. set to 21Mbps when 64QAM is deployed

- Not supported in EPS for non-GBR bearers. Instead, AMBR is used to restrict the aggregate bit rate of non-GBR bearers.

Impacted interfaces

- No impact to any interface protocol

Impacted entities

- RNC, SGSN, GGSN/PGW need to be upgraded to ignore the MBR

- UE impact depends on implementation. Most UEs don't enforce MBR

Advantage of option C

- No change to interface protocol

- Achieves same QoS capability as EPS QoS

Impacted Interfaces NAS, Gn/Gp, Gi, Gx, NAS No

Ga, Rf, Bp, Ro UE impact Yes (NAS) Yes (NAS) Depends on

implementation. No impact to most of the UEs

Impacted Network Gn-SGSN, S4-SGSN, S4-SGSN, PCRF RNC, SGSN,

Entities GGSN/PGW, MME, GGSN/PGW

HLR/HSS, PCRF, AAA,

CGF, Billing system

EPC Required? No Yes No

R1 1 UE in legacy core SGSN ignores the UE sends both UMTS No issue

network extended bitrate QoS and EPS QpS to

para eters and serves SGSN. Legacy SGSN

the UE with 256Mbps ignores the EPS QoS

and serves the UE per

UMTS QoS

Legacy UE in R1 1 core No issue No issue. No issue

network (S4-SGSN understands

UMTS QoS)

Claims

1. A method of wireless communication, comprising:

activating or modifying a packet data protocol context in a UMTS network; and

establishing or modifying a quality of service parameter for the packet data protocol context, wherein the quality of service parameter corresponds to an evolved packet system quality of service parameter.

2. The method of claim 1, further comprising:

receiving, at a serving GPRS support node, from an access terminal, a UMTS quality of service parameter and the evolved packet system quality of service parameter;

ignoring the evolved packet system quality of service parameter; and serving the access terminal in accordance with the UMTS quality of service parameter.

3. The method of claim 1, further comprising:

receiving, at a mobility management entity, from an access terminal, a UMTS quality of service parameter and the evolved packet system quality of service parameter;

ignoring the UMTS quality of service parameter; and

serving the access terminal in accordance with the evolved packet system quality of service parameter.

4. The method of claim 1, wherein the quality of service parameter further corresponds to a UMTS quality of service parameter, such that all non- access stratum messages that include a quality of service parameter comprise both a UMTS quality of service parameter and an EPS quality of service parameter.

5. A method of wireless communication, comprising:

activating or modifying a oacket data orotocol context in a UMTS network: and

ignoring a maximum bit rate parameter in a UMTS QoS profile and restricting a bit rate corresponding to the packet data protocol context by utilizing an aggregate maximum bit rate parameter.

6. The method of claim 5, further comprising:

determining that the aggregate maximum bit rate parameter is available, wherein the ignoring of the maximum bit rate parameter is responsive to the determining that the aggregate maximum bit rate parameter is available.

7. The method of claim 5, wherein the restricting of the bit rate comprises ignoring the maximum bit rate parameter of a non-guaranteed bit rate PDP context or EPS bearer.

8. An apparatus for wireless communication, comprising:

means for activating or modifying a packet data protocol context in a UMTS network; and means for establishing or modifying a quality of service parameter for the packet data protocol context, wherein the quality of service parameter

corresponds to an evolved packet system quality of service parameter.

9. The apparatus of claim 8, further comprising:

means for receiving, at a serving GPRS support node, from an access terminal, a UMTS aualit _Jv of service oarameter and the evolved oacket svstem quality of service parameter;

means for ignoring the evolved packet system quality of service parameter; and

means for serving the access terminal in accordance with the UMTS quality of service parameter.

10. The apparatus of claim 8, further comprising:

means for receiving, at a mobility management entity, from an access terminal, a UMTS quality of service parameter and the evolved packet system quality of service parameter;

means for ignoring the UMTS quality of service parameter; and

means for serving the access terminal in accordance with the evolved packet system quality of service parameter.

11. The apparatus of claim 8, wherein the quality of service parameter further corresponds to a UMTS quality of service parameter, such that all non- access stratum messages that include a quality of service parameter comprise both a UMTS quality of service parameter and an EPS quality of service parameter.

12. An apparatus for wireless communication, comprising:

means for activating or modifying a packet data protocol context in a UMTS network; and

means for ignoring a maximum bit rate oarameter in a UMTS OoS orofile and restricting a bit rate corresponding to the packet data protocol context by utilizing an aggregate maximum bit rate parameter.

13. The apparatus of claim 12, further comprising:

means for determining that the aggregate maximum bit rate parameter is available,

wherein the means for ignoring the maximum bit rate parameter is configured to be responsive to the determining that the aggregate maximum bit rate parameter is available.

14. The apparatus of claim 12, wherein the means for restricting the bit rate comprises means for ignoring the maximum bit rate parameter of a non- guaranteed bit rate PDP context or EPS bearer.

15. A computer program product, comprising:

a computer-readable medium comprising code for: activating or modifying a packet data protocol context in a UMTS network; and

establishing or modifying a quality of service parameter for the packet data protocol context, wherein the quality of service parameter

corresponds to an evolved packet system quality of service parameter.

16. The corrmuter oroeram nroduct of claim 15. wherein the corrmuter- readable medium further comprises code for:

17. The computer program product of claim 15, wherein the computer- readable medium further mrrmri e rode fnr:

ignoring the UMTS quality of service parameter; and

18. The computer program product of claim 15, wherein the quality of service parameter further corresponds to a UMTS quality of service parameter, such that all non-access stratum messages that include a quality of service parameter comprise both a UMTS quality of service parameter and an EPS quality of service parameter.

19. A corrmuter oroeram oroduct. corrmrising:

a computer-readable medium comprising code for:

activating or modifying a packet data protocol context in a UMTS network; and

20. The computer program product of claim 19, wherein the computer- readable medium further comprises code for:

determining that the aggregate maximum bit rate parameter is available, wherein the code for ignoring the maximum bit rate parameter is configured to be responsive to the determining that the aggregate maximum bit rate parameter is available.

21. The computer program product of claim 19, wherein the code for restricting the bit rate comprises code for ignoring the maximum bit rate parameter of a non-guaranteed bit rate PDP context or EPS bearer.

22. An apparatus for wireless communication, comprising:

at least one processor; and

a memory coupled to the at least one processor,

wherein the at least one processor is configured to:

activate or modifying a packet data protocol context in a UMTS network: and

establish or modifying a quality of service parameter for the packet data protocol context, wherein the quality of service parameter corresponds to an evolved packet system quality of service parameter.

23. The apparatus of claim 22, wherein the at least one processor is further configured to:

receive, at a serving GPRS support node, from an access terminal, a UMTS quality of service parameter and the evolved packet system quality of service parameter;

ignore the evolved packet system quality of service parameter; and serve the access terminal in accordance with the UMTS quality of service parameter.

24. The apparatus of claim 22, wherein the at least one processor is configured to: receive, at a mobility management entity, from an access terminal, a UMTS quality of service parameter and the evolved packet system quality of service parameter;

ignore the UMTS quality of service parameter; and

serve the access terminal in accordance with the evolved packet system quality of service parameter.

25. The apparatus of claim 22, wherein the quality of service parameter further corresponds to a UMTS quality of service parameter, such that all non- access stratum messages that include a quality of service parameter comprise both a UMTS quality of service parameter and an EPS quality of service parameter.

26. An apparatus for wireless communication, comprising:

at least one processor; and

a memory coupled to the at least one processor,

wherein the at least one processor is configured to:

activate or modifying a packet data protocol context in a UMTS network; and

ignore a maximum bit rate parameter in a UMTS QoS profile and restrict a bit rate corresponding to the packet data protocol context by utilizing an aggregate maximum bit rate parameter.

27. The apparatus of claim 26, wherein the at least one processor is further configured to: determine that the aggregate maximum bit rate parameter is available, wherein the ignoring of the maximum bit rate parameter is responsive to the determining that the aggregate maximum bit rate parameter is available.

28. The apparatus of claim 26, wherein the restricting of the bit rate comprises ignoring the maximum bit rate parameter of a non-guaranteed bit rate PDP context or EPS bearer.