Transmission of the aggregate maximum bit rate from the MME to the E-node B and mobile terminal

Field of the invention

The invention relates to apparatus and methods for signalling communications in a packet data network, such as a 3^rd Generation Partnership Project (3GPP) cellular communication system.

Background of the Invention

Currently, 3rd generation cellular communication systems are being rolled out to further enhance the communication services provided to mobile phone users. The most widely adopted 3rd generation communication systems are based on Code Division Multiple Access (CDMA) and Frequency Division Duplex (FDD) or Time Division Duplex (TDD) technology. Further description of CDMA, and specifically of the Wideband CDMA (WCDMA) mode of UMTS, can be found in <nplcit id="ncit0001" npl-type="b"><text>'WCDMA for UMTS', Harri Holma (editor), Antti Toskala (Editor), Wiley &amp; Sons, 2001, ISBN 0471486876</text></nplcit>.

In 3GPP systems, such as the General Packet Radio System (GPRS), Evolved Packet System (EPS), the downlink communication endpoint, namely the mobile or handheld wireless communication unit, referred to as user equipment (UE) in 3G parlance, may have multiple simultaneous connections to a number of network elements. Such network elements typically comprise gateways (GWs), such as General GPRS Support nodes (GGSNs), packet data network (PDN) GWs, etc., in order to obtain access to different Packet Data Networks (PDNs) that facilitate the UE accessing a number of different services (for example facilitating access to corporate services as well as simultaneous access to the Internet).

In such systems, the amount of data being transferred between elements may be controlled by setting an aggregate maximum bit rate (AMBR), which is defined as an upper limit for non-guaranteed bit rate (GBR) communication bearers that are associated with a particular PDN connection that a UE has established.

In order to utilise an AMBR to limit a data amount sent to the respective PDNs, the AMBR needs to be enforced for each of the Non-Guaranteed Bit Rate (GBR) bearers connecting the UE with a particular GW providing access to a specific PDN.

In 3GPP (see, for example, 3GPP TS 23.401, 'GPRS enhancements for E-UTRAN access'; Release 8) the AMBR is enforced in the NodeB 110 in 3GPP for the UpLink (UL) traffic and in the GW (for example PDN-1 and PDN-2 GWs in 3GPP) for the respective DownLink (DL) traffic. This is a natural choice given that the NodeB and GWs are the traffic ingress points for the UL and DL traffic respectively. Furthermore, as radio resources are the most cost sensitive for a wireless Operator, it is not reasonable to 'pass through' UL traffic over an air-interface when the UL traffic will be later discarded. Thus, the Node B 110 has to be informed of the PDN connections that the UE 105 has established at any time and be in a position to associate the radio bearer that it assigns scheduling priorities with the UE-PDN connection that it belongs to. In other words the Node B 110 has to take into account the AMBR value and its relationship with each UE-PDN connection to the UL scheduling decisions it makes (for example by assignment of a prioritized bit rate PBR) . The Node-B 110 also controls the radio bearer establishment and management. According to the information received from the relevant Core Network (CN) 115 element, for example MME 120 in the 3GPP Evolved Packet System (EPS), the Node B 110 establishes the radio bearers for all the corresponding gateways (GW).

The characteristics of AMBR are somewhat different to other dynamic bearer parameters that are used in wireless and other communication systems to support a particular end-to-end QoS, in the sense that: <ol id="ol0001" compact="compact"><li>(i) An AMBR value is applied to a 'bundle' of Non-GBR bearers, for a specific UE-PDN connection, and not each one individually. Therefore, AMBR values require a special treatment by the network element that is responsible to enforce and police the AMBR, particularly when this element is responsible to schedule resources that are dynamically changing (such as the Node-B); and</li><li>(ii) The AMBR value is static subscriber information, stored in the subscriber database registry. Therefore, the AMBR value has to be communicated during the initial attach procedure, instead of being dynamically provided by the Policy Server as part of the bearer setup, in contrast to how the other dynamically changing QoS parameters are normally provided.</li></ol>

<figref idref="f0001">FIG. 2</figref> illustrates a known radio bearer establishment mechanism between the UE 105 and the Node-B 110, and the AMBR policing performed in the UL and DL respectively. It is noteworthy that a one-to-one relationship between the radio bearer 205 that connects the UE 105 to the Node-B 110 and access bearer 210 that terminates the traffic to the PDN GW 130 is maintained at the radio bearer 205 establishment. At a given time, there may be more than one radio bearer 205 and access bearer 210 established to the UE 105 for the purposes of providing different Quality of Service (QoS) treatment to different user applications or classes of users. In the DL, the logical elements of the scheduler in the Node-B 110 schedules the DL traffic based on a particular Quality of Service (QoS) of the radio bearers 205 that has been indicated to it by some QoS identifier during the bearer establishment as well as traffic volume used in the respective radio bearers 205. The AMBR policing for the DL traffic is carried out at the respective PDN GW 130, 135, 140, 145, given this is where the 3GPP Policy and Charging Enforcement Function (PCEF) is typically located since the PDN GWs 130, 140 are the first ingress points of downlink (DL) traffic.

If an AMBR level is exceeded in the DL, for a particular PDN connection, the exceeding traffic for all the access (non-GBR) bearers 210 from this PDN GW may be rate limited by the 3GPP PCEF in the PDN GW, in order to conform to the specified AMBR that has been communicated to the PDN GW at the initial bearer establishment.

Thus, UL resource is assigned by the appropriate logical element of the scheduler in the Node-B 110 according to the traffic volume reported by the UE, and allocated on a per UE basis. The scheduling of radio bearers 205 into the allocated grant is performed by the UE 105 using the logical function of the UL packet scheduler based on priorities that are communicated to it at the radio bearer establishment by the Node-B 110. In order to control the radio bearer scheduling by the UE 105, an UL rate control function that manages the sharing of UL resources between radio bearers has been specified in 3GPP. The scheduler in the Node-B 110 configures each radio bearer 205 with scheduling parameters, such as an absolute priority value and a Prioritised Bit Rate (PBR) value, based on the Quality of Service (QoS) parameters that are communicated by the core network (CN), such as the QoS label and the GBR value for the GBR bearers. In addition, a maximum bit rate (MBR) may be optionally configured per radio bearer 205. The assigned priority value and the PBR are signalled to the UE 105 together with the radio bearer configuration information. The priority value is decided by the Node-B 110 based on the QoS information received from the Core Network (CN) 115. In this manner, the PBR sets an UL rate control limit at the UE that applies per radio bearer and ensures that the UE 105 serves its radio bearers 205 in decreasing priority order up to their PBR value.

<u>If</u> any resources remain available, all the radio bearers 205 are served in a strictly decreasing priority order, up to their MBR (if configured). In a case where no AMBR is configured, the radio bearer 205 is served until either the data for that radio bearer 205 or the UL grant is exhausted, whichever occurs first. In general terms these parameters are the scheduling priority parameters that apply in the case of a 3GPP long-term evolution (LTE) wireless communication system.

However, the inventors have recognised and appreciated that the assignment of these scheduling parameters (for example PBR, priority and (optionally) MBR in a case of a 3GPP LTE wireless communication system) are not associated with the AMBR that applies to the entire UE-PDN connection that this radio bearer serves. This means, in effect, that if two bearers have the same QoS characteristics (for example, QoS label) and even though they belong to two different PDN connections (for example one with high AMBR values and one with low AMBI values), both radio bearers will receive the same scheduling treatment given that the AMBR is not communicated to the Node-B. Thus, this scenario is inefficient and wasteful of valuable resource. For example, if a bearer serves hyper text transfer protocol (HTTP) traffic from a virtual private network (VPN) with high AMBR and HTTP traffic from the Internet with a low AMBR, the same scheduling treatment at the Node-B 110 and the UE 105 will apply to both.

Consequently, current techniques are suboptimal. Hence, an improved mechanism to address the problem of handling AMBR over a cellular network would be advantageous.

Summary of the Invention

Accordingly, the invention seeks to mitigate, alleviate or eliminate one or more of the abovementioned disadvantages singly or in any combination.

According to a first aspect of the invention, there is provided, a method of signalling in a wireless communication system comprising a first network element serving a wireless communication unit with at least one packet data network (PDN) connection. The method comprises transmitting, by the first network element to the wireless communication unit, a signalling message relating to a wireless communication unit uplink (UL) PDN transmission. The signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.

In this manner, a mechanism to police the AMBR value in the Node-B without wasting unnecessarily uplink resource is provided by modifying, for example, the scheduler function in the Node-B to assign scheduling parameters relevant to the value of the UL AMBR that has to be enforced for radio bearers serving on UE-PDN connection.

Thus, embodiments of the invention may allow improved use of the communication resource by more efficiently utilising uplink resources in the communication system, for example, as a result of not admitting by the Node-B uplink (UL) traffic transmitted by the UE that may have to be dropped later if it exceeded the AMBR value. Consequently, the invention may provide increased throughput rates and increase the capacity in the communication system by not admitting traffic that may have to be subsequently dropped. Furthermore, the invention may allow improved performance, as perceived by the end-users, and also may allow the network operator to increase a number of users that can be supported by the system, whilst still being able to control the UL AMBR that is transmitted by the UEs to a certain PDN connection.

According to an optional feature of the invention, the aforementioned transmitting comprises transmitting as part of an establishment of the at least one PDN connection. In this manner, the signalling message may be implemented within existing messages to establish at least one PDN connection.

According to an optional feature of the invention, the signalling message comprises at least one AMBR value. In this manner, no association of a parameter needs to be generated by the network element may be avoided, with the AMBR value provided directly.

According to an optional feature of the invention, the signalling message comprises a parameter associated with the at least one AMBR value. In this manner, existing signalled parameters may be modified to reflect (be associated with) the at least one AMBR value.

According to an optional feature of the invention, the method further comprises associating, by the first network element, a received data packet from the wireless communication unit with a user transmission priority level associated with the at least one PDN connection based on the at least one AMBR value. In this manner, an user transmission priority level may be associated with the at least one PDN connection to reflect (be associated with) the at least one AMBR value.

According to an optional feature of the invention, at least one PDN identifier per PDN connection may be associated based on the at least one AMBR value.

According to an optional feature of the invention, the method further comprises deriving, by the first network element, a maximum bit rate (MBR) value per PDN connection of the wireless communication unit to the first network element based on the at least one AMBR level.

According to an optional feature of the invention, the wireless communication system further comprises a first network element operably coupled to a second network element over a PDN connection. The method further comprises transmitting, by the second network element to the first network element, the signalling message relating to the wireless communication unit UL PDN transmission. In this manner, an element in the core network, for example a mobility management entity (MME), may be configured to access and communicate the AMBR value, for example via a user profile of the wireless communication unit that comprises at least one AMBR value per PDN connection.

According to an optional feature of the invention, the method further comprises identifying, by the first network element, when an allocation of a user transmission priority value exceeds the AMBR value applied to the at least one PDN connection.

According to an optional feature of the invention, the method further comprises re-allocating, by the first network element, at least one user transmission priority value associated with the at least one PDN connection when the AMBR value is exceeded.

According to an optional feature of the invention, the aforementioned step of transmitting comprises transmitting as part of an attach procedure to establish the at least one PDN connection of the wireless communication unit to the first network element. In this manner, the signalling message may be implemented within existing messages to establish at least one PDN connection.

In one optional embodiment, the at least one PDN connection of the wireless communication unit comprises a plurality of PDN connections that the wireless communication unit has access to, for example the attach procedure may establish a plurality of PDN connections that the wireless communication unit has access to.

In one optional embodiment, the method may be applied to a 3^rd Generation Partnership Project (3GPP) cellular communication system. In one optional embodiment, the method may be applied to a 3GPP Evolved Packet System (EPS) architecture.

In one optional embodiment, the method may be applied to a WiMAX cellular communication system.

According to a second aspect of the invention, there is provided a wireless communication unit adapted to perform the wireless communication unit operations hereinbefore described.

According to a third aspect of the invention, there is provided a network element adapted to perform the network element operations hereinbefore described.

According to a fourth aspect of the invention, there is provided a network element arranged to provide signalling in a wireless communication system to a wireless communication unit over at least one packet data network (PDN) connection. The network element comprises logic for transmitting a signalling message relating to a wireless communication unit uplink (UL) PDN transmission to the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.

According to a fifth aspect of the invention, there is provided a wireless communication unit arranged to receive a signalling message in a wireless communication system from a network element over at least one packet data network (PDN) connection. The wireless communication unit comprises logic for receiving a signalling message relating to an uplink (UL) PDN transmission of the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.

According to a sixth aspect of the invention, there is provided a method of signalling in a wireless communication system comprising a first network element serving a wireless communication unit with at least one packet data network (PDN) connection. The method comprises receiving, by the wireless communication unit from a first network element, a signalling message relating to an uplink (UL) PDN transmission from the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.

According to a seventh aspect of the invention, there is provided a computer program product comprising program code for signalling in a wireless communication system from a network element to a wireless communication unit over at least one packet data network (PDN) connection. The computer program product comprises program code for transmitting a signalling message relating to a wireless communication unit uplink (UL) PDN transmission to the wireless communication unit, wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.

These and other aspects, feature and advantages of the invention will be apparent from, and elucidated with reference to, the embodiments described hereinafter.

Brief Description of the Drawings

<ul id="ul0001" list-style="none"><li><figref idref="f0001">FIG. 1</figref> illustrates a known 3GPP system using AMBR.</li><li><figref idref="f0001">FIG. 2</figref> illustrates a known AMBR policing, taking place in the Node B for the UL and GW for the DL traffic.</li></ul>

Embodiments of the invention will be described, by way of example only, with reference to the accompanying drawings, in which: <ul id="ul0002" list-style="none"><li><figref idref="f0002">FIG. 3</figref> illustrates a system architecture adapted in accordance with some embodiments.</li><li><figref idref="f0003">FIG. 4</figref> illustrates an attach procedure and bearer establishment in accordance with some embodiments.</li><li><figref idref="f0004">FIG. 5</figref> illustrates an attach procedure and bearer establishment of an EPS/LTE system in accordance with some embodiments.</li><li><figref idref="f0005">FIG. 6</figref> illustrates a scheduling mechanism for the group of bearers corresponding to the same UE-PDN connection in accordance with some embodiments.</li><li><figref idref="f0006">FIG. 7</figref> illustrates a typical computing system that may be employed to implement processing functionality in embodiments of the invention.</li></ul>

Detailed Description of Embodiments of the Invention

The following description focuses on embodiments of the invention applicable to a Evolved-UMTS (Universal Mobile Telecommunication System) cellular communication system and in particular to a Evolved Packet System (EPS) core network (CN) architecture within a 3^rd generation partnership project (3GPP) system. However, it will be appreciated that the invention is not limited to this particular cellular communication system, but may be applied to other cellular communication systems.

Embodiments of the invention propose to obtain the AMBR parameter with its associated PDN connection identifier from a static subscriber database when the communication endpoint bootstraps and attaches initially in the network. Furthermore, and advantageously, the AMBR is communicated with its associated PDN connection identifier to the network element that is responsible to police and enforce the AMBR per PDN connection.

In addition, some embodiments propose a network element enforcing the AMBR for a plurality of PDN connections that the communication endpoint, for example a UE, may have in place. Thus, the network element is configured to be responsible to serve multiple communication endpoints in an environment of dynamically changing resources.

Referring now to <figref idref="f0002">FIG. 3</figref>, a wireless communication system 300 is shown in outline, in accordance with one embodiment of the invention. In this embodiment, the wireless communication system 300 is compliant with, and contains network elements capable of operating over, a universal mobile telecommunication system (UMTS) air-interface. In particular, the embodiment relates to a system's architecture for an Evolved-UTRAN (E-UTRAN) wireless communication system, which is currently under discussion in 3GPP. This is also referred to as Long Term Evolution (LTE).

The architecture consists of radio access network (RAN) and core network (CN) elements, with the core network 304 being coupled to external networks 302 named Packet Data Networks (PDNs), such as the Internet or a corporate network. The main component of the RAN is an eNodeB (an evolved NodeB) 310, 320, which is connected to the CN 304 via S1 interface and to the UEs 320 via an Uu interface. The eNodeB 310, 320 controls and manages the radio resource related functions. The series of Node Bs 310, 320 typically perform lower layer processing for the network, performing such functions as Medium Access Control (MAC), formatting blocks of data for transmission and physically transmitting transport blocks to UEs 325. In addition to these functions that the NodeB's usually perform, the adapted Node Bs 310 scheduler logical element is additionally arranged to interact with the logical element of the PEF that is assigned to enforce the UL AMBR for non-GBR bearers that belong to a certain UE-PDN connection, in order to provide a sub-set of functions that the 3GPP PCEF located in the PDN GW 305 implements in the downlink (DL) such rate limiting. An additional limitation exists in that the rate limiting function of a PEF logical element in the UL has to meet a certain performance, and that it cannot simply 'pass-through' the traffic over-the-air and then drop it. Hence, the adapted schedulers in the Node Bs 310 are arranged to derive adequate scheduling parameters that will be communicated to the UE 320 based on the AMBR that has to be enforced by the logical element of a Policy Enforcement Function (PEF) located in the Node-B 310, in order to support this operation.

The CN 304 has three main components: serving GW 306, the PDN GW (PGW) 305 and mobility management entity (MME) 308. The serving-GW 306 controls the U-plane (user-plane) communication. The PDN-GW 305 controls access to the appropriate external network (e.g. PDN). In addition to this operation, in one embodiment, the PDN-GW 305 is arranged to police the DL AMBR for a number of non-GBR bearers that serve this particular UE-PDN connection. The MME 308 controls the c-plane (control plane) communication, where the user mobility, paging initiation for idle mode UEs, bearer establishment, and QoS support for the default bearer are handled by the MME 308. In addition to these operations, in one embodiment, the MME 308 is arranged to derive, normally using database query mechanisms to the Home Subscriber Server (HSS) 330 with protocols such as DIAMETER (as in RFC3588) or RADIUS (as in RFC2865), the UL and DL AMBR values that apply to each PDN connection that the UE 320 is allowed to establish. The UL and DL AMBR values are based on the UE's subscription profile and provisioning information that may be stored in a static database, such as an HSS 330 that may contain the user credentials that are used for the UE's authentication, user class in terms of tier of service and other static information. The UL AMBR value is communicated to the logical element of the PEF in the Node B 310 that is assigned to enforce the UL AMBR and the DL AMBR value is communicated to the 3GPP PCEF in the PDN GW 305 that the UE 320 initially attaches to.

E-UTRAN RAN is based on OFDMA (orthogonal frequency division multiple access) in downlink (DL) and SC-FDMA (single carrier frequency division multiple access) in uplink (UL).the further information of radio frame formats and physical layer configuration used in E-UTRAN can be found in TS 36.211(3GPP TS 36.211 v.1.1.1 (2007-05), '3GPP Technical specification group radio access network, physical channels and modulation (release 8)',

The Node-Bs 310 are connected wirelessly to the UEs 325. Each Node-B contains one or more transceiver units 312, 322 operably coupled to respective signal processing logic 314, 324. Similarly, each of the UEs comprise transceiver unit 327 operably coupled to signal processing logic 329 (with one UE illustrated in such detail for clarity purposes only) and communicate with the Node B supporting communication in their respective location area. The system comprises many other UEs and Node-Bs, which for clarity purposes are not shown.

Signalling of AMBR value

In accordance with one embodiment of the invention, the interaction between the UE 325, Node-B 310, MME 308, GW 305, 306 and AAA have been adapted to support improved usage of AMBR signalling. In particular, the AMBR value per the UE-PDN connection, together with the PDN gateway identifier from the CN to the Radio access network is communicated, to adequately communicate the available PDN connections that the UE has in place. This mechanism is described below in further detail with respect to <figref idref="f0003">FIG. 4</figref>.

Referring now to <figref idref="f0003">FIG. 4</figref>, a single signalling flow diagram is illustrated showing the two possibilities for the end-to-end bearer establishment in a wireless communication system: <ol id="ol0002" compact="compact"><li>(i) UE-initiated; and</li><li>(ii) Network-initiated</li></ol>

It is noteworthy that this signalling exchange may include also a number of other messages and other information that are not relevant to the description of the embodiments described herein.

In step 430, the UE 325 initiates an Attach procedure by, say, sending its temporary identity (for example the UE System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (S-TMSI) or Packet-Temporary Mobile Subscriber Identity (P-TMSI) to the Node-B 310. In a case of an UE-initiated bearer establishment, the Access Point Name (APN) will indicate the appropriate Gateway 420 serving the PDN that the UE 325 requires to connect to.

In a case of network-initiated there is no need for the UE 325 to provide any indication as the MME 308 will establish a connection to all the PDNs that the UE 325 is allowed to access from its subscription profile.

In step 435, the Node-B 310 derives from the temporary identity of the UE 325, for example the UE S-TMSI or P-TMSI, the appropriate MME 308 that it has to forward the Attach request. In steps 440, 445 the MME 308 completes the authentication procedure with the UE 325.

In step 450, the MME 308 derives the Subscriber Info of the UE 325, which includes the information on all the PDNs the UE 325 has access to. At this stage the MME 308 will have to be able to construct a table for the UE 325, for example as illustrated in Table 1 below: <tables id="tabl0001" num="0001"><table frame="all"><title>TABLE 1</title><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="24mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top"><b><i>UE (imsi=xxxxxyyyyyzzzzz)</i></b></entry></row></thead><tbody><row><entry>APN1</entry><entry>Ul_ambr1, dl_ambr2</entry></row><row><entry>APN2</entry><entry>Ul_ambr2, dl_ambr2</entry></row><row><entry>APN3</entry><entry>Ul_ambr3, dl_ambr3</entry></row></tbody></tgroup></table></tables>

In step 455, the MME 308 creates and sends a bearer request (or requests a bearer depending on whether it is a UE-initiated establishment or a network-initiated establishment) to create connection(s) to the GW(s) 305, 306.

In a case of an UE-initiated establishment, given that the UE 325 would have indicated in step 430 the sole GW address through the APN that it requires to connect to, the MME 308 will send the bearer request to this GW 305, 306 only. The bearer request contains the DL AMBR that the GW 305, 306 has to enforce for this connection.

In a case of network-initiated bearer establishment, the MME 308 sends bearer requests to all GWs serving the PDNs that the UE 325 has access to, as for example identified by the list of APNs it has obtained in step 450. In one embodiment, the requests contain the DL AMBRs for each APN that the relevant GWs have to enforce.

In step 460, the GW(s) 305, 306 create and send the bearer response(s). In case of UE-initiated only the selected GW 305, 306 that received the bearer request sends the response.

In step 465, the MME 308 sends the Attach Response to the Node-B 310 containing the QoS information and the value of the UL AMBR. In a case of an UE-initiated establishment, the Attach Response message will contain only the information required by the particular UE PDN connection. In a case of a network-initiated establishment, the Attach Response message contains all the information on QoS and UL AMBRs for all the APNs that the UE has access to.

In step 470, the Node-B 310 establishes the relevant radio bearer(s), subject to the information provided in step 465. In a case of an UE-initiated establishment, this leads to the establishment of only one radio bearer corresponding to this particular UE-PDN connection. In a case of a network-initiated establishment, the Node-B 310 at this stage establishes all the radio bearers to serve all the required PDN connections for the UE.

The mechanism employed by the Node-B 310 to handle the information provided in step 465, in order to determine scheduling parameters is as follows.

Referring now to <figref idref="f0004">FIG. 5</figref>, an enhanced embodiment is described with respect to AMBR signalling in the core network of an E-UTRAN. As defined in 3GPP TS 23.401, 'GPRS enhancements for E-DTRAN access'; Release 8, the AMBR associated with each PDN that the UE 405 has access to is stored in the home subscriber server (HSS) (equivalent to the home location register in earlier GSM-based systems) based on subscriber information. The AMBR is retrieved by the MME 415 as part of the 'Attach' procedure illustrated in step 430, 435 of <figref idref="f0003">FIG. 4</figref>.

As an example, the following information may be stored in the HSS for each UE, as illustrated in Table 2 below: <tables id="tabl0002" num="0002"><table frame="all"><title>TABLE 2:</title><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="24mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top"><b><i>UE (imsi=xxxxxyyyyyzzzzz)</i></b></entry></row></thead><tbody><row><entry>APN1</entry><entry>Ul_ambr1, Dl_ambr2</entry></row><row><entry>APN2</entry><entry>Ul_ambr2, Dl_ambr2</entry></row><row><entry>APN3</entry><entry>Ul_ambr3, Dl_ambr3</entry></row></tbody></tgroup></table></tables>

This information is retrieved in the MME 415 after the UE attaches, and should be provided in the PDN GW 422 and eNodeB 410 for DL and UL policing respectively.

In this regard, the DL value of the AMBR may be sent from the MME 415 to the PDN GW 422 as part of a 'Create

Default bearer message', as shown in step 550, in order for the PDN GW 422 to be able to police the AMBR in the DL. It is also envisaged, in this regard, that the UL AMBR may also be sent from the MME 415 to the eNodeB 410 as part of an 'Attach Accept' message, as illustrated in step 555.

Thus, the following additional signalling is proposed to the 'Attach' procedure of EPS/LTE as described in 3GPP TS 23.401, 'GPRS enhancements for E-UTRAN access'; Release 8, to achieve the aforementioned communications.

The HSS 510 sends an Insert Subscriber Data message (for example IMSI, Subscription Data) to the new MME 412 in step 515. The Subscription Data contains the Default APN and the UL and DL AMBR values for the APNs that the UE 405 has access to. The new MME 412 validates the UE's presence in the (new) Tracking Area/Location Area (TA/LA). If, due to regional subscription restrictions or access restrictions, the UE 405 is not allowed to attach in the TA/LA, the new MME 412 may be able to reject the Attach Request in step 435 with an appropriate cause, and may return an 'Insert Subscriber Data Ack' message 520 to the HSS 510. If subscription checking fails for other reasons, the new MME 412 may reject the Attach Request 430, 435 with an appropriate cause and returns an Insert Subscriber Data Ack message to the HSS including an error cause. If all checks are successful then the new MME 412 constructs a context for the UE 405 and returns an Insert Subscriber Data Ack message 520 to the HSS 510. The HSS may send an update location acknowledge message to the new MME 412, as shown in step 525, in accordance with the existing process described in section 5.3.2 of 3GPP TS 23.401, `GPRS enhancements for E-UTRAN access'; Release 8.

In step 530 the new MME 412 selects a Serving GW 420 as described under 'GW Selection Function' , in the aforementioned standard, and sends a Create Default Bearer Request (IMSI, MME Context ID, Default Bearer QoS, DL AMBR for the default APN) message to the selected Serving GW 420.

In step 535, the Serving GW 420 creates a new entry in its EPS Bearer table and sends a Create Default Bearer Request (Serving GW Address for the user plane, Serving GW TEID of the user plane, Serving GW TEID of the control plane, Default Bearer QoS, DL AMBR for the default APN) message to the PDN GW 422.

In step 540, the PDN GW 422 may interact with the Policy and Charging Rules Function (PCRF) 505, to obtain the default policy control and charging (PCC) rules for the UE 405, if PCRF is applied in the network. The PDN GW 422 then stores the DL AMBR for the UE 405 for the default bearer.

Subsequent messages 545 and 550 are sent in accordance with the existing process described in section 5.3.2 of 3GPP TS 23.401, 'GPRS enhancements for E-UTRAN access'; Release 8.

In step 555, the new MME 412 sends an 'Attach Accept' (including S-TMSI, PDN address, TA/LA List) message to the eNodeB 410. S-TMSI is included if the new MME allocates a new S-TMSI. This message may be contained in an S1_MME control message Initial Context Setup Request. This S1 control message may also include a security context for the UE 405 and QoS information needed to set up the radio bearer, as well as the Terminal Entity Identifier (TEID) at the Serving GW 420 used for user plane and the address of the Serving GW 420 for user plane.

The PDN address assigned to the UE 405 is included in this message. The APN of the PDN GW 422 that the UE 405 is connected to may also be included in this message. The new MME 412 sends the UL AMBR to the eNodeB 410.

In step 560, the eNodeB 410 sends a Radio Bearer Establishment Request to the UE 405 and the Attach Accept message (S-TMSI, PDN address, TA List, APN) 555 will be sent along to the UE 405.

Thereafter, messages 565-590 are sent as described in section 5.3.2 of 3GPP TS 23.401, "GPRS enhancements for E-UTRAN access"; Release 8.

AMBR handling in the Radio Access Network, for example the Node-B

In accordance with one embodiment of the invention; the interaction between the UE 325, Node-B 310, MME 308, GW 305, 306 and AAA have also been adapted to support improved usage of AMBR information signalled between elements. In particular, apparatus and methods are proposed to allow the radio access network (RAN) to take into account the information provided from the Core Network (CN), to be able to prioritise traffic belonging to a particular PDN connection subject to the AMBR. In an enhanced embodiment, apparatus and methods are also proposed to enforce the AMBR in the Node-B 310 . The proposed mechanism configures the scheduler in the Node-B 310 to assign appropriate scheduling priority parameter values to the radio bearers (for example, PBR, priority values, MBR in 3GPP) in order to reflect the enforcement of the UL AMBR applied to the entire set of radio bearers corresponding to a UE-PDN connection that the PEF has to perform, in addition to the communicated QoS information. In addition, a mechanism is proposed to optimise the signalling between the Node B 410 and the UE 405 (reduced signalling overhead) to assign the scheduling priorities and amend them as and when necessary in order to police the AMBR that applies to the UE-PDN connection.

In a case where a UE 405 has multiple PDN connections, PEF logic in the Node-B 410 needs to police UL traffic belonging to each PDN connection separately. Therefore, the PEF logic in the Node-B 410 should have been informed of any association between the access bearers and the PDN connection during the bearer establishment.

In step 470 of <figref idref="f0003">FIG. 4</figref>, the simplistic case of traffic policing is where the AMBR value of a particular PDN connection is exceeded by the UL traffic, where the data may be dropped at the Node-B 410. However, the data would have already been transmitted over the air-interface. Thus, dropping the already transmitted data at the Node-B 410 would result in inefficient radio resource usage.

Although embodiments of the invention are described with reference to the MME obtaining at least one aggregate maximum bit rate (AMBR) value, and communicating this to the Node-B's PEF logic, it is envisaged that in alternative embodiments it may be possible for the Node-B PEF logic to obtain the UL AMBR value direct. In this scenario, the Node-Bs are arranged to have a direct interface to the AAA Server (or a home subscriber server (HSS) in a case of 3GPP systems) and perform the mobility management, user authentication and QoS provisioning for the default bearer functions themselves. In other words, in such a scenario, all the current functions of the MME are embodied in the Node-B.

Further, although embodiments of the invention are described with reference to the MME obtaining at least one aggregate maximum bit rate (AMBR) value and communicating this to the Node-B, with the Node-B generating an association of the AMBR with the at least one PDN Identifier, it is envisaged that in alternative embodiments it may be possible for the Node-B to obtain to transmit the AMBR value directly to the wireless communication unit (for example the UE). In this scenario, the UE will be responsible for the policing of the UL AMBR for the number of radio bearers that belong to a specific UE-PDN connection. In addition to the AMBR, in this scenario, the information of the PDN identifier may be communicated by the Node-B to the UE upon the radio bearer establishment. The inventors though recognise that this scenario has a limitation that the policing of the AMBR that is associated with the management of radio resources will be relayed solely to the UE that is traditionally considered as an 'untrusted' entity in similar communication systems.

AMBI handling in the NodeB based on assigning absolute priority per PDN connection

Referring now to <figref idref="f0005">FIG. 6</figref>, a possible mechanism to perform scheduling in the NodeB is illustrated. The mechanism is based on the AMBR values that have been communicated as part of the bearer establishment, the Identifier (ID) for PDN GW 422 or 424 (for example APN in 3GPP) may be signalled to the UE 405 together with the assigned scheduling priority parameters (for example absolute priority value and PBR in 3GPP) during the radio bearer configuration. In addition to this signalling, an absolute priority is also signalled to apply to the group of bearers that are related to a specific PDN connection. For example, the priority that applies to each radio bearer may be defined in two steps. First, each PDN connection is provided an absolute priority value (P_i 505 P_z 510). Secondly, the priority of the radio bearer is assigned a relative value, relative to the absolute priority value of the PDN connection. Thus, the UE 405 may calculate the absolute priority value of the radio bearer by considering the absolute priority value of the PDN connection and the relative priority of the radio bearer.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units or processors, for example with respect to the broadcast mode logic or management logic, may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

<figref idref="f0006">FIG. 7</figref> illustrates a typical computing system 700 that may be employed to implement processing functionality in embodiments of the invention. Computing systems of this type may be used in the UE (which may be an integrated device, such as a mobile phone or a USB/PCMCIA modem), or NodeB (in particular, the scheduler of the IvodeB), core network elements, such as the GGSN, and RNCs, for example. Those skilled in the relevant art will also recognize how to implement the invention using other computer systems or architectures. Computing system 700 may represent, for example, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment. Computing system 700 can include one or more processors, such as a processor 704. Processor 704 can be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control logic. In this example, processor 704 is connected to a bus 702 or other communications medium.

Computing system 700 can also include a main memory 708, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by processor 704. Main memory 708 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Computing system 700 may likewise include a read only memory (ROM) or other static storage device coupled to bus 702 for storing static information and instructions for processor 704.

The computing system 700 may also include information storage system 710, which may include, for example, a media drive 712 and a removable storage interface 720. The media drive 712 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive. Storage media 718 may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive 714. As these examples illustrate, the storage media 718 may include a computer-readable storage medium having stored therein particular computer software or data.

In alternative embodiments, information storage system 710 may include other similar components for allowing computer programs or other instructions or data to be loaded into computing system 700. Such components may include, for example, a removable storage unit 722 and an interface 720, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units 722 and interfaces 720 that allow software and data to be transferred from the removable storage unit 718 to computing system 700.

Computing system 700 can also include a communications interface 724. Communications interface 724 can be used to allow software and data to be transferred between computing system 700 and external devices. Examples of communications interface 724 can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via communications interface 724 are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by communications interface 724. These signals are provided to communications interface 724 via a channel 728. This channel 728 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of a channel include a phone line, a cellular phone link, an RF link, a network interface, a local or wide area network, and other communications channels.

In this document, the terms 'computer program product' 'computer-readable medium' and the like may be used generally to refer to media such as, for example, memory 708, storage device 718, or storage unit 722. These and other forms of computer-readable media may store one or more instructions for use by processor 704, to cause the processor to perform specified operations. Such instructions, generally referred to as 'computer program code' (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 700 to perform functions of embodiments of the present invention. Note that the code may directly cause the processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system 700 using, for example, removable storage drive 714, drive 712 or communications interface 724. The control logic (in this example, software instructions or computer program code), when executed by the processor 704, causes the processor 704 to perform the functions of the invention as described herein.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality, may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to 'a', 'an', 'first', 'second', etc. do not preclude a plurality.

The following numbered clauses provide further example embodiments of the invention: <ol id="ol0003"><li>1. A method of signalling in a wireless communication system comprising a first network element serving a wireless communication unit with at least one packet data network (PDN) connection, the method comprising: <ul id="ul0003" list-style="none" compact="compact"><li>transmitting, by the first network element to the wireless communication unit, a signalling message relating to a wireless communication unit uplink (UL) PDN transmission wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.</li></ul></li><li>2. The method of Clause 1, wherein transmitting comprises transmitting as part of an establishment of the at least one PDN connection.</li><li>3. The method of Clause 1 or Clause 2, wherein the signalling message comprises at least one AMBR value.</li><li>4. The method of any of Clauses 1, 2 and 3, wherein the signalling message comprises a parameter associated with the at least one AMBR value.</li><li>5. The method of Clause 4, further comprising associating, by the first network element, a received data packet from the wireless communication unit with a user transmission priority level associated with the at least one PDN connection based on the at least one AMBR value.</li><li>6. The method of Clause 4 or Clause 5, further comprising associating, by the first network element, at least one PDN identifier per PDN connection based on the at least one AMBR value.</li><li>7. The method of any of Clauses 4 to 6, further comprising, deriving, by the first network element, a maximum bit rate (MBR) value per PDN connection of the wireless communication unit to the first network element based on the at least one AMBR level.</li><li>8. The method any of Clauses 4 to 7 wherein the wireless communication system further comprises a first network element operably coupled to a second network element over a PDN connection, the method further comprising transmitting, by the second network element to the first network element, the signalling message relating to the wireless communication unit UL PDN transmission.</li><li>9. The method of Clause 8 further comprising obtaining, by the second network element, a user profile of the wireless communication unit that comprises at least one AMBR value per PDN connection.</li><li>10. The method of Clauses 1 to 9, further comprising identifying, by the first network element, when an allocation of a user transmission priority value exceeds the AMBR value applied to the at least one PDN connection.</li><li>11. The method of Clause 10 further comprising reallocating, by the first network element, at least one user transmission priority value associated with the at least one PDN connection when the AMBER value is exceeded.</li><li>12. The method of any of Clauses 1 to 11, wherein transmitting comprises transmitting as part of an attach procedure to establish the at least one PDN connection of the wireless communication unit to the first network element.</li><li>13. The method of Clause 12 wherein the attach procedure establishes a plurality of PDN connections that the wireless communication unit has access to.</li><li>14. The method of any of Clauses 1 to 13, wherein the at least one PDN connection of the wireless communication unit comprises a plurality of PDN connections that the wireless communication unit has access to.</li><li>15. The method of any of Clauses 1 to 14 when applied to a 3^rd Generation Partnership Project (3GPP) cellular communication system.</li><li>16. The method of Clause 15, when applied to a 3GPP Evolved Packet System (EPS) architecture, where the first network element is an eNodeB.</li><li>17. The method of any of Clauses 1 to 16, when applied to a WiMAX cellular communication system.</li><li>18. A wireless communication unit adapted to perform the wireless communication unit operations of any of the preceding Clauses.</li><li>19. A network element adapted to perform the network element operations of any of Clauses 1 to 17.</li><li>20. A network element arranged to provide signalling in a wireless communication system to a wireless communication unit over at least one packet data network (PDN) connection, the network element comprising: <ul id="ul0004" list-style="none" compact="compact"><li>logic for transmitting a signalling message relating to a wireless communication unit uplink (UL) PDN transmission to the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.</li></ul></li><li>21. The network element of Clause 20 wherein the logic for transmitting comprises logic for transmitting as part of an establishment of the at least one PDN connection.</li><li>22. The network element of Clause 20 or Clause 21 wherein the signalling message comprises at least one AMBR value.</li><li>23. The network element of any of Clauses 20 to 22 wherein the signalling message comprises a parameter associated with the at least one AMBR value.</li><li>24. The network element of Clause 23 further comprising logic for associating a received data packet from the wireless communication unit with a user transmission priority level associated with the at least one PDN connection based on the at least one AMBR value.</li><li>25. The network element of Clause 23 or Clause 24 further comprising logic for associating at least one PDN identifier per PDN connection based on the at least one AMBR value.</li><li>26. The network element of any of Clauses 23 to 25 further comprising logic for deriving a maximum bit rate (MBR) value per PDN connection of the wireless communication unit to the network element based on the at least one AMBR level.</li><li>27. The network element of any of Clauses 23 to 26 further comprising logic for obtaining a user profile of the wireless communication unit that comprises at least one AMBR value per PDN connection.</li><li>28. The network element of any of Clauses 20 to 27 further comprising logic for identifying when an allocation of a user transmission priority value exceeds the AMBR value applied to the at least one PDN connection.</li><li>29. The network element of Clause 28 further comprising logic for re-allocating at least one user transmission priority value associated with the at least one PDN connection when the AMBR value is exceeded.</li><li>30. The network element of any of Clauses 20 to 29 wherein logic for transmitting comprises logic for transmitting as part of an attach procedure to establish the at least one PDN connection of the wireless communication unit to the network element.</li><li>31. The network element of Clause 30 wherein the attach procedure establishes a plurality of PDN connections that the wireless communication unit has access to.</li><li>32. The network element of any of Clauses 20 to 31 wherein the at least one PDN connection of the wireless communication unit comprises a plurality of PDN connections that the wireless communication unit has access to.</li><li>33. The network element of any of Clauses 20 to 32 wherein the network element is a Node-B arranged to provide a signalling message in a 3&lt;rd&gt; Generation Partnership Project (3GPP) cellular communication system.</li><li>34. The network element of Clause 33 wherein the network element is an eNodeB arranged to provide a signalling message in a 3GPP Evolved Packet System (EPS) architecture.</li><li>35. The network element of any of Clauses 20 to 34 arranged to provide a signalling message in a WiMAX cellular communication system.</li><li>36. A wireless communication unit arranged to receive a signalling message in a wireless communication system from a network element over at least one packet data network (PDN) connection, the wireless communication unit comprising: <ul id="ul0005" list-style="none" compact="compact"><li>logic for receiving a signalling message relating to an uplink (UL) PDN transmission of the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.</li></ul></li><li>37. A method of signalling in a wireless communication system comprising a first network element serving a wireless communication unit with at least one packet data network (PDN) connection, the method comprising: <ul id="ul0006" list-style="none" compact="compact"><li>receiving, by the wireless communication unit from a first network element, a signalling message relating to an uplink (UL) PDN transmission from the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.</li></ul></li><li>38. A computer program product comprising program code for signalling in a wireless communication system from a network element to a wireless communication unit over at least one packet data network (PDN) connection, the computer program product comprising program code for: <ul id="ul0007" list-style="none" compact="compact"><li>transmitting a signalling message relating to a wireless communication unit uplink (UL) PDN transmission to the wireless communication unit wherein the signalling message comprises a parameter indicative of at least one aggregate maximum bit rate (AMBR) value.</li></ul></li><li>39. The computer program product of Clause 38 wherein the program code for transmitting comprises program code for transmitting as part of an establishment of the at least one PDN connection.</li><li>40. The computer program product of Clause 38 or Clause 39 wherein the signalling message comprises at least one AMBR value.</li><li>41. The computer program product of any of Clauses 38 to 40 wherein the signalling message comprises a parameter associated with the at least one AMBR value.</li><li>42. The computer program product of Clause 41 further comprising program code for associating a received data packet from the wireless communication unit with a user transmission priority level associated with the at least one PDN connection based on the at least one AMBR value.</li><li>43. The computer program product of Clause 41 or Clause 42 further comprising program code for associating at least one PDN identifier per PDN connection based on the at least one AMBR value.</li><li>44. The computer program product of any of Clauses 41 to 43 further comprising program code for deriving a maximum bit rate (MBR) value per PDN connection of the wireless communication unit to the network element based on the at least one AMBR level.</li><li>45. The computer program product of any of Clauses 41 to 44 further comprising program code for obtaining a user profile of the wireless communication unit that comprises at least one AMBR value per PDN connection.</li><li>46. The computer program product of any of Clauses 38 to 45 further comprising program code for identifying when an allocation of a user transmission priority value exceeds the AMBR value applied to the at least one PDN connection.</li><li>47. The computer program product of Clause 46 further comprising program code for re-allocating at least one user transmission priority value associated with the at least one PDN connection when the AMBR value is exceeded.</li><li>48. The computer program product of any of Clauses 38 to 47 wherein the program code for transmitting comprises program code for transmitting as part of an attach procedure to establish the at least one PDN connection of the wireless communication unit to the network element.</li><li>49. The computer program product of Clause 48 wherein the attach procedure establishes a plurality of PDN connections that the wireless communication unit has access to.</li><li>50. The computer program product of any of Clauses 38 to 49 wherein the at least one PDN connection of the wireless communication unit comprises a plurality of PDN connections that the wireless communication unit has access to.</li><li>51. The computer program product of any of Clauses 38 to 50 arranged to provide a signalling message in a 3^rd Generation Partnership Project (3GPP) cellular communication system.</li><li>52. The computer program product of any of Clauses 38 to 51 arranged to provide a signalling message in a 3GPP Evolved Packet System (EPS) architecture.</li><li>53. The computer program product of any of Clauses 38 to 52 arranged to provide a signalling message in a WiMAX cellular communication system.</li></ol>