Mobile data networks

Abstract

A GPRS telecommunications system, comprising a plurality of networks, at least one of the networks being a home network for a subscriber associated with a mobile terminal; a node maintaining data relating to a service; one or more gateway nodes in networks other than the home networks and operated by the home network service provider, and means for enabling said gateway nodes to interact with the service data maintaining node to provide them with data and/or instructions concerning the service.

Description

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims priority of European Application No. 01300293.6 filed on Jan. 15, 2001.

[0002] 1. Field of the Invention

[0003] This invention relates to mobile data networks. In particular, it relates to mobile networks in which at least some users operate, for example, on a prepaid basis in which data transmission is paid for in advance. In particular, the invention relates to networks where a user is a prepaid subscriber to one particular network but is allowed to roam to other visited networks.

BACKGROUND TO THE INVENTION

[0004] Current standards solutions for prepaid subscribers who are roaming outside their own home network are based upon a protocol known as CAMEL (Customised Applications for Mobile Enhanced Logic), typically CAMEL phase 3 for the GPRS (General Packet Radio System) environment. The control of the prepaid subscription features is between a Serving GPRS Support Node (SGSN) and the CAMEL Service Environment (CSE). In order to allow subscribers the ability to roam, the visited network must be able to support the same level of CAMEL that is, CAMEL phase 3. The practical result of this is that in order to allow prepaid subscribers the ability to roam in any network, all visited networks must support the CAMEL phase 3 protocol.

[0005] The CAMEL protocol has not yet been deployed by all operators and is considered to be quite cumbersome to deploy. Accordingly, it may be some considerable time, if at all, before all operators deploy CAMEL. In the meantime, there is a requirement for some operators to deploy prepaid capability and to allow roaming without waiting for other operators to deploy CAMEL.

[0006] The present invention arose in an attempt to provide a mobile network that allows roaming subscribers the ability to use a prepaid service while in a visited network, and which does not rely on all participating networks deploying CAMEL.

BRIEF SUMMARY OF THE INVENTION

[0007] According to the present invention in a first aspect there is provided a method of enabling a mobile station, associated with a home network, to roam in one or more further networks while using a predetermined service, comprising; providing a node maintaining data relating to said service; providing a set of gateway nodes in the further network which are operated by the home network service provider, and causing the node to interact with the gateway nodes to provide them with data and/or instructions concerning the service.

[0008] Preferably, the service relates to the prepaid status of a subscriber.

[0009] According to the present invention in a second aspect there is provided a GPRS telecommunications system, comprising a plurality of networks, at least one of the networks being a home network for a subscriber associated with a mobile terminal; a node maintaining data relating to a service; one or more gateway nodes in networks other than the home networks and operated by the home network service provider, and means for enabling said gateway nodes to interact with the service data maintaining node to provide them with data and/or instructions concerning the service.

[0010] In a GPRS environment, the set of gateway nodes are preferably gateway GPRS support nodes (GGSNs) in the network, operated by the home service provider (home network). The additional node, which will hereinafter be referred to as the prepaid data server, but which may of course relate to services other than prepaid, may then be arranged to interact with service logic in a CAMEL Service Environment (CSE) and the GGSN, in order to provide the GGSN with thresholds based on formulae that set a limit on the amount of data that can be exchanged at a mobile station and an external network, and/or setting the maximum connection time which a session may last.

[0011] In a further aspect there is provided, in a GPRS Telecommunications System, the provision of a prepaid data server node.

DESCRIPTION OF THE DRAWINGS

[0012] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0013] FIG. 1 shows schematically a network architecture;

[0014] FIG. 2 shows a signal flow for user established PDP context with charging characteristics indicating the prepaid user;

[0015] FIG. 3 shows a signal flow for a prepaid user established PDP context when no information is available to a GGSN about charging characteristics;

[0016] FIG. 4 shows a signal flow for a post-paid user established PDP context when no information is available to the GGSN about charging characteristics;

[0017] FIG. 5 shows a signal flow when a GGSN reaches a threshold for a particular PDP and the PDP replies with another threshold; and

[0018] FIG. 6 shows a signal flow when a GGSN reaches a threshold for a particular PDP, a user has insufficient credit remaining and the PDP requests release of the PDP context.

DESCRIPTION OF THE PREFERRED EMBODIMENTS OF THE INVENTION

[0019] Referring to FIG. 1, this figure shows very generally a network level architecture.

[0020] As described in embodiments of the invention, an additional node, which is in this specification termed the “prepaid data server” 1, is used and this maintains information about all prepaid subscribers in the network.

[0021] The prepaid data server 1 is shown as being associated with, or connected to, a service control point (SCP) 2. In the CAMEL environment this SCP 2 may be termed the CAMEL service environment (CSE). Note that the prepaid data server may be physically part of the SCP server, or it may be a separate entity which is associated with it or at least able to access it.

[0022] A plurality of GGSNs, operated by the home network, but located at other (roaming) networks, are then able to access the prepaid data server. In the figure, two of these are shown, GGSN No. 1(3) and GGSN No. 2(4). As is well known, these will then be connected to Serving GGSN Support Nodes (SSGN). The service control point 2 essentially operates the Service Control Function (SCF) in known manner.

[0023] The prepaid data server 1 is provided with data as to who is a prepaid user and all the relevant policies and other selected information. The GGSNs 3 and 4 are not provided with data which allows them to identify that a particular user is a prepaid user. They receive this information from the prepaid data server.

[0024] In embodiments of the invention, it is assumed that a so called charging characteristics parameter (UMTS standards release 99 only) is used to identify that a user is a prepaid user. For support of pre-release 99, and also for customers roaming to networks where the optional charging characteristics parameter is not supported, the GGSN has to query the prepaid data server 1 to determine if a user is a prepaid user.

[0025] The prepaid data server is used to enforce policies on the partition of credit limits across GGSNs and to perform other functions. For example, it can deny a set up of a session to a GGSN if a credit limit is exhausted.

[0026] The prepaid data server and the SCP2 are closely coupled, thus allowing for voice and data prepaid to co-exist and for the interface between them to be simply based on prepaid application interaction with SCP databases and applications. A basic outline of messages between a GGSN 3 and the prepaid data server is shown in the following Table 1.

TABLE 1
Query messages          Get threshold for prepaid user (as
                        identified by charging characteristics)
                        Check for prepaid user and send
                        instructions accordingly
Query Response messages PrePaid user indicator plus allowed
                        threshold for PDP context
                        PrePaid user indicator plus service
                        denial (no credit available)
                        Non PrePaid user indicator continue
                        as normal
                        Non prepaid - reverse charging
Report message          PDP context update (e.g. QoS changes)
                        plus unused credit
                        Threshold reached
                        PDP context disconnect plus unused credit
Report Response         New threshold
                        Refused new threshold - disconnect PDP

[0027] In more detail, some of the various messages and parameters which can be used are as follows:

[0028] GetThreshold(IMSI,MSISDN, APN, QoS parameters)

[0029] Used by the GGSN when the charging characteristics indicate that the user is a prepaid user.

[0030] CheckforPrePaidAndGetThreshold (IMSI, MSISDN, APN, QoS parameters)

[0031] Used by the GGSN to query the PPS as to whether user is a prepaid user The PPS will reply either indicating that the user is not a prepaid user (NoThresholdApplicable) or will indicate that the user is a prepaid user by returning a threshold for the PDP context (SetThreshold)

[0032] SetThreshold (PPS PDPIdentifier, max limit, coefficient time units, coefficient volume units, max volume, time of day trigger)

[0033] Used by the PPS to indicate to the threshold applicable for the PDP context. This threshold is represented in units made up of a formula based on time and volume. This formula is based on elapsed connection time and data volume transferred in addition to limits based on a maximum volume and time of day. A formula may be sent to the GGSN in the form of αT+βV≦L where T is time in seconds and V is the volume in bytes and L is the maximum limit the allowed for the PDP context.

[0034] NoThresholdApplicable()

[0035] Used by the PPS to indicate to the GGSN that no threshold is applicable for this PDP context.

[0036] FurnishChargingInformation(PPS PDPIdentifier)

[0037] Used by the PPS to instruct the GGSN to generate a Charge Detail Record (CDR). This includes charging related information such as details of the party to pay.

[0038] PDPContextUpdate(PPS PDIdentifier, QoS parameters, elapsed time units, total volume transferred, unused units)

[0039] Used by the GGSN to inform the PPS that the characteristics of the PDP context (e.g. QoS parameters) have changed. This message will include unused limits in units from the previously set threshold, including elapsed session segment time and the total volume transferred in that session segment.

[0040] PDPThresholdReached(PPS PDPIdentifier)

[0041] Used by the GGSN to inform the PPS that the threshold has been reached.

[0042] This message will include the appropriate threshold reached.

[0043] PDPD is connected (PPS PDPIdentifier, elapsed time units, total volume transferred, unused units)

[0044] Used by the GGSN to inform the PPS that the PDP context has been deactivated (user or network initiated but not as a direct result of a prepaid threshold being reached). This message will include unused limits in units from the previously set threshold, including elapsed session segment time and the total volume transferred in that session segment.

[0045] Disconnect(PPS PDPIdentifier)

[0046] Used by the PPS to inform the GGSN to force a disconnect of the PDP context.

[0047] ActivityTest (to check that a session is still in progress)

[0048] Used by either the GGSN or the PPS to ensure correct operation.

[0049] ActivityTestAck (asks for an acknowledgement of activity)

[0050] Used by either the GGSN or PPS as a response to the Activity Test message.

[0051] KeepAlive

[0052] Used to ensure connectivity between the PPS and the GGSN.

[0053] Error Messages

[0054] FIGS. 2 to 6 show in a little more detail signal flow for various scenarios. FIG. 2 shows an example of user established PDP context with charging characteristics indicating a prepaid user. The signal flows are shown as being between a mobile station (MS) 5, a base station (BSS) 6, a serving GPRS support node (SGSN) 7, a gateway GPRS support node (GGSN) 8, and the prepaid data server (PPS) 1.

[0055] In this scenario, the GGSN examines the charging ID and determines that the user is a prepaid subscriber. It then contacts the prepaid data server. The prepaid data server then replies to the GGSN to indicate that sufficient credit remains to allow the PDP to continue and the PPS sends a threshold that the GGSN must apply to that PDP context.

[0056] More particularly, at Step S1, mobile station 5 sends an activate context request to the SGSN 7. After various security functions (S2) the SGSN then sends an invoke trace signal S3 to the base station 6. A cleared PDP context request is then sent from the SGSN to the GGSN and this then requests a threshold from the prepaid data server 1 at Step S5. Then the PPS 1, since it contains details of the user's prepaid status, credit status, etc, sends a threshold at Step S6, which threshold the GGSN must apply to that PDP context (S7). Packet flow context procedures then occur in a normal manner and an activate PDP context accept signal is then transmitted from the SGSN to the mobile station 5.

[0057] The threshold may be either time based or volume based or both. A volume based threshold places a time limit that a PDP context session may last, whilst a volume based threshold places a limit on the maximum data that may be transferred between the mobile station and the GGSN.

[0058] FIG. 3 shows an example of prepaid user established PDP context when no information is available to the GGSN about the charging characteristics. The example assumes that the user is a prepaid user. The signal is similar to that of FIG. 2 except that the GGSN queries the prepaid data server at a step U1 to check whether the user is a prepaid subscriber. The PPS 1 replies (in this case) with an indication that the user is a prepaid user and also sends a threshold that the GGSN must apply to the PDP context, at Step U2. The remaining steps are similar to that of the flow of FIG. 2.

[0059] FIG. 4 shows an example of post paid user established PDP context with no information available to the GGSN about charging characteristics. In this case, the GGSN has no information in the charging identity (ID) to determine if the user is a prepaid user. The example assumes that the user is not a prepaid user. In this case, the GGSN at Step T1 queries the prepaid data server 1 to determine whether the user is a prepaid subscriber. The prepaid data server replies with an indication that the user is not a prepaid user and so no threshold is applicable. The GGSN then continues to establish PDP context in the normal way and no threshold is applied.

[0060] FIG. 5 shows an example when a subscriber is a prepaid subscriber and in which a threshold is reached for a particular PDP context, and in which the PDP replies with another threshold.

[0061] In this example, during a point in a call, the GGSN reports to the prepaid data server that the previously set threshold (e.g. the threshold referred to with reference to FIG. 2 or FIG. 3) has been reached. The PPS determines that the user has sufficient credit remaining and so sends a new threshold to the GGSN. These two signals are shown schematically as signals V1 and V2.

[0062] FIG. 6 shows an example, for a prepaid subscriber, in which, when a call is in progress, a threshold is reached for a particular PDP. In this case, the user has insufficient credit and the PDP requests the release of the PDP context, and thereby termination of a session.

[0063] When the GGSN 8 reaches the previously set threshold, it sends a PDP threshold reach signal W1 to the PPS 1. Since the user has insufficient credit the PPS cannot issue a further threshold and so issues a disconnect signal W2 to the GGSN. The GGSN then forwards a delete PDP context request W3 to the SGSN and the respective deactivate PDP context request and deactivate PDP context accept messages flow to and from the mobile station 5, W4 and W5. Further to this, a delete PDP context response is passed from the SGSN to the GGSN and the radio access bearer is released to terminate the session W7.

Claims

1. A method of enabling a mobile station, associated with a home network, to roam in one or more further networks while using a predetermined service, comprising; providing a node maintaining data relating to said service; providing a set of gateway nodes in the further network which are operated by the home network service provider, and causing the node to interact with the gateway nodes to provide them with data and/or instructions concerning the service.

2. A method as claimed in claim 1, wherein the service relates to the prepaid status of a subscriber.

3. A method as claimed in claim 1 or 2, wherein the gateway nodes are Gateway GPRS Support Nodes (GGSN).

4. A method as claimed in claim 3, wherein the node interacts with service logic in a CSE and GGSN.

5. A method as claimed in claim 4, wherein the data maintaining node provides the GGSN with thresholds usable to set a limit on the amount of data that can be transferred.

6. A GPRS telecommunications system, comprising a plurality of networks, at least one of the networks being a home network for a subscriber associated with a mobile terminal; a node maintaining data relating to a service; one or more gateway nodes in networks other than the home networks and operated by the home network service provider, and means for enabling said gateway nodes to interact with the service data maintaining node to provide them with data and/or instructions concerning the service.

7. A system as claimed in claim 6, wherein the gateway nodes are GPRS support nodes.

8. A system as claimed in claim 7, wherein the node interacts with service logic in a CSE and GGSN.

9. A system as claimed in claim 8, wherein the data maintaining node provides the GGSN with thresholds usable to set a limit on the amount of data that can be transferred.

10. A GPRS Telecommunications System, including a prepaid data server node.