GB2481716A

GB2481716A - Radio access network control means operable to control the transfer of data between a mobile device and a central data backup store

Info

Publication number: GB2481716A
Application number: GB1111310.7A
Authority: GB
Inventors: David Andrew Fox; Youssef Chami; 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: GB201011166D0; GB201111310D0; GB2481716B

Abstract

A mobile telecommunications network includes a core and radio access network having a data store 1420 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 700 operable to control the use of network resources by said mobile terminals, Said control means is further operable control to the uplink transmission of data from the mobile terminals to a central backup data store 1420. The control means may temporarily store uplink data from the mobile terminals, for subsequent transmission to the central data store. The control means may transmit the temporarily stored data in dependence upon network load. The control means is also operable to control the upload of device backup data, and prepositioning of device backup data in the relevant data stores for the device.

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

According to a first aspect of the present invention, 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 control to the transfer of data between the mobile terminals and a store.

The data may be data for upload from the mobile terminals to the store. The data may be backup data from the mobile terminals.

The control means may be operable to temporarily store data transmitted from the mobile terminals at the radio means (e.g. radio site/access node), for subsequent transmission to the data store.

The control means may be operable to temporarily store backup data from the mobile terminals, for subsequent transmission to the store.

The store may be is provided at the core, a webpage and/or cloud storage.

The control means may be provided on a novel "platform" of the type described in detail below in the detailed embodiment to be described by way of example. The control means may include a backup or upload application implemented on such a platform.

The backup data may be transmitted from the terminals to the core backup store, cloud storage or website, or from the backup store to the terminal, or in both directions.

The control means may be operable to temporarily store data from the mobile terminals for subsequent transmission to the core backup store, cloud storage or website. However, in some circumstances the data will be retained for long term storage or permanent storage by the control means -for example if it is determined that the terminal is fixed in position or has a low mobility state, so that it is likely that, should the data be required again by the terminal, the terminal will be in communication with the same control means. The control means may include local storage for storing the data (whether temporarily or otherwise).

The control means may transmit the temporarily stored backup data (for example to the core backup store, cloud storage or website) in dependence upon one or more predetermined criteria. The criteria may be determined by the control means and may include at least one of location of the terminal, priority of the data, radio site backhaul load, network load, time of day, user's subscription information, mobility of the terminal (e.g. whether it is stationary, fast moving or slow moving), available storage on the terminal and/or core backup store, cloud storage or website, radio access technology through which the mobile terminal is connected (such as 2G, 3G etc), offered throughput for the terminal (the communication speed available to the terminal at its current location), the anticipated user experience of the data flow with the current network load, and the user activity in other services (such as other requirements for data communication by other services being used by the terminal).

The control means may be provided at an access node site at the edge of the network, data stores may be provided in addition to the core backup store, cloud storage or website. Each distributed backup store may be associated with a respective control means (and may be in the same geographical location as the control means or proximate the control means). The control means may control when data from each backup store (whether the core backup store or one or more of the distributed backup stores) is transmitted to the terminal or to another one of the backup stores (the core backup store or one or more of the distributed backup stores).

The control means may predict the future location of terminals and control on which of the backup stores (core backup store and/or distributed backup store, cloud storage or website) data are stored in dependence upon the predicted future location. Advantageously, the control means may select a backup store that is likely to be at a location geographically near the mobile terminal when this data are required in future.

The present invention also provides a corresponding method of operating a mobile telecommunications network.

According to a another aspect of the present invention, there is provided a mobile telecommunications network and a radio access network, both including data storage, 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 the mobile terminals, and wherein the control means is operable to control the uploading of data between the mobile terminals and storage in the core network, cloud storage or website.

The control means may be provided on a novel "platform" of the type described in detail below in the detailed embodiment to be described by way of example. The control means may include an application implemented on such a platform responsible for the transfer of data from terminal to a data store, for example to control uplink connections and data associated with such applications. The control means may chose to terminate data from the terminal at a local data store before later transmitting it to a data store in the core network, cloud storage or website.

The control means may transmit the temporarily stored data to a core data store, cloud storage or website in dependence upon one or more predetermined criteria, for example the available backhaul bandwidth.

According to a further aspect of the present invention, there is provided a mobile telecommunications network 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 the mobile terminals, and wherein the control means is operable to control the backing up of data between the mobile terminals and storage in the core network, cloud storage or website.

According to a further embodiment of the present invention, there is provided a mobile telecommunications network including a core having a store 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 the mobile terminals, and wherein the control means is operable to control the synchronisation of stored data between the mobile terminals and the backup data store.

In the embodiment to be described the control means accesses a user specific context for each subscriber using a content synchronisation service. The user specific context may be available from the or each backup store. The user specific context may include a list of locations and security credentials for each of the locations where data are stored for the specific user or mobile terminal.

The user specific context may include a list of file names and content descriptions relating to the data stored for a specific user or mobile terminal at the or each of the storage locations.

In the embodiment the control means may only synchronise a sub-set of the data stored in the backup store or the device.

In the embodiment the data are selected for synchronisation by the user of the mobile terminal.

The selected data may be prioritised and scheduled for synchronisation by the user of the mobile terminal and/or the control means.

In the embodiment the control means is operable to synchronise data based on the measured location of the terminal.

In the embodiment the control means selectively stores data destined for the mobile terminal prior to transmission to the terminal by the mobile network.

For example, when it is required to restore backed up data to the mobile terminal, this data may be retrieved from the core backup store and may be temporally stored in a store associated with the control means until it is transmitted to the mobile terminal wirelessly by the network.

In the embodiment the decision to store data in the or each backup store may be based upon user defined criteria and/or network operator defined criteria and/or criteria defined by the control means.

When a plurality of backup stores are provided, in the embodiment, the control means is operable to interconnect with the stores local to the mobile terminal, over a fixed (wired) connection or a mobile (wireless) connection, for example via the internet. The control means may synchronise a list of data stored locally, and may retrieve data from the local store when requested by the mobile terminal, or by network or user criteria.

The mobile terminal may access and synchronise selected data stored on local storage and the core backup store over the internet.

The user defined criteria for data backup and/or restore may include (but are not limited to) priority, storage capacity of the mobile terminal, selected applications and data sources, time of day, terminal location, cost to synchronise, minimum throughput, minimum battery level, and specific services.

The operator defined criteria may include (but is not limited to): network load, time of day, user subscription information, priority of data, measured location of the device, mobility of the device, the available storage on the device and/or the or each backup store, the radio access technology through which the mobile is connected, the offered throughput for the terminal, and the user activity in other services.

In the embodiment the control means selects the physical location of the backup store in dependence upon the registered billing address of the mobile terminal, the available storage resource, the typical usage patterns and movement patterns of the mobile terminal.

In the embodiment the control means may consolidate user stored content from multiple local stores and backup stores in a single location.

In the embodiment the control means may be operable to move the user's stored content from one backup store to another backup store (whether a local backup store or the core backup store).

In the embodiment the movement of the content may be based on the available capacity in the or each backup store, a change in the user location, statistical analysis of terminal movement, and/or the typical type of access technology used by the user to synchronise or access the stored data.

In the embodiment the control means may be operable to predict the future location of the mobile terminals based on historic movement patterns or based on user provided information. The control means may populate data stores at identified locations prior to the predicted user presence at those locations. This is advantageous because this means that the data are available locally to the mobile terminal, so the data can be provided more quickly and more efficiently to the mobile terminal.

In the embodiment the control means may populate local data stores over the mobile (wireless/cellular) network, although this may also be done using a fixed (cable) connection.

In another aspect the present invention provides a mobile telecommunications network including a core having a backup store 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 control to the backing up of data from the mobile terminals to the backup store.

The control means may be operable to temporarily store backup data from the mobile terminals, for subsequent transmission to the backup store.

The control means may be operable to transmit the temporarily stored backup data in dependence upon network load.

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 the architecture for performing backup according to an embodiment of the invention; and Figure 13 is a flow chart showing the decision steps to perform backup.

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 of 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.

Optimised Content Upload When data is transferred from a device to the internet, the great distance and many interfaces/mediums the content has to pass over limit the upload speed of the radio technology and therefore the time it takes to deliver the content.

The delay that a customer experiences when uploading content or files to the internet has a direct correlation to customer perception of network quality. User experience can be improved if the time taken to delivery the content can be reduced.

As discussed above, the platform 700 allows application environments to move closer to the radio site. This enables more complex functions to be moved to the Radio Access Network and for them to be hosted on the platform 700. That is, the services part 706 of the platform 700 may host applications. The applications may be hosted by a platform 700 at access node 800 at the NodeB or at the Femto, or at the AP site or at the gateway 802 at the RNC or BRAS site of the network The platform 700, in the services part 706, hosts an uplink application 1700.

The uplink optimisation application 1700 may have an associated electronic store. The uplink application 1700 may control the uplink transmission of content from the terminal to central data stores -for example a data store located in the core network 1430, or a 3rd party web page/storage cloud.

When an uplink starts, the uplink Application 1700 estimates the likely difference in user experience for the customer in providing a direct upload, or an upload to the data store located at the radio site.

The uplink application 1700 may decide whether to temporarily store content at the radio site (e.g. in the store associated with the uplink application 1700), or to allow direct transmission to the core, web service, or cloud storage. The decision may be dependent on available radio resources, the customer type, the device capability and the available backhaul transmission resources as well as the assessed User Experience.

The uplink application 1700 may decide when to upload the data at the radio data associated with the uplink application 1700 store to a central location based on the transmission network load, customer type and historic movement patterns and an understanding of the application of the associated data stored.

Optimised Incremental Device Backup, Restore and automatic Content Distribution Smartphone devices are becoming increasing popular and within a couple of years these will represent the majority of personal mobile devices present on the mobile network. These devices have large amounts of storage capacity which will consist of personal data such as address book and calendars etc, together with media such as music and digital photographs. In addition the operating system data, user preferences will be present on the device. All together this data could represent anything from several Megabytes to many Gigabytes of data, if this data was lost or became corrupted it could be a considerable inconvenience to the user, it is therefore desirable to backup some or all of the data on the device.

One option is to perform the backup over the mobile network to store the data on a server which could be outside of the radio access network, situated either in the network operator's core network or in the internet. Transferring this data could put considerable load on the air interface (the interface between the user's device and the base station radio site) and the backhaul (the interface between the radio site and the core network) and onwards towards the backup server and provide poor user experience. Building capacity in these interfaces represent a considerable investment for the network operator, in particularly building radio sites, installing the air interface capacity and provisioning the backhaul capacity (e.g. through fibre optic cables) require large amounts of investment, on top of this are the costs associate with operating such as site rentals and electricity.

There is therefore a need to perform the backup and upload functions in the most efficient manner possible to reduce these investments but at the same time delivering an excellent back up and restore service for the customer.

As discussed above, the platform 700 allows application environments to move closer to the radio site. This enables more complex functions to be moved to the Radio Access Network and for them to be hosted on the platform 700. That is, the services part 706 of the platform 700 may host applications. The applications may be hosted by a platform 700 at access node 800 at the NodeB or at the Femto, or at the AP site or at the gateway 802 at the RNC or BRAS site of the network Also, as devices such as telephones and laptops become increasingly more advanced, additional functionality can be implemented in the application and operating system environment of these devices, allowing the devices to play a greater role in the end-to-end data pipe.

The platform 700, in the services part 706, hosts a backup application 1410.

The backup application 1410 may have an associated electronic store. The backup application 1410 may also forward data to a central backup store 1420 -for example located in the core network, or accessible via the core network.

The platform 700: * Makes measurements of the radio load; * Identifies the frequency and technology layer the subscriber is currently using; * Makes measurements of 2G/3G/4G user coverage/distance from the site per technology, and the overlapped coverage areas; * Makes measurements of Quality of the radio link to the subscriber; * Identifies the device type used by the subscriber/client; * Assesses the properties of that technology/frequency in a specific cell/location.

These measurements may be received at the soft nodes 702 (e.g. eNodeB 711) and passed to functions part 704 (e.g. QoS function 732).

The functions part 704 (e.g. Q0S function 732) may then pass all or selected parts of this information to the backup application 1410 hosted on the platform 700.

In accordance with this embodiment, the platform 700 is modified to introduce functionality which enables the radio resources and backhaul resources to be used more effectively. The backup application 1410 is provided in the services part 706 of the platform 700, as shown in Figure 12. This backup application 1410 is, for example, responsible for detecting the load on the air interface and to begin the backup operation at times of suitable (low) load; this could be during off peak times such as during the dark hours. The backup application 1410 may be configurable to allow the user to set their preferences such as which data to backup and how often to perform the backup. The backup application 1410 may also be configured by the network operator in the same way in order to allow the operator to select which elements of the device data could be backed up. The backup application 1410 may be provided at an access node 800 and/or at a gateway 802.

The backup copy of the device can be performed in two main ways: Periodic: The backup copy of the device data stored on the platform 700 may be transferred to a central backup server 1420 periodically; the frequency of this operation may be configured by the network operator or the backup application 1410 could manage this function again using load information from the backhaul network or information collected from other nodes in the network; the backup application 1410 is able to receive load and scheduling information from any other node in the network. This allows the network operator to transfer data to the central backup server 1420 in the most efficient manner, typically during off peak times where there are low traffic levels.

Event based: For event based backup, data backup can happen when the memory capacity of the platform 700 or the network load exceeds (or is below) a certain utilisation threshold.

During mobility or for specific device types, it is possible to backup to the radio site (the platform 700 at the access node 800 where the call is originated) and co-ordinate the backup with a central backup server 1420.

In case of the soft/softer handover for a 3G network, the serving base-station will be the serving node and the remaining base station(s) will act as drift node (s). The data is then combined in the platform 700 at the access node 800 from where it originated.

Content Caching (transparent caching) The backup application 1410 allows elements of the uploaded data to be distributed to alternative destinations (other than the main backup server 1420), for example photographic media could be automatically distributed to a photo sharing site, the address book data could sent or synchronised with the user's internet email account. Again transmission of this data may be scheduled by the backup application 1410 in order to take advantage of the network load.

Incremental Backup (Data Synchronisation) The backup application 1410 may typically perform an incremental backup function thereby eliminating the need to backup data which has been previously backed up. Control of this function is by the backup application 1410 and implementation of this reduces the load on the air interface.

Restore Upon loss of data the user or network operator may choose to perform an immediate restore, this may be done regardless of network load. Alternatively a background restore may be scheduled by either the user or network operator in this case it could be done using the load information available from the backup application 1410.

Charging Charging is avoided when the customer has a flat rate plan. In this case, the operator/supplier tracks total usage and alarms/rate-limits after that. If charging is not avoidable then CDRs may be generated by the central backup server node 1420.

How "the backup and restore" might work in Practice As described above, the backup and restore decision may be based on the policy role enforced by the operator and/or user in a static or dynamic configuration using the exiting or newly introduced network element(s).

The embodiment will now be described in more detail.

Returning to Figure 12, the network architecture will now be described in more detail. As mentioned above, a central backup server node 1420 is provided in the core network 1430 (but may be located elsewhere and be accessible by the core network 1430, e.g. via the internet). As also mentioned above, a platform 700 of the type described earlier in detail, and including a backup application 1410 provided in the services part 706, may be provided at one or more locations in the radio access network. In Figure 12 a first platform 700 is provided at a first access node 800, and a second platform 700A is provided at a second access node 800A. A third platform 700B is provided at a gateway node 802. The gateway node 802 is connected to the first access node 800 and the second access node 800A. The first access node 800 and the second access node 800A are able to communicate directly by a wireless communication with a mobile terminal 1440, whereas the gateway node 802 communications with mobile terminals, such as mobile terminal 1440, via one or more of the access nodes 800,800A. The access nodes 800, 800A communicate with the core network 1430 via the gateway node 802. The access nodes 800, 800A and the gateway node 802 may also communication with the internet directly if a decision is made to offload data traffic directly to the internet and bypass the core in the manner described earlier.

In practice there will be a multiplicity of access nodes and gateway nodes in the network.

Communications between the access nodes 800, 800A and the gateway nodes 802 may be by a wireless or fixed (cable) connection. Communications between the gateway nodes 802 and the core network 1430 may also be by a wireless or fixed (cable) connection.

Each of the backup applications 1410 has a local store (memory) associated therewith. This memory may be provided on the same platform 700 as the backup application 1410. The store may additionally, or alternatively, be provided elsewhere, and the backup application 1410 is configured to communicate with that store via the platform 700 using a wireless or fixed connection. The communication between the backup application 1410 and the separate store may be via the internet.

The core network 1430 may be connected to various data stores, for example via the internet, such as email servers and content sharing servers.

As discussed above, the user's mobile terminal 1440 may store various data, such as personal data (address book, calendar etc), content such as music and digital photographs, operating system data specific to the user and user preferences for the operation of the device and interaction with the network.

This data may be stored in a store 1445 of the terminal 1440 (although in practice it maybe stored in a plurality of separate stores).

An important feature of the present embodiment is to facilitate the backing up of such data on the terminal 1440 SO that the data can be restored to the terminal 1440 (or to another terminal), in the event that the data on the device becomes lost or the device 1440 itself is damaged or lost. The data from the store 1445 of the terminal 1440 is transmitted wirelessly by the radio access network of the cellular network to the base station with which the terminal 1440 is registered. The base station has associated with it a relevant access node (access node 800 in the example of Figure 12). The platform 700 of the access node 800 receives the data at the soft node part 702 of the platform, and passes this to the services part 706 of the platform. In the services part 706 of the platform 700 the backup application 1410 receives the data.

Data may be transmitted between the mobile terminal 1440 and the base station with which it is registered as the data are generated and stored on the store 1445. Alternatively, the data may be transmitted in dependence upon one or more criteria. The data may be transmitted at predetermined time intervals, when there is a predetermined amount of data to be transmitted, or in dependence upon other criteria. The criteria may be defined by the network operator and include (but not limited to): network load (or predicted network load), time of day, user's subscription type, priority of data, measured location of the terminal 1440 (or predicted location of the terminal 1440), mobility state of the mobile terminal 1440, available storage on the mobile terminal 1440, available storage for the backup application 1410 (on the platform 700 or in the local store), available storage in the backup server node 1420, the radio access technology through which the terminal 1440 is connected to the base station (e.g. 2G, 3G, 4G etc), the data communication rate available to the mobile terminal 1440 (or predicted data communication rate available to the mobile terminal 1440) and other functions simultaneously being performed by the terminal 1440.

The transmission of the data between the terminal 1440 and the base station may be dependent upon user defined criteria which include (but are not limited to): the priority of data, the storage capacity of the terminal 1440 (particularly the store 1445), the applications to which the data relates, the source of the data, the time of day, the terminal 1440 location, the cost to transmit the data, the data rate available for communication between the terminal 1440 and the base station, the remaining battery power of the mobile terminal and specific services.

If the data are transmitted in dependence upon particular criteria, a data transmission application 1450 may be provided on the terminal for controlling the transmission of data. The application 1450 may be configurable by the user to transmit data in accordance with the user defined criteria. If the network operator wishes to define the criteria for transmission of the data, then relevant criteria are transmitted in a message from the core network 1430 to the application 1450 on the mobile terminal via an appropriate access node 800.

Backup application 1410 may also define criteria for the transmission of data from the mobile terminal, and may configure the terminal application 1450 accordingly.

When data from the mobile terminal 1440 are received by the backup application 1410 on the access node 800, the backup application 1410 stores the data in the local store. The application 1410 then determines whether the data should be sent to a different location. Often, the most appropriate action will be for the data to be forwarded, via the gateway 802, to the central backup server node 1420 in the core network 1430. The central backup server node 1430 is a secure storage location and is readily accessible by access nodes 800 and gateways 802 throughout the network. Such an arrangement is particularly advantageous when the terminal 1440 is highly mobile, and it moves extensively around the geographical area served by the cellular network (it has a high mobility state).

However, some terminals may be fixed in position, or may move within a limited and predictable geographical area (they have a low mobility state). The backup application 1410 is operable to calculate the mobility status of the terminal or to communicate with the core network 1430 to obtain information about the mobility status of the terminal from which data are received and includes data processing capability to determine the most appropriate location for storage of the data. For example, if the core network 1430 indicates that the terminal 1440 is fixed, the backup application 1410 may decide to store the data locally. Therefore, in the event that it is required to provide the data back to the terminal 1440 (i.e. perform a data restore), the data can be transmitted efficiently to the terminal 1440 without consuming the capacity in the backhaul links between the access node 800, gateway 802 and core network 1430.

If it is indicated that the terminal 1440 moves within a small geographical area, the information provided by the core network 1430 may be used by the backup application 1410 to calculate which access nodes serve the terminal 1440 during its limited geographical movement. The backup application 1410 may then make available a copy of the data to the respective backup application 1410 (and associated local store) at each relevant access node. The entire data may be copied or a portion of the data copied.

The physical location in which the data are stored may be selected in dependence upon the registered billing address of the user of the terminal 1440, the available storage resource at each storage location, the typical usage patterns and movement patterns of the mobile terminal 1440.

Any data held by the backup application 1410 of an access node 800 may also be copied to the backup application 1410 of a gateway node 802 and/or the central backup server node 1420 in the core network 1430. Therefore, in the event of a failure of the access node 800, the data may be retrieved from the gateway node 802 or the central backup server node 1420 (albeit at the cost of consuming backhaul data transmission resources).

The data provided by the mobile terminal 1440 and stored by the backup application 1410 at its local store and/or the central backup server node 1420 may subsequently be provided to the terminal 1440 in order to restore that data to the terminal 1440 in the even that the data becomes lost or the terminal 1440 itself is damaged or lost.

The backup application 1410 may select which data are stored in local storage and which data are stored in the central backup server node 1420. For example, data more likely to be required frequently by the terminal 1440 may be stored locally, whereas data that is unlikely to be required frequently may be stored in the central backup server node 1420.

Data that is backed up from the mobile terminal 1440 may be retained in the mobile terminal (in the store 1445) or may then be deleted from the terminal 1440 in order to free up storage space. The user may determine which data are retained on the terminal 1440 and which data are deleted. Alternatively, this decision may be made automatically by the application 1450 in dependence upon criteria set by the user and/or the network.

Each user has a user specific context associated therewith. The user specific context includes a list of locations at which the user's data are stored and any security credentials for each of the storage locations where the content is stored, and security credentials for the user's mobile terminal 1440. The user specific context may further include a list of file names and content descriptions relating to the data. The user specific context allows any backup application 1410 to determine the location or locations at which any user's data are stored, and provides sufficient information to allow the retrieval of that data. The user specific contexts are accessible to the backup applications 1410 and the central backup server node 1420. The user specific contexts may be stored in the core network 1430 or at any other suitable location. The information in the user specific contexts in maintained and updated by the relevant backup application(s) 1410 and/or the central backup server node 1420.

In the event that the mobile terminal 1440 requires data to be restored thereto, an appropriate request is sent via the base station with which the terminal 1440 is registered. This request is passed to the backup application 1410 of the access node 800 associated with the base station. The backup application 1410 initially determines whether the data are available in its local store. If the data are not available in the local store, then the user specific context is obtained.

This provides the relevant location, security credentials, file name and content descriptions that allows the data to be retrieved by the backup application 1410 and restored to the terminal 1440.

Data may be transmitted directly between access nodes 800 either wirelessly or by a fixed (cable) link, or may be transmitted via one or more gateway nodes 802 and/or the core network 1430.

Because the access node associated with the base station with which the terminal 1440 is registered is in the radio access network close to the terminal 1440, the backup application 1410 is able to receive from soft nodes 702 and network functions 704 parts of the platform 700 information relating to the radio conditions and terminal 1440 location. The location data may be calculated from GPS data provided by the terminal 1440, and may be calculated by another suitable mechanism, such as cell triangulation or calculating the time that it takes for a transmitted data packet to be acknowledged by the terminal 1440. Various other location determining the arrangements are known to those skilled in the art that will be suitable for implementation by the backup application 1410.

Data relating to the movement of mobile terminals 1440 may be provided to the core network 1430. This data may be used by the central backup server node 1420 to predict the future locations of mobile terminals. This prediction information may be used to control in which local stores data relating to that terminal 1440 are stored. Data may be provided to an appropriate local store based on the prediction of the terminal 1440 being served by the access node 800 with which that local store is associated, so that the backup application 1410 of that store is able to provide that data efficiently to the mobile terminal when it reaches the predicted location.

Data transmitted between the access nodes 800/gateway nodes 802 and central backup server node 1420 may be transmitted at the times selected by the backup application 1410 and/or the central backup server node 1420. The times may depend upon the measured or predicted availability or communication capacity between those nodes. For example, the data may be transmitted in the early hours of the morning when there is significant spare communication capacity. Advantageously, this means that during peak times, the communication capacity is available for other types of communication.

Preferably, data from the terminal 1440 is backed up incrementally. That is, only when there are changes or additions to the data are those changes/additions provided to the backup application 1410. This is in contrast to backing up the whole of the data, including those parts which are unchanged.

This makes more efficient use of the available communication resources.

Similarly, when data are restored to the terminal 1440, only those parts of the data that are required are restored, rather than the entire data associated with the terminal 1440. In some circumstances it will be desirable to backup and/or restore the entire data for the user, and this is also possible.

The user of the terminal 1440 and/or the backup application 1410 may select only certain data that is required to be backed up. For example, some data may be selected as not sufficiently important to require backing up.

The user of the terminal 1440 and/or the backup application 1410 may prioritise data requiring backup. For example, data regarded as most important (such as contact information) may be backed preferentially to other less important data if there are limited communication resources or storage resources allowing backup of data. Also, higher priority data may be backed up more frequently than lower priority data.

The local store associated with a backup application 1410 may be regarded as a temporary store in some situations, where data are temporarily held before transmission to the central backup server node 1420. On the other hand, where it is determined that the data should be held on the local store, the data will be retained at the local store in long term or permanent storage.

In event that it is required to restore data to the terminal 1440, the backup application 1410 of the access node 800 serving the terminal 1440 will determine the most appropriate time to transmit that data. This will depend on the criteria mentioned above. Higher priority data may be restored earlier than lower priority data. The local store associated with the backup application 1410 temporally stores data destined for the terminal 1440 prior to transmission to the terminal 1440. For example, backup data obtained from the central backup server node 1420 may be held in the local store until the backup application 1410 determines that it is appropriate to transmit this to the terminal 1440.

The backup application 1410 or central backup server node 1420 may consolidate data relating to a particular user that is distributed over a plurality of local stores and the central backup server node 1420 into a single store -either a single local store or the central backup server node 1420. Also, the application 1410 or central backup server node 1420 may move data relating to a particular user from one storage location to another storage location, in dependence upon the circumstances. For example, if a user changes their billing address or movement patterns, the storage location may be changed so that it is at a geographical location likely to be closer to the user. The data may also be moved in dependence upon the type of access technology used to access the data.

Although the data stored in the stores are referred to as backup data, it should be understood that the data in the stores may be accessed, consumed and manipulated directly other than by using the terminal 1440. For example, the data may be accessed by a user using their personal computer and accessing the data via the internet.

According to the embodiment, data may be synchronised between a mobile terminal 1440 and a backup store. In this way, the same data may be present on both the mobile terminal 1440 and on one or more backup stores. If the data are changed on the mobile terminal 1440 or on the backup store, then the change may automatically be made to the other of the mobile terminal 1440 and the backup store in order to keep the data identical. The data may be changed to the backup store, for example, by the user accessing this data not via their terminal 1440 but via a different mechanism, such as a personal computer connected to the internet.

The backup data that are transmitted while the terminal 1440 is moving around the radio access network will be received by different base stations, associated with different access nodes 800, as the terminal 1440 is handed over between base stations. The backup application 1410 of a selected access node 800 (for example the access node 800 on which the backup session was initiated) is operable to retrieve the data transmitted to other access nodes (by direct communication between the access nodes 800 or by the data being sent via one or more gateway nodes 802 and/or the core network 1430. This controlling backup application 1410 is operable to assemble the backup data and to then determine whether it should be stored locally in the store associated with the controlling backup application 1410 or whether it should be stored at another local store associated with another access node or in the central backup server 1420.

An example of the process for backing up data of a mobile terminal 1440 will now be described with reference to the flowchart of Figure 13.

At step A data communication session is initiated between the terminal 1440 and the base station associated with the relevant access node 800.

At step B the access node 800 determines whether the terminal 1440 is operated in its home network or whether it is roaming. If it is determined that the terminal 1440 is roaming, the backup of data is not performed.

On the other hand, if it is determined at step B that the terminal 1440 is in its home network, then at step C it is determined whether backup decision criteria are met. The criteria may include, for example, the availability of communication or storage resources to receive and store the data for backup.

The criteria may also include the type of user -the type of subscription that the user has with a cellular network -and identified by the IMSI. Any other decision criteria may also be applied, such as the type of data requiring backup.

For example, if the communication capacity available is limited, then the backup or large items, such as video files, may not be permitted.

If at step C the backup decision criteria are met, then content filters and policy checks are applied at step D to determine whether the content is in principle suitable for backup locally. For example, the historical movement patterns of the device 1440 may be reviewed to determine whether local backup is appropriate. Also, whether local backup is appropriate may depend upon the type of content.

If at step D it is determined that local backup is not appropriate, then backup is performed at the central backup node 1420 (step E). That is, the backup data will be received by the backup application 1410 and passed to the central backup server node 1420 (after optionally being stored temporally on the local store).

On the other hand, if it is determined at step D that the content is in principle suitable for local backup, it is then determined at step F whether the terminal 1440 has moved. If it is determined that the terminal 1440 has moved, then the data are backed up centrally at step E. On the other hand, if the terminal 1440 has not moved, then the data are backed up locally (step G).

The section headings in this patent specification are for ease of reference and should not affect the interpretation of any part of the patent specification.

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 use of network resources by said mobile terminals, and wherein the control means is operable control to the transfer of data between the mobile terminals and a store.
2. The network of claim 1, wherein the control means is operable to temporarily store data transmitted from the mobile terminals at the radio means, for subsequent transmission to the data store.
3. The network of claim 1, wherein the control means is operable to temporarily store backup data from the mobile terminals, for subsequent transmission to the store.
4. The network of claim 1, 2 or 3, wherein the store is provided at the core, a webpage and/or cloud storage.
5. The network of claim 2, 3 or 4, wherein the control means is operable to transmit the temporarily stored data in dependence upon one or more predetermined criteria.
6. The network of claim 5, wherein the criteria are determined by the control means and include at least one of location of the terminal, priority of the data, network load, time of day, user subscription information, mobility of the terminal, available storage on the terminal and/or temporary store, radio access technology through which the mobile terminal is connected, offered throughput for the terminal, estimated user experience of data transmission, available bandwidth of radio site backhaul transmission and the terminal user activity in other services.
7. The network of claim 1, 2, 3, 4, 5 or 6, wherein the control means is provided at an access node site and/or a gateway site.
8. The network of any one of claims 1 to 7, wherein the data are stored in a plurality of distributed data stores, which are at different geographical locations, the control means being operable to control on which of the stores the data are stored.
9. The network of claim 8, wherein the control means is operable to control when data from the distributed data stores are transmitted to the store, webpage or cloud storage.
10. The network of any one of claims 8 to 9, wherein the control means is operable to control when data from each of the stores are transmitted to the terminal or to another one of the stores.
11. The network of claim 8, 9 or 10, wherein the control means is operable to predict the future location of the terminals and to control on which of the stores data are stored in dependence upon the predicted future location.
12. The network of any one of claims 1 to 11, wherein the control means is operable to predict at least one of the future location of the terminals, radio performance and radio capacity, and to control when uplink data is transmitted to one of the stores by the terminal in dependence upon the prediction.
13. A method of operating 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, the method including using the control means to control to the transfer of data between the mobile terminals and a store.
14. The method of claim 13, wherein the control means temporarily stores data transmitted from the mobile terminals at the radio means, for subsequent transmission to the data store.
15. The method of claim 13, wherein the control means temporarily stores backup data from the mobile terminals, for subsequent transmission to the store.
16. The method of claim 13, 14 or 15, wherein the store is provided at the core, a webpage and/or cloud storage.
17. The method of claim 14, 15 or 16, wherein the control means transmits the temporarily stored data in dependence upon one or more predetermined criteria.
18. The method of claim 17, wherein the criteria are determined by the control means and include at least one of location of the terminal, priority of the data, network load, time of day, user subscription information, mobility of the terminal, available storage on the terminal and/or temporary store, radio access technology through which the mobile terminal is connected, offered throughput for the terminal, estimated user experience of data transmission, available bandwidth of radio site backhaul transmission and the terminal user activity in other services.
19. The method of claim 13, 14, 15, 16, 17 or 18, wherein the control means is provided at an access node site and/or a gateway site.
20. The method of any one of claims 13 to 19, wherein the data are stored in a plurality of distributed data stores, which are at different geographical locations, the control means being operable to control on which of the stores the data are stored.
21. The method of claim 20, wherein the control means controls when data from the distributed data stores are transmitted to the store, webpage or cloud storage.
22. The method of any one of claims 20 to 21, wherein the control means controls when data from each of the stores are transmitted to the terminal or to another one of the stores.
23. The method of claim 20, 21 or 22, wherein the control means predicts the future location of the terminals and controls on which of the stores data are stored in dependence upon the predicted future location.
24. The method of any one of claims 13 to 23, wherein the control means predicts at least one of the future location of the terminals, radio performance and radio capacity, and controls when uplink data is transmitted to one of the stores by the terminal in dependence upon the prediction.
25. A mobile telecommunications network substantially as hereinbefore described with reference to and/or as illustrated in any one of or any combination of figures 12 to 13 of the accompanying drawings.
26. A method of operating a mobile telecommunications network, substantially as hereinbefore described with reference to and/or as illustrated in any one of or any combination of figures 12 to 13 of the accompanying drawings.*::r: INTELLECTUAL . ... PROPERTY OFFICE Application No: GB111131O.7 Examiner: Dr Andrew Courtenay Claims searched: ito 24 Date of search: 27 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-4, 7, 13-WO 03/037015 Al 16 and 19 (VAN REENEN et al) See figure 1 for example.X 1-4, 7, 13-US 2008/300020 Al 16 and 19 (NISHIZAWA et al) See figures 9 and 13 for example.X 1-4, 7, 13-US 2003/134625 Al 16 and 19 (CHOI) See figure 2.X 1-4, 7, 13-WO 2008/026797 Al 16 and 19 (PAEK) See figure 1 especially.X 1-4,7, 13-U52007/281664A1 16 and 19 (KANEKO) See figure 6 for example.X 1-4, 7, 13-WO 01/60096 Al 16 and 19 (SHEAHAN) Whole document relevant.X 1 and 13 GB 2358556 A (LG INF & COMM LTD) Whole document relevant, especially figure 3and associated description.A -US 2005/068967 Al (TERRY et al) 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 Intellectual Property Office is an operating name of the Patent Office www.ipo.gov.uk *::r: INTELLECTUAL . .... PROPERTY OFFICE 70 Worldwide search of patent documents classified in the following areas of the IPC GO6F; HO4B; HO4L; H04Q; HO4W The following online and other databases have been used in the preparation of this search report EPODOC, WPI, INSPEC International Classification: Subclass Subgroup Valid From HO4W 0024/04 01/01/2009 GO6F 0011/14 01/01/2006 Intellectual Property Office is an operating name of the Patent Office www.ipo.gov.uk