Patent Description:
In cellular networks, e.g., as specified by 3GPP (<NUM>rd Generation Partnership Project), a user equipment (UE) may establish a packet data connection for utilizing certain packet data services, in particular Internet Protocol (IP) based services. Such services may for example be provided by the IMS (IP Multimedia Subsystem) as specified in 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>).

In the LTE (Long Term Evolution) cellular network technology specified by 3GPP, all connectivity is packet based, while other radio access technologies, e.g., <NUM> technologies such as GSM (Global System for Mobile Communications) or <NUM> technologies such as UMTS (Universal Mobile Telecommunication System) also allow circuit switched (CS) connections, e.g., for voice calls or SMS (Short Message Service). In the LTE technology, also voice and SMS need to be provided via packet based connectivity.

However, usage of packet based connectivity is in some cases not desired from a subscriber perspective. For example, a subscriber may have only limited quota for packet data, and exceeding this quota may cause undesired charging. Further, usage of packet based connectivity while roaming may also result in undesired charging. Accordingly, a common practice is to switch the UE in a "data off" state, or "data off when roaming" state.

On a <NUM> or <NUM> access, the selection of "data off" or "data off when roaming" has the effect of disabling usage all packet data connectivity access points, each identified by an APN (Access Point Name), by the UE. Accordingly, no packet data connectivity is established for the UE.

However, on an LTE access suppressing packet data connectivity may render the UE unusable. Further, if the UE does not provide an APN during initial attach, the default APN from the subscription is used to establish a PDN (Packet Data Network) connection. This might be the Internet APN or another APN which that should not be used when "data off" or "data off when roaming" is selected.

Accordingly, there is a need for techniques which allow for efficiently controlling packet based connectivity in a wireless communication network.

<CIT> discloses pre-stage filtering via user definable filter parameters on data being transferred between a communication unit and a communication server. For downloading, e.g., email from a host post office, a communication server controller preferably either forwards the filter parameters in a query object or message to the post office to apply and return qualified mail, or the communication server receives all unprocessed mail and applies the filters locally, only acknowledging as processed that mail which passes the filters. For uploading, e.g., email from a client, a client controller applies an upload pre-stage filter so as to retain all filter rejected email, while transmitting email passing the filters.

<CIT> discloses a communication system including a user equipment (UE) and a gateway. The UE sends data packets on one or more bearers to the gateway. One or more packet filters are installed in the UE for associating the data packets with the bearers. A decision is performed if installation of a new packet filter in the UE is required to map the data packets of indicated data traffic to a particular bearer. The result of the decision may then be indicated from a policy controller to a gateway and/or from the gateway to the UE. Depending on the result of the decision, the gateway may initiate signaling of the new packet filter to the UE and/or the UE may install the new packet filter.

<CIT> discloses method for updating or handling the update of a media path between a first user terminal and a second user terminal in a telecommunications network. The media path includes one or more gateway nodes. Each gateway node includes a gating function for gating media packets. Each gating function has an associated controlling function for controlling the gating function. A message is received at a gating function from its associated controlling function indicating that an update of the gating at the gating function is required. The gating function arranges for a new gating, appropriate for the new or updated media path, to be opened while keeping the old gating, appropriate for the old or previous or existing media path. The gating function determines when the media has been switched, or at least is likely to have been switched, to the new path. When it is so determined, the gating function arranges for the old gating to be closed.

<NPL> discloses Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including 3GPP accesses (GERAN/UTRAN/E-UTRAN) and Non-3GPP accesses.

According to an embodiment of the invention, a method of controlling packet based connectivity in a wireless communication network is provided. According to the method, a node of the wireless communication network receives, from a UE, an indication that a limitation of volume charged packet data services is required for the UE. Depending on the received indication, the node prevents transmission of packet data associated with the volume charged packet data services and allows transmission of packet data associated with one or more other packet data services.

According to a further embodiment of the invention, a method of controlling packet based connectivity in a wireless communication network is provided. According to the method, a UE detects a command to switch off packet data connectivity of the UE. In response to the command, the UE sends, to the wireless communication network, an indication that a limitation of volume charged packet data services is required for the UE.

According to a further embodiment of the invention, a node for a wireless communication network is provided. The node comprises at least one interface. Further, the node comprises at least one processor. The at least one processor is configured to receive, from a UE, an indication that a limitation of volume charged packet data services is required for the UE. Further, the at least one processor is configured to prevent transmission of packet data associated with the volume charged packet data services and allow transmission of packet data associated with one or more other packet data services. This preventing and allowing is accomplished depending on the received indication.

According to a further embodiment of the invention, a UE is provided. The UE comprises an interface for connecting to a wireless communication network. Further, the UE comprises at least one processor. The at least one processor is configured to detect a command to switch off packet data connectivity of the UE. Further, the at least one processor is configured to send to the wireless communication network an indication that a limitation of volume charged packet data services is required for the user equipment, while services not subject to volume charging remain accessible. The user equipment sends the indication in a procedure for attaching the user equipment to the 3GPP wireless communication network.

According to a further embodiment of the invention, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises program code to be executed by at least one processor of a node of a wireless communication network. Execution of the program code causes the at least one processor to receive, from a UE, an indication that the user equipment is in a data off state. The indication is received in a procedure for attaching the user equipment to the wireless communication network. Further, execution of the program code causes the at least one processor to prevent transmission of packet data associated with the volume charged packet data services and allow transmission of packet data associated with one or more other packet data services not subject to volume charging. This preventing and allowing is accomplished depending on the received indication.

According to a further embodiment of the invention, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises program code to be executed by at least one processor of a UE. Execution of the program code causes the at least one processor to detect a command to switch off packet data connectivity of the UE. Further, execution of the program code causes the at least one processor to send to the wireless communication network an indication that the user equipment is in a data off state indicating that a prevention of volume charged packet data services is required for the user equipment, while services not subject to volume charging remain accessible. The user equipment sends the indication in a procedure for attaching the user equipment to the 3GPP wireless communication network.

In the following, concepts according to embodiments of the invention will be explained in more detail by referring to the accompanying drawings. The illustrated concepts relate to control of packet data connectivity in a wireless communication network. In the illustrated embodiments, it is assumed that the wireless communication network is based on the LTE technology as specified by 3GPP. However, it is to be understood that the illustrated concepts could be applied in a corresponding manner to other technologies, e.g., GSM, UMTS, or CDMA2000.

The concepts as illustrated in the following are based on an indication provided by a UE to the wireless communication network. By means of the indication, the UE can indicate that a limitation of volume charged packet data services is required for the UE. The indication has the purpose of preventing transmission of packet data traffic associated with the volume charged packet data services and allowing transmission of packet data traffic associated with one or more other packet data services by one or more nodes the wireless communication network. The UE may provide this indication when it is in a "data off" state or "data off when roaming" state. One or more nodes of the wireless communication network may react to this indication by taking appropriate measures to prevent the transmission of packet data associated with the volume charged packet data services and allowing the transmission of the packet data traffic associated with the one or more other packet data services. For example, a node which is responsible for providing a service to the UE may reject a request associated with the service or inactivate a volume charged component of the service. Further, a node which is responsible for controlling handling of user plane traffic of the UE may apply a policy, e.g., in the form of a packet filter, which blocks the packet data traffic associated with the volume charged services and allows the transmission of the packet data traffic associated with the one or more other packet data services. Such packet filter may for example be installed in a gateway. Further, such packet filter could also be installed in the UE, e.g., to selectively block the volume charged uplink packet data traffic from the UE.

The indication allows for establishing packet data connectivity of the UE while at the same time avoiding undesirable costs for the subscriber. In particular, certain services which are not subject to volume charging, e.g., a voice telephony service, a text based messaging service, or an electronic book service, may remain accessible for the UE, while volume charged services or media components of a service which are subject to volume charging, such as video, are blocked.

Further details of the concepts and exemplary implementations will now be explained with reference to the accompanying drawings.

<FIG> shows a block diagram for schematically illustrating an LTE based communication network architecture for implementation of the concepts as outlined above. As illustrated, the architecture provides an eNB <NUM>, which is an exemplary base station of an access network <NUM>, referred to as evolved UMTS Terrestrial Radio Access Network (E-UTRAN). Further the architecture provides a Mobility Management Entity (MME) <NUM>, a Serving Gateway (SGW) <NUM>, a Packet Data Network Gateway (PGW) <NUM>, a Policy and Charging Rules Function (PCRF), and a Home Subscriber Server (HSS) <NUM>. Further, <FIG> illustrates elements of the IMS, in particular a Telephony Application Server (TAS) <NUM>, an IP television application server (IPTV-AS) <NUM>, a Service Centralization and Continuity Application Server (SCC-AS) <NUM>, and a Call Session Control Function (CSCF) <NUM>.

The MME <NUM> may be responsible for controlling connectivity and managing mobility of UEs in the cellular network. The PCRF <NUM> may be responsible for policing and charging related functionalities, e.g., as specified in 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>). The eNB <NUM>, SGW <NUM>, and the PGW <NUM> carry user plane data traffic of a UE <NUM>. Between the eNB <NUM> and the UE <NUM>, the user plane data traffic is carried over the LTE radio interface. The user plane data traffic is packet based, in particular based on IP data packets. Unless described otherwise below, the eNB <NUM>, the MME <NUM>, the SGW <NUM>, PGW <NUM>, PCRF <NUM>, and HSS <NUM> may operate as specified by 3GPP, e.g., in 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>) or 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>).

The IMS nodes are responsible for providing an controlling various packet data services in the wireless communication network. Examples of such services are packet based voice telephony, packet based multimedia telephony, packet based text or multimedia messaging, or packet based mobile television. In the illustrated architecture, it is assumed that the TAS <NUM> is responsible for providing packet based voice telephony, packet based multimedia telephony, and/or packet based text or multimedia messaging and that the IPTV-AS <NUM> is responsible for providing packet based mobile television. The SCC-AS <NUM> may be responsible for centralized control of such services, e.g., with respect to termination of incoming CS or packets based calls, and for providing session continuity, e.g., when the UE moves between different accesses, in particular between an access supporting CS services and an access supporting backed based services. The CSCF <NUM> may be responsible for controlling sessions of the services, e.g., with respect to establishment of the session, modification of the session, or ending of the session. The CSCF <NUM> may for example act as a Serving CSCF (S-CSCF) for the UE <NUM>, i.e., be located in the home network of the UE <NUM>, or could act as a proxy CSCF (P-CSCF) for the UE <NUM>, i.e., be located in a visited network in which the UE <NUM> is roaming or in the home network. Unless explained otherwise in the following, the functionalities of the IMS nodes may correspond to those as specified in 3GPP TS <NUM> V12.

As illustrated in <FIG>, various interfaces are provided to allow communication in the architecture of <FIG>. For communication between the UE <NUM> and the eNB <NUM>, a radio interface referred to as Uu is provided. For communication between the eNB <NUM> and the SGW <NUM>, an interface referred to as S1-U is provided. For communication between the SGW <NUM> and the PGW <NUM>, an interface referred to as S5/S8 is provided. For communication between the eNB <NUM> and the MME <NUM>, an interface referred to as S1-MME is provided. For communication between the MME <NUM> and the SGW <NUM>, an interface referred to as S11 is provided. For communication between the MME <NUM> and the HSS <NUM>, an interface referred to as S6a is provided. For communication between the PCRF <NUM> and the SGW <NUM>, an interface referred to as Gxc is provided. For communication between the PCRF <NUM> and the PGW <NUM>, an interface referred to as Gx is provided. For communication between the PCRF <NUM> and the HSS <NUM>, an interface referred to as Sp is provided. For communication between the HSS <NUM> and the SCC-AS <NUM>, an interface referred to as Sh is provided. For communication between the HSS <NUM> and the CSCF <NUM>, an interface referred to as Cx is provided. For communication between the CSCF <NUM> and the application servers, i.e., the TAS <NUM>, the SCC AS <NUM>, and the IPTV-AS <NUM>, an interface referred to as ISC is provided. Further, <FIG> illustrates an interface between the UE <NUM> and the application servers, which is referred to as Ut, and an interface between the UE <NUM> and the CSCF <NUM>, which is referred to as Gm (between UE <NUM> and the P-CSCF) and Mw (between the P-CSCF and S-CSCF). These interfaces may be implemented as for example specified in 3GPP TS <NUM> V12. <NUM>, 3GPP TS <NUM> V12. <NUM>, 3GPP TS <NUM> V12. <NUM>, and 3GPP TS <NUM> V12. In accordance with the concepts as illustrated herein, some of these interfaces may be supplemented with a capability to transmit the above-mentioned indication that a limitation of volume charged packet data services is required.

In the following implementations of the concepts based on the indication that a limitation of volume charged packet data services is required will be explained in more detail with reference to the architecture as illustrated in <FIG> and exemplary processes. In these processes, it is assumed that the indication relates to IMS services and has the form "no volume charged IMS services", which may be provided as an additional information element in some of the illustrated messages. However, it should be understood that in other implementations, the indication could also refer to other volume charged packet data services or to volume charged services in general. Accordingly, the indication will also be referred to as "data off" indication. The indication may also further specify that its applies only when the UE is roaming, i.e., be a "data off when roaming" indication. In some implementations, the indication may also specify an access network in which it is applicable, e.g., that the indication is applicable to LTE access, but not to <NUM> or <NUM> accesses, such as GSM or UMTS. The latter additional attributes allow for deciding on the network side whether the indication should be applied for preventing volume charged packet data traffic. In this way, it can be avoided that the UE <NUM> needs to update the indication when changing status, e.g., between roaming to non-roaming or between LTE and another access network, e.g., based on GSM, UMTS, or WLAN (Wireless Local Area Network).

<FIG> illustrates exemplary processes in which an IMS node uses the indication for preventing transmission of volume charged packet data traffic while allowing other packet data traffic. The processes of <FIG> involve the UE <NUM>, the HSS <NUM>, an application server (AS), such as the TAS <NUM>, SCC AS <NUM>, or IPTV-AS <NUM>, and the CSCF <NUM>. In the processes of <FIG>, it is assumed that the UE <NUM> has established a PDN connection to the wireless communication network, using the IMS APN. The UE <NUM> may be in its home network or in a visited network.

By sending message <NUM> to the CSCF <NUM>, the UE <NUM> registers in the IMS. Message <NUM> may be a message of the Session Initiation Protocol (SIP) as specified in IETF RFC <NUM>. The message <NUM> may be conveyed to the CSCF <NUM> via the Gm/Mw interface. The message <NUM> includes the "data off" indication, which is stored by the CSCF <NUM>.

The CSCF <NUM> may then query the HSS <NUM> for subscriber information related to the UE <NUM>, by sending message <NUM> to the HSS <NUM>. Further, message <NUM> may include information for updating the HSS <NUM>. For example, such information may indicate the presence of the "data off" indication, and the HSS <NUM> could this information for future utilization. Message <NUM> may correspond to a Cx Put/Pull message. In message <NUM>, the HSS <NUM> responds with the subscriber information. The messages <NUM> and <NUM> may be transmitted over the Cx interface between the HSS <NUM> and the CSCF <NUM>.

At some point, the UE <NUM> may request an IMS service, by sending message <NUM> to the CSCF <NUM>. Message <NUM> may be a SIP message transmitted between the UE <NUM> and the CSCF <NUM>. As illustrated, message <NUM> may be a SIP request. For example, the UE <NUM> may request establishment of a voice call by the TAS <NUM>, may request establishment of a video call by the TAS <NUM>, or may request establishment of a mobile television session by the IPTV-AS <NUM>. Upon receiving the message <NUM>, the CSCF <NUM> may for example perform processes for authorizing the requested IMS service.

In message <NUM>, the CSCF <NUM> forwards the request of message <NUM> to the AS <NUM>, <NUM>. In message <NUM>, the CSCF <NUM> may indicate whether the requested service is authorized and also which media components of the service are authorized. This information may depend on the "data off" indication from the UE <NUM>. For example, if the service is completely based on volume charged packet data traffic, the CSCF <NUM> may decide to not authorize the requested service. Further, if the service is partially based on volume charged packet data traffic, the CSCF <NUM> may decide to authorize only media components which are not subject to volume charging. Still further, if the service is completely based on packet data traffic which is not subject to volume charging, it may decide to authorize the service with all media components. As illustrated, also the "data off" indication may be forwarded in message <NUM>.

This allows the AS <NUM>, <NUM>, <NUM> to decide whether the service or components thereof are allowable or not.

As illustrated, message <NUM> may be a SIP request. The AS <NUM>, <NUM>, <NUM> responds to the request of message <NUM> by sending message <NUM>, which may be a SIP response, to the CSCF <NUM>.

In particular, the AS <NUM>, <NUM>, <NUM> may decide to reject the request of message <NUM>. This may for example be the case if the information in message <NUM> indicates that the service or all media components of the service are not authorized. Further, the AS <NUM>, <NUM>, <NUM> may take this decision on the basis of the "data off" indication, even if at least some components of the service are authorized by the CSCF <NUM>. Further, the AS <NUM>, <NUM>, <NUM> may accept the request of message <NUM>. This may for example be the case if the information in message <NUM> indicates that the service or at least some media components of the service are authorized. On the basis of the response in message <NUM>, the CSCF <NUM> sends message <NUM> to the UE <NUM> to indicate the result of the decision by the AS <NUM>, <NUM>, <NUM> and/or by the CSCF <NUM>. As illustrated, message <NUM> may be a SIP response message.

If at least some media components of the service are authorized, the AS <NUM>, <NUM>, <NUM> may then continue with the provision of the service to the UE <NUM>, e.g., by sending packet data traffic associated with the service to the UE <NUM> and/or receiving packet data traffic associated with the service from the UE <NUM>.

The following exemplary rules may be applied in the processes of <FIG>: If the "data off" indication was provided by the UE <NUM>, the IMS node <NUM>, <NUM>, <NUM>, <NUM> responsible for the decision may disallow services with video media and filer transfers, but allow voice media and text messaging. As an alternative to disallowing all video media, the IMS node <NUM>, <NUM>, <NUM>, <NUM> may allow certain video media which is not subject to volume charging, such as video media according to GSMA IR. <NUM> (March <NUM>, <NUM>). If the "data off" indication is not provided by the UE <NUM>, the IMS node <NUM>, <NUM>, <NUM>, <NUM> may allow services and media components of these services, provided that there are no other reasons for disallowing some service or media components thereof.

The AS <NUM>, <NUM>, <NUM> may for example implement such policy by inactivating a disallowed media component, e.g., by modifying Session Description Protocol (SDP) information of the requested service. For example, the TAS <NUM> may inactivate video media from a request to establish a video call. Further, as mentioned above, the AS <NUM>, <NUM>, <NUM> may also reject requests, e.g., requests for file transfer or video transmission. For example, the IPTV-AS <NUM> could reject a request for streaming a video. In the case of rejecting a request, the originator of the request may be informed about the reason of rejection. In the exemplary scenario of <FIG>, the UE <NUM> is the originator of the request of message <NUM> and may thus be informed of the rejection (and its reason) in message <NUM>. However, it should be understood that in some cases the request for a service may also come from other entities than the UE <NUM>. For example, in the case of a incoming call to be terminated at the UE <NUM>, the request could originate from another AS. The CSCF <NUM> may implement such policy by not authorizing and inactivating services or media components of services which are subject to volume charging. For example, the CSCF <NUM> may authorize voice media and inactivate other media components, such as video. In some scenarios, it is also possible that separate nodes implement different parts of such policy. For example, an AS that handles voice and video calls may implement only the video related part of the policy, and another AS may implement the file transfer related part of the policy.

In the exemplary processes of <FIG>, the "data off" indication is provided at IMS registration over the Gm/Mw interface. Alternatively or in addition, the "data off" indication could also be provided or updated over the Ut interface, i.e., directly to the AS <NUM>, <NUM>, <NUM>. For example, the UE <NUM> may update the indication when changing between roaming and non-roaming status. Further, while in the processes of <FIG> the AS <NUM>, <NUM>, <NUM> may receive the "data off" indication from the CSCF <NUM> when an IMS service is requested, it would also be possible that the CSCF <NUM> already informs the AS <NUM>, <NUM>, <NUM> of the "data off" indication at IMS registration, similar to the HSS <NUM>. Further, the AS <NUM>, <NUM>, <NUM> could also obtain the information concerning the "data off" indication from the HSS <NUM>.

<FIG> illustrates exemplary processes in which the indication is applied by one or more in a policy and charging control (PCC) nodes of the communication network for preventing transmission of volume charged packet data traffic while allowing other packet data traffic. The processes of <FIG> involve the UE <NUM>, the eNB <NUM>, the MME <NUM>, the SGW <NUM>, the PGW <NUM>, the PCRF <NUM>, and the HSS <NUM>. In the processes of <FIG>, the UE <NUM> initially attaches to the wireless communication network to establish a PDN connection.

At step <NUM>, the UE <NUM> powers on. This is assumed to occur the coverage region of a cell served by the eNB <NUM>. Having selected this cell, the UE <NUM> continues by performing a random access procedure, as illustrated by step <NUM>, and setting up a RRC (Radio Resource Control) connection. The RRC setup procedure involves that the UE <NUM> sends a message <NUM>, referred to as RRCConnectionRequest, to the eNB <NUM>, and that the eNB <NUM> responds with a message <NUM>, referred to as RRCConnectionSetup. The UE <NUM> then sends message <NUM>, referred to as RRCConnectionSetupComplete, to the eNB <NUM>. The RRCConnectionSetupComplete message <NUM> includes initial NAS (Non Access Stratum) information to be provided to the eNB <NUM>, in the present illustrated example a NAS Attach Request. The NAS attach request includes the above-mentioned "data off" indication. Details concerning the RRC connection procedure may be as for example specified in 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>). Details of the NAS attach procedure and associated messages may be as for example specified in 3GPP TS <NUM> V12.

The eNB <NUM> forwards the initial NAS information, i.e., the NAS attach request with the "data off" indication, to the MME <NUM>.

As illustrated by <NUM>, the MME <NUM> may then update the HSS <NUM>. This may involve sending an Update Location Request, e.g., as specified in 3GPP TS <NUM>. This may also involve updating the HSS <NUM> with the information that the UE <NUM> provided the "data off" indication.

Further, the MME <NUM> sends a Create Session Request via the SGW <NUM> to the PGW <NUM>, as illustrated by messages <NUM> and <NUM>. In the illustrated implementation, the Create Session Request is used to forward the "data off" indication to the SGW <NUM> and PGW <NUM>. Otherwise, the Create Session Request may be as specified in 3GPP TS <NUM> V12.

In the exemplary processes of <FIG>, it is assumed that dynamic PCC is used. Accordingly, the PGW <NUM> contacts the PCRF <NUM> to create a policy control session over the Gx interface. In the exemplary procedures of <FIG>, this is assumed to involve sending a Credit Control Request (CCR) <NUM> from the PGW <NUM> to the PCRF <NUM>. By means of the CCR <NUM>, the "data off" indication is forwarded to the PCRF <NUM>. Depending on the indication, the PCRF <NUM> determines a PCC rule, according to which packet data traffic subject to volume charging is blocked for the UE <NUM>, while other packet data traffic is allowed. In the following, this PCC rule will also be referred to as "data off" (DO) policy. This DO policy may in particular indicate or be used to configure a packet filter which blocks the volume charged packet data traffic and passes other packet data traffic. Such packet filter may be implemented as a correspondingly configured traffic flow template (TFT), as for example specified in 3GPP TS <NUM> V12. <NUM> (<NUM>-<NUM>). The DO policy or packet filter may also be determined in an APN specific manner. That is to say, different APNs may be associated with different APN policies. For example, only for the IMS APN some packet data traffic not subject to volume charging may be allowed, while for other APNs all packet data traffic is blocked when the "data off" indication is provided by the UE <NUM>.

The PCRF <NUM> then responds to the CCR <NUM> by sending a Credit Control Answer (CCA) <NUM> to the PGW <NUM>. The CCA <NUM> is also used to indicate the DO policy to the PGW <NUM>. As illustrated by step <NUM>, the PGW <NUM> may implement the DO policy by installing the corresponding packet filter. Alternatively, the PGW <NUM> may configure an existing packet filter in accordance with the indicated DO policy.

The PGW <NUM> then sends a Create Session Response via the SGW <NUM> to the MME <NUM>, as illustrated by messages <NUM> and <NUM>. In the illustrated implementation, the Create Session Response is used to forward the DO policy to the SGW <NUM> and to the MME <NUM>. Otherwise, the Create Session Response may be as specified in 3GPP TS <NUM> V12. Having received message <NUM>, i.e., the Create Session Response with the DO policy, the SGW <NUM> may install the corresponding packet filter, as indicated by step <NUM>.

The MME <NUM> then sends a Context Setup Request to the eNB <NUM>, as indicated by message <NUM>. The Context Setup Request is used to forward the DO policy to the eNB <NUM>. Otherwise, the Context Setup Request may be as specified in 3GPP TS <NUM> V12.

The eNB <NUM> then sends an RRCConnectionReconfig message <NUM> to the UE <NUM>. The RRCConnectionReconfig message <NUM> may for example be in accordance with 3GPP TS <NUM> V12. The RRCConnectionReconfig message <NUM> includes a NAS Attach Accept message which is a response to the NAS Attach Request in the RRCConnectionSetupComplete message <NUM>. The NAs Attach Request is used for forwarding the DO policy to the UE <NUM>.

Having received the RRCConnectionReconfig message <NUM> with the DO policy, the UE <NUM> may install the corresponding packet filter, as indicated by step <NUM>.

It is to be understood that further processes, not illustrated in <FIG>, may be part of a typical initial attach procedure, such as specified in 3GPP TS <NUM> V12. For example, processes for configuring the default bearer or an additional bearer may be included. Further, rather than using dynamic PCC mechanisms, the DO policy could also be statically or preconfigured in the UE <NUM>, SGW <NUM>, and/or PGW <NUM>, e.g., by a management procedure. Such preconfigured DO policy may be activated when the "data off" indication is provided by the UE <NUM>.

In some scenarios, the UE <NUM> may use different APNs, each for different services. Accordingly, a new PDN connection may need to be established for some services. <FIG> illustrates exemplary processes which use a PCC mechanism similar to the processes of <FIG>, but in which the "data off" indication is provided in a PDN connection establishment procedure. The processes of <FIG> involve the UE <NUM>, the MME <NUM>, the SGW <NUM>, the PGW <NUM>, and the PCRF <NUM>.

To establish the PDN connection, the UE <NUM> sends a PDN Connectivity Request <NUM>. The PDN Connectivity Request is used for providing the "data off" indication to the MME <NUM>. Otherwise, the PDN Connectivity Request may be as for example specified in 3GPP TS <NUM> V12.

The MME <NUM> then sends a Create Session Request via the SGW <NUM> to the PGW <NUM>, as illustrated by messages <NUM> and <NUM>. In the illustrated implementation, the Create Session Request is used to forward the "data off" indication to the SGW <NUM> and the PGW <NUM>. Otherwise, the Create Session Request may be as specified in 3GPP TS <NUM> V12.

The PGW <NUM> the contacts the PCRF <NUM> to create a policy control session over the Gx interface for the new PDN connection. In the exemplary procedures of <FIG>, this is assumed to involve sending a Authentication/Authorization Request (AAR) <NUM> from the PGW <NUM> to the PCRF <NUM>. By means of the AAR <NUM>, the "data off" indication is forwarded to the PCRF <NUM>. Depending on the indication, the PCRF <NUM> determines a PCC rule, according to which packet data traffic subject to volume charging is blocked for the UE <NUM>, while other packet data traffic is allowed, i.e., a DO policy. This DO policy may in particular indicate or be used to configure a packet filter which blocks the volume charged packet data traffic and passes other packet data traffic. Such packet filter may be implemented as a correspondingly configured TFT. The DO policy or packet filter may also be determined in an APN specific manner. That is to say, different APNs may be associated with different APN policies. For example, for one APN certain packet data traffic not subject to volume charging may be allowed, while for other APNs other packet data traffic not subject to volume charging may be allowed.

The PCRF <NUM> then responds to the AAR <NUM> by sending an Authentication/Authorization Answer (AAA) <NUM> to the PGW <NUM>. The AAA <NUM> is also used to indicate the DO policy to the PGW <NUM>. As illustrated by step <NUM>, the PGW <NUM> may implement the DO policy by installing the corresponding packet filter. Alternatively, the PGW <NUM> may configure an existing packet filter in accordance with the indicated DO policy.

The MME <NUM> then sends a PDN Connectivity Accept message <NUM> UE <NUM>. The PDN Connectivity Accept message <NUM> is used to forward the DO policy to the UE <NUM>. Otherwise, the PDN Connectivity Accept message <NUM> may be as specified in 3GPP TS <NUM> V12.

Having received the PDN Connectivity Accept message <NUM> with the DO policy, the UE <NUM> may install the corresponding packet filter, as indicated by step <NUM>.

Further, the UE <NUM> may send a PDN Connectivity Complete message <NUM> to the MME <NUM>, thereby confirming establishment of the new PDN connection. The MME <NUM> may then send a Modify Bearer Request <NUM> to the SGW <NUM>, which the SGW <NUM> may confirm by sending a Modify Bearer Response <NUM>. These procedures may for example be as specified in 3GPP TS <NUM>.

Also in the processes of <FIG>, a preconfigured DO policy could be used in place of the dynamically DO policy.

After having provided the "data off" indication, the state of the UE <NUM> may change to a normal state, in which full packet data connectivity of the UE <NUM> is desired. Also this change of the "data off" indication may be indicated by the UE <NUM> to the wireless communication network. In scenarios where the prevention of the transmission of volume charged data traffic is implemented by an IMS node, such as in the processes of <FIG>, this may be achieved by an update procedure initiated by the UE <NUM>, e.g., by a Tracking Area Update. In scenarios where the prevention of the transmission of volume charged data traffic is implemented by a DO policy, such as in the processes of <FIG> or <FIG>, this may be achieved by the UE <NUM> sending a request or other message to the MME <NUM>. In this request, the change of the "data off" state may be indicated implicitly, by not including the "data off" indication, or may be indicated by an explicit "data on" indication. The MME <NUM> may then forward this information to the SGW <NUM>, PGW <NUM> and PCRF <NUM>, by sending a Modify Bearer Request which includes a corresponding indication (or in which the "data off" indication is omitted).

<FIG> shows a flowchart for illustrating a method of controlling packet data connectivity in a wireless communication network. The method of <FIG> may be used for implementing the above concepts in a node of the wireless communication network, in particular in a node which is responsible for providing a packet data service, e.g. an application server such as the TAS <NUM>, the IPTV-AS <NUM>, or the SCC-AS <NUM>, or in a node which is responsible for authorizing a packet data service, e.g., a CSCF such as the CSCF <NUM>. If a processor based implementation of the node is used, the steps of the method may be performed by one or more processors of the node. For this purpose, the processor(s) may execute correspondingly configured program code. Further, at least some of the corresponding functionalities may be hardwired in the processor(s).

At step <NUM>, the node receives an indication from a UE, e.g., from the UE <NUM>. The indication indicates that a limitation of volume charged packet data services is required for the UE. The indication may indicate that none of the volume charged packet data services are allowed for the UE, such as the above-mentioned "data off" indication. Alternatively, the indication may indicate that none of the volume charged packet data services are allowed while the UE <NUM> is roaming, such as the above-mentioned "data off when roaming" indication. In some implementations, the indication may further indicate one or more access networks in which the indication is applicable, e.g., that the indication is applicable for LTE access networks, but not for <NUM> or <NUM> access networks. The volume charged services may for example correspond to services of an IMS of the wireless communication system. The indication may be provided in a procedure for registering for the volume charged packet data services, e.g., during IMS registration or in a procedure of updating IMS registration.

Depending on the received indication, the node prevents transmission of packet data traffic associated with the volume charged packet data services and allows transmission of packet data traffic associated with one or more other packet data services. In the method of <FIG>, this involves that the node controls provision or authorization of at least one of the volume charged packet data services in accordance with the received indication.

In particular, at step <NUM> the node may receive a request associated with at least one of the volume charged packet data services. For example, the node may be an application server which is responsible for providing the at least one volume charged packet data service, such as one of the application servers <NUM>, <NUM>, <NUM>, and the request may be a request for establishing a session of the at least one volume charged packet data service. An example of such request is the SIP request <NUM> in the processes of <FIG>. Alternatively, the node may be a control server which is responsible for authorizing the at least one volume charged packet data service, such as the CSCF <NUM>, and the request may be a request for authorization of a session of the volume charged packet data service. An example of such request is the SIP request <NUM> in the processes of <FIG>.

At step <NUM>, in response to the indication provided by the UE, the node prevents the transmission of the packet data traffic associated with the at least one volume charged packet data service. For this purpose, the node may reject the request of step <NUM> or inactivate a media component of the at least one of the volume charged service requested for the UE.

<FIG> shows a flowchart for illustrating a further method of controlling packet data connectivity. The method of <FIG> may be used for implementing the above concepts in a node of a wireless communication network, in particular in a node which is responsible for controlling packet data traffic, e.g., a gateway such as the SGW <NUM> or PGW <NUM>, or a policy controller, such as the PCRF <NUM>. If a processor based implementation of the node is used, the steps of the method may be performed by one or more processors of the node. For this purpose, the processor(s) may execute correspondingly configured program code. Further, at least some of the corresponding functionalities may be hardwired in the processor(s).

At step <NUM>, the node receives an indication from a UE, e.g., from the UE <NUM>. The indication indicates that a limitation of volume charged packet data services is required for the UE. The indication may indicate that none of the volume charged packet data services are allowed for the UE, such as the above-mentioned "data off" indication. Alternatively, the indication may indicate that none of the volume charged packet data services are allowed while the UE <NUM> is roaming, such as the above-mentioned "data off when roaming" indication. In some implementations, the indication may further indicate one or more access networks in which the indication is applicable, e.g., that the indication is applicable for LTE access networks, but not for <NUM> or <NUM> access networks. The volume charged services may for example correspond to services of an IMS of the wireless communication system. The node may receive the indication in a request of a procedure for attaching the UE to the wireless communication network. Alternatively or in addition, the node may receive the indication in a request of a procedure for configuring packet data network connectivity between the UE and the wireless communication network.

Depending on the received indication, the node prevents transmission of packet data traffic associated with the volume charged packet data services and allows transmission of packet data traffic associated with one or more other packet data services. In the method of <FIG>, this involves that the node controls traffic handling in the wireless communication network, e.g., using a PCC mechanism.

In particular, at step <NUM> the node may configure at least one packet filter to prevent the transmission of the data traffic associated with the volume charged packet data services. The at least one packet filter blocks the packet data traffic associated with the volume charged packet data services and passes the packet data traffic associated with the one or more other packet data services. The at least one packet filter may operate in the node. That is to say, the node may also install the at least one packet filter, as indicated by step <NUM>. For example, the PGW <NUM> could configure and locally install the at least one packet filter. Alternatively or in addition, the at least one packet filter may operate in a further node of the wireless communication network. The node may then indicate the at least one packet filter to such further node, as indicated by step <NUM>. For example, the node may correspond to the PCRF <NUM> and indicate the at least one packet filter to the PGW <NUM> and/or SGW <NUM>. Alternatively or in addition, the at least one packet filter may operate in the UE. The node may then indicate the at least one packet filter to the UE, as indicated by step <NUM>. For example, the node may correspond to the PCRF <NUM>, PGW <NUM>, or SGW <NUM>, and indicate the packet filter to the UE <NUM>.

<FIG> shows a flowchart for illustrating a further method of controlling packet data connectivity. The method of <FIG> may be used for implementing the above concepts in a UE, such as the UE <NUM>. If a processor based implementation of the UE is used, the steps of the method may be performed by one or more processors of the UE. For this purpose, the processor(s) may execute correspondingly configured program code. Further, at least some of the corresponding functionalities may be hardwired in the processor(s).

At step <NUM>, the UE detects a command to switch off packet data connectivity of the UE. This command may be based on a user selection, e.g., a selection of "data off" or "data off when roaming". Alternatively, this command could be generated by an automatic process in the UE, e.g., a scheduled switching between "data off" and "data on" states or a process in which the command is triggered by a mobility event, such as entry of a visited network or attaching to a certain access network, such as an LTE access network.

At step <NUM>, in response to the command of step <NUM>, the UE sends an indication to the wireless communication network. The indication indicates that a limitation of volume charged packet data services is required for the UE. The indication may indicate that none of the volume charged packet data services are allowed for the UE, such as the above-mentioned "data off" indication. Alternatively, the indication may indicate that none of the volume charged packet data services are allowed while the UE <NUM> is roaming, such as the above-mentioned "data off when roaming" indication. In some implementations, the indication may further indicate one or more access networks in which the indication is applicable, e.g., that the indication is applicable for LTE access networks, but not for <NUM> or <NUM> access networks. The volume charged services may for example correspond to services of an IMS of the wireless communication system. The UE may send the indication in a request of a procedure for attaching the user equipment to the wireless communication network. Alternatively or in addition, the UE may send the indication in a a procedure for configuring packet data network connectivity between the UE and the wireless communication network. Still further, the UE may send the indication in a procedure for registering the UE for at least one of the volume charged packet data services.

At step <NUM>, in response to sending the indication, the UE may receive an indication of a packet filter and install the packet filter at step <NUM>. The packet filter blocks the packet data traffic associated with the volume charged packet data services and passing the packet data traffic associated with the one or more other packet data services.

<FIG> illustrates exemplary structures for implementing the above concepts in a node of a wireless communication network. For example, the illustrated structures may be used to implement an application server, e.g., an IMS application server such as the TAS <NUM>, the IPTV-AS <NUM>, or the SCC-AS <NUM>, or a control function related to a packet data service, such as the CSCF <NUM>.

In the illustrated example, the node includes an interface <NUM> for providing or controlling a packet data service. For example, the interface <NUM> may correspond to a SIP based interface, such as Gm or Mw interface as illustrated in the architecture of <FIG>.

Further, the node includes one or more processor(s) <NUM> coupled to the interface <NUM>, and a memory <NUM> coupled to the processor(s) <NUM>. The memory <NUM> may include a read-only memory (ROM), e.g., a flash ROM, a random access memory (RAM), e.g., a dynamic RAM (DRAM) or static RAM (SRAM), a mass storage, e.g., a hard disk or solid state disk, or the like. The memory <NUM> includes suitably configured program code modules to be executed by the processor(s) <NUM> so as to implement the above-described functionalities of the node, e.g., corresponding to the method steps of <FIG>. More specifically, the program code modules in the memory <NUM> may include a service handling module <NUM> so as to implement the above-described functionalities of providing or authorizing the packet data service. Further, the program code modules in the memory <NUM> may include a communication module <NUM> so as to implement the above-described functionalities of receiving the "data off" indication. Still further, the memory <NUM> may include a "data off" policy handling module <NUM> so as to implement the above-mentioned functionalities of selectively preventing the transmission of the packet data traffic subject to volume charging in response to receiving the "data off" indication, e.g., by rejecting a request associated with the packet data service subject to volume charging or inactivating a media component of the packet data service.

It is to be understood that the structures as illustrated in <FIG> are merely schematic and that the node may actually include further components which, for the sake of clarity, have not been illustrated, e.g., further interfaces or further processors. Also, it is to be understood that the memory <NUM> may include further types of program code modules, which have not been illustrated, e.g., program code modules for implementing known functionalities of an application server or control server, such as an IMS application server or CSCF. In some implementations, also a computer program may be provided for implementing functionalities of the node, e.g., in the form of a physical medium storing the program code modules to be stored in the memory <NUM> or by making such program code available for download or streaming.

<FIG> illustrates exemplary structures for implementing the above concepts in a node of a cellular network. For example, the illustrated structures may be used to implement a node which controls handling of user plane traffic, e.g., a PCC node such as the SGW <NUM>, the PGW <NUM>, or the PCRF <NUM>.

In the illustrated example, the node includes a first traffic interface <NUM> for communication with one or more UEs and a second traffic interface <NUM> for communication with other network nodes. The first and second interfaces <NUM>, <NUM> may in particular have the purpose of conveying user plane traffic of one or more UEs, such as the UE <NUM>. Further, the node includes a control interface <NUM>, which may be used for controlling the handling of user plane traffic. If the node corresponds to a PGW, such as the PGW <NUM>, the control interface <NUM> may correspond to the Gx interface as illustrated in the architecture of <FIG>. If the node corresponds to an SGW, such as the SGW <NUM>, the control interface <NUM> may correspond to the Gxc interface as illustrated in the architecture of <FIG>. If the node corresponds to a policy controller, such as the PCRF <NUM>, the control interface <NUM> may correspond to the Gx and/or Gxc interface as illustrated in the architecture of <FIG>. In the latter case, the traffic interfaces <NUM> and <NUM> may be omitted.

Further, the node includes one or more processor(s) <NUM> coupled to the interfaces <NUM>, <NUM> and <NUM>, and a memory <NUM> coupled to the processor(s) <NUM>. The memory <NUM> may include a ROM, e.g., a flash ROM, a RAM, e.g., a DRAM or SRAM, a mass storage, e.g., a hard disk or solid state disk, or the like. The memory <NUM> includes suitably configured program code modules to be executed by the processor(s) <NUM> so as to implement the above-described functionalities of the node, e.g., corresponding to the method steps of <FIG>. More specifically, the program code modules in the memory <NUM> may include a PCC module <NUM> so as to implement functionalities of controlling the handling of user plane traffic of one or more UEs, e.g., on the basis of a PCC mechanism. Further, the program code modules in the memory <NUM> may include a communication module <NUM> so as to implement the above-described functionalities of receiving the "data off" indication. Still further, the memory <NUM> may include a "data off" policy handling module <NUM> so as to implement the above-mentioned functionalities of selectively preventing the transmission of the packet data traffic subject to volume charging in response to receiving the "data off" indication, e.g., by configuring or installing at least one packet filter which blocks the packet data traffic associated with the volume charged packet data service while passing other packet data traffic.

It is to be understood that the structures as illustrated in <FIG> are merely schematic and that the node may actually include further components which, for the sake of clarity, have not been illustrated, e.g., further interfaces or further processors. Also, it is to be understood that the memory <NUM> may include further types of program code modules, which have not been illustrated, e.g., program code modules for implementing known functionalities of a PCC node, such as an PCRF, PGW, or SGW. In some implementations, also a computer program may be provided for implementing functionalities of the node, e.g., in the form of a physical medium storing the program code modules to be stored in the memory <NUM> or by making such program code available for download or streaming.

<FIG> illustrates exemplary structures for implementing the above concepts in a UE for a wireless communication network, such as the UE <NUM>.

In the illustrated example, the UE includes a radio interface <NUM> for connecting to the wireless communication network. The radio interface <NUM> may for example be based on a packet based cellular radio technology, such as the LTE radio access technology. As further illustrated, the UE may include a user interface <NUM>, e.g., based on keys, a touch-sensitive surface, an optical display, and/or an acoustic input or output. The user interface <NUM> may for example be used for selection of the "data off" state by a user of the UE.

Further, the node includes one or more processor(s) <NUM> coupled to the radio interface <NUM> and to the user interface <NUM>, and a memory <NUM> coupled to the processor(s) <NUM>. The memory <NUM> may include a ROM, e.g., a flash ROM, a RAM, e.g., a DRAM or SRAM, a mass storage, e.g., a hard disk or solid state disk, or the like. The memory <NUM> includes suitably configured program code modules to be executed by the processor(s) <NUM> so as to implement the above-described functionalities of the UE, e.g., corresponding to the method steps of <FIG>. More specifically, the program code modules in the memory <NUM> may include a "data off" state management module <NUM> so as to implement functionalities of managing selection of the "data off" state, e.g., in response to a user selection via the user interface <NUM> or in response to an automatic process, e.g., based on a schedule or triggering event. Further, the program code modules in the memory <NUM> may include a communication module <NUM> so as to implement the above-described functionalities of sending the "data off" indication. Still further, the memory <NUM> may include a PCC module <NUM> so as to implement the above-mentioned functionalities of installing a packet filter which blocks the packet data traffic associated with the volume charged packet data service while passing other packet data traffic.

It is to be understood that the structures as illustrated in <FIG> are merely schematic and that the UE may actually include further components which, for the sake of clarity, have not been illustrated, e.g., further interfaces or further processors. Also, it is to be understood that the memory <NUM> may include further types of program code modules, which have not been illustrated, e.g., program code modules for implementing known functionalities of a UE. In some implementations, also a computer program may be provided for implementing functionalities of the node, e.g., in the form of a physical medium storing the program code modules to be stored in the memory <NUM> or by making such program code available for download or streaming.

As can be seen, the concepts as described above may be used for efficiently controlling packet based connectivity in a wireless communication network. In particular, the concepts may be used for allowing appropriate usage of an access which offers only packet based connectivity, such as an LTE access, while at the same time avoiding undesired volume-charged traffic.

It is to be understood that the examples and embodiments as explained above are merely illustrative and susceptible to various modifications. For example, the prevention of volume charged packet data traffic implemented by an IMS node or the like, such as illustrated by the processes of <FIG>, could be combined with the prevention of volume charged traffic by a PCC mechanism, such as illustrated by the processes of <FIG> and <FIG>. Further, various mechanisms could be used for providing the "data off" indication. For example, providing the indication during an attach procedure, as illustrated in <FIG>, or a radio connectivity configuration procedure, as illustrated in <FIG>, could also be used for conveying the indication to an IMS node by providing the indication to the HSS <NUM>, from where it can be retrieved by the IMS node. Similarly, providing the indication during IMS registration or some other SIP procedure, as illustrated in <FIG>, could also be used for conveying the indication to a PCC node by providing the indication to the HSS <NUM>, from where it can be retrieved by the PCC node.

Claim 1:
A method of controlling packet data connectivity in a 3GPP wireless communication network, the method comprising:
a node (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) of the 3GPP wireless communication network receiving, from a user equipment (<NUM>), an indication that the user equipment (<NUM>) is in a data off state; wherein the node (<NUM>; <NUM>; <NUM>) receives the indication in a procedure for attaching the user equipment (<NUM>) to the 3GPP wireless communication network; and
depending on the received indication, the node (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) preventing transmission of packet data traffic associated with volume charged packet data services to the user equipment and allowing transmission of packet data traffic associated with one or more other packet data services not subject to volume charging to the user equipment.