WO2010005376A1 - Sélection de compte flexible en temps réel pour des communications - Google Patents

Sélection de compte flexible en temps réel pour des communications Download PDF

Info

Publication number
WO2010005376A1
WO2010005376A1 PCT/SE2009/050849 SE2009050849W WO2010005376A1 WO 2010005376 A1 WO2010005376 A1 WO 2010005376A1 SE 2009050849 W SE2009050849 W SE 2009050849W WO 2010005376 A1 WO2010005376 A1 WO 2010005376A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
call
filter
user
communications
Prior art date
Application number
PCT/SE2009/050849
Other languages
English (en)
Inventor
Andreas Abrahamsson
Johan Silvander
Robert TÖRNKVIST
Joachim Wahlberg
Original Assignee
Telefonaktiebolaget L M Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/171,641 external-priority patent/US20100008484A1/en
Priority claimed from US12/258,990 external-priority patent/US20100104076A1/en
Application filed by Telefonaktiebolaget L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Priority to EP09794730.3A priority Critical patent/EP2301191A4/fr
Publication of WO2010005376A1 publication Critical patent/WO2010005376A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1425—Charging, metering or billing arrangements for data wireline or wireless communications involving dedicated fields in the data packet for billing purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/08—Metering calls to called party, i.e. B-party charged for the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/10—Metering calls from calling party, i.e. A-party charged for the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/77—Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/72—Account specifications
    • H04M2215/724—Linked accounts
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/72—Account specifications
    • H04M2215/724—Linked accounts
    • H04M2215/7254—Multiple accounts per user

Definitions

  • This invention pertains to communications, and particularly to methods and apparatus for accounting and/or charging for services rendered by communications companies and utilized by communication customers.
  • Communications companies e.g., telecommunications operators
  • the revenue realized by communications companies upon customer payment (whether in advance or after service) defrays, among other things, the initial capital outlay and maintenance of the network infrastructure, as well as day-to-day operating costs.
  • Some customers may pay a flat fee for communications services.
  • Most customers have an account which is established by a contract or fee arrangement/agreement.
  • a customer's account is structured or arranged, at least in part, so that the customer is assessed a communications fee which is dependent upon an amount of time or other network resource which is utilized by the customer (e.g., degree or quality of service, calendar or clock time of service, for example).
  • the fee or charge typically either reduces a prepaid amount existing in the customer's account, or accumulates against the credit of the customer and is presented for subsequent payment.
  • the communications network provides some type of monitoring of resource consumption by the customers.
  • the monitoring can occur at faculties or nodes involved in setup or administration of the services (e.g., of a call or connection).
  • the resource monitoring and/or other types of reports from the communications network are communicated to a real-time charging system which associates the call or session with a customer's account as maintained by the charging system, and may send reports (e.g., Call Detail Record (CDR) files) to an off-line billing system which is maintained by the communications operator.
  • CDR Call Detail Record
  • the billing system likewise has an off-line account which is associated with the customer, and which includes other (e.g., historical information).
  • a billing system connected directly to the communications equipment without a real-time charging system lacks the possibility of providing real-time credit control (to protect the operator) and real-time spending control (to protect the end-user).
  • the billing systems only acts upon historical records received from the communications equipment (e.g., telecom equipment).
  • the billing system by itself might be able to handle complex relations between accounts and services, but unless connected to a real-time charging system would lack the benefit of handling the balance and usage in real-time.
  • Real-time accounts of a real-time charging system can hold different
  • Buckets or subaccounts, each with a reserved amount, that can only be used for a specific service, e.g. SMS, GPRS etc.
  • a specific service e.g. SMS, GPRS etc.
  • the charging system maintains an account for a customer, at least during the life of the call, connection, or session involving the customer.
  • the account is connected to (e.g., associated with or identified by) a user identifier or user identity such as, e.g. MSISDN (Mobile Subscriber Integrated Services Digital Network Number) or SIP URI (Session Initiation Protocol Uniform Resource
  • a communications account can, in turn, have subaccounts for a specific service, like download of music, for example, in order for a customer to partition or itemize transactions according to a certain criteria (such as type of service utilized, for example).
  • a certain criteria such as type of service utilized, for example.
  • some customer accounts such as corporate accounts
  • Some household customer accounts are partitioned for billing purposes to be able to associate charges with family members or individuals.
  • the technology disclosed herein concerns a method of operating a communications system to charge a call to one or more customer accounts.
  • the term "call” is used throughout the description and may be used interchangeably for event, session, services, etc.
  • the method comprises receiving a user identifier from a communications network in conjunction with a communications call or session (the user identifier being associated with a first account), using a filter for the first account to make a determination whether the call should (alternatively or partially) be associated with a second account; and charging the call to at least one of the customer accounts in accordance with the determination.
  • the first filter associated with the first account makes the determination based, at least in part, on a service parameter of the call.
  • the service parameter of the call can be (by way of non-limiting example) at least one of type of service utilized by the call; time of the call; location of a party to the call; particular user identity employed at authentication of the call
  • An example mode of the method includes initially associating the call to a first account in accordance with the user identifier employed by a party participating in the call.
  • the example mode further comprises using the first filter for the first account to determine, based on the characteristic, whether the call should alternatively or partially be associated with the second account. If the first filter indicates that the call should be associated with the second account, the example mode uses a second filter of the second account to make a confirmation whether the second account can be associated with the call. If the confirmation can be made, the call is charged (at least partially) to the second account. If the confirmation cannot be made, the call is charged to the first account.
  • the charging system comprises an information storage database (comprising plural customer accounts); account selection logic; and an account charging unit.
  • the account selection logic comprises account-based filters which are configured to make a determination whether the call, having a user identifier which is associated with a first account, should be alternatively or partially associated with a second account.
  • the account charging unit is configured to develop financially related information for the call.
  • a first filter for a first account makes the determination based on a characteristic of the call.
  • the characteristic of the call can be at least one of type of service utilized by the call; time of the call; location of a party to the call; particular user identity employed at authentication of the call.
  • the filters can also use information collected from the account storage database or external database as input for determining the association.
  • the account selection logic comprises a set of filters comprising a first filter for the first account which is configured initially to associate the call to a first account in accordance with the user identifier and to determine, e.g., based on the characteristic, whether the call should alternatively or partially be associated with the second account.
  • the account selection logic is further configured, if the first filter indicates that the call should be associated with the second account, to comprise a second filter of the second account which is configured to make a confirmation whether the second account can be associated to the first account. If the confirmation can be made, the account selection logic is configured to direct the charging unit to charge the call to the second account. If the confirmation cannot be made, the account selection logic is further configured to direct the charging unit to charge the call to the second account.
  • the technology disclosed herein thereby provides many advantages.
  • One advantage is that an operator need only have one entry for each party. This in turn provides other benefits: (1) a party can get one bill/invoice/statement no matter what user identity the party may have used; (2) the operator can give promotions based on such criteria as the services the party is using, the time of day, the location, etc., and not the user identity; and (3) the party can use any user identity and be charged correctly.
  • the technology disclosed herein affords an opportunity to define complex business rules without impact in the communications environment e.g. selection of sponsored calls/services for family or corporations.
  • the technology disclosed herein thus may permit the redirecting of costs from one account to another (alternative) account.
  • the technology disclosed herein also permits but does not mandate the sharing of cost between plural customer accounts.
  • FIG. 1 is a diagrammatic view showing plural example contact identifiers associated with a representative user.
  • FIG. 2 is a diagrammatic view showing plural example roles potentially played or fulfilled by a representative user.
  • FIG. 3 is a diagrammatic view of an example, generic embodiment of a communications system suitable for real-time flexible account selection technology.
  • Fig. 4 is a diagrammatic view showing an embodiment of account selection logic that comprises a filter function.
  • Fig. 5 is a diagrammatic view showing a scenario of operation of a user of Fig. 1 in the communications system of Fig. 3.
  • Fig. 6 is a flowchart showing basic, example steps or acts involved in a generic method of real-time flexible account selection.
  • Fig. 7 is a flowchart showing basic, example steps or acts performed in an example mode by account selection logic of the system of Fig. 3.
  • FIG. 8 is a diagrammatic view of an example, detailed embodiment of a communications system suitable for real-time flexible account selection technology.
  • Fig. 9 is a flowchart showing basic, example steps or acts performed in an example mode by account selection logic of the system of Fig. 8.
  • Fig. 10 is a diagrammatic view of an example, detailed embodiment of a real-time charging system in which filters are configurable, e.g., by an account owner.
  • Fig. 11 is a diagrammatic view of an example, detailed embodiment of a real-time charging system in which one or more filters comprise or have access to financial manager/accumulator.
  • Fig. 12 is a diagrammatic view of an example embodiment of account selection logic which provides an account redirection capability.
  • processors may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software.
  • the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared or distributed.
  • explicit use of the term "processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may include, without limitation, digital signal processor (DSP) hardware, read only memory (ROM) for storing software, random access memory (RAM), and non- volatile storage.
  • DSP digital signal processor
  • ROM read only memory
  • RAM random access memory
  • a user 10 can be any natural or physical person or entity (e.g., human being) or legal person or entity (e.g., organization or corporation).
  • the user 10 is identified by a "party ID" (PID).
  • the party ID in the case of a natural or physical person, can be a number such as a social security number, for example.
  • the party ID in the case of a legal person or entity, can be a suitable corporate or organization identifier, such as a taxpayer ID number, for example.
  • Fig. 1 further shows that user 10 can be assigned or associated with one or more contact identities (CIDs).
  • Each contact identify (CID) can be an identifier or user name or a network number or the like through which can be used by user 10 to gain access to a communications service.
  • CIDl for email protocol
  • CID2 for Session Initiation Protocol [SIP]
  • CIDn for MSISDN.
  • PID party ID
  • CID contact identity
  • Fig. 2 illustrates that user 10 may fulfill or play one or more roles in conjunction with his/her communications activities.
  • user 10 can be an employee.
  • user 10 can be a private consumer.
  • user 10 can be a vendor.
  • Fig. 3 shows an example communications system comprising a communications network 20 which has access to a real-time charging system 22 and, through real-time charging system 22, to off-line billing system 24.
  • the communications network 20 can be or comprise any type or radio access network or other type access network, alone or in combination with one or more core networks, and is typically provided and/or maintained, or is available for use, by a communications company or communications operator (e.g., telecommunications company or telecommunications operator ) which provides services to customers or subscribers in exchange for payment.
  • the communications network 20 can thus be or comprise, as examples, a network of a type known as the Universal Mobile
  • UMTS Terrestrial Radio Access Network
  • GSM Global System for Mobile communications
  • AMPS Advance Mobile Phone Service
  • NAMPS Narrowband AMPS type system
  • TACS Total Access Communications type system
  • PDS Personal Digital Cellular
  • the communications system 20 is not limited to wireless communication system but may be any type of, or combination, of data and/or telecommunication systems as fixed line telecommunication networks, IP Multimedia Subsystem (IMS), WLAN, Diameter/Content/Service delivery as specified by 3GPP.
  • IMS IP Multimedia Subsystem
  • WLAN Wireless Fidelity
  • 3GPP 3rd Generation Partnership Project
  • the real-time charging system 22 and off-line billing system 24 can, at least in some embodiments, comprise or be included in nodes or elements of communications network 20. However, as shown in Fig. 3, real-time charging system 22 and off-line billing system 24 are typically situated at nodes or service points which are external to communications network 20. As used herein, a service point or any other site or facility which performs the functions herein described for either real-time charging system 22 or off-line billing system 24 are included in the concept of "node", whether such node or service point is dedicated for the charging/billing function or happens to perform functions in addition to the charging/billing function.
  • Appropriate signaling connections and signaling protocols are established between communications network 20 and real-time charging system 22, as well as between real-time charging system 22 and off-line billing system 24.
  • communications equipment 20 may send call detail records (CDRs) in an off-line manner to the off-line billing system 24, or signal in real time with the real-time charging system 22.
  • CDRs call detail records
  • the transmission of call detail records (CDRs) between the real-time charging system 22 and the off-line billing system 24 is an issue in a converged system (e.g., for providing postpaid customer with real time spending control).
  • Fig. 3 illustrates generically (by communications activity monitor 26) a capability of communications system 20 to monitor communications activity, e.g., setup, termination, and intermediate events for calls and connections involving subscribers, and to obtain and/or signal information to real-time charging system 22 with respect to such activity.
  • the communications activity monitor 26 communicates with real-time charging system over an appropriate link and protocol.
  • the communications activity monitor 26 is configured to consult real-time charging system 22 and/or off-line billing system 24 upon attempted set up of a call or connection (e.g., a transaction) involving a subscriber, and upon approval and successful set up to provide to real-time charging system 22 and/or off-line billing system 24 information germane to the subscriber or the subscriber's account.
  • Such information can be generated by communications activity monitor 26, not only upon set up of a connection, but also at termination of the call or connection as well as intermediate points in between.
  • the information can be for example the contact identity CID as user identifier (e.g., MSISDN (Mobile Subscriber Integrated Services Digital Network Number) , a SIP URI (Session Initiation Protocol Uniform Resource
  • communications activity monitor 26 provides its information for multitudinous subscribers, and for repeated calls or connections of such subscribers on an on-going basis.
  • the communications activity monitor 26 thus typically represents numerous reporting agents comprising or interspersed within communications network 20, which can be situated at various locations throughout communications network 20.
  • communications activity monitor 26 can also be considered part of real-time charging system 22.
  • a generic, representative, real-time charging system 22 as shown in Fig. 3 comprises information storage database 30 (also known as real-time account database 30); account selection logic 32; and rating function 34.
  • realtime account database 30 comprises plural customer accounts 40, e.g., records for plural customer accounts.
  • real-time account database 30 comprises account 40] for customer #1 ; account 4O 2 for customer #2; account 4O n for customer #n; and so forth.
  • Each account 40 can include, for example, a real-time account balance for the corresponding customer.
  • account selection logic 32 is configured to make an assignment of a communications (e.g., telecommunications) call or session to a selected one or more of plural accounts 40.
  • the account selection logic 32 can, in an example embodiment, include a filter function or the like.
  • the filter function can receive input in the form of one or more service parameters (including the call characteristic) and/or use information collected from the account storage database or external database as input for making the determination as to which account(s) should be charged.
  • the filter function may fetch additional parameters from elsewhere for such purposes as (for example) number portability, location, etc., for a balance in available candidate accounts.
  • the account(s) to be charged as determined by the filter function may belong to any party, including the originating user (e.g., user 10).
  • the rating function 34 is configured to calculate the charge rate for the selected call or service, such that an account can be accurately adjusted to reflect the cost of the call/service.
  • FIG. 3 shows three units connected to communications network 20: user equipment (UE-A) 46 A , user equipment (UE-B) 46 B , and user equipment 46c.
  • UE-A user equipment
  • UE-B user equipment
  • user equipment 46c user equipment
  • Fig. 5 illustrates a scenario of operation for a user such as user 10 situated in the context of a communications network such as communications network of Fig. 3.
  • Fig. 5 shows (by broken line 48) that user 10 can play either of the three example roles shown in Fig. 2: the Role Rl of an employee; role R2 of a private consumer; role R3 of a vendor (among other possible roles).
  • party ID PID 1 Another party ID is also shown in Fig. 5, i.e., party ID PID2.
  • this other party ID can be owned by another entity 49, e.g., owned by the employer of user 10.
  • this other party ID can also be owned by user 10 (as an alias or additional personal identifier).
  • having an additional personal identifier can be useful to a user or party if the user desires to debit different accounts for different services, etc., or otherwise have some differentiation or categorization in his business affairs.
  • a first contact identity CID H for home use (home location) or in his/her personal consumer role
  • a second contact identity CID E for his/her work location/use (the contact identity afforded to the user 10 by his/her employer).
  • the first contact identity CID H and the second contact identity CID E can be different MSISDN values, for example.
  • account 4O 2 is associated with the home contact identity CID H and therefore is paid by user 10.
  • a work account 4Oi is paid by the company/employer.
  • a particular communications service e.g., a music download
  • CID E the contact identity allocated to user 10 by this employer
  • the access by user 10 can be in any of several manners, including access using a wireless terminal (e.g., a mobile station, cell phone, or user equipment unit, for example) or using a wired terminal (such as computer, for example).
  • a wireless terminal e.g., a mobile station, cell phone, or user equipment unit, for example
  • a wired terminal such as computer, for example
  • Act 6-1 of Fig. 6 comprises receiving a user identifier from a communications network in conjunction with a communications call or session.
  • a "user identifier” encompasses or includes one or both of party ID (PID) and contact identity (CID).
  • act 6-1 can involve user 10 using his/her work contact identifier CID E while at work to access a personal service (e.g., music download, for example).
  • the employment account associated with the work contact identifier CID E for the service access happens to be illustrated in Fig. 3 and Fig. 5 as account 4O 1 .
  • the user 10 also has a home account which is represented in Fig. 3 and Fig. 5 by account 4O 2 .
  • the particular identifier utilized for the call (in this case the work contact identity
  • a call "characteristic" is any information related to a call that facilitates a determination regarding which of plural possible accounts should be charged for the call.
  • the characteristic of the call can be (by way of non-limiting examples) at least one of type of service utilized by the call; time of the call; location of a party to the call; particular party identifier (PID) employed at authentication of the call Besides the characteristics of the call (based, e.g. on service parameters), the filters also can use information collected from the account storage database or external database as input for determining an account association.
  • Act 6-2 of the method of Fig. 6 comprises account selection logic 32, and particularly a filter comprising the first account, using the user identifier and a characteristic of the call to make a determination, based on a characteristic of a call, whether the call, having a user identifier which is associated with a first account, should be alternatively or at least partially associated with a second account. That is, in the example scenario of Fig.
  • the first filter associated with the first account of account selection logic 32 determines whether, based on the fact that the service is a music download (which fact is a characteristic of the call), should be associated with home or personal account 4O 2 for user 10, even though the contact identity CID E utilized by user 10 for the call would tend to indicate that employer account 40j would be charged.
  • the call characteristic utilized by account selection logic 32 is the type or nature of service utilized (e.g., a musical download). Discernment of whether the type of service involved in the call should be charged to account 40 1 or account 4O 2 can be made by account selection logic 32 consulting a directory or database of services which are authorized by one or the other accounts, e.g. a directory of services authorized by or permitted for account 40] .
  • the filters can also use information collected from the account storage database or external database as input for determining the association.
  • account selection logic 32 can initially determine that account 40] is associated with the particular (work) contact identity [CID E ] utilized by user 10. But also realizing that the particular service (music download) is not a service that should be charged to account 4O 1 , the account selection logic 32 can instead charge the cost of the music download service to the home account of user 10, e.g., account 4O 2 . Accordingly, Fig. 3 shows by arrow 2-2(2) a charging to home account of user 10, e.g., account 4O 2 .
  • the technology disclosed herein has the perspective that "user” is just a role that a specific party can take or play. It might as well take the role of a customer (i.e. the account holder). What role a party takes may depend on a number of things, like what service is used, identity used at authentication, or time of day. These roles can be reflected by the "characteristic" of the call, as discussed above.
  • Act 7-1 of the generalized procedure of account selection logic 32 comprises checking, upon occurrence of a real-time request, to which party a specific user identity utilized in/associated with the call is connected. For example, when the work contact identity CID E of user 10 is utilized, account selection logic 32 associates the work contact identity CID E with user 10. This assumes that user 10 is disconnected from the user identities that are used for authorization and connection.
  • Act 7-2 comprises optionally checking the role the party normally has when using the user identity associated with the call, e.g., used to place the call (e.g., checking whether user 10 normally fulfills the role of employee when using his/her work contact identity CID E ).
  • Act 7-3 comprises checking a characteristic of the call, e.g., checking the type of service the party is trying to access, location, time of day etc.
  • Act 7-4 comprises determining whether the role the user 10 normally has is valid, or if user 10 should be considered as playing or fulfilling another role in light of the information obtained in the previous act (e.g., depending on the characteristic of the call). For example, act 7-4 involves determining whether, in view of the characteristic of the call placed by user 10, the user 10 4O 1 can correctly be considered to play its default role of employee or worker. [0058] If the normal role of the party is not valid, act 7-5 comprises determining the customer (account holder) corresponding to the role the party has actually played, e.g., a role other than the default role for the utilized identifier.
  • Fig. 8 shows an example, more detailed embodiment of a communications system suitable for real-time flexible account selection technology.
  • Fig. 8 has comparable reference numerals for essentially same components and/or units as described in Fig. 3, but shows more details for, e.g., an example embodiment of account selection logic 32 and of off-line billing system 24.
  • the account selection logic 32 is shown as including a set of filters 50, with one or more accounts 40 of real-time account database 30 having one or more filters 50. In other words, associated or linked to at least some of the accounts 40 are one or more filters 50.
  • the filters 50 also known as "characteristic" filters, provide criteria and/or code which can serve as input to account selection logic 32.
  • filter 5O 1-1 also known as service filter X
  • filter 5O 1-2 also known as service filter Y
  • filter 5O 2-1 also known as service filter R
  • filter 50 n _i also known as service filter S
  • the account selection logic 32 also comprises controller 52. It should be appreciated that account selection logic 32 in one or more embodiments can thus take the form of or at least include a processor or controller as those terms are herein expansively explained.
  • the filters 50 can, at least in one example embodiment, comprise code, scripts, or other information executable or usable by controller 52 for selecting an appropriate account to which a call, connection, or session is to be charged. Such information can, as in the illustrated example embodiment, be stored in real-time account database 30 in association with the particular account 40 to which the filter pertains. While Fig. 8 shows the filters 50 as being stored in real-time account database 30, it should be appreciated that the filters 50 can be stored in other memory and yet be associated or linkable to the respective accounts 40.
  • Fig. 8 also shows example details of a generic, representative, off-line billing system 24 of the type shown in Fig. 3.
  • the example off-line billing system 24 of Fig. 8 comprises record processor 60; off-line account database 62; and, invoice/statement generator 64.
  • the record processor 60 receives and processes the CDR-type reports which are generated by rating function 34 of real-time charging system 22.
  • Off-line account database 62 is configured to maintain an off-line, non-real- time account (and thus an off-line account balance) for subscribers.
  • offline account database 62 comprises off-line account 6O 1 which is maintained essentially in parallel with account 40 1 and off-line account 66 2 which is maintained essentially in parallel with account 4O 2 .
  • off-line account database 62 of off-line billing system 24 comprises accounts for myriad subscribers, of which off- line accounts 66] and 66 2 are but two examples.
  • Fig. 9 together with Fig. 8 represents certain example, representative, basic acts or steps performed in implementing a mode of the method particularly suitable for an embodiment such as that of Fig. 8.
  • communications network 20 interrogates real-time charging system 22 in real-time for a call or connection involving a party. Such interrogation can happen at start of a call/session (first interrogation) and during the session (intermediate interrogation).
  • the call or connection involves user 10, who is using his work contact identity CID E to make a call on user equipment unit (UE-A) 46 A for his private or personal benefit (a call not pertinent to his work or employment).
  • user 10 using user equipment unit (UE-A) 46 A attempts to make a personal call to a call recipient at (UE-B) 46 B , as depicted by line A-B in Fig. 8.
  • Act 9-2 comprises account selection logic 32 locating (in real-time account database 30) the appropriate real-time account by using the user identity received from telecom/end-user equipment.
  • act 9-2 comprises initially associating the call to a first account in accordance with the user identifier which is input by or associated with a party participating in the call.
  • the account selection logic 32 selects account 40i as part of act 9-2.
  • Act 9-3 of the mode of Fig. 9 comprises analyzing the charging event using (e.g., in consultation with) the filters associated with the initially charged account.
  • filter 5O 1-1 also known as service filter X
  • filter 50i -2 also known as service filter Y
  • account 4Oi are used, e.g., in act 9-3, in the analysis of the charging event.
  • the criteria or information of service filter 50 M matches the charging scenario (e.g., the filter 5O 1 . ! ascertains or detects information indicating the characteristic of a personal call)
  • a relation between account 4Oi and another account is established. That is, a relation is established between the initially charged account and a second account.
  • user 10 has as his personal account the account 4O 2 .
  • act 9-4 represents using a first filter (e.g., filter 5O]-O for the first account (account 4O 1 ) to determine, based on the characteristic, whether the call should instead be associated with a second account (such as account 4O 2 , for example).
  • a first filter e.g., filter 5O]-O for the first account (account 4O 1 ) to determine, based on the characteristic, whether the call should instead be associated with a second account (such as account 4O 2 , for example).
  • Act 9-5 through act 9-7 can be performed as optional steps of the mode of
  • Act 9-5 through act 9-7 capitalize upon the fact that the second account (e.g., account 4O 2 in the illustrated scenario) owns its own (usually different) set(s)of service filter(s).
  • account 4O 2 owns or has access to filter 50 2- i (also known as service filter R).
  • Act 9-5 comprises using the filter (e.g., filter 50 2 _i) of the second account (account 4O 2 ) to make a confirmation whether the second account can be associated to/with the call. If the confirmation can be made, at least a portion of the call is charged to the second account, as represented by act 9-6 of Fig. 9.
  • service filter 5O 2- 1 is indeed valid for an interrogation from account 4O 1 , and may possibly be valid from other accounts as well.
  • the charging event matches the criteria or information of service filer (R)
  • the interrogation is executed towards account 4O 2 as depicted by arrow 9-6.
  • the charging of the event to account 4O 2 will result in creation by rating function 34 of one or more records (e.g., CDRs) 44.
  • Record(s) 44 are that are received and processed by record processor 60, and applied or utilized in conjunction with off-line account 66 2 which is the home account for party/user (UE-A) 46 A .
  • an invoice, bill, or statement is prepared for party/user (UE-A) 46 A concerning account 66 2 by invoice/statement generator 64.
  • Fig. 10 illustrates an embodiment of a real-time charging system in which the filters 50 are configurable, e.g., by an account owner.
  • Fig. 10 shows real-time charging system 22(10) in which an account owner can interactively configure (e.g., input, modify, delete) information (e.g., data, criteria, rules, scripts, code) included in or associated with one or more of the filters 50 of real-time account database 30.
  • the particular situation of Fig. 10 depicts an owner device 46 D , which happens to belong to or be utilized by the owner of account 40i (e.g., the employer of user 10 who uses user equipment unit (UE-A) 46 A in the above-described scenario).
  • UE-A user equipment unit
  • the owner device 46 D connects to real-time charging system 22 through communications network 20, and thus can be (for example) any time of communications device, including but not limited to a landline phone, a wireless device, or a computer connected by a suitable protocol such as Internet Protocol, for example.
  • filter configuration logic 70 in a non-limiting example embodiment, comprises filter configuration logic 70.
  • the filter configuration logic 70 can receive inputs from and interact with various interfaces, such as owner/telcom interface 72 and operator interface 74.
  • the owner/telcom interface 72 serves as an interface or port through which filter configuration logic 70 of controller 52(10) receives filter specifications (e.g., input, delete, modify filter content instructions or information) from owner device 46 D through communications network 20.
  • operator interface 74 serves as an interface or port through which filter configuration logic 70 of controller 52(10) receives filter specifications from an operator device 46 E -
  • the filter specification(s) obtained from the operator device 46 E can ultimately be obtained from owner device 46 D , as represented by arrow 76 in Fig. 10.
  • the operator device 46 E can be, in one example embodiment, a web server maintained by the communications operator through which owner device 46 D can access the appropriate account (e.g., account 4O 1 ) and thereby establish, delete, or modify filter data or parameters of the filters associated with the appropriate account.
  • the characteristic which is analyzed by account selection logic 32 can be selectively (re)configurable through actions implemented, e.g., by filter configuration logic 70.
  • Fig. 1 1 illustrates an embodiment of a real-time charging system in which one or more filters comprise or have access to financial manager/accumulator 80.
  • one account i.e., customer accounts 40
  • financial manager/accumulator 80 can be integrated in or included as part of an account, or be realized by controller 52, or any other aspect of account selection logic 32.
  • the financial manager/accumulator 80 can be utilized to make an account or track, e.g., measure usage (e.g., of different services).
  • the owner of an account can (using financial manager/accumulator 80) set spending limits on how much the owner is willing to sponsor or allow another end-user to consume or utilize a certain service. Any excess of use by the other use can result in establishing a relation with another account, e.g., charging the relation account of the other user.
  • the account selection logic 32(11) of Fig. 1 1 allows an account owner to set limits on or apportion the amount of use chargeable to his account (e.g., to account 40]), and after such limit is exceed to set up or enforce a relation that causes a balance of the call or connection to be charged to another account (e.g., account 4O 2 ).
  • the parameters of financial manager/accumulator 80 such as the authorization limits, etc., can be interactively established in like manner as the filter specification as described with reference to Fig. 10.
  • Fig. 12 shows an example embodiment of account selection logic 32(12) which provide an account redirection capability.
  • the account selection logic 32(12) comprises controller 52(12).
  • the controller 52(12) in turn comprises functional units such as example functional units 52a and 52b.
  • functional unit 52a comprises a role determination functional unit
  • functional unit 52b comprises an account determination functional unit.
  • the role determination functional unit 52a receives various service parameters (such as party identity [PID] and a contact identity [CID]) and, as a function of at least the PID and possibly other parameters, determines the role played by the party (e.g., by user 10). If necessary, role determination functional unit 52a can fetch other service parameters as inputs for its operation.
  • service parameters such as party identity [PID] and a contact identity [CID]
  • Account determination functional unit 52b receives various service parameters (e.g., PID, CID, and the "role" determined by role determination functional unit 52a) and determines a candidate account to be charged for the call placed by user 10. If necessary, account determination functional unit 52b can fetch other service parameters as inputs for its operation.
  • service parameters e.g., PID, CID, and the "role” determined by role determination functional unit 52a
  • the controller 52(12) also comprises filter(s) 50(12).
  • the account determination functional unit 52b may have selected a candidate account for charging
  • the filter(s) 50(12) can override the determination of account determination functional unit 52b and instead redirect the charge to another account.
  • the controller 52(12) may be programmed or configured to redirect a charge from one account to another account until some condition is fulfilled or satisfied, e.g., until some termination condition or the like is reached. If necessary, filter(s) 50(12) can fetch other service parameters as inputs for operation.
  • the role that a party plays when using a specific service can be used to determine which account is to be charged for the call or connection, not necessarily an account linked to the identity the party happens to be using.
  • the technology disclosed herein thereby provides many advantages.
  • One advantage is that an operator need only have one entry for each party. This in turn provides other benefits: (1) a party can get one bill/invoice/statement no matter what user identity the party may have used; (2) the operator can give promotions based on such criteria as the services the party is using, the time of day, the location, etc., and not the user identity; and (3) the party can use any user identity and be charged correctly.
  • the technology disclosed herein affords an opportunity to define complex business rules without impact in the communications environment e.g. selection of sponsored calls/services for family or corporations.
  • Sponsoring of a call does not necessarily need to be covered by the users own account e.g. children must always be able to call their family members and one of the parents accounts will carry the cost.
  • the service filters could for instance act upon a dialed prefix and thereby let the end-users interact when selecting an account to carry the cost. Time-of-day, day-of- week and dates could be important input for the service filters.
  • Charging scenario (service)-aware account differentiation e.g., voice calls within a company, can be also carried by one account.
  • a customer owner of an account
  • the owner of an account can (using the accumulators) set spending limits on how much he/she is willing to sponsor or allow another end-user to consume or utilize a certain service.
  • Another advantage of the technology disclosed herein is reduced signaling and CPU load in the communications network due, e.g., to the fact that the communications equipment does not need to be in control of the account relations and the fact that the charging system does not need to be interrogated separately for each involved account. Handling this relation internally in the charging system, compared to handling the relation by the communications equipment and the triggering of several session towards the charging system, reduces signaling and CPU load in the communications equipment.
  • the technology disclosed herein thus may permit the redirecting of costs from one account to another (alternative) account.
  • the technology disclosed herein also permits the sharing of cost between plural customer accounts. For example, in some scenarios a call may be partially charged to a first account and partially charged to a second account.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Meter Arrangements (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L’invention concerne un système de télécommunications (20) et son procédé d’exploitation qui facture un appel à au moins un compte parmi plusieurs comptes clients. Un procédé de base comprend la réception d’un identifiant utilisateur depuis un réseau de communications en lien avec un appel ou une session de communications, à l’aide d’un filtre basé sur le compte afin de déterminer si l’appel, ayant un identifiant utilisateur qui est associé à un premier compte, doit être associé en variante ou partiellement à un second compte plutôt qu’au premier compte. Le filtre peut effectuer la détermination sur la base d’une caractéristique de l’appel. Dans des modes de réalisation différents ou mixtes, la caractéristique de l’appel peut être (à titre d’exemple non restrictif) un type de service utilisé par l’appel et/ou la durée de l'appel et/ou l’emplacement d’un correspondant de l’appel et/ou l’identité utilisateur particulière utilisée pour l’authentification de l’appel.
PCT/SE2009/050849 2008-07-11 2009-07-01 Sélection de compte flexible en temps réel pour des communications WO2010005376A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP09794730.3A EP2301191A4 (fr) 2008-07-11 2009-07-01 Sélection de compte flexible en temps réel pour des communications

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US12/171,641 US20100008484A1 (en) 2008-07-11 2008-07-11 Real-time flexible account selection for communications
US12/171,641 2008-07-11
US12/258,990 US20100104076A1 (en) 2008-10-27 2008-10-27 Real-time flexible account selection for communications
US12/258,990 2008-10-27

Publications (1)

Publication Number Publication Date
WO2010005376A1 true WO2010005376A1 (fr) 2010-01-14

Family

ID=41507293

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2009/050849 WO2010005376A1 (fr) 2008-07-11 2009-07-01 Sélection de compte flexible en temps réel pour des communications

Country Status (2)

Country Link
EP (1) EP2301191A4 (fr)
WO (1) WO2010005376A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011163547A3 (fr) * 2010-06-24 2012-09-07 Vonage Network, Llc Systèmes et procédés de terminaison de demandes de communication
WO2013079089A1 (fr) * 2011-11-28 2013-06-06 Telefonaktiebolaget L M Ericsson (Publ) Système de facturation en ligne
WO2014003627A3 (fr) * 2012-06-29 2014-06-26 Telefonaktiebolaget L M Ericsson (Publ) Facturation de télécommunications avec sélection de comptes commandée extérieurement

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774533A (en) 1996-08-14 1998-06-30 Bellsouth Corporation Method and system for providing a billing directed communication service
US6289010B1 (en) 1997-03-11 2001-09-11 Bell Atlantic Network Services, Inc. Inbound gateway authorization processing for inter-carrier internet telephony
US20020022472A1 (en) * 2000-07-21 2002-02-21 Telemac Corporation Multiple virtual wallets in wireless device
US6700961B1 (en) 2000-08-03 2004-03-02 Lucent Technologies Inc. Prepaid calling with warning announcement
US20040121758A1 (en) * 2002-12-18 2004-06-24 Alcatel Accounting advisor method, a mobile telecommunication device, a base station, and a computer software product for guiding a user of a mobile
US20050086138A1 (en) 2002-01-09 2005-04-21 Stefan Prange Separate invoicing of private and service-related conversations on mobile telephones
US20050135264A1 (en) 2003-12-23 2005-06-23 Jeff Popoff Method for implementing an intelligent content rating middleware platform and gateway system
US20060019630A1 (en) * 2004-07-26 2006-01-26 Sbc Knowledge Ventures, Lp System and method to support multiple wireless accounts for a given subscriber
EP1881688A1 (fr) * 2006-07-19 2008-01-23 Siemens Aktiengesellschaft Procédé de sélection d'un compte pour facturer un service offert par un réseau de communication
US20090076952A1 (en) * 2007-09-13 2009-03-19 Motorola, Inc. Variable charging assignment for multi-service environments

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3104389B2 (ja) * 1992-04-20 2000-10-30 株式会社日立製作所 構内交換機システム
US6122354A (en) * 1998-04-27 2000-09-19 At&T Corporation Method and apparatus for extending a pre-paid calling card limit
US6137872A (en) * 1998-05-18 2000-10-24 At&T Combination pre-paid and calling card
US6282274B1 (en) * 1999-07-09 2001-08-28 Telcordia Technologies, Inc. Selectable billing options for a single communications account
US6850755B2 (en) * 2001-01-08 2005-02-01 Lucent Technologies Inc. Transparent billing and display of multiple directory numbers in wireless telephone systems
US6925160B1 (en) * 2002-08-21 2005-08-02 Mobilesense Technologies, Inc. System and method for managing cellular telephone accounts
US7453999B1 (en) * 2003-07-29 2008-11-18 Evans Mark P Prepaid services with security provisions to protect against unauthorized use
US20070061254A1 (en) * 2005-09-15 2007-03-15 Richard Blunck Systems and methods for opening, funding, and managing financial accounts
EP1801748A1 (fr) * 2005-12-23 2007-06-27 Telefonaktiebolaget LM Ericsson (publ) Procédé pour gérer des comptes
CN101090325A (zh) * 2006-06-23 2007-12-19 华为技术有限公司 第三方计费方法和系统
EP1874020A1 (fr) * 2006-06-28 2008-01-02 Telefonaktiebolaget LM Ericsson (publ) Facturation des communications vocales en mode circuit, SMS, MMS et/où de données GPRS
WO2009067101A1 (fr) * 2007-11-21 2009-05-28 Lucent Technologies Inc. Système et procédé de gestion hiérarchisée de ressources de compte fondée sur des règles

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774533A (en) 1996-08-14 1998-06-30 Bellsouth Corporation Method and system for providing a billing directed communication service
US6289010B1 (en) 1997-03-11 2001-09-11 Bell Atlantic Network Services, Inc. Inbound gateway authorization processing for inter-carrier internet telephony
US20020022472A1 (en) * 2000-07-21 2002-02-21 Telemac Corporation Multiple virtual wallets in wireless device
US6700961B1 (en) 2000-08-03 2004-03-02 Lucent Technologies Inc. Prepaid calling with warning announcement
US20050086138A1 (en) 2002-01-09 2005-04-21 Stefan Prange Separate invoicing of private and service-related conversations on mobile telephones
US20040121758A1 (en) * 2002-12-18 2004-06-24 Alcatel Accounting advisor method, a mobile telecommunication device, a base station, and a computer software product for guiding a user of a mobile
US20050135264A1 (en) 2003-12-23 2005-06-23 Jeff Popoff Method for implementing an intelligent content rating middleware platform and gateway system
US20060019630A1 (en) * 2004-07-26 2006-01-26 Sbc Knowledge Ventures, Lp System and method to support multiple wireless accounts for a given subscriber
EP1881688A1 (fr) * 2006-07-19 2008-01-23 Siemens Aktiengesellschaft Procédé de sélection d'un compte pour facturer un service offert par un réseau de communication
US20090076952A1 (en) * 2007-09-13 2009-03-19 Motorola, Inc. Variable charging assignment for multi-service environments

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2301191A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011163547A3 (fr) * 2010-06-24 2012-09-07 Vonage Network, Llc Systèmes et procédés de terminaison de demandes de communication
WO2013079089A1 (fr) * 2011-11-28 2013-06-06 Telefonaktiebolaget L M Ericsson (Publ) Système de facturation en ligne
CN103947179A (zh) * 2011-11-28 2014-07-23 瑞典爱立信有限公司 在线计费系统
WO2014003627A3 (fr) * 2012-06-29 2014-06-26 Telefonaktiebolaget L M Ericsson (Publ) Facturation de télécommunications avec sélection de comptes commandée extérieurement
US8868031B2 (en) 2012-06-29 2014-10-21 Telefonaktiebolaget L M Ericsson (Publ) Telecommunications charging with externally-controlled account selection

Also Published As

Publication number Publication date
EP2301191A4 (fr) 2014-11-26
EP2301191A1 (fr) 2011-03-30

Similar Documents

Publication Publication Date Title
CN1805442B (zh) 在ims网络中提供在线计费的装置和方法
US8406732B2 (en) Rule based hierarchical account resource management system and method
KR101411329B1 (ko) 수익 배당을 갖는 엔티티 마다 과금 데이터를 생성하는 프론트 엔드 과금 시스템
US8594626B1 (en) Post-paid wireless service balance management
US9118779B2 (en) System and method for inbound call billing
CN101006681B (zh) 用于ip多媒体业务的灵活计费机制
US20090006229A1 (en) System and method for telephony billing codes
US20100104076A1 (en) Real-time flexible account selection for communications
US20060007928A1 (en) Flexible traffic rating interworking
EP2791886B1 (fr) Système de suivi et de facturation de communication
CA2589686A1 (fr) Systeme et procede d'activation de service dans la facturation d'un reseau mobile
EP1935152A2 (fr) Systeme et procede de gestion de revenus
CN101227302A (zh) 计费方法、控制装置、计费装置与计费系统
WO2009055960A1 (fr) Procédé, appareil et système permettant la prise en charge d'une facturation ims distribuée
US20170064091A1 (en) Routing of toll-free numbers using a toll-free exchange
US20030114142A1 (en) Distributing billing for a call between a caller and a callee
US20050013423A1 (en) Telecommunication method and apparatus with provisions to exceed usage limit
US20100008484A1 (en) Real-time flexible account selection for communications
Kuhne et al. Charging and billing in modern communications networks—A comprehensive survey of the state of the art and future requirements
RU2165679C1 (ru) Система предоставления платных услуг в телекоммуникационной сети (варианты)
US20080287099A1 (en) System and method for managing charges and airtime values for cellular phones and accounts
US20040152443A1 (en) Charging in a communication system
EP2301191A1 (fr) Sélection de compte flexible en temps réel pour des communications
JP2008543191A (ja) 回線交換ネットワークを介した複数のユーザ間の呼を処理する方法、及び当該方法とともに用いるための通信端末装置
CN101771984A (zh) 数据业务实时计费方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09794730

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009794730

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 200/DELNP/2011

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 746/KOLNP/2012

Country of ref document: IN