GB2509845A

GB2509845A - 4G/LTE Evolved Packet Core (EPC) gateway that offers UE/user option to inhibit downlink of some traffic/data types, particularly whilst roaming

Info

Publication number: GB2509845A
Application number: GB1404079.4A
Authority: GB
Inventors: Haris Zisimopoulos
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2011-07-27
Filing date: 2011-07-27
Publication date: 2014-07-16
Anticipated expiration: 2031-07-27
Also published as: GB201404079D0; GB2509845B

Abstract

4G/LTE (Long term evolution) cellular systems propose an Evolved Packet System (EPS) wherein all traffic, including voice, is carried on a packet/IP network rather than some using circuit switched networks. Thus the inhibition of certain traffic types must occur in the EPS, rather than simply deactivating packet/data functionality. An association is formed between the user equipment UE and one or more gateways (GW, PGW, SGW) in the packet switched data network S210-204. Gateways may send messages to the UE indicating their capability to inhibit downlink transmission of user data towards the user equipment S205. The UE can respond with a blocking request S206-207 and data transmission is disabled at the gateway S208. Alternatively UEs may request blocking without a capability message from the gateway. The gateway responds to the request with parameters specifying UE Gateway transmission behaviour and controls communications in accordance with the parameters (Fig.9). May be used to block data/internet functions whilst roaming.

Description

Controlling Data Transmission Between a User Equipment and a Packet Data Network

Technical Field

The present invention relates to the control of transmission of user data between a user equipment and a packet data network, in particular where the transmission takes place via a packet switched data network including a core network.

Background

Communications systems such as wireless communications systems comprising wireless networks, in which a user equipment (UE) such as a mobile handset communicates via wireless links to a network of base stations or other wireless access points connected to a telecommunications network, have undergone rapid development through a number of generations of radio access technology. The initial deployment of systems using analogue modulation has been superseded by IS second generation (2G) digital systems such as GSM (Global System for Mobile communications), typically using GERA (GSM Enhanced Data rates for GSM Evolution Radio Access) radio access technology, and these systems have themselves been replaced by or augmented by third generation (30) digital systems such as UN'ITS (Universal Mobile Telecommunications System), using the UTRA (Universal Terrestrial Radio Access) radio access technology. Third generation (3G) standards provide for a greater throughput of data than is provided by second generation systems; this trend is continued with the proposals by the Third Generation Partnership Project (3GPP) of the Long Term Evolution (LTE) system, using E-UTRA (Evolved UTRA) radio access technology, which offers potentially greater capacity and additional features compared with the previous standards.

LTE is designed as a high speed packet switched network, and voice and SMS services are provided as packet switched services such as Voice over Internet Protocol Multimedia Subsystem (V0TMS) and SMS over IMS (typically refened to as SMSoIP), whereas previous generation systems such as IJIVITS support voice and SMS services that are primarily circuit switched. Therefore, for LTE, both data and voice services are provided by a packet switched network, and a circuit switched connection is generally not available, The packet switched network is typically "always on", so that following a successful initial attachment, a UE remains connected to one or more packet switched data networks.

It is sometimes desirable to inhibit or prevent transmission of some or all types of user data to and from the user equipment. For example, in 2G and 30 networks, the user is often provided with the option of disabling (by e.g. altering a setting on his or her UP) transmission of all types of user data other than voice and SMS data; in particular, voice and SMS user data are often subject to charges which are different from (typically lower than) charges for other types of user data. This may be particularly useful in situations in which the TIE is "roaming" i.e. connected to a visited network, in which higher charges may apply than when the TiE is connected to its home network.

However, it is not straightforward to inhibit transmission of user data in packet switched networks such as LTE, since, as described above, it is designed as an "always on" connection. In particular, it is not straightforward to distinguish between IS different types of data since, in LTE, all data is transmitted according to a packet-switched method.

It is an object of the invention to at least mitigate some of the problems with

the prior art systems.

Summary

In accordance with a first aspect of the present invention, there is provided a method of controlling user data transmission between a user equipment and one or more packet data networks (PDN) via a packet switched data network including a core network, the core network including one or more gateways, each said gateway being communicatively coupled to said packet data network (PDN), the method comprising: performing a association process to form an association between the user equipment and a first said gateway, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway; receiving, during said association process, an indication to inhibit transmission of user data towards said user equipment, and, in response to receipt of indication to inhibit transmission of data: sending a message to said user equipment indicating one or more parameters defining transmission characteristics of user data that may be transmitted between a first said gateway and the user equipment; and controlling transmission of user data from said first gateway towards said user equipment in accordance with said one or more predefined parameters.

This enables the core network to specify to the user equipment, in response to receiving the indication therefrom, transmission characteristics of user data that may be transmitted to and from the user equipment. By similarly controlling transmission of user data from the first gateway towards user equipment on the basis of the specified transmission characteristics, consistency between the transmissions for the first gateway and those from the user equipment can be ensured.

Further, since the indication to inhibit transmission is received during the association process, it can be ensured that no user data whose transmission is not desired is transmitted prior to the implementation of control of data transmission.

IS In one embodiment, the method comprises inhibiting said data transmission based on a policy. In one embodiment, said first gateway receives said indication to inhibit transmission of user data and, responsive thereto, retrieves said policy from a policy server, such as Policy and Charging Rules Function (PCRF), thereby enabling the policy used by the first gateway to be dynamically varied. Thus, a network operator, for example, may control which data is inhibited.

In accordance with a second aspect of the present invention, there is provided a method of controlling user data transmission between a user equipment and one or more packet data networks (PDN) via a packet switched data network comprising a core network, the core network including one or more gateways, each said gateway being communicatively coupled to said packet data network (PDN), the method comprising: performing an association process to form an association between a first said gateway and the user equipment, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway; sending, during said association process, an indication from the user equipment to the core network to inhibit transmission of said user data towards said user equipment; receiving a message at said user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between the first gateway and the user equipment; and controlling transmission of user data of from said user equipment towards said first gateway in accordance with said one or more predefined parameters.

In one embodiment, the method comprises said user equipment determining that a sewing access network is a visited network, and said indication is sent based at least in part on a determination by said user equipment that said serving access network is a visited network.

Thus, inhibition of the transmission of user data may be implemented as a default when the user device is roaming.

In one embodiment, the indication is sent from said user equipment based at least in part on a user input. This enables a user to control the transmission of user data to and from his or her device.

IS In accordance with a third aspect of the invention, there is provided a gateway for controlling user data transmission between a user equipment and a packet data network (PDN), the gateway being communicatively coupled to the packet data network (PDN), the gateway being arranged to: perform an association process to form an association with the user equipment, thereby enabling transmission of data between the user equipment and the packet data network (PDN) via the gateway; receive, during said association process, an indication to inhibit transmission of user data towards said user equipment, and, in response to receipt of said indication to inhibit transmission of data: send a message to the user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between a first said gateway and the user equipment; and control transmission of user data from the first gateway towards said user equipment in accordance with the one or more predefined parameters.

The gateway of the third aspect may be adapted to provide features corresponding to any of those described above in relation to the method of first aspect of the invention.

In accordance with an fourth aspect of the present invention, there is provided a user equipment for use with a packet switched data network including a core network, the user equipment being capable of receiving user data from, and sending data to, one or more packet data networks (PDN) via said core network, the core network including one or more gateways, each said gateway being communicatively coupled to a said packet data network, the user equipment being arranged to: perform an association process to form an association with a first said gateway and the user equipment, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway; send, during said association process, an indication from the user equipment to the core network to inhibit transmission of said user data towards said user equipment receive a message at said user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between the first gateway and the user equipment; and control transmission of user data from said user equipment towards said first gateway in accordance with said one or more predefined parameters.

The user equipment of the fourth aspect may be adapted to provide features corresponding to any of those described above in relation to the method of second aspect of the invention.

In one embodiment, the user equipment is capable of sending and receiving user data of first and second types, the first type of data comprising voice and Short Message Service (SMS) data, and the second type of data being different from the first type of data, wherein said association with the first gateway enables transmission of data of the second type, and the user equipment is arranged not to form an association with a second gateway for enabling transmission of data of the second type. The user equipment may be arranged to form an association with a third gateway for enabling transmission of data of the first type. These features prevents further associations being formed which may result in the transmission of undesired user data, whilst enabling associations to be formed which enable transmission of desired user data, such as voice and SMS data.

Further features and advantages of the invention will become apparent from the following description of preferred embodiments of the invention, given by way of example only, which is made with reference to the accompanying drawings.

Brief Description of the Drawinzs

Figure 1 is a flow diagram showing steps performed by a user equipment; Figure 2a is a sequence diagram showing steps performed by a user equipment and a core network in ammging to inhibit data tnmsmission; Figure 2b is a sequence diagram showing steps performed by a user equipment and a core network in ceasing inhibition of data; Figure 3 illustrates a message including an indication that a core network is capable of inhibiting transmission of data; Figure 4 shows details of a protocol configurations options (PCO) field of the message of Figure 3; IS Figure 5 shows a message including an indicator that data transmission is to be inhibited; Figure 6 shows details of a traffic flow aggregate field of the message of Figure 5; Figure 7 shows a list of packet data filters that may be included in the traffic

flow aggregate field shown in Figure 6;

Figure 8 is a schematic diagram illustrating data flow patterns being provided to a core network from a user device; Figure 9 is a sequence diagram showing steps performed by a user equipment and a core network in arranging to inhibit data transmission in accordance with an embodiment of the present invention; Figure 10 shows a message including an indication that data transmission is to be inhibited in accordance with the embodiment of the present invention; Figure II shows details of a request type field of the message of Figure 10; Figure 12 is a sequence diagram showing steps performed by a user equipment and a core network in arranging to inhibit data transmission in accordance with an embodiment of the present invention; Figure 13 is a sequence diagram illustrating an arrangement for performing deep packet inspection (DPI) in accordance with an embodiment of the present invention.

Detailed Description

Embodiments of the invention will now be described in the context of a telecommunication network including an LTE Evolved Packet System (EPS) packet switched data network, However, it will be understood that this is by way of example only and that other embodiments may involve other packet switched data networks using other radio access technologies, such as 1EEE802. 16 WiMax.

Figure 1 is a flow diagram of a steps performed by a HE. At step S100, the HE camps in a given LTE cell; at step S 102, the UE performs an attach process. The attach process, which is describe in more detail below with reference to Figure 2, involves the HE forming an association with a core network of the LTE wireless IS communication system, and in particular with one or more a packet data network gateways (P-GW). The P-GWs are each communicatively coupled to one or more packet data networks (PDN), enabling the UE to receive user data from, and transmit user data to, the PDNs. Exemplary PDNs include an ll'/1S, the internet and an intranet, such as a corporate intranet.

At step S 104, the HE receives an indication from the core network that it has a "block data" capability in accordance with an embodiment of the present invention; the "block data" capability of the core network is described below. The HE stores an indication of the core network "block data" capability at step 5106.

At step S108 the UE determines whether or not to adopt a "block data" configuration i.e. a configuration which transmission of some or all user data between the HE and a P-GW is inhibited, The HE may be triggered to adopt the "block data" configuration by a user input, for example a user adjusting a setting on their UE to disable user data transmission. Alternatively, or additionally, the HE may adopt a "block data" configuration in response to determining that it is roaming (i.e. that the serving network, such as a Public Land Mobile Network (PLMN) with which it is connected is a visited network by, for example, receiving a System Identification Number (SID) from the PLMN which indicates that the latter is not the home PLMN for the UE), The liE may have a default setting which specifies that a "block data" configuration is adopted whenever the UE is roaming. The tiE may determine whether its settings indicate to adopt a "block data" configuration in response to receipt of a message from the core network indicating that the initial attach has been successfully completed.

If the determination at step Slog is that the "block data" configuration is not to be adopted, then the UE applies its local policy settings for sending and receiving user data at step S 109, and returns to step Si08.

If the determination at step S108 is that the "block data" configuration is to be adopted, the liE next determines at step SI 10 whether a predetermined the "block all" configuration is to be adopted, or whether a "selective blocking" configuration is to be adopted.

If it is determined at step S 0 a predetermined "block all" configuration is to be adopted, then the UE sends a "block all" message to the core network at step S112.

IS The process then proceeds to step S114, in which the HE adopts a "block all" configuration. When a "block all" configuration is adopted, transmission of all user data between the tiE and the core network may be inhibited, However, in some cases transmission of some types of data may not be inhibited in the "block all" configuration; for example transmission of VoIMS and SMSoIP data may be enabled whilst the "block all" configuration is used; this will be described in detail below.

If it is determined at step SIlO that the "block all" configuration is not to be adopted in relation to all user data, a "selective block" policy is implemented in which the HE specifies types of user data whose transmission is to be inhibited, whilst allowing transmission of other types of user data. For example, there may be user-adjustable setting on the HE to enable user data relating to some applications (e.g. a social networking site) to be transmitted between the liE arid the core network, but not others, If the selective block policy is implemented, the UE sends, at step S 116, a message to the core network including one or more parameters defining transmission characteristics of user data that may be transmitted from the core network to the HE; these parameters may relate to one or more filters. At step 5118, the UE implements a selective blocking policy to allow transmission of user data having transmission characteristics defined by the parameters, and to block data transmission from the HE of user data having other transmission characteristics.

Figure 2a is a sequence diagram showing communications between a UE 1, and core network components in controlling data transmission. The core network components include a control node such as a Mobile Management Entity (MNW) 2, a subscriber database such as a Home Subscriber Server (HSS) 3 and a gateway such as a PDN gateway (P-GW) 4, which may be co-located with a serving gateway (S-GW).

Communication between the HE I and the core network may be performed via a Radio Access Network (RAN), including one or more wireless base stations, such as an eNodeB (eNB), as referred to in the LTE standards.

In steps S201 to S205, the UE I and the core network perform an attach process, as described above in relation to Figure 1, During the attach process, an association is formed between the UE I and the P-GW 4, in the form of a default EPS bearer which is characterised in part by parameters such as a filter specification, IS known as a traffic flow template (TFT), which specifies transmission characteristics of user data transmission that is allowed between the tiE 1 arid the P-GW 4. The transmission characteristics may include IP addresses, port numbers and/or a protocol associated with transmission of user data between the end points of the data transmission to which the default EPS bearer relates. A TFT is communicated from P-GW 4 to the liE 1 during the attach process.

Although only one P-GW 4 is shown in Figure 2a, as described above, the tiE 1 may simultaneously attach to more than one P-GW 4, each of which may be communicatively coupled to a different PDN. The PDN or PDNs to which the liE 1 attaches are each defined by an identifier, such as an Access Point Names (APN), The attach request sent to the core network by the HE 1 at step S201 may include one or more APNs, or one or more default APNs may be provided by the HSS 3 in response to the attach request (cf steps S202 and S203), As part of the attach process, the HE receives a message from the P-GW 4 indicating that the core network has a "block data" capability in accordance with an embodiment of the present invention. Figure 3 shows an exemplary message 300, in which the indication of the "block data" capability is included in the protocol configuration options (PCO) field 302 of the message 300. Figure 4 shows an exemplary PCO parameters list of the PCO field, which includes a "block data" parameter 400, indicating that the core network is capable of implementing a "block data" configuration.

In the example of Figure 2a, the TIE I implements a "block data" configuration in response to determining that is roaming, and a "data when roaming" setting on the UE I is switched off. However, it will be understood that, in some embodiments, a "block data" configuration may be implemented in response to another event, for example the user ad] usting a setting on the TIE I. As described above with reference to Figure 1, once the TiE 1 is triggered to implement a "block data" configuration, it sends at step 206 a message to the core network, such as a "bearer resource modification" request message, including an indication to implement a "block data" configuration in the core network. This message is received at the MME 2, which in turn sends a "bearer resource command", indicating that a "block data" configuration is to be implanted, to the P-OW 4, at step IS S207. A bearer resource modification procedure is then perfomied at step S208 to modify the TFT used for the default EPS bearer.

Figure 5 shows an exemplary "bearer resource modification request" message 500, which includes a traffic flow aggregate information element 502. Details of this information element 502 are shown in figure 6; in particular, it includes a TFT operation code field 600 having a value ("III" in the example of figure 6) which indicates to the core network that a "block data" configuration is to be implemented,

and a packet filter list field 602.

The information element 502 is sent to the P-GW 4 as part of the bearer resource command sent at step S207. The P-GW 4 may interpret the block data 502 element in different ways, depending on whether or not the packet filter list field 602 is empty, We first consider the case in which the packet filter list field 602 is empty. In this case, the P-OW 4 adopts a "block all" configuration and implements a predefined rule, or policy, stored at the P-OW 4; the message 500 in this case corresponds to the "block all" message described above with reference to step 5112 of Figure 1. The predefined rule may be to block all user data, so that all user data transmission towards the liE I from the P-OW 4 is inhibited; this may be the case if the PDN with which the P-GW 4 is coupled is one that does not provide VoTIMS or SMSoIP user data, for example if the PDN is a company intranet, Alternatively, the predefined rule may be to block only predefined types of user data, so that transmission of only user data of the predefined types towards the lIE 1 from the P-OW 4 is inhibited; for example, if the PDN with which the P-GW 4 is coupled is one that provides VoIIYIS and/or SMSoIP user data, the P-GW 4 may allow transmission of VoIMS/SMSoIP data, whilst inhibiting transmission of all other types of data.

We now turn to the case in which the packet filter list field 602 is not empty; in this case a "selective blocking" configuration is adopted, and the message 500 corresponds to that described above with reference to step 5116 of Figure 1. Figure 7 shows an exemplary list of packet filters which may be included in the packet filter list field 602. The P-GW 4 interprets this list as a list of packet filters in the existing TFT for the default EPS bearer which are to be deactivated, so that transmission towards the lIE 1 of user data having transmission characteristics defined by the listed packet filters is inhibited. This enables the TIE to specify (in accordance with a user-defined setting, for example) types of user data whose transmission is to be inhibited.

Although, in the example described above, the value in the TFT operation code field 600 was assumed to be the same whether or not the packet filter list field 602 is empty, in some embodiments a different value is used when the packet filter list field 602 is empty to the value used to when the packet filter list field is not empty.

Although not shown in Figure 2a, the P-OW 4 may contact a policy server, such as a Policy Charging and Rules Function (PCRF) to indicate that a "block data" configuration is being implemented. This may enable an update to, for example, a charging policy.

Various methods may be used to differentiate between different types of user data at the TiE, and at the P-GW 4. We first consider the TIE L The TIE I may have one or more internal interface, such as an application programming interface (API) which differentiates between different types of user data, according to, for example, the application to which the type of user data relates. For example, the TIE I may allow transmission of user data which is used by an application that uses VoIMS and/or SMSoIP, but inhibit transmission of user data by applications which use other types of user data.

Alternatively, or additionally, the HE may define different transmission characteristics of data for different types of data, and filter accordingly. For example, in the case of an lEVIS APN (i.e. in the case that an association is formed between the UE I and a P-GW 4 communicatively coupled with an IMS), the IJE may define a different IMS flows for VoIIMS/SMSoIIP than for non-Vo]IMS/SMSoIP data. These lEVIS flows could be defined as follows: Flow 1: (IP address TIE 1, port A) <--> (IP address P-CSCF, port C) over TCP; Flow 2: (IP address TIE 1, port_B) <--> (IP address P-CSCF, port_D) over TCP The IJE I could thus use Flow I for VoIMS/SMSoIP, and Flow 2 for non-VoIIVIS/SMS0IP; by applying filters that allow transmission of user data from port_A IS on the HE I side to port_C on a Proxy Call Session Control Function (P-CSCF) (the destination of the transmission in the LVIS), but not from port_B on the IJE 1 side to port_D on the P-CSCF side, it is thus possible to allow voice calls and SMS messages to be sent, whilst preventing other types of user data transmission. Alternatively, or additionally, different IP addresses and/or protocols could be used to distinguish between different types of user data. For example, the P-CSFC could be arranged to allocate different IP addresses on IMS registration, so that the IP address used for VoIIVIS/SMS is different from that used for non-VoItvIS/SMSoIP; flow I could then specify the IP address for the former, and flow 2 the IP address for the latter. In another example, flow I could specify TCP as the transport protocol, with flow 2 specifying TJIDP.

The P-GW 4 may similarly apply packet filters to distinguish different types of user data. As described above, the user may include a list of packet filters in the packet filter field 602 in the "bearer resource modification" request message including the indication implement a "block data" configuration. This enables the HE 1 to selectively control the user data that it transmitted towards the HE 1 from the P-GW 4, as well as the user data that is transmitted towards the P-GW 4 from the HE I. in In some embodiments, the P-OW 4 stores predefined data flows (such as JIvIS data flows) corresponding to those used by the UP I as described above, so that a predefined packet filters can be deactivated to inhibit transmission of predefined types of user data. Alternatively, or additionafly, the TIE 1 may be arranged to create and send data flows to the P-GW 4. For example, as shown in Figure 8, the data flows may be sent initially to a P-CSFC 5 by the UE I as part of a message, such as a SIP register message; the data flows are then sent to a Policy Charging and Rules Function (PCRF) 6 as part of a message, for example a Rx message, arid subsequently to the P-OW 4 as part of a message, for example a Ox message. Thus, when implementing a "block data" configuration, the UE I may first send the data flows to the P-OW 4 as described above with reference to Figure 8, and subsequently send a "block data" message, as described above, including a list of one or more packet data filters that are to be deactivated at the P-GW 4. In this way, the UP I may define arbitrary types of user data whose data transmission is to be inhibited. This enables the user-adjustable IS setting described above with reference to Figure 1 to be implemented; a traffic flow can be created specifically for ariy type of user data whose receipt at the P-Ow 4 the user wishes to inhibit (or allow).

Alternatively, or additionally, to using packet filters, the P-OW 4 may use another method, such as a deep packet inspection (DPI) method to distinguish between, and inhibit transmission of different types of user data.

Figure 2b shows a process that may be implemented when the "block data" configuration is to be cancelled; as shown, this may be triggered by the user of the UE adjusting a setting on the TIE ito enable connectivity with respect to the user data whose transmission was inhibited in the "block data" configuration, At step S209, the TIE 1 sends a "bearer resource modification" message to the IvilviE 2 indicating that the default TFT (i.e. the TFT that was initially transmitted to the LIE I from the P-OW 4 during the attach process) is to be used. The MME 2 then sends a "bearer resource command" message, also indicating that the default TFT is be used, to the P-OW 4 at step S210; a procedure is then performed at step S21 1 to restore the default TFT at the P-Ow 4. Similarly, the default TFT is implemented at the TIE 1, so that transmission of all user data allowed by the TFT is enabled in both directions between the TiE 1 and the P-OW 4, The processes described above relate to the default EPS bearer that is established between the UP and the P-GW 4, In the case that one or more dedicated bearers also exist between the IJE I and the P-OW 4 at the time that the "block data" configuration is implemented by the UE 1, corresponding processes are also preferably imp'emented in relation to the one or more dedicated EPS bearers, to ensure that transmission of user data whose transmission is inhibited in the default EPS bearer is also inhibited in the one or more dedicated EPS bearers. Further, a policy stored in the P-GW 4 may specify that any dedicated EPS bearer initiated by the P-GW 4 during implementation of a "block data" configuration must inhibit transmission of the types of user data that are inhibited in the defauft EPS bearer.

In the embodiments described above with reference to figure 1 to figure 8, a message indicating that data transmission is to be inhibited is sent subsequently to completion of the attach process. However, in some embodiments, an indication that data transmission towards the HE 1 is to be inhibited is sent to the P-GW 4 as part of IS the attach process; the sending of the message may be conditional on the HE I making a determination, prior to initiating the attach process, that it has been set to implement a "block data" configuration and/or making a detennination that it is roaming.

Figure 9 illustrates an exempbry process in which the indication is included in an attach request sent from the TiE 1. The HE 1 sends an attach request at step S901, which includes the indication, in the form of a "block data" flag. As described above with reference to Figure 2a, the attach request may optionally include an APN, or an APN may instead be retrieved from the HSS 3 (cf steps S902 and S903). After completing an APN provisioning check at step 5904, the MIv1IE 2 sends a create session request including the block data flag at step S905.

Figure 10 shows an exemplary "attach request" message, which includes a "request type" information element 1000, details of which are shown in Figure ii. As can be seen in Figure II, the request type includes a value 1100 indicating that a "block data" configuration is to be implemented.

Returning to Figure 9, at step S906 the P-GW 4 retrieves a policy for implementing the "block data" configuration from a policy server, such a PCRF 6. As shown in Figure 9, this retrieval may be performed as part of a process to establish an IP Connectivity Access Network (IP-CAN) Session with the PCRF 6. As with the policy described above with reference to Figure 2a, the retrieved policy may define how the block data indication is to be interpreted; this policy may depend on the APN to which the P-OW 4 corresponds. For example, in the case of an IMS APN, the policy may be to allow VoIMS/SMSoIP data transmission, but to inhibit transmission of other types of data, for examp'e; in the case of an internet APN, the policy may be to inhibit transmission of all user data, for example.

Based on the retrieved policy, at step 5907 the P-OW 4 sends a message at towards the HE 1 including one or more parameters defining transmission characteristics of user data that may be transmitted between the P-OW 4 and the HE 1; the one or more parameters may be provided as a TFT, and the message in which one or more parameter are included may be a "create session response" message, which is sent from the P-GW 4 to the MME 2. The one or more parameters are subsequently sent from the MME 2 to the UP at step S908, as part of an "attach accept" message. The liE 1 then completes the attach process by sending an "attach complete" message to the MME 2 at step S909.

The P-OW 4 and UE 1 may then each implement a block data policy to control transmission of user data, by inhibiting transmission of some or all user data on the basis of the one or more parameters sent to the HE 1; this may be done using, for example a method as described above using packet filters, an API and/or a DPI method.

When a "block data" configuration is to be cancelled, the procedure described above in relation to Figure 2b may be used to set the TFT for the bearer to default TFT, Alternatively, a Tracking Area Update (TAU) or Service Request (SR) could be used.

In this embodiment, types of user data whose transmission is inhibited in a "block data" configuration are determined by a policy of the core network. In the example described above, this policy is retrieved from a policy server such as a PCRF 6; this enables the policy to be dynamically varied, for example by a network operator, by changing the policy stored in the PCRF 6. However, in some embodiments, a policy may instead by stored at the P-OW 4, with no retrieval from the PCRF 6 being performed; in this case, the P-OW 4 may contact the PCRF 6 to indicate the policy being used, so that that the PCRF 6 can update, for example, a charging policy.

A further embodiment in which the indicator to inhibit transmission of data is sent by the UE I during an attach process is illustrated in figure 12. In this example, the indicator is not included in the initial attach request; instead, the attach request sent at step S]20] to the MME is embedded with a PDN connectivity request including a EPS Session Management (ESM) information transfer flag. The MIVIE 2 sends an ESM information request at step S 1202 to the UE 1, and the liE 1 responds with an ESM information response message at step S 1203, this latter message including an indicator to inhibit transmission of user data from the P-GW 4 towards the liE 1, the indicator in this case identifying of an APN, herein referred to as a "block data" APN. The block data APN may be a standardised or well-known APN, which defines transmission characteristics of types of user data whose transmission between UE 1 and the P-GW 4 is to be inhibited.

IS After performing an update location procedure with the HSS 3 (steps S1202 and S 1203) and an APN provisioning check at step S 1207, the MME 2 sends a message, for example a "create session request" message, including the identifier of the block data APN, to the P-GW 4. The P-GW 4 responds with a message, such as a "create session response" message, to the Mv1IE 2 which confirms that the block data APN is to be implemented. The MI1!'vIE 2 then sends a message to the HE I confirming that the block data APN is to be used at step S1209; the message may be an "attach accept" message having an embedded "activate default EPS bearer context request".

Although not shown in Figure 12, the P-GW 4 also sends one or more parameters to the UP I defining data transmission characteristics of user data that may be transmitted between the P-OW 4 and the HE 1; these parameters are typically provided as a TFT, as described above. The liE 1 then completes the attach process by sending an "attach complete" message at step S 1210.

In this embodiment, the types of data whose data transmission is to be inhibited are defined by the APN in use. The APN may thus identify a P-GW 4 communicatively coupled to an IMS, but which uses, for example, packet filters and/or a DPI method described above, to inhibit transmission of for example, all non-VoIIVIS/SMSoIP user data. In another example, the APN may identify a P-OW 4 coupled to a PDN, but which inhibits transmission of all user data towards the UP L The IJE I may similarly inhibit transmission of some or all types of user data towards the P-OW 4 using, for example, an API and/or a packet filter method as described above.

In this embodiment the UE 1 may be aranged such that, once the block data APN is implemented, the HE 1 may not connect to a further P-OW 4 (i.e. may not implement a further APN) which allows transmission of types of user data whose transmission is inhibited for the block data APN, For example, if in the "block data" APN, the transmission of e-mail data is inhibited, then the TIE 1 may be arranged not to attach to a P-GW 4 which allows transmission of e-mail data.

Additionally or alternatively, the TiE 1 may be arranged such that, where the p-Ow 4 for the block all data APN is communicatively coupled to a PDN which does not transmit certain types of data, the TiE 1 may attach to a P-OW 4 which does transmit those types of data. For example, if the PDN for the block data APN does not provide Vo1MS data, the APN may be arranged such that it may attach to a P-OW 4 coupled to a PDN which does provide VoIMS, for example when the UE I initiates a voice call.

In this example, when the "block data" configuration is to be cancelled, the association between the TIE 1 and the P-OW 4 may be terminated, for example by an APN tear down initiated by the UE I sending a tear down indicator. The UE I may then re-attach to the core network using a different APN, for example an APN in which transmission of user data is not blocked.

In the embodiments described above with reference to figure 9 to figure 12, the default EPS bearer is implemented in accordance with the "block data" configuration during the attach process; accordingly, the P-OW 4 may have a policy that any dedicated EPS bearers which are initiated during implementation of a block data configuration must inhibit transmission of the types of user data that are inhibited in the default EPS bearer.

As mentioned above, in some embodiments of the present invention, the core network may use a DPI method to identify different types of user data. This may be particularly useful for identifying Rich Communications Suite (RCS) data. The DPI method may be implemented using a Traffic Detection Function (TDF), as illustrated in Figure 13; the TDF may co-locate with a Policy and Charging and Enforcement Function (PCEF) on the P-GW 4, or it may be standalone.

In embodiments of the present invention, the HE 1 may be a mobile device capable of accessing an LTE network, such as smart phone, personal digital assistant (PDA), laptop computer or tablet computer. In some embodiments, the UP I is an ilviS device, capable of making VoIMS calls and sending SMSoIP via an ilviS. In other embodiments, the HE 1 is a Circuit Switch Fallback (CSFB) device, which connects to a circuit-switched network for performing voice calls and sending SMS, but connects to an EPS for sending and receiving other types of user data. In still other embodiments, the UE 1 may be a device that is not capable of making voice calls but is capable of sending/receiving SMS messages, such as a "data dongle" or a laptop computer.

The UE 1 typically includes one or more communications interfaces, such as radio transceivers for communicating with the LTE wireless communication system, and a processor or set of processors for performing the steps described above in conjunction, where appropriate, with a data storage device, The processor or processors may be arranged to execute a computer program which causes the UE I to perform the steps described above.

Each of the components of the core network described above, such as the P-GW 4, may be implemented as a combination of hardware and software components and may comprise one or more communications interfaces for sending and receiving data, and one or more processors for performing the steps described above, The processor or processors may be arranged to execute a computer program which causes the P-GW 4, or other component, to execute the steps described above.

It is to be understood that any feature described in relation to any one embodiment may be used alone, or in combination with other features described, and may also be used in combination with one or more features of any other of the embodiments, or any combination of any other of the embodiments. Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the invention, which is defined in the accompanying claims,

Claims

Claims 1. A method of controlling user data transmission between a user equipment and one or more packet data networks (PDN) via a packet switched data network including a core network, the core network including one or more gateways, each said gateway being communicatively coupled to said packet data network (PDN), the method comprising: performing an association process to form an association between the user equipment and a first said gateway, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway receiving as part of a request message from the user equipment requesting formation of said association, during said association process, an indication to inhibit transmission of user data towards said user equipment, and, in response to receipt of indication to inhibit transmission of data: sending a message to said user equipment indicating one or more parameters defining transmission characteristics of user data that may be transmitted between a first said gateway and the user equipment; and controlling transmission of user data from said first gateway towards said user equipment in accordance with said one or more predefined parameters.
2. A method according to claim 1, wherein said indication message from the user equipment is received at a control node in said core network, and said control node sends said indication to inhibit transmission of user data to said first gateway.
3. A method according to claim 2, wherein said packet data network (PDN) control node comprises a Mobile Management Entity (MME).
4. A method according to either of claim 2 and claim 3, wherein the control node sends said indication to inhibit transmission of user data to a second said gateway in response to the user equipment requesting formation of an association with said second gateway.
5, A method according to any of claim I to claim 4, wherein said inhibition of data transmission is based on a policy.
6. A method according to claim 5, wherein said first gateway receives said indication to inhibit transmission of user data and, responsive thereto, retrieves said policy from a policy server, thereby enabling the policy used by the first gateway to be dynamically varied,
7. A method according to claim 6, wherein said policy sewer comprises a Policy and Charging Rules Function (PCRF).
8. A method according to any of claim I to claim 7, comprising receiving a further indication from the user equipment, the further indication being an indication IS to cease said control of transmission of user data, and, responsive thereto, ceasing said control of transmission of data.
9. A method according to claim 8, wherein said further indication is included in a Tracking Area Update (TAU).
10. A method according to claim 8, wherein said further indication is included in a Service Request (SR).
II. A method according to claim 8, wherein said further indication comprises an indication to terminate said association.
12. A method according to any of claim U8 to claim II, comprising using a Deep Packet Inspection (DPI) method at said first gateway to identify user data whose transmission is to be controlled.
i3. A method according to any of claim 1 to claim 12, wherein said transmission characteristics relate to at least one of: a destination address; a source address; a destination port number; a source port number; arid a protocol identifier.
14. A method according to any of claim to claim 13, wherein said one or more parameters relate to a plurality of filters associated with said first gateway for filtering transmission of user data from a said gateway to said user equipment, each said filter defining transmission characteristics of user data that may be transmitted between the first gateway and the user equipment.
15, A method according to any of claim Ito claim 14, wherein said one or more parameters are included in a Traffic Flow Template (TFT).
16. A method according to any of claim Ito claim 15, wherein said one or more packet data networks (PDN) includes an IP Multimedia Subsystem (IMS).
17. A method according to any of claim to claim 16, wherein said one or more gateways each comprise a Packet Date Network Gateway (P-GW).
18. A method according to any of claim 1 to claim 17, wherein the packet switched data network comprises an Evolved Packet System (EPS).
19. A method of controlling user data transmission between a user equipment and one or more packet data networks (PDN) via a packet switched data network comprising a core network, the core network including one or more gateways, each said gateway being communicatively coupled to said packet data network (PDN), the method comprising: performing ari association process to form an association between a first said gateway and the user equipment, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway; sending, during said association process, an indication from the user equipment to the core network to inhibit transmission of said user data towards said user equipment; receiving a message at said user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between the first gateway and the user equipment; and controlling transmission of user data from said user equipment towards said first gateway in accordance with said one or more predefined parameters.
20. A method according to claim 19, comprising sending said indication from said user equipment based at least in part on said user equipment determining a serving access network is a visited network.
21. A method according to either of claim 1 9and claim 20, comprising sending said indication from said user equipment based at least in part on a user input.
22. A method according to any of claim l9to claim 21, wherein said indication is included in a request message requesting formation of a said association.
23. A method according to claim 22, wherein the indication is included as a request type in the request message.
24. A method according to either of claim 22 and claim 23, wherein said request message includes an indication of a predefined Access Point Name (APN) for which data transmission is inhibited.
25. A method according to any of claim 19 to claim 24, comprising sending, in response to user input, a further indication towards said first gateway, the further indication being an indication to cease said control of transmission of user data.
26. A method according to claim 25, wherein said further indication is included in a Tracking Area Update (TAU). fin Li27. A method according to claim 25, wherein said further indication is included in a Service Request (SR).28. A method according to claim 25, wherein said further indication comprises an indication to terminate said association.29. A gateway for controlling user data transmission between a user equipment and a packet data network (PDN), the gateway being communicatively coupled to the packet data network (PDN), the gateway being arranged to: perform an association process to form an association with the user equipment, thereby enabling transmission of data between the user equipment and the packet data network (PDN) via the gateway; receive as part of a request message from the user equipment requesting formation of said association, during said association process, an indication to inhibit transmission of user data towards said user equipment, and, in response to receipt of said indication to inhibit transmission of data: send a message to the user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between a first said gateway and the user equipment; and control transmission of user data from the first gateway towards said user equipment in accordance with the one or more predefined parameters.30. A user equipment for use with a packet switched data network including a core network, the user equipment being capable of receiving user data from, and sending data to, one or more packet data networks (PDN) via said core network, the core network including one or more gateways, each said gateway being communicatively coupled to a said packet data network, the user equipment being arranged to: perform an association process to form an association with a first said gateway and the user equipment, thereby enabling transmission of data between the user equipment and a first said packet data network (PDN) via the first gateway; send, during said association process, an indication from the user equipment to the core network to inhibit transmission of said user data towards said user equipment; receive a message at said user equipment indicating one or more parameters defining data characteristics of user data that may be transmitted between the first gateway and the user equipment; and control transmission of user data from said user equipment towards said first gateway in accordance with said one or more predefined parameters.31. A user equipment according to claim 30, wherein said user equipment is capable of sending and receiving user data of first and second types, the first type of data comprising voice and Short Message Service (SMS) data, and the second type of data being different from the first type of data, wherein said association with the first gateway enables transmission of data of the second type, and the user equipment is arranged not to form an association with a IS second gateway for enabling transmission of data of the second type.32. A user equipment according to claim 31, wherein said user equipment is arranged to form an association with a third gateway for enabling transmission of data of the first type.