WO2015183167A1

WO2015183167A1 - Method and system for managing user account data relating to the use of a mobile communications unit

Info

Publication number: WO2015183167A1
Application number: PCT/SE2015/050606
Authority: WO
Inventors: Björn KNUDSEN; Fredrik SALQVIST
Original assignee: Globetouch Ab
Priority date: 2014-05-27
Filing date: 2015-05-26
Publication date: 2015-12-03
Also published as: SE1450633A1

Abstract

Method for managing user account data relating to the use of a mobile communications unit, wherein a gateway node (210) communicates information regarding consumption of mobile communication services to a charging server (220). The invention is characterized in that the charging server (220) provides a first digital communications interface (222) for queries regarding the updated data communication usage of a particular mobile communication device or a particular mobile subscription, in that a BSS (Business Support System) (230) provides a second digital communications interface (231) for queries regarding current data communication usage, and in that the BSS (230), upon a request for updated data communication usage information via said second interface (231), queries the charging server (220) regarding the updated data communication usage and, in reply to said query, returns updated data communication usage information. The invention also relates to a system.

Description

METHOD AND SYSTEM FOR MANAGING USER ACCOUNT DATA RELATING TO THE USE OF A MOBILE COMMUNICATIONS UNIT

The present invention relates to a method and a system for managing user account data relating to the use of a mobile communications unit. Specifically, the invention relates to the use of such a mobile communications unit in a mobile communications network, such as a GSM, GPRS, 3G or 4G net^¬ work, or the like. In particular, the present invention re- lates to mobile data access, as opposed to voice communica^¬ tions .

Data communications to and from a mobile communication device are conventionally routed via a serving node, such as a SGSN (Serving GPRS Support Node) for a GPRS network and an SGW (Serving Gateway) for an LTE network, in communication with a gateway node, such as a GGSN (Gateway GPRS Support Node) for a GPRS network and a PGW (Packet Data Network Gateway) for an LTE network. The gateway node is typically connected to an OCS (Online Charging System) or an RTS (Realtime Charging System) . In the following, OCS : s and RTS : s will interchangea^¬ bly be referred to as "charging servers". CDR:s (Charging Data Records) are produced by the gateway node and communi^¬ cated to the charging server for subsequent processing, such as invoicing. The charging server also holds information regarding allowed data quotas, such as the amount of data traffic prepaid by the user of the mobile communication de^¬ vice, and possibly various other types of information relat^¬ ing to the data usage profile of the user.

Typically, a BSS (Business Support System) is used for han^¬ dling the user account data on a higher level, such as manag^¬ ing the amount of data traffic allowed in total or over a certain time period. Conventionally, the BSS receives infor- mation regarding used data traffic after a series of data aggregating and processing steps based upon CDR data.

It is desirable for the user to be able, via an interface provided by the BSS, to receive updated information regarding current data usage and to purchase additional data or to modify the currently used data usage plan for the user in question . With the very high data speeds provided by modern mobile communication technology, such as 4G and above, substantial amounts of data may be used over only short periods of time. Since the mentioned aggregating and processing of the CDR data introduces latency, the information about data usage received and held by the BSS at any specific point in time is not reliable. In particular, the information is many times too unreliable for the user to be able to correctly determine whether or not the quota is about to run out, or how much data is left of the current quota.

The present invention solves this problem.

Thus, the invention relates to a method for managing user account data relating to the use of a mobile communications unit, wherein a gateway node communicates information regard^¬ ing consumption of mobile communication services to a charging server in the form of an OCS (Online Charging Server) or an RTS (Realtime Charging Server) , which method is characterized in that the charging server is caused to provide a first digital communications interface arranged to accept queries regarding the updated data communication usage of a particu^¬ lar mobile communication device or a particular mobile subscription, in that a BSS (Business Support System) is caused to provide a second digital communications interface arranged to accept queries regarding current data communication usage, and in that the BSS is caused to, upon a request for updated data communication usage information via said second interface, query the charging server, via said first interface, regarding the updated data communication usage and to, in reply to said query, return updated data communication usage information .

Further, the present invention relates to a system.

In the following, the invention will be described in detail, with reference to the appended drawings, where:

Figure 1 is a simplified overview diagram of a known system for managing data communication usage;

Figure 2 is a simplified overview diagram of a system accord^¬ ing to the present invention for use in a method according to the present invention; and

Figure 3 is a flow chart of a method according to the present invention.

Hence, figure 1 shows a conventional system 100 for managing data communication usage. The system 100 is for 2G or 3G communications, but corresponding systems are also known for LTE . Mobile data communications 111 are routed via a GGSN 110, in a way which is conventional as such. The data traffic 111 gives rise to data usage information data 112, such as in the form of CDR:s, that are sent to a database 120. The pro^¬ duction and sending of the CDR:s 112 may involve a charging server (not shown in figure 1) .

An intermediary data processing unit 130, which may comprise for instance a conventional mediation device and a conven^¬ tional rating engine, reads 131 the CDR database 120 in an intermittent, batch-wise manner; processes the CDR infor^¬ mation; and stores 132 the processed information in an addi^¬ tional database 140. Thereafter, a BSS 150 reads 151, in another series of intermittent batch jobs, the processed information from the data^¬ base 140, and updates its information regarding the current data usage for a particular mobile user using the said pro^¬ cessed information. The BSS 150 also feeds 152 user data usage information to a user portal 160, which is arranged to hold updated information regarding particular users, such as current data consumption plan and current quota usage. Users can access the user portal 160 via an external interface 161, for instance over the internet. Using this interface 161, a user may, for instance, view current data usage and update user-related information and subscription parameters.

Since the steps 112, 131, 132, 151, 152 are associated with latency, in particular since they involve batch-wise data fetching and data processing, the data communication usage information available to the user portal 160 at any given moment is uncertain. This is particularly true for high-speed mobile data connections, such as LTE connections, since sub^¬ stantial amounts of data can be used before the information at the user portal 160 actually has been updated. This in turn makes it difficult for a user to maintain a valid view of current data consumption status via interface 161. Also, it is difficult to implement advanced data consumption con^¬ trolling functionality in the user portal 160.

Figure 2 illustrates a system 200 according to the invention for managing user account data relating to the use of a mo^¬ bile communications unit (not shown in figure 2) . The system 200 comprises a gateway node 210, which may be a GGSN, PGW or similar. The node 210 is arranged to provide mobile communi^¬ cations 211 to and from the mobile device in a way which is conventional as such. The node 210 is caused to communicate with a charging server 220 via a digital communications interface 212, preferably a bidirectional interface, most preferably a diameter inter^¬ face. It is preferred that the gateway node 210 is arranged to communicate continuously updated data communication usage information to the charging server 220, such as continuously delivered information regarding used number of data chunks of a given size. The information is preferably provided in realtime or near realtime for at least one or, preferably, a plurality of users, most preferably for all users handled by the gateway node 210. The expression "realtime or near realtime" is intended to mean that no significant buffering is performed in connection to interface 212, but that updated usage data is distributed to the charging server 220 substan^¬ tially immediately when the usage data has been updated. It may, however, be so that an update is sent only when a com^¬ plete block of data, such as a data chunk, has been handled by the node 210.

The charging server 220 may produce CDR:s 221 for further processing by subsequent steps (not shown) , that may be simi^¬ lar to the steps shown in figure 1. It is preferred that the charging server 220 is either an OCS or an RTS .

According to the invention, the charging server 220 is ar- ranged with a digital communications interface 222, arranged to accept and respond to queries for updated data communica^¬ tion usage information, preferably for a certain mobile communication device or a particular mobile subscription, such as identified using an IMSI (International Mobile Subscriber Identity) code for a particular mobile communications device or an MSISDN code for a particular mobile subscription.

Further according to the invention, a BSS 230 is arranged with a digital communications interface 231, arranged to accept and respond to queries regarding current data communi^¬ cation usage. Preferably, a user portal 240, such as a web server hosting a web service accessible to mobile users of the system 200 and/or maintenance personnel, is arranged with an external interface 241, such as a web interface arranged to present user account data status, via which for instance a mobile user can query for, view and possibly modify mobile subscription parameter settings, such as personal data, current service plan and so forth. It is also preferred that the interface 241 is arranged to accept commands for purchasing more connectivity for a certain subscription or mobile commu^¬ nications unit. Hence, the user can purchase such additional connectivity or data communication services, such as addi^¬ tional data volumes once or before the current quota runs out, via the user portal 240.

According to the invention, the BSS 230 is arranged to, upon a request for updated data communication usage information via the interface 231, query the charging server 220, via the interface 222, regarding the updated data communication usage and to, in reply to said first query, return updated data communication usage information via interface 231.

Figure 3 illustrates the method steps of a method according to the invention, using a system 200 such as the one illustrated in figure 2.

In a first step, the above discussed gateway node 210, the charging server 220, the BSS 230 and the user portal 240 are provided. In a second step, the interface 222 is provided at and by the charging server 220, arranged to accept and reply to queries regarding the updated data communication usage of a particular mobile communication device or a particular mobile subscription. In a third step, the interface 231 is provided at and by the BSS 230, arranged to accept and reply to queries regarding current data communication usage for a particular mobile communication device or a particular mobile subscription .

In a fourth step, the user uses the said mobile communica^¬ tions device for communicating, such as sending/receiving e- mails or other messages; surfing the web; watching streamed media; and so on. It is preferred that all such communica- tions being handled by the system 200 are data traffic only, and as such to no part comprising pure voice traffic. These communications are routed via the gateway node 210.

As a result, in a fifth step, the gateway node 210 provides, via interface 212, the above discussed information to the charging server 220. This provision preferably takes place continuously, preferably essentially as soon as the communi^¬ cation in question has taken place, possibly once a small fixed-sized amount of data communication, such as a single data chunk as discussed above, has been completed. A pre^¬ ferred delivery format is number of data chunks of a certain size .

This provision is performed for as long as the user carries on with said mobile data communications. At some point, the user wants to view his or her currently updated data communi^¬ cation usage, preferably for a particular mobile communica^¬ tion device or a particular subscription, such as the subscription used by the currently active mobile communications device. The user then, in a sixth step, interacts with the user portal via interface 241, and requests data usage infor^¬ mation . As a result, in a seventh step, a query is sent form the user portal 240 to the BSS 230, via interface 231, requesting updated data communication usage information. The BSS 230, in an eighth step, as a reaction to the query in the seventh step, queries, using the interface 222, the charging server for updated such information. Since the charging server has been provided continuously updated information all along, it can and will, in a ninth step, reply to the BSS 230 via in^¬ terface 222 with the requested updated data communication usage information.

Then, in a tenth step, the BSS 230 replies, via interface 231, to the user portal 240 with the updated usage infor^¬ mation. Finally, in an eleventh step, the user portal 240 presents the updated information to the user via interface 241; uses the updated information internally in the portal 240 in a processed way or as a basis for an automated usage managing functionality provided to the user; or uses the updated usage information in any other suitable way. In a preferred embodiment, the interface 241 is a web interface, which is arranged to, in said eleventh step, display infor^¬ mation based upon the data returned from the BSS 230 to the user portal 240, in a way so that the user can view this information in a conventional web browser or the like. According to a preferred embodiment, the BSS 230 is arranged to only send at the most a limited number of queries per time unit regarding updated data communication usage information to the charging server 220. It is preferred that this limited number is maximally 100 queries per second, more preferably maximally 10 queries per second, for all subscriptions han^¬ dled by the BSS 230. Alternatively or in addition thereto, it is preferred that the limited number is maximally 1 query per second, more preferably maximally 1 query per 10 seconds, for each individual subscription handled by the BSS 230. The BSS 230 is preferably arranged with software-implemented logic for monitoring that too frequent queries are not handled. In case too frequent queries arrive via the interface 231, it is preferred that the BSS 230 either queues surplus queries for handling at an allowed rate, or denies them.

It is furthermore preferred that the interface 222 is caused to only accept a limited number of queries per time unit regarding updated data communication usage information. This restriction may be implemented as a software function in the charging server 220. The limited number of queries per time unit is preferably maximally 100 queries per second, more preferably maximally 10 queries per second, for all subscrip^¬ tions handled by the server 220, and alternatively or in addition thereto maximally 1 query per second, more prefera^¬ bly maximally 1 query per 10 seconds, for each individual subscription handled by the server 220.

It is furthermore preferred that the charging server 220 does not provide the BSS 230 with continuously updated usage in^¬ formation. In particular, it is preferred that the charging server 220 is arranged to only provide updated usage infor^¬ mation to the BSS 230 as a response to a query from the BSS 230 via interface 222.

According to a preferred embodiment, the mobile communica^¬ tions device or the mobile subscription is identified using a corresponding IMSI (International Mobile Subscriber Identity) or a corresponding MSISDN, and the IMSI or MSISDN is associ- ated with a user account; the mobile communications device; and/or the subscription in the charging server 220. The corresponding association is preferably also made in the BSS 230 and in the user portal 240. Preferably, said user account is further associated with at least one particular mobile commu^¬ nications device or at least one particular subscription in the user portal 240, whereby the user can login to the user portal 240 and automatically be provided updated information regarding current data usage status for one or all of the user's active mobile data subscriptions.

As is illustrated in figure 2, a query posed to the interface 231 is processed in a straight-through process, via functionality internal to BSS 230, interface 222, functionality in- ternal to charging server 220, and back again, via interface 222, internal BSS 230 functionality and interface 231. In other words, there is preferably no aggregation of queries or query replies in a method and system 200 according to the invention, and each query to interface 231 is preferably dealt with completely, until final reply is delivered via interface 231, essentially immediately when the query is received .

By using such a method and system 200, precise and accurate control over data communications usage information can be achieved in near realtime, even on a level as high as a web server accessible for individual users, without having to deal with a stream of very frequently updated information from a GGSN or the like, via a charging server and to a BSS.

Furthermore, the method and system 200 achieves acceptable results even in the case in which the BSS 230 is arranged geographically distant from the charging server 220, since the latency when querying for updated usage information over the Internet in most cases is acceptable, in particular when in the context of a user-accessible web page. According to one. At the same time, it is preferred that the charging server 220 is arranged in geographic proximity to, such as in the same premises, to the node 210.

Above, preferred embodiments have been described. However, it is apparent to the skilled person that many modifications may be made to the described embodiments without departing from the basic thought of the invention.

For instance, a method according to the present invention can be used with other wireless networks than a 2G, 3G or LTE network, using the corresponding principles.

Also, plenty of additional functionality can be built into the various components 210, 212, 220, 221, 222, 230, 231, 240, 241 described above. For instance, the BSS 230 may be arranged with functionality for keeping track of the current- ly allowed data quota for a particular user, device or sub^¬ scription. Then, the node 210 may query the charging server 220 for such an allowed quota, which query is re-stated from the charging server 220 to the BSS 230 via interface 231. Thus, the invention shall not be limited to the described embodiments, but may be varied within the scope of the en^¬ closed claims.

Claims

C L A I M S

1. Method for managing user account data relating to the use of a mobile communications unit, wherein a gateway node (210) communicates information regarding consumption of mobile communication services to a charging server (220) in the form of an OCS (Online Charging Server) or an RTS (Realtime Charging Server), wherein the charging server (220) provides a first digital communications interface (222) arranged to accept queries regarding the updated data communication usage of a particular mobile communication device or a particular mobile subscription, in that a BSS (Business Support System)

(230) provides a second digital communications interface

(231) arranged to accept queries regarding current data com- munication usage, and wherein the BSS (230), upon a request for updated data communication usage information via said second interface (231), queries the charging server (220), via said first interface (222), regarding the updated data communication usage and to, in reply to said query, returns updated data communication usage information, c h a r a c t e r i z e d i n that the gateway node (210) is caused to communicate continuously updated data communication usage information to the charging server (220), in that the charging server (220) is caused not to provide the BSS (230) with continuously updated usage information, and in that the BSS (230) is caused to only send a limited number of queries per time unit regarding updated data communication usage information to the charging server (220) .

2. Method according to claim 1, c h a r a c t e r i z e d i n that the gateway node (210) is caused to communicate with the charging server (220) via a diameter interface.

3. Method according to claim 1 or 2, c h a r a c t e r i z e d i n that the first interface (222) is caused to only accept a limited number of queries per time unit regard^¬ ing updated data communication usage information.

4. Method according to any one of the preceding claims, c h a r a c t e r i z e d i n that the mobile communications device or the mobile subscription is identified using a cor^¬ responding IMSI (International Mobile Subscriber Identity) or a corresponding MSISDN, and that the IMSI or MSISDN is associated with a user account, the mobile communications device or the subscription in the charging server (220), and preferably also in the BSS (230) and in a user portal (240) con^¬ nected to the BSS (230) .

5. Method according to any one of the preceding claims, c h a r a c t e r i z e d i n that a user portal (240) , pref^¬ erably comprising a web server, is caused to provide a third interface (241), such as a web interface, arranged to present user account data status, in that the user portal (240) que^¬ ries the BSS (230) for such data, via the second interface (231), and in that the third interface (241) displays infor^¬ mation to the user based upon data returned from the BSS (230) .

6. Method according to claim 5, c h a r a c t e r i z e d i n that the second interface (231) is caused to accept commands for purchasing more connectivity for the mobile communication unit or a particular subscription.

7. System (200) for managing user account data relating to the use of a mobile communications unit, wherein a gateway node (210) is arranged to communicate information regarding consumption of mobile communication services to a charging server (220) in the form of an OCS (Online Charging Server) or an RTS (Realtime Charging Server) , which charging server (220) is comprised in the system (200), the charging server (220) is arranged to provide a first digital communications interface (222), in turn arranged to accept queries regarding the updated data communication usage of a particular mobile communication device or a particular mobile subscription, in that the system (200) further comprises a BSS (Business Sup^¬ port System) (230), arranged to provide a second digital communications interface (231), in turn arranged to accept queries regarding current data communication usage, and in that the BSS (230) is arranged to, upon a request for updated data communication usage information via said second interface (231), query the charging server (220), via said first interface (222), regarding the updated data communication usage and to, in reply to said query, return updated data communication usage information, c h a r a c t e r i z e d i n that the gateway node (210) is arranged to communicate continuously updated data communication usage information to the charging server (220), in that the charging server (220) is not arranged to provide the BSS (230) with continuously updated usage information, and in that the BSS (230) is ar^¬ ranged to only send a limited number of queries per time unit regarding updated data communication usage information to the charging server (220) .

8. System (200) according to claim 7, c h a r a c t e r i z e d i n that the first interface (222) is arranged to only accept a limited number of queries per time unit regard^¬ ing updated data communication usage information.

9. System (200) according to claim 7 or 8, c h a r a c t e r i z e d i n that the system (200) further comprises a user portal (240), preferably comprising a web server, arranged to provide a third interface (241), such as a web interface, in turn arranged to present user account data status, in that the user portal (240) is arranged to query the BSS (230) for such data, via the second interface (231), and in that the third interface (241) is arranged to display information to the user based upon data returned from the BSS (230) .

10. System (200) according to claim 9, c h a r a c t e r i z e d i n that the second interface (231) is arranged to accept commands for purchasing more connectivity for the mobile communication unit or a particular subscription.