The present invention relates to a system, method, and network elements for providing information related to a service such as a Supplementary Service, preferably an Advice of Charge, AoC, Supplementary Service. The service may preferably be provided with or for another service such as a communication service which may e.g. be a voice communication service, a data communication service, a multimedia communication service, etc. The supplementary service and the communication service are provided in a communication network with a suitable protocol, preferably Session Initiation Protocol, SIP, and preferable in a SIP network such as the IP Multimedia Subsystem (IMS). Further, the information needed to accomplish this supplementary service could also be provided in a diameter credit control application, DCCA.
The present AoC specification is based on a solution where the AoC Function, which could be located in a dedicated AOC application server, AoC AS, or could be included in other IMS entity, takes care of building AoC information, which is delivered to user equipment. In order to provide that information, the AoC Function needs to get relevant AoC information from an online charging system, OCS, or other similar entity where such information is stored. When an IMS-gateway, IMS-GW triggers to an OCS using diameter credit control application, DCCA (Ro-interface), the IMS-GW must obtain an indication about AoC in order to request AoC related information from the OCS. This information is also needed by other network entities involved in the session, e.g. application servers offering services. That is, the AoC related information should be transferred to S-CSCF and further to AoC Function. If this is not done, AoC Function must do the additional Rating Request to OCS itself leading to additional signalling and load for the OCS.
According to an aspect of the present invention, there is provided a system, comprising:
According to further refinements of the invention as defined under the above aspect,
According to a further aspect of the present invention, there is provided a network element, comprising:
According to further refinements of the invention as defined under the above aspect,
According to a still further aspect of the present invention, there is provided a method, comprising:
According to further refinements of the invention as defined under the above aspect,
According to a further aspect of the present invention, there is provided a computer program product including a program for a processing device, comprising software code portions for performing the steps of the method as described above when the program is run on the processing device.
The invention proposes providing information related to a service or supplementary service such as the Advice of Charge, AoC, service that is compliant with current requirements and standards.
When the serving call session control function, S-CSCF, detects that a subscriber could have an active AoC service, it will route SIP messages via an AoC Function. AoC Function will fetch precise AoC service type from HSS using Sh-interface. In online cases, the triggering from IMS-GW to OCS will be done using the Ro-interface.
In case of SIP, in order to be able to request needed AoC related information from the OCS, the IMS-GW must get this information from the S-CSCF via SIP. This information could be added to a private session initiation protocol header, P-Header, in a P-Charging-Vector header.
In case of DCCA, when session related charging is in question, there is currently no method available in DCCA to get AoC related information asked from OCS in a credit control request CCR(INITIAL_REQUEST) or to have it returned from OCS in a credit control answer CCA(INITIAL_REQUEST). According to known methods, the AoC related PRICE_ENQUIRY is done using only CCR(EVENT_REQUEST) and the got information is only the cost, not tariffs.
According to embodiments of the present invention, this problem is solved by additional AoC related attribute value pairs AVPs.
The invention is preferably implemented in or for a mobile communication network, but could also be used in a fixed or cable communication network.
Generally, a communication service can be provided by SIP requests such as INVITE, SUBSCRIBE, MESSAGE, PUBLISH, etc., or by any other appropriate service providing or setting up a communication or session, such as a call, with another network element. A supplementary service can, e.g., be an Advice of Charge.
Generally, without restriction thereto, the invention relates to DCCA and the SIP area, IP Multimedia Subsystem, IMS, NGN, Next Generation Networks, and the provision of information related to Supplementary Services with SIP and DCCA. Particularly, but without restriction thereto, it applies to the provision of information related to the Advice of Charge Supplementary Service with SIP and DCCA.
For the purpose of the present invention to be described herein below, it should be noted that
Embodiments of the present invention are described herein below with reference to the accompanying drawings, wherein:
Embodiments of the present invention will be described herein below with reference to the accompanying drawings.
The IMS charging architecture as shown in
In the following, embodiments of the present invention are described, in which the communication network employs SIP.
Here, it is assumed that signalling optimization is used, that is, AoC Function does not make the rating request separately. Also the additional method where AoC Function will send in session setup phase SIP message 183 Sessions progress to UE via S-CSCF and receive PRACK from UE via S-CSCF is left out for sake of simplicity.
First, in a step 1, a SIP INVITE message is sent from user equipment UE or a P-CSCF (not shown in
The SIP messages are routed via AoC Function. AoC Function will fetch the precise AoC-type from HSS using Sh-interface. In this phase there is added a P-Header in SIP with a P-Charging-Vector having a new value indicating one or a combination of AoC-types. The values can be, e.g.:
When AoCC-S/D/E are in question, it can be assumed that UE is using prepaid SIM card, or any corresponding device, where credit is stored and deducted at set-up, during or at the end of the session according to parameters UE has received from the network.
When AoCI-S/D/E are in question, charging information is presented in UE at set-up, during or at the end of the session without any action required by phone.
Then, in a step 2, a SIP INVITE message is forwarded from the S-CSCF to the AoC Function. Further, in a step 3, a SIP INVITE message is sent from the AoC Function to the S-CSCF and, in a step 4, a SIP INVITE message is sent from the S-CSCF to the IMS-GW.
In a step 5, a credit control request CCR is sent from the IMS-GW to the OCS. Since, the IMS-GW has got the AoC indication (AoC type) from SIP, the IMS-GW can deliver that information to the OCS.
Then, in a step 6, a credit control answer CCA is sent from the OCS to the IMS-GW. The OCS returns the granted service units and AoC related charging information according to the received AoC type.
Then, in a step 7, a SIP INVITE message is sent from the IMS-GW to the S-CSCF and in step 8, a SIP INVITE message is sent from the S-CSCF to a terminating party (not shown in
If the AoC Function will take care of all rating requests, signalling involving an additional application server serving a subscriber according to embodiments of the invention could be as follows.
In a step 11, a SIP INVITE message is sent from the S-CSCF to the AS. The S-CSCF detects that the subscriber has a service which is offered by the AS. In the SIP message there is added a P-Header in SIP with a P-Charging-Vector having a new value or a combination indicating an AoC-types, as described above with respect to
According to this information, the AS knows that it must return additional data in step 14 so that the AoC Function is able to retrieve service specific charging info from OCS, because otherwise, the AoC Function will know nothing about the service offered by the OCS.
In a step 12, a CCR, which includes an AoC indication, is sent from the AS to the OCS. The OCS will then rate the request and reserve money. In a step 13, a CCA, which may include special AS AoC related data, is sent from the OCS to the AS and the OCS returns the granted service units.
In a step 14, a SIP INVITE message, in which data needed to retrieve AoC related information concerning the AS is included, as mentioned above, is sent from the AS to the S-CSCF. Further, in a step 15, a SIP INVITE message, in which AoC related data concerning the AS is included, is sent from the S-CSCF to the AoC Function.
In a step 16, a rating request is sent from the AoC Function to the OCS. In the request, the AoC Function requests AS related AoC information from the OCS. The request may include special AS AoC related data received in the SIP INVITE. IN a step 17, a rating response is sent from the OCS to the AoC Function, in which the OCS returns the AoC related information. The AoC Function then stores the AoC related information (to be inserted into a 183 response or 200OK response).
Then, in a step 18, a SIP INVITE message is sent from the AoC Function to the S-CSCF and, in a step 19, a SIP INVITE message is sent from the S-CSCF to a terminating party (not shown in
In the following, embodiments of the present invention are described, in which the communication network employs DCCA. Here, reference is made to the signalling diagram shown in
In a similar manner as described above, it is assumed here that signalling optimization is used, that is, AoC AS does not make the rating request separately.
First, in a step 1, a SIP INVITE message is sent from user equipment UE or a P-CSCF (not shown in
Then, in a step 2, a SIP INVITE message is forwarded from the S-CSCF to the AoC Function. Further, in a step 3, a SIP INVITE message is sent from the AoC Function to the S-CSCF and, in a step 4, a SIP INVITE message is sent from the S-CSCF to the IMS-GW.
In a step 5, a credit control request CCR is sent from the IMS-GW to the OCS. According to an example of the present invention, in this CCR, there is included an attribute value pair (AVP) AoC-type, or several of them if combination of AoC types is used. The construction of the AVP presented here is exemplification which does not exclude other possible AVP structuration. The AVP could have (at least) the following values:
Hence, the CCR from the IMS-GW to the OCS includes an AoC-indicator and the OCS will rate the request, reserve money (if needed) and fetch AoC related information.
In a step 6, a credit control answer CCA is sent from the OCS to the IMS-GW. In this CCA, the OCS returns granted service units and the AoC related information.
According to an example of the present invention, in the CCA there is provided the following AVP which provides the AoC related information:
The format of Tariff-Information and Add-On-Charging-Information AVPs are constructed so that all information related to AoC could be conveyed there, e.g. currency, pulses (if used), actual tariff, tariff switch times, other AS specific AoC information and so on.
In a step 7, a SIP INVITE message is sent from the IMS-GW to the S-CSCF. In this message, the AoC related charging information which will be used in the AoC Function to produce the actual AoC information is returned to the S-CSCF, and stored there, if it is not stored already in IMS-GW.
Then, a SIP INVITE message is sent from the S-CSCF to the terminating party (not shown in
Now, reference is made to
In a step 21, a SIP 200OK message is sent from the terminating party (not shown in
Further, in a step 26, a SIP 200OK message is sent from the S-CSCF to the AoC Function. In this message, the AoC related information, which will be used in the AoC Function to produce actual AoC information will be delivered to the AoC Function. With this AoC related charging information, the AoC Function produces the actual AoC information which will be delivered to UE.
Then, in a step 27, a SIP 200OK message is sent from the AoC Function to the S-CSCF with the AoC information being included in SIP.
After that, in a step 28, a SIP 200OK message is sent from the S-CSCF to the originating party (not shown in
Such a network element 61 is, e.g. the S-CSCF. According to
In the foregoing description of the network element, only the units that are relevant for understanding the principles of the invention have been described using functional blocks. Of course it is obvious that the network element may comprise further units that are necessary for their operation. However, a description of these units is omitted in this specification. The arrangement of the functional blocks of the network devices is not construed to limit the invention, and the functions may be performed by one block or further split into sub-blocks.
According to embodiments of the present invention, there is described how the AoC information is transferred from the OCS to the S-CSCF. For this purpose, according to embodiments of the present invention, a SIP header handling the AoC information is defined which is transferred to the IMS-GWF.
Further, according to embodiments of the present invention, there is described an optimization of the already existing Ro interface (between IMS-GWF and OCS) to reduce the signalling traffic and the load on the OCS. For this purpose, according to embodiments of the present invention, a new AVP is added to the Ro definition. Additionally these AVPs would be needed in every other alternative solution where other interface is used to fetch needed AoC related charging information from OCS.
All processing steps that have been described in the foregoing can also be implemented using computer-readable signals that may be stored on a computer-readable medium and carry instructions to be executed by one of the entities/devices involved.
In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.
The invention provides a method, comprising detecting, at a network element, a type of a supplementary service requested by a user equipment, sending, by the network element, a message containing the detected type of the requested supplementary service to a charging system, receiving, at the network element, a message including information related to the detected type of the requested supplementary service from the charging system. The present invention further provides a respective system and network elements.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/EP08/54424 | 4/11/2008 | WO | 00 | 10/8/2010 |