WO2023219538A1

WO2023219538A1 - Methods and apparatus for announcement-related charging control

Info

Publication number: WO2023219538A1
Application number: PCT/SE2022/050467
Authority: WO
Inventors: Robert TÖRNKVIST; Jan Dahl
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-05-12
Filing date: 2022-05-12
Publication date: 2023-11-16

Abstract

Information exchanged between a Charging Trigger Function (CTF) (18) of a communication network (12) and a Charging Function (CHF) (16) of the network (12) includes playback results indicating playback results for an announcement monitored by the CTF (18), with such information advantageously supporting, for example, playback failure handling by the CHF (16). In at least one embodiment, the CHF (16) configures one or more aspects of announcement monitoring by the CTF (18), such as by initiating the announcement monitoring or configuring the CTF (18) to report announcement event information at least for certain types of announcements.

Description

METHODS AND APPARATUS FOR

ANNOUNCEMENT-RELATED CHARGING CONTROL

TECHNICAL FIELD

Methods and apparatus provide for the exchange of information between a Charging Trigger Function (CTF) of a communication network and a Charging Function (CHF) of the network, regarding playback results for called or calling party announcements.

BACKGROUND

A Charging Trigger Function (CTF) of a communication network sends or initiates the sending of announcements towards one or both of a calling party and called party involved in a call supported by a network node that includes the CTF, such as an Internet Multimedia Subsystem (IMS) node. See Technical Specification (TS) 32.281 vl7.1.0 by the Third Generation Partnership Project (3GPP) for example details regarding announcement services and see 3GPP TS 32.240 V17.5.0 for example details regarding charging architecture and charging management.

The CHF or another entity within the charging system can instruct a CTF to send an announcement towards a user during a call, e.g., to give a low-credit warning. In this context, the CTF supports a charging session associated with a call between a calling party and a called party, such as a call supported by an Internet Multimedia Subsystem (IMS). For announcement playback for the calling party, the CTF places the called party on hold, plays the announcement to the calling party, and then resumes the call. The hold/resume actions are performed using e.g., Session Initiation Protocol (SIP) messaging, including a SIP re-INVITE or UPDATE message.

There are further capabilities described in 3GPP TS 32.281, which allow the CHF or other charging-system node to order the CTF to play different announcements to both the calling and called parties. Further capabilities include requesting a delay of the playback based on time and indicating whether quota consumption should be counted during the announcements. If multiple announcements are ordered at the same time, the charging system may indicate a playback order for the multiple announcements. Still further, announcements may include interaction with the involved party or parties. For instance, the calling party may be prompted to confirm that they would like to replenish credit in their subscriber account. Although announcement playback fulfills important functions for parties involved in calls supported by the communication network, such as warning callers of low credit or other account issues, a number of challenges remain unaddressed in the context of announcements. For example, current implementations supporting announcement playback do not provide mechanisms for a CTF for return information about announcement playback events to the CHF or charging system.

SUMMARY

Information exchanged between a Charging Trigger Function (CTF) of a communication network and a Charging Function (CHF) of the network includes playback results indicating playback results for an announcement monitored by the CTF, with such information advantageously supporting, for example, playback failure handling by the CHF. In at least one embodiment, the CHF configures one or more aspects of announcement monitoring by the CTF, such as by initiating announcement monitoring by the CTF or configuring the CTF to report announcement event information at least for certain types of announcements.

An example embodiment comprises a CTF of a communication network, where the CTF includes communication interface circuitry configured to communicatively couple the CTF to a CHF of the communication network and processing circuitry operatively associated with the communication interface circuitry. The processing circuitry is configured to monitor playback of an announcement to one or both of a calling party and a calling party involved in a call, where a charging session between the CTF and the CHF corresponds with the call and send announcement event information towards the CHF using the charging session, the announcement event information indicating playback results for the announcement.

A related embodiment comprises a method of operation by a CTF, where the method includes (a) monitoring playback of an announcement to one or both of a calling party and a called party involved in a call, where a charging session between the CTF and a CHF of the communication network corresponds with the call, and (b) sending announcement event information towards the CHF using the charging session, the announcement event information indicating playback results for the announcement.

Another example embodiment is a CHF of a communication network. The CHF includes communication interface circuitry configured to communicatively couple the CHF to a CTF of the communication network, and processing circuitry operatively associated with the communication interface circuitry. The processing circuitry is configured to: (a) receive announcement event information reported by the CTF supporting a charging session for a call involving calling and called parties, the announcement event information indicating playback results for playback of an announcement monitored by the CTF, the announcement targeting one or both of the calling and called parties, and (b) initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure for the announcement.

A related embodiment comprises a method of operation by CHF of a communication network. The method includes the CHF receiving announcement event information reported by a CTF supporting a charging session for a call involving calling and called parties. The announcement event information indicates playback results for playback of an announcement monitored by the CTF, where the announcement targets one or both of the calling and called parties. The method further comprises initiating a failure-handling procedure responsive to the announcement event information indicating a playback failure for the announcement.

Another example embodiment comprises a system instantiated in a communication network, the system comprising a Charging Function (CHF) and a Charging Trigger Function (CTF), wherein: (a) the CTF is configured to send announcement event information to the CHF, indicating playback results for an announcement monitored by the CTF with respect to one or both of a calling party and a called party in a call for which the CTF supports a charging session, and (b) the CHF is configured to initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure.

Of course, the present invention is not limited to the above features and advantages. Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a signal flow diagram illustrating signals between a Charging Function (CHF) of a communication network and a Charging Trigger Function (CTF) of the communication network, according to an example embodiment.

Figure 2 is a signal flow diagram illustrating establishment of an example call between a calling party and a called party.

Figure 3 is a logic flow diagram illustrating a method of operation by a CHF, according to an example embodiment.

Figure 4 is a block diagram illustrating implementation details for a CHF, according to an example embodiment. Figure 5 is a block diagram illustrating example details for processing circuitry of a CHF.

Figure 6 is a block diagram illustrating implementation details for a CHF, according to another example embodiment.

Figure 7 is a logic flow diagram illustrating a method of operation by a CTF, according to an example embodiment.

Figure 8 is a block diagram illustrating implementation details for a CTF, according to an example embodiment.

Figure 9 is a block diagram illustrating example details for processing circuitry of a CTF.

Figure 10 is a block diagram illustrating implementation details for a CTF, according to another example embodiment.

Figure 11 is a block diagram of a communication network, according to an example embodiment.

Figure 12 is a block diagram of a charging system of a communication network, according to an example embodiment.

DETAILED DESCRIPTION

Figure 1 illustrates an example signal flow, where a first user device 10-1 operates as the calling party with respect to a call established between the first user device 10-1 and a second user device 10-2 operating as a called party. Here, “call” refers to a communication session and a non-limiting example of such a session is a voice call established through an Internet Multimedia Subsystem (IMS), which is not shown in the diagram.

At step 1, there is an established call between calling party and the called party, and step 2 indicates that the call is quota-controlled, meaning that seconds or other consumption units are deducted from a granted number of consumption units. For example, one or both of the calling and called parties connect via a communication network 12, such as a wireless communication network configured according to Third Generation Partnership Project (3GPP) specification. The example communication network 12 provides communicative coupling to one or more further networks 14 — e.g., an IMS network — that completes end-to-end connectivity between the calling and called parties, and the communication network 12 assesses charges to one or both parties for the connectivity.

A Charging Function (CHF) 16 of the communication network 12 grants the abovedetailed quota for consumption, based on communicating with a Charging Trigger Function (CTF) 18 of the communication network 12. There may be multiple CTFs 18 in the communication network 12 and multiple CTFs 18 may be involved in supporting a given call, with each such CTF 18 instantiated in a respective one of the network functions/nodes involved in supporting the given call. In the context of this disclosure, a CTF 18 is involved in supporting a charging session established between the CHF 16 and the CTF 18 to handle charging for a call. At step 3, in response to consumption of granted quota, or imminent exhaustion of the granted quota, the CTF 18 requests more consumption units from the CHF 16. At step 4, the CHF 16 responds with more granted units, as well as announcement information and enables a trigger for the announcement to be played, e.g., to the calling party, or the called party, or both. At step 5, the conditions for the announcement to be played are met, and at step 6 the CTF 18 puts the called party on hold and may play a hold announcement for the called party, which is shown as step 7. At steps 8, 9, and 10, the CTF 18 initiates announcement playback for the calling party.

At step 11, the CTF 18 sends a charging data request, for example, that advantageously carries announcement playback information, based on the CTF 18 monitoring the announcement playback. For example, the charging data request includes an information element (IE) or other data item that indicates announcement playback results. Particularly, the charging data request indicates whether playback was successful. At step 12, the CHF 16 returns a charging data response and at step 13 the called party is reinvited to the call, and the call continues at step 14.

At step 15, the CHF 16 processes the event announcement information conveyed to it by the CTF 18. For example, responsive to the announcement event information indicating successful playback of the announcement, the CHF 16 indicates successful playback or otherwise initiates another function in the communication network 12 to record an indication that playback was successful. Alternatively, responsive to the announcement event information indicating unsuccessful playback, the CHF 16 initiates a failure handling procedure, which in one or more embodiments includes initiating another playback attempt of the announcement.

Figure 2 is a signal flow diagram depicting example details for establishing a call such as the one at issue in the signal flow shown in Figure 1. Additional details shown in Figure 2 include illustration of a Radio Access Network (RAN) 20 included in the communication network 12, e.g., the calling party connects to the communication network 12 by establishing radio connectivity with the RAN 20. A Core Network (CN) 22 of the communication network 12 provides communication handling and connectivity to the one or more external networks 14, which may comprise an IMS 26 and one or more other networks 28, such as the Internet or the Public Switched Telephone Network (PSTN). The CHF 16 comprises part of a charging system 24 of the communication network 12.

Operations depicted in the signal flow include attachment of the calling party to the communication network 12, followed by IMS registration of the calling party and a call request originating from the calling party. The call is established following call session establishment.

With the above call examples in mind, Figure 3 illustrates a method 300 of operation by a CHF 16. Optional operations or steps of the method 300 include the CHF 16 generating (Block 302) configuration information to enable announcement event reporting by a CTF 18 and sending (Block 304) the configuration information to the CTF 18. Such operations are optional in at least one embodiment, because the CTF 18 may not need such configuration information in order to carry out announcement event reporting, or at least may not need such configuration information in some scenarios or for some kinds of announcement events.

In an example embodiment where the operations of Blocks 302 and 304 are included in the method 300, the CHF 16 includes in the configuration information at least one of: information indicating the type(s) of announcements for which event reporting is to be performed by the CTF 18, information indicating a specific announcement for which event reporting is to be performed or indicating trigger conditions for triggering announcement event reporting. As an example, such information may be sent by the CHF 16 to the CTF 18 in a charging-related messages, e.g., in an initial charging request response sent to the CTF 18 for a given call for which the CTF 18 and the CHF 16 have established or are establishing a charging session. As a particular example, the CHF 16 may enable announcement event reporting at the CTF 18 for at least some types of announcements and then disable reporting at a later time. For the duration during which reporting is enabled, the CTF 18 sends announcement event information to the CHF 16, for all or particular announcement playback attempts.

Thus, operations depicted at Block 306 of the method 300 should be understood as the CHF 16 receiving announcement event information from a particular CTF 18 for an announcement attempted during a particular call involving calling and called parties and for which the CHF 16 and the CTF 18 are involved in a charging session. The announcement event information indicates, for example, playback results. At Block 308, the CHF 16 processes the announcement event information. As an example, the CHF 16 performs a failure-handling procedure responsive to the announcement event information indicating that the announcement playback was unsuccessful. As such, the CHF 16 is informed of announcement playback results meaning that it can take remedial or other action, at least when the announcement is one of import with respect to charging or billing and the announcement event information indicates that the playback was not successful. More broadly, the announcement event processing may involve the CHF 16 recording the playback results, alerting another node in the charging system 24 or initiating communication with the party/parties targeted by the announcement, such as by initiating the sending of a Short Messaging Service (SMS) message that communicates the announcement.

The announcement event information comprises one or both of an IE indicating whether playback of the announcement was successful, or an IE indicating a time at which the playback was initiated. In more detail, in at least one embodiment, the announcement event information reported by the CTF 18 comprises a results IE that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

In embodiments where the method 300 includes the CHF 16 sending configuration information to the CTF 18 (Block 304), such sending occurs in advance of the receiving operations shown in Block 306. In at least one such embodiment, the configuration information configures an announcement-event reporting trigger to be active at the CTF 18, and the CTF 18 conditions the reporting of the announcement event information on the announcement-event reporting trigger being active — i.e., enabled. As noted, such configuration information may be included in a charging data response sent by the CHF 16 in response to the CHF 16 receiving a charging data request from the CTF 18. Note that the request and response message is sent for a particular call, but the configuration may apply globally at the CTF 18 — e.g., the configuration information may configure announcement event reporting for all calls handled by the CTF 18, although the configuration information may restrict announcement event reporting by the CTF 18 such that the CTF 18 returns announcement event information for any given announcement attempt only if one or more specific conditions are satisfied. In at least one example, the CHF 16 determines that a charging or billing related announcement needs to be played for the calling or called parties involved in a particular call, and that announcement event reporting should be performed by the CTF 18 for the announcement. Correspondingly, the CHF 16 indicates the announcement and reporting configuration to the CTF 18, e.g., in a next occurring charging data response sent from the CHF 16 to the CTF 18. That is, the CHF 16 determines that a certain type of announcement needs to be played for at least one of the parties involved in a call for which the CHF 16 is providing charging-session support, and the CHF 16 indicates the announcement to the CTF 18 and enables announcement event reporting for at least that announcement or that type of announcement, so that the CTF 18 will return announcement event information to the CHF 16 upon attempting playback of the announcement.

Thus, in one or more embodiments, the CHF 16 is configured to activate an announcement event reporting trigger at the CTF 18 that causes the CTF 18 to perform announcement event reporting for one or more announcement events at the CTF 18. Correspondingly, in at least one such embodiment, the CHF 16 is further configured to send further configuration information to the CTF 18 to deactivate the announcement-event reporting trigger at the CTF. That is, the CHF 16 may enable and disable announcement event reporting by the CTF 18, to control or limit the number of announcement event reports it receives from the CTF 18. Such capability offers several advantages, such as allowing the CHF 16 to receive announcement event information only during times when it chooses to enable such reporting, and only for particular types of announcements — e.g., important billing or charging announcements.

In one or more embodiments, the method 300 includes the CHF 16, in advance of receiving the announcement event information in Block 306, sending announcement information to the CTF 18 that comprises the announcement or otherwise indicates the announcement. The announcement information activates the announcement-event reporting at the CTF 18, thereby causing the CTF 18 to send the announcement event information corresponding to the announcement. Of course, as noted, the CHF 16 in one or more embodiments is configured to send configuration information to the CTF 18 that includes information that restricts announcement event reporting by the CTF 18 to announcements of one or more particular announcement types. Examples of such types include promotions, commercial offers, subscription warnings, low-account balance or other “need to refill account” warnings, etc. In one or more embodiments, the processing of announcement event information in Block 308 includes performing a failure-handling procedure in response to the announcement event information indicating unsuccessful playback of the announcement. For example, the CHF 16 initiates a further attempt by the CTF 18 for playback of the announcement. The failurehandling procedure in at least one embodiment comprises the CHF 16 initiating generation of an alert message for delivery to the party or parties targeted by the corresponding announcement via an alternate delivery mechanism, the party or parties targeted by the corresponding announcement being at least one of the calling party and the called party. Additionally or alternatively, the failure-handling procedure comprises the CHF 16 sending an indication of the playback failure towards another node in the communication network 12.

In at least one embodiment, in response to the announcement event information indicating successful playback of an announcement, the CHF 16 initiates recording of billingrecords data confirming playback of the announcement.

Figure 4 illustrates an example implementation of a CHF 16 comprising communication interface circuitry 30, including transmitter circuitry 32 and receiver circuitry 34, and further including processing circuitry 36 that is operatively associated with the communication interface circuitry 30. Being “operatively associated” with the communication interface circuitry 30 means that the processing circuitry 36 uses the communication interface circuitry 30 to exchange signaling with one or more other nodes or functions in the network 12, e.g., to exchange charging-related messages with one or more CTFs 18 and/or one or more other nodes in the charging system 24 of the communication network 12. The communication interface circuitry 30 comprises physical-layer circuitry for transmitting and receiving signaling over the involved wired or wireless medium and, in an example embodiment, the communication interface circuitry 30 comprises an Ethernet interface circuit or other computer data network interface.

In at least one embodiment, the processing circuitry 36 includes or is associated with storage 38, which comprises one or more types of computer-readable media. Such media stores, for example, one or more computer programs 40 and/or one or more types of configuration data 42, e.g., data indicating the type(s) of announcement events for which announcement event reporting should be activated.

The processing circuitry 36 is configured to: (a) receive announcement event information reported by a CTF 18 supporting a charging session for a call involving calling and called parties, the announcement event information indicating playback results for playback of an announcement monitored by the CTF 18, and where the announcement targets one or both of the calling and called parties; and (b) initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure for the announcement. More generally, the processing circuitry 36 is configured to carry out any one or more of the operations described for the method 300.

Consider Figure 5, for example, which illustrates an example implementation of the processing circuitry 36 / storage 38. Particularly, the processing circuitry 36 comprises one or more microprocessors 50 or other digital processing circuits that are specially adapted to perform the CHF operations described herein at least in part based on the execution of computer program instructions held in one or more memory devices 52.

Figure 6 illustrates another example implementation of a CHF 16 that is configured to carry out the operations described herein for the CHF 16. Here, the CHF 16 includes a set 600 of processing modules or units that are respectively configured to carry out various ones of the described CHF operations. Although the CHF 16 in one or more embodiments is implemented as a virtualized device in a virtualization environment, a set 600 of processing modules is realized using underlying computer resources, e.g., allocated processing and memory resources that are used to instantiate the functional logic that carries out the CHF operations described herein.

In the specific example of Figure 6, the CHF 16 includes a generating module 602 that is configured to generate configuration information for a CTF 18. The configuration information configures an announcement-event reporting trigger to be active at the CTF 18, and wherein the CTF 18 conditions the reporting of the announcement event information on the announcementevent reporting trigger being active. Further processing modules included in the set 600 of processing modules are: a sending module 604 that is configured to send the configuration information to the CTF 18; a receiving module 606 that is configured to receive announcement event information from the CTF 18; and a processing module 608 that is configured to process the announcement event information, e.g., to initiate a failure-handling procedure responsive to the announcement event information indicating an unsuccessful playback attempt.

Figure 7 illustrates a method 700 of operation by a CTF 18 of a communication network 12, according to an example embodiment. The method 700 comprises: (a) monitoring (Block 702) playback of an announcement to one or both of a calling party and a called party involved in a call, where a charging session between the CTF 18 and a CHF 16 of the communication network 12 corresponds with the call; and (b) sending (Block 704) announcement event information towards the CHF 16 using the charging session, the announcement event information indicating playback results for the announcement.

The announcement event information comprises, for example, at least one of an IE indicating whether playback of the announcement was successful and an IE indicating a time at which the playback was initiated. In at least one embodiment, the announcement event information reported by the CTF 18 comprises a results IE that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

Sending the announcement event information comprises, in at least one embodiment, sending the announcement event information conditioned on an announcement-event reporting trigger being active at the CTF 18.

In at least one embodiment, prior to monitoring the playback of the announcement, the method 700 includes the CTF 18 receiving configuration information from the CHF 16 or from another node in the communication network 12. The configuration information activates the announcement-event reporting trigger, which can be understood as activating the announcementmonitoring function of the CTF 18. Receiving the configuration information comprises, for example, the CTF 18 receiving the configuration information in a charging data response received from the CHF 16 in reply to a charging data request sent from the CTF 18 towards the CHF 16.

In at least one embodiment, the configuration information restricts announcement event reporting only to one or more certain types of announcements and the method 700 further comprises the CTF 18 conditioning the sending of the announcement event information towards the CHF 16 for the announcement in dependence on the announcement being of a type matching the configuration information.

In at least one embodiment, the method 700 further comprises the CTF 18 tracking quota consumption during the playback of the announcement and including an indication of the quota consumption in the announcement event information. For example, if the call is metered in seconds, the CTF 18 tracks the number of seconds spanned by the announcement playback and reports that consumption to the CHF 16, along with reporting the announcement playback results.

Figure 8 illustrates an example implementation of a CTF 18 comprising communication interface circuitry 60, including transmitter circuitry 62 and receiver circuitry 64, and further including processing circuitry 66 that is operatively associated with the communication interface circuitry 60. Being “operatively associated” with the communication interface circuitry 60 means that the processing circuitry 66 uses the communication interface circuitry 60 to exchange signaling with one or more other nodes or functions in the network 12, e.g., to exchange charging-related messages with one or more CHFs 16. The communication interface circuitry 60 comprises physical-layer circuitry for transmitting and receiving signaling over the involved wired or wireless medium and, in an example embodiment, the communication interface circuitry 30 comprises an Ethernet interface circuit or other computer data network interface.

In at least one embodiment, the processing circuitry 66 includes or is associated with storage 68, which comprises one or more types of computer-readable media. Such media stores, for example, one or more computer programs 70 and/or one or more types of configuration data 72, e.g., data indicating the type(s) of announcement events for which announcement event reporting is active.

The processing circuitry 66 is configured to: (a) monitor playback of an announcement to one or both of a calling party and a called party involved in a call, where a charging session between the CTF 18 and a CHF 16 corresponds with the call; and (b) send announcement event information towards the CHF 16 using the charging session, the announcement event information indicating playback results for the announcement. More generally, the processing circuitry 66 is configured to carry out any one or more of the operations described for the method 700.

Consider Figure 9, for example, which illustrates an example implementation of the processing circuitry 66 / storage 68. Particularly, the processing circuitry 66 comprises one or more microprocessors 80 or other digital processing circuits that are specially adapted to perform the CTF operations described herein at least in part based on the execution of computer program instructions held in one or more memory devices 82. Figure 10 illustrates another example implementation of a CTF 18 that is configured to carry out the operations described herein for a CTF 18. Here, the CTF 18 includes a set 1000 of processing modules or units that are respectively configured to carry out various ones of the described CTF operations. Although the CTF 18 in one or more embodiments is implemented as a virtualized device in a virtualization environment, a set 1000 of processing modules is realized using underlying computer resources, e.g., allocated processing and memory resources that are used to instantiate the functional logic that carries out the CTF operations described herein.

In the specific example of Figure 10, the CTF 18 includes a receiving module 1002 that is configured to receive configuration information from a CHF 16, wherein the configuration information configures or otherwise controls announcement event reporting by the CTF 18.

The modules further include an announcing module 1004 that is configured to monitor announcement playback to one or more parties involved in a call for which the CTF 18 is involved. Still further, the modules included in the set 1000 of modules include a compiling module 1006 that is configured to compile announcement event information for reporting with respect to an announcement for which announcement event reporting is active, and a sending module 1008 that is configured to send the announcement event information to the CHF 16.

A system instantiated in a communication network 12 according to the above example details includes CHF 16 and a CTF 18, wherein the CTF 18 is configured to send announcement event information to the CHF 16, indicating playback results for an announcement monitored by the CTF 18 with respect to one or both of a calling party and a called party in a call for which the CTF 18 supports a charging session. As a further part of the system, the CHF 16 is configured to initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure.

In one or more implementations, the reporting of announcement event reporting by a

CTF 18 to a CHF 16 is based on extending Table 5.43.1 set out in 3GPP TS 32.260 V17.2.0, as follows:

Separate triggers for the calling and called parties is preferred because in most cases the interest is mainly on the served party as this is also the charged party, but there may be cases where both parties are of interest. There may be triggers to record the start of an attempted announcement playback, along with recording the announcement ending time. In most cases there is no need for immediate reporting by the CTF 18 to the CHF 16 of announcement playback information, so deferred action may be preferred. However, immediate reporting may be used.

Having the possibility from the CHF 16 or other entity in the charging system 14 to enable and disable the triggers at the CTF 18 that control announcement event monitoring and corresponding reporting means by the CTF 18 that the CHF/charging-system might set the trigger for announcement event reporting only for announcements for which confirmation of playback is important, announcements warning of low account balance or warning that a refill is needed to keep the subscription active. The ability to enable / disable reporting by the CTF 18 limits the signaling and processing impact associated with announcement-event reporting and monitoring. To play an announcement, the CHF 16 / charging system 24 returns, for example, an instruction to the CTF 18 using one or more instances of the Announcement-Information (3GPP TS 32.281) in the Charging data Response. A proposed structure appears in the below table:

An announcement may consist of several sub-parts, each being an announcement itself, and the CTF 18 may be configured to return the result from playing each of these announcements sub-parts. In at least one such embodiment, the following information would be sent in a charging request to the CHF 16, where such information is new in the context of 3GPP

TS 32.281:

One alternative solution could be to have a further CTF 18 in a Media Resource Function Controller of an IMS 26 as well and use a correlation identifier (ID) to correlate the information received from a CTF 18 in an IMS Application Server (AS) and the CTF in the MRFC.

When the CHF 16 /charging system 24 decides to order the playing of announcement, it will at the same time also decide if the announcement requires the recording of the confirmation that it was played and enable the trigger at the involved CTF 18 based on this. When the trigger is satisfied and the CTF reports the announcement playback information, the CHF 16 /charging system 24 records the playback results. More particularly, if the playback is successful, the CHF/charging system may record an indication of the success, e.g., with timestamp information, but may initiate a failure handling procedure if the playback was not successful.

Figure 11 is a block diagram of a communication network, according to an example embodiment. Nomenclature and connections shown in the diagram correspond with Fifth Generation (5G) specifications by the 3GPP. For additional information, see 3GPP TS 38.401 V17.0.0 and 3GPP TS 38.410 V17.0.0.

A user device 10, e.g., a “User Equipment” or “UE” in 3GPP parlance, connects to the communication network 12 through a radio access node, such as a gNB 100. A User Plane Function (UPF) 102 handles user traffic and provides, for example, communicative coupling to external networks. A Session Management Function (SMF) 104 includes a CTF 18 that is operative to initiate the establishment of a charging session with a CHF 16 in a charging system 24 of the network 12. In this context, the CTF 18 performs any one or more of the announcement event reporting operations detailed in the method 700 and the CHF 16 performs any one or more of the announcement event configuring/reporting operations detailed in the method 300.

Additional network functions (NF) supporting communications and charging include a Policy Control Function (PCF) 106, and an Access and Mobility Management Function (AMF) 108. Note that announcement event reporting and processing may be carried out by the CTF 18 and the CHF 16 with respect to a call by the user device 10 as, e.g., a calling party, placing a call to a called party through an IMS 26, which is represented in the diagram by an Application Function (AF) 110 that is in a Proxy Call Session Control Function (P-CSCF) in the IMS 26, operating as a SIP proxy. In operation, the setup is from a UDF and is routed/controlled by a SMF/PCF to the IMS node(s) where the CTF 18 resides.

Figure 12 is a block diagram of example details for a charging system 24 of a communication network 12, according to an example embodiment. A multiplicity of CTFs 18 reside in a CN domain 120, within various service elements 122, and within the IMS subsystem 124, and generate charging-related messages towards a CHF 16 in the charging system 24. Any one or more of the CTFs 18 is configured to perform announcement event reporting as detailed herein, and the CHF 16 is configured to perform announcement event processing and, optionally, announcement event configurations, according to the details disclosed herein.

The CHF 16 communicates with an account balance management function (ABMF) 130 for account information, and with a rating function (RF) 132, e.g., to determine rated consumption units to be granted for service consumption by given user devices 10 using communication services provided by or though the communication network 12. The CHF 16 may also communicate with a Charging Gateway Function (CFG) 134, which interfaces with a billings system — not shown. Notably, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS What is claimed is:

1. A method (700) of operation by a Charging Trigger Function (CTF) of a communication network, the method comprising: monitoring (702) playback of an announcement to one or both of a calling party and a calling party involved in a call, where a charging session between the CTF and a Charging Function (CHF) of the communication network corresponds with the call; and sending (704) announcement event information towards the CHF using the charging session, the announcement event information indicating playback results for the announcement.

2. The method of claim 1, wherein the announcement event information comprises an information element (IE) indicating whether playback of the announcement was successful.

3. The method of claim 1 or 2, wherein the announcement event information comprises an information element (IE) indicating a time at which the playback was initiated.

4. The method of any one of claims 1-3, wherein the announcement event information sent by the CTF comprises a results information element (IE) that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

5. The method of any one of claims 1-4, wherein sending the announcement event information comprises sending the announcement event information conditioned on an announcement-event reporting trigger being active at the CTF.

6. The method of claim 5, further comprising, prior to monitoring the playback of the announcement, receiving configuration information from the CHF or from another node in the communication network, the configuration information activating the announcement-event reporting trigger.

7. The method of claim 6, wherein receiving the configuration information comprises receiving the configuration information in a charging data response received from the CHF in reply to a charging data request sent from the CTF towards the CHF.

8. The method of claim 7, wherein the configuration information restricts announcement event reporting only to one or more certain types of announcements and wherein the method further comprises the CTF conditioning the sending of the announcement event information towards the CHF for the announcement in dependence on the announcement being of a type matching the configuration information.

9. The method of any one of claims 1-8, further comprising tracking quota consumption during the playback of the announcement and including an indication of the quota consumption in the announcement event information.

10. A method (300) of operation by Charging Function (CHF) of a communication network, the method comprising: receiving (306) announcement event information reported by a Charging Trigger Function (CTF) supporting a charging session for a call involving calling and called parties, the announcement event information indicating playback results for playback of an announcement monitored by the CTF, the announcement targeting one or both of the calling and called parties; and initiating (308) a failure-handling procedure responsive to the announcement event information indicating a playback failure for the announcement.

11. The method of claim 10, wherein the announcement event information comprises an information element (IE) indicating whether playback of the announcement was successful.

12. The method of claim 10 or 11, wherein the announcement event information comprises an information element (IE) indicating a time at which the playback was initiated.

13. The method of any one of claims 10-12, wherein the announcement event information reported by the CTF comprises a results information element (IE) that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

14. The method of any one of claims 10-13, further comprising sending configuration information to the CTF in advance of receiving the announcement event information, the configuration information configuring an announcement-event reporting trigger to be active at the CTF, and wherein the CTF conditions the reporting of the announcement event information on the announcement-event reporting trigger being active.

15. The method of claim 14, wherein sending the configuration information to the CTF comprises sending the configuration information in a charging data response sent by the CHF in response to the CHF receiving a charging data request from the CTF.

16. The method of claim 14 or 15, wherein sending the configuration information comprises sending the configuration information responsive to determining that the announcement is of a certain type.

17. The method of any one of claims 14-16, further comprising sending further configuration subsequent to receiving the announcement event information, to deactivate the announcementevent reporting trigger at the CTF.

18. The method of any one of claims 10-17, further comprising, in advance of receiving the announcement event information, sending announcement information to the CTF that comprises the announcement or otherwise indicates the announcement.

19. The method of claim 18, wherein the announcement information activates announcement-event reporting at the CTF, thereby causing the CTF to send the announcement event information corresponding to the announcement.

20. The method of any one of claims 10-19, wherein the failure-handling procedure comprises the CHF initiating a further attempt by the CTF for playback of the announcement.

21. The method of any one of claims 10-20, wherein the failure-handling procedure comprises the CHF initiating generation of an alert message for delivery to the party or parties targeted by the corresponding announcement via an alternate delivery mechanism, the party or parties targeted by the corresponding announcement being at least one of the calling party and the called party.

22. The method of any one of claims 10-21, wherein the failure-handling procedure comprises the CHF sending an indication of the playback failure towards another node in the communication network.

23. The method of any one of claims 10-22, further comprising sending configuration information to the CTF that includes information that restricts announcement event reporting by the CTF to announcements of one or more particular announcement types.

24. The method of claim 10, further comprising initiating recording of billing-records data confirming playback of the announcement responsive to the announcement event information indicating a successful playback of the announcement.

25. A system instantiated in a communication network, the system comprising a Charging Function (CHF) (16) and a Charging Trigger Function (CTF) (18), wherein: the CTF is configured to send announcement event information to the CHF, indicating playback results for an announcement monitored by the CTF with respect to one or both of a calling party and a called party in a call for which the CTF supports a charging session; and the CHF is configured to initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure.

26. A Charging Trigger Function (CTF) (18) of a communication network (12), the CTF (18) comprising: communication interface circuitry (60) configured to communicatively couple the CTF (18) to a Charging Function (CHF) (16) of the communication network (12); and processing circuitry (66) operatively associated with the communication interface circuitry (60) and configured to: monitor playback of an announcement to one or both of a calling party and a called party involved in a call, where a charging session between the CTF (18) and the CHF (16) corresponds with the call; and send announcement event information towards the CHF (16) using the charging session, the announcement event information indicating playback results for the announcement.

27. The CTF (18) of claim 26, wherein the announcement event information comprises an information element (IE) indicating whether playback of the announcement was successful.

28. The CTF (18) of claim 26 or 27, wherein the announcement event information comprises a results information element (IE) that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

29. The CTF (18) of any one of claims 26-28, wherein the processing circuitry (66) is configured to send the announcement event information conditioned on an announcement-event reporting trigger being active at the CTF.

30. The CTF (18) of claim 29, wherein the processing circuitry (66) is configured to, prior to monitoring the playback of the announcement, receive configuration information from the CHF or from another node in the communication network, the configuration information activating the announcement-event reporting trigger.

31. The CTF (18) of claim 30, wherein the processing circuitry (66) is configured to receive the configuration information in a charging data response received from the CHF in reply to a charging data request sent from the CTF towards the CHF.

32. The CTF (18) of claim 31, wherein the configuration information restricts announcement event reporting only to one or more certain types of announcements and wherein the processing circuitry (66) is configured to condition the sending of the announcement event information towards the CHF for the announcement in dependence on the announcement being of a type matching the configuration information.

33. A Charging Function (CHF) (16) of a communication network (12), the CHF (16) comprising: communication interface circuitry (30) configured to communicatively couple the CHF (16) to a Charging Trigger Function (CTF) (18) of the communication network (12); and processing circuitry (36) operatively associated with the communication interface circuitry (30) and configured to: receive announcement event information reported by the CTF (18) supporting a charging session for a call involving calling and called parties, the announcement event information indicating playback results for playback of an announcement monitored by the CTF (18), the announcement targeting one or both of the calling and called parties; and initiate a failure-handling procedure responsive to the announcement event information indicating a playback failure for the announcement.

34. The CHF (16) of claim 33, wherein the announcement event information comprises an information element (IE) indicating whether playback of the announcement was successful.

35. The CHF (16) of claim 33 or 34, wherein the announcement event information comprises an information element (IE) indicating a time at which the playback was initiated.

36. The CHF (16) of any one of claims 33-35, wherein the announcement event information reported by the CTF comprises a results information element (IE) that indicates the playback results, and comprises one or more further IES indicating at least one of: an announcement identifier IE that identifies the announcement, a start time IE that indicates the time at which announcement playback was initiated, a duration IE that indicates the duration of the announcement playback, a quota IE that indicates quota consumption for the announcement playback, a party IE that indicates the party or parties targeted by the corresponding announcement, or a data IE that contains information entered by the targeted party or parties in response to playback of the corresponding announcement, the targeted party or parties being one or both of the calling and called parties.

37. The CHF (16) of any one of claims 33-36, wherein the processing circuitry (36) is configured to send configuration information to the CTF in advance of receiving the announcement event information, the configuration information configuring an announcementevent reporting trigger to be active at the CTF, and wherein the CTF conditions the reporting of the announcement event information on the announcement-event reporting trigger being active.

38. The CHF (16) of claim 37, wherein the processing circuitry (36) is configured to send the configuration information to the CTF in a charging data response sent by the CHF in response to the CHF receiving a charging data request from the CTF.

39. The CHF (16) of claim 37 or 38, wherein the processing circuitry (36) is configured to send the configuration information responsive to determining that the announcement is of a certain type.

40. The CHF (16) of any one of claims 36-39, wherein the processing circuitry (36) is configured to send further configuration subsequent to receiving the announcement event information, to deactivate the announcement-event reporting trigger at the CTF.

41. The CHF (16) of any one of claims 33-40, wherein the processing circuitry (36) is configured to, in advance of receiving the announcement event information, send announcement information to the CTF that comprises the announcement or otherwise indicates the announcement.

42. The CHF (16) of claim 41, wherein the announcement information activates announcement-event reporting at the CTF, thereby causing the CTF to send the announcement event information corresponding to the announcement.

43. The CHF (16) of any one of claims 33-42, wherein the failure-handling procedure comprises the CHF initiating a further attempt by the CTF for playback of the announcement.

44. The CHF (16) of any one of claims 33-43, wherein the failure-handling procedure comprises the CHF initiating generation of an alert message for delivery to the party or parties targeted by the corresponding announcement via an alternate delivery mechanism, the party or parties targeted by the corresponding announcement being at least one of the calling party and the called party.

45. The CHF (16) of any one of claims 33-44, wherein the failure-handling procedure comprises the CHF sending an indication of the playback failure towards another node in the communication network.

46. The CHF (16) of any one of claims 33-45, wherein the processing circuitry (36) is configured to send configuration information to the CTF that includes information that restricts announcement event reporting by the CTF to announcements of one or more particular announcement types.

47. The CHF (16) of claim 33, wherein the processing circuitry (36) is configured to initiate recording of billing-records data confirming playback of the announcement, responsive to the announcement event information indicating a successful playback of the announcement.