Packet data connectivity control with pay-per-use service restriction

Abstract

Packet data connectivity control with metered service restriction. A node (150; 160; 170; 210; 220; 230; 240) of a wireless communication network receives an indication from a user equipment (10). The indication indicates that the user equipment (10) requires restriction of a metered packet data service. Depending on the received indication, the node (150; 160; 170; 210; 220; 230; 240) prevents transmission of packet data associated with the metered packet data service and allows transmission of packet data associated with one or more other packet data services.

Description

Technical Field

[0001] The invention relates to a method for packet data connectivity and to a corresponding device. Background Art

[0002] In a cellular network, such as that specified by 3GPP (3rd Generation Partnership Project), a user equipment (UE) may establish a packet data connection for utilizing certain packet data services, in particular services based on the Internet Protocol (IP). Such services may be provided, for example, by the IMS (IP Multimedia Subsystem), as specified in 3GPP TS 23.228 V12.4.0 (2014-03).

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

[0004] However, using packet-based connectivity is undesirable from a subscriber perspective in some cases. For example, a subscriber may only have a limited quota for packet data, and exceeding this quota may result in unexpected charges. In addition, using packet-based connectivity when roaming may also result in unexpected charges. Thus, a common practice is to switch the UE to a "data off" state, or a "data off when roaming" state.

[0005] On 2G or 3G access, selecting "Data Off" or "Data Off When Roaming" has the effect of prohibiting the UE from using all packet data connectivity access points, each identified by an APN (Access Point Name). Thus, no packet data connectivity is established for the UE.

[0006] However, on LTE access, suppressing packet data connectivity may render the UE unavailable. In addition, if the UE does not provide an APN during the initial attach, a PDN (Packet Data Network) connection is established using a default APN from the subscription. This may be an Internet APN or another APN that should not be used when "Data Off" or "Data Off When Roaming" is selected.

[0007] Thus, a need exists for techniques that allow for efficient control of packet-based connectivity in wireless communication networks. Summary of the invention

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

[0009] According to another embodiment of the present invention, a method for controlling packet-based connectivity in a wireless communication network is provided. According to the method, a UE detects a command to cut off the packet data connectivity of the UE. In response to the command, the UE sends an indication to the wireless communication network that the UE requires restriction of a pay-as-you-go packet data service.

[0010] According to another embodiment of the present invention, a node for a wireless communication network is provided. The node includes at least one interface. In addition, the node includes at least one processor. The at least one processor is configured to receive from a UE an indication that the UE requires a restriction of a charge-by-volume packet data service. In addition, the at least one processor is configured to prevent the transmission of packet data associated with the charge-by-volume packet data service and allow the transmission of packet data associated with one or more other packet data services. This prevention and allowing is completed depending on the received indication.

[0011] According to another embodiment of the present invention, a UE is provided. The UE includes an interface for connecting to a wireless communication network. In addition, the UE includes at least one processor. The at least one processor is configured to detect a command to cut off the packet data connectivity of the UE. In addition, the at least one processor is configured to send an indication to the wireless communication network that the UE requires a restriction of a pay-per-use packet data service. This sending is completed in response to the command.

[0012] According to another embodiment of the present invention, a computer program or computer program product (e.g., in the form of a non-transitory storage medium) is provided, which includes program code to be executed by at least one processor of a node of a wireless communication network. The execution of the program code causes the at least one processor to receive an indication from a UE that the UE requires a restriction of a packet data service that is charged by volume. In addition, the execution of the program code causes the at least one processor to prevent the transmission of packet data associated with the packet data service that is charged by volume, and to allow the transmission of packet data associated with one or more other packet data services. This prevention and allowing is completed depending on the received indication.

[0013] According to another embodiment of the present invention, a computer program or computer program product (e.g., in the form of a non-transitory storage medium) is provided, which includes program code to be executed by at least one processor of a UE. The execution of the program code causes the at least one processor to detect a command to cut off the packet data connectivity of the UE. In addition, the execution of the program code causes the at least one processor to send an indication to the wireless communication network that the UE requires a restriction of the packet data service charged by volume. This sending is completed in response to the command.

[0014] Details of such and additional embodiments will become apparent from the following detailed description of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An exemplary architecture in which packet data connectivity control may be implemented according to an embodiment of the present invention is schematically illustrated.

[0016] Figure 2 An exemplary process according to an embodiment of the present invention is schematically illustrated.

[0017] Figure 3 Further exemplary processes according to embodiments of the present invention are schematically illustrated.

[0018] Figure 4 Further exemplary processes according to embodiments of the present invention are schematically illustrated.

[0019] Figure 5 A flow chart is shown for illustrating a method according to an embodiment of the present invention, which may be implemented by an IMS node, for example.

[0020] Figure 6 A flow chart is shown for illustrating a further method according to an embodiment of the present invention, which may be implemented, for example, by a node controlling user plane data traffic handling.

[0021] Figure 7 A flow chart is shown for illustrating a further method according to an embodiment of the present invention, which may be implemented by a UE, for example.

[0022] Figure 8 The structure of a node according to an embodiment of the present invention is schematically illustrated (for example, corresponding to an IMS node).

[0023] Fig. 9 The structure of a node according to an embodiment of the present invention is schematically illustrated (eg, a node corresponding to controlling user plane data service handling).

[0024] Fig.10 The structure of a UE according to an embodiment of the present invention is schematically illustrated. DETAILED DESCRIPTION

[0025] In the following, the concepts according to the embodiments of the present invention will be described in more detail with reference to the accompanying drawings. The illustrated concepts relate to the 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 specified by 3GPP. However, it is to be understood that the illustrated concepts may be applied to other technologies (e.g. GSM, UMTS or CDMA2000) in a corresponding manner.

[0026] The concept as illustrated below is based on an indication provided by the UE to the wireless communication network. With the aid of this indication, the UE can indicate that the UE needs a restriction of a packet data service that is charged on a metered basis. The indication has the purpose of preventing one or more nodes of the wireless communication network from transmitting packet data services associated with the packet data service that is charged on a metered basis and allowing the transmission of packet data services associated with one or more other packet data services. When the UE is in a "data off" state or a "data off when roaming" state, it can provide this indication. One or more nodes of the wireless communication network can react to this indication by taking appropriate measures to prevent the transmission of packet data associated with the packet data service that is charged on a metered basis and allow the transmission of packet data services associated with one or more other packet data services. For example, the node responsible for providing the service to the UE can reject the request associated with the service or deactivate the component of the service that is charged on a metered basis. In addition, the node responsible for controlling the user plane service handling of the UE can apply a policy, for example in the form of a packet filter, which blocks the packet data services associated with the service that is charged on a metered basis and allows the transmission of packet data services associated with one or more other packet data services. Such a packet filter can be installed in a gateway, for example. Additionally, such packet filters may also be installed in the UE, for example to selectively block metered uplink packet data traffic from the UE.

[0027] This indication allows packet data connectivity of the UE to be established while avoiding unexpected charges to the subscriber. Specifically, certain services not subject to metering, such as voice telephony services, text-based messaging services, or e-book services, may remain accessible to the UE while blocking metered services or media components of metered services, such as video.

[0028] Further details of the concepts and exemplary implementations will now be described with reference to the accompanying drawings.

[0029] Figure 1A block diagram is shown for schematically illustrating an LTE-based communication network architecture for implementing the concepts outlined above. As illustrated, the architecture provides an eNB 100, which is an exemplary base station of an access network 110, referred to as an evolved UMTS terrestrial radio access network (E-UTRAN). In addition, the architecture provides a mobility management entity (MME) 120, a serving gateway (SGW) 150, a packet data network gateway (PGW) 160, a policy and charging rules function (RCRF), and a home subscriber server (HSS) 180. In addition, Figure 1 Elements of the IMS are illustrated, specifically a Telephony Application Server (TAS) 210 , an IP Television Application Server (IPTV-AS) 220 , a Service Centralization and Continuity Application Server (SCC-AS) 230 , and a Call Session Control Function (CSCF) 240 .

[0030] The MME 120 may be responsible for controlling connectivity and managing the mobility of UEs in the cellular network. The PCRF 170 may be responsible for policy and charging related functionality, such as specified in 3GPP TS 23.203 V12.4.0 (2014-03). In the eNB 100, the SGW 150 and the PGW 160 carry user plane data traffic for the UE 10. Between the eNB 100 and the UE 10, the user plane data traffic is carried over the LTE radio interface. The user plane data traffic is packet-based, specifically based on IP data packets. Unless otherwise described below, eNB 100, MME 120, SGW 150, PGW 160, PCRF 170, and HSS 180 may operate as specified by 3GPP, such as specified in 3GPP TS 23.401 V12.4.0 (2014-03) or 3GPP TS 23.402 V12.4.0 (2014-03).

[0031] The IMS node is responsible for providing and controlling various packet data services in the wireless communication network. Examples of such services are packet-based voice calls, packet-based multimedia calls, packet-based text or multimedia messaging, or packet-based mobile television. In the illustrated architecture, it is assumed that the TAS 210 is responsible for providing packet-based voice calls, packet-based multimedia calls, and / or packet-based text or multimedia messaging, and the IPTV-AS 220 is responsible for providing packet-based mobile television. The SCC-AS 230 may be responsible for centralized control of such services (e.g., with respect to the termination of incoming CS or packet-based calls), and is responsible for providing session continuity (e.g., when the UE moves between different accesses, specifically, between accesses that support CS services and accesses that support fallback-based services). The CSCF 240 may be responsible for controlling service sessions, such as with respect to session establishment, session modification, or session termination. CSCF 240 may, for example, act as a serving CSCF (S-CSCF) for UE 10, i.e., located in the home network of UE 10, or may act as a proxy CSCF (P-CSCF) for UE 10, i.e., located in a visited network or in the home network where UE 10 is roaming. Unless otherwise specified below, the functionality of an IMS node may correspond to those specified in 3GPP TS 23.228 V12.4.0.

[0032] like Figure 1 As shown in the figure, various interfaces are provided to allow Figure 1For communication between the UE 10 and the eNB 100, a radio interface called Uu is provided. For communication between the eNB 100 and the SGW 150, an interface called S1-U is provided. For communication between the SGW 150 and the PGW 160, an interface called S5 / S8 is provided. For communication between the eNB 100 and the MME 120, an interface called S1-MME is provided. For communication between the MME 120 and the SGW 150, an interface called S11 is provided. For communication between the MME 120 and the HSS 180, an interface called S6a is provided. For communication between the PCRF 170 and the SGW 150, an interface called Gxc is provided. For communication between the PCRF 170 and the PGW 160, an interface called Gx is provided. For communication between the PCRF 170 and the HSS 180, an interface called Sp is provided. For communication between HSS 180 and SCC-AS 230, an interface called Sh is provided. For communication between HSS 180 and CSCF 240, an interface called Cx is provided. For communication between CSCF 240 and application servers, namely TAS 210, SCC AS 230 and IPTV-AS 220, an interface called ISC is provided. Figure 1 The interface between the UE 10 and the application server, which is referred to as Ut, and the interface between the UE 10 and the CSCF 240, which is referred to as Gm (between the UE 10 and the P-CSCF) and Mw (between the P-CSCF and the S-CSCF) are illustrated. These interfaces may be implemented, for example, as specified in 3GPP TS 23.203 V12.4.0, 3GPP TS 23.228 V12.4.0, 3GPP TS 23.401 V12.4.0, and 3GPP TS 23.402 V12.4.0. According to the concepts illustrated herein, some of these interfaces may be supplemented with the ability to convey the above-mentioned indication of the restriction of the packet data service requiring metered charging.

[0033] In the following, reference will be made to Figure 1The architecture and exemplary processes illustrated in more detail illustrate the implementation of the concept of an indication based on the restriction of a packet data service requiring metered usage. In these processes, it is assumed that the indication is related to an IMS service and has the form of "IMS service without metered usage", which can be provided as an additional information element in some of the illustrated messages. However, it should be understood that in other implementations, the indication may also relate to other metered packet data services, or generally to metered services. Therefore, the indication will also be referred to as a "data off" indication. The indication may further specify that it is only applicable when the UE is roaming, that is, it is a "data off when roaming" indication. In some implementations, the indication may also specify the access network to which it is applicable, for example, the indication may be applicable to LTE access, but not to 2G or 3G access, such as GSM or UMTS. The latter additional attribute allows the network side to determine whether the indication should be applied for preventing metered packet data services. In this way it may be avoided that the UE 10 needs to update the indication when changing conditions, for example between roaming to non-roaming or between LTE and another access network, for example based on GSM, UMTS or WLAN (Wireless Local Area Network).

[0034] Figure 2 An exemplary process of using the indication by an IMS node for preventing the transmission of metered packet data services while allowing other packet data services is illustrated. Figure 2 The process involves UE 10, HSS 180, application server (AS) such as TAS 210, SCC AS 230 or IPTV-AS 220 and CSCF 240. Figure 2 In the process of FIG. 1 , it is assumed that the UE 10 has established a PDN connection to the wireless communication network using the IMS APN. The UE 10 may be in its home network or in a visited network.

[0035] UE 10 registers in the IMS by sending message 201 to CSCF 240. Message 201 may be a message of Session Initiation Protocol (SIP) as specified in IETF RFC3261. Message 201 may be delivered to CSCF 240 via a Gm / Mw interface. Message 201 includes a "Data Off" indication, which is stored by CSCF 240.

[0036] CSCF 240 may then query HSS 180 for subscriber information related to UE 10 by sending message 202 to HSS 180. In addition, message 202 may contain information for updating HSS 180. For example, such information may indicate that there is a "data off" indication, and HSS 180 may use this information for future use. Message 202 may correspond to a Cx Put / Pull message. In message 203, HSS 180 responds with the subscriber information. Messages 202 and 203 may be transmitted between HSS 180 and CSCF 240 on the Cx interface.

[0037] At some point, the UE 10 may request an IMS service by sending a message 204 to the CSCF 240. The message 204 may be a SIP message transmitted between the UE 10 and the CSCF 240. As illustrated, the message 204 may be a SIP request. For example, the UE 10 may request a voice call to be established by the TAS 210, may request a video call to be established by the TAS 210, or may request a mobile TV session to be established by the IPTV-AS 220. Upon receiving the message 204, the SCF 240 may, for example, execute a process for authorizing the requested IMS service.

[0038] In message 205, CSCF 240 forwards the request of message 204 to AS 210, 220. In message 205, CSCF 240 may indicate whether the requested service is authorized, and also indicate which media components of the authorized service. This information may depend on the "data off" indication from UE 10. For example, if the service is entirely based on a packet data service that is charged by volume, CSCF 240 may decide not to authorize the requested service. In addition, if the service is partially based on a packet data service that is charged by volume, CSCF 240 may decide to only authorize media components that are not subject to charge by volume. Further, if the service is entirely based on a packet data service that is not subject to charge by volume, it may decide to authorize a service with all media components. As illustrated, the "data off" indication may also be forwarded in message 205. This allows AS 210, 220, 230 to determine whether a service or its components are allowable.

[0039] As illustrated, the message 205 may be a SIP request. The AS 210, 220, 230 responds to the request of the message 205 by sending a message 206 to the CSCF 240, which may be a SIP response.

[0040] Specifically, AS 210, 220, 230 may decide to reject the request of message 205. This may be the case, for example, if the information in message 205 indicates that the service or all media components of the service are not authorized. In addition, AS 210, 220, 230 may make this determination based on the "data off" indication, even if at least some components of the service are authorized by CSCF 240. In addition, AS 210, 220, 230 may accept the request of message 205. This may be the case, for example, if the information in message 205 indicates that the service or at least some media components of the service are authorized. Based on the response in message 206, CSCF 240 sends message 207 to UE 10 to indicate the determination result by AS 210, 220, 230 and / or CSCF 240. As illustrated, message 207 may be a SIP response message.

[0041] If at least some media components of the service are authorized, the AS 210, 220, 230 may then continue to provision the service to the UE 10, such as by sending and / or receiving packet data traffic associated with the service to and / or from the UE 10.

[0042] The following model rules may apply Figure 2 In the process of: If the UE 10 provides a "data off" indication, the IMS node 210, 220, 230, 240 responsible for the decision may not allow services with video media and filer transfer, but allow voice media and text messaging. As an alternative to not allowing all video media, the IMS nodes 210, 220, 230, 240 may allow certain video media that is not subject to volume-based charging, such as video media according to GSMA IR.94 V.5.0 (March 4, 2013). If the UE 10 does not provide a "data off" indication, the IMS nodes 210, 220, 230, 240 may allow services and media components of these services, as long as there are no other reasons for not allowing a certain service or its media components.

[0043] The AS 210, 220, 230 may implement such policies, for example, by deactivating disallowed media components (e.g., by modifying the Session Description Protocol (SDP) information of the requested service). For example, the TAS 210 may deactivate video media from a request to establish a video call. In addition, as mentioned above, the AS 210, 220, 230 may also deny requests, such as requests for file transfer or video transfer. For example, the IPTV-AS 220 may deny a request for streaming video. In the event of a request being denied, the initiator of the request may be notified of the reason for the denial. Figure 2In the exemplary case of , UE 10 is the initiator of the request of message 204, and thus, UE 10 can be notified of the rejection (and the reason thereof) in message 207. However, it should be understood that in some cases, the request for service may also come from other entities different from UE 10. For example, in the case where the incoming call is to be terminated at UE 10, the request may originate from another AS. CSCF 240 may implement such a policy by not authorizing and deactivating the service or media component of the service that is subject to a pay-per-view charge. For example, CSCF 240 may authorize voice media, and deactivate other media components, such as video. In some cases, it is also possible that separate nodes implement different parts of such a policy. For example, an AS that handles voice and video calls may implement only the video-related part of the policy, while another AS may implement the file transfer-related part of the policy.

[0044] exist Figure 2 In the exemplary process of , the "data off" indication is provided at the time of IMS registration via the Gm / Mw interface. Alternatively or in addition, the "data off" indication may also be provided or updated via the Ut interface, i.e., directly to the AS 210, 220, 230. For example, the UE 10 may update the indication when changing between roaming and non-roaming conditions. In addition, although in Figure 2 In the process of requesting IMS service, AS 210, 220, 230 may receive the "Data Off" indication from CSCF 240, but it is also possible that CSCF 240 has informed AS 210, 220, 230 of the "Data Off" indication at the time of IMS registration, similar to HSS 180. In addition, AS 210, 220, 230 may also obtain information about the "Data Off" indication from HSS 180.

[0045] Figure 3 An exemplary process is illustrated in which the indication is applied by one or more of the Policy and Charging Control (PCC) nodes of the communication network to prevent the transmission of metered packet data traffic while allowing other packet data traffic. Figure 3 The process involves UE 10, eNB 100, MME 120, SGW 150, PGW 160, PCRF 170 and HSS 180. Figure 3 In the process, UE 10 initially attaches to the wireless communication network to establish a PDN connection.

[0046] At step 301, the UE 10 is powered on. This is assumed to occur in the coverage area of ​​a cell served by the eNB 100. Having selected this cell, the UE 10 proceeds by performing a random access procedure, as illustrated at step 302, and sets up an RRC (Radio Resource Control) connection. The RRC setup procedure involves the UE 10 sending a message 303, called RRCConnectionRequest, to the eNB 100, and the eNB 100 responding with a message 304, called RRCConnectionSetup. The UE 10 then sends a message 305, called RRCConnectionSetupComplete, to the eNB 100. The RRCConnectionSetupComplete message 305 contains initial NAS (Non Access Stratum) information to be provided to the eNB 100, in this illustrated example a NAS Attach Request. The NAS Attach Request contains the "Data Off" indication mentioned above. Details on the RRC connection procedure may be as specified, for example, in 3GPP TS 36.331 V12.1.0 (2014-03). Details of the NAS attach procedure and associated messages may be as specified in 3GPP TS 23.401 V12.4.0, for example.

[0047] The eNB 100 forwards the initial NAS information to the MME 120, ie, the NAS Attach Request with the "Data Off" indication.

[0048] The MME 120 may then update the HSS 180 as illustrated at 307. This may involve sending an Update Location Request, such as specified in 3GPP TS 23.401. This may also involve updating the HSS 180 with information that the UE 10 provided a "Data Off" indication.

[0049] In addition, MME 120 sends a Create Session Request to PGW 160 via SGW 150, as illustrated by messages 308 and 309. In the illustrated implementation, the Create Session Request is used to forward the "Data Off" indication to SGW 150 and PGW 160. Otherwise, the Create Session Request may be as specified in 3GPP TS 23.401 V12.4.0.

[0050] exist Figure 3 In the exemplary process of FIG. 1 , it is assumed that a dynamic PCC is used. Thus, PGW 160 contacts PCRF 170 to create a policy control session over the Gx interface. Figure 3In the exemplary process of , this is assumed to involve sending a credit control request (CCR) 310 from PGW 160 to PCRF 170. With the help of CCR 310, a "data off" indication is forwarded to PCRF 170. Depending on the indication, PCRF 170 determines a PCC rule according to which packet data services subject to volume-based charging are blocked for UE 10 while other packet data services are allowed. In the following, this PCC rule will also be referred to as a "data off" (DO) policy. This DO policy can specifically indicate or be used to configure a packet filter that blocks packet data services subject to volume-based charging and passes other packet data services. Such a packet filter can be implemented as a correspondingly configured service flow template (TFT), for example as specified in 3GPP TS 23.060 V12.4.0 (2014-03). The DO policy or packet filter can also be determined in an APN-specific manner. That is, different APNs can be associated with different APN policies. For example, when the UE 10 provides a "data off" indication, some packet data services that are not subject to metered charges may be allowed only for IMS APNs, while all packet data services are blocked for other APNs.

[0051] PCRF 170 then responds to CCR 310 by sending a Credit Control Answer (CCA) 311 to PGW 160. CCA 311 is also used to indicate the DO policy to PGW 160. PGW 160 may implement the DO policy by installing the corresponding packet filter, as illustrated in step 312. Alternatively, PGW 160 may configure an existing packet filter according to the indicated DO policy.

[0052] PGW 160 then sends a create session response to MME 120 via SGW 150, as illustrated by messages 313 and 315. In the illustrated implementation, the create session response is used to forward the DO policy to SGW 150 and MME 120. Otherwise, the create session response may be as specified in 3GPP TS 23.401 V12.4.0. Having received message 313, i.e., a create session response with a DO policy, SGW 150 may install the corresponding packet filter, as indicated by step 314.

[0053] The MME 120 then sends a context setup request to the eNB 100, as indicated by message 316. The context setup request is used to forward the DO policy to the eNB 100. Otherwise, the context setup request may be as specified in 3GPP TS 23.401 V12.4.0.

[0054] The eNB 100 then sends a RRCConnectionReconfig message 317 to the UE 10. The RRCConnectionReconfig message 317 may be in accordance with 3GPP TS 36.331 V12.1.0, for example. The RRCConnectionReconfig message 317 contains a NAS Attach Accept message, which is a response to the NAS Attach Request in the RRCConnectionSetupComplete message 305. The NAS Attach Request is used to forward the DO policy to the UE 10.

[0055] Having received the RRCConnectionReconfig message 317 with the DO policy, the UE 10 may install the corresponding packet filters, as indicated by step 318 .

[0056] To understand that Figure 3 Additional processes not shown in the figure may be part of a typical initial attach process, such as specified in 3GPP TS 23.401 V12.4.0. For example, processes for configuring a default bearer or an additional bearer may be included. In addition, instead of using a dynamic PCC mechanism, a DO policy may also be statically or pre-configured in the UE 10, SGW 150 and / or PGW 160, for example, through a management process. When the UE 10 provides a "data off" indication, such a pre-configured DO policy may be activated.

[0057] In some cases, the UE 10 may use different APNs, each for a different service. Thus, it may be necessary to establish a new PDN connection for some services. Figure 4 The diagram shows the use of a Figure 3 An exemplary process of the PCC mechanism of the process, but in which a "data off" indication is provided during the PDN connection establishment process. Figure 4 The process involves UE 10, MME 120, SGW 150, PGW 160 and PCRF 170.

[0058] To establish a PDN connection, the UE 10 sends a PDN Connectivity Request 401. The PDN Connectivity Request is used to provide a "Data Off" indication to the MME 120. Otherwise, the PDN Connectivity Request may be as specified in 3GPP TS 23.401 V12.4.0, for example.

[0059] MME 120 then sends a Create Session Request to PGW 160 via SGW 150, as illustrated by messages 402 and 403. In the illustrated implementation, the Create Session Request is used to forward the "Data Off" indication to SGW 150 and PGW 160. Otherwise, the Create Session Request may be as specified in 3GPP TS 23.401 V12.4.0.

[0060] PGW 160 contacts PCRF 170 to create a policy control session for the new PDN connection over the Gx interface. Figure 4 In the exemplary process of FIG. 1 , this is assumed to involve sending an authentication / authorization request (AAR) 404 from the PGW 160 to the PCRF 170. With the help of the AAR 310, the "data off" indication is forwarded to the PCRF 170. Depending on the indication, the PCRF 170 determines a PCC rule according to which packet data services subject to pay-as-you-go charging are blocked for the UE 10 while other packet data services are allowed, i.e., a DO policy. This DO policy may specifically indicate or be used to configure a packet filter that blocks packet data services subject to pay-as-you-go charging and passes other packet data services. Such a 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, different APNs may be associated with different APN policies. For example, for one APN, a certain packet data service that is not subject to pay-as-you-go charging may be allowed, while for other APNs, other packet data services that are not subject to pay-as-you-go charging may be allowed.

[0061] PCRF 170 then responds to AAR 404 by sending an authentication / authorization answer (AAA) 405 to PGW 160. AAA 405 is also used to indicate the DO policy to PGW 160. PGW 160 may implement the DO policy by installing the corresponding packet filter, as illustrated in step 406. Alternatively, PGW 160 may configure an existing packet filter according to the indicated DO policy.

[0062] PGW 160 then sends a create session response to MME 120 via SGW 150, as illustrated by messages 407 and 409. In the illustrated implementation, the create session response is used to forward the DO policy to SGW 150 and MME 120. Otherwise, the create session response may be as specified in 3GPP TS 23.401 V12.4.0. Having received message 407, i.e., a create session response with a DO policy, SGW 150 may install the corresponding packet filter, as indicated by step 408.

[0063] The MME 120 then sends a PDN Connectivity Accept message 410 to the UE 10. The PDN Connectivity Accept message 410 is used to forward the DO policy to the UE 10. Otherwise, the PDN Connectivity Accept message 410 may be as specified in 3GPP TS 23.401 V12.4.0.

[0064] Having received the PDN Connectivity Accept message 410 with the DO policy, the UE 10 may install the corresponding packet filters, as indicated by step 410 .

[0065] In addition, UE 10 may send a PDN Connectivity Complete message 413 to MME 120, thereby confirming the establishment of the new PDN connection. MME 120 may then send a Modify Bearer Request 413 to SGW 150, which may confirm by sending a Modify Bearer Response 414. These procedures may be as specified, for example, in 3GPP TS 23.401.

[0066] Still Figure 4 In the process of, instead of a dynamic DO strategy, a pre-configured DO strategy can be used.

[0067] After the "data off" indication has been provided, the state of the UE 10 may be changed to a normal state, in which full packet data connectivity of the UE 10 is desired. Also, this change of the "data off" indication may be indicated by the UE 10 to the wireless communication network. In situations where the prevention of delivery of metered data traffic is implemented by an IMS node, such as in Figure 2 In the process of , this can be achieved by an update procedure initiated by the UE 10, such as by a tracking area update. In the case where the DO policy prevents the transmission of metered data services, such as in Figure 3 or Figure 4 In the process of modifying the bearer state of the UE 10, this can be achieved by the UE 10 sending a request or other message to the MME 120. In this request, the change of the "data off" state can be implicitly indicated by not including a "data off" indication, or can be indicated by an explicit "data on" indication. The MME 120 can then forward this information to the SGW 150, PGW 160 and PCRF 170 by sending a modify bearer request containing a corresponding indication (or in which the "data off" indication is omitted).

[0068] Figure 5 A flow chart illustrating a method of controlling packet data connectivity in a wireless communication network is shown. Figure 5The method can be used to implement the above-mentioned concepts in a node of a wireless communication network, specifically in a node responsible for providing packet data services (e.g., an application server, such as TAS 210, IPTV-AS 220, or SCC-AS 230) or in a node responsible for authorizing packet data services (e.g., a CSCF, such as CSCF 240). If a processor-based implementation of the node is used, the steps of the method can be performed by one or more processors of the node. For this purpose, one or more processors can execute corresponding configured program codes. In addition, at least some corresponding functionality can be hardwired in one or more processors.

[0069] In step 510, the node receives an indication from a UE, for example, from UE 10. The indication indicates that the UE requires restriction of a pay-as-you-go packet data service. The indication may indicate that none of the pay-as-you-go packet data services are allowed for the UE, such as the "data off" indication mentioned above. Alternatively, the indication may indicate that none of the pay-as-you-go packet data services are allowed when UE 10 is roaming, such as the "data off when roaming" indication mentioned above. In some implementations, the indication may further indicate one or more access networks to which the indication is applicable, for example, the indication may be applicable to an LTE access network but not to a 2G or 3G access network. The pay-as-you-go service may, for example, correspond to a service of an IMS of a wireless communication system. The indication may be provided in a process for registering for a pay-as-you-go packet data service (for example, during IMS registration) or in a process for updating an IMS registration.

[0070] Depending on the received indication, the node prevents transmission of packet data traffic associated with the metered packet data service and allows transmission of packet data traffic associated with one or more other packet data services. Figure 5 In the method of claim 1, this involves the node controlling the provision or authorization of at least one pay-per-use packet data service in accordance with the received indication.

[0071] Specifically, at step 520, the node may receive a request associated with at least one metered packet data service. For example, the node may be an application server (such as one of application servers 210, 220, 230) responsible for providing at least one metered packet data service, and the request may be a request to establish a session for at least one metered packet data service. An example of such a request is Figure 2 Alternatively, the node may be a control server (eg, CSCF 240) responsible for authorizing at least one metered packet data service, and the request may be a request to authorize a session for the metered packet data service. An example of such a request is Figure 2 SIP request 205 in progress.

[0072] In response to the indication provided by the UE, the node prevents transmission of packet data traffic associated with at least one pay-per-meter packet data service at step 530. To this end, the node may reject the request of step 520 or deactivate the media component of at least one pay-per-meter service requested for the UE.

[0073] Figure 6 A flow chart illustrating a further method of controlling packet data connectivity is shown. Figure 6 The method can be used to implement the above-mentioned concepts in a wireless communication network node, in particular in a node responsible for controlling packet data services (e.g. a gateway such as SGW 150 or PGW 150 or a policy controller such as PCRF 170). If a processor-based implementation of the node is used, the steps of the method can be performed by one or more processors of the node. For this purpose, one or more processors can execute correspondingly configured program codes. In addition, at least some corresponding functionalities can be hardwired in one or more processors.

[0074] In step 610, the node receives an indication from a UE (e.g., from UE 10). The indication indicates that the UE requires a restriction of a metered packet data service. The indication may indicate that no metered packet data service is allowed for the UE, such as the "data off" indication mentioned above. Alternatively, the indication may indicate that no metered packet data service is allowed when the UE 10 is roaming, such as the "data off when roaming" indication mentioned above. In some implementations, the indication may further indicate one or more access networks to which the indication is applicable, for example, the indication may be applicable to an LTE access network but not to a 2G or 3G access network. The metered service may, for example, correspond to a service of an IMS of a wireless communication system. The node may receive the indication in a request for a process for attaching the UE to a wireless communication network. Alternatively or in addition, the node may receive the indication in a request for a process for configuring packet data network connectivity between the UE and the wireless communication network.

[0075] Depending on the received indication, the node prevents transmission of packet data traffic associated with the metered packet data service and allows transmission of packet data traffic associated with one or more other packet data services. Figure 6 In the method of , this involves a node controlling traffic handling in the wireless communication network, for example using a PCC mechanism.

[0076] Specifically, at step 620, the node may configure at least one packet filter to prevent the transmission of data traffic associated with a charge-by-volume packet data service. The at least one packet filter blocks the packet data traffic associated with the charge-by-volume packet data service and passes the packet data traffic associated with one or more other packet data services. The at least one packet filter may be operated in the node. That is, the node may also install at least one packet filter, as indicated by step 630. For example, the PGW 160 may configure and locally install at least one packet filter. Alternatively or in addition, the at least one packet filter may be operated in another node of the wireless communication network. The node may then indicate the at least one packet filter to such another node, as indicated by step 640. For example, the node may correspond to the PCRF 170 and indicate the at least one packet filter to the PGW 160 and / or the SGW 150. Alternatively or in addition, the at least one packet filter may be operated in the UE. The node may then indicate the at least one packet filter to the UE, as indicated by step 640. For example, the node may correspond to PCRF 170 , PGW 160 , or SGW 150 , and indicate a packet filter to UE 10 .

[0077] Figure 7 A flow chart illustrating a further method of controlling packet data connectivity is shown. Figure 7 The method can be used to implement the above-mentioned concepts in a UE (such as UE 10). If a processor-based implementation of a UE is used, the steps of the method can be performed by one or more processors of the UE. For this purpose, one or more processors can execute corresponding configured program codes. In addition, at least some corresponding functionalities can be hardwired in one or more processors.

[0078] At step 710, the UE detects a command to cut off the packet data connectivity of the UE. This command may be based on a user selection, such as a selection of "data off" or "data off when roaming". Alternatively, this command may be generated in the UE by an automatic process (e.g., a scheduled switch between a "data off" state and a "data on" state) or a process that triggers the command by a mobility event (such as entry into a visited network or attachment to an access network (such as an LTE access network)).

[0079] At step 720, in response to the command of step 720, the UE sends an indication to the wireless communication network. The indication indicates that the UE requires a restriction of the metered packet data service. The indication may indicate that no metered packet data service is allowed for the UE, such as the "data off" indication mentioned above. Alternatively, the indication may indicate that no metered packet data service is allowed when the UE 10 is roaming, such as the "data off when roaming" indication mentioned above. In some implementations, the indication may further indicate one or more access networks to which the indication is applicable, for example, the indication may be applicable to an LTE access network, but not to a 2G or 3G access network. The metered service may correspond to a service of an IMS of a wireless communication system, for example. The UE may send the indication in a request for a process for attaching a user equipment to a wireless communication network. Alternatively or in addition, the UE may send the indication in a process for configuring packet data network connectivity between the UE and the wireless communication network. Further, the UE may send the indication in a process for registering the UE for at least one metered packet data service.

[0080] In response to sending the indication, the UE may receive an indication of a packet filter at step 730 and install the packet filter at step 740. The packet filter blocks packet data traffic associated with the metered packet data service and passes packet data traffic associated with one or more other packet data services.

[0081] Figure 8 The diagram illustrates an exemplary structure for implementing the above concepts in a node of a wireless communication network. For example, the illustrated structure can be used to implement an application server, such as an IMS application server, such as TAS 210, IPTV-AS 220 or SCC-AS 230, or a control function related to a packet data service, such as CSCF 240.

[0082] In the illustrated example, the node includes an interface 810 for providing or controlling a packet data service. For example, the interface 810 may correspond to a SIP-based interface, such as in Figure 1 The Gm or Mw interface shown in the architecture.

[0083] In addition, the node includes one or more processors 850 coupled to the interface 810 and a memory 860 coupled to the one or more processors 850. The memory 860 may include a read-only memory (ROM) (e.g., a flash ROM), a random access memory (RAM) (e.g., a dynamic RAM (DRAM) or a static RAM (SRAM)), a mass storage device (e.g., a hard disk or a solid-state disk), etc. The memory 860 includes appropriately configured program code modules to be executed by the one or more processors 850 in order to implement the above-mentioned functionality of the node, such as corresponding to Figure 5More specifically, the program code modules in the memory 860 may include a service handling module 870 to implement the above-mentioned functionality for providing or authorizing a packet data service. In addition, the program code modules in the memory 860 may include a communication module 880 to implement the above-mentioned functionality of receiving a "data off" indication. Still further, the memory 860 may include a "data off" policy handling module 890 to implement the above-mentioned functionality of selectively preventing the transmission of a packet data service subject to metering (e.g., by rejecting a request associated with a packet data service subject to metering or deactivating a media component of the packet data service) in response to receiving a "data off" indication.

[0084] To understand that Figure 8 The structures illustrated in the figure are only schematic, and the node may actually include other components, which have not been illustrated for the sake of brevity, such as other interfaces or other processors. In addition, it is to be understood that the memory 860 may include other types of program code modules (which have not been illustrated), such as program code modules for implementing known functionality of application servers or control servers (such as IMS application servers or CSCF). In some implementations, a computer program for implementing the functionality of the node may also be provided, such as in the form of a physical medium storing the program code modules to be stored in the memory 860, or by making such program code available for download or streaming.

[0085] Fig. 9 An exemplary structure for implementing the above-described concepts in a node of a cellular network is illustrated. For example, the illustrated structure may be used to implement a node controlling user plane traffic handling, such as a PCC node, such as SGW 150, PGW 160 or PCRF 170.

[0086] In the illustrated example, the node includes a first service interface 910 for communicating with one or more UEs and a second service interface 920 for communicating with other network nodes. The first interface 910 and the second interface 920 may specifically have the purpose of conveying user plane traffic of one or more UEs (such as UE 10). In addition, the node includes a control interface 930, which can be used to control the handling of user plane traffic. If the node corresponds to a PGW (such as PGW 160), the control interface 930 may correspond to Figure 1 If the node corresponds to an SGW (such as SGW 150), the control interface 930 may correspond to the Gx interface shown in the architecture of FIG. Figure 1 If the node corresponds to a policy controller (such as PCRF 170), the control interface 930 may correspond to the Gxc interface shown in the architecture of FIG. Figure 1In the latter case, the service interfaces 910 and 920 may be omitted.

[0087] In addition, the node includes one or more processors 950 coupled to interfaces 910, 920 and 930 and a memory 960 coupled to the one or more processors 950. The memory 960 may include a ROM (e.g., a flash ROM), a RAM (e.g., a DRAM or an SRAM), a mass storage device (e.g., a hard disk or a solid-state disk), etc. The memory 960 includes appropriately configured program code modules to be executed by the one or more processors 950 in order to implement the above-mentioned functionality of the node, such as corresponding to Figure 6 More specifically, the program code modules in the memory 960 may include a PCC module 970 so as to implement functionality such as controlling user plane service handling of one or more UEs based on a PCC mechanism. In addition, the program code modules in the memory 960 may include a communication module 980 so as to implement the above-mentioned functionality of receiving a "data off" indication. Still further, the memory 960 may include a "data off" policy handling module 990 so as to implement the above-mentioned functionality of selectively preventing transmission of packet data services subject to metered charges (e.g., by configuring or installing at least one packet filter that blocks packet data services associated with metered charge packet data services and passes other packet data services) in response to receiving a "data off" indication.

[0088] To understand that Fig. 9 The structures illustrated in the figure are only schematic, and the node may actually include additional components, which have not been illustrated for the sake of brevity, such as additional interfaces or additional processors. Also, it is to be understood that the memory 960 may include other types of program code modules (which have not been illustrated), such as program code modules for implementing known functionality of PCC nodes (such as PCRF, PGW or SGW). In some implementations, a computer program for implementing the functionality of the node may also be provided, such as in the form of a physical medium storing program code modules to be stored in the memory 960, or by making such program code available for download or streaming.

[0089] Fig.10 An exemplary structure for implementing the above-described concepts in a UE (such as UE 10) of a wireless communication network is illustrated.

[0090] In the illustrated example, the UE includes a radio interface 1010 for connecting to a wireless communication network. The radio interface 1010 may be based on a packet-based cellular radio technology, such as an LTE radio access technology, for example. As further illustrated, the UE may include a user interface 1020 (e.g., based on keys, touch-sensitive surfaces, optical displays, and / or voice-based input or output). The user interface 1020 may be used, for example, to select a "data off" state by a user of the UE.

[0091] In addition, the node includes one or more processors 1050 coupled to the radio interface 1010 and the user interface 1020, and a memory 1060 coupled to the one or more processors 1050. The memory 1060 may include a ROM (e.g., a flash ROM), a RAM (e.g., a DRAM or an SRAM), a mass storage device (e.g., a hard disk or a solid state disk), etc. The memory 1060 includes appropriately configured program code modules to be executed by the one or more processors 1050 in order to implement the above-mentioned functionality of the UE, for example, corresponding to Figure 7 More specifically, the program code modules in the memory 1060 may include a "data off" state management module 1070 to implement the functionality of managing the "data off" state selection, for example, in response to a user selection via the user interface 1020 or in response to an automatic process (e.g., based on a schedule or trigger event). In addition, the program code modules in the memory 1060 may include a communication module 1080 to implement the above-mentioned functionality of sending a "data off" indication. Still further, the memory 1060 may include a PCC module 1090 to implement the above-mentioned functionality of installing a packet filter that blocks packet data traffic associated with a pay-per-use packet data service and passes other packet data traffic.

[0092] To understand that Fig.10 The structures illustrated in the are only schematic, and the UE may actually include additional components, which have not been illustrated for the sake of brevity, such as additional interfaces or additional processors. It is also understood that the memory 1060 may include other types of program code modules, which have not been illustrated, such as program code modules for implementing known functionality of the UE. In some implementations, a computer program for implementing the functionality of the node may also be provided, such as in the form of a physical medium storing program code modules to be stored in the memory 1060, or by making such program code available for download or streaming.

[0093] As can be seen, the concepts described above can be used to effectively control packet-based connectivity in wireless communication networks. In particular, the concepts can be used to allow appropriate use of access that only provides packet-based connectivity (such as LTE access) while avoiding undesirable metered traffic.

[0094] It is to be understood that the examples and embodiments as described above are merely illustrative and susceptible to various modifications. For example, the prevention of a charge-by-volume packet data service implemented by an IMS node or the like (such as Figure 2 The process diagram of the process diagram) can be combined with the prevention of pay-per-use services through the PCC mechanism (such as by Figure 3 and Figure 4 In addition, various mechanisms can be used to provide a "data off" indication. For example, during the attach process, an indication is provided (e.g. Figure 3 ) or a radio connectivity configuration process (as shown in Figure 4 ) may also be used to deliver an indication to an IMS node by providing the indication to HSS 180 (from which the IMS node can retrieve the indication). Similarly, providing an indication during IMS registration or some other SIP process (such as Figure 2 ) may also be used to deliver the indication to the PCC node by providing the indication to the HSS 180 from which the PCC node may retrieve the indication.

[0095] In addition, the concept illustrated can be used in conjunction with various types of cellular network technologies, without limitation to the LTE technology mentioned above. Moreover, it is to be understood that the above concept can be implemented by using correspondingly designed software to be executed by one or more processors of an existing device or network node or by using dedicated hardware.

Claims

1. A method for controlling packet data connectivity in a wireless communication network, performed by a node of the wireless communication network, the method comprising: The node of the wireless communication network receives, from a user equipment, an indication that the user equipment requires restriction of a pay-as-you-go packet data service; as well as Depending on the received indication, the node prevents transmission of packet data traffic associated with the metered packet data service and allows transmission of packet data traffic associated with one or more other packet data services that are not subject to metered charges.

2. The method according to claim 1, The indication indicates that none of the pay-as-you-go packet data services is allowed for the user equipment.

3. The method according to claim 1, The indication indicates that none of the pay-as-you-go packet data services is allowed when the user equipment is roaming.

4. A method according to any one of the preceding claims, The indication further indicates one or more access networks to which the indication is applicable.

5. The method according to any one of claims 1 to 3, comprising: The node configures at least one packet filter that blocks the packet data traffic associated with the metered packet data service and passes the packet data traffic associated with the one or more other packet data services.

6. The method according to claim 5, Wherein the packet filter operates in the node.

7. The method according to claim 5, Wherein the packet filter operates in a further node of the wireless communication network.

8. The method of claim 5, wherein the packet filter operates in the user equipment.

9. The method according to any one of claims 1 to 3, The node receives the indication in a process for attaching the user equipment to the wireless communication network.

10. The method according to any one of claims 1 to 3, The node receives the indication in a process for configuring packet data network connectivity between the user equipment and the wireless communication network.

11. The method according to any one of claims 1 to 3, The node is an application server responsible for providing at least one of the pay-as-you-go packet data services.

12. The method according to any one of claims 1 to 3, The node is a control server responsible for authorizing at least one of the pay-per-meter packet data services.

13. The method according to claim 11, The node prevents transmission of the packet data traffic associated with the at least one pay-per-meter packet data service by deactivating a media component of the at least one pay-per-meter packet data service.

14. The method according to claim 11, wherein the node prevents transmission of the packet data traffic associated with the at least one metered packet data service by denying a request associated with the at least one metered packet data service.

15. The method according to claim 11, The node receives the indication during a process for registering the user equipment for the at least one pay-per-capacity packet data service.

16. The method according to any one of claims 1 to 3, The pay-as-you-go packet data service and the other packet data services are services of an Internet Protocol Multimedia Subsystem of the wireless communication network.

17. A method for controlling packet data connectivity in a wireless communication network performed by a user equipment, the method comprising: The user equipment detects a command to cut packet data connectivity of the user equipment, In response to the command, the user equipment sends an indication to a node of the wireless communication network that the user equipment requires restriction of the metered packet data service, so that the node prevents transmission of packet data traffic associated with the metered packet data service and allows transmission of packet data traffic associated with one or more other packet data services that are not subject to metered traffic.

18. The method of claim 17, The indication indicates that none of the pay-as-you-go packet data services is allowed for the user equipment.

19. The method of claim 17, The indication indicates that none of the pay-as-you-go packet data services is allowed when the user equipment is roaming.

20. The method according to any one of claims 17 to 19, The indication further indicates one or more access networks to which the indication is applicable.

21. The method according to any one of claims 17 to 19, The user equipment sends the indication in a process for attaching the user equipment to the wireless communication network.

22. The method according to any one of claims 17 to 19, The user equipment sends the indication in a process for configuring packet data network connectivity between the user equipment and the wireless communication network.

23. The method according to any one of claims 17 to 19, The user equipment sends the indication during a process for registering the user equipment for at least one of the pay-per-meter packet data services.

24. The method of any one of claims 17 to 19, comprising: In response to sending the indication, the user equipment receives an indication of a packet filter; as well as The user equipment installs the packet filter, which blocks the packet data traffic associated with the pay-per-meter packet data service and passes the packet data traffic associated with the one or more other packet data services.

25. The method according to any one of claims 17 to 19, The pay-as-you-go packet data service and the other packet data services are services of an Internet Protocol Multimedia Subsystem of the wireless communication network.

26. A node for a wireless communication network, the node comprising: at least one interface; as well as at least one processor, the at least one processor configured to: - receiving from a user equipment an indication that the user equipment requires restriction of a metered packet data service; and - dependent on said received indication, preventing the transmission of packet data traffic associated with said metered packet data service and allowing the transmission of packet data traffic associated with one or more other packet data services not subject to metered charges.

27. The node according to claim 26, The indication indicates that none of the pay-as-you-go packet data services is allowed for the user equipment.

28. The node according to claim 26, The indication indicates that none of the pay-as-you-go packet data services is allowed when the user equipment is roaming.

29. A node as claimed in any one of claims 26 to 28, The indication further indicates one or more access networks to which the indication is applicable.

30. A node as claimed in any one of claims 26 to 28, The at least one processor is configured to configure at least one packet filter that blocks the packet data traffic associated with the pay-per-meter packet data service and passes the packet data traffic associated with the one or more other packet data services.

31. The node according to claim 30, Wherein the packet filter operates in the node.

32. The node according to claim 30, Wherein the packet filter operates in a further node of the wireless communication network.

33. The node according to claim 30, The packet filter operates in the user equipment.

34. A node as claimed in any one of claims 26 to 28, Wherein the at least one processor is configured to receive the indication in a process for attaching the user equipment to the wireless communication network.

35. A node as claimed in any one of claims 26 to 28, Wherein the at least one processor is configured to receive the indication in a process for configuring packet data network connectivity between the user equipment and the wireless communication network.

36. A node as claimed in any one of claims 26 to 28, The node is an application server responsible for providing at least one of the pay-as-you-go packet data services.

37. A node as claimed in any one of claims 26 to 28, The node is a control server responsible for authorizing at least one of the pay-per-meter packet data services.

38. The node according to claim 36, The at least one processor is configured to prevent delivery of the packet data traffic associated with the at least one pay-per-meter packet data service by deactivating a media component of the at least one pay-per-meter packet data service.

39. The node according to claim 36, The at least one processor is configured to prevent transmission of the packet data traffic associated with the at least one pay-per-meter packet data service by denying a request associated with the at least one pay-per-meter packet data service.

40. The node of claim 36, The at least one processor is configured to receive the indication in a process for registering the user equipment for the at least one pay-per-meter packet data service.

41. A node as claimed in any one of claims 26 to 28, The pay-as-you-go packet data service and the other packet data services are services of an Internet Protocol Multimedia Subsystem of the wireless communication network.

42. The node of claim 26, Wherein the at least one processor is configured to perform the steps of the method as claimed in any one of claims 1 to 16.

43. A user equipment comprising: An interface for connecting to a wireless communication network; as well as at least one processor, the at least one processor configured to: - detecting a command to cut off the packet data connectivity of said user equipment, - in response to the command, sending an indication to a node of the wireless communication network that the user equipment requires restriction of the metered packet data service, so that the node prevents the transmission of packet data services associated with the metered packet data service and allows the transmission of packet data services associated with one or more other packet data services that are not subject to metered charges.

44. The user equipment according to claim 43, The indication indicates that none of the pay-as-you-go packet data services is allowed for the user equipment.

45. The user equipment according to claim 43, The indication indicates that none of the pay-as-you-go packet data services is allowed when the user equipment is roaming.

46. ​​The user equipment according to any one of claims 43 to 45, The indication further indicates one or more access networks to which the indication is applicable.

47. The user equipment according to any one of claims 43 to 45, The at least one processor is configured to send the indication in a process for attaching the user equipment to the wireless communication network.

48. The user equipment according to any one of claims 43 to 45, Wherein the at least one processor is configured to send the indication in a process for configuring packet data network connectivity between the user equipment and the wireless communication network.

49. The user equipment according to any one of claims 43 to 45, The at least one processor is configured to send the indication in a process for registering the user equipment for at least one of the pay-per-meter packet data services.

50. The user equipment according to any one of claims 43 to 45, comprising: wherein the at least one processor is configured to: - receiving an indication of a packet filter in response to sending said indication; as well as - installing the packet filter, the packet filter blocking the packet data traffic associated with the metered packet data service and passing the packet data traffic associated with the one or more other packet data services.

51. The user equipment according to any one of claims 43 to 45, The pay-as-you-go packet data service and the other packet data services are services of an Internet Protocol Multimedia Subsystem of the wireless communication network.

52. The user equipment according to claim 43, Wherein the at least one processor is configured to perform the steps of the method as claimed in any one of claims 17 to 25.

53. A computer readable storage medium comprising program code to be executed by at least one processor of a node of a radio communication network, wherein execution of the program code causes the at least one processor to perform the steps of the method of any one of claims 1 to 16.

54. A computer program product comprising program code to be executed by at least one processor of a node of a radio communications network, wherein execution of the program code causes the at least one processor to perform the steps of the method of any one of claims 1 to 16.

55. A computer-readable storage medium comprising program code to be executed by at least one processor of a user device, wherein execution of the program code causes the at least one processor to perform the steps of the method of any one of claims 17 to 25.

56. A computer program product comprising program code to be executed by at least one processor of a user equipment, wherein execution of the program code causes the at least one processor to perform the steps of the method of any one of claims 17 to 25.

Images