6 Definition of charging information
32.2723GPPCharging managementPush-to-talk over Cellular (PoC) chargingRelease 17Telecommunication managementTS
6.1 Data description for PoC offline charging
6.1.0 General
The PoC Server generates charging information that can be transferred from the CTF to the CDF with the Charging Data transfer operation. Detailed information about the usage of the Charging Data transfer operation is described in TS 32.299 [50].
6.1.1 Rf message contents
6.1.1.1 Summary of offline charging message formats
The PoC Charging application for offline charging employs the Charging Data Request and Charging Data Response. The Charging Data Request can be of type start, stop, interim and event and includes all charging information. The Charging Data Response is just an acknowledgement of the CHARGING DATA REQUEST.
Table 6.1.1.1 describes the use of these messages for offline charging.
Table 6.1.1.1: Offline charging messages reference table
|
Message |
Source |
Destination |
|---|---|---|
|
Charging Data Request |
PoC Server |
CDF |
|
Charging Data Response |
CDF |
PoC Server |
6.1.1.2 Structure for the Charging Data message formats
6.1.1.2.0 Introduction
PoC offline charging used the Charging Data transfer with the two messages Charging Data Request and Charging Data Response. The request can be of type Start, Stop, Interim and Event. The Charging Data Request message includes all charging information and the answer is just an acknowledgement of the request message. Detailed information about the offline charging application is described in TS 32.299 [50].
This clause describes the different fields used in the Charging Data messages. and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]
6.1.1.2.1 Charging Data Request message
Table 6.1.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for PoC offline charging.
Table 6.1.1.2.1.1: Charging Data Request message contents for offline charging
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Originator Host |
M |
Used as described in TS 32.299 [50]. |
|
Originator Domain |
M |
Used as described in TS 32.299 [50]. |
|
Destination Domain |
M |
Used as described in TS 32.299 [50]. |
|
Operation Type |
M |
Used as described in TS 32.299 [50]. |
|
Operation Number |
M |
Used as described in TS 32.299 [50]. |
|
Operation Identifier |
OM |
Used as described in TS 32.299 [50]. |
|
OC |
Used as described in TS 32.299 [50]. |
|
|
User Name |
OC |
Used as described in TS 32.299 [50]. |
|
Destination Host |
OC |
Used as described in TS 32.299 [50]. |
|
Operation Interval |
OC |
|
|
Origination State |
OC |
|
|
Origination Timestamp |
OC |
|
|
Proxy Information |
– |
Not used in 3GPP. |
|
Route Information |
– |
Not used in 3GPP. |
|
Operation Token |
OM |
Used as described in TS 32.299 [50] |
|
Service Information |
OM |
This field holds the PoC specific parameter and is described in clause 6.3. Subscription-Id is used as described in TS 32.299 [50] |
NOTE: Detailed descriptions of the fields are provided in TS 32.299 [50].
6.1.1.2.2 Charging Data Response message
Table 6.1.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for PoC charging. This message is always used by the CDF as specified below, regardless of the PoC Server it is received from and the Charging Data Request record type that is being replied to.
Table 6.1.1.2.2.1: Charging Data Response message contents for offline charging
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Operation Result |
M |
Used as described in TS 32.299 [50]. |
|
Originator Host |
M |
Used as described in TS 32.299 [50]. |
|
Originator Domain |
M |
Used as described in TS 32.299 [50]. |
|
Operation Type |
M |
Used as described in TS 32.299 [50]. |
|
Operation Number |
M |
Used as described in TS 32.299 [50]. |
|
Operation Identifier |
OC |
Used as described in TS 32.299 [50]. |
|
Error Reporting Host |
– |
Not used in 3GPP. |
|
Operation Interval |
OC |
Used as described in TS 32.299 [50]. |
|
Origination State |
OC |
Used as described in TS 32.299 [50]. |
|
Origination Timestamp |
OC |
Used as described in TS 32.299 [50]. |
6.1.2 GTP’ message contents
Editor’s note:
< Based on clause 5.2.4. If not applicable as per 5.2.4, insert only the following text. >
{Not applicable. Refer to clause 5.2.4 for further information.}
6.1.3 CDR description on the BT interface
6.1.3.1 CDR field types
The content of the PoC CDR type is defined in table 6.1.3.3.1 and table 6.1.3.3.2. For the CDR type the field definition includes the field name, category and description. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. The detailed field descriptions are provided in TS 32.298 [51].
The CDF provides the CDRs at the BT interface in the format and encoding described in TS 32.298 [51]. Additional CDR formats and contents may be available at the interface to the billing system to meet the requirements of the billing system, these are outside of the scope of 3GPP standardization.
6.1.3.2 CDR triggers
6.1.3.2.1 PoC session related CDRs
Reflecting the usage of PoC sessions CDRs are generated by the CDF on a per session basis. In the scope of the present document the term "PoC session" refers to the following cases:
– 1 to 1 PoC sessions;
– PoC group sessions (1 to many).
Accounting information for SIP sessions is transferred from the PoC Server to the CDF using Charging Data Request [start, interim and stop] messages. A PoC session CDR is opened in the CDF upon reception of a Diameter Charging Data Request [start] message.
Partial CDRs may be generated upon reception of a Charging Data Request [interim] message.
The Diameter Charging Data Request [Interim] message is sent by the network entity towards the CDF due to a session modification procedure (i.e. change in media) , due to a change to location of the user, or due to usage threshold (e.g. volume, duration, number of change conditions).
Session CDRs are updated, or partial CDRs are generated upon reception of a Charging Data Request [Interim] message, which is sent by the network entity due to expiration of the Accounting-Interim-Interval parameter.
The CDF closes the final session CDR upon reception of a Charging Data Request [stop] message, which indicates that the SIP session is terminated.
Accounting information for unsuccessful session set-up attempts may be sent by the PoC Server to the CDF employing the Charging Data Request [event] message. The behaviour of the CDF upon receiving Charging Data Request [event] messages is specified in clause 6.1.3.2.2.
6.1.3.2.2 Session unrelated CDRs
To reflect chargeable events not directly related to a PoC session the CDF may generate CDRs upon the occurrence of session unrelated SIP procedures, such as:
– Sending/Receiving instant personal alert. Unsuccessful message shall not be charged.
– Sending/Receiving PoC group advertisement. Unsuccessful message shall not be charged.
– PoC Client subscription to the conference state (based on a PoC group identity of the PoC group or on a PoC session identity).
– PoC Client adding a user to a PoC session
– PoC Client handling for PoC session locking in a particular PoC session (simultaneous session control): the PoC Client may request to lock itself in a particular PoC session while initiating a PoC session or at any time later when a valid PoC session exists.
– PoC Client handling for PoC session priority in a particular PoC session (simultaneous session control): the PoC Client may set a PoC session priority in a particular PoC session while initiating a PoC session or at any time later when a valid PoC session exists.
Accounting information for SIP session-unrelated procedures is transferred from the PoC Server to the CDF using Diameter Charging Data Request [event] messages. Session unrelated CDRs are created in the CDF in a "one-off" action based on the information contained in the Diameter Charging Data Request [event] message. One session unrelated CDR is created in the CDF for each Diameter Charging Data Request [event] message received, whereas the creation of partial CDRs is not applicable for session unrelated CDRs.
6.1.3.3 PoC CDR content
The detailed description of the field is provided in TS 32.298 [51].
6.1.3.3.1 Participating PoC Function
Table 6.1.3.3.1.1 contains the content of Participating PoC Function (PPF) CDR.
Table 6.1.3.3.1.1: Charging data of PPF-CDR
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Identifies the PoC service record. |
|
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Diameter Charging Data Requests has been used in this CDR. |
|
SIP Method |
OC |
Specifies the SIP-method for which the CDR is generated. Only available in session unrelated cases. This parameter corresponds to Event-Type. |
|
Node Address |
OM |
This item holds the address of the node providing the information for the CDR. This may either be the IP address or the FQDN of the IMS node generating the accounting data. This parameter corresponds to the Origin-Host. |
|
Session ID |
OM |
The Session identification. For a SIP session the Session-ID contains the SIP Call ID as defined in the Session Initiation Protocol RFC 3261 [404]. This parameter corresponds to User-Session-ID. |
|
Calling Party Address |
OM |
The address (Public User ID) of the party requesting a service or initiating a session. This field holds either the SIP URI (according to RFC 3261 [404]) or the TEL URI (according to RFC 3966 [405]) of the calling party. This parameter corresponds to Calling-Party-Address. |
|
Called Party Address |
OM |
In the context of an end-to-end SIP transaction this field holds the address of the party (Public User ID) to whom the SIP transaction is posted. This parameter corresponds to Called-Party-Address. |
|
Service Request Time Stamp |
OM |
This field contains the time stamp which indicates the time at which the service was requested. This parameter corresponds to SIP-Request-Timestamp in Charging Data Request[Start]. |
|
Service Delivery Start Time Stamp |
OM |
This field holds the time stamp reflecting either: successful session set-up, a delivery unrelated service, an unsuccessful session set-up and an unsuccessful session unrelated request. This parameter corresponds to SIP-Response-Timestamp in Charging Data Request[Start]. |
|
Service Delivery End Time Stamp |
OC |
This field records the time at which the service delivery was terminated. It is Present only in SIP session related case. This parameter corresponds to SIP-Request-Timestamp. in Charging Data Request[Stop]. |
|
Record Opening Time |
OC |
A time stamp reflecting the time the CDF opened this record. Present only in SIP session related case. |
|
Record Closure Time |
OM |
A Time stamp reflecting the time the CDF closed the record. |
|
Inter Operator Identifiers |
OC |
Holds the identification of the home network (originating and terminating) if exchanged via SIP signalling, as recorded in the Inter-Operator-Identifier. |
|
Originating IOI |
OC |
This parameter corresponds to Originating-IOI. |
|
Terminating IOI |
OC |
This parameter corresponds to Terminating-IOI. |
|
Local Record Sequence Number |
OM |
This field includes a unique record number created by this node. The number is allocated sequentially for each partial CDR (or whole CDR) including all CDR types. The number is unique within the CDF. |
|
Record Sequence Number |
OC |
This field contains a running sequence number employed to link the partial records generated by the CDF for a particular session. |
|
Cause For Record Closing |
OM |
This field contains a reason for the release of the CDR. |
|
Incomplete CDR Indication |
OC |
This field provides additional diagnostics when the CDF detects missing Charging Data Requests. |
|
IMS Charging Identifier |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the IMS node for the SIP session. This parameter corresponds to IMS-Charging-Identifier (ICID). |
|
SDP Session Description |
OC |
Holds the Session portion of the SDP data exchanged between the User Agents if available in the SIP transaction. This parameter corresponds to SDP‑Session‑Description. |
|
List of SDP Media Components |
OC |
This is a grouped field comprising several sub-fields associated with one media component. It may occur several times in one CDR. The field is present only in a SIP session related case. |
|
SIP Request Timestamp |
OM |
This parameter contains the time of the SIP Request (usually a (Re)Invite). This parameter corresponds to SIP-Request-Timestamp in INTERIM Charging Data Request. |
|
SIP Response Timestamp |
OM |
This parameter contains the time of the response to the SIP Request (usually a 200 OK). This parameter corresponds to SIP-Response-Timestamp in INTERIM Charging Data Request. |
|
SDP Media Components |
OM |
This is a grouped field comprising several sub-fields associated with one media component. Since several media components may exist for a session in parallel these sub-fields may occur several times. This parameter corresponds to SDP‑Media-Component. |
|
SDP Media Name |
OM |
This field holds the name of the media as available in the SDP data. This parameter corresponds to SDP-Media-Name. |
|
SDP Media Description |
OM |
This field holds the attributes of the media as available in the SDP data. This parameter corresponds to SDP-Media-Description. |
|
GPRS Charging ID |
OC |
This parameter holds the GPRS charging ID (GCID) which is generated by the GGSN for a GPRS PDP context. This parameter corresponds to GPRS-Charging-Id. |
|
Media Initiator flag |
OC |
This field indicates if the called party has requested the session modification and it is present only if the initiator was the called party. |
|
Media Initiator Party |
OC |
This field indicates the address (SIP URI or TEL URI) of the party (Public User ID or Public Service ID) who initiates the media action, like adding/removing the media. |
|
GGSN Address |
OC |
This parameter holds the control plane IP address of the GGSN that handles one or more media component(s) of a IMS session. This parameter corresponds to the P‑Charging-Vector header. |
|
Service Delivery Failure Reason |
OC |
Holds the reason for why a requested service could not be successfully provided (i.e. SIP error codes taken from SIP-Method). This field is not present in case of a successful service delivery. |
|
Service Specific Data |
OC |
This field contains service specific data. |
|
List of Message Bodies |
OC |
This grouped field comprising several sub-fields describing the data that may be conveyed end-to-end in the body of a SIP message. Since several message bodies may be exchanged via SIP-signalling, this grouped field may occur several times. |
|
Content Type |
OC |
This sub-field of Message Bodies holds the MIME type of the message body, Examples are: application/zip, image/gif, audio/mpeg, etc. This parameter corresponds to Event-Type / Content-Type. |
|
Content Disposition |
OC |
This sub-field of Message Bodies holds the content disposition of the message body inside the SIP signalling, Content-disposition header field equal to "render", indicates that "the body part should be displayed or otherwise rendered to the user". Content disposition values are: session, render, inline, icon, alert, attachment, etc. This parameter corresponds to Event-Type / Content-Disposition. |
|
Content Length |
OC |
This sub-field of Message Bodies holds the size of the data of a message body in bytes. This parameter corresponds to Event-Type / Content-Length. |
|
Originator |
OC |
This sub-field of the "List of Message Bodies" indicates the originating party of the message body. This parameter corresponds to P-Asserted-Identity header. |
|
PoC Information |
OC |
A set of PoC specific parameters such as PoC session Type, PoC Server Role and the accumulated send/received talk burst information of the participant. . See clause 6.3.1.2. |
|
User Location Info |
OC |
This field holds information about the location of the user to the level of that made available to the PoC Server. If no location information is available then this parameter is not included. |
|
Service Context Id |
OM |
Holds the context information to which the CDR belongs |
|
Record Extensions |
OC |
A set of operator/manufacturer specific extensions to the record, conditioned upon existence of an extension. |
6.1.3.3.2 Controlling PoC Function
Table 6.1.3.3.2.1 contains the content of Controlling PoC Function (CPF) CDR.
Table 6.1.3.3.2.1: Charging data of CPF-CDR
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Identifies the PoC service record. |
|
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Diameter Charging Data Requests has been used in this CDR. |
|
SIP Method |
OC |
Specifies the SIP-method for which the CDR is generated. Only available in session unrelated cases. This parameter corresponds to Event-Type. |
|
Node Address |
OM |
This item holds the address of the node providing the information for the CDR. This may either be the IP address or the FQDN of the IMS node generating the accounting data. This parameter corresponds to the Origin-Host. |
|
Session ID |
OM |
The Session identification. For a SIP session the Session-ID contains the SIP Call ID as defined in the Session Initiation Protocol RFC 3261 [404]. This parameter corresponds to User-Session-ID. |
|
Calling Party Address |
OM |
The address (Public User ID) of the party requesting a service or initiating a session. This field holds either the SIP URI (according to RFC 3261 [404]) or the TEL URI (according to RFC 3966 [405]) of the calling party. This parameter corresponds to Calling-Party-Address. |
|
Called Party Address |
OM |
In the context of an end-to-end SIP transaction this field holds the address of the party (Public User ID) to whom the SIP transaction is posted. This parameter corresponds to Called-Party-Address. |
|
Service Request Time Stamp |
OM |
This field contains the time stamp which indicates the time at which the service was requested. This parameter corresponds to SIP-Request-Timestamp in START Charging Data Request. |
|
Service Delivery Start Time Stamp |
OM |
This field holds the time stamp reflecting either: successful session set-up, a delivery unrelated service, an unsuccessful session set-up and an unsuccessful session unrelated request. This parameter corresponds to SIP-Response-Timestamp in START Charging Data Request. |
|
Service Delivery End Time Stamp |
OC |
This field records the time at which the service delivery was terminated. It is Present only in SIP session related case. This parameter corresponds to SIP-Request-Timestamp in STOP Charging Data Request. |
|
Record Opening Time |
OC |
A time stamp reflecting the time the CDF opened this record. Present only in SIP session related case. |
|
Record Closure Time |
OM |
A Time stamp reflecting the time the CDF closed the record. |
|
Inter Operator Identifiers |
OC |
Holds the identification of the home network (originating and terminating) if exchanged via SIP signalling, as recorded in the Inter-Operator-Identifier. |
|
Originating IOI |
OC |
This parameter corresponds to Originating-IOI. |
|
Terminating IOI |
OC |
This parameter corresponds to Terminating-IOI. |
|
Local Record Sequence Number |
OM |
This field includes a unique record number created by this node. The number is allocated sequentially for each partial CDR (or whole CDR) including all CDR types. The number is unique within the CDF. |
|
Record Sequence Number |
OC |
This field contains a running sequence number employed to link the partial records generated by the CDF for a particular session. |
|
Cause For Record Closing |
OM |
This field contains a reason for the release of the CDR. |
|
Incomplete CDR Indication |
OC |
This field provides additional diagnostics when the CDF detects missing Charging Data Requests. |
|
IMS Charging Identifier |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the IMS node for the SIP session. This parameter corresponds to IMS-Charging-Identifier (ICID). |
|
SDP Session Description |
OC |
Holds the Session portion of the SDP data exchanged between the User Agents if available in the SIP transaction. This parameter corresponds to SDP‑Session‑Description. |
|
List of SDP Media Components |
OC |
This is a grouped field comprising several sub-fields associated with one media component. It may occur several times in one CDR. The field is present only in a SIP session related case. |
|
SIP Request Timestamp |
OM |
This parameter contains the time of the SIP Request (usually a (Re)Invite). This parameter corresponds to SIP-Request-Timestamp in INTERIM Charging Data Request. |
|
SIP Response Timestamp |
OM |
This parameter contains the time of the response to the SIP Request (usually a 200 OK). This parameter corresponds to SIP-Response-Timestamp in INTERIM Charging Data Request. |
|
SDP Media Components |
OM |
This is a grouped field comprising several sub-fields associated with one media component. Since several media components may exist for a session in parallel these sub-fields may occur several times. This parameter corresponds to SDP‑Media-Component. |
|
SDP Media Name |
OM |
This field holds the name of the media as available in the SDP data. This parameter corresponds to SDP-Media-Name. |
|
SDP Media Description |
OM |
This field holds the attributes of the media as available in the SDP data. This parameter corresponds to SDP-Media-Description. |
|
Media Initiator flag |
OC |
This field indicates if the called party has requested the session modification and it is present only if the initiator was the called party. |
|
Media Initiator Party |
OC |
This field indicates the address (SIP URI or TEL URI) of the party (Public User ID or Public Service ID) who initiates the media action, like adding/removing the media. |
|
GGSN Address |
OC |
This parameter holds the control plane IP address of the GGSN that handles one or more media component(s) of a IMS session. This parameter corresponds to the P‑Charging-Vector header. For the controlling PoC Server, this is only included if the charged party is participating in the session. |
|
Service Delivery Failure Reason |
OC |
Holds the reason for why a requested service could not be successfully provided (i.e. SIP error codes taken from SIP-Method). This field is not present in case of a successful service delivery. |
|
Service Specific Data |
OC |
This field contains service specific data. |
|
List of Message Bodies |
OC |
This grouped field comprising several sub-fields describing the data that may be conveyed end-to-end in the body of a SIP message. Since several message bodies may be exchanged via SIP-signalling, this grouped field may occur several times. |
|
Content Type |
OC |
This sub-field of Message Bodies holds the MIME type of the message body, Examples are: application/zip, image/gif, audio/mpeg, etc. This parameter corresponds to Event-Type / Content-Type. |
|
Content Disposition |
OC |
This sub-field of Message Bodies holds the content disposition of the message body inside the SIP signalling, Content-disposition header field equal to "render", indicates that "the body part should be displayed or otherwise rendered to the user". Content disposition values are: session, render, inline, icon, alert, attachment, etc. This parameter corresponds to Event-Type / Content-Disposition. |
|
Content Length |
OC |
This sub-field of Message Bodies holds the size of the data of a message body in bytes. This parameter corresponds to Event-Type / Content-Length. |
|
Originator |
OC |
This sub-field of the "List of Message Bodies" indicates the originating party of the message body. This parameter corresponds to P-Asserted-Identity header. |
|
PoC Information |
OC |
A set of PoC specific parameters such as PoC session Type, PoC Server Role, Number and List of Participants and the accumulated talk burst information during the PoC session. See clause 6.3.1.2. |
|
User Location Info |
OC |
This field holds information about the location of the charged party to the level of that made available to the PoC Server. If no location information is available then this parameter is not included. For the controlling PoC Server, this additionally is only included if the charged party is participating in the session. |
|
Service Context Id |
OM |
Holds the context information to which the CDR belongs |
|
Record Extensions |
OC |
A set of operator/manufacturer specific extensions to the record, conditioned upon existence of an extension. |
6.2 Data description for PoC online charging
6.2.0 General
PoC online charging is using Debit / Reserve Units operation. with the two messages Debit / Reserve Units Request and Debit / Reserve Units Reponse The request performs rating of the PoC service and reserves units on the users account. The answer replies back with amount of reserved units or an error code if the user is out of credit.
Detailed information about the used of Diameter Credit-Control Application is described in TS 32.299 [50]
Table 6.2.0.1 describes the use of these messages for online charging.
Table 6.2.0.1: Online charging messages reference table
|
Message |
Source |
Destination |
|
Debit / Reserve Units Request |
PoC Server |
OCS |
|
Debit / Reserve Units Reponse |
OCS |
PoC Server |
The structure of the Debit / Reserve Units Request and Debit / Reserve Units Reponse messages defined in the following clauses. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]..
6.2.1 Ro message contents
Void.
6.2.1.1 Debit / Reserve Units Request message
Table 6.2.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from the PoC Server as used for PoC online charging.
Table 6.2.1.1: Debit / Reserve Units Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Originator Host |
M |
Used as described in TS 32.299 [50]. |
|
Originator Domain |
M |
Used as described in TS 32.299 [50]. |
|
Destination Domain |
M |
Used as described in TS 32.299 [50]. |
|
Operation Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Operation Token |
M |
Used as described in TS 32.299 [50] |
|
Operation Type |
M |
Used as described in TS 32.299 [50]. |
|
Operation Number |
M |
Used as described in TS 32.299 [50]. |
|
Destination Host |
OC |
Used as described in TS 32.299 [50]. |
|
User Name |
OC |
Used as described in TS 32.299 [50]. |
|
Origination State |
OC |
Used as described in TS 32.299 [50]. |
|
Origination Timestamp |
OC |
Used as described in TS 32.299 [50]. |
|
Subscriber Identifier |
OC |
Used as described in TS 32.299 [50]. |
|
Termination Cause |
OC |
Used as described in TS 32.299 [50]. |
|
Requested -Action |
OC |
Used as described in TS 32.299 [50]. |
|
Multiple Operation |
OM |
Used as described in TS 32.299 [50]. |
|
Multiple Unit Operation |
OC |
Used as described in TS 32.299 [50]. |
|
Subscriber Equipment Number |
– |
Not used in PoC charging. |
|
Proxy Information |
– |
Not used. |
|
Route Information |
OC |
Used as described in TS 32.299 [50]. |
|
Service-Information |
OM |
This field holts the PoC specific parameter and is described in clause 6.3. |
The protocol specific parameter definition is specified in TS 32.299 [50].
6.2.1.2 Debit / Reserve Units Response message
Table 6.2.1.2.1 illustrates the basic structure of a Debit / Reserve Units Response message as used for the PoC Server. This message is always used by the OCS as specified below, independent of the receiving PoC Server and the Debit / Reserve Units Request request type that is being replied to.
Table 6.2.1.2.1: Debit / Reserve Units Response message
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Operation Result |
M |
Used as described in TS 32.299 [50]. |
|
Originator Host |
M |
Used as described in TS 32.299 [50]. |
|
Originator Domain |
M |
Used as described in TS 32.299 [50]. |
|
Operation Identifier |
M |
Used as described in TS 32.299 [50]. |
|
Operation Type |
M |
Used as described in TS 32.299 [50]. |
|
Operation Number |
M |
Used as described in TS 32.299 [50]. |
|
Operation Failover |
OC |
Used as described in TS 32.299 [50]. |
|
Multiple Unit Operation |
OC |
Used as described in TS 32.299 [50]. |
|
Operation Failure Action |
OC |
Used as described in TS 32.299 [50]. |
|
Operation Event Failure ActionRedirection Host |
– |
Not used in PoC charging. |
|
OC |
Used as described in TS 32.299 [50]. |
|
|
Redirection Host Usage |
OC |
Used as described in TS 32.299 [50]. |
|
Redirection Cache Time |
OC |
Used as described in TS 32.299 [50]. |
|
Proxy Information |
– |
Not used in PoC charging . |
|
Route Information |
OC |
Used as described in TS 32.299 [50]. |
|
Failed parameter |
OC |
Used as described in TS 32.299 [50]. |
6.3 PoC charging specific parameters
6.3.1 Definition of the PoC charging information
6.3.1.0 General
The PoC Information parameter used for PoC charging is provided in the Service Information parameter.
6.3.1.1 PoC charging information assignment for Service Information
The components that are used for PoC charging are provided in the Service Information as described in table 6.3.1.1.1.
Table 6.3.1.1.1: Components of the Service Information used for PoC charging
|
Information Element |
Category |
Description |
|
Service Information |
OM |
A set of fields hold the 3GPP specific parameter as defined in TS 32.299 [50]. For MMS Charging the PS Information, IMS Information and PoC Information are used. |
|
Subscriber Identifier |
OM |
Used as defined in TS 32.260 [20]. |
|
PS Information |
OC |
A set of fields hold the PS specific parameters. The details are defined in TS 32.251 [11]. |
|
User Location Info |
OC |
Used as defined in TS 32.251 [11]. |
|
GGSN Address |
OC |
Used as defined in TS 32.251 [11]. |
|
IMS Information |
OC |
A set of fields hold the IMS specific parameters. The details are defined in TS 32.260 [20]. |
|
Event Type |
OC |
Used as defined in TS 32.260 [20]. |
|
User Session ID |
OC |
Used as defined in TS 32.260 [20]. |
|
Calling Party Address |
OC |
Used as defined in TS 32.260 [20]. |
|
Called Party Address |
OC |
Used as defined in TS 32.260 [20]. |
|
Time stamp |
OC |
Used as defined in TS 32.260 [20]. |
|
Inter Operator Identifier |
OC |
Used as defined in TS 32.260 [20]. |
|
IMS Charging Identifier |
OC |
Used as defined in TS 32.260 [20]. |
|
SDP Session Description |
OC |
Used as defined in TS 32.260 [20]. |
|
SDP Media Components |
OC |
Used as defined in TS 32.260 [20]. |
|
Cause Code |
OC |
Used as defined in TS 32.260 [20]. |
|
PoC Information |
OM |
A set of fields hold the PoC specific parameters. The details are defined in clause 6.3.1.2. |
6.3.1.2 Definition of the PoC Information
PoC specific charging information is provided within the PoC_Information. The detailed structure of the PoC_Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the PoC Information
|
Information Element |
Category |
Description |
|---|---|---|
|
PoC Server Role |
OM |
Identifies the PoC Server as participating or controlling PoC Server. |
|
PoC User Role |
OC |
Identifies the PoC user’s role detailed information which should be a list of roles information group. See further details in OMA-AD-POC document [203]. |
|
PoC Session Type |
OM |
Type of the PoC session as defined in appendix C.5.1 in OMA-CP-POC [204]. |
|
Number Of Participants |
OM |
Indicates the number of invited parties of the PoC session when included in the initial charging request message. When included in interim / update charging messages, it indicates the number of parties currently who are attached to the session at the time the interim / update charging messages are sent. |
|
List Of Participants |
OC |
Holds the information for participants, e.g., the addresses, the access priority, the user participating type of the invited parties of the PoC session when included in the initial charging request message. When included in the interim /update charging messages, it holds the addresses and access priority of the parties currently who are attached to the session at the time the interim / update charging messages are sent. |
|
Called Party Address |
OC |
The address (Public User ID, SIP URL, E.164, etc.) of the participants. |
|
Participant Access Priority |
OC |
Indicates the user priority level when participating in the PoC session. |
|
User Participating Type |
OC |
Indicates the participating user type when participating in the PoC session, i.e. Normal, NW PoC Box, UE PoC Box. |
|
PoC Session initiation type |
OC |
Indicates PoC session initiation type. It can be only used for the served parties. |
|
PoC Event Type |
OC |
Indicates PoC session unrelated charging event. |
|
List Of Talk Burst-Exchange |
OC |
Applicable to offline charging only – a list of changes in charging conditions for the PoC session, each change is time stamped. Charging conditions are used to categorize charging, such as per tariff period or based on the number of participants. A set of charging data (number of talk bursts, talk burst bearer volume, sum of talk bursts time) for sent and received talk burst. |
|
PoC Controlling Address |
OC |
Identifies the PoC Server performing the controlling function. This is only included when PoC Server Role indicates "participating". This information may be obtained from the "Contact" header of SIP message received from the controlling PoC function. |
|
PoC Group Name |
OC |
Identifies a pre-arranged group. Included if the session is a pre-arranged group session. This information may be obtained from the "P-Asserted-Identity" header of the SIP message received from the controlling PoC function, or from the "Request-URI" header from the PoC user. |
|
PoC Session Id |
OC |
Uniquely identifies an end-to-end PoC session. Note that the PoC Session-Id may not be available in the initial charging interactions for the PoC session. |
|
Served Party |
OM |
Applicable to offline charging only – holds the identity of the party that the charging information relates to. |
6.3.2 Formal parameter description
6.3.2.1 PoC charging information for CDRs
The detailed definitions, abstract syntax and encoding of the PoC CDR parameters are specified in TS 32.298 [51].
6.3.2.2 PoC charging information for charging events
The detailed charging event parameter definitions are specified in TS 32.299 [50].
Annex A (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in this specification.
Annex B (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
|
Jun 2006 |
SA_32 |
SP-060248 |
0013 |
— |
Add charging flow for mid PoC session Procedure |
B |
6.4.0 |
7.0.0 |
|
Jun 2006 |
SA_32 |
SP-060248 |
0014 |
— |
Add a new field named PoC_user_role to PoC_Information – Align with OMA PoC 2.0 |
B |
6.4.0 |
7.0.0 |
|
Sep 2006 |
SA_33 |
SP-060516 |
0016 |
— |
Clarify the description of Number-Of-Participants in PoC-information |
A |
7.0.0 |
7.1.0 |
|
Sep 2006 |
SA_33 |
SP-060543 |
0017 |
— |
Correction of PoC-Information – Align with 32.299 |
C |
7.0.0 |
7.1.0 |
|
Dec 2006 |
SA_34 |
SP-060718 |
0018 |
– |
Add an identifier for the service initiating offline Diameter Accounting |
B |
7.1.0 |
7.2.0 |
|
Dec 2006 |
SA_34 |
SP-060718 |
0019 |
– |
Add an identifier for the served user in offline Diameter Accounting |
B |
7.1.0 |
7.2.0 |
|
Dec 2006 |
SA_34 |
SP-060718 |
0020 |
– |
Add PoC User Access Priority into PoC-information – Align with OMA-RD-PoC-V2_0 |
B |
7.1.0 |
7.2.0 |
|
Mar 2007 |
SA_35 |
SP-070041 |
0021 |
— |
Add Participant number based charging Trigger Type |
C |
7.2.0 |
7.3.0 |
|
Mar 2007 |
SA_35 |
SP-070041 |
0022 |
— |
Add PoC session initiation type into PoC-information – Alignment with OMA PoC Requirements |
C |
7.2.0 |
7.3.0 |
|
Jun 2007 |
SA_36 |
SP-070275 |
0023 |
– |
Add User Participating Type into PoC-information |
B |
7.3.0 |
7.4.0 |
|
Jun 2007 |
SA_36 |
SP-070275 |
0024 |
– |
Addition of Media Initiator Party. |
F |
7.3.0 |
7.4.0 |
|
Jun 2008 |
SA_40 |
SP-080330 |
0025 |
– |
PoC Information |
B |
7.4.0 |
8.0.0 |
|
Sep 2008 |
SA_41 |
SP-081253 |
0026 |
— |
Alignment on Bx interface |
D |
8.0.0 |
8.1.0 |
|
Dec 2008 |
SA_42 |
SP-080841 |
0028 |
– |
Correction on Multiple Service Indicator category |
A |
8.1.0 |
8.2.0 |
|
Dec 2009 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
– |
8.2.0 |
9.0.0 |
|
Mar 2011 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
– |
9.0.0 |
10.0.0 |
|
2012-09 |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
– |
10.0.0 |
11.0.0 |
|
2013-12 |
SA_62 |
SP-130676 |
0033 |
– |
Correction for use of Destination-Host AVP in ACR |
A |
11.0.0 |
11.1.0 |
|
2014-07 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
– |
11.1.0 |
11.1.1 |
|
2014-09 |
SA_65 |
SP-140564 |
0034 |
1 |
Corrections for alignment between charging specifications |
F |
11.1.1 |
12.0.0 |
|
2014-12 |
SA_66 |
SP-140804 |
0035 |
1 |
Additional corrections for removal of I-WLAN solution |
F |
12.0.0 |
12.1.0 |
|
SP-140805 |
0036 |
– |
Corrections on definition for parameter category |
|||||
|
2016-01 |
Upgrade to Rel-13 (MCC) |
12.1.0 |
13.0.0 |
|||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
SP-170138 |
0038 |
1 |
C |
Remove reference to RFC 3588 |
14.0.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2021-09 |
SA#93e |
SP-210895 |
0039 |
– |
F |
Inclusive language review |
17.0.0 |