Methods and systems for differential billing of services used during a mobile data service session

[0001] Embodiments of the present invention pertain to methods and systems for differential billing of services used during a mobile data service session.

[0002] The Internet facilitates the access of resources that are available on the world-wide-web. Many different types of services are available that provide access to the Internet. These services provide access to the Internet via various devices such as computers, mobile phones, etc. Mobile data services provide access to the Internet via mobile phones.

[0003] Mobile data services facilitate the access of Internet resources by mobile data service customers. Internet based resources that can be accessed by mobile data service customers via mobile data services include services such as world-wide-web services, email, VoIP, text messaging, etc. Mobile data services charge for the use of the services that they provide to mobile data service users.

[0004] Mobile data service providers maintain billing systems that allow the mobile data service providers to charge customers for the mobile data services that they use. The systems that facilitate customer billing are maintained by the mobile data service and can be accessed by authorized requestors. Conventional mobile data services maintain systems for compiling billing records for their customers.

[0005] General Packet Radio Service/Universal Mobile Telecommunications System (GPRS/UMTS) is a mobile data service that is available to users of GSM mobile phones. In GPRS/UMTS networks, a gateway support node (e.g., GGSN) generates billing records called Call Detail Records (G-CDRs). The G-CDR contains the usage information for various events for a specific PDP context of the user. A user can do multiple different services on the same packet data protocol (PDP) contexts. However, with standard G-CDR there is no way to do differential billing for the services since it does not have any service specific information in it.

[0013] The drawings referred to in this description should not be understood as being drawn to scale except if specifically noted.

[0014] Reference will now be made in detail to various embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with these embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.

[0015] FIG. 1A shows an exemplary network setting 100 of a system for differential billing of services used during a mobile data service session (SDBS) according to one embodiment of the present invention. In one embodiment, SDBS 105 accommodates a fine-grained accounting of mobile data service usage by providing an accounting of each of the services used during a mobile data service session. FIG. 1A shows mobile data service user 101, mobile data service 103, SDBS 105 and access point 107.

[0016] Referring to FIG. 1A, mobile data service user 101 uses a mobile data telecommunications device (e.g., mobile telephone) to initiate, facilitate and terminate a mobile data service session. In one embodiment, during a mobile data service session one or more services can be solicited and used by mobile data service user 101. It should be appreciated that service specific parameters can be used to determine service usage of specific services by a mobile data service user 101. In one embodiment, these parameters correspond to layers 4-7 of the open systems interconnect (OSI) model. In other embodiments, these parameters can include other services.

[0017] In one embodiment, the aforementioned service specific parameters that can be used to determine usage of specific services can include but are not limited to service specific identifiers, charging status to indicate pre-paid or post-paid user status, time of first usage and time of last usage, time based usage, uplink and downlink volume usage, negotiated QoS, SGSN IP address, PLMN identifier, reason for the usage report.

[0018] Mobile data service 103 facilitates the access by mobile data service user 101 of access point 107. In one embodiment, access point 107 is an IP network to which a mobile device can be connected. In one embodiment, mobile data service 103 can be operated under the control of a service provider.

[0019] In one embodiment, mobile data service 103 can include one or more support nodes. Moreover, these support nodes can be implemented using a data relay device (e.g., routers, switches, etc.).

[0020] FIG. 1B shows exemplary nodes (e.g., components) of a mobile data service 103 according to one embodiment of the present invention. It should be appreciated that the components of mobile data service 103 shown in FIG. 1B are exemplary of one embodiment of the present invention. However other components can be used in other embodiments. In the FIG. 1B embodiment, mobile data service 103 includes base station controller (BSC) 103A, mobile switching center (MSC) 103B, serving support nodes (SGSN) 103C, gateway support nodes (GGSN) 103D, and charging gateway (CG) 103E.

[0021] Referring to FIG. 1B, BSC 103A is the base station control system that manages base station operations that connect mobile data service users 101 to mobile data service 103. BSC 103A handles allocation of radio channels, receives measurements from mobile phones and controls handovers.

[0022] MSC 103B is a telephone exchange that provides circuit-switched calling, mobility management, and global system for mobile communications (GSM) services to mobile data service users 101 as mobile data service users 101 roam within the area that it serves.

[0023] SGSN 103C decides which GGSN is to be used for a particular mobile data service session. SGSN 103C carries out uplink and downlink functions and provides mobility management as mobile data service user 101 moves from routing area to routing area.

• • [0024] GGSN 103D generates billing records for mobile data service sessions. In one embodiment, GGSN 103D is the component of mobile data service 103 where SDBS 105 actually resides. In other embodiments, SDBS 105 can be separate from but operate cooperatively with GGSN 103D. GGSN 103D provides an interface between mobile data service 103 and other networks such as the Internet or private networks.

[0025] In one embodiment, CG 103E receives billing information from mobile data service GGSN 103D. In one embodiment, for pre-paid users, GGSN 103D communicates with CG 103E for quota authorization and usage reporting. In one embodiment, the various triggers and thresholds for generating the aforementioned service usage reports are obtained from the CG 103E. In one embodiment, there can be a billing records closure criteria maintained by CG 103E that is based on a specific number of service records.

[0026] Referring again to FIG. 1A, SDBS 105 accommodates a fine-grained differential billing of services used by mobile data service user 101 during mobile data service sessions. SBDS 105 directs the compilation of service usage reports for each of the services used by mobile data service user 101 during a mobile data service session as is describe herein in detail. In one embodiment, the service usage reports can be maintained in the aforementioned billing records generated by GGSN 103D.

Operation

[0027] In operation, service user 101 initiates a mobile data service session using a mobile telecommunications device. Upon initiation of the mobile service session and being connected to an access point 107 via mobile data service 103, a monitoring of the mobile data service session is begun. When the mobile data service session is terminated, an accounting of service usage by mobile data service user 101 is made for billing purposes. As a part of the accounting, a service usage report for each of the services used by a service user 101 is made. These reports correspond to service specific parameters that are included in system billing records. From these service usage reports charges for a mobile service user based on differential billing can be determined.

[0028] In one embodiment, specific services (A, C and H) that are used during a particular mobile data service session are identified as is shown in FIG. 1C. As shown in FIG. 1C, after the services used during a service session are identified, the aforementioned service usage reports can be compiled. From the compiled reports the total charges for a mobile data service session can be determined.

[0029] In one embodiment, billing records also contain the usage information for various events that occur during a specific mobile data service session of a service user (e.g., 103). It should be appreciated that a mobile data service user (e.g., 103) can use many services during a single service session.

[0030] In exemplary embodiments, billing records are expanded to include the aforementioned service specific usage information. In one embodiment, it can include billing information relevant to both pre-paid and post-paid billing.

[0031] FIG. 2 shows components of a system 105 for differential billing of services (SDBS) used during a mobile data service user session according to one embodiment of the present invention. In the FIG. 2 embodiment, SDBS 105 includes user session detector 201, user identifier 203, service identifier 205, service usage report generator 207, access provider 209.

[0032] Referring to FIG. 2, user session identifier 201 identifies a mobile data service user session for billing purposes. In one embodiment, the mobile data service user session can involve the access of Internet resources using the mobile data service by a mobile data service user.

[0033] User identifier 203 identifies a user that is associated with an identified user session. In one embodiment, an identification of the particular user that is associated with an identified user session facilitates a determination of service specific parameters that are to be used in the billing process (e.g., proper charging profile etc.)

[0034] Service identifier 205 identifies one or more services used by a user during a mobile data service session. In one embodiment, identifying the one or more services that are used by a user facilitates differential billing which tracks charges for each of the services that are used by a user during a user session.

[0035] Service usage report generator 207 generates a service usage report for each of the identified one or more services used by the user during a mobile data service session. In one embodiment, a service usage report details the amount of each service of the identified one or more services that is used by a service user.

[0036] Access provider 209 provides access to mobile data service user service usage reports. In one embodiment, service usage reports can be used to determine session charges for a particular mobile data service session of a particular mobile data service user.

[0037] FIG. 3 shows a flowchart 300 of the steps in a method for differential billing of services (SDBS) used during a mobile data service user session according to one embodiment of the present invention. The flowchart includes processes of the present invention which, in one embodiment can be carried out by processors and electrical components under the control of computer-readable and computer-executable instructions. Although specific steps are disclosed in the flowcharts, such steps are exemplary. That is the present invention is well suited to performing various other steps or variations of the steps recited in the flowcharts. Within various embodiments, it should be appreciated that the steps of the flowcharts can be performed by software, by hardware or by a combination of both.

[0038] Referring to FIG. 3, at step 301, a mobile data service user session is identified. In one embodiment, a session identifier (e.g., 201 in FIG. 2) can be employed to identify a mobile data service user session for billing purposes. In one embodiment, the mobile data service user session can involve the access of Internet resources by a mobile data service user using the mobile data service.

[0039] At step 303, a user associated with an identified mobile data service user session is identified. In one embodiment, a user identifier (e.g., 203 in FIG. 2) identifies a user that is associated with an identified user session. In one embodiment, an identification of the particular user that is associated with an identified user session facilitates a determination of certain service specific parameters that are to be used in the billing process (e.g., proper charging profile etc.)

[0040] At step 305, one or more services used by a user during a mobile data service session are identified. In one embodiment, a service identifier (e.g., 205 in FIG. 2) can be used to identify one or more services used by a user during a mobile data service session. In one embodiment, identifying the one or more services that are used by a user facilitates differential billing which tracks charges for each of the services that are used by a user during a user session.

[0041] At step 307, a service usage report is generated for each of the identified one or more services used during a mobile data service session. In one embodiment, a service usage report generator (e.g., 207 in FIG. 2) generates a service usage report for each of the identified one or more services used by the user during a mobile data service session. In one embodiment, a service usage report details the charges for each service of the identified one or more services that is used by a service user.

[0042] At step 309, access to service user service usage reports are provided. In one embodiment, an access provider (e.g., 209 in FIG. 2) can be used to provide access to service user service usage reports. In one embodiment, service usage reports can be used to determine session charges for a particular mobile data service session of a particular mobile data service user.

[0043] FIG. 4 is a block diagram of an exemplary computer system 400 in accordance with embodiments of the present invention. System 400 may be well suited to be any type of electronic computing device (e.g., server computer, embedded computing device, portable computing system etc.). Within the following discussions herein, certain processes and steps are discussed that are realized, in some embodiments, as a series of instructions (e.g., software program) that reside within computer readable memory units of computer system 400 and executed by a processor(s) of system 400. When executed, the instructions cause computer 400 to perform specific actions and exhibit specific behavior which is described in detail below. According to one embodiment, the instructions may include code that when executed perform the method for differential billing of services (SDBS) used during a mobile data service user session described herein.

[0044] Computer system 400 of FIG. 4 comprises an address/data bus 414 for communicating information, one or more central processors 402 coupled with bus 414 for processing information and instructions. Central processor unit 402 may be a microprocessor or any other type of processor. The computer 400 also includes data storage features such as a computer usable volatile memory unit 404 (e.g., random access memory, static RAM, dynamic RAM, etc.) coupled with bus 414 for storing information and instructions for central processor(s) 402, a computer usable non-volatile memory unit 406 (e.g., read only memory, programmable ROM, flash memory, EPROM, EEPROM, etc.) coupled with bus 414 for storing static information and instructions for processor(s) 402. System 400 also includes one or more signal generating and receiving devices 408 coupled with bus 414 for enabling system 400 to interface with other electronic devices. The communication interface(s) 408 of the present embodiment may include wired and/or wireless communication technology such as a wireless telephone circuitry. For example, in some embodiments, the communication interface 408 is a serial communication port, but could also alternatively be any of a number of well known communication standards and protocols, e.g., Universal Serial Bus (USB), Ethernet, FireWire (IEEE 1394), parallel, small computer system interface (SCSI), infrared (IR) communication, Bluetooth wireless communication, broadband, and the like.

[0045] The system 400 may also include a computer usable mass data storage device 412 such as a magnetic or optical disk and disk drive (e.g., hard drive or floppy diskette) coupled with bus 414 for storing information and instructions.

[0046] In accordance with exemplary embodiments thereof, methods and systems for differential billing of services used during a mobile data service user session are disclosed. A method includes identifying a mobile data service user session and identifying a mobile data service user that is associated with the identified mobile data service user session. One or more services used by the mobile data service user during the mobile data service user session are identified. A service usage report is generated for each of the one or more services used by the mobile data service user. The usage reports are based on a measure of service usage of each of the identified one or more services and a billing profile that is associated with the user. Access is provided to the user service usage reports for storage as a part of billing records.

[0047] The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents.