Technical field

[0001 ] The present disclosure relates to applications offering services by means of a communication network and in particular to adapting charging of such services.

Background

[0002] In communication networks, different service providers may offer services to users by means of various applications. These applications may communicate with, and gain access to, the communication networks via

Application Programming Interfaces, APIs.

[0003] Generally, in communication networks, a first party initiates a

communication session to a second party, e.g. user A makes a telephone call to user B, wherein the initiating (also referred to as the calling or originating) party is charged for the cost of the communication session. The called party is usually not charged for the call. Some businesses or companies may offer to pay for the cost for communication sessions between itself and users (e.g. customers) even though the businesses or companies are not the calling party. This is done by the calling party dialling a toll-free number, wherein the "owner" of the number, i.e. the business or company may be charged for the call. Often, such toll-free numbers only works for national calls and not for international calls.

[0004] A toll-free telephone number is a telephone number that is free for the calling party. They are special numbers with a "well-known" prefix. This prefix may vary per country. For example:

• In Australia, the toll-free prefix is "1800", "1300", "13" followed by 6 to 10 digits.

• In Colombia, toll-free numbers start with 018000.

• In Croatia, the prefix for toll-free numbers is "0800". • In Denmark telephone-numbers have eight digits. The toll-free numbers all begin with "80" followed by six further digits.

• In France the "0800" or "0805" prefix is used for toll-free numbers.

• In Finland, the toll-free prefix is "0800".

• In Hungary, toll-free numbers have "80" prefix.

• In India, the toll-free prefix is "1800" followed by a six or seven digit number.

• In Japan, the prefixes are "0120" and "0800".

• In Sweden, the prefix is "020" or "0200" for toll-free numbers. (Additionally, 0800 is reserved for future use).

These numbers are usually unreachable from other countries.

[0005] This solution is very rigid, static and often not applicable globally. The solution does not provide any flexibility and the charge for calls are only applicable domestically (nationally), wherein the charging is performed in the same manner for all domestic calls.

Summary

[0006] The object is to obviate at least some of the problems outlined above. In particular, it is an object to provide an application, a node in a communication network and a node in a charging system as well as a respective method performed by the application, a node in a communication network and a node in a charging system for charging of services offered by the application to users. These objects and others may be obtained by providing an application, a node in a communication network and a node in a charging system and a method performed by an application, a node in a communication network and a node in a charging system according to the independent claims attached below.

[0007] According to an aspect a method performed by an application for charging of services offered by the application to users is provided. The

application is accessible via a communication network. The method comprises determining, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application; and generating an indication of the charging policy to be applied with respect to the user. The method further comprises transmitting the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy.

[0008] According to an aspect a method performed by a node in a

communication network associated with an application, for charging of

communication sessions with the application when such a communication session is being initiated by a user is provided. The method comprises receiving a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The method also comprises recognising that a communication session is initiated by a user on the list; and generating a second indication of the charging policy to be applied with respect to the user for the initiated communication session. The method further comprises transmitting the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[0009] According to an aspect a method performed by a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user is provided. The method comprises receiving

information from the communication network, an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated

communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The method further comprises determining how and who to charge for the initiated communication session based on the received charging policy; and creating a charging session and a charging record for the initiated communication session based on the received charging policy.

[00010] According to an aspect node comprising an application for charging of services offered by the application to users is provided. The application is accessible via a communication network. The node comprising the application is configured for determining, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application; and for generating an indication of the charging policy to be applied with respect to the user. The node comprising the application is further configured for transmitting the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy.

[0001 1 ] According to an aspect a node in a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user is provided. The node in the communication network is configured for receiving a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node in the communication network is also configured for recognising that a communication session is initiated by a user on the list; and for generating a second indication of the charging policy to be applied with respect to the user for the initiated communication session. The node in the communication network is further configured for transmitting the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[00012] According to an aspect a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user is provided. The node in the charging system is configured for receiving information from the communication network, an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated

communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node in the charging system is further configured for determining how and who to charge for the initiated communication session based on the received charging policy; and for creating a charging session and a charging record for the initiated communication session based on the received charging policy.

[00013] The method performed by the application, method performed by the node in the communication network, the method performed by the node in the charging system as well as the application, the node in the communication network and the node in the charging system have several advantages. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

Brief description of drawings

[00014] Embodiments will now be described in more detail in relation to the accompanying drawings, in which:

[00015] Figure 1 a is a flowchart of a method performed by an application for charging of services offered by the application to users, according to an

exemplifying embodiment. [00016] Figure 1 b is a flowchart of a method performed by an application for charging of services offered by the application to users, according to still an exemplifying embodiment.

[00017] Figure 2a is a flowchart of a method performed by a node in a

communication network for charging of communication sessions with the application when such a communication session is being initiated by a user, according to an exemplifying embodiment.

[00018] Figure 2b is a flowchart of a method performed by a node in a

communication network for charging of communication sessions with the application when such a communication session is being initiated by a user, according to yet an exemplifying embodiment.

[00019] Figure 2c is a flowchart of a method performed by a node in a

communication network for charging of communication sessions with the application when such a communication session is being initiated by a user, according to still an exemplifying embodiment.

[00020] Figure 3a is a flowchart of a method performed by a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user, according to an exemplifying embodiment.

[00021 ] Figure 3b is a flowchart of a method performed by a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user, according to yet an exemplifying embodiment.

[00022] Figure 4a is a signalling diagram of the solution for charging of services offered by the application to users, according to an exemplifying embodiment.

[00023] Figure 4b is a signalling diagram of the solution for charging of services offered by the application to users, according to still an exemplifying embodiment. [00024] Figure 4c is a signalling diagram of a scenario where a user calls a toll- free number according to prior art.

[00025] Figure 5 is a block diagram of a node comprising an application for charging of services offered by the application to users, according to an exemplifying embodiment.

[00026] Figure 6 is a block diagram of a node comprising an application for charging of services offered by the application to users, according to another exemplifying embodiment.

[00027] Figure 7 is a block diagram of a node in a communication network for charging of communication sessions with the application when such a

communication session is being initiated by a user, according to an exemplifying embodiment.

[00028] Figure 8 is a block diagram of a node in a communication network for charging of communication sessions with the application when such a

communication session is being initiated by a user, according to another exemplifying embodiment.

[00029] Figure 9 is a block diagram of a node in a charging system of a communication network associated with an application, for charging of

communication sessions with the application when such a communication session is being initiated by a user, according to an exemplifying embodiment.

[00030] Figure 10 is a block diagram of a node in a charging system of a communication network associated with an application, for charging of

communication sessions with the application when such a communication session is being initiated by a user, according to another exemplifying embodiment.

[00031 ] Figure 1 1 is a block diagram of an arrangement in a node comprising an application for charging of services offered by the application to users, according to an exemplifying embodiment. [00032] Figure 12 is a block diagram of an arrangement in a node in a

communication network for charging of communication sessions with the application when such a communication session is being initiated by a user, according to an exemplifying embodiment.

[00033] Figure 13 is a block diagram of an arrangement in a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user, according to an exemplifying embodiment.

Detailed description

[00034] Briefly described, an application (or node comprising an application), a node in a communication network, a node in a charging system and respective methods performed thereby for charging of communication sessions with the application when such a communication session is being initiated by a user. The solution comprises the application determining at least one or more users for which a charging policy is to apply. The charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application when the communication session is initiated by the users. The application can do so dynamically whenever it determines to do so. The application informs the communication network by means of which it is accessible to users, wherein the network node takes appropriate actions in order to charge in accordance with the charging policy.

[00035] Embodiments of a method performed by an application for charging of services offered by the application to users are provided. The application is accessible via a communication network. Embodiments of such a method will now be described with reference to figures'! a and 1 b.

[00036] Figure 1a illustrates the method 100 comprising determining 1 10, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application; and generating 120 an indication of the charging policy to be applied with respect to the user. The method further comprises transmitting 130 the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the

communication session is to be redirected according to the charging policy.

[00037] The application may be comprised in a node or device, wherein the node or device can be said to perform the method by running the application. Different users may be charged differently for using the service offered by means of the application for any number of reasons. There may be a variety of different charging policies that may apply to different users as will be explained in more detail below. Generally in this disclosure, a user may be associated with an identity, e.g. a telephone number, a personal number or identity, PIN code, user- id, Session Initiation Protocol (SIP) user-id, IP Multimedia Public Identity (IMPU) or any other identity which the network is capable of recognising, wherein the user may be associated with a specific charging policy regardless of the device the user is using for the communication session with the application. In case the user is identified by any other means than that of the telephone number of the device he/she is using, the user may e.g. enter such an identity into the device he/she is using for initiating a communication session, thereby providing such an identity to the communication network. However, the term "user" may also be interpreted to be a specific user device having a unique identity, e.g. a telephone number, or a corporation associated with a unique identity. Further in this disclosure, a communication session may comprise a telephone call, video session, text message, file transfer etc. The communication network and the application are capable of handling all these and other types of communication sessions. The node in the communication network which the application communicates with may be for example a, Internet Protocol Multimedia Subsystem (IMS) node. Further in this disclosure, when it is stated that the application (being the called party) is charged at least a part of a cost for a communication session initiated by the user (being the calling party), it is a service provider who offers its services to the users by means of the application that is charged. The service provider may own the application, may rent the application or in other way making use of the application in order to provide its offered services to users. [00038] Since different users (which incorporates either a physical person or a user device or both) may be charged differently depending on which charging policy is to apply to the user, the application first determines for which users a specific charging policy is to apply when such a user initiates a communication session with the application. Merely as a very simplified example, according to charging policy A, users associated with charging policy A shall not be charged for the communication session with the application when the user(s) is/are the initiating part. Instead, the application shall be charged for the communication session. The application determines that users "a1 ", "a2" and "a3" shall be associated with charging policy A. In this manner when any of them initiates a communication session with the application, the application shall be charged and not the user.

[00039] The application is not the entity that performs the charging so it has to inform the communication network to which it is associated about the charging policy. The communication network comprises or is coupled to a charging system or charging function that handles charging for sessions and the like within the communication network. Consequently, the application has to inform the communication network, which in turn informs the charging system in order for the communication network to handle the charging policy correctly.

[00040] Accordingly, the application generates the indication of the charging policy to be applied with respect to the user. The indication may comprise a list of users for which the charging policy is to be applied. The charging policy itself may also be comprised in the indication or otherwise indicated to communication network. The indication may comprise an ENUM parameter indicating the charging policy in question. Examples of such an ENUM parameter are BusinessAppPays and DefaultChargingApplies. In case there are only two options for the charging policy (e.g. the application is to be charged in full or not at all), the indication may comprise a Boolean parameter. The indication may also comprise an integer or number indicating a ratio or percentage of the cost for the communication session that is to be charged to the application. Still further, the indication may comprise a formula or the like to indicate the charging policy. In practice any type of indication which is identifiable by the network node and the charging system can be applied. The determining and generating steps could be executed e.g. by applying an API, enabling a business or owner of the application to tailor a suitable charging policy for specific users.

[00041 ] The application then transmits the indication to the node of the

communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy. By redirecting, means in this disclosure that all or a part of the charging for the cost of a communication session is taken care of by the

application. Following the exemplifying and simplified example above, the application transmits the indication comprising at least a list of users a1 , a2 and a3 to the node in the communication network so that the node will subsequently be able to inform the charging system or charging function, so that charging can be executed accordingly, which will be described in more detail below. The

transmitted indication also comprises information identifying the charging policy in question, in the illustrative and simplified example above, charging policy A. How the charging policy may be comprised in the indication is exemplified above. In an example, the indication comprises a Boolean parameter which can be "yes'T'true" or "no'T'false". Typically, if set to "yes", then the application shall be charged for the cost of any session initiated by any user on the list, the list and the Boolean parameter both being comprised in the first indication transmitted by the

application to the node in the communication network. If the Boolean parameter is set to "no", then the application is not to be charged for the cost of any session initiated by any user on the list.

[00042] The method performed by the application has several possible

advantages. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[00043] The transmitting 130 of the indication to the network node of the communication network may comprise sending a list of user identifiers of the one or more users for which the indicated charging policy apply to the communication network.

[00044] In order for the communication network to charge for e.g. traffic within itself, wherein traffic may be the above described session, the communication network needs rules, e.g. charging policies to apply to the different types of traffic and/or sessions within the communication network. Generally, the originator of a communication session is the one that is most often charged for the cost of the communication session, at least within the communication network to which it belongs to. By transmitting the indication of the list of users, the application may inform the communication network about which users that are to be charged differently that they normally would when initiating a communication session with the application. The charging policy will be valid for the users on the list until an update is provided from the application to the network node. Such an update may be triggered manually or automatically, typically by applying a suitable API, as mentioned above.

[00045] The users may be identified in different ways depending on the implementation or the type of communication network. Consequently, the application sends the list of user identifiers of the one or more users for which the indicated charging policy apply. The list may be sent to a node in the

communication network. The user identifiers may be a telephone number or any other identifier e.g. a personal number, PIN code, social security number etc., wherein the user identifier may be associated with the user himself/herself irrespective of user device (also referred to as a communication device), or the user identifier may be associated with a specific user device (communication device). In case the user is identified by any other means than that of the telephone number of the device he/she is using, the user may e.g. enter such an identity into the device he/she is using for initiating a communication session, thereby providing such an identity to the communication network.

[00046] The communication network may be an Internet Protocol Multimedia Subsystem, IMS, network.

[00047] Different communication networks may be based on different

technologies. In this example, the communication network is an IMS network. An IMS network is an architectural framework for delivering IP multimedia services. IMS is a packet based communication network often using Session Initiation Protocol, SIP. Examples of IMS network nodes with which the application communicates are Proxy Call State Control Function (P-CSCF), IMS CSCF (I- CSCF), Serving CSCF (S-CSCF), Multimedia Telephony Application Service ( MMTel AS), Interconnection Border Control Functions ( IBCF), Media Resource Function (MRF), Border Gateway Function (BGF).

[00048] Depending on the type of communication session, different application servers may be responsible for sending a charging indication. Merely as an example, when the communication session is a telephone or video call, the MMTel AS will send the charging indication.

[00049] The transmitting 130 of the indication to the network node of the communication network may be performed by sending a SIP message comprising at least an information element indicating that the charging policy is to be applied to users indicated in the SIP message, or any other type of message which the network node can recognise.

[00050] When the application communicates with the communication network, it may send and receive messages, e.g. SIP messages. There are a vast number of existing SIP messages, which are generally of the two types, request and response. A SIP message generally also has a SIP header and a payload.

[00051 ] The SIP headers typically comprise a plurality of fields, e.g. identifying version of the SIP, indication of payload length and type, source address, destination address etc. [00052] The application may thus transmit the indication to the network node by means of sending a SIP message. An information element, which may be comprised in the header or the payload, may indicate to the communication network that the user identities comprised in the SIP message are associated with the charging policy in question. The charging policy in question is indicated by an information element which may be added to the header or payload, e.g. in the form of an ENUM parameter. In case there are only two options for the charging policy (e.g. the application is to be charged in full or not at all), the information element may comprise a Boolean parameter. The information element may also comprise an integer or number indicating a ratio or percentage of the cost for the

communication session that is to be charged to the application. Still further, the information element may comprise a formula or the like to indicate the charging policy. The information elements suggested above constitutes the indicator suggested herein.

[00053] In an example, the determining 1 10 of one or more users for which the charging policy is to apply when initiating the communication session with the application is performed on a per charging policy basis, wherein different charging policies may apply to different users.

[00054] There may be one, two, three or more different charging policies that may be applied to different users. For each charging policy, the application determines which user(s) is/are to be associated with which charging policy.

[00055] As will be exemplified and described in more detail below, the application may apply a plurality of charging policies. Merely as a simplified and illustrative example, the application may employ charging policy B and determine that users b1 , b2, b3, b4 and b5 should be associated with charging policy B; the application bay further employ charging policy C and determine that users c1 and c2 should be associated with charging policy C.

[00056] In another example, the indication is indicative of a charging policy comprising one or more of (a) the application will be charged the total cost for the communication session; (b) the application will be charged an indicated ratio of the total cost for the communication session; and (c) the application will be charged an indicated fixed amount for the communication session, wherein the user will have to be charged for any additional cost for the communication session.

[00057] As stated above, there may be a plurality of different charging policies, wherein different charging policies are to apply to different users. Reverting to the simplified and illustrative examples above, charging policy A entails that the application will be charged the total cost for the communication session.

Consequently, if any of users a1 , a3 or a3 initiates a communication session with the application, the application is to be charged for the total cost for the

communication session. Assume further in this simplified and illustrative example that charging policy B entails that the application will be charged a ratio, e.g. 60%, of the total cost for the communication session. Then if any of users b1 , b2, b3, b4 or b5 initiates a communication session with the application, then that user will be charged 40% of the total cost for the communication session and the application 60% of the total cost for the communication session. Still further, assume that charging policy C entails the application being charged a fixed amount for the communication session, e.g. $5, wherein the user will have to be charged for any additional cost for the communication session. Then if any of users c1 r c2 should initiate a session with the application and the cost of the session (once it is terminated) is $8, then the application will be charged $5 and the user (c1 or c2) will be charged the remaining $3.

[00058] However, should any other user, say user d5 (not associated with any other charging policy for the application), initiate a communication session with the application then user d5 will be charged for the total cost for the communication session.

[00059] The method may further comprise, as illustrated in figure 1 b, updating 1 15 which users for which the charging policy is to apply, anew generating 120 an indication of the charging policy to be applied with respect to the user, and transmitting 130 the indication to a network node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy. [00060] Charging policies and the users to who it should apply may change dynamically for various reasons. For example, assume that a user a3 will get three toll-free calls to the application, then once the user a3 has used his/her three toll- free calls, then the user a3 should be charged in full for any subsequent call to the application. If so, once the user a3 has made his/her third call, the application may remove the user a3 from the charging policy giving the user toll-free calls to the application. The application may comprise a control unit keeping track of the number of calls user a3 has made or initiated to the application. Once user a3 has made his/her third call, the control unit may take action to remove user a3 from the list of being allowed the user toll-free calls to the application, generating the indication and transmitting the updated indication as stated above.

[00061 ] In another illustrative example, assume user b4 will only be charged for 40% (or any other ratio) of the total cost for a communication session, e.g. a telephone call, to the application during a month after having participated in a course or event. Then right after the course or event, the application first includes user b4 in a list of users associated with charging policy B. In other words, the application determines 1 10 at least user b4 to be associated with charging policy B, generates and transmits the indication thereof to the communication network. After expiry of the month, the user b4 is no longer entitled to a reduction of the cost for communication sessions with the application. Consequently, the application determines 1 10 which users (b4 excluded) for which charging policy B is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part (60% in this example) of the cost for the communication session between the user and the application.

[00062] In another example, the charging policy is only valid for a limited period of time. Once such a charging policy starts to be valid a timer is started, e.g. when transmitting 130 the indication to the network node. At timer time-out a new, updated charging policy is provided, according to step 1 15, resulting in that a new charging policy, typically indicating that the calling user is now to be charged in a conventional manner, is transmitted to the network node. [00063] In this manner, any user may dynamically be added or removed from a charging policy as well as being moved from one charging policy to another.

[00064] Embodiments herein also relate to a method performed by a node in a communication network associated with an application, for charging of

communication sessions with the application when such a communication session is being initiated by a user. Embodiments of such a method will now be described with reference to figures 2a-2c.

[00065] Figure 2a illustrates the method 200 comprising receiving 210 a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The method 200 also comprises recognising 220 that a communication session is initiated by a user on the list; and generating 230 a second indication of the charging policy to be applied with respect to the user for the initiated communication session. The method further comprises transmitting 240 the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[00066] When the node in the communication network first receives the first indication comprising the list of user identifiers of users for which a charging policy is to be applied from the application, the node (hereinafter also referred to as the network node) stores the list of users, i.e. list of user identities identifying respective user, so that it may subsequently recognise whether a communication session to the application is initiated by a user on the list for the charging policy, wherein the charging policy shall apply; or the communication session to

application is initiated by user not on the list for the charging policy. The charging policy in question valid for the user on the list may also be indicated by the received first indication as described and exemplified above, or indicated separately in another way. [00067] Once a user from the list initiates a communication session to the application, the network node will, e.g. upon reception of a connection request message, invite message or the like, recognise that the communication session is initiated by a user on the received list. Consequently, the cost for this session is to be charged, according to the charging policy, wherein the network node generates the second indication of the charging policy to be applied with respect to the user for the initiated communication session. The second indication comprises the content from the first indication described above, i.e. the mentioned list, which is associated with the mentioned user(s) of the list and the charging policy. The network node may then transmit the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the second indication, i.e. according to the charging policy comprised in the second indication.

[00068] Reverting to the simplified and illustrative example above, assume the network node receives the first indication informing the network node that charging policy A is to be applied if a communication session is initiated by any of users a1 , a2 or a3. The network node stores this information and when e.g. user a2 subsequently initiates a communication session to the application, the network node recognises that a2 is associated with charging policy A, wherein the network node may generate and transmit the second indication to the charging system, e.g. a node in the charging system or a charging function. The second indication informs the node in the charging system or the charging function that this communication session should be charged according to the indicated charging policy A, which entails the application being charged for the cost of the

communication session. User a2 should accordingly not be charged.

[00069] The method performed by the node in the communication network associated with the application has the same and/or similar advantages as the method performed by the application. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[00070] The method may further comprise transmitting 250 a third indication to a communication network associated with the user initiating the communication session about the charging policy for user and the communication session, when that user is not accessible via the same communication network as the application.

[00071 ] It may be that the user and the application are not associated with the same communication network. Merely as an example, and also illustrated in figure 4b, the application 410 may be associated with a first communication network 420 and the user 440 may be associated with a second communication network 430. In such a case, each communication network may comprise or be associated with a first and second charging system 425, 435 respectively. By charging system is meant in this disclosure a charging node or a charging function, which may be implemented in one or more nodes. Generally, the charging system of, or associated with, the communication network of the originating party (user 440) is to be charged for the communication session. However, in this case, since the "general" charging policy does not apply, the communication network 430 of the user 440 needs to be informed about what charging policy applies, i.e. how shall the charging system 435 of communication network 430 charge for the

communication session initiated by the user 440. The third indicator informs the communication network 430 of what charging policy applies and how the

communication network shall charge user 430 accordingly.

[00072] Consequently, when a communication session is initiated 2 by the user 410 in (or associated with) the second communication network 430 to the application 410 in (or associated with) the first communication network 420, a respective charging session in the individual communication network may be initiated and established. In order for the charging to be correctly performed, both communication networks or both charging systems may need to be provided with the charging policy information.

[00073] Again reverting to the simplified and illustrative example, assume that the network node in the first communication network 420 receives 1a the first indication informing the network node that charging policy A is to be applied if a communication session with the application is initiated by any of users a1 , a2 or a3. The network node stores this information and when e.g. user a2 440

subsequently initiates 2 a communication session to the application 410, the network node in the first communication network 420 recognises that a2 is associated with charging policy A, wherein the network node may generate and transmit 3 the second indication to the charging system 425 of the first

communication network, e.g. a node in the charging system or a charging function. However, in this case, also the communication network 430 to which a2 belong will need to be informed when a2 initiates the communication session. Consequently, the network node, i.e. the node in the first communication network 420, generates and transmit 4 the third indication to the communication network 430 associated with the user a2 440 initiating the communication session about the charging policy for user a2 and the communication session. In this manner, both charging systems425, 435 may create charging records that correspond to each other, which in this simplified example means that the charging record of the first communication network charges the application for the cost of the communication session; and the charging record of the second communication network does not charge user a2. It shall be pointed out that in the case that the charging policy defines that the application is to be charged for a ratio or percentage of the total cost for the session, both charging systems will perform charging functions in accordance with the ratio or percentage of the charging policy.

[00074] The first, second and third indications may comprise the same

information regarding the list of user(s) and charging policy. However, the message format or protocol between the entities the respective indications are sent may be different, hence the indications are herein separated by stating first, second and third indication. [00075] The manner in which the two communication networks settle charging between them is out of the scope of this disclosure. An example is by means of a broker or broker function connected to both charging systems.

[00076] The method may still further comprise, when the communication session is terminated, transmitting 260 a termination indication to the charging system indicating the termination of the communication session

[00077] At a point in time, the session is terminated, e.g. by the application, the user or another entity. Once the communication session is terminated, the total cost for the session may be fully determined. The charging system was informed when the communication session was initiated, and now the charging system is again informed upon termination of the communication session in order to determine the total length of the communication session. It may be that the application may be charged a flat rate irrespective of the length of the

communication session or a specified amount per time unit.

[00078] The two communication networks 420 and 430 may have some sort of previously arranged agreement of how to handle charging and billing between themselves, e.g. by means of a broker. However, such agreement is out of the scope of this disclosure as stated above.

[00079] As described above, the communication network may be an IMS network.

[00080] In an example, transmitting any indication to the charging system informing the charging system of any of the events and/or informing the communication network associated with the user initiating the communication session about the charging policy for user and the communication session, when that user is not associated with the same communication network as the application is performed by the IMS network sending a SIP message to the charging system and/or the communication network associated with the user initiating the communication session, the SIP message comprising at least an information element indicating that the charging policy is to be applied to user(s) indicated in the SIP message.

[00081 ] When the communication network is an IMS network, the network node may send SIP messages to the charging system. The charging system may comprise one node, a two or more nodes, or a charging function. One node of the charging system may be connected to the network node, so that relevant information can be provided to the charging system as described herein. Further, the application and the network node may communicate by means of SIP messages, also referred to as SIP signalling.

[00082] The SIP message may comprise a SIP header and payload as described above, wherein information may be carried by an information element comprised in the SIP header or in the payload section.

[00083] Embodiments herein also relate to a method performed by a node in a charging system of a communication network associated with an application, for charging of communication sessions with the application when such a

communication session is being initiated by a user. Embodiments of such a method will now be described with reference to figures 3a and 3b.

[00084] Figure 3a illustrates the method 300 comprising receiving 310 information from the communication network, an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated

communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The method 300 further comprises determining 320 how and who to charge for the initiated communication session based on the received charging policy; and creating 330 a charging session and a charging record for the initiated communication session based on the received charging policy.

[00085] The charging system is responsible for determining who and how much to charge for communication sessions within the communication network. Generally, the charging system enforces a set of charging rules applicable to different communication sessions, users and so on.

[00086] By receiving the indication comprising information regarding at least the identity of the user, the identity of the initiated communication session, and the charging policy for the user with regard to the initiated communication session, the node in the charging system can set aside the set of charging rules that would otherwise apply and instead perform the charging according to the received information.

[00087] Again reverting to the simplified and illustrative example, assume that user a2 has initiated the communication session to the application, wherein charging policy A is to be applied meaning that the application should be charged the total cost of the communication session. The node in the charging system may then determine how (total cost) and who (the application) to charge for the initiated communication session. Consequently, the node in the charging system may thus create the charging session and a charging record accordingly.

[00088] The method performed by the node in the charging system of the communication network has the same and/or similar advantages as the individual methods performed by the application and the node in the communication network respectively. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[00089] The method may further comprise receiving 340 a termination indication from the communication network, about a termination of the communication session; and closing 350 the charging session and updating 355 the charging record based on the received charging policy.

[00090] As described above, at a point in time the session is terminated. When that happens, the node in the charging system will receive the termination indication from the communication network. The node in the charging system may consequently determine the total length in time of the communication session and the total cost of the communication session. The node in the charging system may then update the charging record accordingly and close the charging session.

[00091 ] Also as described above, the communication network may be an IMS network.

[00092] When the communication network is an IMS network, the node in the charging system will receive the indications from the network node by means of SIP messages as described above.

[00093] In this disclosure, the application is sometimes illustrated and described as a separate entity for reasons of simplicity and illustration of the respective methods described above. It is pointed out that the application may be

implemented in one or more nodes or devices in a distributed fashion, which node(s) or device(s) is/are either connected to the communication network or comprised in the communication network.

[00094] Figures 4a and 4b are signalling diagram illustration the solution described above, the solution comprising the respective method performed by respective application/node. In figure 4a, the actions taken by the application 410, the communication network A 420, and the charging system A 425 are

schematically illustrated. The same actions are taken by the same entities in figure 4b but are left out for simplicity reasons; only additional actions due to the user 440 and the application 410 not being accessible via the same

communication network are illustrated in figure 4b. Figure 4a and 4b illustrate 1 the application 410 determining, one or more users for which a charging policy is to apply when initiating a communication session with the application; 2 generating a first indication of the charging policy to be applied with respect to the user(s), and transmitting 3a the indication to a node of the communication network 420, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy. The node in the communication network 420 may optionally transmit a response 3b back to the application in response to receiving the first indication from the application, the first indication the a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application.

[00095] Although not illustrated in the figures, the node of the communication network 420 may store the received information from the application 410. As a point in time after, a user 440 being on the list for which the charging policy is to apply initiates 4 a communication session with the application 410. The node of the communication network 420 recognises 5 that the communication session is initiated by user 440 on the list, generates 7 a second indication of the charging policy to be applied with respect to the user 440 for the initiated communication session, and transmitting 8 the second indication to a charging system 425 of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[00096] Figure 4b illustrates the case in which the user 440 is not accessible via the same communication network as the application 420. Instead the user 440 is accessible via communication network 430. The node of communication network 420 then transmits 9 a third indication to the communication network 430 associated with the user 440 initiating the communication session about the charging policy for the user 440 and the communication session. In this manner, the communication network 430 may inform 10 its charging system 435 about the charging policy for the user 440 and the communication session initiated by the same.

[00097] The communication session is then ongoing 15 for a while and may comprise transmissions of a plurality of signals between some or all nodes/entities illustrated in the figures. At a point in time, the communication session is terminated. When this happens, the node in the communication network 420 transmits 16 a termination indication to the charging system 425 indicating the termination of the communication session. In the case in which the user 440 is not accessible via the same communication network as the application 420, the node in the communication network 430 transmits 18 a termination indication to the charging system 435 indicating the termination of the communication session.

[00098] Upon reception of the transmitted indication 8 (and/or 10) from the communication network, the indication comprising information regarding at least an identity of the user 440, an identity of the initiated communication session, and the charging policy for the user 440 with regard to the initiated communication session, the charging system/node/function 425 (and/or 435) may determine 11 and/or 13 how and who to charge for the initiated communication session based on the received charging policy, and create 12 and/or 14 a charging session and a charging record for the initiated communication session based on the received charging policy,

[00099] Upon reception of the transmitted indication 16 (and/or 18) from the communication network about the termination of the communication session, the charging system/node/function 425 (and/or 435) may close 17 and/or 19 the charging session and update the charging record based on the received charging policy.

[000100] The solution will now be described by means of example, wherein the communication network is an IMS communication network. In an IMS

communication network, a business application may use APIs provided by the operator network for their contextual communication (e.g. health service sending reminder messages, or IT support answering video calls from customers, call centres, etc.).

[000101 ] Open Mobile Alliance, OMA, defines standard APIs to expose e.g. TelCo capabilities to business applications. The capabilities may be exposed directly by the operator or by intermediate companies. These companies may have agreements with different operators and may provide proprietary APIs.

[000102] There are some companies providing "Communication as a Service" API-s. They provide API-s and Software Development Kits, SDKs, to the developers of business applications. Application developers may focus on the core business of the company (e.g. car rental, health care, restaurant, etc.) and by simply invoking an API may use the communication services from the operator.

[000103] The OMA API program provides standardised interfaces to the communication services provided by the operator. Some API-s to consider for this solution are: "Third Party Call [REST_NetAPI_3PC]"; "Call Notification

[REST_NetAPI_CallNotif]"; and "Audio Call [REST_NetAPI_AudioCall]".

[000104] The Ericsson Multimedia Telephony Application Server, MTAS, is a high-performing carrier class application server for voice and multimedia applications. The MTAS node may partially implement some Parlay-X API. Parlay- X API is a precursor of the OMA API that is also used to expose telecom network capabilities.

• Call Direction interface is a subset of the Parley X Call Notification API

[3GPP TS 29.199-03]. Call Direction makes it possible to temporarily break out to an external application server during call setup. The external application server is able to receive different call related parameters as input for its service execution. The external application server (also called Parlay-X AS or VAS server) will based on the input information received from MTAS plus from possible other external interfaces execute one or more services and then return control to MTAS. The VAS server is able to influence the continued call handling in MTAS by for example instruct MTAS to reroute the call to a new destination or terminate the call.

• Third Party Call Interface is a subset of the Parley X Third Party Call API

[3GPP TS 29.199-02]. Third Party Call interface can for instance be used for a click to dial use-case where the VAS server can request MTAS to initiate a session on behalf of a user. It is also possible for the VAS server to get the session status for the initiated call as well as order termination of the session.

[000105] A problem with existing mechanisms (OMA API or proprietary solutions) is that none of them provide a full global flexible toll-free number solution. Instead it relies on the toll free solution provided by the operator.

[000106] A toll-free telephone number is a telephone number that is free for the calling party. They are special numbers with a well-known prefix. These are associated with other problems or drawbacks. When the company is international the toll-free number may be called from abroad. The calling party shouldn't be charged but it is, since Universal International Freephone Service, UIFS, is not globally deployed, (agreements among countries needed). Problem with video part of the all. Some operators have decided to charge the video part of a video call as data. That is when the user calls to a toll-free number; the video part of the call is still billed to him. It will be deducted from his data bucket. The business cannot change the charging model without changing the phone number.

[000107] The solution described herein provides a flexible and global free toll number mechanism to business applications via a programmatic API. The solution may be illustrated with the following non-limiting example:

• The company buys a regular number. Let ^' s say the company wants this number to be toll-free for the first 6 months (special offer). Users will not pay for the calls made to that number but the company shall.

• The company subscribes to notification to the network. When someone calls the company number, the business application is contacted. At this point the application must indicate to the network whether it ^' s a toll free call or not. This may be done programmatically (a new parameter in the existing API (e.g. in OMA it would be the HTTP POST direction

subscription API)

• When a call is made to that number the application handles the call. It executes the business related logic: contacting the right operator, or sales person, or IT support, adding video media, putting the call in a queue, etc. • The IMS network includes the indication about whether the call is toll free or not in the SIP signalling (i.e. a new SIP header). The IMS nodes generate charging records (new Diameter Attribute-Value Pairs, AVPs) including this indication.

• The charging system zero-rates the Call Detail Records, CDR-s,

associated with the user and adds the cost to the bill for the business. The business will therefore pay for the cost of the telephone number, for the usage of the API and also for the cost of the user calls.

• If the used service is a video call, the video part of the call will also be paid by the company. I.e. the data bucket of the user is not impacted.

• If the call is made from abroad, the indication shall traverse the Network to Network Interface, NNI, in the SIP signalling. Arrangement can be made later on between operators.

• After 6 months, the company will indicate the network that it ^' s not a toll free call any longer. No headers will be included in SIP and the default charging model principles will apply. This way typically the users will pay for their calls.

[000108] The solution is applicable globally and not dependent on the prefixes but on the NNI agreements. The numbers may be regular. The business may have "vanity" numbers, easier to remember. The business may change the charging model for its application, programnnatically and anytime decide whether the phone is toll-free or not without changing the phone number (of course it should inform its customers). The business can change the charging model for its application, per subscriber, using the same phone number. E.g. premium users, special offers etc.

[000109] Reverting to figures 4a and 4b, wherein the communication networks A and B, having reference numbers 420 and 430 are IMS communication networks, the business application subscribes programnnatically (OMA API) (e.g. via a broker, which is not shown in the figures) to call events related to a particular business customer. It also indicates to the operator (and/or the broker), with a new parameter (information element), that the business will take the cost of the call for that user. With "the operator" is meant the communication network A.

[0001 10] The communication network A having reference number 420 comprises a node as described above in conjunction with figures 1 a-3b, and/or a broker, wherein the node or the broker may be a SIP Application Server, AS. The SIP AS is triggered when an originating (outgoing) or terminating (incoming) call involves the business number.

[0001 1 1 ] Based on the SIP header, the originating IMS nodes add an element in the charging records for that user so the charging system zero-rates the call. The operator may bill the broker according to their commercial agreement. The broker may bill the business application according to their commercial

agreement.

[0001 12] The solution provides a flexible and global free toll number mechanism to business applications e.g. via a programmatic API, complementing the communication exposure API (standard OMA API or other proprietary APIs). This indication traverses the IMS network in the SIP signalling and it ^' s sent to the charging system. The charging system charges the business application for the calls made by the user, overriding the default operator charging model. The business application may therefore apply a different charging model over the time, or per subscriber, without changing the phone number.

[0001 13] Figure 4c is a schematic illustration of signalling diagram of a tell-free call according to prior art. The application 410 does not determine a charging policy and consequently does not identify user for which such a non-existent charging policy should apply. The application 410 does send C3a a "subscribe to call events for particular user", however without any charging policy and list of users for which it shall apply. User 440 dials a toll-free number associated with the application, wherein the cost for the call is predetermined to be charged to the application 410. The user 440 thus initiates C4 a communication session with the application 410.The communication network 420 does not recognise that the user is on the list since there is no list. Instead, communication network (i.e. a node therein) informs its charging system 425 about the session and the user initiating the session, wherein the charging system 425 may create C12 a charging record and charging session based on the toll-free number, wherein the application 410 is to be charged for the cost of the communication session. The communication network does not send a specific charging policy for the user since there is none. The communication session is ongoing C15 and is at a point in time terminated. Upon termination, the communication network 420 informs C16 the charging system 425 about the termination of the session again without including any sort of charging policy for the user 440, wherein the charging system 425 may close C17 the charging session and update the charging record according to the called number being a toll-free number.

[0001 14] Embodiments herein also relate to a node comprising an application accessible via a communication network for charging of services offered by the application to users. Embodiments of such a node will now be described with reference to figures 5 and 6. The node has the same technical features, objects and advantages as the method performed by the application described above. The node comprising the application will therefore be described only in brief in order to avoid unnecessary repetition.

[0001 15] Figures 5 and 6 illustrate the node (500, 600) comprising the

application being configured for: determining, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application; and for generating an indication of the charging policy to be applied with respect to the user. The node comprising the application is further configured for transmitting the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the

communication session is to be redirected according to the charging policy.

[0001 16] The node 500, 600 comprising the application may be realised or implemented in different ways. One exemplifying implementation, or realisation, is illustrated in figure 5. Figure 5 illustrates the node 500 comprising a processor 521 and memory 522, the memory comprising instructions, e.g. by means of a computer program 523, which when executed by the processor 521 causes the node 500 comprising the application to determine, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application; and to generate an indication of the charging policy to be applied with respect to the user. The memory may further comprise instructions, which when executed by the processor causes the node 500 comprising the application to transmit the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy.

[0001 17] Figure 5 also illustrates the node 500 comprising a memory 510. It shall be pointed out that figure 5 is merely an exemplifying illustration and memory 510 may optionally, be a part of the memory 522 or be a further memory of the node 500 comprising the application. The memory may for example comprise

information relating to the node 500, to statistics of operation of the node 500, just to give a couple of illustrating examples. Figure 5 further illustrates the node 500 comprising processing means 520, which comprises the memory 522 and the processor 521 . Still further, figure 5 illustrates the node 500 comprising a communication unit 530. The communication unit 530 may comprise an interface through which the node 500 communicates with other nodes, servers, wireless devices or entities of the communication network. Figure 5 also illustrates the node 500 comprising further functionality 540. The further functionality 540 may comprise hardware of software necessary for the node 500 comprising the application to perform different tasks that are not disclosed herein.

[0001 18] Another implementation, or realisation, is illustrated in figure 6. Figure 6 illustrates the node 600 comprising a determining unit 603 for determining, one or more users for which a charging policy is to apply when initiating a

communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application. The node 600 further comprises a generating unit 604 for generating an indication of the charging policy to be applied with respect to the user. Still further, the node 600 comprises a

transmitting unit 605 for transmitting the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy.

[0001 19] In figure 6, the application 600 is also illustrated comprising a communication unit 601 . Through this unit, the application 600 is adapted to communicate with other nodes and/or entities in the communication network. The communication unit 601 may comprise more than one receiving arrangement. For example, the communication unit 601 may be connected to both a wire and an antenna, by means of which the application 600 is enabled to communicate with other nodes and/or entities in the communication network. Similarly, the communication unit 601 may comprise more than one transmitting arrangement, which in turn are connected to both a wire and an antenna, by means of which the application 600 is enabled to communicate with other nodes and/or entities in the communication network. The application 600 further comprises a memory 502 for storing data. Further, the application 600 may comprise a control or processing unit (not shown) which in turn is connected to the different units 603-605. It shall be pointed out that this is merely an illustrative example and the application 600 may comprise more, less or other units or modules which execute the functions of the application 600 in the same manner as the units illustrated in figure 6.

[000120] It should be noted that figure 6 merely illustrates various functional units in the application 600 in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the application 600 and the functional units. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the application 600. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of application 600 as set forth in the claims.

[000121 ] The node comprising the application has the same possible advantages as the method performed by the application. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[000122] According to an embodiment, the node 500, 600 comprising the application is further configured for transmitting of the indication to the network node of the communication network by sending a list of user identifiers of the one or more users for which the indicated charging policy apply to the communication network.

[000123] According to yet an embodiment, the communication network is an IMS network (also referred to as an IMS communication network herein).

[000124] According to still an embodiment, the node 500, 600 comprising the application is configured for transmitting of the indication to the network node of the communication network by sending a SIP message comprising at least an information element indicating that the charging policy is to be applied to users indicated in the SIP message.

[000125] According to a further embodiment, the node 500, 600 comprising the application is configured for determining of one or more users for which the charging policy is to apply when initiating the communication session with the application on a per charging policy basis, wherein different charging policies may apply to different users. [000126] According to another embodiment, the indication is indicative of a charging policy comprising one or more of (a) the application will be charged the total cost for the communication session; (b) the application will be charged a ratio of the total cost for the communication session; and (c) the application will be charged a fixed amount for the communication session, wherein the user will have to be charged for any additional cost for the communication session.

[000127] According to yet an embodiment, the node 500, 600 comprising the application is further configured for updating which users for which the charging policy is to apply, anew generating an indication of the charging policy to be applied with respect to the user, and transmitting the indication to a network node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy.

[000128] Embodiments herein also relate to a node in a communication network associated with an application, for charging of communication sessions with the application when such a communication session is being initiated by a user.

Embodiments of such a node will now be described with reference to figures 7 and 8. The node in the communication network has the same technical features, objects and advantages as the method performed by the node in the

communication network described above. The node in the communication network will therefore be described only in brief in order to avoid unnecessary repetition.

[000129] Figures 7 and 8 illustrate the node 700, 800 in the communication network being configured for receiving a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node in the communication network is also configured for recognising that a communication session is initiated by a user on the list; and for generating a second indication of the charging policy to be applied with respect to the user for the initiated communication session. The node in the communication network is further configured for transmitting the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[000130] The node 700, 800 in the communication network may be realised or implemented in different ways. One exemplifying implementation, or realisation, is illustrated in figure 7. Figure 7 illustrates the node 700 in the communication network comprising a processor 721 and memory 722, the memory comprising instructions, e.g. by means of a computer program 723, which when executed by the processor 721 causes the node 700 in the communication network to receive a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application; to recognise that a communication session is initiated by a user on the list; and to generate a second indication of the charging policy to be applied with respect to the user for the initiated communication session. The memory may further comprise instructions, which when executed by the processor causes the node 700 in the communication network to transmit the second indication to a charging system of the

communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[000131 ] Figure 7 also illustrates the node 700 comprising a memory 710. It shall be pointed out that figure 7 is merely an exemplifying illustration and memory 710 may optionally, be a part of the memory 722 or be a further memory of the node 700 in the communication network. The memory may for example comprise information relating to the node 700, to statistics of operation of the node 700, just to give a couple of illustrating examples. Figure 7 further illustrates the node 700 comprising processing means 720, which comprises the memory 722 and the processor 721 . Still further, figure 7 illustrates the node 700 comprising a communication unit 730. The communication unit 730 may comprise an interface through which the node 700 communicates with other nodes, servers, wireless devices or entities of the communication network. Figure 7 also illustrates the node 700 comprising further functionality 740. The further functionality 740 may comprise hardware of software necessary for the node 700 in the communication network to perform different tasks that are not disclosed herein.

[000132] Another implementation, or realisation, is illustrated in figure 8. Figure 8 illustrates the node 800 in the communication network comprising a receiving unit 803 for receiving a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node 800 further comprises a recognising unit 804 for recognising that a communication session is initiated by a user on the list; and a generating unit 805 for generating a second indication of the charging policy to be applied with respect to the user for the initiated communication session. Still further, the node 800 comprises a transmitting unit 806 for transmitting the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[000133] In figure 8, the node 800 in the communication network is also illustrated comprising a communication unit 801 . Through this unit, the node 800 in the communication network is adapted to communicate with other nodes and/or entities in the communication network. The communication unit 801 may comprise more than one receiving arrangement. For example, the communication unit may be connected to both a wire and an antenna, by means of which the node 800 in the communication network is enabled to communicate with other nodes and/or entities in the communication network. Similarly, the communication unit 801 may comprise more than one transmitting arrangement, which in turn are connected to both a wire and an antenna, by means of which the node 800 in the

communication network is enabled to communicate with other nodes and/or entities in the communication network. The node 800 in the communication network further comprises a memory 802 for storing data. Further, the node 800 in the communication network may comprise a control or processing unit (not shown) which in turn is connected to the different units 803-806. It shall be pointed out that this is merely an illustrative example and the node 800 in the communication network may comprise more, less or other units or modules which execute the functions of the node 800 in the communication network in the same manner as the units illustrated in figure 8.

[000134] It should be noted that figure 8 merely illustrates various functional units in the node 800 in the communication network in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the node 800 in the communication network and the functional units. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer- readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the node 800 in the communication network. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the node 800 in the communication network as set forth in the claims.

[000135] The node in the communication network has the same possible advantages as the method performed by the node in the communication network. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[000136] According to an embodiment, the node 700, 800 in the communication network is further configured for transmitting a third indication to a communication network associated with the user initiating the communication session about the charging policy for user and the communication session, when that user is not accessible via the same communication network as the application. [000137] According to yet an embodiment, the node 700, 800 in the communication network is further configured for, when the communication session is terminated, transmitting a termination indication to the charging system indicating the termination of the communication session.

[000138] According to still an embodiment, the communication network is an IMS network.

[000139] According to another embodiment, transmitting any indication to the charging system informing the charging system of any of the events and/or informing the communication network associated with the user initiating the communication session about the charging policy for user and the communication session, when that user is not associated with the same communication network as the application is performed by the IMS network sending a SIP message to the charging system and/or the communication network associated with the user initiating the communication session, the SIP message comprising at least an information element indicating that the charging policy is to be applied to user(s) indicated in the SIP message.

[000140] Embodiments herein also relate to a node in a charging system of a communication network associated with an application, for charging of

communication sessions with the application when such a communication session is being initiated by a user. Embodiments of such a node will now be described with reference to figures 9 and 10. The node in the charging system has the same technical features, objects and advantages as the method performed by the node in the charging system described above. The node in the charging system will therefore be described only in brief in order to avoid unnecessary repetition.

[000141 ] Figures 9 and 10 illustrate the node 900, 1000 in the charging system being configured for receiving information from the communication network, by means of an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node in the charging system is further configured for determining how and who to charge for the initiated communication session based on the received charging policy; and for creating a charging session and a charging record for the initiated communication session based on the received charging policy.

[000142] The node 900, 1000 in the charging system may be realised or implemented in different ways. One exemplifying implementation, or realisation, is illustrated in figure 9. Figure 9 illustrates the node 900 in the charging system comprising a processor 921 and memory 922, the memory comprising

instructions, e.g. by means of a computer program 923, which when executed by the processor 921 causes the node 900 in the charging system to receive information from the communication network, by means of an indication

comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application;. The memory may further comprise instructions, which when executed by the processor causes the node 900 in the charging system to determine how and who to charge for the initiated

communication session based on the received charging policy; and to create a charging session and a charging record for the initiated communication session based on the received charging policy.

[000143] Figure 9 also illustrates the node 900 comprising a memory 910. It shall be pointed out that figure 9 is merely an exemplifying illustration and memory 910 may optionally, be a part of the memory 922 or be a further memory of the node 900 in the communication network. The memory may for example comprise information relating to the node 900, to statistics of operation of the node 900, just to give a couple of illustrating examples. Figure 9 further illustrates the node 900 comprising processing means 920, which comprises the memory 922 and the processor 921 . Still further, figure 9 illustrates the node 900 comprising a communication unit 930. The communication unit 930 may comprise an interface through which the node 900 communicates with other nodes, servers, wireless devices or entities of the communication network. Figure 9 also illustrates the node 900 comprising further functionality 940. The further functionality 940 may comprise hardware of software necessary for the node 900 in the charging system to perform different tasks that are not disclosed herein.

[000144] Another implementation, or realisation, is illustrated in figure 10. Figure 10 illustrates the node 1000 in the charging system comprising a receiving unit 1003 for receiving information from the communication network, by means of an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The node 1000 further comprises a determining unit 1004 for determining how and who to charge for the initiated communication session based on the received charging policy and a creating unit 1005 for creating a charging session and a charging record for the initiated communication session based on the received charging policy.

[000145] In figure 10, the node 1000 in a charging system of the communication network is also illustrated comprising a communication unit 1001 . Through this unit, the node 1000 in the charging system is adapted to communicate with other nodes and/or entities in the communication network. The communication unit 1001 may comprise more than one receiving arrangement. For example, the

communication unit may be connected to both a wire and an antenna, by means of which the node 1000 in the charging system is enabled to communicate with other nodes and/or entities in the communication network. Similarly, the communication unit 1001 may comprise more than one transmitting arrangement, which in turn are connected to both a wire and an antenna, by means of which the node 1000 in the charging system is enabled to communicate with other nodes and/or entities in the communication network. The node 1000 in the charging system further comprises a memory 1002 for storing data. Further, the node 1000 in the charging system may comprise a control or processing unit (not shown) which in turn is connected to the different units 1003-1005. It shall be pointed out that this is merely an illustrative example and the node 1000 in the charging system may comprise more, less or other units or modules which execute the functions of the node 1000 in the charging system in the same manner as the units illustrated in figure 10.

[000146] It should be noted that figure 10 merely illustrates various functional units in the node 1000 in the charging system in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the node 1000 in the charging system and the functional units.

Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the node 1000 in the charging system. The instructions executable by the computing system and stored on the computer- readable medium perform the method steps of the node 1000 in the charging system as set forth in the claims.

[000147] The node in the charging system has the same possible advantages as the method performed by the node in the charging system. One possible advantage is that different charging policies may dynamically be associated with different users as opposed to having a toll-free number which is static and all users calling that number won't be charged. Another possible advantage is that the telephone numbers may be regular numbers identifying the calling user/party for which the charging policy is to apply. Yet another possible advantage is that the charging policy can be dynamic and can easily be changed with respect to individual users. Still a further possible advantage is that the solution is applicably on a global scale irrespective of country prefixes.

[000148] According to an embodiment, the node 900, 1000 in the charging system is further configured for receiving a termination indication from the communication network, about a termination of the communication session; and for closing the charging session and updating the charging record based on the received charging policy.

[000149] According to yet an embodiment, the communication network is an IMS network.

[000150] According to still an embodiment, the received indicator is received for IMS nodes involved in the communication session by means of SIP protocol.

[000151 ] Figure 11 schematically shows an embodiment of an arrangement 1 100 in a node comprising an application 600. Comprised in the arrangement 700 in the node comprising the application 600 are here a processing unit 1 106, e.g. with a Digital Signal Processor, DSP. The processing unit 1 106 may be a single unit or a plurality of units to perform different actions of procedures described herein. The arrangement 1 100 of the application 600 may also comprise an input unit 1 102 for receiving signals from other entities, and an output unit 1 104 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of figure 6, as one or more interfaces 601 .

[000152] Furthermore, the arrangement 1 100 in the node 600 comprising the application comprises at least one computer program product 1 108 in the form of a non-volatile memory, e.g. an Electrically Erasable Programmable Read-Only Memory, EEPROM, a flash memory and a hard drive. The computer program product 1 108 comprises a computer program 1 1 10, which comprises code means, which when executed in the processing unit 1 106 in the arrangement 1 100 in the node 600 comprising the application causes the node 600 comprising the application to perform the actions e.g. of the procedure described earlier in conjunction with figures 1a and 1b.

[000153] The computer program 1 1 10 may be configured as a computer program code structured in computer program modules 1 1 10a-1 1 10e. Hence, in an exemplifying embodiment, the code means in the computer program of the arrangement 1 100 in the node 600 comprising the application comprises a determining unit, or module, for determining, one or more users for which a charging policy is to apply when initiating a communication session with the application, wherein the charging policy entails the application being charged for at least part of a cost for the communication session between the user and the application. The computer program further comprises a generating unit, or module, for generating an indication of the charging policy to be applied with respect to the user(s); and a transmitting unit, or module, for transmitting the indication to a node of the communication network, thereby enabling identification of the user as a user for which charging of the communication session is to be redirected according to the charging policy..

[000154] The computer program modules could essentially perform the actions of the flow illustrated in figures 1a and 1 b, to emulate the application 600. In other words, when the different computer program modules are executed in the processing unit 1 106, they may correspond to the units 603-605 of figure 6.

[000155] Figure 12 schematically shows an embodiment of an arrangement 1200 in a node 800 in a communication network. Comprised in the arrangement 1200 in the node 800 are here a processing unit 1206, e.g. with a DSP. The processing unit 1206 may be a single unit or a plurality of units to perform different actions of procedures described herein. The arrangement 1200 in the node 800 may also comprise an input unit 1202 for receiving signals from other entities, and an output unit 1204 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of figure 8, as one or more interfaces 801 .

[000156] Furthermore, the arrangement 1200 in the node 800 comprises at least one computer program product 1208 in the form of a non-volatile memory, e.g. an EEPROM, a flash memory and a hard drive. The computer program product 1208 comprises a computer program 1210, which comprises code means, which when executed in the processing unit 1206 in the arrangement 1200 in the node 800 in the communication network causes the node 800 to perform the actions e.g. of the procedure described earlier in conjunction with figures 2a-2c. [000157] The computer program 1210 may be configured as a computer program code structured in computer program modules 1210a-1210e. Hence, in an exemplifying embodiment, the code means in the computer program of the arrangement 1200 in the node 800 comprises a receiving unit, or module, for receiving a first indication from the application, the first indication comprising a list of user identifiers of users for which a charging policy is to be applied, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The computer program further comprises a recognising unit, or module, for recognising that a communication session is initiated by a user on the list. The computer program further comprises a generating unit, or module, for generating a second indication of the charging policy to be applied with respect to the user for the initiated communication session; and a transmitting unit, or module for transmitting the second indication to a charging system of the communication network, thereby enabling the charging system to charge for the communication session according to the indication.

[000158] The computer program modules could essentially perform the actions of the flow illustrated in figures 2a-2c, to emulate the node 800 in the communication network. In other words, when the different computer program modules are executed in the processing unit 1206, they may correspond to the units 803-806 of figure 8.

[000159] Figure 13 schematically shows an embodiment of an arrangement 1300 in a node 1000 in a charging system of a communication network.

Comprised in the arrangement 1300 in the node 1000 are here a processing unit 1306, e.g. with a DSP. The processing unit 1306 may be a single unit or a plurality of units to perform different actions of procedures described herein. The

arrangement 1300 in a node 1000 may also comprise an input unit 1302 for receiving signals from other entities, and an output unit 1304 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of figure 10, as one or more interfaces 1001 . [000160] Furthermore, the arrangement 1300 in a node 1000 comprises at least one computer program product 1308 in the form of a non-volatile memory, e.g. an EEPROM, a flash memory and a hard drive. The computer program product 1308 comprises a computer program 1310, which comprises code means, which when executed in the processing unit 1306 in the arrangement 1300 in the node 1000 in the charging system in the communication network causes the node 1000 to perform the actions e.g. of the procedure described earlier in conjunction with figures 3a and 3b.

[000161 ] The computer program 1310 may be configured as a computer program code structured in computer program modules 1310a-1310e. Hence, in an exemplifying embodiment, the code means in the computer program of the arrangement 1300 in the node 1000 comprises a receiving unit, or module, for from the communication network, an indication comprising information regarding at least an identity of a user, an identity of an initiated communication session, and a charging policy for the user with regard to the initiated communication session, wherein the charging policy entails the application being charged at least part of a cost for a communication session between the user and the application. The computer program further comprises a determining unit, or module, for

determining how and who to charge for the initiated communication session based on the received charging policy; and a creating unit, or module, for creating a charging session and a charging record for the initiated communication session based on the received charging policy.

[000162] The computer program modules could essentially perform the actions of the flow illustrated in figures 3a and 3b, to emulate the node 1000 in the charging system of the communication network. In other words, when the different computer program modules are executed in the processing unit 1306, they may correspond to the units 1003-1005 of figure 10.

[000163] Although the code means in the respective embodiments disclosed above in conjunction with figures 6, 8 and 10 are implemented as computer program modules which when executed in the respective processing unit causes the application, the node in the communication network and the node in the charging system in the communication network respectively to perform the actions described above in the conjunction with figures mentioned above, at least one of the code means may in alternative embodiments be implemented at least partly as hardware circuits.

[000164] The processor may be a single Central Processing Unit, CPU, but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits, ASICs. The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a computer readable medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-Access Memory RAM, Read-Only Memory, ROM, or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories within the application, the node in the communication network and the node in the charging system in the communication network respectively.

[000165] It is to be understood that the choice of interacting units, as well as the naming of the units within this disclosure are only for exemplifying purpose, and nodes suitable to execute any of the methods described above may be configured in a plurality of alternative ways in order to be able to execute the suggested procedure actions.

[000166] It should also be noted that the units described in this disclosure are to be regarded as logical entities and not with necessity as separate physical entities.

[000167] While the embodiments have been described in terms of several embodiments, it is contemplated that alternatives, modifications, permutations and equivalents thereof will become apparent upon reading of the specifications and study of the drawings. It is therefore intended that the following appended claims include such alternatives, modifications, permutations and equivalents as fall within the scope of the embodiments and defined by the pending claims.