WO2009152847A1 - Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur - Google Patents

Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur Download PDF

Info

Publication number
WO2009152847A1
WO2009152847A1 PCT/EP2008/057581 EP2008057581W WO2009152847A1 WO 2009152847 A1 WO2009152847 A1 WO 2009152847A1 EP 2008057581 W EP2008057581 W EP 2008057581W WO 2009152847 A1 WO2009152847 A1 WO 2009152847A1
Authority
WO
WIPO (PCT)
Prior art keywords
credit control
final
credit
server
unit
Prior art date
Application number
PCT/EP2008/057581
Other languages
English (en)
Inventor
Vesa Hellgren
Original Assignee
Nokia Siemens Networks Oy
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
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2008/057581 priority Critical patent/WO2009152847A1/fr
Publication of WO2009152847A1 publication Critical patent/WO2009152847A1/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/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
    • 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/64—On-line charging system [OCS]
    • 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/66—Policy and charging system
    • 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/83—Notification aspects
    • H04M15/84—Types of notifications
    • H04M15/844—Message, e.g. SMS
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/852—Low balance or limit reached
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H04M17/02—Coin-freed or check-freed systems, e.g. mobile- or card-operated phones, public telephones or booths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/8129—Type of notification
    • H04M2215/8137—Message, e.g. alphanumeric text, SMS, MMS, EMS or www-based messaging service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/815—Notification when a specific condition, service or event is met
    • H04M2215/8158—Low balance or limit reached

Definitions

  • the present invention relates generally to a method of commu ⁇ nication for use in a credit control application, a respec- tive communication system and a computer program product and, more particularly, to a respective method, a communication system and a computer program product realized in data net ⁇ works, where Diameter Credit Control Application (DCCA) and Wireless Application Protocol (WAP) push architecture can be used.
  • DCCA Diameter Credit Control Application
  • WAP Wireless Application Protocol
  • the present invention may include networks, which are based on 3GPP (3rd Generation Partnership Project), GPP2 (3 rd Generation Partnership Project 2) or OMA (Open Mobile AlIi- ance) reference architectures.
  • 3GPP 3rd Generation Partnership Project
  • GPP2 3 rd Generation Partnership Project 2
  • OMA Open Mobile AlIi- ance
  • the current accounting models specified in the Radius Ac ⁇ counting (RFC2866) Diameter base (DIAMBASE) are not sufficient for a real-time credit control, where credit-worthiness is to be determined prior to service initiation.
  • the existing Diameter authorization applications (NASREQ, DIAMMIP) only provide service authorization, but do not pro ⁇ vide credit authorization for prepaid users.
  • a new type of server was needed in the AAA infrastructure (Authentication, Authoriza ⁇ tion and Accounting) i.e. a Diameter credit control server.
  • the Diameter credit control server is the entity responsible for credit authorization for prepaid subscribers.
  • a service element usually authenticates and authorizes an end user with the AAA server by using AAA protocols (e.g. RADIUS or Diameter base protocol with a possible diameter applica ⁇ tion) .
  • Figure 1 illustrates a conventional credit control architec ⁇ ture, which consists of a service element 3 with an embedded Diameter credit control client (CC client) , a Diameter credit control server 1, and a AAA server 2.
  • CC client Diameter credit control client
  • AAA server 2 a business support system 5 may be deployed, which includes at least the billing functionality.
  • the credit control server 1 and the AAA server 2 constitute logical entities in this architecture model. A real configuration can combine them into a single host.
  • the credit control protocol may be the diameter base protocol with the Diameter Credit Control Application (DCCA) .
  • DCCA Diameter Credit Control Application
  • an end user 4A or 4B requests services, such as SIP (Session Initiation Protocol) or messaging
  • the request is typically forwarded to the service element 3 (e.g. SIP proxy) in the end user's home domain.
  • the service element 3 in the visited domain can offer services to the end user 4A or 4B.
  • Network access is an example of a service offered in the visited do- main where a Network Access Server (NAS) authenticates and authorizes the end user with the user's home network through an AAA infrastructure (Authentication, Authorization and Accounting) .
  • NAS Network Access Server
  • service is used and hereinafter will be understood to broadly include any service or goods which are used and/or the user may desire, require or be provided with. The term would be understood to cover the provision or complementary services.
  • service will be understood to include e. g. internet protocol multimedia IM ser- vices, conferencing, telephoning, gaming, E-commerce and messaging (instant messaging) .
  • credit control defines a mechanism that directly interacts in real-time with an account and controls or moni ⁇ tors the charges related to the service usage.
  • credit control is a process of checking whether credit is available, credit reservation, deduction of credit from the end user account when service is completed and refunding of reserved credit that is not used.
  • the Diameter credit control Server 1 acts as a prepaid server, performing real-time and credit control. It is lo ⁇ cated in the home domain and is accessed by service elements or Diameter AAA servers in real-time for purpose of price de ⁇ termination and credit control before the service event is delivered to the end user. It may also interact with the business support system 5.
  • the Diameter credit control client uses interrogation to ini ⁇ tiate a session based credit control process. During the credit control process, it is used to report the used quota and requests a new one. An interrogation maps to a re ⁇ quest/answer transaction.
  • the service element 3 is a network element that provides a service to the end user.
  • the service element may include the Diameter credit control client or another entity that can act as a credit control client on behalf of the service element.
  • Examples of the service element include Network Access Serv ⁇ ers (NAS) , SIP Proxy, and Application Servers such as messag ⁇ ing server, content server and gaming server.
  • NAS Network Access Serv ⁇ ers
  • SIP Proxy SIP Proxy
  • Application Servers such as messag ⁇ ing server, content server and gaming server.
  • the DCCA specification contains elaborate mechanism for initiating redirection of user plane traffic based on Final- Unit-Indication AVP (Attribute-Value-Pair) .
  • This redirection mechanism can be used e.g. when quota runs out and the end user should be redirected to a portal, where subscriber can purchase more quota, i.e. credit units for a specific ser ⁇ vice.
  • DCCA server there is no mechanism, which would allow DCCA server to define that WAP-push message should be sent when quota runs out and DCCA server could define the content of the WAP-push message.
  • Figure 2 illustrates a status diagram showing how "graceful service determination" works in Diameter credit control ap ⁇ plication according to the prior art.
  • Figure 2 illustrates a status diagram as defined in RFC4006, section 5.6.
  • the end user 4 may not be allowed to compile additional chargeable events or services.
  • the home service provider may offer some services; for instance, access to a service portal where it is possible to refill or replenish the account for which the user is allowed to benefit for a limited time. The length of this time is usually dependent on the home service provider policy.
  • the graceful service determination may be used to redirect the subscriber or end user 4 to a service portal for online balance refill or other services offered by the home service provider.
  • the graceful termination process installs a set of packet filters to restrict the user's access capability only to/from specified destinations. All the IP packets not matching the filters will be dropped or, possibly, re-directed to the ser- vice portal.
  • the end user 4 may also be sent an appropriate notification as to why the access has been limited.
  • These ac ⁇ tions may be communicated explicitly from the server 1 to the client, i.e. service element 3, or may be configured per- service at the client. Explicitly signaled redirect or re ⁇ strict instructions always take precedence over configured ones .
  • the service element 3 including a credit control client (CC client) delivers service to the end user 4 in a step Sl.
  • a credit control re ⁇ quest requests for an update of used units to the AAA server 2 and from this server 2 to the credit control server 1.
  • the credit control server 1 submits a credit control an ⁇ swer (CCA) to the AAA server 2 in step S4 and from the server 2 to the service element 3 in step S5.
  • CCA credit control an ⁇ swer
  • This credit control answer CCA may include a Final-Unit-Indication AVP (Attribute-Value-Pair) , which indicates that the granted quota in Granted-Service-Units AVP is the final quota and the action defined in the Final-Unit-Indication shall be executed when the granted quota has been consumed.
  • AVP Attribute-Value-Pair
  • the Final-Unit-Indication has the format as shown in Figure 2, wherein the Final-Unit-Action AVP defines the action to be executed. If the action is REDIRECT as shown in Figure 2, then the credit control client shall start redirecting all traffic (which does not match with Filter-Id AVP or Restric ⁇ tion-Filter-Rule AVP (not shown) ) to redirection server de- fined by the Redirect-Server AVP, i.e. TS server (Top-up server) .
  • TS server Topic-up server
  • the Redirect-Address-Type AVP (not shown), thus, defines the type of the redirect address in Redirect-Server-Adress (not shown) .
  • RFC allows usually 4 different values: IPv4 address, IPv6 address, (WAP/HTTP) URL (Uniform Resource Locator) or SIP URI (Uniform Resource Indicator) .
  • the Redirect-Server-Address AVP has type UTF ⁇ String, which means that it may contain text, which is interpreted based on the Redirect-Address-Type AVP.
  • the graceful service termination procedure described in Fig ⁇ ure 2 allows, thus, the functionality, to connect the prepaid end user 4 to a top-up server (TS server) 6 that plays an an ⁇ nouncement and prompts the end user 4 to replenish the ac ⁇ count.
  • the credit control server 1 sends only the address of the top-up server 6 where the prepaid user shall be connected after the final granted units have been consumed.
  • a credit control client of the service element 3 starts blocking traffic and redirects the traffic to the TS server 6.
  • a credit control re ⁇ quest is again sent to the AAA server 2 and credit control server 1 to update the used units which is responded in steps S9 and SlO by the credit-control server 1 and via the AAA server 2 to the service element 3 by the credit control an- swer CCA including the above-mentioned validity time for the redirection to the top-up server 6.
  • the main disadvantage of this prior art solution is the lim- ited support for redirection actions.
  • the credit- control server 1 can initiate redirection to IPv4/IPv6 ad ⁇ dress, SIP URI or HTTP URL.
  • IPv4/IPv6 address would not be a useful address for redirection to the top-up server 6. For example, if the subscriber 4 is using an e-mail cli- ent, even if e-mail traffic from the subscriber end user de ⁇ vice is redirected to the top-up page, there is no practical way of showing information to subscriber 4 and replenish the account.
  • a method of communication for use in a credit- control application comprising the steps: determining in a credit control server, whether a final credit unit has been used for a requested service, if so, sending a Final-Unit- Indication to a gateway node including a code value, and sending a WAP Push message, which explicitly corresponds to said code value, to a requester of the service with an indi ⁇ cation whether final unit has been used.
  • the code value may include the action WAP_PUSH, which initiates sending of said WAP Push message to the requester, when there is the first packet, which needs to be blocked.
  • the code value may include the action WAP_PUSH_IMMEDIATE, which immediately initiates sending of said WAP Push message to said requester.
  • WAP_PUSH_IMMEDIATE the action immediately initiates sending of said WAP Push message to said requester.
  • the Final-Unit-Indication includes information defining a link for replenishing an account of the credit units and/or a text for showing to the requester.
  • Figure 1 illustrates a simplified block diagram of a communi ⁇ cation system in accordance with the prior art
  • Figure 2 illustrates a status diagram of a graceful service termination in accordance with the prior art
  • Figure 3 illustrates a status diagram of a graceful service termination in accordance with a first embodiment of the pre ⁇ sent invention
  • Figure 4 illustrates a status diagram of a graceful service termination in accordance with a second embodiment of the present invention.
  • the present invention will be described with respect to pre- ferred embodiments in a specific context, namely the graceful service termination using Diameter Credit Control Application (DCCA) and Wireless Application Protocol (WAP) push architec ⁇ ture.
  • DCCA Diameter Credit Control Application
  • WAP Wireless Application Protocol
  • the invention may also be applied, however, to other protocols in data networks supporting credit control applica- tions.
  • FIG 3 illustrates a simplified status diagram of a grace ⁇ ful service termination in accordance with a first embodiment of the present invention, wherein same reference signs refer to same or equivalent elements as in Figure 2. Thus, it is referred to Figure 2 and its detailed description in order to avoid unnecessary reiterations.
  • Figure 3 includes a credit control server 1, an (optional) AAA server 2 (Authentication, Authorization, Accounting) , a service element 3 which preferably includes a credit control client (CC Client) and an end user 4 requesting a specific service.
  • the service element 3 constitutes a gateway node of the home domain and particularly may implement the above- mentioned credit control client supporting the above- mentioned Diameter credit control application.
  • the gateway node or service element 3 supports Wireless Application Protocol (WAP) and may send WAP Push messages to the end user 4 being the requester of a specific service.
  • WAP Wireless Application Protocol
  • the credit con ⁇ trol server 1 may determine whether a final credit unit or quota has been used for a requested service, which means that money runs out for a specific service.
  • the respective service delivery is indicated by step Sl in Figure 3 while in steps S2 and S3 a credit control request CCR is indicated which could be submitted to the AAA server 2 and from this server to the credit control server 1.
  • the AAA server 2 could also be omitted in some specific cases.
  • Credit control request CCR updating the credit-control server 1 and indicat ⁇ ing the used units could thus be sent also directly from the credit-control client within the gateway node or service ele- ment 3 to the credit control server 1.
  • the credit control server 1 sends a Final-Unit- Indication to the gateway node 3 and its respective credit control client via steps S40 and S50.
  • the AAA server 2 could be omitted and the respective Final-Unit-Indication could be sent directly from the credit control server 1 to the credit control client in the gateway node 3.
  • this Final-Unit- Indication now includes a specific code value indicating the Final-Unit-Action WAP_PUSH_IMMEDIATE as well as it may contain information defining a link for replenishing an account of units, i.e. Redirect-Server : WAP Push message content.
  • the Final-Unit-Indication according to Figure 3 may include information defining a text for showing to the requester, i.e. end user 4.
  • the credit control server 1 may send an explicit message in e.g. the Final-Unit- Indication to the gateway node 3, which detects this message and sends a respective WAP Push message, which explicitly corresponds to the code value of the Final-Unit-Indication, to the end user 4 requesting the service in a step S55. More ⁇ over, an indication may be sent by this WAP Push message that a final unit has been used.
  • a free editable mes ⁇ sage could be submitted within the field " ⁇ text>" of the Fi ⁇ nal-Unit-Indication which is also unconditionally submitted to the end user 4 by the WAP Push message in step S55.
  • a step S60 the credit control client may start blocking traffic if credit units have been completely used, submitting therewith a credit control request CCR in steps S7 and S8 via the AAA server 2 to the credit control server 1.
  • the credit control server 1 may answer this request by a credit control answer CCA indicating a specific validity time back to the gateway node 3 in steps S9 and SlO.
  • the end user 4 has now the possibility to refill or replenish the account by directly contacting the top-up server 6 (TS server) .
  • the respective address, i.e. URL, URI etc. may be already included in the Final-Unit-Indication AVP indicating also the Final-Unit-Action AVP: WAP_PUSH_IMMEDIATE .
  • the present invention provides a more comfortable way for a graceful service termination which is independent from a real situation in the gateway node 3.
  • Figure 4 illustrates a simplified status diagram of a grace ⁇ ful service termination according to a second embodiment of the present invention, wherein same reference signs define same or similar elements as in Figures 2 and 3. Therefore, it is referred to the detailed description of Figures 2 and 3 in order to avoid unnecessary reiterations.
  • the em ⁇ bodiment according to Figure 4 now submits the Final-Unit- Action AVP: WAP_PUSH sent in steps S41 and S51 from the credit control server 1 via the AAA server 2 to the service element 3, i.e. gateway node.
  • the code value of the Final-Unit-Indication AVP (Attribute Value Pair) now includes the action WAP_PUSH which results in a WAP Push message sent to the end user 4, when there is the first packet, which needs to be blocked by the gateway node 3.
  • the credit control client within the gateway node 3 starts blocking traffic in step S60, sends out the credit control request CCR in step S7 via the AAA server 2 in step S8 to the credit control server 1 indicating that quota run out and sending at the same time the WAP Push message in step S71 to the end user 4.
  • an indication that a final unit has been used may be submitted by this WAP Push message to the end user 4 wherein a free ed ⁇ itable text could be further shown to the end user 4.
  • the credit control server 1 acknowledges the credit control re- quest CCR by a credit control answer CCA including a specific validity-time in steps S9 and SlO which enables the end user 4 to fill up the account in step SIl at the top-up server 6 (TS server) .
  • One action is used to initiate sending a WAP Push message to the subscriber user device immediately, when the credit control client receives the Final-Unit-Indication AVP (Attribute Value Pair) .
  • the other action is used to initiate sending of a WAP Push message to the subscriber end user device, when quota runs out.
  • the credit control server 1 may also define a text information, which could be shown to the subscriber end user device 4.
  • the code value 3 may be used according to the second embodiment to define the action WAP_PUSH, which is used to initiate sending of a WAP Push message to the end user 4 when the related quota has been completely consumed and there is the first packet, which needs to be blocked due to insufficient quota.
  • the code value 4 is used according to the first embodiment of the present invention to define the action WAP_PUSH_IMMEDIATE, which means that the credit control client will immediately initiate sending of a WAP Push message to the end user. Having two different explicit code values offers more flexibility for a credit control applica ⁇ tion .
  • the action WAP_PUSH_IMMEDIATE is suitable in those cases where the credit control server 1 wants to send the notification imme ⁇ diately to the end user 4, even before the quota runs out completely.
  • the action WAP_PUSH is suitable in those cases, where notification send ⁇ ing should be delayed as long as possible.
  • the Redirect-Server AVP defines the address of the respective top-up server 6, according to the present invention the Redirect-Server AVP defines the content of the WAP push message to be submitted to the end user 4.
  • the content of the Redirect-Server AVP including an optional text information ⁇ text> defines explicitly the con ⁇ tent of the WAP push message sent from the gateway node 3 to the end user 4.
  • two new code values are also defined for the Redirect-Server-Type AVP, because there are two types of WAP Push messages.
  • the code value 4 is used for the WAP Push Service Indication and the code value 5 is used for the WAP Push Service Loading.
  • Service Indication may be used to show text and possible address information such as URL to the end user 4. Service Loading will automatically start loading URI included in the WAP Push message and thus subscriber will be redirected to the top-up server 6 even if the end user 4 is currently not using WAP or HTTP applica ⁇ tions .
  • the Redirect-Server-Address AVP may contain the text to be sent in the WAP Push message.
  • This text may con ⁇ tain normal text and/or IP-information such as URLs (Uniform Resource Locators) .
  • URLs Uniform Resource Locators
  • the Final-Unit-Indication AVP may also contain Restriction-Filter-Rule AVP to inform the credit control client that traffic to the top-up server 6 may pass.
  • the WAP Push message may contain link infor ⁇ mation to the top-up server 6 and this link information will work even if all the other traffic is blocked based on the Final-Unit-Indication AVP.
  • the WAP Push architecture used in the present invention is specified by Open Mobile Alliance specifications (OMA) for- mally known as WAP Forum.
  • OMA Open Mobile Alliance specifications
  • WAP Push architec ⁇ ture includes three nodes.
  • the WAP client receives the WAP Push message and it corresponds to the end user.
  • the Push Proxy Gateway (PPG) may send the WAP Push message using push Over-The-Air (OTA) protocol.
  • the Push Proxy Gateway (PPG) is typically implemented as part of the WAP Gateway node.
  • the third node is the Push Initiator (PI), which sends the Push Access Protocol (PAP) request to the Push Proxy Gateway (PPG), when it needs to send the WAP Push message.
  • PI Push Initiator
  • PAP Push Access Protocol
  • PPG Push Proxy Gateway
  • the credit control client takes the role of the Push Initiator (PI) .
  • PI Push Initiator
  • the exception may be the case, where the credit control client implements Push Proxy Gateway (PPG) function and then the credit control client can initiate sending of the WAP push message using push OTA protocol immediately .
  • PPG Push Proxy Gateway
  • the present invention has been described for graceful service termination in Diameter Credit Control Applications (DCCA) .
  • the invention can be used in online charging interfaces, such as Gy interface between GGSN (Gateway GPRS (General Packet Radio Service) Support Node) and OCS (Online Charging System or Ro interface between CDF (Charging Delivery Function) and a charging system (OCS) .
  • This may offer the online charging system a way to inform end users when the end user is running out of money.
  • Online charging system may in this case send a Final-Unit-Indication AVP with action WAP_PUSH to send a WAP push message, which informs the end user that when he or she will first time try to access a cer ⁇ tain service it will be locked until the end user or sub- scriber has acknowledged that service price is acceptable.
  • AVP Advice of Charging functionality
  • FIGS. 3 and 4 illustrate a status diagram of a method and a computer program product according to the present invention. It will be understood that each step of the status diagram and combinations of blocks in the status diagram can be im ⁇ plemented by computer program instructions. These computer program instructions may be loaded onto a computer or another programmable apparatus to produce a machine, such that the instructions which are executed on the computer or other pro- grammable apparatus create means for implementing the func ⁇ tion specified in the steps of the status diagram. These com ⁇ puter program instructions may also be stored in a computer readable memory, e.g. DVD, CD, diskette, that can direct a computer or other programmable apparatus to function in a particular manner. Moreover, these computer program instructions may be downloaded in e.g.
  • steps of the status diagram support combinations of means for performing the specified func ⁇ tions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each step of the status diagram and combinations of steps in the status diagram can be implemented by special purpose hardware based computer systems which perform a specified function or steps or combinations of special purpose hardware and com ⁇ puter instructions.

Abstract

La présente invention porte sur un procédé de communication à usage dans une application de gestion de crédit, sur un système de communication et sur un programme d'ordinateur respectifs dans lesquels un serveur de gestion de crédit (1) détermine si une unité de crédit finale a été utilisée pour un service demandé et, si oui, envoie une indication d'unité finale (S40, S50) à un nœud passerelle (3) comprenant une valeur de code spécifique. Un message de poussée WAP (S55) qui correspond explicitement à la valeur de code est envoyé à un demandeur (4) du service avec une indication selon laquelle l'unité finale a été utilisée.
PCT/EP2008/057581 2008-06-17 2008-06-17 Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur WO2009152847A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/057581 WO2009152847A1 (fr) 2008-06-17 2008-06-17 Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/057581 WO2009152847A1 (fr) 2008-06-17 2008-06-17 Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur

Publications (1)

Publication Number Publication Date
WO2009152847A1 true WO2009152847A1 (fr) 2009-12-23

Family

ID=40436413

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/057581 WO2009152847A1 (fr) 2008-06-17 2008-06-17 Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur

Country Status (1)

Country Link
WO (1) WO2009152847A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017000644A1 (fr) * 2015-06-30 2017-01-05 华为技术有限公司 Procédé et dispositif permettant un partage de ressources de compte

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1407401A1 (fr) * 2001-06-01 2004-04-14 Watercove Networks Possibilite pour un abonne d'un reseau de communication d'accroitre la valeur d'un compte prepaye
US20050009505A1 (en) * 2003-07-09 2005-01-13 Nokia Corporation Communication network and method for suspending services
US20050135428A1 (en) * 2003-12-19 2005-06-23 Nokia Corporation Communication network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1407401A1 (fr) * 2001-06-01 2004-04-14 Watercove Networks Possibilite pour un abonne d'un reseau de communication d'accroitre la valeur d'un compte prepaye
US20050009505A1 (en) * 2003-07-09 2005-01-13 Nokia Corporation Communication network and method for suspending services
US20050135428A1 (en) * 2003-12-19 2005-06-23 Nokia Corporation Communication network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Charging management; Diameter charging applications (3GPP TS 32.299 version 7.7.0 Release 7); ETSI TS 132 299", ETSI STANDARDS, LIS, SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 3-SA5, no. V7.7.0, 1 October 2007 (2007-10-01), XP014040201, ISSN: 0000-0001 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017000644A1 (fr) * 2015-06-30 2017-01-05 华为技术有限公司 Procédé et dispositif permettant un partage de ressources de compte

Similar Documents

Publication Publication Date Title
Hakala et al. Diameter credit-control application
US7684551B2 (en) Method, means and a computer program product for managing online charging in a communications network
US9014663B2 (en) Sponsored data plan management
US9491606B2 (en) Device and method for controlling charging in a mobile communication system
JP4842317B2 (ja) オンライン課金管理サーバー
JP4965752B1 (ja) 通信セッションの制御
US20060286963A1 (en) Controlling provision of services in a communications network
US20040193513A1 (en) Method and apparatus providing prepaid billing for network services using explicit service authorization in an access server
US20020116338A1 (en) Prepaid access to internet protocol (IP) networks
WO2012138277A2 (fr) Procédé et appareil pour gérer le trafic des services dans un réseau de communication
MX2007014576A (es) Portal de servicios de informacion y gestion para suscriptores de sistemas de comunicacion.
EP2545679B1 (fr) Détermination d'unité centralisée dynamique dans un système de facturation à contrôle de crédit
CN105611517B (zh) 用于在移动通信系统的用户设备中提供服务的方法和装置
US9602554B2 (en) System, method, network entity and device for connecting a device to a communications network
WO2003047164A2 (fr) Maitrise des services dans des reseaux mobiles de donnees par paquets
JP2007521709A (ja) レイティング通知方法及びシステム
WO2009152847A1 (fr) Procédé de communication à usage dans une application de gestion de crédit, système de communication et programme d'ordinateur
Bertz et al. Diameter Credit-Control Application
Hakala et al. RFC 4006: Diameter Credit-Control Application
Bertz et al. RFC 8506: Diameter Credit-Control Application
WO2014153720A1 (fr) Procédé de facturation, dispositif d'accès et dispositif de facturation
EP1942632A2 (fr) Procédé et système pour la prévision automatique de services et d'abonnés
Stura et al. Network Working Group H. Hakala Request for Comments: 4006 L. Mattila Category: Standards Track Ericsson JP. Koskinen
KR20050094939A (ko) 무선 인터넷 서비스 이용에 대한 요금 안내 부가 서비스제공 방법 및 시스템
IE83598B1 (en) Control of services in mobile packet data networks

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: 08761084

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08761084

Country of ref document: EP

Kind code of ref document: A1