GB2493216A

GB2493216A - Mobile communications network with reduced signalling requirement

Info

Publication number: GB2493216A
Application number: GB1113148.9A
Authority: GB
Inventors: Stephen Barrett
Original assignee: SCA IPLA Holdings Inc
Current assignee: SCA IPLA Holdings Inc
Priority date: 2011-07-29
Filing date: 2011-07-29
Publication date: 2013-01-30
Anticipated expiration: 2031-07-29
Also published as: GB201113148D0; GB2493216B

Abstract

A mobile communications network for communicating data to/from communications devices, the network comprising one or more base stations operable to provide a wireless access interface to communications devices; one or more communications devices operable to communicate packets with the one or more base stations via the wireless access interface; one or more packet gateways operable to transmit user data packets received via the one or more base stations from and/or to the one or more communications devices; and one or more mobility managers operable to send and receive signalling packets for controlling user data communications between communications devices and packet gateways. The one or more mobility managers arc operable, upon reception of a signalling packet from a communications device and comprising user data intended for a destination, to detect that the packet is not associated with any established signalling connection between the one or more mobility managers and this communication device. The one or more mobility managers are operable, responsive to said detection, to transmit the user data comprised in the signalling packet to the destination. Accordingly a short message may be sent (e.g. from a machine type communications (MTC) terminal) in a reduced context or context-less manner in a mobile communications network, thereby reducing the amount of signalling and of context to be required in the network elements.

Description

MOBILE COMMUNICATIONS NETWORK. INFRASTRUCTURE EQUIPMENT, MOBILE COMMUNICATIONS TERMINAL ANI) METHOD

Field of the Invention

The present invention relates to mobile cornniunieations systems for communicating data to/from comimmications devices and methods for communicating.

Background of the Invention

Third and fourth generation mobile telecommunication systems, such as those based on the 3GPP defined UMTS and Long Term Evolution (LIE) architecture are able to support more sophisticated services than simple voice and messaging services offered by previous generations of mobile teleconununication systems.

For example, with the improved radio interface and enhanced data rates provided by LTE systems, a user is able to enjoy high data rate applications such as mobile video streaming and mobile video confercncing that would previously only have been available via a fixed line data connection. The demand to deploy third and fourth generation networks is therefore strong and the coverage area of these networks, i.e. geographic locations where access to the networks is possible, is expected to increase rapidly.

The anticipated widespread deployment of third and fourth generation networks has led to the parallel development of a class of terminals and applications which, rather than taking advantage of the high data rates available, instead take advantage of the robust radio interface and increasing ubiquity of the coverage area. Examples include so-called machine type communication (MTC) applications, which are typified by semi-autonomous or autonomous wireless communication terminals (i.e. MTC terminals) communicating small amounts of data on a relatively infrequent basis. Thus the usc of an MTC tcnninal may differ from the conventional "always-on" use case for conventional LTE terminals. Examples of MTC terminals include so-called smart meters which, for example, are located in a customer's house and periodically transmit information back to a central MTC server data relating to the customers consumption of a utility such as gas, water, electricity and so on. In the cxamplc of a smart meter, the meter may both receive small data transmissions (e.g. new price plans) and send small data transmissions (e.g. new reading) where these data transmissions are generally infrequent and delay-tolerant transmissions. Charactetstics of MTC terminals may include for example one or more of; low mobility; nine controlled; time tolerant; packet switched (PS) only; small data transmissions; mobile originated only; infrequent mobile terminated; MTC monitoring; priority alarm; secure connection; location specific trigger; network provided destination for uplink data; infrequent transmission; and group based MTC features (for example: group based policing and group based addressing). Other examplcs of MIC terminals may include vending machines, "sat nay" terminals, and security cameras or sensors, etc. Mobile networks developed recently are generally well adapted to high-rate and high reliability services and may not always be well suited to MIC services.

Summary of the Invention

According to an aspect of the present invention there is provided a mobile communications network for communicating data to/from communications devices, the network comprising one or more base stations operable to provide a wireless access interface to communications devices for communicating packets and one or more mobility managers operable to send and receive signalling packets fbr controlling user data communications between conijnwiications devices and packet gateways. The one or more mobility managers are operable, upon reception of a signalling packet from a communications device and comprising user data intended for a destination, to detect that the packet is not associated with any established signalling connection between the one or more mobility managers and this communication device. The one or more mobility managers are operable. responsive to said detection, to transmit the user data comprised in the signalling packet to the destination.

In some embodiments the mobility manager may be configured to set up a temporary mobility manager context for transmitting the user data to the destination. For example, the mobility mnager may be operable to discard the temporary mobility manager context after a predetermined number of packets have been exchanged with the communications device, the signalling packet being included in the number of packets, In other examples the temporary mobility manager context may be associated with a timer; and, upon expiry of the timer, the temporary mobility manager context may be discarded.

According to another aspect of the present invention there is provided a mobile communications system for conimurneating data to/from communications devices, the system comprising one or more base stations operable to provide a wireless access interface to communications devices; one or more communications devices operable to communicate packets with the one or more base stations via the wireless access interface; one or more packet gateways operable to transmit user data packets received via the one or more base ) stations from and/or to the one or more communications devices; and one or more mobility managers operable to send and receive siia1ling packets for controlling user data communications between communications devices and packet gateways. The one or more base stations are operable, upon reception of a signalling message from a communications device and comprising user data intended for a destination, to detect that thc message is not associated with any established signalling connection between the one or more base stations and this communication device. The one or more base stations are operable, responsive to said detection, to fransmit the user data comprised in the signalling message to the destination and via the one or more mobility managers.

The one or more base stations being operable to transmit the user data may for example comprise the one or more base stations being operable to set up a temporary base station context for transmitting the user data to the destination. For example, the one or more base stations may be opei-able to discard the temporary base station context after a predetermined number of messages have been exchanged with the communications device, the signalling message being included in the number of messages.

Also, the one or more base stations being operable to set up a temporary base station context may comprise the one or more base stations being operable to associate the temporary base station context with a timer; and, upon expiry of the timer, to discard the temporary base station context.

Accordingly, embodiments of the present invention can provide for a short message to be sent in a reduced-context or context-less manner in a mobile communications network, thereby reducing the amount of signalling and of context to be maintained in the network elements.

Further aspects and features of the present invention are defined in the appended claims and include a mobilily manager element, a base station, a communications terminal and methods.

Brief Description of the Drawings

Example embodiments of the present invention will now be described with reference to the accompanying drawings in which lilce parts have the same designated references and in which: Figure 1 is a schematic block diagi-am of a mobile communications network according to the LTE standard; Figure 2 illustrates an example of a path followed by a message sent by a terminal in a conventional network; Figure 3 is an illustration of transitions between EMM and ECM states in a conventional LTE network; Figure 4 is an illustration of a possible call flow corresponding to Figure 2; FigureS is a schematic illustration of Figure 4; Figures 6 to 10 are schematic illustrations of a call flows associated with the communication of a short message; Figure 11 is an illustration of a possible path for sending a short message; Figure 12 is another illustration of a possible path for sending a short message; Figure 13 is an illustration of a possible protocol stack for sending short messages; Figure 14 is an illustration of another possible protocol stack for sending short messages; Figure 15 is a schematic block diagram of a parts of a mobile communications network according to the LTB standard shown in Figures 1 and 2 illustrating a change of affiliation of a mobile communications terminal from one base station to another; Figure 16 is schematic block diagram of a mobility manager shown in Figure 15; Figure 17 is an iilusti-ative representation of a call flow process for delivering a. down link data packet according to one example of the present technique; Figure 18 is an illustrative representation of a call flow process for delivering a dow-n link data packet according to another example of the present technique; Figure 19 is an illustrative representation of a call flow process for delivering a down link data packet according to a further example of the present teehnique Figures 20 to 23 provide illustrative arrangements of states which a mobile communications tenninal can adopt when operating in accordance with the present technique; Figure 24 is a schematic illustration of a path of packets through elements of the mobile communications network for both a conventional RRC connected state and an RRC messaging connected state in accordance with the present technique; and Figure 25 is a table illustrating a ielationship between the RRC messaging connected leashedlunleashed states and the ECM idle, ECM messaging connected and the ECM connected states.

Description of Example Embodiments

The example embodiments will be generally described in the context of a 3GPP LTE architecture. However, the invention is not limited to an implementation in a 3GPP LTE architecture. Conversely, any suitable mobile architecture is considered to he relevant.

Conventional Network Figure 1 pi-ovides a schematic diagram illustrating the basic fimctionality of a conventional mobile telecommunications network. The network includes one or more base stations 1 02 (one base station represented) connected to a serving gateway (S-GW) 103 for traffic in the user plane and to a Mobility Management Entity (MME) for signalling in the control plane. In LYE, the base stations are called e-Node]3, which are referred to in the following description as cNB. Each base station provides a coverage area 103 within which data can be communicated to and from mobile terminals 101. Data is transmitted from a base station 102 to a mobile terminal 101 within a coverage area via a radio dowtiink. Data is transmitted from a mobile terminal 101 to a base station 102 via a radio uplink. The core network, comprising the MME 105, the S-GW 103 and the PDN-Gateway (P-GW) 104, routes data to and from the mobile terminals 101 and provides thnetions such as authentication, mobility management, charging and so on. The P-GW is connected to one or more other networks, which may for example include the internet, an IMS core network, etc. in the illustration of Figure 1, connections on the user plane have been represented with a plain line while connections on the control plane have been represented with a dashed line.

Figure 2 illustrates an example of a path followed by a message 1 30 communicated by a mobile terminal 101. Tn that example an MTC terminal 101, wishes to send the message to a destination 120, the destination being reachable via the inte met. In this example. a destination device is represented as a computer. However the destination 120 could be an element of any suitable type where the element can be addressed by the mobile tenninal 101.

For example, the destination device 120 may be another terminal, a personal computer, a server, a proxy, or an intermediary element (to a final destination).

The following description provides a summary explanation of an example of operation in which a mobile terminal communicates the message 130 via an LTE network, which is helpfUl in appreciating some aspects and advantages of the present technique.

Tn order for the mobile terminal 101 to send data to a destination, an EPS bearer between the terminal 101 and the POW 104 is set up, the EPS bearer being partially carried over a GTP tunnel between the eMB 1 02 and the SGW and another GTP tunnel between SOW and POW 104, as illustrated in Figure 2. As the message 130 is carried to the destination device, it is sent from the terminal 101, at a first end of an BPS beaTer to the eNB 102 (step 1), then to the S-OW 103 (stern 2) and then to the P-OW 104 (step 3), at the other end of the BPS bearer. The F-OW 104 then forwards the message 130 to the destination 120 (step 4).

Fiaure 3 illustrates the various transitions between the four possible combinations of ECM states (connected or idle) and EMM states (registered or unregistered) as defined in the LTE standards for a terminal with a view to illustrating how terminals' connections are managed. The acronym ECM stands for "EPS Connection Management" and the ECM state generally indicates whether the terminal has a Non-Access Stratum (NAS) connection set up with the MME. In LIE, as the terminal connects to the MME and switches to BcMcomiected, it also sets up an EPS bearer, that is, a data connection to the P-OW via the S-OW, Also, as the terminal switches from ECMeonnected to ECM_idle, the BPS bearer is torn down, and all Si and RRC connections are released. The acronym BMM stands for "BPS Mobility Management" and the EMM state generally indicates whether a terminal is attached to the network. When the terminal is in EMM unregistered, it may for example be turned off, out of coverage or connected to a different network. In contrast, when a terminal is in BMM registered, it is attached to the network and, as such, it has an IP address and a NAS security context in the MME. It may or may not have an BPS bearer set up, hut in any case, it has some context associated with it in the MME (e.g. NAS security context) and in the P-OW (e.g. the lP address). In addition the MMB will know in which tracking areas the UE is located, The four ECMIEMM states and the transitions between them is described next.

Ihe mobile terminal 101 is assumed to start front a state 153 iii which the mobile terminal 101 is not connected to the network. In the state 153, the terminal is in EMM unregistered and ECM idle states. From this state, the terminal can attach to the network to be in EMM registered and ECM connected states. However, in order to attach, the terminal cannot switch to EMM_registercd if it has not switched to BCM connected first.

In other words, starting from state 153, the terminal cannot go to states 152 or 151 and it has to go to state 154 first. Therefore, as illustrated by arrow 161, a terminal in state 153 can attach to the network by first switching to ECM connected and then to BMM registered. As a terminal starts an attachment procedure from state 153, the terminal moves from a state 153 where it does not have any connection to a state 15! where it has a NAS connection to the MME, an IP address allocated by the P-OW, and a BPS bearer to the P-OW via the c-NB and the S-OW.

Transitions between states 151 and 152 occur when a data connection (BPS bearer) is set up (164) or whcn all data connections have, been released (165). Generally, transition 165 occurs when the user had an BPS bearer active and has not been using the bearer [or a certain time. The network can then decide that the terminal no longer needs an BPS bearer and thus release all the corresponding resources and switch the terminal to ECM idle. Transition 164 generally occurs when the terminal has not been using any BPS bearer (see for example the discussion on transition 164) and now has data to send or receive. An EPS bearer is then set up for this terminal and it is switched to BCM connected. Whenever the terminal is EMM registered, regardless of the BCM states, the terminal will have an IP address that can be used to reach the terminal, in other words an IP context remains active even if no actual EPS bearer is currently active (e.g. state 152).

If the terminal detaches from the network, for example because it is turned off, moving to a different network, or for any other reason, it will switch from any state it is into state 153, releasing any outstanding BPS bearer or context that was previously maintained for the terminal, via transitions 162 or 163.

As can he understood, the state 154 where the terminal is in ECM connected and in EMM unregistered is a transient state and the terminal does not generally remain in that particular state. A terminal in that state is either a terminal switching from state 153 (detached and inactive) to state 151 (attached and active) or a terminal switching from state 151 to state 153.

RRC states are also provided to reflect the status of the RRC connection between the terminal and the eNB (RRC connected and RRC idle). Under conventional operation cotditions, the RRC states correspond to the ECM states: if the terminal is in ECM connected, it should also be in RRC connected and if it is in ECM idle, it should also be in RRC idle, Discrepancies between ECM and RRC states may occur for a short pedod of time as a connection is being set-up or torn-down.

Figure 4 illustrates an example of the messages exchanged for setting up a connection from the terminal 101 to the destination 120, for using the connection to communicate data and for releasing the connection after the communications between the tenninal 101 and the destination 120 have been completed. The call flow of Figure 4 can he schematically divided into four steps A-D. Before step A starts, the terminal 101 is in the ECM idle state which means that the terminal 101 is not currently communicating. At step A (messages 1-3) an RRC connection is set up between the terminal 101 and the eNB 102 for controlling communications between the terminal 101 and the eNB 102. Once this RRC connection has been successifilly established, at step B (messages 3-12), the terminal 101 can establish a NAS connection with the MME 105. Following this NAS connection request from the terminal 1 01 to the MME 105, the MMB sets up a connection (e.g. BPS bearer) between the terminal 101 and the P-OW 104, via the S-OW 103 and the eNE 102, and controls this connection. Although they have not been represented here. messages may also be sent to the P-OW 104, for example from the S-OW 103, for setting up the connection (e.g. BPS bearer) at the P-OW 104, for example the OTP tunnel and EPS bearer. At the end of step B, the terminal 101 has an EPS bearer set-up and available to send and receive messages and is therefore in the BCM-eonnected state. The call flow of Figure 4 is an illustration and some of the messages may vary, for example depending on the EMM state before step A. For example, the terminal may he in EMM unregistered state and switch to BMIVI registered during step B, or may already he in EMM registered before step A starts.

Once this connection (e.g. FF8 bearer) has been set up, the terminal 101 can use the connection to send the message 130 to the desfination 120 (step C). In the example illustrated in Figure 4, the message 130 sent via messages 13-16 and is followed by an acknowledgement message to confirm that the message 130 has been received by the destination 120 and/or its final destination. In other example, messages 13-16 may not be followed by any aclatowledgement messages as this is likely to depend on the protocol used for sending the message 1 30. The scenario shown in Figure 4 may be applicable where an application layer protocol running over UDP requires an acknowledgement to be sent..

At a point in time after completion of step C, the resources are released (step D). Step D could happen at any time after step C, for example just after message 20, or at a later point in time, for example after the terminal 101 stopped communicating for a predetermined time.

The aim of step D is to release all unused connections, that is, to release the NAS connection between the MME 105 and the terminal 101 (also leading to the release of resources such as the OTP tunnel between S-OW and eNB and the FF8 hearer), and to release the RRC connection between the tennina.l 101 and the eNB 102. Again, depending on whether the terminal 101 should remain in EMM registered after step I) or should switch to EMM unregistered, the call flow for step D is likely to be affected. For example, the terminal 101 may remain in EMM registered if the terminal simply releases the RRC connection, NAS connection and BPS bearer because it has been inactive for too long, or the terminal 101 may

Q

dc-attach from the network and switch to EMM unregistered (for example following a handovcr to a GSM network).

In the event that the terminal 101 has to send and/or receive large amount of data, this connection method can be efficient in setting up a high-throughput connection to the P-OW for transmitting such data. It is however based on the exchange of a large number of signalling messages between different parties and the setup of a large number of advanced connections (RRC. NAS. FF5, etc), which may render the system inefficient if the terminal's transmission is actually a brief and small transmission. which is likely to be the case for an MTC type applications. Furthermore. MTC type applications are likely to require reduced ffinctionality in comparison to conventional mobile terminals, in order to reduce the cost of producing such devices. This is because it is envisaged that MTC devices will he more ubiquitous and utilitarian then conventional mobile terminals and therefore should be less expensive to produce in order to be attractive to usc mobile communications networks to transmit and receive data. Accordingly, the present technique aims to provide an advantage of adapting conventional mobile communications techniques, particularly in respect of data communications in order to reduce a complexity and therefore a cost of implementing mobile terminals which use the techniques as provided by an adapted mobile communications network. This is because recent networks, including LTE networks, have bccn designed for high-capabilities and high-mobility terminals and, as a result, they usually provide for the setup of a high-speed high-reliability connection with an advanced mobility management with a view' to supporting terminals potentially transmitting large amount of data while moving.

However, in the case of a terminal that is not moving as much as a personal phone and/or transmits only small amount of data on a relatively infrequent basis, the amount of signalling and of mobility tracking required for the termina.l to conmmnicate may be excessive. In particular, it may be excessive compared to the sometimes low level of service that may be acceptable for this type of terminals. For example MTC tenninals are more delay-tolerant than a human-to-human terminal, arc less likely to move and/or to change cell during transmissions and usually send or receive small amount of data.

It may therefore he desirable to provide ways to improve an efficiency of the network for transmitting small messages and/or MTC communications. The following sections provide different example techniques which font aspects and features of the present technique.

Tramsnissiou of Short Messages lii LTE, SMS can currently be supported in two ways. In the first method the short message is conveyed via an Application Server (AS), called an IP Short Message Gateway (IP-SM-GW), in the IMS core which provides an inter-working thnction into the legacy SMS nctworlc. For example, when the terminal wishes to send a SMS in LTB, it will then set-up an EPS hearer as discussed above and will send the SMS through the EPS bearer and to the IMS core's IP-SM-GW. Likewise, if the terminal is to receive a SMS, the network will trigger an EPS bearer set-up and the IMS core's IP-SM-GW will then forward the SMS to the terminal through the BPS bearer. As discussed above, a large number of messages have to he exchanged for setting up and tearing down at least the RRC connection, the NAS connection and the EPS bearer which makes the sending and receiving of infrequent short messages very inefficient. Of course, in the case of a personal phone, the user is likely to t.akc fill advantage of the "always-on" approach and the user may have most of the time an BPS bearer already set-up for other services as well (e.g. emails, web browsing, eu.). Howevcr, MTC terminals may ha.ve to send only one short message and this may bc the only data sent or received for a 1 5 long period of time. In that case, setting-up an RRC connection, a NAS connection and an BPS bearer for sending a short message to the IMS core is very inefficient when using SMS over IMS.

In case the mobile network is not connected to an LMS core or the UE does not have TMS ftnctionalitv, a transition solution has been proposed under the name "SMS over SGs" for transferring a SMS message to the legacy and circuit-switched (CS) core via a SGs interface between the MME and an MSC. Short messages are conveyed between the MME and the UE using control plane protocols including RRC and NAS. Because Packet Switched-only mobile networks haw been designed for high-capacity and high-usage terminals, it is therefore assumed that if a terminal sends a service request, a high capacity data path (e.g. an BPS bearer) will be setup for the terminal's use, not necessarily Ilinited to the use of the service that triggered the service request. This path may be thus used by the terminal for accessing one or more services (e.g. web browsing, emails, etc.) so that the terminal is in "always-on" mode and does not need to set up a new hearer for every new service. Therefore, as the terminal informs the network of its wish to use the mobile network to communicate (for example sending an SMS message) or as the network detects that it has data to communicate with the terminal (for example an SMS message), a data path is set up first before the terminal can start communicating using the mobile network. As a result, according to SMS over SGs, a terminal sending a SMS should first perform a ftrll attachment to the network, including the setup of an RRC connection, NAS connection and an EPS bearer before it sends a SMS to the legacy SMSC in the 2G/30 network, via the TvTh.4E. This failback solution uses a new interface SGs between a MMB and a MSC. As for SMS over IMS, the terminal should first set up all connections, including RRC, NAS and BPS before it can send or receive a SMS.

in other words, because of the way that recent networks have been designed, any time that a terminal has data to send or receive, a flu s data path (for example an BPS bearei) is set up hefbi-e everything, which include setting up other connections as well (e.g. RRC and NAS) and only then data can be communicated. Such an approach may be appropriate for high-throughput and high-usage tenninals but is less suitable for MTC terminals. For example, the amount of signalling compared to the amount of data to he transmitted is disproportionate. Also, the various elements involved all have to maintain connection information called "context" which relate to information that may not be needed in the specific case of MTC terminals having only brief communications. For example, the advanced mobility services provided by the network involve a significant amount of signalling and context which could be reduced with less advanced and more tailored mobility.

Accordingly, an alternative solution for sending short messages is proposed so as to improve the efficiency of the sending of short messages.

It is proposed that short messages be sent without setting up the full RRC and NAS connections and be sent in a signalling packet on the control plane rather than on the user plane. The amount of signalling, context and mobility management can thus he reduced, thereby improving the efficiency of the network for MTC terminals.

Connection and Context for Sendin2 Short Messages ln order to better illustrate the simplification for the connections and contexts, the call flow of Figure 4 can be schematically represented as in Figure 5. At first, a RRC connection is setup between the terminal lOl and the eNB 102. Once this RRC connection has been set up, at time t1, the cNB maintains an RRC context, referred to as Cont RRC, for the duration of the RRC connection. In other words, until the RRC is released, the eNB will maintain this ContRRC. Such a context may for example include a terminal identifier (e.g. C-RNTT), power control settings, mobility settings, security settings, other radio settings or any other information. There will also be a corresponding context in the UE storing similar infonna.tion pertaining to the operation of the radio layers, however, this is not shown in the diagram.

Once the RRC connection has been set up, a NAS connection is set up between the terminal 101 and the MME 105. Once this NAS connection has been set up, at time 1', the MME 105 maintains a context for this NAS connection to the terminal 101, referred to as Cont NAS, for the duration of the NAS connection. Such a NAS context may for example include a terminal identifier, a terminal's TP address, a current eND, mobility settings. security settings, QoS settings, or any other information. As explained above, when the terminal 101 attaches/sets up a data. connection via the mobile network, an EPS bearer is set up in the user plane between the terminal and the P-OW 104, the bearer being controlled in the control plane by the MJvIE I 05. There will also be a conlext in the UE storing UE related information 1 0 pertaining to the NAS protocol. Note that the context Cont NAS shown in the diagram as being stored at the MME, may include more information thait ust that used by or transferred in EPC NAS signalling procedures, it may also contain information pertaining to the session which has been gathered by the MME from for example, an HSS.

Once the RRC connection, the NAS connection and the EPS bearer have been set up, the terminal can send uplink data through the EPS bearer and to the destination. Even though in the example of Figure 5, the terminal 101 sends uplink data, the same connection setup would occur for a downlink or for an uplink and downlink transmission. Likewise the path of an acknowledgement message has been illustrated in the example of Figure 5 even though there may not be any acknowledgement message in other examples. As discussed earlier, this may for example be dependent upon the typc of protocol(s) used for transmitting the data.

As can be seen in Figure 5, Cont RRC and Cont NAS are maintained for the duration of the RRC and NAS connection (i.e. until they are expressly released with a connection Telease message exchange) and, as a result, the RRC context is used for every packet that eNB 101 receives from or sends to the terminal 101. Once the EPS bearer can be released, the NAS connection between the ten-nina! 101 and the MME 105 is released at the same time. As a result, at the time t3 where the NAS connection is released., the context Cont NAS is also released. The tearing down of the NAS connection is followed by a tearing down of the corresponding RRC connection at time t4. Again, as the RRC connection is released, the context Cont RRC is also released.

Generally according to embodiments of the present technique the short messages arc sent in a context-less or quasi-context-less manner. In one example, thc tcrminal may send a message prior to the establishment of any NAS connection between the terminal and the MME, thereby reducing the signalling but also the level of service for the terminal. in another example, the terminal may send a message prior to the establishment of any RRC connection between the terminal and the eNB, thereby also reducing the signalling hut also the I eve! of service for the terminal. In f rther examples, the terminal may send a message after a temporary RRC andlor NAS connection has been set-up, with for example limited features, where the connection is only set up for a predetermined number of messages or for no more than a predetermined number of messages, the number being any number greater than or equal to one. In one example, it may be set up for one message only, in another example it may be set up for the duration of a two-message exchange. It is intended that any suitable combination of the establishment of a partial connection and of the absence of connection establishment for the RRC connection and the NAS connection be considered under the present disclosure. Various combinations are considered below.

The illustration of Figure 6 shows an example where the tenninal 101 sends the message when a temporary and reduced RRC connection is set up for a one-message conversation and where no NAS connection is pre-established.

Tn the example of Figure 6, a temporary RRC connection is setup at t, where the RRC connection is not a conventional full RRC connection but is a connection that is (I) limited to a one-message conversation and (2) only configures the power settings. For example, Access Stratum (AS) security and mobility settings may not be configured even though it would nomtally be configured for a conventional transmission. As a result, the context to be maintained at the eNB can be reduced to contain only a reduced amount of information. For example, it may only comprise a terminal identifier and power settings. The RRC connection setup could rely on a new type of RRC message or on re-using existing RRC messages. For example, the tenttinal 101 could use an existing message and use a flag, field or indicator in the message to indicate that the RRC setup is not a conventional and conplete RRC setup but is only.a limited andlor temporary RRC setup. Alternatively, conventional RRC messages may be used at all stages where for example only the power settings parameters have been indicated in the messages.

The ter inal thcn sends a NAS packet, i.e. a signalling packet, comprising uplink data for the destination 120, and sends this NAS packet to the MIVIE 105. via a message to the eNB 102. Tn the example of Figure 6, the NAS packet is carried in a RRC message, for example in a "RRC Uplink Information Transfer" message, however in other examples it ma.y be carried in another type of RRC message or in a message for a different protocol. As the packet goes through the eNB 102, the eNB can release the RRC context at t2 as this context was only setup for a one message conversation with the terminal 101. After receiving the message, the eNB 102 forwards the NAS packet to the MME 105 at t3. Tn the illustration of Figure 6, t3 has been represented as being after t2. However, the skilled person will understand that t could also be before t, or at the same time as t2. For example, the eNB 102 may first forsvard the NAS packet to the MME 105 first and then only release the RRC context. Even thoLigh this has not been illustrated in the Figures, the NAS packet sent by the eND 102 to the MME 105 is geiera11y sent in a SI-AP message. However, any other suitable protocol may be used for sending the NAS packet to the MME 105.

As the MME 105 receives the NAS packet, it will detect that it does not have any NAS context already set up with the terminal 101 and can then set up a temporary context ContNAS-tentp. In the example of Figure 6, the temporary context is set up for a two packet conversation with the terminal 101. The MME 105 then sends the uplink data to the destination 120. As the context ContNAS-temp has been set up for a two packet conversation, the MMF. 105 maintains the context even after the uplink data has been sent.

In the example of Figure 6, a suecessftLl transmission of the uplink data triggers an acknowledgement message in response. As generally the acknowledgement ("ack") message comes back via the same path as the uplink data, this ack message comes back to the MME 105. The MME then recognises that this message is associated with the terminal 101 and with the context Cont NAS-temp and sends the a.ek packet to the tenninal 101 via the eNB 102 using the context. After the MME 105 has sent the ack message, for example in a NAS packet, to the eNB 102 at time t4, the MME 105 can delete the context Cont NAS-temp as two packets have been exchanged and the context was setup for a two-packet conversation.

In this example, the MME 105 sets up a temporay context for a two message conversation when it receives the NAS packet comprising the data for the destination 120. For the MME 105 to know that it should set up a two-packet conversation context, as opposed to for example no context, a one-packet conversation context, etc., various solutions may be used.

In one example, the MME 105 can always set up a two-packet conversation context, i.e. the MME may not have any decision making capabilities in respect of the context. This may, for example, he well suited to an environment where only MTC short messages arrive at the MME 105 without any prior NAS connection setup and where it is known in advance that such messages are sent in a two-message conversation (e.g. message and acknowledgement).

in another example, the MME may have some higher-layer(s) capabilities and may for example be arranged to identi' the protocol above the NAS layer (or the relevant layer for termina.1-MME direct communications), andlor to reco rise some information in this higher layer protocol. For example, the MME maybe able to detect whether the content of the NAS packet is transported in a. short message protocol, and to detect whether the content of the NAS packet relates to a short message (e.g. first part of the conversation) or to an acknowledgement (e.g. second part of the conversation), in another example, the NAS packet may include a flag or an indication obtained from higher layer(s) (e.g. from a short messaging protocol layer) which indicates if and how a context should be set up. For example, to achieve the two-packet conversation context of Figure 6, the NAS packet might include an indicator set to the value two to indicate that the MME 105 should expect a two packet NAS conversation.

As the NAS packet arrives from the MME 105 to the eNB 102, the eN B can then detect that it is not associated with any RRC connection or context lot the terminal 101 and, at time t5, it sets up a limited/temporary RRC connection for sending a mcssagc comprising the NAS packet, i.e. for a one-message conversation. In the cxample of Figurc 6, t4 has been 1 5 shown as being before t5, however, in some examples, t5 could in fact he before t4. Once the temporary RRC context has been set up, the eNB 102 forwards the NAS packet compnsing the acle message to the terminal 101. For example the NAS packet may he carried by a RRC message, or by a message of any other protocol 1 ower than NAS.

Once the RRC message has been sent to the terminal 101, the eNB can then discard the temporary context at a time tç, as the one message conversation has been completed.

hi the example of Figure 6. the terminal does not have to set up a data path in the user plane for sending its message. Therefore a significant amount of signalling and set up can thereby he avoided, &1so, the terminal can send the message before any conventional connection or context is setup at the eNB 102 and MME 105. In this particular example, the MME 105 does not have any context or connection set up for terminal 101 when it receives the message.

Therefore the amount of signalling and of context can be reduced. by being set-up as the message arrives, rather than prior to sending any message.

In the example of Figure 6 where radio layer context information is stored in the eNB during a temporary radio connection, radio layer infonnation may also he stored in the UB, this is not shown in the diagram. The UE may also store information of relevance to the NAS protocol such as security algorithm related information, this information may be stored during and between short message transfers, if any such information is required to be shared with the MME NAS protocol then this can be conveyed by the communications terminal to the MME along with the message carrying the applicalion packet. Information stored in the MME context Cont NAS-temp may also include information gathered from other sources than the communications terminal via the NAS protocol, for example it could include routing or security inform ati on gathered from the HSS.

As a result the complexity of sending a short message for an MTC terminal can be reduced and the efficiency of sending short messages can also therefore be improved. For example, the terminal can send a message according to Figure 6 (or Figures 7-10) while it remains in the ECM idle state, and the terminal can then communicate a short message to a remote destination even though a conventional terminal would have to set up RRC, NAS and EPS connections first and therefore would have to be in ECM_eonnected to send a message.

Typically the terminal would have performed an ATTACH to the network and be in BMM Registered state prior to conveying any short messages, which would avoid the necessity for an authentication process and NAS security establishment process with every packet transfer. However, the possibility that the tenninal is also in EMM unregistered state when sending a short message would also be a possibility, particularly where the frequency of short message exchange is very low or where simplified NAS security management processes are utilised. However, as the skilled person will recognise, some conventional mobile network features may be lost in sending a. short message in this manner. For example, if the RRC connection comprises only power control and ARQ related contexts but does not include any mobility or AS security parameters or settings, the mobile network may be unable to provide any AS security or any mobility services to terminal 101. In that case, if the terminal 101 loses connectivity with eNB 102 (for example moves out of range of eNB 102), then no mechanism will be in place for the tenninal 101 to handover to another base station while maintaining a continuity of services during and after the handover. As a result, the terminal 101 may not receive the ack message from the destination and it then cannot know whether the destination has received the short message. This may have to he managed by upper layer protocols (for example a messaging protocol) which may for example detect that the message should he re-sent because the terminal has not received any ack message in response to the first transmission. Therefore while such an approach may he well suited to MTC communications, it may be less suited to conventional mobile transmissions from a convention terminal.

Another example is illustrated in Figure 7. In this example, the MME 105 sets up a one-packet conversation context ContNAS-tenip at time t3, i.e. when it receives a NAS message from a terminal 101 and when this message is not associated with any pro-existing context at the MME 105. This behaviour from the MME 11)5 may for example be a default behaviour which may for example always he used, or may be used unless it is overwritten by a specific behaviour. For example a system may be configured to have the example of Figure 7 as a default configuration and may use the example of Figure 6 when the NAS message comprises an indicator that a two-packet conversation context should be set up.

At time t4, i.e. when or after the uplinic data has been transmitted to its destination, the MME discards the context Cont NAS-temp as the packet of the one-packet conversation has already been received from the terminal 101 (via the eNB 102) and processed.

Likewise, as the acic message arrives at the MME 105 from the destination 120 at time, the MME 105 sets us a thither temporary context Cont NAS-temp' for sending the NAS packet comprising the ack message to the terminal 101 via the eNB 102. As this packet is sent to the eNB 102 for transmission to the tcnninal 101, the MME 105 can discard the context ContNAS-temp' at time t5.

1.5 Then, as the eNB 102 receives the NAS packet, it sets up a temporary RRC connection with the terminal 101 for the purposes of sending the ack message, for example in an RRC message. This temporary RRC connection is also associated with the setup of a temporary RRC context at the eNB 102, which is therefore set up at t7 and discarded at tg. An example of where contextual information Cont NAS-temp may be stored for a short period in the MME as shown in Figure 7 might be where the MME needs to access infhrmation from another entity, such as accessing routing or security information stored in an HSS.A further example is illustrated in Figure 8. In this example, the eNB sets up a temporary RRC context for a two-message conversation, but the eNB 102 sets up this context as the RRC message arrives, rather than after a temporary RRC connection set up a.s in Figures 6 and 7. To elaborate thi-ther, the temporary connection setup of Figure 7 nught include a period whereby channel soundings and channel sounding measurements exchanged so that message transmissions can be made at the appropriate power settings and in the optimum time/frequency resources, In the case of figure 8 transmissions might be made using coimnon channels, where there is no prior train up of power control loops and exchange of channel soundings. In the case of Figure 7 the temporary connection release at the radio layer may be implicit, for example the temporary connection being released immediately that the radio layer ARQ ACK has been received. Also, in the example of Figure 8, the MME does not set up any context and simply forwards the message to the destination. Likewise, as the ack message arrives back from the destination 120. the MME 105 simply forwards the ack message to the terminal 101 via the eNB 102. This can be achieved, for example, with a message that includes information that may usually be found in the context. For example any routing information that may be required for i-outing the ack message back to the terminal 101 may he included in the first message sent by the terminal, so that the destination can then send a message that is routabic by the MME. One example is that the terminal may include its S-TMSI identifier in the message sent to the destination 120, the message might also include the address of the cell under winch the IJE is camped and the address of the destination. The destination 120 can then include some or all of this information in the ack message such that, as this ack message arrives at the MME 105, the MME is able to identify that this message is for the terminal 101 and can then route this a.ck message to the appropriate eNB and then the eNB is able to route the packet to the appropriate terminal 101 in the appropriate cell. 101.

Because in this example the RRC temporary context is a two-message conversation context, as the ack message is sent by the eNB to the terminal 101 at time t,, the eNB 102 can then I 5 delete the temporary context.

in a conventional system during the ATTACH procedure the MME could be loaded up with useful NAS security information. The NAS information could be stored for a predetermined time in the MME between ATTACH and DETTACH. As illustrated in Figure 9 the NAS infonnation could be established once the mobile terminal is switched on, which includes authentication and security which could be maintained indefinitely. In some examples, when communicating an RRC message 140, the communications terminal could establish a temporary context or context update for the communication of the RRC message 1 40 In Figure 9, an example is provided in which the communications terminal 101 sets up a NAS connection with the MME 101 At time tI, the temporary NAS connection is set up and the MME creates a context ContNAS-temp including, for example, the NAS security parameters, which could he after the communications terminal is switched on. In that example, the context is set up for a two-packet conversation. However the context might be set up for a conversation of any number of messages of one or more.

Then the terminal 101 sends the RRC message 140 to the eNB. The eNB detects that the content of the RRC messagc should be forwarded to the MME 105. For example, the eNB 102 can identify that the RRC message is not associated with any existing connection with the terminal 101 and'or with any context for this terminal. In another example, the eND 102 could be arranged to idcnti that the message 140 is not associated with any connection or context and to detect a flag or indicator 142 in the RRC message and would then set up a temporary context. In that particular example, the flag or indicator 142 could be used as a check for the eNB 102 to ensure that the message 140 is intended for the lvll%4E 105. In one example, the eNB 102 could then for example reject an incoming message 140 if it is not S associated with any context and if it does not include the flag or indicator 142. The message of course also includes data 144 which is being communicated to the destiuation device and may also include an indication of the TIMSI 146.

The eNB 102 then forwards the NAS packet to the MME, which then recognises that this NAS packet is associated with the context Cont_NAS-temp. The MME 105 then forwards the message to the destination 120.

As the MME 105 receives the a.ck message back from the destination 120, confirming that the destination has received the short message. The MME 105 recognises that the ack message is for the terminal 101 and is therefore associated with the context ContNAS-ternp.

It sends the ack message to the terminal 101 in a NAS. which may itself be in a Sl-AP message for sending it to the eNB 102. The eNB 102 then transfers the ack message to the tenninal 101 in a message 140.

At time t2, after the two-packet conversation between the MME 105 and the terminal 101 has been completed, the connection can be released and the temporary context Cent NAS-temp can be discarded.

Tn in the example of Figure 10, the terminal 101 sends the short message while no context exists for this message in the eNB 102 or in the IVDVIE 105. Also the eNB 102 and the MME 105 do not set up any context, temporary or not, and they forward the message to the next node in a. context-less manner. The ack message received in return is sent to the terminal 101 in a similar manner. In that particuiar example, the amount of signalling and of context to be maintained can be significantly reduced compared to sending a message in a conventional manner. Of course, some fcatures or services may he lost in doing so, such as sonic security, mobility or session management features. Even though the loss of these features is likely to be considered as unacceptable for a. conventional terminal, they may be acceptable for an MTC terminal at least because the transmissions are shorter, MTC terminals may be less likely to move and/or to change cell during a (brief) transmission and/or because MTC terminals are more delay-tolerant than other terminals (e.g. human-to-human communications terminals) and/or because a higher layer protocol such as that running between destination and UE maybe able to re-instantiate or recover from failed short message transfers.

In the example of Figures 10, as the RRC messages are sent when the eNB does not have any existing context for them. some features provided by a RRC connection establishment may not be provided. For example, the terminal 101 may not have any C-RNTI allocated as this identifier is generally allocated during a RRC connection establishment.

Thus, the terminal may USC and he addressed using the S-TMSI as the identifier. Other identifiers may also be used, for example the IMSI or MSJSDN. Therefoi-e for the example shown in Figure 10, the allocation message used to specilr the resources on which the RRC message can be transferred may include the S-TMS1 or a proxy therefor.

In general, in Figiu-e 6-10, a situation has been illustrated where the temporary contexts (RRC or NAS) are discarded after a certain number of messages or packets of a conversation have been received andior processed. The eNB 102 and MMB 105 may also have timers for discarding the context For example, in the example of Figure 6, the MME might have a timer T03tAs for maintaining the temporary context ContNAS-temp. For example, it may be desirable to discard the context at the timer's expiiy even if the ack message has not been received. This may for instance be preferable in the event that the aek message is lost between the destination 120 and the MMB 105 and thus never reaches the MME 105 or if the nature of operation of any destination server is such that the delay in receipt of the higher layer ACK by the MME may be long. If for exanipi e an ack message is generally received within 0.5s, one might consider that if the ack message has not been received after 3s, it has very probably been lost and is therefore unlikely to arrive at the MME at all, hi that case, one bound for the setting of die COntNAS timer might be 3s.

Alternatively, if the context includes routing information about the last known location of the UE then the timer might be set according to expectations about for how long the routing infonnation is likely to be valid (and whether routing subsequent messages using that information is likely to be successful), This example and the values used in it is purely illustrative, the timer might have any value that is considered to he suitable to a particular situation and/or enviromnent.

Example of Short Messages Infrastructure In order to forward the message to the destination 1 20, adaptations to the infrastmcture and/or protocols may be provided.

Figure ii is a schematic illustration of a mobile terminal, in that exampic MTC terminal 101, sending a message 130 to the destination 120 via the MME 105. At first (step 1), the message is sent by the terminal 101 to the eNB 102, the message being carried in a signalling message (e.g. NAS message encapsulated in an RRC message). Sending this message does not require or trigger the set-up of a data path as would normally be expected in PS networks when sending user data, and (step 2) the eNB, upon reception and identification of the signalling message, forwards the message 130 to the MME 105 in a signalling message.

The MME 105 then sends the message 130 to the destination 120 at SIC!) 3. This illustration is a schematic illustration of a mobile-originated sending of a short message, it does not for example illustrate the specific connection between the MME 105 and the destination 120.

This connection may for example be a direct connection or indirect, going via the Internet or via another route.

Figure 12 is an illustration where the connection is indirect and is via a messaging server 106. For the purposes of illustration, the messaging server will be called "MTC-SC" for "MTC Service Centre". As illustrated in Figure 12, the MME 105 detects that the signalling packet carrying the message 130 is a short message to be forwarded to MTC-SC 106. This detection could be carried out in different ways, for example and as discussed above, the MME 105 could detect the type of message carried in the NAS packet, or the NAS packet may comprise an indicator that this NAS packet actually carries a short message for forwarding to MTC-SC 106. Finally, MTC-SC 106 can transmit the message 130 to its destination 120. This transmission can also be performed in any other appropriate manner.

For example, it can be transmitted directly to the destination, or via a further messaging server and/or a router.

Although this MTC-SC 106 has been represented in Figire 12 as separate from the MME, the skilled person would understand that the separation in the illustration is only logical and for the ease of representation and understanding, and that the MTC-SC may for example physically form part of the MME. In another example, the MTC-SC may he a separate server, for example a standalone server.

Advantageously, this MTC-SC 106 can be used for advanced funetionalities such as store and forward. For example, the server can store an incoming mobile terminated message if the terminal 101 is not attached to the network yet and sends this message a.s soon as it attaches IC) the network. Likewise, if the terminal 101 sends a message to another party that cannot be reached, the messaging server MTC-SC 106 can store the message and forward it when this other party becomes available.

Figures 13 and 14 illustrate two possible protocol stacks arrangement that may be suitable for an arrangement according to for example Figure 11 or Figure 12. In Figure 13, the MME can act as a relay for messages between the terminal (or UE) and the MTC-SC and, in this example, the short messages are carried by a protocol called "Protocol for short messaging" (PSM), This name does not refer to any particular specific protocol and is used for illustrative purposes: PSM may he any existing, modified or new protocol suitable for sending the message to the MTC-SC. In Figure 13, protocols from LTE have bcen used for illusfltive purposes and the skilled person will understand that the invention could also be carried with a different set of protocols. Because in LTE the terminal communicates directly with the MME using a "NAS" protocol, the short message may be carried by a NAS packet so that the short message can be sent to the destination 120 and/or MTC-SC 106 via the MME 105 (via the eNB 102). The MME can then foi'ard the upper layer (relative to the NAS layer) information to the MTC-SC. In the example of Fiaure 13, the protocols used between the MME and the MTC-SC have not been specified and have simply been referred to as P1-P6. In cffcct any suitable protocol and suitable number of protocols (it could for example be more or less than six protocols) for an interface between the MME and the MTC-SC may he used. For example, thc stack may include five main layers such as Ethernet; MAC; IPsec; SCTP; and MTC-AP where MTC-AP is a protocol *for MTC applications (standing for example for "MTC Application Protocol").

With such a protocol stack, a short message 130 can be sent by the terminal 101 in a PSM message, the message itself being sent in a NAS packet, and the packet being sent in a RRC message to the eNB 102. The eNB 102 then forwards the NAS packet in a SI-AP message to the MME 105. After rccciving the NAS packet, the MME 105 can then forward the PSM message comprising (the short message 130) to the MTC-SC for transmission to the destination 120. In the event that the tenninal receives a short message and has to return ai ack message to confinn that the short message was successfully received, the ack message can follow the same path a-s the mobile-originated short message 130 discussed above.

Any PSM message for the terminal 101 (mobile-terminated message) may follow the same path in the other direction as a mobile originated short message. Such a mobile terminated message may for example be a mobile-terminated short message (c.g. the tenninal 101 receives a short message) or an ack message in response to a mobile-originated short message.

The example of Figure 14 illustrates another protocol stack arrangement which may be suitable for an MME that ineludcs short messaging capabilities. In that easc, the MM E may for example process the actual short message 130. It may also not actually process the short message 130 but may for example have PSM-relay capabilities that require that the MME implements some PSM Thnctionalitics.

Some might consider that including PSM capabilities iii the MME 105 may not be preferable as the MME was originally designed to perform only as a signalling node, while other might consider that it might simplify the global arclutecture to have PSM capabilities in the MME 105. The skilled person will be able to identify which arrangement would he preferred in a specific situation. depending on its specific requirements.

Reduced Mobility Mana2ernent for MTC Terminals According to an aspect of the present invention a mobile communications network is configured to provide a reduced mobility functionality to reflect a reduction in a capability of a mobile terminal which might for example be used for MTC type apphcations. The following description and figures provides an explanation of the redLleed mobility functionality in accordance with the present technique.

Embodiments of the present technique can provide a reduced mobility functionality to some mobile terminals, such as those which might be operating as MTC type terminals.

Examples illustrating the reduced mobility functionality are explained as follows with reference to Figures 15 to 25.

Figure 15 provides a schematic block diagram of parts of a mobile communications network which are provided to illustrate the reduced mobility functionality in accordance with the present technique. The parts of the mobile communications network are illustrative of an example of an LTE network as for example illustrated in Figures 1 and 2. In Figure 15 a mobile tenninal 201 communicates a message datagram to or from a source or an anchor base station (eNB) 202. The anchor eNB 202 forms part of a cluster of eNB's 204, 206 which serve to provide a facility for conununicating data to or from mobile terminals 201 via a wireless access interface provided by each of the eNB's 202, 204, 206. hi accordance with a conventional operation the eNB's 202, 204, 206 are connected to a serving gateway (SC) 208 as for example shown in Figure 1. Also connected to the eI'B's 202, 204, 206 is a mobility management entity (MME) 210, Of particular relevance to the present explanation is a message server 212 which is connected to the MME 210. In one example the message sen'er 212 is an MTC-SC referred to in the above explanations.

According to the present teclmique and in relation to the context-less communication explained above, the MME 210 is arranged to provide a. reduced mobility function in connection with the communication of messages to or from the mobile terminal 201. To this end, the MME 21 0 is alTanged to store a current location of a mobile terminal 201 until either all outstanding message transfers have occurred or an "routing information freshness timer" has expired. If either of these conditions is met then the routing contexts for the mobile terminal in the M_ME are removed. According to one aspect the mobility management functionality for MTC terminals will thcn have to establish a location of the communications terminal when this has changed attachment from one base station to a second base station.

Thus the mobility management solution as proposed in accordance with the present technique can be applied to one or both of the following messaging scenarios: a NAS signalling message exchange iii which most NAS messaging exchangcs consist of multiple messages exchange between a mobile terminal and an MME 210. These message exchanges should typically be completed in a short period of time.

Short message exchange, short messages are transferred in a NAS container in which thc short message exchanges arc expected to consist of two steps that is a transfer of the message from the originator entity (eg MTC-SC) followed by an acknowledgement from the recipient cntity, for example the mobile communication terminal 201.

As an illustration of a reduced mobility management functionality, Figure 15 illustrates that the mobile terminal 201 which is currently attached to an eND 202 changes affiliation to a second eNB 206. In the following description the first eNB 202 will be referred to as the anchor eNB whereas the second eNB 206 will be referred to as the second eNB or the target eNB. The present technique therefore addresses a technical problem of how to deliver a message to the mobile terminal 201 when the mobile terminal 201 has changed affiliation from onc base station to another.

Conventionally, the communication of data messages or data grains to or from a mobile terminal which changes its affiliation from one base station to another is handled using handover procedures in which the network directs the mobile tenninal to change affiliation in response to link quality measurements reported by the mobile tenninal. The mobile communications netwofic then arranges to communicate data from a new target base station or eNB 206 and stops communicating from the source or first base station 202, However the present technique provides a simplification for mobility management which does not include a full handover procedure which typically requires a significant amount of signalling to configure mcasurements, send measurement reports, prepare target base station, command handover, reconfigure tunnels and release resources from the source base station. As explained above, if the amount of data communicated to or from the mobile terminal 201 is relatively small then the amount of sialling overhead required to deliver this message would represent a very inefficient use of radio communications resources. According to the present technique therefore it is envisaged that a mobile communication terminal which for example may be operating as an MTC type terminal is pi-ovided with a reduced mobility functionality which may be reflected in a new connection state which will be cxplained below. However the following paragraphs serve to provide an illustration of an example of the present technique in providing a reduced mobility management function.

Figure 16 provides a more detailed view of the MME 210. In Figure 16 a processor 220 is arranged to control thc operation of the MME and includes a data store 222. The processor also receives an input from a clock 224. The processor is connected to a communications protocol slack 226 which serves to implement the various levels of the communications protocol stack which are performed by the MME 210.

In accordance with the present technique the MME 210 is arranged to store a cun-ent location of each of the mobile terminals for which it is responsible within a tracking area served by the MME. However the location of each of the mobile terminals in respect of a base station (eNB) to which they are currently attached is stored in the data store 222 by the processor 220 only for a predetermined period. The eNB to which the mobile terminal is attached is maintained until all outstanding message transfers to a mobile terminal have been completed or until a "routing information fresimess timer" as determined by the clock 224 has expired. At this time the eNB location of the mobile terminal is deleted from the data store 222. Thus as shown in Figure 16 a list 230 of mobile tcnninals within a tracking area served by the MME is stored in a table with the mobile terminal's STMSI and an identifier of the base station eNB-A to which the mobile terminal is attached. In addition a clock value indicating a time at which the location of the mobile terminal was registered 232 is provided within the table. Thus as mentioned above once the mobile terminal has been attached to an eNB for a predetermined amount of lime then the entry in the data store of the current location of the mobile communication terminal is cancelled. In Figure 16 this is illustrated with respect to the mobile terminal identified as UE3.

According to the present technique there is provided a reduced mobility fimctionality to a mobile terminal which might find application in particular with MTC type mobile terminals which are simplified with respect to conventional mobile terminals. Accordingly with the present teelmique fill handover may not be supported. Thus if a mobile tenninal wishes to transfer a message to a destination via, the mobile communications network or receive a message from the mobile communications network as for example a NAS sigualling message or a short message exchange, then handover is not supported. To this end, the mobile terminal may include a further communications state refen-ed to in the description below as a "radio resource communication (RRC) messaging connected" state. in this state the mobile communications network does not support full handover and therefore does not direct the mobile terminal to reattaeh to a new base station for continuing a communications session. Accordingly if the mobile terminal detaches from a first or source base station and attaches to a second or target base station then in accordance with the present technique the message which is to be communicated to the mobile terminal is simply lost. Higher layer protocols can then arrange for the message to be resent to the mobile terminal. To this end, the mobile terminal determines that it should reselect to a target base station and reselects to that base station. The network may be adapted to determine a location of the mobile terminal in order to communicate the message. Examples of detecting that the mobile terminal has reselected to a new target base station and determining an identification of the target base station will be explained in the following paragraphs.

In Figure 17 a message flow diagi-an is presented for operation of an MME 210 in arranging for a message to he communicated to a mobile terminal 201 when the terminal 201 has moved on from a source base station 202 and reselected to a target base station 206.

As shown in Figure 17 and reflecting the situation shown in Figure 15, after the mobile terminal 201 has detached from the first or source base station 202 and reselected the second or target base station 206 the mobile terminal 201 sends a first message Ml to provide a cell update to the source base station 202 to indicate that it will be changing affiliation to the target base station 206. The MME 210 has previously communicated a message N from the mobile terminal 201 to the destination and therefore assumes that the mobile terminal 201 is still attached to the source base station. Accordingly the MME 210 has in its data store a location of the mobile terminal 201 which is that of the source base station 202. Accordingly when the MMF 210 has a message N-x to communicate to the mobile terminal 201 the MME 210 communicates using a message M2 the data packet for communication to the mobile communication terminal 201. However as illustrated in Figure 17 the MMF. 210 communicates the data packet to the source base station or eNB 202.

In message M3 when the source base station 202 attempts to communicate the packet to the mobile terminal 201, that communication fails. However since in message Ml the mobile terminal 201 communicated the cell update to the source base station 202 indicating that it had reselected to the target base station 206, the source base station 202 in message M3.2 communicates the data packet to the targct base station 206. Accordingly the target base station 206 coimnunicates the data packet to the mobile terminal in message M4.

In Figure 18 a similar arrangement is shown to that represented in Figure 17 exccpt that the mobile terminal conununicates its cell update through the target eNB 206. Thus as shown in Figure 18 a mobile terminal 201 sends a message Mb. 1 which includes a cell update to the target base station 206 which advises the target eNB that the mobile terminal is currently attached to the target base station 206. The target base station 206 sends a message Ml0.2 to inform the source base station 202 of an update of the mobile terminals' location by informing the source station 202 that the mobile communication terminal 201 is attached to the target base station 206. lii message Ml 2 the MME communicates a data packet N+x to the source base station 202 because, as with the case shown in Figure 1 7, the MME last communicated a message N from the source base station 202 to the destination and therefore assumes that the mobile terminal is attached to the source base station. However since the source base station 202 has been informed by the target base station 206 that the mobile terminal is attached to the target base station 206, file source base station 202 forwards the data packet to the target base station 206. Accordingly the target base station 206 then communicates the data packet as the message N-! X in a message Ml 4 to the mobile terminal.

In accordance with a further aspect of the present technique the MME may have the prcvious location of the mobile tenninal as attached to the anchor base station 202.

Accordingly with a message M3 1 the MME eonrnrnnicates a data packet providing a message N+x to the anchor base station or eNB 202 for communication to the rnohile terminal. As shown in message M32 the anchor base station 202 attempts to communicate the message to the mobile terminal 201. However the message delivery fails. This is because the mobile terminal has now reselected itself onto the target or second base station 206. Accordingly, the anchor base station triggers paging messages to be transmitted to its neighbouring base stations 204, 206 in order to page the mobile terminal. The base stations which are paged are provided from the anchor base station 202 in a list which is to be used in ease that the message M32 cannot be delivered to mobile terminal in which case it is assumed that the mobil.e terminal has changed its location. This list may contain the same set of ce[ls/eNBs as are in the neighbour list which an eNodeB may anyway store for the purposes of handover control or improving cell reselection performance. Accordingly, as shown in messages M33 the source or anchor eNB 202 communicates a message to the neighbouring base stations 204, 206 to trigger a paging message to he transmitted from those base stations. Since the mobile tenninal 201 is attached to the second base station 206, the second base station 206 detects that the mobile terminal 201 is currently attached to it and responds to the paging trigger message M33 with a message M34 informing the anchor eNB 201 that the mobile terminal is currently attached to it. The anchor base station 202 therefore transfers the packet in a transfer message M35 to the second base station 206 which the second base station 206 then communicates to the mobile terminal 201 in a transfer message M36. Accordingly the data packet providing message N-f X is communicated to a mobile terminal from the second base tO station 206.

hi another example the mobility manager 210 is configured to request from at least one of the mobile communications terminal or the eNB 206 information providing an update of the second base station which the mobile communications terminal has reselected. The information could be provided by the communications tenninai in an RRC message, which is communicated by the communications terminal via the eNB as a a non access stratum message. Thus in one example, the cell update information is provided in a way which is substantially transparent to the eNB. If the eNB does not know the content of the NAS message is, it just forwards it to the MME.

The alternative is that the communications terminal can provide a cell update to the eNB (which may then use the information) as per for example Figures 17 or 18), but in which case additionally the eNB also forwards the cell update to the MME.

In another example the first base station may send the paging message to one or more base stations in a list of neighbouring ba-se stations, which may be provided to base stations in a neighbour list'. The neighbour list' may be 0MG configured or an eNB learnt list of surrounding base stations which communications terminals may hand over or hand off to.

This list is conventionally already available in base stations and is conventionally used for configuring handover measurement reporting, identifying local cells to aid cell reselection.

New RRC Messa2in Connected State As mentioned above, in accordance with the prcsent technique the mobile terminal 201 and the base station to which the mobile terminal is attached 206 can fonn a new state referred to as an RRC messaging connected state which is shown in Figure 20. In Figure 20 an RRC messaging connected state 280 is shown to be one of three states which include an RRC idle state 282 and an RRC connected state 284. The RRC idle state 282 and the RRC connected state 284 are conventional states of the mobile terminal and the base stations which transition between these states in response to whether the mobile terminal is currently provided with a communications bearer for communicating data or not. Thus when in the idle state 282 the communication to or from the mobile terminal is not possible and the eNB is unaware that the UE is camped on it. However in the RRC connected state 284 the mobile terminal is attached to the mobile communications network and is provided with radio comm Linications resources for communicating data.

According to the present technique the mobile terminal 201 and the base station 206 to which it is attached form a new RRC messaging connected state in which only messaging is supported and no user plane can he provided, reduced radio flmctionality sufficient and optimised for a messaging only application is provided for communication to/from the mobile terminal. Furthermore within the RRC messaging connected state 280 there are two sub states referred to as thc RRC messaging connected unleashed state and the RRC messaging is connected leashed state 286, 288 which at-c showing in Figure 21. In the leashed state the mobile terminal is required to update the RAN about changes in tile location of the terminal so that the RAN can route downlink packets to the correct base station to which the terminal is attached. In contrast in the unleashed state the mobile terminal and the base station are not required to update the RAN about changes in the location of the mobile terminal. The leashed state may be supported using conventional network controlled handover. Alternatively the state may be supported using UE controlled cell resciection, which may be augmented with other mobility techniques as have already been described such as liE provided cell update to source or target eNB or anchor eNB triggered paging to find the UEs new location.

The states of the state diagram of the mobile terminal shown in Figure 21 are sunuuariscd as follows:

State descriptions:

RRC Idle o mobile terminal is unknown to the RAN. No contexts associated with that mobile terminal exist in the RAN * No data transfer or signalling transfer is possible in idle mode (except as part of transitioning to another state) RRC Connected mobile terminal is known to RAN, contexts exist within the RAN for that mobile termrnal * Access Stratum security is set up * SRB1, SRB2 and DRB available C-RNTI assigned * 1-landover based mobility management o Transfer of any NAS signalling, short messages or data over an [P connection is possible in this state RRCMessagingconn.ectedUfnieashed o Transfer of short messages and optionally NAS signalling possibic * No SRB2, DRB or AS security is available Preferentially, contexts will be established/deleted in the RAN implicitly as part of the message transfer transaction (not using separate a priori, a. postcriori RRC signalling) Unicashod: ccli roselection mobility provided, UB does not providc notification to network of cell change. This may imply reliance on higher layers such as NAS or PSM to rccovor fl-cm any packel loss that occurs as a result.

* No signalling based SI tunnel re-arrangement.

o Optionally mobile terminal listens to and utilises RAN stack optinfised for messaging and/or MTC, which may include simplified PHY, MAC, RLC.

RRcAJesagingconnectedLeashed o Only iransfer oF short messages and optionally NAS signalling possible * Leashed: mobile terminal/eNB required to update RAN about changes in mobile terminal location, so that RAN can route downlink packets to the correct eNB.

* May use network confrolled handovcr based mobility management: a This means that mobile tenninal location is tracked a.s the mobile terminal moves from cell to cell. handover measurements will be configured, packet forwarding on handover may be supported, eNB may notify MME of cell cliuugc. -o Instead of handover source eNB may act as an anchor and either the UP directly or indirectly provides the anchor eNB with information about cell change or the anchor eNB pages local cells to discover the UE's new location.

* No DRB or AS security is available Optionally mobile terminal listel1s to and utilises RAN stack optimised for messaging and/or MTC Transitions: RRC Idle to RRC_Messaging_Connected Unleashed a Trigger: Short message (or possibly NAS siial1ing to be sent either on uplink or downlink a Realized by: Signalling prior to data transfer or preferentially implicitly as part of packet transmission RRC Messaging Connected Unleashed to Ri? C_Idle * Trigger: One way short message transfer is completed or multi-step message conversation is completed or inactivity timer expires * Realized by: Signalling or implicitly by removal of contexts after message transfer(s) are completed or after inactivity timer expires RRC Messaging Connected Unleashed to RRC Messaging Connected Leashed a Trigger: Frequency of messaging exceeds threshold and/or number of cell changes per unit time exceeds threshold o Realized by: Signalling RRC Messaging Connected Leashed to RR(2_Messaging_Connected_Unieashed o Support for this transition is not critical and is shown as not supported in the diagram.

If activity in RRC Messaging Crnmected Leashed drops below a threshold then a transirion to RRC Idle should be enacted. However, optionally the transition could be supported if frequency of messaging drops below a threshold and/or number of cell changes per unit time drops below a threshold.

RRC Messaging Connected Ulnleashed to RRC Connected * Trigger: This transition could be triggered by the need to set up aji IP pipe or possibly by a need to transfer NAS signalling o Realized by: Signalling RRC Connected to RRC Messaging Connectea Unleashed * Support for this transition is not critical and is shown as not supported in the diagram.

If a mobile terminal is currently engaged in an SMS transfer or a NAS signalling exchange then the system should remain in RRC Connected state, If the system is in RRC_Conneeted and all data transfers have ceased and/or there has been a period of inactivity then a transition to RRC Idle is expected instead.

RRC Messaging Connected Leas hed to RRC Idle Trigger: inactivity timer expires or all outstanding message transfer conversations have completed Realized by: Signalling RRC Idle to PR C'_iVfessaging Connected Leashed a would not be essential to support this transition (hence dotted line).

Trigger: The transition might be triggered if an application was staited for which it was a priori known that only a messaging bearer would he initially required and if it were axlthtionally known that the frequency of messaging, frequency of cell change or link ieliability requirement would be such that a leashed mobility management approach (handover or ccli reselection with cell update) should be supported.

a Realized by: Signalling RRC Messaging Connected Leashed to RRC Connected a Trigger: This transition could be triggered by the need to set up an IP pipe or possibly by a. need to transfer NAS signalling a Realized by: Signalling RRC Connected to RRC Messaging Connected Leashed Tngger: Support for this transition is non-essential. Whether or not the transition should he supported would depend on whether there are efficiencies to be gained by working in RRC Messaging Connected Leashed mode (for example through use of MTC/messaging optin-iised PHY/MAC/RLC/PDCP).

* Realized by: Signalling RRC Connected to RRC Idle * Trigger: Inactivity timer expires * Realized by: Signalling RRC [die to RRC Connected * Trigger: mobile tenninal requires EPS bearer (1? pipe) to be established or possibly required for the transfer of NAS signalling * Realized by: Signalling Note that transition between from/to cell resclection and handover based mobility management within the RR Messaging Connected Leashed state may be triggered when frequency of messaging exceeds/reduces below threshold and/or number of cell changes per unit time exceeds/reduces below a threshold.

An alternative alTangement for including the RRC message in connected unleashed and leashed states is shown in Figure 22. Accordingly a transition between the states and sub states is performed internally within the RRC messaging connected state 280.

According to the present technique the mobile terminal and the base station to which it is attached may transition between the various states shom in Figures 20 dependent on the need to support Thnctionality and whether for example only messaging needs to be supported or whether an IP pipe is required. Within the messaging connected state 280 and depending upon a relative number of packets generated and/or the frequency of cell change, the mobile terminal and the base station may transition between the unleashed and leashed states, the leashed state being used for more frequently generated data packets or higher frequency of cell change than is the case for the unleashed state. Of course where no data is to be sent then the mobile tenninal transitions to the RRC idle state 282.

In a more simplified arrangement a mobile terminal and base station could form the messaging state shown in Figure 23 in which the terminal can only transition to the RRC messaging connected state 280 or the idle state 282 thus providing an even more simplified representation of possible states.

An illustration of a difference between the communication of data packets which is supported for the RRC Messaging Connected state and the RRCCoimected state is illustrated in Figure 24. As shown in Figure 24, for the RRC MessagingConnected state, application packets are communicated to/from the mobile terminal 2200 via an eNB 2202 and MME 2210 fionilto the MTC-SC 2204 whereas for the RRC Connected state data packets are communicated 2212 to/from the mobile tenninal either via the cNB 2202, PDN OW 2216 and S_OW 2212 to/from IP PDN 2214 and/or via the control plane 2200 to/from the MIC-SC.

A schematic block diagram summarising the relative states explained above with reference to Figures 20 to 24 is shown in Figure 25 in association with states corresponding to NAS signalling connections providing communications between the mobile terminal and the MMF. In particular, a new ECM Messaging state is introduced; properties of the state include the following: Only transfer of SMS or NAS messages over the control plane is supported, no user plane is supported.

The last known eNB address of the UE maybe stored and made available for routing of packets which arrive later on during the period while the MME is in this state.

o Nc) SI bearer or tunnels are configured o An RRC Connection may not exist and any radio functionality that does exist may be limited (eg no AS security, no hand over configured) o Period in this state may be very short ° State change from ECM idle to ECM Messaging Connected at the MME may be triggered: o Implicitly by the arrival of a packet within a message transfer transaction.

o State change from ECM Messaging to ECM Idle may be triggered by: o Age of last update of eNB <-> MM F, routing information exceeding some period o Completion of single message transfer, completion of outstanding message transfers within a message conversation and/or completion of all outstanding message conversations o Inactivity tinicr O The MNE may need to page to find the UE's location if no sufficiently recent routing infonnation exists, or if a network initiated message transaction is new.

The UE may optionally he leashed' to the MME, specifically the UE could be configured via signalling to provide the MME with cell updates when the GE changes cell. The decision to invoke this sigualling may be triggered by the quantity of paging messages per unit time exceeding some quantity and/or if the frequency of short message conversations becomes high.

o Stored knowledge of UF location may be inaccurate or more specifically out of date.

This may be dealt with by requiring that higher layers such as NAS or PSM recover from any packet loss which results from the MME forwarding a packet to sn eN B under which the GE is no longer camped. Alternatively the RAN could provide a mobility management solution to prevent packet loss if the MME uses its last known eNB address for routing purposes. for example according to the methods described earlier.

As indicated by the dotted lines in Figure 25, whilst the MIVIE NAS is in ECM Messaging Connected state the RRC state can be variously in RRC Idle or an RRC Messaging Connected state dependent on the radio solution adopted, and as described previously. The ECM Connected state is most commonly associated with the RRC Connected state.

Routing information in the MME concerning which eNB the UE is camped under may be updated by a number of means: * Response to paging performed by the MME Inclusion of routing information in any mobile originated packetlmesssagc that transits the MME Through configuring the liE to send a cell update to the MME every time a cell change occurs By the cNB notifying the MME if a ecU change occurs which may be possible if the RAN is in an RRC Messaging Connected Leashed state.

Conclusion

Generally, the invention has been described in an LIE enviromnent as the invention can be advantageously implemented in this environment, however the invention is not limited to an LTB environment and may be implcmcnted in any other suitable environment.

Various modifications can be made to examples of the present invention.

Embodiments of the present invention have been defined largely in terms of reduced capability terminals, however, it will be understood that any suitable terminal can transmit and receive short messages according to the present disclosure, including conventional terminals such as a personal phone.

Also, for the ease of illustration and in the interest of intelligibility, only one node for each element of the network has been represented and discussed. However, thc skilled person will understand that there may be more than one of each node. For example, the mobile network may comprise a plurality of eNB, of MME, of S-OW and/or of P-OW.

Various further aspects and features of the present invention are defined in the appended claims. Various modifications may be made to the embodiments described above without departing fiDni the scope of the present invention. For example, embodiment of the present invention finds application with other types of mobile communications networks and is not limited to LTE.

Claims

<claim-text>CLAIMS1. A mobile communications network for communicating data to/from communications devices, the network comprising: one or more base stations operable to provide a wireless access intcrfacc to communications devices; one or more communications devices operable to communicate packets with the onc or more base stations via the wireless access interface; one or more mobility managers operable to send and receive signalling packets 1 0 between base stations and a destination; wherein: the one or more mobility managers are operable, upon reception of a signaUing packet from a communications device and comprising user data intended for a destination, to detect that the packet is not associated with any established signalling connection between the one or IS more mobility managers and this communication device; and the one or more mobility managers are operable, responsive to said detection, to transmit the user data comprised in the signalling packet to the destination.</claim-text> <claim-text>2. A mobile communications network according to claim 1, wherein the one or more mobility managers being operable to transmit the user data comprises the one or more mobility managers being operable to set up a temporary mobility manager context for transmitting the user data to the destination.</claim-text> <claim-text>3. A mobile coimnunications network according to claim
2. wherein the one or more mobility managcrs arc opcrablc to discard thc temporary mobility managcr context after a predetermined number of packets have been exchanged with the communications device, the signalling packet being inc]uded in the number of packets.</claim-text> <claim-text>4. A mobile communications network according to ebim 3, wherein the predetennined number of packets is any integer equal to or greater than one.</claim-text> <claim-text>5. A mobile communications network according to any of claims 3 to 4, wherein the one or more mobility managers are operable to configure the predetermined number of packets on a per temporary mobility manager context basis.</claim-text> <claim-text>6. A mobile communications network according to claim 5, wherein: the one or more mobility managers are operable to identi' that the signalling packet is part of a two-packet exchange; and the one or more mobility managers are operable, upon this identification, to configure the predetermined number of packets for the temporary mobility manager context to the number two.</claim-text> <claim-text>7. A mobile communications network according to any of claims 2 to 6, wherein: the one or more mobility managers being operable to set up a temporary mobility manager context comprises the one or more mobility managers being operable to associate the temporary mobility manager context with a timer; and the one or more mobility managers are operable, upon expiry of the timer, to discard the temporary mobility manager context.</claim-text> <claim-text>8. A mobile communications network according to any preceding claim, wherein: the one or more base stations are operable, upon reception of a signalling message from a communications device and comprising user data intended for a destination, to detect that the message is not associated with any established signalling connection between the one or more base stations and this communication device; and the one or more base stations are operable, responsive to said detection, to forward the message to the one or more mobility managers.</claim-text> <claim-text>9. A mobile communications network according to claim 8, wherein the one or more base stations are operable to set up a temporary base station context for transmitting the signalling message to the one or more mobility managers.</claim-text> <claim-text>10. A mobile communications network accothing to claim S or 9, wherein thc one or more base stations are operable to discard the temporary base station context after a predetermined number of messages have been exchanged with the communications device, the signalling message being included in the number of messages.</claim-text> <claim-text>11. A mobile communications network according to claim 10, wherein: the one or more base stations are opeiable to identify that the signalling message is part of a two-message exchange; and the one or more base stations are operable, upon this identification, to configure the predetermined number of messages for the temporary base station context to the number two.</claim-text> <claim-text>12. A mobile couuuunications network according to any of claims S to Ii, wherein: die one or more base stations being operable to set up a temporary base s tation context comprises the one or more base stations being operable to associate the temporary base station context with a timer; and the one or more base stati oils are operable, upon expiry of the timer, to discard the temporary base station context.</claim-text> <claim-text>13. A mobile conrniunieations network according to any of claims 2 to 12, wherein the temporary mobility manager context is set up using information comprised in the signalling 23 packet.</claim-text> <claim-text>14. A mobile communications network for communicating data to/from communications devices, the network comprising: one or more base stations operable to provide a wireless access interface to communications devices; one or more communications devices operable to communicate packets with the one or more base stations via the wireless access interface; S one or more mobility managers operable to send and receive signalling packets for conutlling user data communications between base stations and a destination; wherein: the one or more base stations are operable, upon reception of a signalling message from a communications device and comprising user data intended for a destination, to detect 1 0 that the message is not associated with any established signalling connection between the one or more base stations and this communication device; and the one or more base stations are operable, responsive to said detection, to ansinit the user data comprised in the signalling message to the destination and via the one or more mobility managers.</claim-text> <claim-text>15. A mobile communications network according to claim 14, wherein the one or more base stations being operable to transmit the user data comprises the one or nioie base stations being operable to set up a temporary base station context for forwarding the user data to the one or more mobility managers.</claim-text> <claim-text>16. A mobile communications network according to claim 15, wherein the one or more base stations arc operable to discard the tempora.iy base station context after a predetermined number of messages have been exchanged with the communications device, the signalling message being included in the number of messages.</claim-text> <claim-text>17. A mobile communications network according to claim 16, wherein the predetermined number of messages is any integer equal to or eater than one.</claim-text> <claim-text>18. A mobile communications network according to any of claims 15 to I 7, wherein the one or more base stations are operable to configure the predetermined number of messages on a per temporary base station context basis.</claim-text> <claim-text>19. A mobile communications network according to claim 18, wherein: the one or more base stations are operable to identify that the signalling message is part of a two-message exchange; and the one or more base stations are operable, upon this identification, to configure the predetermined number of messages for the temporary base station context to the number two.</claim-text> <claim-text>20. A mobile communications network according to any of claims 15 to 19, wherein: the one or more base stations being operable to set up a temporary base station context comprises the one or more base stations being operable to associate the temporary base station context with a timer; and the one or more base stations are operable, upon expiry of the timer, to discard the temporary base station context.</claim-text> <claim-text>21. A mobile eonununications network according to any of claims 15 to 20, wherein: the one or more mobility managers are operable, upon reception of a signalling packet from a communications device and comprising user data intended for a destination, to to transmit the user data comprised in the signalling packet to the destination 22. A mobile communications network according to claim 21, wherein the one or more mobility managers are operable to set up a temporary mobility manager context storing routing information, for routing of a mobile terminated packet to communications device.23. A mobile communications network according to claim 21 or 22, wherein the one or more mobility managers are operable to discard the temporary mobility manager context afler a predetermined number of packets have been exchanged with the communications device, the signalling pac]cet being included in the number of packets.24. A mobile communications network according to claim 23, wherein: the one or more mobility managers are operable to identify that the signalling packet is part of a two-packet exchange; and the one or more mobility managers are operable, upon this identification, to confignre the predetermined number of packets for the temporary mobility manager context to the number two 25. A mobile communications network according to any of claims 21 to 24, wherein: the one or more mobility managers being operable to set up a. temporary mobility manager context comprises the one or more mobility managers being operable to associate the temporary mobility manager context with a timer; and the one or more mobility managers are operable, upon expiry of the timer, to discard Ilic (tmporary mobility manager context.26. A mobile communications network according to any of claims 15 to 25, wherein the temporary base station context is set up using information comprised in the signalling message.27. A mobile communications network according to any preceding claim wherein the one or more mobility managers are operable to transmit the user daLa Lu Lhe destinali.uu via a messaging server connected to the one or more mobility managers.28. A mobile communications network according to any preceding claim, wherein the network is a 3OPP-compliant network.29. A mobile communications network according to any preceding claim, wherein the network is a LTE-compliant network.30. A mobile communications network according to claim 29, wherein one of the one or more packet gateway is a Sej-ving-GateWay.31. A mobile communications network according to claim 29 or 30, wherein one of the one or more mobility managers is a Mobility Management Entity (MME).32. A method of communicating data to/from communications devices in a mobile communications network, the mobile communications network comprising one or more base stations operable to provide a wireless access interface to communications devices; one or more communications devices operable to communicate packets with the one or more base stations via the wireless access interface; and one or more mobility managers operable to send and receive siialling packets for controlling user data communications bctween base stations and a destination; wherein the method comprises: upon reception of a signalling packet from a communications device and comprising user data intended for a destination, the one or more mobility managers detecting that the packet is not associated with any cstablished signalling connection between the one or more mobility managers and this communication device; and responsive to said detecting step, the one or more mobility managers Uansmitting the user data comprised in the signalling packet to the destination.33. A method according to claim 32, the method fudher comprising the one or more mobility managers setting up a temporary mobility manager context for transmitting the user data to the destination.34. A method according to claim 33, the method further compri sing the one or more mobility managers discarding the temporary mobility manager context after a predetermined number of packets have been exchanged with the communications device, the sina1ling packet being included in the number of packets. c35. A method according to claim 34, wherein the predetermined number of packets is any integer equal to or greater than one.36. A method according to any of claims 34to 35, the method further comprising the one or more mobility managers configuring the predetermined number of packets on a per temporary mobility manager context basis, 37. A method according to claim 36, the method comprising: the one or more mobihty managers identifying that the signalling packet is part of a two-packet exchange; and upon this identification, the one or more mobility mam%gers confi gui-i ng the predetermined number of packets for the temporary mobility manager context to the number two.38. A method according to any of claims 32 to 37, the method comprising: the one or more mobility managers setting tip a. temporary mobility manager context comprises the one or more mobility managers being operable to associate the temporary mobility manager context with a timer; and npon cxpiry of the timer, the one or more mobility managers discarding the temporary mobility manager context.39. A method according to any one of claims 32 to 39. the method comprising: upon reception of a signalling message from a communications device and comprising user data intended for a destination, the one or more base stations detecting that the message is not associated with any established ignal1ing connection between the one or more base stations and this conrnmnication device; and responsive to said detection, the one or more base stations transmitting the user data comprised in the signalling message to the one or more mobility managers.D40. A method according to claim 39, the method comprising, responsive to said detection, the one or more base stations setting up a temporary base station context for fransmitting the signalling message to the one or more mobility managers.41 -A method according to claim 39 or 40, the method comprising the one or more base stations discarding the temporary base station context after a precielennined nmnber of messages have been exchanged with the communications device, the signalling message being included in the number of messages.42. A method according to claim 41, the method comprising: the one or more biwe etations identifying that the signalling message is part of a two-message exchange; and upon this identification, the one or morc base stations configuring the predetennined number of messages for the temporary base station context to the number two.43. A method according to any of claims 39 to 42, the method comprising: the one or more base stations being setting up a temporary base station context comprises the one oi niore base stations associating thc tcmporery base station context with a timer; and upon expiry of the timer, the one or more base stations discarding the temporary base station context.44. A method according to any of claims 32 to 43, the method comprising setting up the temporary mobility manager context using information comprised in the signalling packet.45, A method of communicating data to/from communications devices in a mobile communications network, the mobile communications network comprising one or more base stations operable to povide a witeless access interface to communications devices; one or more communications devices operable to communicate packets with the one or more base slations via the wi -eless access interface; and one or more mobility managers operable to send and receive signalling packets for controlling user data communications between communications devices and packet gateways; wherein the method comprises: 1 0 upon reception of a signalling message from a communications device and comprising user data intended for a destination, the one or more base stations are detecting that the message is not associated with any established signalling connection between the one or more base stations and this communication device; and responsive to said detection, the one or more base stations transmitting the user data comprised in the signalling message to the one or more mobility managers.46. A method according to claim 45, the method ftwther comprising the one or more base stations setting up a temporary base station context for transmitting the user data to the destination and via the one or more mobility managers.47. A method according to claim 46, the method comprising the one or more base stations discarding the temporary base station context after a predetermined number of messages have been exchanged with the communications device, the signalling message being included in the number of messages.48. A method according to claim 47, wherein the predetermined number of messages is any integer equal to or geatcr than one.49. A method according to any of claims 46 to 48, the method compnsing the one or more base stations configuring the predetermined number of messages on a per temporary base station context basis.50. A method according to claim 49, the method comprising: the one or more base stations identifying that the signalling message is part of a two-message exchange; and upon this identification, the one or more base stations configuring the predetermined number of messages for the temporary base station context to the number two. 1 051. A method according to any of claims 46 to 50, the method comprising: the one or more base stations setting up a temporary base station context comprises the one or more base stations associating the temporary base station context with a timer; and upon expiry of the timer, the one or more base stations discarding the teniporat-y base station context.52. A method according to any of claims 46 to 51, the method comprising: upon reception of a signalling packet from a communications device and comprising user data intended for a destination, the one or more mobility managers detecting that the message is not associated with any established signalling connection between the one or more mobility managers and this communication device; and responsive to said detection, the one or more mobility managers transmitting the user data comprised in the signalling packet to the destination.53. A method according to ciaim 52, wherein the one or more mobility managers transmitting the user data comprises the one or more mobility managers setting up a temporary mobility manager context for transmitting the user data to the destination.54. A method according to claim 52 or 53, the method comprising the one or more nobility managers discarding the temporary mobility manager context after a predetermined number of packets have been exchanged with thc communications device, the signalling packet being included in the number of packets.55. A method according to claim 54, the method comprising: the one or more mobility managers identifying that the signalling packet is part of a two-packet exchange; and upon this identification, the one or more mobility managers configuring the predetermined number of packets for the temporary mobility manager context to the number two.56. A method according to any of claims 52 to 55, thc mcthod comprising: the one or more mobility managers setting up a temporary mobility manager context comprises the one or more mobility managers being operable to associate the temporary mobility manager context with a timer; and upon expiry of the timer, the one or more mobility managers discarding the temporary mobility manager context.57. A communications network according to any of claims 45 to 56, the method comprising the one or more tnobility managers transmitting the user data to the destination via a messaging server connected to the one or more mobility managers.58. A method according to any of claims 46 to 57, the method comprising the temporary setting up the base station context using information comprised in the signalling message.59. A method according to any of claims 32 to 57, the method comprising the one or more mobility managers transmitting the user data to the destination via a messaging server connected to the one or more mobility managers.60. A method according to any of claims 32 to 59, wherein the mobile communications network is a 3UPP-compliant network.61. A mobile communications network according to any of claims 32 to 60, wherein the mobile communications network is a LIE-compliant network.62. A method according to claim 61, wherein one of the one or more packet gateway is a Serving-Gaw Way.63. A method according to claim 61 or 62, wherein one of the one or more mobility managers is a Mobility Management Entity (MME).64. A mobility manager br use iii a mobile conunuuications network euwinunicating data to/from communications devices, the network including one or more base stations for communicating with one or more communications terminals via thc wireless access interface; wherein the mobility manager is: operable to send and receive signalling packets for controlling user data communications between communications devices and a destination; operable, upon reception of a signalling packet from a communications device and comprising user data intended for a destination, to detect that the packet is not associated with any established signalling connection between the mobility manager and this communication device; and is operable, responsive to said detection, to transmit the user data comprised in the signalling packet to the destination.65. A mobility manager according to claim 64, the mobility manager being operable to transmit the user data comprises the mobility managcr being operable to set up a temporary mobility manager context for transmitting the user data to the destination.66. A base station for use in a mobile communications network communicating data to/from communications devices, the network comprising one or more communications devices operable to communicate packets via a wireless access interface; one or more packet gateways operable to transmit user data packets received \qa the wireless access interface from and/or to the one or more communications devices; and one or more mobility managers operable to send and receive signalling packets for controlling user data communications between communications devices and packet gateways; where the base station is operable to provide a wireless access interface for communications devices to communicate packets; operable, upon reception of a signalling message from a eommunicaflons device and comprising user data intended for a destination, to detect that the message is not associated with any established signalling connection between the base station and this communication devir.e; and operable, responsive to said detection, to transmit the user data comprised in the signalling message to the destination.67. A mobile communications network according to claim 66, wherein the base station being operable to transmit the user data comprises the base station being operable to set up a temporary base station context for transmitting the user data to the destination and via the one or more mobility managers.68. A mobile communications netwoj-k substantially as hereinbefore described with reference to the drawings.69. A network apparatus substantially as hereinbefore described with reference to the drawings.70. A method of communicating in a mobile communications network as hereinbefore described with reference to the drawings.</claim-text>