WO2015133948A1 - Methods and credit control servers for enabling efficient communication over a communication system - Google Patents

Methods and credit control servers for enabling efficient communication over a communication system Download PDF

Info

Publication number
WO2015133948A1
WO2015133948A1 PCT/SE2014/050268 SE2014050268W WO2015133948A1 WO 2015133948 A1 WO2015133948 A1 WO 2015133948A1 SE 2014050268 W SE2014050268 W SE 2014050268W WO 2015133948 A1 WO2015133948 A1 WO 2015133948A1
Authority
WO
WIPO (PCT)
Prior art keywords
authorization request
request message
sending
session
server
Prior art date
Application number
PCT/SE2014/050268
Other languages
French (fr)
Inventor
Magnus MALMGREN
Stephan Galler
Sabina ZAHIROVIC
Göran Karlsson
Stefan Nilsson
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
Application filed by Telefonaktiebolaget L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Priority to PCT/SE2014/050268 priority Critical patent/WO2015133948A1/en
Publication of WO2015133948A1 publication Critical patent/WO2015133948A1/en

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
    • 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/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
    • H04M15/59—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on real time
    • 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/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • 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
    • H04M17/02—Coin-freed or check-freed systems, e.g. mobile- or card-operated phones, public telephones or booths

Definitions

  • the present disclosure relates generally to methods performed by a
  • Real time charging in a communication network of e.g. a subscriber of a mobile communication network is controlled by an Online Charging System, OCS.
  • OCS Online Charging System
  • an application has to be able to rate service information in real-time. This is today implemented in an application based on the Diameter protocol, defined by the Internet Engineering Task Force, IETF, in RFC 4006 published August 2005.
  • the OCS is, using IETF terminology, referred to as a credit control server, CC server.
  • the CC server controls real-time charging for applications connected to the network.
  • the applications are called credit control clients, CC clients.
  • the CC server can, based on information about its ongoing sessions and its service logic, request credit re- authorization.
  • a CC client that receives a re-authorization request from the CC server has to answer by sending a re-authorization answer followed by a CC request to the CC server, in order to initiate the credit re-authorization.
  • This is today implemented by letting the CC server send a re-authorization request when a change on an account, e.g. an account of a subscriber connected to the CC client, has been made that could affect rating for sessions ongoing for the subscriber. An example is when an account has been replenished.
  • a method is provided performed by a credit control, CC, server in a communication system for enabling efficient
  • the method comprises sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first reauthorization request message.
  • the method further comprises sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
  • a CC server operable in a communication system for enabling efficient communication over the
  • the CC server comprises a processor and a memory. Said memory contains instructions executable by said processor, whereby said CC server is operative for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message.
  • Said memory P42245 further contains instructions executable by said processor, whereby said CC server is operative for sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second reauthorization request message is triggered before the CC answer message has been sent.
  • a CC server operable in a communication system for enabling efficient communication over the
  • the CC server is adapted for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message.
  • the CC server is further adapted for sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
  • Fig. 1 is a schematic block diagram of an example of a communication system in which the present invention may be used.
  • FIGS. 2 and 3 are flow charts illustrating procedures in a CC server according to different possible embodiments.
  • Figs. 4-6 are signaling diagrams illustrating examples of a procedure performed by a CC server according to possible embodiments.
  • FIGs. 7-9 are schematic block diagrams illustrating a CC server in more detail according to different possible embodiments.
  • a solution is provided performed by a credit control, CC, server, in a communication system for enabling efficient communication over the communication system between the CC server and a CC client.
  • This may be achieved by the CC server blocking any triggered second re-authorization request message triggered between the time point when a first re-authorization request message is sent and the time point when a CC answer is sent in response to a CC request triggered by the first re-authorization request message.
  • any triggered unnecessary re-authorization request messages are prevented from being sent during this time period, which results in less load on the communication interface between the CC server and the CC client.
  • Fig. 1 shows an exemplary communication system in which the present invention may be used.
  • the communication system comprises a communication network 100 to which an online charging system, OCS, 120 is connected.
  • the OCS 120 may be, or comprise, a CC server for controlling credit information for CC clients 1 1 1 1 , 1 12, 1 13 also connected to the communication network 100.
  • the CC clients 1 1 1 1 , 1 12, 1 13 are in fig. 1 exemplified as a Mobile Switching Center, MSC, 1 1 1 for a GSM-based mobile network, a Gateway GPRS Serving Node, GGSN for a GPRS-based mobile network and an application server 1 13.
  • P42245 communication system may also comprise a Home Location Register, HLR, connected to the communication network.
  • HLR Home Location Register
  • FIG. 2 shows a method according to an embodiment, performed by a CC server 120 in a communication system for enabling efficient communication over the communication system between the CC server 120 and a CC client 1 1 1 , 1 12, 1 13.
  • the method comprises sending 202 a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving 204 a CC request message from the CC client, in response to the sent first re-authorization request message.
  • a CC client may be a node in the communication server that delivers a service to subscribers in the communication network.
  • the CC client may for example be an application server delivering applications to the subscriber, such as a server of a supplier of domestic electrical power for calculating used electrical power (in e.g. kWh) and price for subscribers, or an MSC/GGSN delivering telecommunication services.
  • the messages may be messages according to the Diameter Credit Control Application protocol, IETF RFC 4006 and Diameter Base Protocol RFC 6733 published October 2012.
  • the Diameter protocol is an authentication, authorization and accounting protocol for communication networks.
  • the re-authorization request message may be a Diameter RAR message.
  • the preventing sending a second re-authorization request message following the first re-authorization message may signify blocking sending of a second re-authorization second, even though a sending of the second reauthorization has been triggered.
  • the term "a session" is a session between the CC server and a subscriber connected to the CC client which session is credit control monitored. A subscriber may have one or many sessions simultaneously.
  • One session may be e.g. a web browser using a certain service for browsing the Internet, another service may be a voice call.
  • a subscriber may be a subscriber of a telecommunication operator.
  • Other examples of subscribers are an electrical power/water/gas meter or a "household" that has a session with possible services electrical power/water/gas/heating.
  • Another example of a subscriber may be a vending machine.
  • a re-authorization message may be triggered by e.g. a changed price for a service.
  • the changed price may be due to a price offer accepted by a user, a changed user subscription, a triggered user bonus resulting in a cheaper price, a threshold value that has been exceeded resulting in a changed price for the service etc.
  • the second re-authorization request message may also be triggered e.g. by the received CC request message. Such a second re-authorization request message is unnecessary since the price change has already been taken care of by the first re-authorization request message. Sending of such a second re- authorization request message causes unnecessary signaling in the network.
  • Fig. 3 shows other embodiments of a method performed by a CC server 120 in a communication system for enabling efficient communication over the communication system between the CC server 120 and a CC client.
  • the preventing of sending 208 of a second re-authorization request message may comprise setting 304 a state of the session to a re-authorization request non-sending state, in response to the sending 202 of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re- authorization request message is sent for the session, and setting 314 the state of
  • the preventing of sending 208 may further comprise checking the state of the session before sending the second re-authorization request message, and only sending the second re-authorization request message when the state of the session is in the re-authorization request sending state. This is illustrated in fig.
  • the method may further comprise, when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period 306, allowing sending a second re-authorization request message triggered after the defined time period has expired.
  • this is realized by checking the time from the first re-authorization request message has been sent and if a defined time period has expired 306 and no CC request message has been received, there is probably something wrong and it will be allowed to send a re-authorization request again.
  • the allowing of sending a second re-authorization request message triggered after the defined time period comprises setting 314 the state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
  • the method may further comprise performing 309 a rating procedure triggered by the received CC request, and in response to the performed rating procedure, allowing sending the second reauthorization request message.
  • the allowing of sending a second re-authorization request message triggered in response to a performed rating procedure may comprise setting 314 a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
  • a rating procedure performed in response to a CC request may, according to an embodiment, trigger that it is allowed to send a second re-authorization request even though the CC answer has not yet been sent.
  • a race condition can occur after rating and a re-authorization request evaluation for a received CC request have been concluded but before a CC answer is sent.
  • a new account update might happen. When sending of a new re-authorization request triggered by such an account update is prevented, new information that should be sent will not be sent.
  • the state of the session is set 304 to a reauthorization request non-sending state by setting a block re-authorization request flag in a session memory and the state of the session is set 314 to a reauthorization request sending state by clearing the block re-authorization request flag in the session memory.
  • a second RAR triggered by an external trigger received 307 after the first RAR has been sent 202 is blocked 308.
  • the external trigger is received between the reception 204 of the CC request and the sending 206 of the CC answer, but such an external trigger may be received anytime during the procedure. As long as the external trigger is received after the sending of the first RAR and before the sending of the CC answer it will be blocked.
  • Fig. 4 is a signaling diagram showing signals sent between a CC client and a CC server in a re-authorization procedure according to a possible scenario in which Diameter messages are used.
  • a first trigger message is sent from the CC client or from an external node to the CC server.
  • the first trigger message may be an internal trigger 1 .1 a sent from the CC client, e.g. as a CC request, or an external trigger 1 .1 b sent from an external node, such as e.g. a self-care portal for the end user.
  • the first trigger message may trigger a rating procedure to be performed.
  • the rating procedure produces a rating result, for example if a rate is to be changed for a session.
  • the rating result is used in a RAR evaluation procedure.
  • the RAR evaluation procedure evaluates whether or not a RAR is to be sent to the active sessions of a subscriber.
  • the RAR evaluation procedure may for example be performed according to the following: It starts by checking whether a new resource got active based on the rating result. If no new resource got active no RAR is to be sent. If a resource got active, the RAR evaluation procedure proceeds by checking whether the new resource has impact on rating for other services. This may be performed according to different configured rules. If the new resource has no impact, no RAR is to be sent. If the new resource has impact on other services, the RAR evaluation procedure proceeds by acquiring data of active sessions in a session memory for a subscriber and matching the services of the active sessions with the impacted services. If there is no match, no RAR is to be sent, if there is a match, it is checked whether the RAR blocking flag is set, if it is not set a RAR is to be sent.
  • the trigger message 1 .1 a or 1 .1 b may trigger a first reauthorization request, RAR, message 1.2.
  • a RAR blocking flag is set 1 .3 by the CC server. This RAR blocking flag prevents, or blocks, any triggered new (also called second) RAR following the first RAR from being sent from the CC server to the CC client for the same session.
  • the first RAR sent to the CC client triggers the CC client to send a re-authorization answer 1 .4 to the CC server followed by a CC request 1 .5.
  • Such a CC request 1 .5 may trigger a second RAR that does not need to be sent since the changes on the subscriber's account is taken care of already by the CCR resulting from the first RAR.
  • the CC request 1 .5 triggers the CC server to send a CC answer 1 .6 to the CC client.
  • the sending of the CC answer may trigger clearing 1 .7 of the RAR blocking flag.
  • second RARs 1.8 may be sent again.
  • Fig. 5 shows signals sent between a CC client and a CC server in a reauthorization procedure according to another scenario in which there are two CC clients involved: CC client A and CC client B.
  • the procedure starts by the CC server receiving a trigger for starting a re-authorization procedure for CC client A, in this case an external trigger 2.1.
  • the external trigger 2.1 may trigger a rating procedure and/or a RAR evaluation procedure to be performed to evaluate whether a RAR is to be sent to the CC client A.
  • An external trigger may be e.g. an account change or any other type of change that may influence a rating result.
  • the RAR evaluation procedure results in a first RAR 2.2 being sent to CC client A.
  • the sending of the first RAR triggers a RAR blocking flag to be set 2.3 for CC client A.
  • the CC client A responds by sending a re-authorization answer 2.4 to the CC server, followed by a CC request 2.10.
  • an external trigger 2.5 for both A and B is received.
  • the external trigger triggers a RAR evaluation procedure to be performed which results in a first RAR being sent 2.6 to P42245 CC client B.
  • no RAR is sent to CC client A since the RAR block flag for A is set. In other words, the (second) RAR triggered for CC client A is blocked 2.7.
  • the first RAR sent 2.6 to CC client B triggers the RAR blocking flag for CC client B to be set. Thereafter, a re-authorization answer 2.9 is sent from CC client B to the CC server. Further, the CC request 2.10 sent from the CC client A to the CC server triggers the CC server to send a CC answer 2.1 1 to the CC client A. The sending of the CC answer 2.1 1 triggers the release 2.12 of the RAR blocking flag for A. Thereafter, it is again possible to send RARs to the CC client A, catering for new necessary charging updates to make online-charging possible for client A.
  • a CC request 2.13 is sent from CC client B to the CC server which triggers the CC server to send a CC answer 2.14 to CC client B.
  • the sending of the CC answer triggers release 2.15 of the RAR blocking flag for CC client B, catering for new necessary charging updates to make online-charging possible for CC client B.
  • Fig. 6 shows another possible signaling scenario according to another embodiment. This embodiment differs from the embodiment described in fig. 4 in that the rating procedure 3.6 triggered by the received CC request 3.5 triggers the RAR blocking flag to be cleared, whereas in the embodiment of fig. 4 the RAR blocking flag is cleared when the CC answer is sent.
  • the RAR blocking flag is cleared a little bit earlier, catering for the case where the CC request 3.5 actually triggers a change which need to be reflected at the CC client, in other words, a change is triggered for which a RAR needs to be issued.
  • FIG. 7 schematically shows a CC server 120 according to an
  • the CC server may comprise a session memory 716 for storing information about the active sessions controlled by the CC server.
  • the session memory 716 may hold information about connected services per subscriber.
  • One session may provide one or more services.
  • a service may be a service as specified in RFC 4006, for example a Gy session for a subscriber.
  • the session memory may further store information needed to send a RAR for a specific session and keep track of state information, i.e. the RAR blocking flag.
  • the CC may comprise a session memory 716 for storing information about the active sessions controlled by the CC server.
  • the session memory 716 may hold information about connected services per subscriber.
  • One session may provide one or more services.
  • a service may be a service as specified in RFC 4006, for example a Gy session for a subscriber.
  • the session memory may further store information needed to send a RAR for a specific session and keep track of state information, i.e. the RAR blocking flag.
  • P42245 server may further comprise a service configuration unit 702 that has information controlling the behavior of the CC server at rating for different context.
  • the information may be a set of parameters that specifies certain services, where each service has an internal service ID.
  • the CC server may further comprise a rating unit 704 that performs the rating procedure and/or calculates price for a service and/or performs other possible account changes.
  • the CC server may further have a communication interface 712 for receiving and handling incoming none charging requests, e.g. any other type of request that may for example change pricing, that can affect a subscriber's account and for receiving charging requests.
  • the CC server may further comprise a resource configuration unit having a list of resources that are connected to a subscriber ' s account. Each resource may have an internal resource ID.
  • a resource may comprise different attributes.
  • a resource may be an entity connected to a subscriber in the OCS.
  • the resource can be both individual and shareable between different subscribers. It can be for example a counter, a threshold, an account with monetary units or any other consumption unit, e.g. time, bytes etc.
  • a possible rule execution flow/analysis may be as follows: Resource ID is matched with service ID. If at least one service is configured to be affected by the resource change, i.e. if the resource ID matches the service ID, the analysis continues, otherwise no RAR is to be triggered. If the resource has been added or removed, a RAR will be triggered. In case of an update, the analysis continues. Then it is verified whether rules for specific attributes of the updated resource are configured. If not, a RAR is triggered. Then the updated attributes that are configured not to be eligible for triggering a RAR are filtered out.
  • At least one updated attribute passes the filter the analysis continues, otherwise no RAR is to be triggered. Thereafter it is checked whether there are specific rules for the nature for the update for an updated attribute. If no additional rules for at least one of the updated, and not in the previous step filtered, attributes exist, a RAR is to be triggered. Then it is P42245 checked that the nature of attribute change is applicable for triggering a RAR. If this is the case a RAR is triggered, if it is not the case a RAR is not triggered.
  • the CC server also comprises a RAR evaluation unit 708 for deciding if there has been an account change that affects the rating for any of the active services on an account.
  • An account may be the same as a subscriber.
  • the RAR evaluation unit 708 may further be arranged for receiving a request when an account change has occurred.
  • the RAR evaluation unit 708 may comprise a set of configurable rules that determine if the account change should generate a RAR and a configuration that holds the relationship between services and resources and that maps which resources that affect which services.
  • the RAR evaluation unit may further have an interface towards the session memory, an interface towards the service configuration unit 702 and an outgoing interface through which RARs are sent.
  • Fig. 8 shows a CC server 120 according to an embodiment.
  • the CC server 120 is operable in a communication system for enabling efficient
  • the CC server 120 comprises a processor 803 and a memory 804, said memory containing instructions executable by said processor, whereby said CC server 120 is operative for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message.
  • the memory further contains instructions executable by said processor, whereby said CC server 120 is operative for sending a CC answer message to the CC client for the session, in response to the received CC request message, and for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second reauthorization request message is triggered before the CC answer message has been sent.
  • the CC server 120 may further comprise a communication unit 802, which may be considered to comprise conventional means for communicating from and/or to the other nodes in the communication system, such as the CC clients 1 1 1 , 1 12, 1 13.
  • the conventional communication means may include at least one transmitter and at least one receiver.
  • the CC server may further comprise one or more storage units 806 and further functionality 807 useful for the CC server 120 to serve its purpose as CC server.
  • the instructions executable by said processor may be arranged as a computer program 805 stored in said memory 804.
  • the processor may comprise a processing circuitry incorporating functions of a computer central processing unit, CPU, on one or plural integrated circuits.
  • the processor 803 and the memory 804 may be arranged in an arrangement 801 .
  • the arrangement 801 may alternatively be a micro processor and adequate software and storage therefore, a
  • PLD Programmable Logic Device
  • the computer program 805 may comprise computer readable code means, which when run in CC server 120 causes the CC server to perform the steps described in the method described in relation to figs. 2 and/or 3.
  • the computer program may be carried by a carrier.
  • the carrier may be connectable to the processor.
  • the carrier may be an electronic signal, optical signal, radio signal or computer readable storage medium.
  • the storage medium may be an electronic memory such as a RAM, ROM, EEPROM, magnetic tape, blueray disc, CD, DVD or flash memory, from which the program could be downloaded into the memory 804.
  • the storage medium may be a server or any other entity connected to the communication network to which the CC server has access via its communication unit 802. The computer program may then be downloaded from the server into the memory 804.
  • P42245 at least one of the instructions may in alternative embodiments be implemented at least partly as hardware circuits.
  • the CC server 120 may be operative for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request non-sending state, in response to the sending of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re-authorization request message is sent for the session, setting the state of the session to a re-authorization request sending state, in response to the sending of a CC answer message to the CC client for the session, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session, and checking the state of the session before sending the second re-authorization request message, and only sending the second re-authorization request message when the state of the session is in the
  • the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is further operative for, when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period, allowing sending a second re-authorization request message triggered after the defined time period has expired.
  • the CC server may be operative for allowing sending a second re-authorization request message triggered after the defined time period by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
  • the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is further operative for performing a rating procedure triggered by the received CC request, and, in response to the performed rating procedure, allowing sending the second re-authorization request message.
  • the CC server may be operative for allowing sending the second re-authorization request message triggered in response to the performed rating procedure by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
  • the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is operative for setting the state of the session to a re-authorization request non-sending state by setting a block re-authorization request flag in a session memory and whereby the CC server is operative for setting the state of the session to a re-authorization request sending state by clearing the block re-authorization request flag in the session memory.
  • Fig. 9 shows another embodiment of a CC server 120 which is operable in a communication system 100 for enabling efficient communication over the communication system between the CC server and a CC client 1 1 1 1 , 1 12, 1 13.
  • the CC server comprises a first sending module 902 for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and a receiving module 904 for receiving a CC request message from the
  • the CC server further comprises a second sending module 906 for sending a CC answer message to the CC client for the session, in response to the received CC request message, and a sending-preventing module 908 for preventing sending a second re-authorization request message following the first re-authorization request
  • P42245 message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Disclosed is a credit control, CC, server (120), and a method performed by a CC server in a communication system for enabling efficient communication over the communication system between the CC server (120) and a CC client (111, 112, 113). The method comprises sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message. The method further comprises sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.

Description

METHODS AND CREDIT CONTROL SERVERS FOR ENABLING EFFICIENT COMMUNICATION OVER A COMMUNICATION SYSTEM
Technical field
[0001 ] The present disclosure relates generally to methods performed by a
credit control, CC, server, and CC servers in a communication system for enabling efficient communication over the communication system between the CC server and a CC client.
Background
[0002] Real time charging in a communication network of e.g. a subscriber of a mobile communication network is controlled by an Online Charging System, OCS. According to 3GPP charging and billing requirements, an application has to be able to rate service information in real-time. This is today implemented in an application based on the Diameter protocol, defined by the Internet Engineering Task Force, IETF, in RFC 4006 published August 2005. [0003] The OCS is, using IETF terminology, referred to as a credit control server, CC server. The CC server controls real-time charging for applications connected to the network. The applications are called credit control clients, CC clients. According to the RFC 4006, paragraph 5.5, the CC server can, based on information about its ongoing sessions and its service logic, request credit re- authorization. A CC client that receives a re-authorization request from the CC server has to answer by sending a re-authorization answer followed by a CC request to the CC server, in order to initiate the credit re-authorization. This is today implemented by letting the CC server send a re-authorization request when a change on an account, e.g. an account of a subscriber connected to the CC client, has been made that could affect rating for sessions ongoing for the subscriber. An example is when an account has been replenished.
[0004] However, it may happen that unnecessary initiation of re-authorization procedures are performed by the CCS, for example in case of parallel events. As a result there is unnecessary signaling load on the communication network.
P42245 Consequently, there is a need for a more efficient re-authorization procedure avoiding such unnecessary re-authorizations.
Summary
[0005] It is an object of the invention to address at least some of the problems and issues outlined above. More specifically, it is an object of the present invention to make signaling between a CC server and a CC client in a communication network more efficient.
[0006] It is possible to achieve these objects and others by using a method and an apparatus as defined in the attached independent claims. [0007] According to one aspect, a method is provided performed by a credit control, CC, server in a communication system for enabling efficient
communication over the communication system between the CC server and a CC client. The method comprises sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first reauthorization request message. The method further comprises sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
[0008] According to another aspect, a CC server is provided operable in a communication system for enabling efficient communication over the
communication system between the CC server and a CC client. The CC server comprises a processor and a memory. Said memory contains instructions executable by said processor, whereby said CC server is operative for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message. Said memory P42245 further contains instructions executable by said processor, whereby said CC server is operative for sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second reauthorization request message is triggered before the CC answer message has been sent.
[0009] According to another aspect, a CC server is provided operable in a communication system for enabling efficient communication over the
communication system between the CC server and a CC client. The CC server is adapted for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message. The CC server is further adapted for sending a CC answer message to the CC client for the session, in response to the received CC request message, and preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent. [00010] According to other aspects, computer programs and carriers containing the computer programs are also provided, the details of which will be described in the claims and the detailed description.
[0001 1 ] The above methods and CC servers may be configured and
implemented according to different optional embodiments. Those embodiments and further possible features and benefits of this solution will become apparent from the detailed description below.
Brief description of drawings
[00012] The solution will now be described in more detail by means of exemplary embodiments and with reference to the accompanying drawings, in which:
P42245 [00013] Fig. 1 is a schematic block diagram of an example of a communication system in which the present invention may be used.
[00014] Figs. 2 and 3 are flow charts illustrating procedures in a CC server according to different possible embodiments. [00015] Figs. 4-6 are signaling diagrams illustrating examples of a procedure performed by a CC server according to possible embodiments.
[00016] Figs. 7-9 are schematic block diagrams illustrating a CC server in more detail according to different possible embodiments.
Detailed description
[00017] Briefly described, a solution is provided performed by a credit control, CC, server, in a communication system for enabling efficient communication over the communication system between the CC server and a CC client. This may be achieved by the CC server blocking any triggered second re-authorization request message triggered between the time point when a first re-authorization request message is sent and the time point when a CC answer is sent in response to a CC request triggered by the first re-authorization request message. Thereby, any triggered unnecessary re-authorization request messages are prevented from being sent during this time period, which results in less load on the communication interface between the CC server and the CC client. [00018] Fig. 1 shows an exemplary communication system in which the present invention may be used. The communication system comprises a communication network 100 to which an online charging system, OCS, 120 is connected. The OCS 120 may be, or comprise, a CC server for controlling credit information for CC clients 1 1 1 , 1 12, 1 13 also connected to the communication network 100. The CC clients 1 1 1 , 1 12, 1 13 are in fig. 1 exemplified as a Mobile Switching Center, MSC, 1 1 1 for a GSM-based mobile network, a Gateway GPRS Serving Node, GGSN for a GPRS-based mobile network and an application server 1 13. The
P42245 communication system may also comprise a Home Location Register, HLR, connected to the communication network.
[00019] Fig. 2 shows a method according to an embodiment, performed by a CC server 120 in a communication system for enabling efficient communication over the communication system between the CC server 120 and a CC client 1 1 1 , 1 12, 1 13. The method comprises sending 202 a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving 204 a CC request message from the CC client, in response to the sent first re-authorization request message. The method further comprises sending 206 a CC answer message to the CC client for the session, in response to the received CC request message, and preventing 208 sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent. [00020] A CC client may be a node in the communication server that delivers a service to subscribers in the communication network. The CC client may for example be an application server delivering applications to the subscriber, such as a server of a supplier of domestic electrical power for calculating used electrical power (in e.g. kWh) and price for subscribers, or an MSC/GGSN delivering telecommunication services. The messages may be messages according to the Diameter Credit Control Application protocol, IETF RFC 4006 and Diameter Base Protocol RFC 6733 published October 2012. The Diameter protocol is an authentication, authorization and accounting protocol for communication networks. For example, the re-authorization request message may be a Diameter RAR message. The preventing sending a second re-authorization request message following the first re-authorization message may signify blocking sending of a second re-authorization second, even though a sending of the second reauthorization has been triggered. The term "a session" is a session between the CC server and a subscriber connected to the CC client which session is credit control monitored. A subscriber may have one or many sessions simultaneously.
P42245 One session may be e.g. a web browser using a certain service for browsing the Internet, another service may be a voice call. A subscriber may be a subscriber of a telecommunication operator. Other examples of subscribers are an electrical power/water/gas meter or a "household" that has a session with possible services electrical power/water/gas/heating. Another example of a subscriber may be a vending machine.
[00021 ] A re-authorization message may be triggered by e.g. a changed price for a service. The changed price may be due to a price offer accepted by a user, a changed user subscription, a triggered user bonus resulting in a cheaper price, a threshold value that has been exceeded resulting in a changed price for the service etc. The second re-authorization request message may also be triggered e.g. by the received CC request message. Such a second re-authorization request message is unnecessary since the price change has already been taken care of by the first re-authorization request message. Sending of such a second re- authorization request message causes unnecessary signaling in the network. By preventing sending any second re-authorization request message triggered in the time span from sending the first re-authorization request message and to the CC answer has been sent in response to the first re-authorization request message, such unnecessary signaling would be prevented. This would save communication resources and result in a lower load over the communication interface between the CC server and the CC client.
[00022] Fig. 3 shows other embodiments of a method performed by a CC server 120 in a communication system for enabling efficient communication over the communication system between the CC server 120 and a CC client. According to one embodiment, the preventing of sending 208 of a second re-authorization request message, as mentioned in relation to fig. 2, may comprise setting 304 a state of the session to a re-authorization request non-sending state, in response to the sending 202 of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re- authorization request message is sent for the session, and setting 314 the state of
P42245 the session to a re-authorization request sending state, in response to the sending 206 of a CC answer message to the CC client for the session, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session. The preventing of sending 208 may further comprise checking the state of the session before sending the second re-authorization request message, and only sending the second re-authorization request message when the state of the session is in the re-authorization request sending state. This is illustrated in fig. 3 by the steps of blocking 308 the second re-authorization request when the state is in the re-authorization request non-sending state and sending 316 the second (or third re-authorization request if one re-authorization request has already been blocked) when the state is in the re-authorization request sending state.
[00023] According to another embodiment, the method may further comprise, when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period 306, allowing sending a second re-authorization request message triggered after the defined time period has expired. In the embodiment of fig. 3 this is realized by checking the time from the first re-authorization request message has been sent and if a defined time period has expired 306 and no CC request message has been received, there is probably something wrong and it will be allowed to send a re-authorization request again. According to an alternative, the allowing of sending a second re-authorization request message triggered after the defined time period comprises setting 314 the state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session. By such an embodiment, it is avoided that no received CC request due to e.g. process failure reasons, results in no more re-authorization requests are being sent for the session and consequently no more charging updates are performed for the session.
P42245 [00024] According to another embodiment, the method may further comprise performing 309 a rating procedure triggered by the received CC request, and in response to the performed rating procedure, allowing sending the second reauthorization request message. The allowing of sending a second re-authorization request message triggered in response to a performed rating procedure may comprise setting 314 a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session. [00025] In other words, a rating procedure performed in response to a CC request may, according to an embodiment, trigger that it is allowed to send a second re-authorization request even though the CC answer has not yet been sent. A race condition can occur after rating and a re-authorization request evaluation for a received CC request have been concluded but before a CC answer is sent. In the short time frame between "performed/concluded rating" and "sent CC answer", a new account update might happen. When sending of a new re-authorization request triggered by such an account update is prevented, new information that should be sent will not be sent. By allowing sending of a new reauthorization request in response to the performed rating procedure such a second re-authorization request will still be sent and the new information will be provided. The new account update should in this situation trigger a new reauthorization request because the CCA that is sent will already be based on old account data. Therefore, the re-authorization request block flag need to be cleared as early as possible. [00026] According to an embodiment, the state of the session is set 304 to a reauthorization request non-sending state by setting a block re-authorization request flag in a session memory and the state of the session is set 314 to a reauthorization request sending state by clearing the block re-authorization request flag in the session memory.
P42245 [00027] According to another embodiment, a second RAR triggered by an external trigger received 307 after the first RAR has been sent 202 is blocked 308. In the figure the external trigger is received between the reception 204 of the CC request and the sending 206 of the CC answer, but such an external trigger may be received anytime during the procedure. As long as the external trigger is received after the sending of the first RAR and before the sending of the CC answer it will be blocked.
[00028] Fig. 4 is a signaling diagram showing signals sent between a CC client and a CC server in a re-authorization procedure according to a possible scenario in which Diameter messages are used. A first trigger message is sent from the CC client or from an external node to the CC server. The first trigger message may be an internal trigger 1 .1 a sent from the CC client, e.g. as a CC request, or an external trigger 1 .1 b sent from an external node, such as e.g. a self-care portal for the end user. The first trigger message may trigger a rating procedure to be performed. The rating procedure produces a rating result, for example if a rate is to be changed for a session. The rating result is used in a RAR evaluation procedure. The RAR evaluation procedure evaluates whether or not a RAR is to be sent to the active sessions of a subscriber. The RAR evaluation procedure may for example be performed according to the following: It starts by checking whether a new resource got active based on the rating result. If no new resource got active no RAR is to be sent. If a resource got active, the RAR evaluation procedure proceeds by checking whether the new resource has impact on rating for other services. This may be performed according to different configured rules. If the new resource has no impact, no RAR is to be sent. If the new resource has impact on other services, the RAR evaluation procedure proceeds by acquiring data of active sessions in a session memory for a subscriber and matching the services of the active sessions with the impacted services. If there is no match, no RAR is to be sent, if there is a match, it is checked whether the RAR blocking flag is set, if it is not set a RAR is to be sent.
P42245 [00029] As mentioned, the trigger message 1 .1 a or 1 .1 b may trigger a first reauthorization request, RAR, message 1.2. In response to the sending of the first RAR message, a RAR blocking flag is set 1 .3 by the CC server. This RAR blocking flag prevents, or blocks, any triggered new (also called second) RAR following the first RAR from being sent from the CC server to the CC client for the same session. The first RAR sent to the CC client triggers the CC client to send a re-authorization answer 1 .4 to the CC server followed by a CC request 1 .5. Such a CC request 1 .5 may trigger a second RAR that does not need to be sent since the changes on the subscriber's account is taken care of already by the CCR resulting from the first RAR. By the blocking flag being set, such an unnecessary triggered second RAR is blocked/prevented from being sent, which results in a more efficient re-authorization procedure. The CC request 1 .5 triggers the CC server to send a CC answer 1 .6 to the CC client. The sending of the CC answer may trigger clearing 1 .7 of the RAR blocking flag. After the RAR blocking flag has been cleared, second RARs 1.8 may be sent again.
[00030] Fig. 5 shows signals sent between a CC client and a CC server in a reauthorization procedure according to another scenario in which there are two CC clients involved: CC client A and CC client B. The procedure starts by the CC server receiving a trigger for starting a re-authorization procedure for CC client A, in this case an external trigger 2.1. The external trigger 2.1 may trigger a rating procedure and/or a RAR evaluation procedure to be performed to evaluate whether a RAR is to be sent to the CC client A. An external trigger may be e.g. an account change or any other type of change that may influence a rating result. These procedures may be performed in a similar way as described in relation to fig. 4 or in any other possible way. In this example the RAR evaluation procedure results in a first RAR 2.2 being sent to CC client A. The sending of the first RAR triggers a RAR blocking flag to be set 2.3 for CC client A. The CC client A responds by sending a re-authorization answer 2.4 to the CC server, followed by a CC request 2.10. At the same time, before the CC request is received, an external trigger 2.5, for both A and B is received. The external trigger triggers a RAR evaluation procedure to be performed which results in a first RAR being sent 2.6 to P42245 CC client B. However, no RAR is sent to CC client A since the RAR block flag for A is set. In other words, the (second) RAR triggered for CC client A is blocked 2.7. Further, the first RAR sent 2.6 to CC client B triggers the RAR blocking flag for CC client B to be set. Thereafter, a re-authorization answer 2.9 is sent from CC client B to the CC server. Further, the CC request 2.10 sent from the CC client A to the CC server triggers the CC server to send a CC answer 2.1 1 to the CC client A. The sending of the CC answer 2.1 1 triggers the release 2.12 of the RAR blocking flag for A. Thereafter, it is again possible to send RARs to the CC client A, catering for new necessary charging updates to make online-charging possible for client A. Thereafter, a CC request 2.13 is sent from CC client B to the CC server which triggers the CC server to send a CC answer 2.14 to CC client B. The sending of the CC answer triggers release 2.15 of the RAR blocking flag for CC client B, catering for new necessary charging updates to make online-charging possible for CC client B. [00031 ] Fig. 6 shows another possible signaling scenario according to another embodiment. This embodiment differs from the embodiment described in fig. 4 in that the rating procedure 3.6 triggered by the received CC request 3.5 triggers the RAR blocking flag to be cleared, whereas in the embodiment of fig. 4 the RAR blocking flag is cleared when the CC answer is sent. By such a measure the RAR blocking flag is cleared a little bit earlier, catering for the case where the CC request 3.5 actually triggers a change which need to be reflected at the CC client, in other words, a change is triggered for which a RAR needs to be issued.
[00032] Fig. 7 schematically shows a CC server 120 according to an
embodiment. The CC server may comprise a session memory 716 for storing information about the active sessions controlled by the CC server. The session memory 716 may hold information about connected services per subscriber. One session may provide one or more services. A service may be a service as specified in RFC 4006, for example a Gy session for a subscriber. The session memory may further store information needed to send a RAR for a specific session and keep track of state information, i.e. the RAR blocking flag. The CC
P42245 server may further comprise a service configuration unit 702 that has information controlling the behavior of the CC server at rating for different context. The information may be a set of parameters that specifies certain services, where each service has an internal service ID. The CC server may further comprise a rating unit 704 that performs the rating procedure and/or calculates price for a service and/or performs other possible account changes. The CC server may further have a communication interface 712 for receiving and handling incoming none charging requests, e.g. any other type of request that may for example change pricing, that can affect a subscriber's account and for receiving charging requests. The CC server may further comprise a resource configuration unit having a list of resources that are connected to a subscriber's account. Each resource may have an internal resource ID. A resource may comprise different attributes. A resource may be an entity connected to a subscriber in the OCS. The resource can be both individual and shareable between different subscribers. It can be for example a counter, a threshold, an account with monetary units or any other consumption unit, e.g. time, bytes etc.
[00033] There may also be configurable rules that describe a relation between the service IDs and the resource IDs that point out which services are affected if resources, resource attributes and/or attribute values are modified. A possible rule execution flow/analysis may be as follows: Resource ID is matched with service ID. If at least one service is configured to be affected by the resource change, i.e. if the resource ID matches the service ID, the analysis continues, otherwise no RAR is to be triggered. If the resource has been added or removed, a RAR will be triggered. In case of an update, the analysis continues. Then it is verified whether rules for specific attributes of the updated resource are configured. If not, a RAR is triggered. Then the updated attributes that are configured not to be eligible for triggering a RAR are filtered out. If at least one updated attribute passes the filter, the analysis continues, otherwise no RAR is to be triggered. Thereafter it is checked whether there are specific rules for the nature for the update for an updated attribute. If no additional rules for at least one of the updated, and not in the previous step filtered, attributes exist, a RAR is to be triggered. Then it is P42245 checked that the nature of attribute change is applicable for triggering a RAR. If this is the case a RAR is triggered, if it is not the case a RAR is not triggered.
[00034] The CC server also comprises a RAR evaluation unit 708 for deciding if there has been an account change that affects the rating for any of the active services on an account. An account may be the same as a subscriber. The RAR evaluation unit 708 may further be arranged for receiving a request when an account change has occurred. The RAR evaluation unit 708 may comprise a set of configurable rules that determine if the account change should generate a RAR and a configuration that holds the relationship between services and resources and that maps which resources that affect which services. The RAR evaluation unit may further have an interface towards the session memory, an interface towards the service configuration unit 702 and an outgoing interface through which RARs are sent.
[00035] Fig. 8 shows a CC server 120 according to an embodiment. The CC server 120 is operable in a communication system for enabling efficient
communication over the communication system between the CC server and a CC client 1 1 1 , 1 12, 1 13. The CC server 120 comprises a processor 803 and a memory 804, said memory containing instructions executable by said processor, whereby said CC server 120 is operative for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and receiving a CC request message from the CC client, in response to the sent first re-authorization request message. The memory further contains instructions executable by said processor, whereby said CC server 120 is operative for sending a CC answer message to the CC client for the session, in response to the received CC request message, and for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second reauthorization request message is triggered before the CC answer message has been sent.
P42245 [00036] The CC server 120 may further comprise a communication unit 802, which may be considered to comprise conventional means for communicating from and/or to the other nodes in the communication system, such as the CC clients 1 1 1 , 1 12, 1 13. The conventional communication means may include at least one transmitter and at least one receiver. The CC server may further comprise one or more storage units 806 and further functionality 807 useful for the CC server 120 to serve its purpose as CC server.
[00037] The instructions executable by said processor may be arranged as a computer program 805 stored in said memory 804. The processor may comprise a processing circuitry incorporating functions of a computer central processing unit, CPU, on one or plural integrated circuits. The processor 803 and the memory 804 may be arranged in an arrangement 801 . The arrangement 801 may alternatively be a micro processor and adequate software and storage therefore, a
Programmable Logic Device, PLD, or other electronic component(s)/processing circuit(s) configured to perform the actions, or methods, mentioned above.
[00038] The computer program 805 may comprise computer readable code means, which when run in CC server 120 causes the CC server to perform the steps described in the method described in relation to figs. 2 and/or 3. The computer program may be carried by a carrier. The carrier may be connectable to the processor. The carrier may be an electronic signal, optical signal, radio signal or computer readable storage medium. The storage medium may be an electronic memory such as a RAM, ROM, EEPROM, magnetic tape, blueray disc, CD, DVD or flash memory, from which the program could be downloaded into the memory 804. Alternatively, the storage medium may be a server or any other entity connected to the communication network to which the CC server has access via its communication unit 802. The computer program may then be downloaded from the server into the memory 804.
[00039] Although the instructions described in the embodiments disclosed above are implemented as a computer program 805 to be executed by the processor 803
P42245 at least one of the instructions may in alternative embodiments be implemented at least partly as hardware circuits.
[00040] According to an embodiment, the CC server 120 may be operative for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request non-sending state, in response to the sending of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re-authorization request message is sent for the session, setting the state of the session to a re-authorization request sending state, in response to the sending of a CC answer message to the CC client for the session, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session, and checking the state of the session before sending the second re-authorization request message, and only sending the second re-authorization request message when the state of the session is in the re-authorization request sending state.
[00041 ] According to another embodiment, the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is further operative for, when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period, allowing sending a second re-authorization request message triggered after the defined time period has expired.
[00042] According to another embodiment, the CC server may be operative for allowing sending a second re-authorization request message triggered after the defined time period by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
P42245 [00043] According to another embodiment, the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is further operative for performing a rating procedure triggered by the received CC request, and, in response to the performed rating procedure, allowing sending the second re-authorization request message.
[00044] According to another embodiment, the CC server may be operative for allowing sending the second re-authorization request message triggered in response to the performed rating procedure by the memory 804 further containing instructions executable by the processor 803 whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
[00045] According to another embodiment, the memory 804 may further contain instructions executable by the processor 803 whereby the CC server is operative for setting the state of the session to a re-authorization request non-sending state by setting a block re-authorization request flag in a session memory and whereby the CC server is operative for setting the state of the session to a re-authorization request sending state by clearing the block re-authorization request flag in the session memory. [00046] Fig. 9 shows another embodiment of a CC server 120 which is operable in a communication system 100 for enabling efficient communication over the communication system between the CC server and a CC client 1 1 1 , 1 12, 1 13. The CC server comprises a first sending module 902 for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client and a receiving module 904 for receiving a CC request message from the
CC client, in response to the sent first re-authorization request message. The CC server further comprises a second sending module 906 for sending a CC answer message to the CC client for the session, in response to the received CC request message, and a sending-preventing module 908 for preventing sending a second re-authorization request message following the first re-authorization request
P42245 message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
[00047] Although the description above contains a plurality of specificities, these should not be construed as limiting the scope of the concept described herein but as merely providing illustrations of some exemplifying embodiments of the described concept. It will be appreciated that the scope of the presently described concept fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the presently described concept is accordingly not to be limited. Reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." All structural and functional equivalents to the elements of the above- described embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed hereby. Moreover, it is not necessary for an apparatus or method to address each and every problem sought to be solved by the presently described concept, for it to be encompassed hereby.
P42245

Claims

1 . A method performed by a credit control, CC, server (120), in a
communication system for enabling efficient communication over the
communication system between the CC server (120) and a CC client (1 1 1 , 1 12, 1 13), the method comprising:
sending (202) a first re-authorization request message to the CC client for a session between the CC server and the CC client;
receiving (204) a CC request message from the CC client, in response to the sent first re-authorization request message;
sending (206) a CC answer message to the CC client for the session, in response to the received CC request message, and
preventing (208) sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
2. Method according to claim 1 , wherein the preventing (208) sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second reauthorization request message is triggered before the CC answer message has been sent comprises:
setting (304) a state of the session to a re-authorization request non- sending state, in response to the sending of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re-authorization request message is sent for the session;
setting (314) the state of the session to a re-authorization request sending state, in response to the sending of a CC answer message to the CC client for the session, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session, and
checking the state of the session before sending the second re- authorization request message, and only sending the second re-authorization
P42245 request message when the state of the session is in the re-authorization request sending state.
3. Method according to any of the preceding claims, further comprising:
when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period (306), allowing sending a second re-authorization request message triggered after the defined time period has expired.
4. Method according to claim 3, wherein the allowing of sending a second re-authorization request message triggered after the defined time period comprises setting (314) a state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
5. Method according to any of the preceding claims, further comprising:
performing (309) a rating procedure triggered by the received CC request,
in response to the performed rating procedure, allowing sending the second re-authorization request message.
6. Method according to claim 5, wherein the allowing of sending a second re-authorization request message triggered in response to a performed rating procedure comprises setting (314) a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the reauthorization request sending state allowing that a new re-authorization request message is sent for the session.
7. Method according to claim 2, 4 or 6, wherein the state of the session is set (304) to a re-authorization request non-sending state by setting a block reauthorization request flag in a session memory and wherein the state of the
P42245 session is set (314) to a re-authorization request sending state by clearing the block re-authorization request flag in the session memory.
8. A Credit Control, CC, server (120) operable in a communication system (100) for enabling efficient communication over the communication system between the CC server and a CC client (1 1 1 , 1 12, 1 13), the CC server (120) comprising a processor (803) and a memory (804), said memory containing instructions executable by said processor, whereby said CC server (120) is operative for:
sending a first re-authorization request message to the CC client for a session between the CC server and the CC client;
receiving a CC request message from the CC client, in response to the sent first re-authorization request message;
sending a CC answer message to the CC client for the session, in response to the received CC request message, and
preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
9. CC Server (120) according to claim 8, wherein the CC server being operative for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, comprises the memory (804) further contains instructions executable by the processor (803) whereby the CC server is operative for:
setting a state of the session to a re-authorization request non- sending state, in response to the sending of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re-authorization request message is sent for the session;
setting the state of the session to a re-authorization request sending state, in response to the sending of a CC answer message to the CC client for the
P42245 session, the re-authorization request sending state allowing that a new reauthorization request message is sent for the session, and
checking the state of the session before sending the second reauthorization request message, and only sending the second re-authorization request message when the state of the session is in the re-authorization request sending state.
10. CC Server (120) according to claim 8 or 9, wherein the memory (804) further contains instructions executable by the processor (803) whereby the CC server is further operative for:
when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period, allowing sending a second re-authorization request message triggered after the defined time period has expired.
1 1 . CC Server (120) according to claim 10, wherein the CC server being operative for allowing sending a second re-authorization request message triggered after the defined time period comprises the memory (804) further containing instructions executable by the processor (803) whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re-authorization request message is sent for the session.
12. CC Server (120) according to any of claims 8-1 1 , wherein the memory (804) further contains instructions executable by the processor (803) whereby the CC server is further operative for:
performing a rating procedure triggered by the received CC request, and
in response to the performed rating procedure, allowing sending the second re-authorization request message.
13. CC Server (120) according to claim 12, wherein the CC server being operative for allowing sending the second re-authorization request message triggered in response to the performed rating procedure comprises the memory (804) further containing instructions executable by the processor (803) whereby the CC server is operative for setting a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the reauthorization request sending state allowing that a new re-authorization request message is sent for the session.
14. CC Server (120) according to claim 9, 1 1 or 13, wherein the memory (804) further containing instructions executable by the processor (803) whereby the CC server is operative for setting the state of the session to a re-authorization request non-sending state by setting a block re-authorization request flag in a session memory and whereby the CC server is operative for setting the state of the session to a re-authorization request sending state by clearing the block re- authorization request flag in the session memory.
15. A credit control, CC, server (120) operable in a communication system (100) for enabling efficient communication over the communication system between the CC server and a CC client (1 1 1 , 1 12, 1 13), the CC server comprising:
a first sending module (902) for sending a first re-authorization request message to the CC client for a session between the CC server and the CC client;
a receiving module (904) for receiving a CC request message from the CC client, in response to the sent first re-authorization request message;
a second sending module (906) for sending a CC answer message to the CC client for the session, in response to the received CC request message, and
a sending-preventing module (908) for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
16. A computer program (805) comprising computer readable code means, which when run in a credit control, CC, server (120), operable in a communication system (100) for enabling efficient communication over the communication system between the CC server and a CC client, causes the CC server (120) to perform the following steps:
sending a first re-authorization request message to the CC client for a session between the CC server and the CC client;
receiving a CC request message from the CC client, in response to the sent first re-authorization request message;
sending a CC answer message to the CC client for the session, in response to the received CC request message, and
preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
17. A carrier containing the computer program (805) according to claim 16, wherein the carrier is one of an electronic signal, optical signal, radio signal or computer readable storage medium.
18. A credit control, CC, server (120) operable in a communication system (100) for enabling efficient communication over the communication system between the CC server and a CC client (1 1 1 , 1 12, 1 13), the CC server being adapted for:
sending a first re-authorization request message to the CC client for a session between the CC server and the CC client;
receiving a CC request message from the CC client, in response to the sent first re-authorization request message;
sending a CC answer message to the CC client for the session, in response to the received CC request message, and
preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent.
19. CC server (120) according to claim 18, wherein the CC server being adapted for preventing sending a second re-authorization request message following the first re-authorization request message to the CC client for the session, when the second re-authorization request message is triggered before the CC answer message has been sent comprises:
setting a state of the session to a re-authorization request non- sending state, in response to the sending of the first re-authorization request message for the session, the re-authorization request non-sending state preventing that any new re-authorization request message is sent for the session;
setting the state of the session to a re-authorization request sending state, in response to the sending of a CC answer message to the CC client for the session, the re-authorization request sending state allowing that a new re- authorization request message is sent for the session, and
checking the state of the session before sending the second reauthorization request message, and only sending the second re-authorization request message when the state of the session is in the re-authorization request sending state.
20. CC server (120) according to claim 18 or 19, further being adapted for allowing sending a second re-authorization request message triggered after the defined time period has expired, when no CC request message has been received from the CC client in response to the first re-authorization request message within a defined time period.
21 . CC server (120) according to claim 20, wherein the CC server being adapted for allowing sending a second re-authorization request message triggered after the defined time period comprises setting a state of the session to a reauthorization request sending state, in response to expiry of the defined time period, the re-authorization request sending state allowing that a new re- authorization request message is sent for the session.
22. CC server (120) according to any of claims 18-21 , further being adapted for:
performing a rating procedure triggered by the received CC request, and
in response to the performed rating procedure, allowing sending the second re-authorization request message.
23. CC server (120) according to claim 22, wherein the CC server being adapted for allowing sending a second re-authorization request message triggered in response to a performed rating procedure comprises setting a state of the session to a re-authorization request sending state, in response to the performed rating procedure, the re-authorization request sending state allowing that a new reauthorization request message is sent for the session.
24. CC server (120) according to claim 19, 21 or 23, wherein the state of the session is set to a re-authorization request non-sending state by setting a block re- authorization request flag in a session memory and wherein the state of the session is set to a re-authorization request sending state by clearing the block reauthorization request flag in the session memory.
P42245
PCT/SE2014/050268 2014-03-05 2014-03-05 Methods and credit control servers for enabling efficient communication over a communication system WO2015133948A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2014/050268 WO2015133948A1 (en) 2014-03-05 2014-03-05 Methods and credit control servers for enabling efficient communication over a communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2014/050268 WO2015133948A1 (en) 2014-03-05 2014-03-05 Methods and credit control servers for enabling efficient communication over a communication system

Publications (1)

Publication Number Publication Date
WO2015133948A1 true WO2015133948A1 (en) 2015-09-11

Family

ID=50390165

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2014/050268 WO2015133948A1 (en) 2014-03-05 2014-03-05 Methods and credit control servers for enabling efficient communication over a communication system

Country Status (1)

Country Link
WO (1) WO2015133948A1 (en)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Diameter Credit Control Application protocol", IETF RFC 4006 AND DIAMETER BASE PROTOCOL RFC 6733, October 2012 (2012-10-01)
"Internet Engineering Task Force, IETF", RFC 4006, August 2005 (2005-08-01)
FAJARDO V ET AL: "Diameter Base Protocol; rfc6733.txt", DIAMETER BASE PROTOCOL; RFC6733.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARD, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 25 October 2012 (2012-10-25), pages 1 - 152, XP015086454 *
HAKALA L MATTILA ERICSSON J-P KOSKINEN M STURA J LOUGHNEY NOKIA H: "Diameter Credit-Control Application; rfc4006.txt", 20050801, 1 August 2005 (2005-08-01), XP015041993, ISSN: 0000-0003 *

Similar Documents

Publication Publication Date Title
US10462623B2 (en) Method for processing rate group, method for charging for data service, and related device and system
US10575146B2 (en) Method and apparatus relating to online charging in an IP multimedia subsystem
US8949447B2 (en) Optimized interface between two network elements operating under an authentication, authorization and accounting protocol
EP3087702B1 (en) Providing toll-free application data access
EP3042468B1 (en) Secure toll-free application network access
RU2473178C2 (en) Control of subscription and billing notice
EP3014806B1 (en) Providing toll-free application data access
CN105611517B (en) Method and apparatus for providing service in user equipment of mobile communication system
CN109479007B (en) Data service control method, related equipment and system
US10326890B2 (en) Method, system and apparatus for data session management in core mobile networks
EP3195635A1 (en) Method, system and apparatus for processing low-balance data session requests
WO2015133948A1 (en) Methods and credit control servers for enabling efficient communication over a communication system
US9241250B2 (en) System and method to support mediation of OCS diameter/RO reauthorization on GSM camel networks
EP1835698B1 (en) Communications system
US10091008B2 (en) Method and apparatus for performing credit reservations for online charging in a communication network
EP2577906B1 (en) Session related data retrieval for online charging
CN101860634A (en) Method and system for implementing packet prepayment
KR101707544B1 (en) Method and apparatus for providing prepay service in Fixed Mobile Convergence environment
WO2009152847A1 (en) A method of communication for use in a credit control application, communication system and computer program product
OA18002A (en) Application based selection of a radio network for toll-free applications.

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

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

Country of ref document: EP

Kind code of ref document: A1