GB2481715A

GB2481715A - Control of transmission of data based on assessed/predicted radio conditions

Info

Publication number: GB2481715A
Application number: GB1111306.5A
Authority: GB
Inventors: David Andrew Fox; Youssef Chami; Steve Allen; John Mccracken
Original assignee: Vodafone Group PLC
Current assignee: Vodafone Group PLC
Priority date: 2010-07-02
Filing date: 2011-07-04
Publication date: 2012-01-04
Anticipated expiration: 2031-07-04
Also published as: GB201111306D0; GB2481715B; GB201011168D0

Abstract

A mobile telecommunications network includes a plurality of terminals 1200, a core 1218 and a radio access network 1214 having radio means for providing wireless communication resources to the terminals. The radio access network includes control means 700 operable to control the allocation of network resources to said mobile terminals, and wherein the control means is operable to gauge the radio conditions available to said mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon. The control means may build and maintain a record of radio quality across a coverage area of the network (a cell in an embodiment), and may use this record to predict the radio conditions available to the mobile terminals within that coverage area. The control means may calculate the location and/or velocity of the mobile terminal and may control the transmission of data in dependence thereon. In the embodiment the control means uses the record of radio quality across the coverage area and the calculated location and velocity of one of the mobile terminals to estimate the radio conditions available to that mobile terminal at a future location and to thereby control the transmission of data between the radio access network and that mobile terminal. The assessment/prediction of radio conditions may be based on quality, capacity, load etc. In one embodiment available backhaul resources/capacity are taken into account in the assessment. In a further embodiment the control means is operable to trigger initialisation, suspension or termination of applications based on the predicted/measured radio conditions or backhaul capacity. A further embodiment involves optimising the distribution of data, such as video, such that a larger amount of data is transmitted which conditions are detected as good and a minimal amount of data (to maintain a minimum buffer occupancy at the mobile terminal) is transmitted when conditions are detected as poor.

Description

Telecommunication Networks

Field of the Invention

The present invention relates to a mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, and to a method of operating such a mobile telecommunications network.

Background

Recently, a dramatic rise in sales of both smart-phones and laptop data cards has resulted in a substantial increase in the amount of data communications passing through mobile telecommunications networks. This volumetric increase can also be attributed to enhancements made to the capabilities of the networks. In fact it has been reported that mobile data growth grew 30 percent over the course of the second quarter of 2009. The most popular use for mobile data was HTTP browsing, although usage of HTTP streaming is growing considerably. Other mobile data uses include HTTP downloading and Peer-to-Peer (P2P) activities such as file sharing.

This ability to use the cellular networks for mobile data services, such as Internet browsing is resulting in subscribers treating their mobile networks in much the same way as they treat their fixed networks. That is, users are tending to expect the same service from the Internet, irrespective of their access method. However, mobile networks have a more restricted capacity and are more costly to operate, as compared to fixed networks.

In this regard, from the network operator's viewpoint, as the mobile broadband traffic volume carried over 2G, 3G and HSPA (High Speed Packet Access) networks continues to grow, the cost of supporting this data volume is becoming more and more expensive based on the current network architecture and deployments. In fact, access and data volumes are likely to rise faster than the revenue used to build and maintain the networks. This cost differential is exacerbated by one of the current business models being utilised, whereby operators charge a flat rate for unlimited amounts of data.

The increased usage is also unfortunately likely to result in an increase of data traffic jams, and hence a degradation of service for mobile users if not properly managed.

It has been proposed to control data-heavy users by "choking" the bandwidth available to them when a maximum data volume limit is exceeded. Whilst this addresses the problem on an individual level, it does not address the network capacity problem as a whole.

It is therefore apparent that mobile broadband is at a crossroads as networks and business models are strained by bandwidth demand that is unmatched by revenue generation.

These problems will only get worse with moves to position mobile data as a replacement for fixed DSL (Digital Subscriber Line) access and with the advent of higher radio access speeds with the proposed 4G LTE/SAE (Long Term EvolutionlSystem Architecture Evolution) network. A large percentage of this traffic will consist of data which is destined for the public Internet, a significant proportion of which mobile operators will not be able to add value to, despite carrying the data on their own backhaul transport, core transport or cellular core infrastructure.

In addition to the problems discussed above, conventional mobile telephone communications networks have architectures that are hierarchical and expensive to scale. Many of the network elements, such as the BTS, routers, BSC/RNC etc are proprietary: devices of one manufacturer often do not interface with devices from another manufacturer. This makes it difficult to introduce new capabilities into the network as a different interface will be required for devices from each manufacturer. Further, conventional base stations are not capable of intelligent local routing or processing. Furthermore, the capacity of existing networks is not always used effectively. For example, many cell sites are under used, whilst others are heavily used.

The current network architecture has the following disadvantages:- * Hierarchical and expensive to scale 10. Backhaul is a major problem * Proprietary platforms: BTS, BSC/RNC, SGSN etc * Closed nodes and interfaces * Very limited application or customer awareness (except for Q0S priority) 15. No intelligent local routing or processing * Inefficient use of installed capacity There is therefore a need to overcome or ameliorate at least one of the problems of the prior art. In particular there is a need to address the needs of both the network operators and the users in improving the provision of mobile broadband data services.

Summary of the Invention

In one aspect the present invention provides a mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access network includes control means operable to control the allocation of network resources to the mobile terminals, and wherein the control means is operable to gauge the radio conditions available to the mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon.

In the embodiment the radio access network comprises a plurality of cells and the control means controls the transmission of data within a one of the cells in dependence upon the gauged conditions within that cell.

The control means may gauge the radio conditions by assessing the radio conditions available to the mobile terminals. For example, the control means may calculate the load on the cell and/or the quality of the radio conditions at the location of the mobile terminals.

The control means may be operable to gauge the radio conditions by predicting the radio conditions available to said mobile terminals. The control means may build and maintain a record of radio quality across a coverage area of the network (a cell in the embodiment), and may use this record to predict the radio conditions available to the mobile terminals within that coverage area. The record may be in the form of a map of the coverage area, indicating which areas of the coverage area provide which qualities of radio coverage. The control means may calculate the present location and/or velocity of the mobile terminal and may control the transmission of data in dependence thereon. In the embodiment the control means uses the record of radio quality across the coverage area and the calculated present location and velocity of one of the mobile terminals to estimate the radio conditions available to that mobile terminal at a future location and to control the transmission of data between the radio access network and that mobile terminal at the calculated location in dependence thereon. That is, the control means may calculate the present location of the mobile terminal. If the velocity of the mobile terminal is also calculated, this allows the position of the mobile terminal at a time in the future to be estimated. By consulting the record of radio quality across the coverage area, the control means can determine the radio conditions at an estimated future location of the mobile terminal. The control means may increase the amount of data transmitted at the calculated (present) location of the mobile terminal if the radio conditions at the estimated future location predictedto be below a quality threshold. Alternatively or additionally the control means may decrease the amount of data transmitted at that calculated (present) location of the mobile terminal if the radio conditions at the future location are predicted to be above a quality threshold. For example, in the embodiment, if the control means determines that the mobile terminal is moving from a present location in which radio conditions are relatively poor to a future location in which the radio conditions are relatively good, the amount of data transmitted to the mobile terminal at the present location may be reduced, and the amount of data that is transmitted at the future location is increased. Conversely, if the present radio conditions are assessed to be relatively good, and the future radio conditions are predicted to be relatively poor, then additional data may be transmitted to the mobile terminal at the present location, and less or no data may be transmitted at the predicted future location. Advantageously, the mobile terminal includes a buffer or other memory for storing this received data.

According to the embodiment, relatively more data will be transmitted to the buffer when the mobile terminal experiences good radio conditions then when the mobile terminal experience is poor radio conditions. This is advantageous because the transmission of data when the mobile terminal experiences good radio conditions is much more efficient in terms of bandwidth used.

The present invention also provides a telecommunications method as defined in the claims.

In another aspect, there is provided a mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access network includes control means operable to control the allocation of network resources between mobile terminals and between radio access nodes.

This control means may be operable to assess the downlink radio quality, downlink bandwidth efficiency for said mobile terminals and to transmit data to the mobile terminals in dependence thereon This control means may be operable to assess the uplink radio quality, uplink bandwidth efficiency for said mobile terminals and to allocate network resources to the mobile terminals in dependence thereon This control means may be operable to calculate the location of said mobile terminal The calculation of the location is determined through measurements of own and neighbouring cell provided by said mobile terminal.

The calculation of the location is determined through network measurements of transmissions from said mobile terminal.

The control means may be operable to build and maintain a coverage/quality map of radio quality across the coverage area, and to transmit data or allocate network resources to the mobile terminals in dependence thereon.

The control means may measure the change in location to determine the speed and direction of said mobile terminals The control means may be operable to predict future downlink radio quality, and downlink bandwidth efficiency for said mobile terminal and act thereon.

The control means may be operable to predict future uplink radio quality, uplink bandwidth efficiency for said mobile terminals and to allocate network resources to the mobile terminals in dependence thereon.

The predicted future radio conditions are used by the control means to schedule the transmission of data The predicted future radio conditions may be used by the control means to differentially allocate resources to said mobile terminals The predicted future radio conditions may be used by the control means to optimise the scheduling of applications hosted by the control means or by said mobile terminals The predicted future radio conditions may be used by the control means to optimise the network parameters for caching, media optimisation, traffic routing and radio parameters.

The predicted future radio conditions may be used by the control means to trigger optimisations and RRM decisions on other cells hosted by the control means or other control means.

In a further aspect, there is provided a mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access network includes control means operable to control the use of network resources by said mobile terminals, and wherein the control means is operable to predict the current and future radio quality and capacity available to said mobile terminals and to transmit data, initialise applications or terminate applications in dependence thereon.

The control means may be operable to build and maintain a logical map of radio quality across its coverage area, and to transmit data initialise applications or terminate applications to the mobile terminals in dependence thereon.

The control means may determine location of mobile terminals through radio measurement.

The control means may determine speed of mobile terminals through changes in radio measurements.

The radio measurements may include received signal strength, transmit power levels, neighbour cell measurements.

The control means may modify the radio measurement control parameters to give greater resolution to frequency of measurement.

The control means may controls the flow of packets for specific applications.

The control means may control the resource allocated by the control means to each mobile terminal. The resources include the memory resources, Call Admission Control parameters, Cell load/congestion parameters.

The control means may measure the speed and direction of said mobile terminals, and uses this in conjunction with future radio link quality measurements.

The radio link quality measurements may include CQI, ACK/NACK ratios, BLER, Frame Errors Rates, BERs, Qqual, RSSI, RSCP. . .etc.

The flow of data to said mobile terminal may be controlled dependent on knowledge of: -mobile terminal buffer occupancy, -Basestation Downlink Buffer Occupancy, and/or -Video playback rate and session duration and volume of data transmitted by the session.

The control means may initiate or terminate an application hosted by or controlled by the control means based on the prediction of the future radio environment.

In another aspect, the present invention provides a mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access network includes control means operable to control the allocation of network resources to said mobile terminals, and wherein the control means is operable to gauge the radio conditions and backhaul (between the radio access network and the core) available to said mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon.

The control means may be operable to gauge the radio conditions by assessing the radio conditions and backhaul resources available to said mobile terminals.

The control means may be operable to gauge the radio conditions by predicting the backhaul capacity available to said mobile terminals.

The control means may be operable to build and maintain a record of backhaul capacity for a cell or radio site, and to use this record to predict the backhaul capacity available to said mobile terminals.

The control means may be operable to trigger initialisation, suspension or termination of applications based on the radio conditions or backhaul capacity measured or predicted.

The control means may be operable to control transmission of the data based on the current and predicted mobile location.

The present invention also provides a method of operating a mobile telecommunications network as defined in the claims.

Brief Description of the Drawings

An embodiment of the present invention will now be described in more detail with reference to the accompanying Figures in which: Figure 1 illustrates a high level packet data network architecture, useful for explaining the prior art and embodiments of the present invention; Figure 2 illustrates the introduction of a new functional "platform" in a 3G network; Figure 3 illustrates a flow chart of an example offload decision process as implemented in the 3G network of Figure 2 Figure 4 illustrates a flow chart of an example offload decision making process that may be implemented by a redirection module Figure 5 shows the novel "platform" in more detail provided in the Radio Access Network in accordance with an embodiment of the invention; Figure 6 shows possible locations of the platform within a mobile telecommunications network; Figure 7 is a flow chart showing the steps performed when a mobile terminal is activated; Figure 8 shows the optimisation of content delivery to a mobile terminal; Figure 9 shows a further optimisation of content delivery to a mobile terminal; Figure 10 is a flow chart showing the procedures performed when a mobile terminal moves within the network; Figure 11 shows the transfer of information between platforms; Figure 12 shows schematically the elements according to an embodiment of the invention, including a mobile device having an access control client and a data managing server; Figure 13 shows an enhanced architecture in accordance with an embodiment of the invention; Figure 14 shows a flowchart of data collection operations to generate a radio conditions map of a cell in accordance with the embodiment; and Figures iSA and 15B are a flowchart showing a process for providing improved delivery of data between mobile terminals and the radio access network in accordance with the embodiment.

In the drawings like elements are generally designated by the same reference numerals.

Detailed Description

Key elements of a 3G mobile telecommunications network, and its operation, will now briefly be described with reference to Figure 1.

Each base station (e.g. Node B 1 and Femto 2) corresponds to a respective cell of the cellular or mobile telecommunications network and receives calls from and transmits calls to a mobile terminal (not shown) in that cell by wireless radio communication in one or both of the circuit switched or packet switched domains. The mobile terminal may be any portable telecommunications device, including a handheld mobile telephone, a personal digital assistant (PDA) or a laptop computer equipped with a network access datacard.

The nodeB 1 or Femto 2 can be considered to comprise two main parts: a radio frequency part and a baseband part. The radio frequency part handles the transmission of radio frequency signals between the antenna of the nodeB 1 or Femto 2 and the mobile terminal, and for converting radio frequency signals into digital baseband signals (and vice versa). The baseband part is responsible for controlling and managing the transmission of the baseband signals to other components of the mobile telecommunications network.

In a macro 3G network, the Radio Access Network (RAN) comprises Node Bs and Radio Network Controllers (RNCs). The Node B is the function within the 3G network that provides the physical and transport radio link between the mobile terminal (User Equipment, UE) and the network. The Node B performs the transmission and reception of data wirelessly across the radio interface, and also applies the codes that are necessary to describe channels in a CDMA system. The RNC is responsible for control the Node Bs that are connected to it. The RNC performs Radio Resource Management (RRM), some of the mobility management functions and is the point where encryption is done before user data is sent to and from a mobile terminal. The RNC connects to the Circuit Switched Core Network through a Media Gateway (MGW) and to an SGSN (Serving GPRS Support Node) 5 in the Packet Switched Core Network. In Figure 1, Node B 1 is controlled by RNC 3 across the Tub interface. An RNC may control more than one node B. Figure 1 also illustrates a Femto 3G RAN, with Femto 2 operating as the base station. Femto 2 is connected to an Access Gateway (AGW) (a.k.a Concentrator) 4 via an Iuh interface. Femto is an abbreviation of "femto-cells", and many other different names have been used, including home access points (HAPs), access points (APs) and femto-base stations, but all names refer to the same apparatus.

The radio link between the Femto 2 and the mobile terminal uses the same cellular telecommunication transport protocols as Node B 1 but with a smaller range -for example 25m. The Femto 2 appears to the mobile terminal as a conventional base station, so no modification to the mobile terminal is required for it to operate with the Femto 2. The Femto 2 performs a role corresponding to that of Node B 1 in the macro 3G RAN.

The Femto 2 would typically be configured to serve a Wireless Local Area Network (WLAN) located in a home or office, in addition to GSM/UMTS/LTE networks. The WLAN could belong to the subscriber of the mobile terminal, or be an independently operated WLAN. The owner of Femto 2 can prescribe whether it is open or closed, whereby an open AP is able to carry communications from any mobile device in the GSM/UMTS/LTE network, and a closed AP is only able to carry communications from specific pre-assigned mobile devices.

Conventionally, in a 3G network (macro or Femto), the RANs are controlled by a mobile switching centre (MSC) and an SGSN (Serving GPRS Support Node) of the core network. The MSC supports communications in the circuit switched domain, whilst the SGSN 5 supports communications in the packet switched domain -such as GPRS data transmissions. The SGSN is responsible for the delivery of data packets from and to the mobile terminals within its geographical service area. It performs packet routing and transfer, mobility management (attach/detach and location management), logical link management, and authentication and charging functions. A location register of the SGSN stores location information (e.g., current cell, current VLR) and user profiles (e.g., IMSI, address(es) used in the packet data network) of all mobile terminals registered with this SGSN. In Figure 1, since the embodiment is concerned with data transmission, only the SGSN is illustrated as being in communication with RNC 3 and AGW 4, across the lu interface. The RNC 3 typically has a dedicated (not shared) connection to its SGSN 5, such as a cable connection.

Communications between the AGW 4 and the SGSN 5 are preferably IP based communications, and may be, for example, transmitted over a broadband IP network. Further, the connection between the Femto and the AGW 4 may use the PSTN (Public Switched Telephone Network). Typically a DSL cable connects the AGW to the PSTN, and data is transmitted there-between by IP transport/DSL transport. The Femto or AGW converts the cellular telecommunications transport protocols used between the mobile terminal and the Femto 2 to the appropriate IP based signalling.

The femto 2 may be connected to the AGW by means other than a DSL cable and the PSTN network. For example, the femto 2 may be connected to the AGW by a dedicated cable connection that is independent of the PSTN, or by a satellite connection.

The SGSN 5 is in communication with the GGSN 6 (Gateway GPRS Support Node) across the Gn interface. The GGSN is responsible for the interworking between the GPRS network and external packet switched networks, e.g. the Internet. The GGSN enables the mobility of mobile terminals in the networks.

It maintains routing necessary to tunnel the Protocol Data Units (PDUs) to the SGSN that service a particular mobile terminal. The GGSN converts the GPRS packets coming from the SGSN into the appropriate packet data protocol (PDP) format (e.g., IP or X.25) and sends them out on the corresponding packet data network. In the other direction, PDP addresses of incoming data packets are converted to the mobile network address of the destination user. The readdressed packets are sent to the responsible SGSN. For this purpose, the GGSN stores the current SGSN address of the user and their profile in its location register. The GGSN is responsible for IP address assignment and is the default router for the connected mobile terminal. The GGSN also performs authentication and charging functions. Other functions include IP Pool management and address mapping, Q0S and PDP context enforcement.

In turn the GGSN 6 may route data via any applicable Value Added Service (VAS) equipment 7, before data is forwarded towards its intended destination via the Internet 8. As an example of the functionality of the VAS equipment, the traffic may be inspected for adult content before reaching the end-user if this user is under 18 years of age.

For billing purposes in particular, a PCRF (Policy and Charging Rules Function) apparatus 9 is also provided, in communication with both the SGSN and the GGSN 6.

The SGSN 5, GGSN 6, VAS 7 and PCRF apparatus 9 comprise the core network of the mobile telecommunications network.

Mobile telecommunications networks have an active state of communication with their mobile terminals and an inactive/idle state of communication with their terminals. When in the active state, as the mobile terminals move between different cells of the network, the communication session is maintained by performing a "handover" operation between the cells. In the inactive/idle state, as a mobile terminal moves between different cells of the network the mobile terminal performs "cell reselection" to select the most appropriate cell on which to "camp" in order that the mobile terminal can be paged by the network when mobile terminating data is destined for that mobile terminal.

Conventionally, the mobile terminal or network determines whether a handover/cell reselection procedure should be triggered in dependence upon measurements of the radio signals of the cells in the region of the mobile terminal. A filter is applied to the signals (either by the network or by the mobile terminal) which calculates an average (e.g. arithmetical mean) value of these signals over a particular time period. This filtered/average values of the cells are then compared with each other or with a threshold value. In dependence upon these comparisons, cell reselectionlhandover related procedures are triggered. This cell reselection/handover process generally comprises taking radio signal measurements of neighbouring cells and comparing these to each other and to the radio signal of the current cell to determine which cell provides the best signal strengthlquality.

Handover/reselection to the best cell can then occur.

Generally calculations to determine whether to perform a handover from one base station to another base station are performed by the network, whereas calculations whether to perform cell reselection are performed by the mobile terminal.

Data in a mobile telecommunications network can be considered to be separated into "control plane" and "user plane ". The control plane performs the required signalling, and includes the relevant application protocol and signalling bearer, for transporting the application protocol messages. Among other things, the application protocol is used for setting up the radio access bearer and the radio network layer. The user plane transmits data traffic and includes data streams and data bearers for the data streams. The data streams are characterised by one or more frame protocols specific for a particular interface. Generally speaking, the user plane carries data for use by a receiving terminal -such as data that allow a voice or picture to be reproduced -and the control plane controls how data are transmitted.

In addition to the elements and functions described above, mobile telecommunications networks also include facilities for transmitting SMS messages. SMS messages are transmitted over the control plane only (and not the user plane).

This architecture is what currently is being used to carry all packet data to and from mobile terminals. That is, in today's implementation of the Packet data architecture, user plane traffic traverses across all the network elements shown between the Node B or Femto on which the user is camped and the internet.

That is, all data is directed from the applicable RAN through the core network components SGSN, GGSN and VAS before reaching the internet. All PS traffic accordingly follows the same path and therefore has the same network costs.

All applications are processed on the client (on the mobile device) or on the server (which is connected to the internet), and the network core therefore acts like a bit-pipe in the current architecture. For data, where the mobile network operator cannot add any value by carrying it on its own backhaul transport, core transport or cellular core infrastructure (the core network), such as data destined for the public internet without required intervention from the core network, there is no benefit to routing this data via the core network.

However, a large percentage of this traffic can be handled in a more intelligent manner for example through content optimisation (Video & Web), content caching, or locally routed or directly routing content to the public Internet. All these techniques reduce the investment required by a mobile operator to carry the data on its own backhaul and core transport or cellular core infrastructure.

In order to offer low cost packet data, to support new services and to manage customer expectation, a step-change reduction in the end-to-end cost per bit is required.

Mobile operators want to reduce their packet data handling costs through alternate network architectures based on commoditised IT platforms, breaking away from the traditional architecture based on their voice legacy. These new network architectures overcome the Access architecture issues of today In order to successfully offer cheap packet data and be able to compete with the fixed broadband offers (flat fee) a solution is proposed which focuses on the reduction of the end-to-end cost per bit, especially for Internet access service.

This enables mobile operators to reduce packet data handling costs by means of an alternative network cost model architecture, which breaks out of the traditional network architecture and nodes and utilises lower cost transport networks to optimise the data flow.

In this regard, Figure 2 shows a high level description of the architecture that may be adopted to deploy this on a 3G network.

According to this arrangement, novel "platforms" 24, 25, 26 for performing functions such as caching, routing, optimisation and offload/return decision functionality are integrated into the network. This decision functionality may be incorporated in the radio architecture. In this regard, the platforms 24, 25, 26 may be incorporated into the NodeBs 1 (25), RNCs 3 (26) or exist as separate physical entities (24). It is these platforms 24, 25, 26 that, for example, determine the path of communications originating from the mobile terminals.

The exact placement of the platform 24, 25, 26 is not essential, and, for a macro 3G network, it can be placed at or between the Node Bs and the RNCs, and also between the RNCs and the SGSNs (or any combination thereof). It would also be possible to place the platform 24, 25, 26 at the GGSN (although not the SGSN as this does not control user data, only control data).

In the 3G Macro network, the aim is to offload a high percentage of the macro network traffic from the core and transport (IuPS, Gn, etc) by diverting specific traffic type for certain user(s) class directly to the Internet.

Where the platform 24, 25 is located in the Node Bs (or on the lub interface), it may be possible to redirect the data from all the remaining mobile network elements (e.g. the RNC, SGSN, GGSN and VAS for macro 3G), and sending the data directly to the Internet 8. In a similar manner, where the platform 26 is located at the RNC (or on the lu interface), it becomes possible to redirect the data from the SGSN 5, GGSN 6 and the VAS 7. The alternative data route is preferably a DSL using ADSL.

It is also preferable to aggregate the alternative data routes for each cell, where applicable. In this regard, each cell will have at least one RNC 3 and a plurality of Node Bs, so where the decision blocks are situated at or in the vicinity of the Node Bs, for instance, there will be a plurality of links which should ideally be aggregated before being passed to the Internet 8. At the point of this aggregation 42, there is preferably a further decision block which enables data to be returned to the legacy route. For instance, a new policy rule may have been implemented, which requires or enables previously offloaded data to be returned to the core network route. This new policy rule may be communicated to the return decision module by the core network policy module. In Figure 2, this returning of data is only shown to the VAS 7, but the data may be returned to one or more of the other core network elements.

Each of the NodeBs 1 is connected to the mobile network core through a Point of Concentration (P0C) 27. All traffic from the NodeBs 1 which is to be routed through the core mobile network is routed to the PoC 27. This includes both user plane and control plane data. On the control plane level, the PoC 27 routes data to and from the SGSN 5 and the GGSN 6. Control data is also sent to and from other core network components, including the Lawful Interception Database (LI DB) 30, DNS Server 32, Policy Server 9 (including Charging rules and IT Network 9A) and Home Location Register/Home Subscriber Server (HLR/HSS) 36 (which contains subscriber and device profile and state information).

User plane data is transmitted by the PoC 27 to the SGSN 5 and the GGSN 6.

From the GGSN 6, data is routed across a VAS 7 node to the Internet 8. In 3G this is the standard data path from the mobile terminals to the Internet.

To implement an advantageous feature, an alternative path on which to re-route certain data to the internet 8 is provided, whereby, each NodeB 1 and Femto 2 may be connected to a fixed line connection 40 (e.g xDSL) which is directly connected to the internet 8. These xDSL connections may be made directly to the NodeB and/or Fernto or made to the NodeB/Femto via other components, such as the PoC 27. In figure 2, the xDSL Network 40 may be a third party network or may be a network owned or controlled by the owner of the mobile telecommunications network. By using such an alternative path, radio capacity, backhaul transport resource, core transport resource, cellular core network resources can be saved as well as improving performance and enhancing revenue for the mobile network operator.

As each Node B 1 and/or PoC 27 is associated with a platform 24, 25, 26, for each data packet request originating from a mobile terminal, a decision at the platform 24, 25, 26 is made as to whether the traffic may bypass the core mobile network entirely or may be passed into the core mobile network. The location at which the traffic is routed towards the internet is preferably at the platform 24, 25, 26; however, it may alternatively be routed out from the core network towards the internet at a different component. Traffic offloaded from the macro network is routed by the platform 26 to the xDSL network 40 by link 44 (the decision to offload this traffic may have been made at platform 24, 25 or 26 -although the decision is implemented at platform 26) Preferably the Offload/Return decision is dependent upon the type of data or user. To exemplify this feature of the embodiment, Figure 3 is a flow diagram showing the steps taken when deciding how to route the traffic in the architecture of figure 2. For instance, consider an NodeB receives a request to set up a data call from a user device which is camped on the NodeB at 300.

Once the NodeB has identified the request as a data call and the type of traffic/user, rather than automatically routing the data traffic to the core network, the data request is held at the NodeB at 310 until a decision has been made as to how to route the data, in particular whether to offload the traffic directly to the internet or whether to return the data through the core mobile network. Typically, the signalling (control plane) for the connection will continue through the normal route but the user data traffic will be held at the NodeB, this is possible by virtue of the separate user and control planes, as shown in figure 2.

The decision as to whether or not to use the Core mobile Network to route the data traffic can be based on various aspects, particularly relating to the properties of the data being routed and/or status of the user routing the data.

The Mobile Network may add value to traffic by providing a number of services, such as compressing the user data to speed-up the data transfer while downloading (if this functionality is not already supported by the platforms 24, 25, 26). These different services can be broken up into groups and provided by different entities (e.g. this enables greater flexibility in the provision of the services, such as the mandated Internet Watch Foundation -IWF -requirement, which can only be supported by the mobile operator). The platforms 24, 25, 26 therefore make a decision on whether to service the data locally through caching, fetch the data from other node or from the internet via offload functionally or whether to route the traffic through the core network, based on the applicability of one or more of the services to the traffic. That is, platform 24, 25, 26 decides when data traffic requires one or more of the services and when it can do without them.

It should also be noted that these services are ones that could be provided without using the core network. These are services that add value to the customer, and which subscribers will pay for (explicitly or implicitly).

Referring again to Figure 3, the platform 24, 25, 26 decides at 320 what to do with the traffic (from coming for the networkl internet or orientated by the device). This decision may be made by interrogating certain servers or databases stored centrally within the core network which can compare the type of service, type of user etc with criteria which identifies the type of action shall be considered, e.g whether the traffic is suitable for offloading directly to the internet (at 330) from the NodeB or whether the traffic should be routed through the core (at 340). Examples of some of the considerations used in influencing the decision of whether to offload the traffic are discussed below in more detail. The implementation of this data offload technique needs to be carefully considered, as it places additional constraints on the network design.

The following is a non-exhaustive list of examples of challenges that have to be considered when implementing the data offload technique: a) maintaining Customer Services provided by the core network or otherwise; b) maintaining Network Services (e.g. Charging Rate Limiting/application control); and c) maintaining Regulatory Services (e.g. to enable Lawful Interception and Regulatory Content Filtering).

Some specific examples of Customer Services that can be taken into account by the offload decision module include: i) Parental Control: A service which customers subscribe to that filters content in order to shield children from unwanted websites and programs.

Whether traffic from a given user needs to be filtered can be determined by a Common User Repository (CUR) lookup, where the CUR stores user profile information, such as whether the user is an adult or a child etc. If traffic needs to be filtered, then either the traffic cannot be offloaded or it needs to be filtered somewhere other than the core network.

ii) Traffic Optimisation: Optimisation is only required for low bandwidth connections (2G). By looking at the Radio Access Type (RAT) and the International Mobile Equipment Identity (IMEI) it can be determined whether or not a subscriber needs these services. Where traffic optimisation is not required, the traffic can be offloaded iii) Marketing Proposition: The mobile network is typically setup to provide full mobility with acceptable Quality of Service (QoS). A further option could be to offer best effort QoS without guaranteed full mobility. As an example, for when a heavy user has exceeded their fair usage limit, their traffic could be designated as low priority traffic and offloaded.

The Network Services that can be taken into account by the offload decision module are typically those that the network operator needs to manage its network. Some examples include: i) Charging: The charging plan that a user subscribes to can be used to determine whether or not to offload that user's data. For instance, it is most easily avoided when the customer has a flat rate plan. That is, users on flat rate plans do not need their usage tracked for charging purposes in real time and so can be offloaded onto the alternative route. For users who are roaming or whose charging plan depends upon usage, then, the operator/supplier needs to track their total usage in real-time, and so their data needs to be maintained on the core network route so that rate-limits and data usage can be accurately tracked and alarms/alerts activated when usage exceeds allowances. This is because, if this is not avoidable then Call Data Records (CDRs) need to be generated by the module for the real time charging.

ii) Rate-limiting/application control: This is currently used to manage the traffic flow according to a certain usage policy. Excessive bandwidth usage or controlling P2P applications are common reasons to rate limit users.

Therefore, where a user transmitting data is determined to be under a rate restriction (i.e. throttling) or the data they are transmitting has an application restriction (i.e. the application is blocked), then that data can be offloaded. This exceeded allowance information would typically be communicated to the decision module (24, 25, 26) by the HLRIHSS. This traffic management enables the total traffic volume to be reduced and is typically fully managed by the network operator.

iii) Q0S: The network uses QoS to manage traffic during high load situations and to support marketing propositions. To enable QoS considerations to be enforced by the offload decision module, a connection is established between the offload module and the Policy and Charging Rules Function (PCRF) entity. This enables decision criteria to be dynamically fed to the offload module, for instance to maintain high priority users on the core network path and/or high priority application types, such as VoIP. It is to be appreciated that the connection to the PCRF is not essential, and alternatively, static or semi-static rules, pre-stored with the offload module, can be considered.

iv) Mobility: Mobility, such as cell handover, is an issue that needs to be managed by the core network. Therefore, terminals that are in motion should not be offloaded. The mobility of a mobile terminal could be determined by querying the Node B. Some users could be provided with a contract that allows only fixed or limited mobility use, so that the service provided was equivalent to a fixed broadband package. Different charging tariffs could be applied depending on whether a user was at a fixed location or mobile. Two ways the offload decision module can handle a mobile terminal's mobility are as follows: 1. The offload decision module can have the capability to characterise the radio link between the device and the network by monitoring the number of handovers implemented for the mobile terminal. If a certain number of handovers occur over a fixed duration, the mobile terminal can be classified as in motion, and any data from the mobile terminal can thereafter be routed back into the core network to avoid any further packet data delay. This of course assumes that the mobile terminal had been designated for data offload on the bypass link.

2. The offload decision module is situated on the IuPS for the 3G network (i.e. between the RNC and the SGSN) or Si for the LTE (i.e. between the eNode B and the PoC), and checks the lur or X2 signalling information (i.e. between a set of RINCs controlled by a given 3G SGSN and between a corresponding set of eNode Bs for LTE). If this monitoring shows that a mobile terminal is hopping between cells one of which is not connected to (and therefore managed by) the offload decision module, any data from the mobile terminal can thereafter be routed back to the legacy path through the core network.

Regulatory Services are services that are mandated by legislation, and are typically provided to all traffic. Some specific examples of Regulatory Services that can be taken into consideration by the offload decision module include: i) Lawful Interception (LI): The ability to provide Lawful interception will be maintained in any offload or local breakout plans. The options for offload are: -Maintain the evaluation of LI in the core network, and not offload users whose traffic needs to be intercepted (e.g. where the user has been tagged by the police for communication interception). Since the LI functionality is handled by the core network, the core network accordingly cannot be bypassed; -Add LI capability to the offload decision module, which will require a local LI interface with a dedicated database identifying the users to be intercepted. With this option, upon identifying traffic from a user on the list, a copy of the data can be made at the local LI interface and the traffic offloaded. The copied data can then be reported to the appropriate authorities; or -Alternatively, LI may be performed at the Internet Service Provider (ISP). With this option, since LI is considered at the ISP it is not a consideration at the offload decision engine, and so the data may be offloaded, where possible. However, to effect this option, a Service Level Agreement (SLA) with relevant ISP providers may need to be amended in order to include the support of LI in the ISP network rather than in the mobile network infrastructure.

ii) Regulatory Content Filtering (e.g. for Internet Watch Foundation (IWF)): This required functionality blocks illegal websites. This functionality could easily be added to the offload decision module as it is not processor intensive. An http proxy server, for instance, could be used to support this functionality. Otherwise, the traffic will be returned back to a dedicated core node(s).

A further criterion that the platform (24, 25, 26) module may consider is the priority of the customer. In this regard, a network operator may wish to prioritise traffic across its network based on the priority level of the customer.

For example, a high value customer (e.g. a corporate customer or a subscriber with on a high tariff contract) may be given priority over a low value customer.

In this situation, a network may decide to offload lower value customers directly to the internet. This is related to the QoS criterion mentioned above, although the QoS criterion is generally linked to traffic management to maintain a balanced network, whereas the priority referred to can be used to ensure subscribers get a level of service commensurate with their service agreement.

The embodiment of Figure 2 is in relation to a 3G network. Embodiments of the invention are equally applicable to 4G (LTE/SAE) networks.

The LTE/SAE macro network includes eNode Bs which make up the RAN.

The eNode Bs effectively combine the functionality of the node B and the RNC of the 3G network. These eNodeBs are the network components which communicate with the mobile communication devices. It is envisaged that the eNodeBs will be arranged in groups and each group controlled by a Mobility Management Entity (MME) and a User Plane Entity (UPE).

The MME performs many of the mobility functions traditionally provided by the SGSN. The MME terminates the control plane with the mobile device. It is responsible for terminating NAS (Non Access Stratum) Signalling such as MM (Mobility Management) and SM (Session Management) information as well as coordinating Idle Mode procedures. Other responsibilities of the MME include gateway selection inter MME Mobility and authentication of the mobile device.

The UPE manages protocols on the user plane such as, storing mobile terminal contexts, terminating the Idle Mode on the user plane, and PDP context encryption.

The platforms would operate in the same manner as described in relation to the 3G network. The platforms may be located at many different locations in the 4G network.

A more specific example of how the platform 24, 25, 26 may be implemented is described in relation to Figure 4. Figure 4 is a flow diagram illustrating a preferred method for deciding whether to offload data traffic to the internet.

The decision structure is composed in a hierarchical form in order that certain types of user or data are always directed through the core network. The example of figure 4 is described for a 3G network but it will be clear to those skilled in the art that these decisions could be applied to any type of radio access technology.

Once a PS HSPA data call (or other connection) is made and received at the Node B at 600, a primary consideration by the platform 24, 25, 26 at 610 is whether the device is operating on its home network or whether it is roaming. If the device is roaming then all traffic is automatically routed through the core network. The reason for this is that the home network would want to guarantee the security and accurate billing (due to different charging principle between home and visited operator) of the user's traffic. The platform 24, 25, 26 at 610 will also consider other factors, such as what application types running on the mobile terminal require connections. If the mobile device is operating on its home network at 610, or if the applications do not require a connection to the core network, the platform 24, 25, 26 considers secondary offloading criteria at 620. Examples of secondary criteria may include the functions required by the device, the radio bearer currently used by the device, the APN, or the priority level of the customer identified, for example, through IMSI, IMEI or the target subscriber. If the offloading criteria are met at 620, the decision moves to the tertiary criteria, otherwise, the traffic is not offloaded.

At 630, the system checks the mobility of the user. If the user is moving, he is considered not suitable for offload due to an expected interruption delay of the user data when moving between source and target cell.

Finally, at 640 the system conducts a contents and policy check to confirm whether the user is suitable for offload. If it is determined that the user is suitable for offload to the internet, the eNodeB offloads the traffic to the internet at 650. If it is determined that the user is not suitable for offloading to the internet at 640 then the procedure returns "home" at 660. A connection is provided by a network core in a conventional way and the tests of the flowchart shown in figure 4 are repeated periodically to determine whether offloading directly to the internet becomes possible subsequently.

If the device is determined to be roaming at step 610, then the device is not offloaded directly to the internet, but remains connected via the network core in a conventional way at 670. Similarly, if the offloading criteria are not met at steps 620, the mobile device remains communicating via the network core in the conventional way, again at 670.

The hierarchical decision method is useful because it reduces the number of challenges across the network. It will be evident to those skilled in the art that different hierarchical structures will be appropriate for different networks, different conditions etc and that the example of figure 4 is just one way the decision could be made.

For instance, whilst arrangements have chiefly been described in relation to transmitting data traffic from a mobile terminal to a data network, the principles may also be applied to transmissions from a data network towards a mobile terminal.

In the arrangements described above the decision regarding the route is said to be made at call set-up. However, it should be appreciated that a decision to change the routing of data may be made at the beginning of a communication session (for example establishment of a PDP context), or during a communication session. The routing of data may change several times during a single communication session. For example, when a communication session is initiated it may be detected that the user is not moving, in which case a decision will be made to offload the data over the alternative data route. Subsequently it may be detected that the user is moving, and at this point a decision may be made to beginning routing data for the communication session via the mobile network. During the communication session, the mobile terminal may become stationary for a prolonged period of time again, and at this time a further decision may be made to send subsequent data during the communication session via the alternative data route. Subsequently again, the user may then attempt to access age-restricted content, and it will be detected that parental control is required. In response for the requirement for parental control, a decision may be made to redirect subsequent data during the Communication session via the core network so that core network parental controls can be applied.

It is to be appreciated that the present embodiments of the invention are to be distinguished from HSDPA offload, a technique used on the lub interface between the Node B and the RINC. HSDPA offload which serves to separate data traffic from voice traffic, so that non-real time data traffic is sent down a less expensive backhaul to complement or replace the expensive El/Ti TDM backhaul link between the two. Once this diverted traffic reaches the RNC, however, it is returned to the cellular and transport core networks and there is no differentiation made based upon data traffic type.

In the arrangement described above the platform 24, 25, 26 primarily handles data offload decisions. As will be described below, the platform can perform may other functions.

Embodiments of the invention in which the Radio Access Network controls the use of resources by mobile terminals will now be described.

Platform Architecture As discussed above, a mobile telecommunication network is modified by the introduction of a "platform" 24,25,26. Such a platform is shown in more detail at 700 figure 5 and which includes three principal parts: soft nodes 702 (physical/transport layer), network functions 704 and services 706 (application layer).

The platform 700 communicates with the radio frequency (RF) part of a base station, such as a NodeB 1. The soft nodes 702 of the platform 700 comprise components such as a soft NodeB 708, soft BTS 710, soft eNodeB 711 and soft RNC 712 and soft SGSN/GGSN 714. The soft nodeB 708 provides functions equivalent to the baseband part of a conventional NodeB in a 3G telecommunications network. The soft BTS 710 provides baseband functions equivalent to the baseband functions of a BTS in a conventional 2G mobile telecommunications network. The soft enodeB 711 provides baseband functions equivalent to the baseband functions provided by a conventional enodeB in a 4G mobile telecommunications network. The platform 700 may therefore communicate with the radio frequency part of a 2G, 3G or 4G base station and provide appropriate baseband services for 2G, 3G or 4G technologies (or indeed for other technologies). A 3G mobile terminal that wishes to obtain telecommunication services from the mobile telecommunications networks connects wirelessly to the radio frequency part of a NodeB. Baseband functions may be provided either by a baseband part of the conventional NodeB or by the soft NodeB 708 forming an element of the soft node part of the platform 700. For example, the soft NodeB 708 may receive radio measurements from the radio frequency part of the NodeB to which it is connected, and may provide these radio measurements to other elements of the platform 700.

The network functions part 704 of the platform 700 includes modules for performing functions similar to those performed by the core network of a mobile telecommunications network, such as billing 720, location tracking 722 and the radio resource management (RRM) 724. The network functions may further comprise an offload decision module 726 that performs a function similar to the offload decision modules 24, 25 and 26 described above. The network functions part 704 may further comprise a caching function 728 and Content Delivery Network function 730.

The network functions parts 704 of the platform 700 provides an Application Programming Interface (API) framework to the services part 706 of the platform 700. The services part 706 of the platform supports a plurality of applications 740, 742 etc. The network functions fall into three main categories, those that enable the network operation (e.g. charging, O&M), those that support service operation (e.g. Location) and those that optimise the usage of the network by certain applications and services (e.g. Caching, Video Optimisation).

The applications supported on the Platform 700 are the entities that supply or demand the flow of data on the network, akin to a server on the internet, e.g. gaming server, navigation server.

The API is implemented by a software program running on the network function part 704 which presents a novel standardised interface for the applications 740, 742 etc of the services part 706. The novel standardised API provides a consistent interface, defining communication protocols, ports etc. Full details of the API may be published to allow a multiplicity of applications to be developed for the platform 700 by multiple developers. This should be contrasted with prior art arrangements where each component of a mobile telecommunications network (such as BTS, BSC/RNC, SGSN etc) is proprietary and tends to have a unique interface, meaning that a different application must be written for each node of a conventional network.

The applications 740, 742 etc may provide services to users of the telecommunications network by co-operating with other parts of the platform 700.

The details of the use of each application used by the a user of the mobile telecommunications network is stored in an application context! container. The Application context contains application names, protocol used to carry such application, their characteristics that are measured! reported over period of time and some statistical information about these applications (volume, number of users using these applications, etc.).

As shown in figure 6, a platform 700 may be provided at each base station of the mobile network (where it is connected to the radio frequency part of the base station -NodeB 1 in figure 2), forming an access node 800. Platform 700 may also be provided at the RINC (item 3 in figure 2) where it forms a gateway 802. The access node 800 and the gateway 802 are both configured to communicate directly with the network core 804 (for example, comprising the SGSN 5, GGSN 6 and VAS 7 (as shown in figure 4)). The access node 800 and gateway 802 may also be connected to the internet 8 for direct internet access via direct links 806 and 808, respectively, such that at least a portion of the core network 804 is bypassed in the manner described above.

The following are examples of access technologies that can be provided within the access node 700: 3GPP: GSM/GPRS, UMTS/HSPA & LTE IEEE: 802.11 family & 802.16 family ITU: DSL, ADSL, VDSL, VDSL2 Allocation of Functions to Platforms The steps performed when a mobile terminal is activated at a NodeB, at the Femto or at the Access Point (AP) of the network which includes the novel platform 700 will now be described with reference to figure 7. At step 9A the mobile terminal (UE) is activated within the coverage area of a particular NodeB, at the Femto or at the AP. The access part of the NodeB, at the Femto or at the AP communicates information from the mobile terminal to the platform 700 associated with the NodeB, at the Femto or at the AP. At step 9B the platform 700 then allocates the baseband NodeB, at the Femto or at the AP function and the RNC or BRAS (Broadband Remote Access Server) function either at access node 800 at the NodeB at the Femto or at the AP site or at the gateway 802 at the RNC or BRAS site of the network or even from neighbouring nodes that have spare resources to pull. The decision as to whether the RNC or BRAS function is allocated at the platform 700 of access node 800 or the gateway node 802 may be made depending on various criteria, including: * The device type -for example this decision can be based on the radio access capabilities that the mobile terminal indicates upon activation, such as whether it is operating in the circuit switched or packet switched domains.

* The location of the mobile terminal. If the mobile terminal is near the edge of the cell (which can be determined by network power measurements or neighbour cell measurements from the mobile terminal, within a plus or minus 3dB range for the RACH).

* The establishment cause of the connection request: such that the NodeB can filter the unnecessary signalling information from the mobile terminal which is not critical -for example periodic routing area update messages.

Upon allocating the baseband NodeB at the Femto or at the AP and the RNC or BRAS function, the NodeB at the Femto or at the AP may allocate the mobile terminal to a particular carrier dedicated to the RNC or BRAS function.

Once the RNC or BRAS function is allocated to either the access node 800 or the gateway 802 at step 9C, other functions performed by the platform 700 at the access node 800 (or other access node) and the gateway 802 (or other gateway) are allocated to the mobile device. All other platform functions may be provided by the platform where the RNC or BRAS function is allocated to the mobile terminal. However, a platform at a different location to that which provides the RNC or BRAS function to the mobile terminal may provide some or all other functions.

At step 9D the platform which is allocated the RNC or BRAS function is provided with a Common ID message from the core network 804.

At step 9E, this message is used by the platform 700 to look up the complete subscription information for the mobile terminal, as well as the resource requirements (QoS) of the services required and negotiated PDP context, this information being provided by the core network 804.

The subscription information relating to the device that is obtained from the central nodes (e.g, core network) 804 is used to allocate the other functions at access node 800 and/or the gateway 802 in dependence upon various factors, including: Detailed information regarding the mobile terminal type obtained from the core network.

The subscription characteristics of the mobile terminal.

The applications previously used most frequently by the mobile terminal.

The characteristics of the applications previously used by the mobile device and the performance requirements thereof The historic mobility of the mobile terminal (speed, connection, distance travelled etc).

The location of the mobile terminal and the likely destination of traffic from the mobile terminal based on historic usage patterns.

The load of the NodeB providing RF services to the mobile terminal, and the historic traffic trends at that NodeB at Femto or at AP.

The characteristics of the NodeB at the Femto or at the AP providing RF services (for example, the location, what other devices are connected through the NodeB at the Femto or at the AP, the number of machine to machine devices being attached and served by the NodeB, etc).

As mentioned above, a single mobile terminal may have platform functions/applications allocated on a plurality of platforms. Generally, when a mobile terminal is near-stationary it is most efficient for its functions/applications to be served from an access node 800 (i.e. distributed), whereas mobile terminals with greater mobility (or lower anticipated cell hold times) will be most efficiently served by having fewer or no functions/applications served from the access Node 800, and more or all functions/applications served from a gateway 802 (i.e. centralised). The assignment of functions/applications to a mobile terminal between an access node 800 and a gateway 802 will also depend upon the characteristics of the service type provided by the application (for example, the average IP session duration, the popularity of the particular application, the average mobility of mobile terminal using the service provided by the application etc).

Traffic management may be performed at the access node 800, where there is access to real-time radio information from the radio frequency part of the NodeB, the Femto or the AP serving the mobile device.

Centralised Radio Resource Management (RRM) may be provided at the gateway 802, and maintains performance across different access modes 800, which may have different radio access technologies, frequency bands, coverage etc. The RRM function 724 of the platform 700 of the gateway 802 may obtain information regarding radio traffic management from each access node 800 to dynamically position subscribers to particular radio technology. This technique will be used to allocate network resources based on the resource availability, application used and user mobility, For example, the traffic management information may be provided by the soft NodeB 708, Femto or AP of the platform 700 at the access node 800. This soft NodeB 708 obtains radio information relating to the mobile terminal from the radio frequency part of the NodeB to which the mobile terminal is wirelessly connected.

For a particular mobile terminal, functions provided by an access node 800 and gateway 802 may be coordinated to work together in an advantageous manner (i.e. a hybrid or distributed arrangement). For example, the gateway 802 may set operating limits or ranges within which functions performed by the access node 800 may be performed, without reference to the gateway 802. When the functions move outside the ranges set, control of those functions may be passed to the gateway 802.

Further, the access node 800 and the gateway 802 may cooperate to advantageously optimise content delivery to a mobile terminal.

The optimisation of content delivery will now be described with reference to figure 8 of the drawings. Content may be optimised at gateway 802 and at an access node 800. The gateway 802 may serve multiple access nodes 800, and my distribute content to those multiple access nodes 800, for onward transmissions from each of those access nodes 800 to a mobile terminal via the radio frequency part of NodeB, the Feinto or the AP serving that node. Radio quality measurements are reported by the mobile terminal to the access node 800 at regular intervals, such as 2 millisecond intervals. Radio quality measurement relating to that mobile terminal are transmitted between the radio frequency part of the NodeB, the Femto or the AP serving the mobile terminal to the access node 800 at regular intervals, such as between 2 and 10 millisecond intervals. These radio measurements are received at the soft nodes 702 and are passed to functions 704 (e.g. to Q0S function 732 for analysis).

These radio frequency measurements from the mobile terminal and the NodeB are reported by the access node 800 to the gateway 802 (e.g. to Q0S function 732 of the gateway 802 for analysis) at regular intervals, such as intervals of between 1 and 10 seconds. The gateway 802 may receive radio information from multiple access nodes 800. The radio measurements received by the gateway 802 may be analysed over a relatively long period, such as between 1 and 2 minutes. The radio quality measurements may be averaged (for example, the arithmetical mean of the radio quality maybe determined) over this time period. The transmission of content from the gateway 802 may then be optimised according to this calculation. Where the content is distributed by the gateway 802 to a plurality of access nodes gOO, the content distribution will be based on the analysis of the radio quality indicators from all of the access nodes 800. The analysis may consider the maximum or peak radio performance over the time period of between 1 and 2 minutes.

When the content is received by each access node 800, the access node 800 then distributes the content to each mobile terminal. This distribution is optimised based on real-time network mode and mobile terminal specific radio link quality, as determined over a period of, for example, between 1 and 10 milliseconds. That is, content delivered to a mobile terminal that has high radio link quality may be optirnised in a different manner to a mobile terminal that had poor radio link quality.

The co-operation between access nodes 800 and gateways 802 may further enhance the distribution of content in a manner now to be described with reference to figure 9.

When a mobile terminal requests a particular content item, this request is transmitted to the access node 800 serving that mobile terminal, assuming that this is the first request for this content item to the access node 800, the access node 800 passes this request to the gateway 802 serving the access node 800.

Assuming that this is the first request for this content item from the gateway 802, the gateway 802 retrieves the content from a content server. The content is then provided by the content server to the gateway 802, and from there is distributed to the access node 800, and onwardly to the requesting mobile terminal. Advantageously, the gateway 802 maintains a record of content items that are requested frequently. When a content item is determined by the gateway 802 to be requested frequently, this is stored in a cache 1110 associated with the gateway 802 (which may be the cache 728 of the platform 700). Subsequent requests for that content item from access nodes 800 to the gateway 802 can then be serviced by retrieving the content item from the cache 1110 and distributing the content item to the requesting access node 800, and thus avoiding the need to request the content from the content server.

The gateway 802 may be further configured to identify popular content items that are likely to be requested by a large number of access nodes 800. When it is determined that a content item is popular, the gateway 802 may push these content items to each of the access nodes 800 associated therewith (so that this content is hosted at the access node 800, using Content Delivery Network (CDN) function 730 of the network functions 704 of the gateway 802 and the access node 800). The content is then available at the access node 800 for transmission to any mobile terminal that requests it, without having to retrieve this content from the gateway 802 or the content server. Advantageously, the distribution of such content items is performed in a manner which takes into account the capacity or the congestion of the link between the mobile terminal and the gateway 802 and the nature of the content. For example, typically a link between a mobile terminal and the gateway 802 may experience very little usage and congestion in the early hours of the morning. The content item can be advantageously transmitted in between the gateway 802 and the access node 800 at this time, when there is spare capacity. The gateway 802 will determine whether the content item is suitable for transmission on this basis, for example, by taking into account a number of times that the content item has been requested, the size of the content item and the storage space at the access node 800. If a content item is relatively small and is time-critical, such as news headlines, then such a content item may be distributed frequently throughout the day, as such content is not suitable for transmission once a day at early hours of the morning, as it becomes quickly out of date.

Relocation of Mobile Terminal The procedures performed when a mobile terminal moves between cells in the mobile telecommunications network will now be described with reference to figure 10. In the conventional manner at step 12A, when the mobile terminal moves to the edge of its current serving cell, the radio measurements reported from the mobile terminal and the radio frequency part of the NodeB, the Femto or the AP serving that mobile terminal are used by the core network to determine when to perform a handover and to which target cell the handover should be performed. When the best target cell has been identified, handover to that target cell from the serving cell it is performed at 12B in a conventional manner.

At step 12C selected platform functions may be relocated from the source access node (that served the old cell) to the destination access node (that serves the new target cell).

When the source and destination access nodes are served by the same gateway, only base station function (such as soft NodeB functions 708) may be relocated to the destination access node.

The relocation of functions of the access nodes is performed independently to the radio handover, so for some time after the radio handover, the source access node continues to serve content to the mobile terminal through the destination access node. The routing of data packets for the 3G network between the destination and the source access nodes may be performed using an lu interface between the RNC or BRAS function 712 of the destination access node and the SGSN/GGSN function 714 of the source access node. Alternatively, the routing of data packets between the destination and the source access nodes can be completed by the SGSN/ GGSN function 714 of the destination access node connecting directly to functions of the source access node through an IP interface.

After handover has been completed at step 12B, the access node controlling the mobile terminal may be relocated from the source access node to the destination access node in coordination with the gateway. the standardised handover decisions (mainly based on coverage, quality, power, interference, etc.) for 2G, 3G, LTE & fixed network are used to move the mobile from one node or system to another. However, the platform 700 introduces new opportunity to make the handover decision based on type or characteristics of the certain application, type of user and the QoS requirements.

The timing of the relocation of access node functions from the source to destination platform may be dependent on the following: * the duration of the current connectionlconununication of the mobile terminal * the speed of movement of the mobile terminal 5. the characteristics of the applications being used by the mobile device, the quality of service, the predicated type and amounts of transmission ongoing.

* The radio resource allocations status at the mobile terminal * The respective node of the source and destination and access nodes.

At step 12D, optionally, some functions will be reallocated from the access nodes to the gateway. For example, if the destination access node is heavily loaded and is congested, or has a lower capability then the source access node, or the mobile terminal is determined to be very mobile, it may be advantageous to transfer functions to the gateway. Functions are reallocated from the access node to the gateway by, for example, a Serving Radio Network Subsystem (SRNS) relocation between the RNC function 712 of the access node and the gateway. Alternatively the functions may be reallocated by performing a radio reconfiguration of user connection to the mobile terminal.

The reallocation of functions from an access node to the gateway may be performed at call/communication sessions set-up. At call/communication session set-up, further subscriber information will be provided, which may be used by the access node or gateway to be determine whether it would be advantageous to reallocate functions from the access node to the gateway.

Reallocation of functions from the access node 800 to the gateway 802 may be performed during an active connection when a requirement of the communication sessions has been modified, or where the required resource is not available at the access node 800.

According to the same principles, applications may be (re)located (or distributed) between access nodes 800 and for gateways 802 to provide optimised application delivery/best use of the communication resources.

As mentioned above, information about each application used by the user at the mobile terminal is stored in an application context. The application context is shared between each access node 800 and gateway 802 that control the user connection for that mobile terminal. One of the access nodes 800/gateways 802 will be the "master" for that particular application, and that will also be the master of an application specific record in the application context. The application context is advantageously periodically synchronised between the access node 800 and the gateway 802.

The application information is the application context specific to a particular mobile terminal, and this is passed between access nodes and gateways during reallocation for a mobile terminal, enabling the application to be seamlessly passed access nodes/gateways, avoiding impacts to the user experience.

Figure 11 shows the transfer of application information between access nodes and gateways.

Tailoring Bandwidth to Application Radio measurements received from the radio frequency part of the NodeB, the Femto or the AP serving the mobile terminal are passed to the soft nodes 702 of the platform 700 (of the access node 800 or gateway 802 serving the mobile terminal), and are passed to the network functions 704 of the platform 700, which then distributes the measurements to where necessary within the platform 700. The platform 700 has access to the subscriber information from the core network, which allows the network functions 704 to deliver data traffic in a manner that is optirnised for radio conditions as indicated by the radio measurements. The data traffic may also be optimised according to the subscription of the user of the mobile terminal available radio resource, mobile terminal capability, and/or for the class of the terminal (e.g. access technologies used). This optimisation allows bandwidth usage to be balanced with customer experience. The subscriber information may include information about the price plan of the user of the mobile terminal. The mobile network operator may track the type of application used by the user, the total data usage of the user, and may differentially target radio resources the highest data value stream of users.

By hosting applications 740, 742 in the services part 706 of the platform the access node 800 (or at least the gateway 802), the point of the network that is aware of the application being used by the user of the mobile terminal closer in the link between the mobile terminal and the core network to the NodeB serving the mobile terminal. This enables the sharing of network resources to the most appropriate data streams, such as the most profitable data streams.

Such awareness of the application to which a request for data transmission relates allows the use low value data streams, such as peer-to-peer file sharing, to be allocated only limited bandwidth, so that remaining bandwidth can be targeted to particular users. In the uplink, transmission of data can be controlled by the access node 800 (or gateway 802) hosting the application to control data flow appropriately before data is onwardly transmitted towards the core of the network (which was not possible with conventional arrangements).

Application Prorammin Interface (API) As mentioned above, a novel API is provided which defines the language that each of the software modules 740, 742 of the platform 700 use to communicate to coordinate to optimise application delivery to users. The platform 700 negotiates which each application 740, 742 the specific resource and performance requirements based on the application characteristics, allowing the application to directly communicate the scheduling performance requirements, rather than using a predefined set of quality of service parameters. This negotiation between the platform 700 and the applications 740, 742 is facilitated by the API.

The API may also facilitate the provision of radio link quality information (e.g. from Q0S function 732) to applications 740, 742.

The API may further enable the platform 700 to control use of the applications 740, 742 -e.g. to allow, disallow or adapt the applications.

By way of example, the application 740 may be a Voice over IP (VoIP) application. The nature of Voice over IP communications is that there is a virtually continuous succession of small data packets in which voice data is communicated. The voice data must be communicated with no or minimal latency in order that a two-way conversation can be performed successfully.

The Voice over IP application 740 is able to compress voice data before transmission using a variety of techniques/CODECs. The compression techniques/CODECs may range from a relatively low compression technique, which provides high quality voice reproduction but requires a large bandwidth, to a much higher compression technique which provides reduced voice quality and which requires a much lower bandwidth.

The API is operable to provide details of the application characteristics to the network functions part 704 of the platform 700. This makes the network functions part 704 of the platform aware of the characteristics of the application. In the present example, as the application is a Voice over IP application, the network functions part 704 may be made aware that the application will tend to transmit continuous successions of small data packets that require transmission with no or low latency. The network function 704 may then be configured appropriately.

The API may further be operable to allow the network functions part 704 to communicate radio link quality information to the application 740. For example, when the network functions part 704 received information regarding the application characteristics (via the API), it may allocate radio link resources to that application 740. This allocation of radio link resources may be communicated by the network functions part 704 to the application 740 (via the API). The application 740 may then select an appropriate compression technique/CODEC in dependence upon the radio link quality available. During a Voice over IP call, the available radio link quality may be communicated regularly from the network functions part 704 to the application 740 (via the API) to allow the application 740 to vary the compression technique/CODEC used in accordance with changes to the radio link quality.

The network functions part 704 may control how the applications 740, 742 work (via the API). The network functions part 704 may allow, disallow or adapt the applications 740, 742 hosted in the services part 706 of the platform 700. For example, the network functions part 704 may require the Voice over IP application 740 to use a particular compression technique/CODEC if radio link bandwidth is restricted.

Another example of how the network functions part 704 may advantageously provide radio link quality information to an application (via the API) is when the application 742 is a gaming application used by several users. If the radio link quality information received by the application 742 indicates that bandwidth is restricted, the application 742 may adapt is communications to the users such that latency of the communications is increased uniformly for all of the users (so that they all experience the same delay), in order that each of the users is provided with the same gaming experience.

In the embodiments described, the devices that connect to the platforms 700 are mobile devices that connect to the platforms via the radio access network of a mobile/cellular telecommunications network. It should be appreciated that non-mobile (fixed) devices may be connected to the platforms 700, for example by a wired or cable connection.

Allocation of Services The control means is responsible for allocating the service instance for each UE, based on the UE locations and the control means capacity, capability and available resources to host another instance of a service.

For certain low popularity services or where the available serving control means capacity or capability is limited, the service can be hosted from a central control means, or from a neighbouring distributed control means.

For some services/functions, where the source and destination client applications are in the same geographical region, being served by the same site (e.g. BTS location) or site cluster (e.g. finite number of sites), the access node 800/gateway 802 ensures that the server for the service is located close to both users, and the traffic is routed between the users within the site.

"Video Buffer Preloading" Within a cell the cost to carry data between a particular mobile device and the base station depends on many factors. This "cost to carry" data is an indicator of total resources required to convey the data. For example, macro or femto base stations and mobile devices that operate in accordance with cellular telecommunications Standards/transport protocols vary the power of radio transmissions in dependence upon the characteristics of the link between the base station and the device. Power is increased if the distance between the base station and the device is greater, or if the radio conditions are poor (which may be caused by environmental factors or by obstacles, such as buildings) between the base station and the device. Such an increase in power increases interference, and therefore reduces the overall capacity of the base station to convey data between itself and other devices in the cell.

Conventionally, a mobile telecommunications network has no control over when or where data is transmitted between a mobile device and base station or other access point, and will simply enable transmission of the data on demand.

In the current HSPA networks the data bandwidth on the radio provides ample average user rates to support uninterrupted viewing of video content.

The massive growth of data on mobile networks will require high capacity investment to maintain the customer experience; however mobile operators are optimising the usage of the radio resource to manage the investment.

For video applications this currently consists of three techniques: -Scaling the codec rate of the content to provide similar user experience but lower the required user data rate over the network; and -Shaping the flow of packets to manage the service impact to the network -Managing the buffer of the mobile device to ensure that data is delivered just in time.

The video buffer of the mobile devices may be managed as it was found that many customers often only watch part of a downloaded video clip/film before channel hopping or jumping forward to another part of the video, with the consequence being that much content that has been downloaded and buffered at the device and is discarded without being viewed.

As the mobile devices move around the network the radio conditions vary.

which means at some moments in time the data transmission to the device is costly in terms of network resource; and others there it has little cost.

Typically the most costly time is when the device is at the cell edge and is about to perform a handover; but equally there are many other areas where the coverage is degraded, e.g. deep inside buildings.

As shown in figure 12, a mobile device 1200 is connected to the core network 1216 via a base station 1214. Currently the video optimisation function 1220 is implemented as part of the service cloud 1218 of the core network 1216 of the operator. The video optimisation function 1220 optimises video content from content server 1232 for transmission over the mobile network. This has the advantage that video optimisation can be implemented in a single location, but has the disadvantage that it does not have any load information about the network or radio quality information about the customer.

The present embodiment seeks to overcome some of the problems associated with conventional mobile telecommunications networks. The embodiment seeks to allow mobile device users to send and receive data at times that are appropriate for the user whilst managing and making best use of the radio capacity of a telecommunications network.

The platform 700 described above allows application environments to move closer to the radio site. This enables more complex functions to be moved closer to the radio site, including video optimisation.

Figure 13 shows an enhanced architecture that allows radio conditions to be gauged and the instantaneous radio load to be taken into account when controlling the radio resources used by applications such as video, in the services part 706 of the platform 700, enabling the network to maximize the user experience and differentially target the radio investment at different applications.

Briefly, the access node 800 hosting the platform 700 can capture performance measurements from the network through: -Analysis of the normal power, timing advance measurement of the serving and neighbour cells it receives from all mobile devices allowing device location to be determined, without the device explicitly being required to provide its location, e.g. through GPS measurements the device -Tracking each user device allows measurements of velocity and degradation in radio performance; -Information from the scheduler in the RRM function 724 of the platform 700 allows measurements of quantity of radio resource required to serve each kbps, i.e. the devices radio efficiency.

The new architecture allows this to be completed in real time and allows the access node 800 to build up a map (or other record) of quality across its coverage area, as well as a probability that a device at a location and velocity will experience poor performance in the near future.

The video application includes an optirnisation function 1240 in the application/services environment 706 at the access node 800 which uses this information to determine the best time to transmit video content to the device.

The video optimisation application 1240 then uses this prediction of the future radio quality of the mobile device to determine whether the network should increase the quantity of the video buffered at the device -e.g. when the device is likely to move into the handover region; or reduce the quantity of the video buffered at the device when the predictions suggest the device is likely to move to better radio conditions.

This approach increases the efficiency of the radio whilst maintaining the user experience of the video service; the increase in efficiency allows the network operator to manage investment in radio resources.

A detailed embodiment that manages the delivery of data to users will now be described with reference to Figures 13 to 15B of the drawings.

Referring initially to Figure 13, the mobile device 1200 includes a service part 1202 (application layer) which hosts video application 1204. A buffer 1208 is associated with the application 1204. The application 1204 requires the periodic reception of data.

The radio access network of the telecommunications network includes a plurality of base stations, of which one base station 1214 is shown. Here, the term "base station" should be interpreted in its broader sense. The base station may be a cellular communications base station, such as a 2G, 2.5G, 3G or 4G "macro" base station. Alternatively, the base station may be a femto cell or may be an access point of a WiFi or other type of radio access network.

The network further comprises a network core 1216. The network may be provided with platforms 700 of the type described above, and a platform 700 may be associated with the base station 1214, for example to form an access node 800 (see Figure 6). The video optimisation function 1220 of the service cloud 1218 is linked to the core network 1216. A local video optimisation function 1240 is provided on the platform 700.

Data collection operations to generate a radio conditions map (or other record) of the cell associated with the base station 1214 will now be described with reference to the flow chart of Figure 14.

As described above, the mobile terminal 1200 measures the radio conditions of the cell on which it is registered and the neighbouring cells. These measurements are conventionally used, for example, for determining when to perform handover or cell reselection. According to this embodiment of the invention, at step 14A, the mobile terminal 1200 records the signal measurement data from the current cell and neighbouring cells and reports these to the scheduler / RRM function 724 of the platform 700.

The scheduler/RRM function 724 of the platform 700 may also record measurements of radio conditions made by the base station 1214 relating to radio communications with the mobile terminal 1200. Radio conditions information for the mobile terminal 1200 and from the base station 1214 provides an indication of the radio quality within the cell at the location of the mobile terminal 1200. Thus, the platform gauges (assesses) the radio conditions available to mobile telecommunications in the cell. If the radio quality at the location is high, then the amount of radio resource required to send data between the base station 1214 and the mobile terminal 1200 will be small, whereas if the radio quality at the location of mobile terminal is poor, relatively more radio resources will be required to transmit the same quantity of data. The radio conditions measurements recorded may include any or all of: Channel quality indicator (CQI), which is a measurement of communication quality of the communication channel between the mobile terminal 1200 and the base station 1214, for example, based on signal-to-noise ratio, signal-to-interference plus noise ratio (SINR), signal-to-noise plus distortion ratio (SNDR). Then you receive signal strength.

Received signal strength Transmit power level Neighbour cell measurements ACK/NACK ratio: the ratio of acknowledgements of successfully delivered data packets to the ratio of unsuccessfully delivered data packets.

Block error rate (BLER): the ratio of the number of the blocks containing errors to the total number of blocks received.

Frame error rate (FER): an indicator of the proportion of frames transmitted that are received with errors.

Bit error rate (BER): the ratio of received bits that contain errors to the total number of received bits.

Relative signal strength indicator (RSSI): the measurement of strength of radio signals at the point at which they are received.

Received signal code power (RSCP): the power measured by a receiver on a particular physical communication channel, and which can be used to calculate path loss.

Call Admission Control Parameters.

Call load/congestion parameters.

Q qual: Measurement of downlink quality parameters, e.g. downlink transport block error rate.

At step 14B the location of the device 1200 at which the ratio conditions measurements are made is determined by location tracking function 722 of the platform 700. The location may be determined by GPS, cell triangulation or any other method. Preferably, the access node 800 hosting the platform 700 determines the location of a mobile terminal by analysing the received signal power from that terminal and the timing advance measurement for that terminal, and does not require explicit location information to be provided, such as GPS measurements.

This data is stored in a profile store 1242 in the platform 700.

At step 14C it is determined whether the map of the cell served by the access node 800 is complete. If the profile is complete, then the procedure of Figure 14 may be terminated for a predetermined time period; however, the procedure may be reactivated periodically in order to update the profile.

On the other hand, if it is determined at step 14C that the profile of the store 1242 of the platform 700 is incomplete then the procedure returns to step 14A and radio data continues to be recorded by the terminal 1200 and reported to the platform 700.

The map may reflect radio conditions provided by a multiplicity of mobile devices in the cell.

When the profile of the cell is complete a logical or virtual map of radio conditions across the coverage area of the cell is created. This map provides an indication of the radio resources required to transmit data at any particular location within the cell, in both the downlink and the uplink. For example, locations at the edge of the cell will generally require use of greater amount of radio resources to transmit data than a location at the centre of the cell, adjacent to the base station 1214 (that is the uplink and downlink bandwidth efficiency is lower at the edge of the cell than at the centre of the cell). Also, areas within a cell that are shielded by obstructions will require greater radio resources to transmit a given amount of data. This information is reflected in the map.

The cell profile data in the profile store 1242 may be used to identify parts of the coverage area of the cell where high quality radio resources are available for advantageously performing data communication with the device 1200 -typically, when the device is in a part of the cell which has good radio conditions and therefore low "cost to carry" data.

Optionally, the platform 700 modifies the radio measurement control parameters for the mobile terminal 1200 (and other mobile devices in the cell) so that the terminal 1200 (and other devices) measure radio conditions with greater resolutions and frequency. The more detailed radio conditions information is reported to the RRM function 724 of the platform 700 and enables the generation of a more accurate cell map/profile.

When the profile in the profile store 1242 is complete the profile store 1242 contains a logical map of the radio conditions within the cell served by the base station 1214. The "cost to carry" data within the cell at each location can be determined from the information in the profile store 1242. Using the data in the profile store 1242, a prediction processor 1244 of the platform is able to predict at a particular location in the cell whether the mobile terminal 1200 will be in radio coverage in the cell which has a low cost to deliver data or a high cost to deliver data (that is, a high bandwidth efficiency or a lower bandwidth efficiency). The predictions of the radio conditions are based on the data collected in the procedure described in relation to the flow chart of Figure 14.

However, as the radio conditions within the cell change infrequently, the prediction is generally likely to be accurate. As mentioned above, the profile/map stored in the profile store 1242 may be updated at regular intervals so that changes to the radio conditions within the cell are reflected by the information stored in the profile store 1242.

A process for providing improved delivery of data to mobile terminals will now be described with reference to the flow charts of Figures 15A and 1SB.

At step 15A the video application 1204 on mobile terminal 1200 issues a request for the data. This request is transmitted wirelessly to the base station 1214 and onwardly to the platform 700. This request is received by the prediction processor 1244.

At step 1 5B the current radio condition measurements on the mobile terminal 1200, are gauged by reporting them to the RRM function 724 by the mobile terminal 1200 for assessment. These radio condition measurements are then passed to the prediction processor 1244. Optionally, the RRM function 724 of the platform 700 modifies the radio measurement control parameters of the mobile terminal 1200 so that the terminal 1200 measures radio conditions with greater resolution frequency then it does conventionally. A more detailed radio condition information is reported to the RRM function 724 of the platform 700 and provides more accurate cell information to the prediction processor 1244.

At step 15C the prediction processor 1244 uses the radio condition measurements received from the RRM function 724 to calculate the location of the mobile terminal 1200. The radio conditions information may include the transmission power, timing advance measurement for the device, such that this allows the location of the device to be determined without the device explicitly being required to provide its location. Alternatively, the mobile device 1200 may explicitly indicate its location in by transmitting GPS measurements from the mobile terminal 1200 to the prediction processor 1244.

At step 1 5D the radio conditions measurements are further analysed by the prediction processor 1244 to estimate the velocity of the mobile terminal 1200 -that is, the speed and direction of a mobile terminal 1200.

At step 15E the prediction processor 1244 calculates the load of the cell served by the base station 1214. That is, the processor 1244 calculates the proportion of total cell capacity that is currently being used by all the mobile devices served by the cell. The prediction processor 1244 makes this calculation using information received from the RRM function 724.

At step 15F the prediction processor 1244 identifies that the application is a source of the request for data in step 15A. In this example, the application is video application 1204 of mobile terminal 1200. Information about the application may also be obtained, such as the video playback rate, session duration and volume of data transmitted by the session.

In this example, the prediction processor 1244 then determines, at step 15G, the status of any buffer associated with the application. In this example, the video application 1204 is associated with buffer 1208 of the mobile terminal 1200. A value indicative of the amount of data in the buffer is retrieved and analysed by the processor 1244.

The buffer 1208 operates in association with the video application 1204 in the generally conventional manner so that, when video data is streamed to the mobile terminal 1200 a portion of advance video data is held in the buffer. For example, the buffer 1208 may seek to generally store 20 seconds of video data in advance of the video currently being displayed by the user of the mobile terminal 1200. In this manner, should there be a temporary interruption of transmission of video data to the mobile terminal 1200, the user can continue viewing the content uninterrupted for up to 20 seconds until the content of the buffer is exhausted. Generally, once consumed, the content stored in the buffer is discarded. In this step, the prediction processor 1244 receives the current status of the buffer 1208. For example, if the buffer has 30 seconds of advance video content store, this information is passed processor 1244.

The base station 1214 also includes a downlink buffer, and the occupancy of this buffer may also be reported to the prediction processor 1244.

As mentioned above, the service cloud 1218 conventionally includes video optimisation function 1220 for optimising video content for transmission over a mobile telecommunications network. Alternatively or additionally a video optimisation function 1240 may be provided in the services part 706 of a platform 700. If the video optimisation function 1240 is provided instead of the video optimisation function 1220, then the video optimisation function 1240 may perform the functions that would otherwise be performed by the video optimisation function 1220 (i.e. optimising video content for general transmission over a mobile telecommunications network). Video optimisation function 1240 may also perform the function of optimising video content so that it is adjusted for maximum efficiency of transmission within the particular cell served by the platform 700. For example, video optimisation function 1240 may take into account cell load information provided by the RRM function 724 and may vary the CODEC used to transmit the data in dependence upon the load conditions. If the cell is heavily loaded, then a CODEC will be used that performs a greater amount of compression, whereas if the cell load is light, then the CODEC used may perform less compression in order to provide a higher quality image.

The video optimisation function 1240 has associated with it a video buffer 1246. This buffer 1246 stores video content received from the service cloud 1218 so that it is ready for onward transmission to mobile terminals within the cell served by the platform 700 when required.

At step 1511 the status of the buffer 1246 is determined by the processor 1244.

The processor 1244 determines how much advance data is present in the buffer 1246 which relates to the content being consumed by the mobile terminal 1200 (the buffer may include many different types of content).

At step 151 the processor 1244 predicts the location of mobile terminal 1200 when the next video content data will be received from the video optimisation function 1240 by the mobile terminal 1200. That is, the current location and current velocity information calculated at steps i SC and 1 SD is used to predict the future location of the mobile terminal at a time when video content will next be transmitted. For example, if the position of mobile terminal in latitude and longitude is calculated at step 1 5C and it is known that the terminal is travelling at five mph in an easterly direction, then the position of mobile terminal one minute later can be predicted.

At step 15J the cell map/profile from the store 1242 is consulted by the processor 1244 to retrieve data relating to the predicted future location of the mobile terminal.

At step 15K a decision is made whether to transmit video content data to the mobile terminal 1200. The processor 1244 makes this decision by evaluating the nature of the application requesting data (from step 1 5F), the mobile terminal 1200 buffer 1208 status (from step 1SG), the status of the video content buffer 1246 of the platform 700 (from step 15H), the radio measurements at the current position of the mobile device (from step 1 5B), and the estimated radio conditions at the predicted location of the mobile terminal 1200 (from step 15J). If the radio conditions are good at the current location and are estimated to be poor (e.g. below a quality threshold) at the predicted location of the mobile terminal 1200 this will be considered by the processor 1244 as a factor in favour of transmitting a large amount of video content data to the video buffer 1208 of the mobile terminal 1200 when at the current location. This is because, when the radio conditions are favourable at a particular location, the "cost to carry" the video content data will be relatively low. Transmitting the video content data at such a time will make efficient use of radio resources. If the radio conditions are estimated to be favourable, the status of the buffers 1208 and 1246 are still taken into account. For example, if the buffer 1208 is full or nearly full, then it may be determined by a processor 1244 that content should not be transmitted. Also, if it is determined by the processor 1244 that the video content buffer 1246 of the platform 700 is empty or almost empty of content relating to the video content required by the video application 1204, then the processor 1244 will prevent the content for being transmitted (at is unlikely to be available from the buffer 1246).

On the other hand, if it is determined at step 1 5B that the radio conditions at the current location are poor and is estimated at step 15K that radio conditions at the predicted location of the mobile terminal 1200 are good (e.g. above a quality threshold), so that there will be a high "cost to carry" data at the current location, then this will be a factor taken into account by the processor 1244 against transmitting content at the current location of the mobile terminal 1200.

For example, if the determined that radio conditions at the current location of the mobile terminal 1200 are poor, then the transmission of video content data will consume a large amount of resources of the cell and will make inefficient use of the available resources of the cell. Instead, the transmission of data is delayed until the mobile terminal moves to the future location, where radio conditions are good. However, the processor 1244 will not make a decision as to whether or not to transmit the video content data based solely on the assessed radio conditions at step 1 5B and the estimated radio conditions at step 15K. The processor 1244 will take into account the status of the buffers 1208 and 1246. For example, if the buffer 1208 of the mobile terminal 1200 is empty or nearly empty, and the nature of the application consuming the content is one that requires continuous delivery of content (such as video streaming), then a decision may be made to transmit video content data even though the radio conditions are poor. The processor 1244 takes into account the nature of the application requesting the data. In this example the application is a video application 1204. To provide video streaming the video application 1204 must have access to a continuous supply of video content data. However, if the request for content is from an application 1206 which does not require a continuous stream of data, such as a web browser application, the processor 1244 may determine that it is acceptable for there to be an interruption of delivery of content from the application 1206.

In summary, the information obtained in steps 15B, F, G, H, I and J are used to determine at step 15K whether to allow the video optimisation function 1240 to transmit any (or how much) data to the mobile terminal 1200 at the current location. If the processor 1244 decides not to transmit data for the curent location of mobile terminal 1200, then the process returns to step 15B. On the other hand, if it is determined at step 15K to transmit data to the mobile terminal 1200, then the process continues to step 1SL.

At step 1SL the processor 1244 optimises video content data for a mobile terminal 1200. The processor 1244 may determine an amount of content data to transmit. For example, if the radio conditions are assessed to be poor at step 1 5B, then a small amount of content data will be transmitted, whereas if the estimated radio conditions at step 1 5B are good, then a larger amount of video content data may be transmitted. At step 1 5L the content data may be further optimised by compression data using an appropriate CODEC. In this regard, the processor 1244 issues an instruction to the video optimisation function 1240 of the platform 700 to use a particular CODEC. For example, if radio conditions are good at the current location of the mobile terminal 1200 then the processor 1244 may instruct the video optimisation function 1240 to use a CODEC with a lower compression than if the radio conditions are estimated to be poor. The CODEC used by the video optimisation function 1240 may also take into account the overall radio load on the cell as mentioned above, and as determined at step 15 E. At step 15M the video optimisation function 1240 transmits data to the mobile terminal in an amount and in a format as determined at step 1 5L. Video content data is transmitted by the base station 1214 over the radio access network to the mobile terminal 1200 where it is received by the video buffer 1208 and made available for use by the video application 1204 for displaying streaming with video content to the user of mobile terminal 1200.

The effect of the procedure of the flow chart of Figures 15A and 15B is to ensure that the applications which require data on mobile terminal served by the cell for which the platform 700 is provided receive content in the most efficient manner in terms of radio resources. For example, when the application is a video application 1204, the platform 700 will vary the amount of data stored in the video buffer 1208 on the mobile terminal 1200 as the mobile terminal 1200 moves around the cell. When the mobile terminal 1200 is in an area of the cell where there are good radio conditions, a large amount of video content data may be transmitted and stored on the video buffer 1208 in preparation for use by the video application 1204. In contrast, when the mobile terminal 1200 moves to an area of the cell there are poor radio conditions data may not be transmitted and the amount of data in the buffer may be allowed to be decreased to a minimum amount (for example 3 seconds of advance video content). In this way, video content data is transmitted generally when radio conditions are good, so that the event radio resources of the cell are used most efficiently.

Data Flow Management As mentioned above, the type of application requiring the data may be taken into account. For applications such as web browsing or operating system updates interrupting the delivery of data is acceptable, so that no content data may be transmitted by the platform 700 when the mobile terminal 1200 is in an area of the cell where there are poor radio conditions. On the other hand, applications such as video applications 1204 must provide the user with continuous content.

The processor 1244 may initialise applications, suspend applications, or terminate applications in dependence upon the estimated radio conditions or the predicted radio conditions of one or more mobile terminals. The applications may be hosted on the platform 700 or on the mobile terminal 1200. An API may be used to control state of the application.

The processor 1244 may initialise, suspend, or terminate data flow associated with applications in dependence upon the estimated radio conditions or the predicted radio conditions of one or more terminals.

The terminals may be a source or destination of the traffic associated with the application, or a terminal or application competing for radio resource with the higher priority application.

The processor 1244 may initialise applications, suspend applications, or terminate applications in dependence upon the estimated backhaul transmission conditions or the predicted future backhaul capacity available to an application being provided to one or more mobile terminals. The applications may be hosted on the platform 700 or on the mobile terminal 1200. An API may be used to control state of the application.

The processor 1244 may initialise, suspend, or terminate data flow associated with applications in dependence upon the estimated backhaul capacity or the predicted backhaul capacity available for the application being provided to one or more terminals.

The predicted backhaul capacity available to the application may be based on measurements of the traffic flowing from the site, including: -Number of active customers sharing for resources -Number of application instances running in the Platform or running through the platform -% of applications being high capacity applications (e.g. Video, or connections to specific URLs/IP addresses/domains) -The number of connection request, DNS requests or content and application requests flowing through platform in the previous seconds -The % recent connection, content, application requests being for high capacity applications or services -Historic usage pattern trends seen over previous hours, days at same time, previous weeks at same time of day and weekday The example discussed above is primarily concerned with transmitting video data in the downlink. The map represents the cost to carry data in the cell in both the uplink and the downlink. The procedure of Figures 1 5A and 1 5B may be used to predict the location of the mobile terminal 1200 and to allocate network resources to the mobile terminal for transmitting data in the uplink in dependence upon the estimated radio conditions at the predicted location.

The radio conditions predictions may be used to trigger optimisations and RRM decisions in other cells hosted by the platform 700 or another platfom.

A differential charging structure may be applied to data downloaded in the background to the buffer 1208 in accordance with this embodiment. For example, the user may not be charged for such background downloading of data but may only be charged when the data is actually consumed.

The headings used in this description shall have on affect on the meaning or

interpretation of the description.

Claims

Claims 1. A mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access network includes control means operable to control the allocation of network resources to said mobile terminals, and wherein the control means is operable to gauge the radio conditions available to said mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon.
2. The network of claim 1, wherein the radio access network comprises a plurality of cells and the control means controls the transmission of data within one of the cells in dependence upon the gauged conditions within that cell.
3. The network of claim 1 or 2, wherein the control means is operable to gauge the radio conditions by assessing the radio conditions available to said mobile terminals.
4. The network of claim 1 or 2, wherein the control means is operable to gauge the radio conditions by predicting the radio conditions available to said mobile terminals.
5. The network of claim 4 wherein the control means is operable to build and maintain a record of radio quality across a coverage area of the network, and to use this record to predict the radio conditions available to said mobile terminals.
6. The network of any one of claims 1 to 5 wherein the control means is operable to gauge the backhaul resources available to said mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon, and wherein: the control means is operable to gauge the radio conditions by assessing the backhaul resources available to said mobile terminals; the control means is operable to gauge the radio conditions by predicting backhaul capacity available to said mobile terminals and/or the control means is operable to build and maintain a record of backhaul capacity for a cell or radio site, and to use this record to predict the backhaul capacity available to said mobile terminals.
7. The network of any one of claims 1 to 6, wherein the control means is operable to calculate the location and/or velocity of the mobile terminals and to control the transmission of data in dependence thereon.
8. The network of claim 7, wherein the control means is operable to use the record of radio quality across the coverage area and the calculated location and velocity of one of said mobile terminals to estimate the radio conditions available to that mobile terminal at a future location and to control the transmission of data between the radio access network and that mobile terminal at the calculated location in dependence thereon.
9. The network of any one of claims 1 to 8 wherein the control means is operable to trigger initialisation, suspension or termination of applications based on the radio conditions or backhaul capacity measured or predicted.
1O.The network of claim 8, wherein the control means is operable to increase the amount of data transmitted at the calculated location of the mobile terminal if the radio conditions at the future locations are predicted to be below a quality threshold, and/or to decrease the amount of data transmitted at the calculated location of the mobile terminal if the radio conditions at the future location are predicted to be above a quality threshold.
11. A method of operating mobile telecommunications network including a core and a radio access network having radio means for wireless communication with mobile terminals registered with the network, wherein the radio access includes control means, the method including operating the control means to control the allocation of network resources to said mobile terminals, and to gauge the radio conditions available to said mobile terminals and to control the transmission of data between the radio access network and the mobile terminals in dependence thereon.
12. The method of claim 11, wherein the radio access network comprises a plurality of cells and the control means controls the transmission of data within one of the cells in dependence upon the gauged conditions within that cell.
13. The method of claim 11 or 12, wherein the control means gauges the radio conditions by assessing and/or predicting the radio conditions available to said mobile terminals.
14. The method of claim 13, wherein the control means builds and maintains a record of radio quality across a coverage area of the network, and uses this record to predict the radio conditions available to said mobile terminals.
15.the method of claims 13 or 14, wherein the control means calculates the location and/or velocity of the mobile terminals and controls the transmission of data in dependence thereon.
16.The method of claim 15, wherein the control means uses the record of radio quality across the coverage area and the calculated location and velocity of one of said mobile terminals to estimate the radio conditions available to that mobile at a future location and controls the transmission of data between the radio access network and that mobile terminal at the calculated location in dependence thereon.
17.The network of claim 16, wherein the control means increases the amount of data transmitted at the calculated location of the mobile terminal if the radio conditions at the future location are predicted to be below a quality threshold, and/or decreases the amount of data transmitted at the calculated location of the mobile terminal if the radio conditions at the future location are predicted to be above a quality threshold.
18. A telecommunications network substantially as hereinbefore described with reference to and/or as illustrated in any one of Figures 13 to 1 5B of the accompanying drawings.
19. A method of operating a telecommunications network, substantially as hereinbefore described with reference to and/or as illustrated in any one of Figures 13 to 1 5B of the accompanying drawings.t::r: INTELLECTUAL . ...* PROPERTY OFFICE Application No: GB 1111306.5 Examiner: Mr Adam Tucker Claims searched: 1-19 Date of search: 28 October 2011 Patents Act 1977: Search Report under Section 17 Documents considered to be relevant: Category Relevant Identity of document and passage or figure of particular relevance to claims X 1-3&11-US6697378B1 13 (Patel) See the whole document and in particular the abstract, Figures 3 & 12 and col 1 lines 24-36, col 2 lines 33-48 and lines 57-64, col 3 line 58-col 4 line 19, col 4 lines 49-54, col 7 lines 57-65, col 8 line 64-col 9 line 1, col 9 lines 37-40 and claims 1-4 X 1-3&11-U52003/0142632A1 13 (Lin et al.) See in particular Figure 1 and paragraphs 10, 12, 26, 32, 35, 36 and claims 1 & 15 X 1-3&11-WOO2/049237A2 13 (Ericsson) See in particular the abstract, page 3 line 17-page 4 line 13, page 5 line 19-page 6 line 6, pages 9-11, 13, page 14 line 26-page 15 line 19 and page 21 lines 24-26 and claim 1 and Figure 1 A,P -WO 2011/057292 Al (Movik Networks) See the whole document and in particular paragraphs 5, 7, 10-13, 15, 26 & 38-48 A -EP2253179A1 (Qualcomm Inc.) See the abstract and paragraphs 5 & 14 Categories: X Document indicating lack of novelty or inventive A Document indicating technological background and/or state step of the art.Y Document indicating lack of inventive step if P Document published on or after the declared priority date but combined with one or more other documents of before the filing date of this invention.same category.& Member of the same patent family E Patent document published on or after, but with priority date earlier than, the filing date of this application.Field of Search:Search of GB, EP, WO & US patent documents classified in the following areas of the UKCX: Worldwide search of patent documents classified in the following areas of the IPC HO4L; HO4N; HO4W The following online and other databases have been used in the preparation of this search report WPI, EPODOC Intellectual Property Office is an operating name of the Patent Office www.ipo.gov.uk *.:r: INTELLECTUAL . ... PROPERTY OFFICE 71 International Classification: Subclass Subgroup Valid From HO4W 0088/12 01/01/2009 HO4L 0012/56 01/01/2006 HO4L 0029/06 01/01/2006 HO4L 0029/08 01/01/2006 HO4N 0007/26 01/01/2006 HO4W 0004/02 01/01/2009 HO4W 0024/02 01/01/2009 HO4W 0028/02 01/01/2009 HO4W 0028/16 01/01/2009 HO4W 0064/00 01/01/2009 Intellectual Property Office is an operating name of the Patent Office www.ipo.gov.uk