6 Definition of charging information
32.2703GPPCharging managementMultimedia Messaging Service (MMS) chargingRelease 18Telecommunication managementTS
6.0 General
This clause provides the Stage 3 specifications of the CDR type and content for MMS, in line with the CDR type definitions provided in clause 5.2.3.
6.1 Data description for MMS offline charging
6.1.0 Introduction
Dedicated types of CDRs can be generated for MMS by the MMS R/Ss. The content of each CDR type is defined in one of the tables that are part of this clause. For each CDR type the parameter definition includes the parameter name, description and category.
The MMS R/S CGF shall be able to provide the CDRs at the Billing System (BS) interface in the format and encoding described in the present document. In MMS, both fully qualified partial CDRs (FQPC) and reduced partial CDRs (RPC), as specified in TS 32.240 [1] may be supported on the Bm interface. In line with TS 32.240 [1], the support of FQPCs is mandatory, the support of RPCs is optional.
The following tables provide a brief description of each CDR parameter and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. Full definitions of the parameters, sorted by the parameter name in alphabetical order, are provided in TS 32.298 [51].
6.1.1 MMS records for Originator MMS R/S
6.1.1.0 General
The following subclauses specify CDRs created in the OOriginator MMS R/S based on messages flowing over the MM1 and MM4 reference points. The CDRs referring to MM4 messages (Originator MM4 *** CDR) are created only if the Originator and Recipient MMS R/Ss communicate over the MM4 interface (i.e. the OOriginator MMS R/S is not also the Recipient MMS R/S). The CDRs referring to MM1 messages (Originator MM1 *** CDR) are created regardless of whether the OriginatorOriginator MMS R/S is also the Recipient MMS R/S or not. Unless otherwise specified, the CDR parameters are copied from the corresponding MM1 or MM4 message parameters as applicable.
6.1.1.1 Originator MM1 Submission record (O1S-CDR)
If enabled, an Originator MM1 Submission O1S-CDR shall be produced in the Originator MMS R/S for each MM submitted in an MM1_submit.REQ by an originator MMS User Agent to the Originator MMS R/S if and when the Originator MMS R/S responds with an MM1_submit.RES. The operator can configure whether this CDR, if enabled, shall only be created for MM1_submit.RES indicating acceptance of the submitted MM, or also for the unsuccessful submissions.
NOTE 1: This includes the case where the MM is a reply-MM to an original MM. In this case the MMS User Agent sending the reply-MM is called the originator MMS User Agent of this reply-MM and the MMS R/S receiving the reply-MM in an MM1_submit.REQ is called the OriginatorOriginator MMS R/S for this reply-MM.
NOTE 2: The case of an MMS R/S receiving an MM1_forward.REQ is treated in clause 6.1.3.
Table 6.1.1.1.1: Originator MM1 Submission record (O1S-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Originator MM1 Submission record |
Originator MMS Relay/Server Address |
M |
.IP address or domain name of OriginatorOriginator MMS R/S |
Message ID |
M |
The MM identification provided by the OriginatorOriginator MMS R/S |
Reply-Charging ID |
C |
This field is present in the CDR only if the MM is a reply-MM to an original MM. The Reply-Charging ID is the Message ID of the original MM |
Originator address |
M |
The address of the originator MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_submit.REQ) |
Recipients address list |
M |
The address(es) of the Recipient MMS User Agent(s) of the MM. Multiple addresses are possible if the MM is not a reply MM |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent |
Content type |
M |
The content type of the MM content |
Content Class |
OC |
This field classifies the content of the MM to the smallest content class to which the MM belongs, if specified in the MM1_submit_REQ |
DRM Content |
OC |
This field indicates if the MM contains DRM-protected content, if specified in the MM1_submit_REQ |
Adaptations |
OC |
This field indicates if the originator allows adaptation of the content (default True), if specified in the MM1_submit_REQ |
MM component list |
OM |
The list of media components with volume size |
Message size |
M |
The total size of the MM content |
Message class |
OC |
The class selection such as personal, advertisement, information service if specified in the MM1_submit_REQ |
Charge Information |
OM |
The charged party indication and charge type |
Submission Time |
OC |
The time at which the MM was submitted from the originator MMS User Agent if specified in the MM1_submit_REQ |
Time of Expiry |
OC |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the originator MMS User Agent |
Earliest Time Of Delivery |
C |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM as specified by the originator MMS User Agent |
Duration Of Transmission |
OM |
The time used for transmission of the MM between the User Agent and the MMS R/S |
Request Status Code |
OM |
The status code of the MM as received in the MM1_submit_REQ |
Delivery Report Requested |
OM |
This field indicates whether a delivery report has been requested by the originator MMS User Agent or not |
Reply Charging |
OC |
A request for reply-charging if specified by the originator MMS User Agent |
Reply Deadline |
OC |
In case of reply-charging the latest time of submission of replies granted to the recipient(s) as specified by the originator MMS User Agent |
Reply Charging Size |
OC |
In case of reply-charging the maximum size for reply-MM(s) granted to the recipient(s) as specified by the originator MMS User Agent |
Priority |
OC |
The priority (importance) of the message if specified by the originator MMS User Agent |
Sender visibility |
OM |
A request to show or hide the sender’s identity when the message is delivered to the recipient as specified by the originator MMS User Agent |
Read reply requested |
OM |
A request for read-reply report as specified in the MM1_submit.REQ |
Status Text |
OC |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated. This field is only present if the MM submission is rejected |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
MMBox Storage Information |
OC |
A set of parameters related to the MMBox management. This parameter is only present if the MMBox feature is supported by the MMS R/S and storage of the MM was requested by originator MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_submit.REQ) |
MSCF Information |
OC |
A set of parameters provided by the MSCF when interacting with the MMS R/S via the MM10 interface prior to the MM1_submit.RES |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.2 Originator MM4 Forward Request record (O4FRq-CDR)
If enabled, an Originator MM4 Forward Request O4FRq-CDR shall be produced in the Originator MMS R/S if and when the Originator MMS R/S has sent an MM4_forward.REQ to the Recipient MMS R/S, regardless of whether or not an MM4_forward.RES is received from the recipient. That is, the CDR is created upon completion of transmission of the MM4_forward.REQ.
The MM4_forward.REQ may be generated as a reaction to an incoming MM1_forward.REQ. In this case, the Originator address field specifies the address of the originator MMS User Agent of the original MM, whereas the address of the forwarding MMS User Agent is contained in the Forwarding address field.
Table 6.1.1.2.1: Originator MM4 Forward Request record (O4FRq-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Originator MM4 Forward Request record |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Originator address |
M |
The address of the originator MMS User Agent of the MM. (If the MM4_forward.REQ is generated as a reaction to an incoming MM1_forward.REQ, this is the address of the originator MMS User Agent of the original MM |
Recipients address list |
M |
The address(es) of the Recipient MMS User Agent(s) of the MM as specified in the MM4_forward.REQ that triggered the CDR |
Recipient address for routing |
M |
The address(es) of the Recipient MMS User Agent(s) of the MM for that routing is requested as specified in the MM4_forward.REQ that triggered the CDR |
Content type |
M |
The content type of the MM content |
Content Class |
Oc |
This field classifies the content of the MM to the smallest content class to which the MM belongs, if specified in the MM4_forward_REQ |
DRM Content |
Oc |
This field indicates if the MM contains DRM-protected content, if specified in the MM4_forward_REQ |
Adaptations |
Oc |
This field indicates if the originator allows adaptation of the content (default True), if specified in the MM4_forward_REQ |
MM component list |
OM |
The list of media components with volume size |
Message size |
M |
The total size of the MM content |
Message class |
C |
The class of the MM (e.g., personal, advertisement, information service) if specified by the Originator MMS User Agent |
Submission Time |
M |
The time at which the MM was submitted or forwarded as specified in the corresponding MM1_submit.REQ or MM1_forwarding.REQ |
Time of Expiry |
C |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the originatorOriginator MMS User Agent |
Delivery Report Requested |
M |
This field indicates whether a delivery report has been requested by the originator MMS User Agent or not |
Priority |
C |
The priority (importance) of the message if specified by the originator MMS User Agent |
Sender visibility |
M |
A request to show or hide the sender’s identity when the message is delivered to the MM recipient if the Originator MMS User Agent has requested her address to be hidden from the recipient |
Read reply requested |
M |
A request for read-reply report if the originator MMS User Agent has requested a read-reply report for the MM |
Acknowledgement Request |
M |
Request for MM4_forward.RES |
Forward counter |
C |
A counter indicating the number of times the particular MM was forwarded |
Forwarding address |
C |
The address(es) of the forwarding MMS User Agent(s). Multiple addresses are possible. |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
M |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OM |
SGSN PLMN Identifier (MCC and MNC) used during this record |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.3 Originator MM4 Forward Response record (O4FRs-CDR)
If enabled, an Originator MM4 Forward Response O4FRs-CDR shall be produced in the Originator MMS R/S if and when, after an MM has been forwarded with an MM4_forward.REQ to the Recipient MMS R/S, the Originator MMS R/S receives a corresponding MM4_forward.RES from the Recipient MMS R/S.
Table 6.1.1.3.1: Originator MM4 Forward Response record (O4FRs-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Originator MM4 Forward Response record |
Originator MMS Relay/Server Address |
OM |
IP address or domain name of the Originator MMS R/S |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Recipient MMS R/S |
Request Status Code |
OM |
The status code of the request to route forward the MM as received in the MM4_forward.RES |
Status Text |
OC |
This field includes the status text as received in the MM4_forward.RES corresponding to the Request Status Code. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.4 Originator MM4 Delivery Report record (O4D-CDR)
If enabled, an Originator MM4 Delivery Report O4D-CDR shall be produced in the Originator MMS R/S if and when the Originator MMS R/S receives an MM4_delivery_report.REQ from the Recipient MMS R/S.
Table 6.1.1.4.1: Originator MM4 Delivery Report record (O4D-CDR)
Field |
Category |
Description |
Record Type |
M |
Originator MM4 Delivery report record |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
OM |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Recipient MMS R/S |
Originator address |
OM |
The address of the originator MMS User Agent of the MM |
Recipient address |
M |
The address of the MM recipient of the MM |
MM Date and time |
M |
Date and time the MM was handled (retrieved, expired, rejected, etc.) as specified in the MM4_delivery_report |
Acknowledgement Request |
M |
Request for MM4_delivery_report.RES |
MM Status Code |
M |
The status code of the delivered MM as received in the MM4_delivery_report.REQ |
Status Text |
OC |
This field includes the status text as received in the MM4_delivery_report.REQ corresponding to the MM Status Code. Present only if provided in the MM4_delivery_report.REQ |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.5 Originator MM1 Delivery Report record (O1D-CDR)
If enabled, an Originator MM1 Delivery Report O1D-CDR shall be produced in the Originator MMS R/S if and when the Originator MMS R/S sends an MM1_delivery_report.REQ to the originator MMS User Agent.
Table 6.1.1.5.1: Originator MM1 Delivery Report record (O1D-CDR)
Field |
Category |
Description |
Record Type |
M |
Originator MM1 Delivery report record |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
OM |
IP address or domain name of the Originator MMS R/S |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Originator address |
OM |
The address of the originator MMS User Agent of the MM |
Recipient address |
M |
The address of the MM recipient of the MM |
MM Status Code |
OM |
The status code of the MM as sent in the MM Status information element in the MM1_delivery_report.REQ |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.6 Originator MM4 Read Reply Report record (O4R-CDR)
If enabled, an Originator MM4 Read Reply Report O4R-CDR shall be produced in the Originator MMS R/S if and when the Originator MMS R/S receives an MM4_read_reply_report.REQ from the Recipient MMS R/S.
Table 6.1.1.6.1: Originator MM4 Read Reply Report record (O4R-CDR)
Field |
Category |
Description |
Record Type |
M |
Originator MM4 Read reply report record |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
OM |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Recipient MMS R/S |
Originator address |
OM |
The address of the originator MMS User Agent of the MM |
Recipient address |
OM |
The address of the MM recipient of the MM |
MM Date and time |
OM |
Date and time the MM was handled (retrieved, expired, rejected, etc.) |
Acknowledgement Request |
M |
Request for MM4_read_reply_report.RES |
Read Status |
OM |
The status of the MM as received in the MM4_read_reply_report.REQ |
Status Text |
OC |
This field includes the status text if received in the MM4_read_reply_report.REQ corresponding to the Read Status. Present only if provided in the MM4_read_reply_report.REQ |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.7 Originator MM1 Read Reply Originator record (O1R-CDR)
If enabled, an Originator MM1 ReadRreply Originator O1R-CDR shall be produced in the Originator MMS R/S if and when the Originator MMS R/S sends an MM1_read_reply_Originator.REQ to the originator MMS User Agent.
Table 6.1.1.7.1: Originator MM1 Read Reply Originator record (O1R-CDR)
Field |
Category |
Description |
Record Type |
M |
Originator MM1 Read reply Originator record |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
OM |
IP address or domain name of the Originator MMS R/S |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Originator address |
OM |
The address of the originator MMS User Agent of the MM |
Recipient address |
OM |
The address of the MM recipient of the MM |
Read Status |
OM |
The status of the MM as sent in the MM1_read_reply Originator.REQ |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.1.8 Originator MM Deletion record (OMD-CDR)
If enabled, an Originator MM Deletion OMD-CDR shall be produced in the Originator MMS R/S, after sending an MM1_submit.RES to the originator MMS User Agent, if and when:
a) the Originator MMS R/S decides to abandon processing of the MM at any point after receiving the corresponding MM1_submit.REQ; or
b) the Originator MMS R/S decides to delete the MM because of expiry of storage time, which may either be indicated in the submit request or governed by operator procedure (e.g. after successful MM delivery).
Abandoning the processing of the MM, or deleting the MM, implies that there remains no knowledge of the MM in the Originator MMS R/S.
The status code indicates the precise reason for abandoning or deleting the MM with respect to the MMS transactions specified in TS 23.140 [201].
This CDR is created regardless of whether the Originator MMS R/S is also the Recipient MMS R/S or not.
Table 6.1.1.8.1: Originator MM Deletion record (OMD-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Originator MM Deletion record |
Originator MMS R/S Address |
OM |
IP address or domain name of the Originator MMS R/S |
Recipient MMS R/S Address |
C |
IP address or domain name of the Recipient MMS R/S. This field is present, if such an address is known |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Message size |
OM |
The total size of the MM content |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OM |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2 MMS records for Recipient MMS R/S
6.1.2.0 General
The following subclauses specify CDRs created in the Recipient MMS R/S based on messages flowing over the MM1 and MM4 interfaces. The CDRs referring to MM4 messages (Recipient MM4 *** CDR) are created only if the Originator and Recipient MMS R/Ss communicate over the MM4 interface (i.e. the Recipient MMS R/S is not also the Originator MMS R/S). The CDRs referring to MM1 messages (Recipient MM1 *** CDR) are created regardless of whether the Recipient MMS R/S is also the Originator MMS R/S or not. Unless otherwise specified the CDR parameters are copied from the corresponding MM1 or MM4 message parameters as applicable.
6.1.2.1 Recipient MM4 Forward record (R4F-CDR)
If enabled, a Recipient MM4 Forward R4F-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM4_forward.REQ from the Originator MMS R/S.
Table 6.1.2.1.1 : Recipient MM4 Forward record (R4F-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM4 Forward record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Originator address |
M |
The address of the originator MMS User Agent of the MM |
Recipients address list |
M |
The address(es) of the recipient MMS User Agent(s) of the -MM |
Content type |
M |
The content type of the MM content |
MM component list |
OM |
The list of media components with volume size |
Message size |
M |
The total size of the MM content |
Message class |
C |
The class selection such as personal, advertisement, information service |
Submission Time |
M |
The time at which the MM was submitted or forwarded as specified in the MM4_forward.REQ |
Time of Expiry |
C |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the originator MMS User Agent |
Delivery Report Requested |
M |
This field indicates whether a delivery report has been requested by the originator MMS User Agent or not |
Priority |
C |
The priority (importance) of the message if specified by the originator MMS User Agent |
Sender visibility |
M |
A request to show or hide the sender’s identity when the message is delivered to the MM recipient if the originator MMS User Agent has requested her address to be hidden from the recipient |
Read reply Requested |
M |
A request for read-reply report if the originator MMS User Agent has requested a read-reply report for the MM |
Request status code |
M |
The status of the request to route forward the MM. If the MM4_forward.REQ is responded by an MM4_forward.RES, this shall be the same information as specified in the Request Status Code information element in the MM4_forward.RES |
Status Text |
C |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated. If the MM4_forward.REQ is responded by an MM4_forward.RES, this shall be the same information as specified in the Status Text information element in the MM4_forward.RES corresponding to the Request Status Code |
Acknowledgement Request |
M |
Request for MM4_forward.RES |
Forward_counter |
C |
A counter indicating the number of times the particular MM was forwarded |
Forwarding address |
C |
The address(es) of the forwarding MMS User Agent(s). Multiple addresses are possible. In the multiple address case this is a Sequential list of the address(es) of the forwarding MMS User Agents who forwarded the same MM |
Record Time stamp |
M |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.2 Recipient MM1 Notification Request record (R1NRq-CDR)
If enabled, a Recipient MM1 Notification Request R1NRq-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S sends an MM1_notification.REQ to the Recipient MMS User Agent.
Table 6.1.2.2.1: Recipient MM1 Notification Request record (R1NRq -CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM1 Notification Request record |
Recipient MMS R/S Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Reply Charging ID |
C |
This field is present in the CDR only if the MM is a reply-MM to an original MM. The Reply-Charging ID is the Message ID of the original MM |
Sender address |
M |
The address of the MMS User Agent as used in the MM1_notification_REQ. This parameter is present in the CDR regardless of address hiding |
Recipient address |
M |
The address of the MM recipient of the MM |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the Recipient MMS User Agent |
Message class |
M |
The class selection such as personal, advertisement, information service; default = personal |
MM component list |
OM |
The list of media components with volume size |
Message size |
OM |
The total size of the MM content |
Time of Expiry |
OM |
The date of expiry or duration of time prior to expiry for the MM |
Message Reference |
M |
A reference, e.g., URI, for the MM |
Delivery Report Requested |
OM |
This field indicates whether a delivery report is requested or not as specified in the MM1_notification.REQ |
Reply Charging |
OC |
Information that a reply to this particular original MM is free of charge as specified in the MM1_notification.REQ |
Reply Deadline |
OC |
In case of reply-charging the latest time of submission of a reply granted to the recipient as specified in the MM1_notification.REQ |
Reply Charging-Size |
OC |
In case of reply-charging the maximum size of a reply-MM granted to the recipient as specified in the MM1_notification.REQ |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated. |
MSCF Information |
OC |
A set of parameters provided by the MSCF when interacting with the MMS R/S via the MM10 interface prior to the MM1_notification.REQ |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Replace-ID |
OC |
If present, this parameter holds the Identifier of the previous MM that is replaced by the current MM, if requested by a VASP |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
VAS-Id |
OC |
This field indicates the VAS that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
VASP-Id |
OC |
This field indicates the VASP that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.3 Recipient MM1 Notification Response record (R1NRs-CDR)
If enabled, a Recipient MM1 Notification Response R1NRs-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM1_notification.RES from the Recipient MMS User Agent.
Table 6.1.2.3.1: Recipient MM1 Notification Response record (R1NRs-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM1 Notification Response record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Recipient address |
M |
The address of the MM recipient of the MM |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the Recipient MMS User Agent |
Report allowed |
C |
Request to allow or disallow the sending of a delivery report to the MM Originator if specified in the MM1_notification_RES |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.4 Recipient MM1 Retrieve record (R1Rt-CDR)
If enabled, a Recipient MM1 Retrieve R1Rt-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S has sent an MM1_retrieve.RES to the Recipient MMS User Agent. That is, the CDR is created upon completion of transmission of the MM1_retrieve.RES.
Table 6.1.2.4.1: Recipient MM1 Retrieve record (R1Rt-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Recipient MM1 Retrieve record |
Recipient MMS R/S Address |
M |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Reply Charging ID |
C |
This field is present in the CDR only if the MM is a reply-MM to an original MM. The Reply-Charging ID is the Message ID of the original MM. |
Sender address |
C |
The address of the MMS User Agent as used in the MM1_retrieve.RES, or the address of VASP as used in the MM7_submit.REQ. This parameter is present in the CDR regardless of address hiding. |
Recipient address |
M |
The address of the Recipient MM User Agent of the MM. |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Message Reference |
M |
Location of the content of the MM to be retrieved as specified in the MM1_retrieve.REQ. |
Original MM Content Content type Message size MM component list |
M |
This parameter contains a set of information elements related to the original MM. |
M |
The content type of the MM content. |
|
OM |
The total size of the original MM content. |
|
OM |
The list of media components with volume size. |
|
Adapted MM Content Content type Message size MM component list |
C |
If the MM content is adapted prior to its retrieval, this parameter is present and contains the resulting set of information elements related to the adapted MM. |
C |
The content type of the adapted MM content. |
|
OC |
The total size of the adapted MM content. |
|
OC |
The list of media components with volume size of the adapted MM. |
|
Message class |
OC |
The class of the message (e.g., personal, advertisement, information service) if specified in the MM1_retrieve.RES |
Submission Time |
M |
The time at which the MM was submitted or forwarded as specified in the MM1_retrieve.RES |
Delivery report Requested |
OM |
A request for delivery report as specified in the Delivery Report information element in the MM1_retrieve.RES |
Priority |
OC |
The priority (importance) of the message if specified in the MM1_retrieve.RES |
Read reply Requested |
OC |
A request for read-reply report if specified in the Read Reply information element in the MM1_retrieve.RES |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Replace-ID |
OC |
If present, this parameter holds the Identifier of the previous MM that is replaced by the current MM, if requested by a VASP |
Reply Deadline |
OC |
In case of reply-charging the latest time of submission of a reply granted to the recipient as specified in the MM1_retrieve.RES |
Reply Charging-Size |
OC |
In case of reply-charging the maximum size of a reply-MM granted to the recipient as specified in the MM1_retrieve.RES |
Duration Of Transmission |
OM |
The time used for transmission of the MM between the User Agent and the MMS R/S |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
VAS-Id |
OC |
This field indicates the VAS that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
VASP-Id |
OC |
This field indicates the VASP that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.5 Recipient MM1 Acknowledgement record (R1A-CDR)
If enabled, a Recipient MM1 Acknowledgement R1A-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM1_acknowledgement.REQ from the Recipient MMS User Agent.
Table 6.1.2.5.1: Recipient MM1 Acknowledgement record (R1A-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM1 Acknowledgement record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Recipient address |
M |
The address of the Recipient MM User Agent of the MM |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Report allowed |
C |
Request to allow or disallow the sending of a delivery report to the MM Originator if specified in the MM1_acknowledgement.RES |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.6 Recipient MM4 Delivery Report Request record (R4DRq-CDR)
If enabled, a Recipient MM4 Delivery Report Request R4DRq-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S sends an MM4_delivery_report.REQ to the Originator MMS R/S.
Table 6.1.2.6.1: Recipient MM4 Delivery Report Request record (R4DRq-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM4 Delivery report Request record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Recipient MMS R/S |
Originator address |
M |
The address of the originator MMS User Agent of the MM |
Recipient address |
M |
The address of the MM recipient of the MM |
MM Date and time |
OM |
Date and time the MM was handled (retrieved, expired, rejected, etc.) |
Acknowledgement Request |
M |
Request for MM4_delivery_report.RES |
MM Status Code |
OM |
The status code of the MM as sent in the MM4_delivery_report.REQ |
Status Text |
OC |
This field includes the status text as sent in the MM4_delivery_report.REQ corresponding to the MM Status Code |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OM |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.7 Recipient MM4 Delivery Report Response record (R4DRs-CDR)
If enabled, a Recipient MM4 Delivery Report Response R4DRs-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM4_delivery_report.RES from the Originator MMS R/S.
Table 6.1.2.7.1: Recipient MM4 Delivery Report Response record (R4DRs-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM4 Delivery report Response record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Request Status Code |
OM |
The status code of the MM as received in the MM4_delivery_report.RES |
Status Text |
OC |
This field includes the status text as received in the MM4_delivery_report.RES corresponding to the Request Status Code |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.8 Recipient MM1 Read Reply Recipient record (R1RR-CDR)
If enabled, a Recipient MM1 Read Reply Recipient R1RR-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM1_read_reply_recipient.REQ from the Recipient MMS User Agent.
Table 6.1.2.8.1: Recipient MM1 Read Reply Recipient record (R1RR-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM1 Read reply Recipient record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Recipient address |
M |
The address of the Recipient MM User Agent of the MM |
Originator address |
M |
The address of the MM Originator of the original MM, i.e., the recipient of the read-reply report |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.9 Recipient MM4 Read Reply Report Request record (R4RRq-CDR)
If enabled, a Recipient MM4 Read Reply Report Request R4RRq-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S sends an MM4_read_reply_report.REQ to the Originator MMS R/S.
Table 6.1.2.9.1: Recipient MM4 Read Reply Report Request record (R4RRq-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM4 read reply report Request record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Recipient MMS R/S |
Originator address |
M |
The address of the originator MMS User Agent of the MM |
Recipient address |
M |
The address of the MM recipient of the MM |
MM Date and time |
OM |
Date and time the MM was handled (retrieved, expired, rejected, etc.) |
Acknowledgement Request |
M |
Request for MM4_read_reply_report.RES |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.10 Recipient MM4 Read Reply Report Response record (R4RRs-CDR)
If enabled, a Recipient MM4 Read Reply Report Response R4RRs-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM4_read_reply_report.RES from the Originator MMS R/S.
Table 6.1.2.10.1: Recipient MM4 DeliveryRead Reply Report Response record (R4DRRs-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM4 Read reply report Response record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Request Status Code |
OM |
The status code of the MM as received in the MM4_read_reply_report.RES |
Status Text |
OC |
This field includes a more detailed technical status if received in the MM4_read_reply_report.RES corresponding to the Request Status Code |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.11 Recipient MM1 Cancellation record (R1C-CDR)
If enabled, a Recipient MM1 Cancellation R1C-CDR shall be produced in the Recipient MMS R/S if and when the Recipient MMS R/S receives an MM1_Cancel.RES from the Recipient MMS User Agent.
Table 6.1.2.11.1: Recipient MM1 Cancellation record (R1C-CDR)
Field |
Category |
Description |
Record Type |
M |
Recipient MM1 Cancellation record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Cancel ID |
M |
The identification of the cancelled MM |
3GPP MMS Version |
OM |
The MMS version of the Originator MMS R/S |
Request Status Code |
OM |
The status code of the cancellation as received in the MM1_Cancel.RES |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.2.12 Recipient MM Deletion record (RMD-CDR)
If enabled, a Recipient MM Deletion RMD-CDR shall be produced in the Recipient MMS R/S if and when:
1) the Recipient MMS R/S decides to abandon processing of the MM at any point after receiving the corresponding MM4_forward.REQ; or
2) the Recipient MMS R/S decides to delete the MM because of expiry of storage time, which may either be indicated in the submit request or governed by operator procedure(e.g. after successful MM delivery); or
3) The Recipient MMS R/S decides to delete the MM prior to the expiry of storage time because it received a request to delete a deferred MM (i.e. MM for that retrieval has been deferred) from the recipient MMS User Agent in the corresponding MM1_delete.REQ and before an MM1_cancel.REQ, if any, is sent to the recipient MMS User Agent.
Abandoning the processing of the MM implies that there remains no knowledge of the MM in the Recipient MMS R/S.
The status code indicates the precise reason for abandoning or deleting the MM with respect to the MMS transactions specified in TS 23.140 [201].
A special case is where the Recipient MMS R/S is also the Forwarding MMS R/S. In this case only the Originator MM Deletion CDR specified in clause 6.1.1.8 is required.
Table 6.1.2.12.1: Recipient MM Deletion record (RMD-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
Recipient MM Deletion record |
Originator MMS Relay/Server Address |
M |
IP address or domain name of the Originator MMS R/S |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Message size |
OM |
The total size of the MM content |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of delivering the message |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.3 MMS records for Forwarding MMS R/S
6.1.3.1 Forwarding record (F-CDR)
If enabled, a Forwarding F-CDR shall be produced in the Forwarding MMS R/S on receipt of an MM1_forward.REQ if and when the Forwarding MMS R/S responds with an MM1_forward.RES indicating acceptance.
Table 6.1.3.1 : MM Forwarding record (F-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM Forwarding record |
Forwarding MMS Relay/Server Address |
M |
IP address or domain name of the Forwarding MMS R/S |
Message ID |
M |
The MM identification provided by the Originator MMS R/S |
Forwarding address |
M |
One or more addresses of the forwarding MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_forward.REQ) |
Recipients address list |
M |
The address(es) of the Recipient MMS User Agent(s) of the forwarded MM. Multiple addresses are possible |
Charge Information |
OM |
The charged party indication and charge type |
Time of Expiry |
OC |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the forwarding MMS User Agent |
Earliest Time Of Delivery |
OC |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM |
Delivery Report Requested |
OM |
This field indicates whether a delivery report has been requested by the forwarding MMS User Agent or not |
Read reply requested |
OM |
A request for read-reply report as specified in the MM1_forward.REQ |
Message reference |
M |
A reference, e.g., URI, for the MM as specified in the MM1_forward.REQ |
MM Status Code |
OM |
The status code of the MM at the time when the CDR is generated |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
MMBox Storage Information |
OC |
A set of parameters related to the MMBox management. This parameter is only present if the MMBox feature is supported by the MMS R/S and storage of the MM was requested by the forwarding MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_forward.REQ) |
Reply Charging |
OC |
A request for reply-charging if specified by the forwarding MMS User Agent |
Reply Deadline |
OC |
In case of reply-charging the latest time of submission of replies granted to the recipient(s) as specified by the forwarding MMS User Agent |
Reply Charging Size |
OC |
In case of reply-charging the maximum size for reply-MM(s) granted to the recipient(s) as specified by the forwarding MMS User Agent |
Serving network identity |
OM |
SGSN PLMN Identifier (MCC and MNC) used during this record |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension |
6.1.4 Service records for MMS R/S supporting MMBoxes
6.1.4.1 MMBox MM1 Store record (Bx1S-CDR)
If enabled, an MMBox MM1 Store Bx1S-CDR shall be produced in the MMS R/S if and when the MMS R/S responds with an MM1_mmbox_store.RES to the MMS User Agent.
Table 6.1.4.1.1: MMBox MM1 Store record (Bx1S-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MMBox MM1 Store record |
MMS Relay/Server Address |
M |
An address of the MMS R/S |
Managing address |
M |
The address of the managing MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_mmbox_store.REQ) |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent |
Content type |
OM |
The content type of the MM content |
Message size |
OM |
The size of the MM |
Message Reference |
OM |
A reference to the newly stored or updated MM, suitable for subsequent usage (e.g.: with MM1_retrieve.REQ and MM1_mmbox_delete.REQ) |
MM State |
OM |
The state of the MM. If not present when the Message Reference is from a notification request, defaults to New. No value is assumed when the Message Reference refers to an already stored MM |
MM Flags |
OC |
If available, the keyword flags of the MM. There are no defaults |
Store status |
OC |
The status code of the request to store the MM as received in the MM1_store.RES |
Store Status Text |
OC |
This field includes a more detailed technical description of the store status at the point in time when the CDR is generated. This field is only present if the store status is present |
Sequence Number |
OM |
Record number |
Time Stamp |
OM |
Time of generation of the CDR |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record |
6.1.4.2 MMBox MM1 View record (Bx1V-CDR)
If enabled, an MMBox MM1 View Bx1V-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM1_mmbox_view.RES to the MMS User Agent.
Table 6.1.4.2.1: MMBox MM1 View record (Bx1V-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MMBox MM1 View record |
MMS Relay/Server Address |
M |
An address of the MMS R/S. |
Managing address |
M |
The address of the managing MMS User Agent (i.e., of the MMS User Agent that has sent the MM1_mmbox_view.REQ). |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Attributes list |
OM |
A list of information elements that are to be returned as a group for each MM to be listed in the MM1_mmbox_view.RES. If absent, the default list (i.e. Message ID, Date and time, Sender address, Subject, Message size, MM State, and MM Flags) shall apply. |
Message Selection |
OM |
A list of MM State or MM Flags keywords (e.g. new or draft) or a list of Message Reference by which MMs within the MMBox can be selected. If both are absent, a listing of all MMs currently stored within the MMBox shall be selected. |
Start |
OM |
A number, indicating the index of the first MM of those selected to have information elements returned in the response. If this is absent, the first item selected is returned. |
Limit |
OM |
A number indicating the maximum number of selected MMs to their information elements returned in the response. If this is absent, information elements from all remaining MMs are returned. |
Totals requested |
OM |
This field indicates whether the current total number of messages and/or size contained by the MMBox has been requested by the managing MMS User Agent. |
Quotas requested |
OM |
This field indicates whether the current message and/or size quotas (i.e. the maximum number of messages allowed and/or the maximum size allowed) has been requested by the managing MMS User Agent. |
MM listing |
OM |
The requested listing of the selected MMs, which shall be one or more groups of information elements, one for each MM listed. Each MM group shall include: a Message Reference, and may include additional information elements as well. If absent, no MMs were found or selected. |
Request Status Code |
OM |
The status code of the request to view the MM as received in the MM1_view.RES. |
Status Text |
OC |
This field includes the status text as received in the MM1_view.RES corresponding to the Request Status Code. Present only if provided in the MM1_view.RES. |
Totals |
OC |
The total number of messages and/or octets for the MMBox, identified with Messages or Octets, respectively, depending upon the presence of Totals in the request. |
Quotas |
OC |
The quotas of the MMBox in messages and/or octets identified with Messages or Octets, respectively, depending upon the presence of Quotas in the request. |
Sequence Number |
OM |
Record number. |
Time Stamp |
OM |
Time of generation of the CDR. |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record. |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.4.3 MMBox MM1 Upload record (Bx1U-CDR)
If enabled, an MMBox MM1 Upload Bx1U-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM1_mmbox_upload.RES to the MMS User Agent.
Table 6.1.4.3.1: MMBox MM1 Upload record (Bx1U-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MMBox MM1 Upload record |
MMS Relay/Server Address |
M |
An address of the MMS R/S. |
Managing address |
M |
The address of the managing MMS User Agent (i.e., of the MMS User Agent that sends the MM1_mmbox_upload.REQ). |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Message class |
OC |
The class of the MM (e.g., personal, advertisement, information service) if provided by the MMS User Agent. |
Upload Time |
OM |
The time and date at which the MM was uploaded (time stamp). |
Time of Expiry |
OC |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the originator MMS User Agent |
Earliest Time Of Delivery |
OC |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM if specified by the originator MMS User Agent |
Priority |
OC |
This field indicates the priority (importance) of the message if specified by the MMS User Agent, |
MM State |
OM |
The state of the MM. Will default to the Draft state if absent |
MM Flags |
OC |
If available, the keyword flags of the MM. There are no defaults. |
Content type |
OM |
The content type of the MM content. |
Message size |
OM |
The size of the MM. |
Message Reference |
OM |
A reference to the newly stored MM, suitable for subsequent usage (e.g.: with MM1_retrieve.REQ, MM1_mmbox_delete.REQ, etc.). |
Request Status Code |
OM |
The status code of the request to view the MM as received in the MM1_upload.RES. |
Status Text |
OC |
This field includes the status text as received in the MM1_upload.RES corresponding to the Request Status Code. Present only if provided in the MM1_upload.RES. |
Sequence Number |
OM |
Record number. |
Time Stamp |
OM |
Time of generation of the CDR. |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record. |
RAT Type |
OC |
The radio access technology used during this record.. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.4.4 MMBox MM1 Delete record (Bx1D-CDR)
If enabled, an MMBox MM1 Delete Bx1D-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM1_mmbox_delete.RES to the MMS User Agent.
Table 6.1.4.4.1: MMBox MM1 Delete record (Bx1D-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MMBox MM1 Delete record |
MMS Relay/Server Address |
M |
An address of the MMS R/S. |
Managing address |
M |
The address of the managing MMS User Agent (i.e., of the MMS User Agent that sends the MM1_mmbox_upload.REQ). |
Access Correlation |
OM |
A unique identifier delivered by the used access network domain of the originator MMS User Agent. |
Message Reference |
OC |
A reference to the message in error, if any, to which the following information elements apply |
Request Status Code |
OM |
The status code of the request to view the MM as received in the MM1_delete.RES. |
Status Text |
OC |
This field includes the status text as received in the MM1_delete.RES corresponding to the Request Status Code. Present only if provided in the MM1_delete.RES. |
Sequence Number |
OM |
Record number. |
Time Stamp |
OM |
Time of generation of the CDR. |
Serving network identity |
OC |
If present this parameter holds the SGSN PLMN Identifier (MCC and MNC) used during this record. |
RAT Type |
OC |
The radio access technology used during this record. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MMS User Agent is currently located, if available. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.5 MMS records for MMS VAS applications
6.1.5.0 General
The following subclauses specify CDRs created in the Originator MMS R/S based on messages flowing over the MM7 reference point. Unless otherwise specified, the CDR parameters are copied from the corresponding MM7 message parameters as applicable.
6.1.5.1 MM7 Submission record (MM7S-CDR)
If enabled, an MM7 Submission MM7S-CDR shall be produced in the MMS R/S for each MM submitted in an MM7_submit.REQ by a VASP to the MMS R/S if and when the MMS R/S responds with an MM7_submit.RES. The operator can configure whether this CDR, if enabled, shall only be created for MM7_submit.RES indicating acceptance of the submitted MM, or also for the unsuccessful submissions.
Table 6.1.5.1.1: MM7 Submission record (MM7S-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM7 Submission record. |
Originator MMS Relay/Server Address |
M |
.IP address or domain name of Originator MMS R/S. |
Linked ID |
C |
This field is present in the CDR only if the MM defines a correspondence to a previous message that was delivered by the MMS R/S. The MM identification provided by the Originator MMS R/S. |
VASP ID |
M |
Identifier of the VASP for this MMS R/S |
VAS ID |
M |
Identifier of the originating application. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator Address |
M |
The address of the MM Originator. |
Recipients address list |
M |
The address(es) of the Recipient MMS User Agent(s) of the MM. Multiple addresses are possible if the MM is not a reply MM. |
Service code |
OC |
Charging related information that is used directly for billing purposes |
Content type |
M |
The content type of the MM content. |
Content Class |
OC |
This field classifies the content of the MM to the smallest content class to which the MM belongs, if specified in the MM7_submit_REQ |
DRM Content |
OC |
This field indicates if the MM contains DRM-protected content, if specified in the MM7_submit_REQ |
Adaptations |
OC |
This field indicates if the Originator allows adaptation of the content (default True), if specified in the MM7_submit_REQ |
MM component list |
OM |
The list of media components with volume size. |
Message size |
M |
The total size of the MM content. |
Message class |
OC |
The class selection such as personal, advertisement, information service if specified in the MM7_submit_REQ. |
Charge Information |
OM |
The charged party indication and charge type e.g. the sending, receiving, both parties, third party or neither. |
Submission Time |
OC |
The time at which the MM was submitted from the VASP if specified in the MM7_submit_REQ. |
Time of Expiry |
OC |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the VASP |
Earliest Time Of Delivery |
C |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM if specified by the VASP |
Delivery Report Requested |
OM |
This field indicates whether a delivery report has been requested by the VASP or not. |
Reply Charging |
OC |
A request for reply-charging if specified by the VASP |
Read reply requested |
OM |
A request for read-reply report as specified in the MM7_submit.REQ. |
Reply Deadline |
OC |
In case of reply-charging the latest time of submission of replies granted to the recipient(s) as specified by the VASP |
Reply Charging Size |
OC |
In case of reply-charging the maximum size for reply-MM(s) granted to the recipient(s) as specified by the VASP |
Priority |
OC |
The priority (importance) of the message if specified by the VASP |
Charged Party ID |
OC |
The address of the third party which is expected to pay for the MM. |
Message Distribution Indicator |
OC |
This field is present if specified in the MM7_submit.REQ If set to "false" the VASP has indicated that content of the MM is not intended for redistribution. If set to "true" the VASP has indicated that content of the MM can be redistributed. |
Request Status Code |
OM |
The status code of the associated MM7_submit_REQ |
Status Text |
OC |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated. This field is only present if the MM submission is rejected. |
MSCF Information |
OC |
A set of parameters provided by the MSCF when interacting with the MMS R/S via the MM10 interface prior to the MM7_submit.RES |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.2 MM7 Deliver Request record (MM7DRq-CDR)
If enabled, a MM7 Deliver Request MM7DRq-CDR shall be produced in the MMS R/S if and when the MMS R/S sends an MM7_deliver.REQ to the Recipient MMS VASP.
Table 6.1.5.2.1: MM7 Deliver Request record (MM7DRq -CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Deliver Request record. |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S. |
Linked ID |
C |
This field is present in the CDR only if the MM defines a correspondence to a previous message that was delivered by the MMS R/S. The MM identification provided by the Originator MMS R/S. |
Reply Charging ID |
C |
This field is present in the CDR only if the MM is a reply-MM to an original MM. The Reply-Charging ID is the Message ID of the original MM. |
Originator address |
M |
The address of the MMS User Agent as used in the MM7_deliver_REQ. |
Recipient address |
M |
The address of the MM recipient of the MM. |
MM component list |
OM |
The list of media components with volume size. |
Message size |
OM |
The total size of the MM content. |
Content type |
M |
The content type of the MM content. |
MMS User Agent Capabilities |
OC |
Information about the capabilities of the MMS User Agent that originated the MM. Present only if provided in the MM7_deliver.REQ. |
Priority |
OC |
The priority (importance) of the message if specified by the VASP |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.3 MM7 Deliver Response record (MM7DRs-CDR)
If enabled, a MM7 Deliver Response MM7DRs-CDR shall be produced in the MMS R/S if and when the MMS R/S receives an MM7_deliver.RES from the Recipient MMS VASP.
Table 6.1.5.3.1: MM7 Deliver Response record (MM7DRs-CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Deliver Response record. |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Recipient address |
M |
The address of the MM recipient of the MM. |
Service code |
OC |
Charging related information that is used directly for billing purposes |
Request Status Code |
OM |
The status code of the associated MM7_deliver_REQ |
Status Text |
OM |
This field includes a more detailed technical status of the message at the point in time when the CDR is generated. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.4 MM7 Cancel record (MM7C-CDR)
If enabled, an MM7 Cancel MM7C-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM7_cancel.RES to the MMS VASP.
Table 6.1.5.4.1: MM7 Cancel record (MM7C-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM7 Cancel record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of Recipient MMS R/S. |
VASP ID |
M |
Identifier of the VASP for this MMS R/S |
VAS ID |
M |
Identifier of the originating application. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator Address |
M |
The address of the MM Originator. |
Content Class |
OC |
This field classifies the content of the MM to the smallest content class to which the MM belongs, if specified in the MM7_cancel_REQ |
DRM Content |
OC |
This field indicates if the MM contains DRM-protected content, if specified in the MM7_ cancel_REQ |
Adaptations |
OC |
This field indicates if the Originator allows adaptation of the content (default True), if specified in the MM7_ cancel_REQ |
Request Status Code |
OM |
The status code of the associated MM7_cancel.REQ. |
Status Text |
OC |
This field includes the status text as received in the MM7_cancel.RES corresponding to the Request Status Code. Present only if provided in the MM7_cancel.RES. |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Sequence Number |
OM |
Record number. |
Time Stamp |
OM |
Time of generation of the CDR. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.5.5 MM7 Replace record (MM7R-CDR)
If enabled, an MM7 Replace MM7R-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM7_replace.RES to the MMS VASP.
Table 6.1.5.5.1: MM7 Replace record (MM7R-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM7 Replace record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of Recipient MMS R/S. |
VASP ID |
M |
Identifier of the VASP for this MMS R/S |
VAS ID |
M |
Identifier of the originating application. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator Address |
M |
The address of the MM Originator. |
Service code |
OC |
Charging related information that is used directly for billing purposes |
Content type |
M |
The content type of the MM content. |
Submission time |
OC |
The time at which the MM was submitted from the VASP if specified in the MM7_replace_REQ. |
Time of Expiry |
OC |
The desired date of expiry or duration of time prior to expiry for the MM if specified by the VASP |
Earliest Time Of Delivery |
OC |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM if specified by the VASP |
Request Status Code |
OM |
The status code of associated MM7_replace.REQ. |
Status Text |
OC |
This field includes the status text as received in the MM7_replace.RES corresponding to the Request Status Code. Present only if provided in the MM7_replace.RES. |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Sequence Number |
OM |
Record number |
Time Stamp |
OM |
Time of generation of the CDR. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.5.6 MM7 Delivery Report Request record (MM7DRRq-CDR)
If enabled, a MM7 Delivery Report Request MM7DRRq-CDR shall be produced in the MMS R/S if and when the MMS R/S sends an MM7_delivery_report.REQ to the MMS VASP.
Table 6.1.5.6.1: MM7 Delivery Report Request record (MM7DRRq-CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Delivery Report Requestrecord. |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator address |
OM |
The address of the VAS that submitted the original MM. |
Recipient address |
M |
The address of the MM recipient of the MM. |
MM Date and time |
M |
Date and time the MM was handled (retrieved, expired, rejected, etc.) as specified in the MM7_delivery_report.REQ. |
MM Status Code |
M |
The status code of the delivered MM as received in the MM7_delivery_report.RES. |
MM Status Text |
OC |
This field includes the status text as received in the MM7_delivery_report.RES corresponding to the MM Status Code. Present only if provided in the MM7_delivery_report.RES. |
MMS User Agent Capabilities |
OC |
Information about the capabilities of the MMS User Agent that originated the MM. Present only if provided in the MM7_delivery_report.REQ. |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.7 MM7 Delivery Report Response record (MM7DRRs-CDR)
If enabled, an MM7 Delivery Report Response MM7DRRs-CDR shall be produced in the MMS R/S if and when the MMS R/S receives an MM7_delivery_report.RES from the MMS VASP.
Table 6.1.5.7.1: MM7 Delivery Report Response record (MM7DRRs-CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Delivery Report Response record. |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator address |
OM |
The address of the VAS that submitted the original MM. |
Recipient address |
M |
The address of the MM recipient of the MM. |
Request Status Code |
OM |
The status code of the associated MM7_delivery_report.REQ. |
Status Text |
OC |
This field includes the status text as received in the MM7_delivery_report.RES corresponding to the Request Status Code. Present only if provided in the MM7_delivery_report.RES. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.8 MM7 Read Reply Report Request record (MM7RRq-CDR)
If enabled, a MM7 Read Reply Report Request MM7RRq-CDR shall be produced in the MMS R/S if and when the Recipient MMS R/S sends an MM7_read reply_report.REQ to the MMS VASP.
Table 6.1.5.8.1: MM7 Read Reply Report Request record (MM7RRq-CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Read reply report Requestrecord. |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator address |
OM |
The address of the VAS that submitted the original MM. |
Recipient address |
M |
The address of the MM recipient of the MM. |
MM Date and time |
M |
Date and time the MM was handled (retrieved, expired, rejected, etc.) as specified in the MM7_Read reply_report.REQ. |
Read Status |
M |
The status of the MM (e.g. Read, deleted without being read, etc.) as sent in the MM7_read_reply_report.REQ. |
MM Status Text |
OC |
This field includes the status text as received in the MM7_read reply_report.RES corresponding to the Read Status. Present only if provided in the MM7_read reply_report.REQ. |
Applic-ID |
OC |
If present, this field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply-Applic-ID |
OC |
If present, this parameter indicates a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux-Applic-Info |
OC |
If present, this parameter indicates additional application/implementation specific control information. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.9 MM7 Read Reply Report Response record (MM7RRs-CDR)
If enabled, an MM7 Read Reply Report Response MM7RRs-CDR shall be produced in the MMS R/S if and when the MMS R/S receives an MM7_Read reply_report.RES from the Originator MMS VASP.
Table 6.1.5.9.1: MM7 Read Reply Report Response record (MM7RRs-CDR)
Field |
Category |
Description |
Record Type |
M |
MM7 Read reply report Response record. |
Recipient MMS Relay/Server Address |
OM |
IP address or domain name of the Recipient MMS R/S. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Originator address |
OM |
The address of the VAS that submitted the original MM. |
Recipient address |
M |
The address of the MM recipient of the MM. |
Request Status Code |
OM |
The status code of the associated MM7_read reply_report.REQ. |
Status Text |
OC |
This field includes the status text as received in the MM7_read reply_report.RES corresponding to the Request Status Code. Present only if provided in the MM7_read reply_report.RES. |
Record Time Stamp |
OM |
Time of generation of the CDR |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5.10 MM7 Extended Cancel record (MM7EC-CDR)
If enabled, an MM7 Extended Cancel MM7EC-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM7_extended_cancel.RES to the MMS VASP.
Table 6.1.5.10.1: MM7 Extended Cancel record (MM7EC-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM7 Extended Cancel record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of Recipient MMS R/S. |
VASP ID |
M |
Identifier of the VASP for this MMS R/S |
VAS ID |
M |
Identifier of the originating application. |
Cancel ID |
M |
The identification of the cancelled MM |
Request Status Code |
OM |
The status code of the associated MM7_cancel.REQ. |
Sequence Number |
OM |
Record number. |
Time Stamp |
OM |
Time of generation of the CDR. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.1.5.11 MM7 Extended Replace record (MM7ER-CDR)
If enabled, an MM7 Extended Replace MM7ER-CDR shall be produced in the MMS R/S if and when the MMS R/S has sent an MM7_extended_replace.RES to the MMS VASP.
Table 6.1.5.11.1: MM7 Extended Replace record (MM7ER-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MM7 Extended Replace record |
Recipient MMS Relay/Server Address |
M |
IP address or domain name of Recipient MMS R/S. |
VASP ID |
M |
Identifier of the VASP for this MMS R/S |
VAS ID |
M |
Identifier of the originating application. |
Message ID |
M |
The MM identification provided by the Originator MMS R/S. |
Service code |
OC |
Charging related information that is used directly for billing purposes |
Content type |
M |
The content type of the MM content. |
Submission time |
OC |
The time at which the MM was submitted from the VASP if specified in the MM7_replace_REQ. |
Earliest Time Of Delivery |
OC |
This field contains either the earliest time to deliver the MM or the number of seconds to wait before delivering the MM if specified by the VASP |
Request Status Code |
OM |
The status code of associated MM7_extended_replace.REQ. |
Sequence Number |
OM |
Record number |
Time Stamp |
OM |
Time of generation of the CDR. |
Record extensions |
OC |
A set of network/manufacturer specific extensions to the record. |
6.2 Data description for MMS online charging
6.2.1 Ro message contents
6.2.1.0 General
The MMS R/S generate Debit / Reserve Units information that can be transferred from the CTF to the OCF. For this purpose, MMS online charging utilises the Debit Units and Reserve Units procedure that is specified in the 3GPP Debit / Reserve Units operation in TS 32.299 [50].
The Debit / Reserve Units procedure employs the Debit / Reserve Units Request and Debit / Reserve Units Response messages.
Table 6.2.1.1 describes the use of these messages for MMS online charging.
Table 6.2.1.1: MMS online charging messages contents
Message |
Source |
Destination |
Debit / Reserve Units Request |
MMS R/S |
OCS |
Debit / Reserve Units Response |
OCS |
MMS R/S |
This clause describes the different Information Elements (IE) used in the Debit / Reserve Units messages and the charging data configuration defined in clause 5.4 of TS 32.240 [1].
Note that not for all structured IEs the individual parameters are listed in the table. Detailed descriptions of the IEs are provided in TS 32.299 [50].
6.2.1.1 Debit / Reserve Units Request message
Table 6.2.1.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from MMS R/S as used for MMS online charging.
Table 6.2.1.1.1: Debit / Reserve Units Request message contents for MMS
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
This field identifies the operation session. |
Originator Host |
M |
This field contains the identification of the source point of the operation. |
Originator Domain |
M |
This field contains the realm of the operation Originator. |
Destination Domain |
M |
This field contains the realm of the operation destination. |
Operation Identifier |
M |
This field is a unique operation identifier. |
Operation Token |
M |
This field contains the service identifier. |
Operation Type |
M |
This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number |
M |
This field contains the sequence number of the transferred messages. |
Destination Host |
OC |
This field contains the identification of the destination point of the operation. |
User Name |
OC |
This field contains the identification of the user. |
Origination State |
– |
Not used for MMS in 3GPP. |
OrignationTimestamp |
OC |
This field contains the time when the operation is requested. |
Subscriber Identifier |
OM |
This field contains the identification of the mobile subscriber (i.e. MSISDN) that uses the requested service. |
Termination Cause |
– |
Not used for MMS in 3GPP. |
Requested Action |
OC |
This field contains the requested action. |
Multiple Operation |
OM |
This field indicate the occurrence of multiple operations. |
Multiple Unit Operation |
OC |
This field contains the parameter for the quota management. |
Subscriber Equipment Number |
– |
Not used for MMS in 3GPP. |
Proxy Information |
OC |
This field contains the parameter of the proxy. |
Route Information |
OC |
This field contains the parameter of the route. |
Service Information |
OM |
This field holds the MMS specific parameter and is described in clause 6.3. |
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 MMS charging. This message is always used by the OCS as specified below, independent of the receiving MMS R/S and the operation type that is being replied to.
Table 6.2.1.2.1: Debit / Reserve Units Response message contents for MMS
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
This field identifies the operation session. |
Operation Result |
M |
This field identifies the result of the operation. |
Originator Host |
M |
This field contains the identification of the source point of the operation. |
Originator Domain |
M |
This field contains the realm of the operation Originator. |
Operation Identifier |
M |
This field is a unique operation identifier. |
Operation Type |
M |
This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number |
M |
This field contains the sequence number of the transferred messages. |
Operation Failover |
– |
Not used for MMS in 3GPP. |
Multiple Unit Operation |
OC |
This field contains the parameter for the quota management. |
Operation Failure Action |
OC |
This field defines the operation if a failure has occurred at the OCS for ECUR. |
Operation Event Failure Action |
OC |
This field defines the operation if a failure has occurred at the OCS for IEC. |
Redirection Host |
– |
Not used for MMS in 3GPP. |
Redirection Host Usage |
– |
Not used for MMS in 3GPP. |
Redirection Cache Time |
– |
Not used for MMS in 3GPP. |
Proxy Information |
OC |
This field contains the parameter of the proxy. |
Route Information |
OC |
This field contains the parameter of the route. |
Failed parameter |
OC |
This field contains missing and/or unsupported parameter that caused the failure. |
Service Information |
– |
Not used for MMS in 3GPP. |
6.2a Data description for MMS converged charging
6.2a.1 Message contents
6.2a.1.1 General
The Charging Data Request and Charging Data Response are specified in TS 32.290 [2] and include charging information. The Charging Data Request can be of type [Event, Initial, Termination].
Table 6.2a.1.1.1 describes the use of these messages for converged charging.
Table 6.2a.1.1.1: Converged charging messages reference table
Message |
Source |
Destination |
Charging Data Request |
MMS Node |
CHF |
Charging Data Response |
CHF |
MMS Node |
The following clauses describe the different fields used in the Charging Data messages and the category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.2a.1.2 Structure for the converged charging message formats
6.2a.1.2.1 Charging Data Request message
Table 6.2a.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for MMS converged charging.
Table 6.2a.1.2.1.1: Charging Data Request message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
OC |
Described in TS 32.290 [2] |
Subscriber Identifier |
OM |
Described in TS 32.290 [2] |
NF Consumer Identification |
M |
Described in TS 32.290 [2] |
Charging Identifier |
OM |
Described in TS 32.290 [2] |
Invocation Timestamp |
M |
Described in TS 32.290 [2] |
Invocation Sequence Number |
M |
Described in TS 32.290 [2] |
Retransmission Indicator |
– |
This field is not applicable. |
One-time Event |
OC |
Described in TS 32.290 [2] |
One-time Event Type |
OC |
Described in TS 32.290 [2] |
Notify URI |
– |
This field is not applicable. |
Supported Features |
OC |
Described in TS 32.290 [2] |
Service Specification Information |
OC |
Described in TS 32.290 [2] |
Triggers |
– |
This field is not applicable. |
Multiple Unit Usage |
OC |
This field is present when the number of units is beyond one (i.e., more than one MMS) |
Rating Group |
M |
Described in TS 32.290 [2] |
Requested Unit |
OC |
Described in TS 32.290 [2] |
Time |
– |
This field is not applicable. |
Total Volume |
– |
This field is not applicable. |
Uplink Volume |
– |
This field is not applicable. |
Downlink Volume |
– |
This field is not applicable. |
Service Specific Units |
OC |
This field is present when the number of units is beyond one (i.e., more than one MMS) |
Used Unit Container |
OC |
This field holds MMS charging information when more than one MMS. It may have multiple occurrences. |
Service Identifier |
OC |
Described in TS 32.290 [2] |
Quota management Indicator |
OC |
Described in TS 32.290 [2] |
Triggers |
– |
This field is not applicable. |
Trigger Timestamp |
– |
This field is not applicable. |
Time |
– |
This field is not applicable. |
Total Volume |
OC |
Described in TS 32.290 [2] |
Uplink Volume |
– |
This field is not applicable. |
Downlink Volume |
– |
This field is not applicable. |
Service Specific Unit |
OC |
Described in TS 32.290 [2] |
Event Time Stamps |
OC |
Described in TS 32.290 [2] |
Local Sequence Number |
OM |
Described in TS 32.290 [2] |
MMS Charging Information |
OM |
This field holds the MMS specific information described in clause 6.5.2 |
6.2a.1.2.2 Charging Data Response message
Table 6.2a.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for MMS converged charging.
Table 6.2a.1.2.2.1: Charging Data Response Message Contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
OC |
Described in TS 32.290 [2] |
Invocation Timestamp |
M |
Described in TS 32.290 [2] |
Invocation Result |
OC |
Described in TS 32.290 [2] |
Invocation Sequence Number |
M |
Described in TS 32.290 [2] |
Session Failover |
OC |
Described in TS 32.290 [2] |
Supported Features |
OC |
Described in TS 32.290 [2] |
Triggers |
– |
This field is not applicable. |
Multiple Unit information |
OC |
This field is applicable for ECUR. |
Result Code |
OC |
Described in TS 32.290 [2] |
Rating Group |
OM |
Described in TS 32.290 [2] |
Granted Unit |
OC |
Described in TS 32.290 [2] |
Tariff Time Change |
– |
This field is not applicable. |
Time |
– |
This field is not applicable. |
Total Volume |
– |
This field is not applicable. |
Uplink Volume |
– |
This field is not applicable. |
Downlink Volume |
– |
This field is not applicable. |
Service Specific Units |
OC |
This field is present when the number of units is beyond one (i.e., more than one MMS) |
Validity Time |
OC |
Described in TS 32.290 [2] |
Final Unit Indication |
– |
This field is not applicable. |
Time Quota Threshold |
– |
This field is not applicable. |
Volume Quota Threshold |
– |
This field is not applicable. |
Unit Quota Threshold |
– |
This field is not applicable. |
Quota Holding Time |
– |
This field is not applicable. |
Triggers |
– |
This field is not applicable. |
6.3 MMS charging specific parameters
6.3.0 General
The MMS Information parameter used for MMS charging is provided in the Service Information parameter.
6.3.1 MMS charging information assignment for Service Information
The components in the Service Information that are use for MMS charging can be found in table 6.3.1.1.
Table 6.3.1.1: Service Information used for MMS charging
Information Element |
Category |
Description |
Service Information |
OM |
This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50]. For MMS Charging the MMS-Information and PS-Information are used. |
MMS Information |
OM |
This is a structured field and holds the MMS specific parameters. The details are defined in table 6.3.2. |
SMS Information |
OC |
This is a structured field and holds PS specific parameters relevant to MMS. The complete structure is defined in TS 32.274 [34]. |
Originator SCCP Address |
OC |
This field holds the SCCP calling address used to receive the MMS. |
Recipient Info |
OC |
This field holds recipient information for the MMS. It occurs at most one time in the MMS delivery case. |
PS Information |
OC |
This is a structured field and holds PS specific parameters relevant to MMS. The complete structure is defined in TS 32.251 [11]. |
3GPP User Location Info |
OC |
This field holds the information about the location of the subscriber during the MMS transaction. Only applicable to online charging. |
3GPP RAT Type |
OC |
This field holds information about the radio access technology used for the MMS transaction. |
PDP Address |
OC |
This field holds the IP address used by the subscriber for the MMS transaction. |
MS Time Zone |
OC |
This field indicates the offset between universal time and local time in steps of 15 minutes of where the MS currently resides. |
6.3.2 Definition of the MMS Information
MMS specific charging information is provided within the MMS Information. The detailed structure of the MMS Information parameter can be found in table 6.3.2.1.
Table 6.3.2.1: Structure of the MMS Information
Information Element |
Category |
Description |
---|---|---|
Originator Address |
OC |
This field holds the address (Public User ID: SIP URL, E.164, etc.) of the party generating the MMS. |
Recipient Address |
OC |
This field holds the address (Public User ID: SIP URL, E.164, etc.) of the party to whom the MMS is sent. |
Correlation Information |
OM |
Bearer correlation information |
Submission Time |
OC |
The time at which the MM was submitted or forwarded as specified in the corresponding MM1 message. |
MM Content Type |
OC |
The content type of the MM content. |
Priority |
OC |
The priority (importance) of the message if specified by the originator MMS User Agent. |
Message ID |
OC |
This field holds the MM identification provided by the Originator MMS R/S. |
Message Type |
OC |
This field holds the type of the message according to the MMS transactions e.g. submission, delivery. |
Message Size |
OC |
This field holds the total size of the MMS. |
Message Class |
OC |
The class of the MM (e.g., personal, advertisement, information service) if specified by the originator MMS User Agent. |
Delivery Report Requested |
OC |
This field indicates whether a delivery report has been requested by the originator MMS User Agent or not. |
Read Reply Report Requested |
OC |
A request for read-reply report as specified in the MM1 message. |
MMBox Storage Requested |
OC |
This parameter is only present if the MMBox feature is supported by the MMS R/S and storage of the MM was requested by |
Applic ID |
OC |
This field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply Applic ID |
OC |
This field holds the identifier of a “reply path”, i.e. the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux Applic Info |
OC |
This field holds additional application/implementation specific control information. |
Content Class |
OC |
This field classifies the content of the MM to the smallest content class to which the MM belongs |
DRM Content |
OC |
This field indicates if the MM contains DRM-protected content. |
Adaptations |
OC |
This field indicates if the Originator allows adaptation of the content (default True). |
VAS Identifier |
OC |
This field indicates the VAS that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
VASP Identifier |
OC |
This field indicates the VASP that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
6.3.3 Detailed message format for online charging
Editor’s note: TBD.
6.3.4 Formal MMS charging parameter description
6.3.4.1 MMS charging information for CDRs
The detailed definitions, abstract syntax and encoding of the MMS CDR parameters are specified in TS 32.298 [51].
6.3.4.2 MMS charging information for charging events
The detailed charging event parameter definitions are specified in TS 32.299 [50].
6.4 Definition of the MMS converged charging information
6.4.1 General
The Charging Information parameter used for MMS converged charging is provided in the following clauses.
6.4.2 Definition of MMS charging information
MMS specific charging information used for MMS converged charging is provided within the MMS charging Information.
Table 6.4.2.1: Structure of MMS Charging information
Information Element |
Category |
Description |
Originator Info |
OM |
This field is a grouped field and holds information on originator of the MMS |
Originator SUPI |
OM |
This field holds the SUPI of the originator of the MMS. This field is present if different from subscriber identifier field. |
Originator GPSI |
OC |
This field holds the GPSI of the originator of the MMS. |
Originator Other Address |
OM |
This field holds the address of the originator of the MMS, when different from SUPI and GPSI e.g., email, short code. This field may have multiple occurrences. |
Recipient Info |
OC |
This field holds recipient information for the MMS. It occurs at most one time in the MMS delivery case. |
Recipient SUPI |
OM |
This field holds the SUPI of the recipient of the MMS. This field is present if different from subscriber identifier field. |
Recipient GPSI |
OC |
This field holds the GPSI of the recipient of the MMS. |
Recipient Other Address |
OC |
This field holds the address of the recipient of the MMS, when different from SUPI and GPSI, if available e.g., email, short code. This field may have multiple occurrences |
User Location Info |
OC |
This field holds the information about the location of the subscriber during the MMS transaction. |
UE Time Zone |
OC |
This field indicates the offset between universal time and local time in steps of 15 minutes of where the UE currently resides. |
RAT Type |
OC |
This field holds information about the radio access technology used for the MMS transaction. |
Submission Time |
OC |
The time at which the MM was submitted or forwarded as specified in the corresponding MM1 message. |
MM Content Type |
OC |
The content type of the MM content. |
Priority |
OC |
The priority (importance) of the message if specified by the originator MMS User Agent. |
Message ID |
OC |
This field holds the MM identification provided by the Originator MMS Node. |
Message Type |
OC |
This field holds the type of the message according to the MMS transactions e.g., submission, delivery. |
Message Size |
OC |
This field holds the total size of the MMS. |
Message Class |
OC |
The class of the MM (e.g., personal, advertisement, information service) if specified by the originator MMS User Agent. |
Delivery Report Requested |
OC |
This field indicates whether a delivery report has been requested by the originator MMS User Agent or not. |
Read Reply Report Requested |
OC |
A request for read-reply report as specified in the MM1 message. |
Applic ID |
OC |
This field holds the identification of the destination application that the underlying MMS abstract message was addressed to. |
Reply Applic ID |
OC |
This field holds the identifier of a “reply path” i.e., the identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed. |
Aux Applic Info |
OC |
This field holds additional application/implementation specific control information. |
Content Class |
OC |
This field classifies the content of the MM to the smallest content class to which the MM belongs |
DRM Content |
OC |
This field indicates if the MM contains DRM-protected content. |
Adaptations |
OC |
This field indicates if the Originator allows adaptation of the content (default True). |
VAS Identifier |
OC |
This field indicates the VAS that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
VASP Identifier |
OC |
This field indicates the VASP that originated the MM. Only present in MM1 Retrieval and if the MM was received over an MM7 interface. |
Editor’s Note: The content of the table is FFS.
6.4.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by MMS Node for MMS converged charging.
The Operation Types are listed in the following order: I (Initial)/T (Termination)/E (Event). Therefore, when all Operation Types are possible it is marked as ITE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e., IT or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e., I-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.4.3.1 defines the basic structure of the supported fields in the Charging Data Request message for MMS converged charging.
Table 6.4.3.1: Supported fields in Charging Data Request message
Information Element |
Node Type |
MMS Node |
---|---|---|
Supported Operation Types |
ITE |
|
Session Identifier |
ITE |
|
Subscriber Identifier |
ITE |
|
NF Consumer Identification |
ITE |
|
Charging Identifier |
ITE |
|
Invocation Timestamp |
ITE |
|
Invocation Sequence Number |
ITE |
|
Retransmission Indicator |
– |
|
One-time Event |
–E |
|
One-time Event Type |
–E |
|
Notify URI |
– |
|
Supported Features |
I-E |
|
Service Specification Information |
ITE |
|
Triggers |
– |
|
Multiple Unit Usage |
ITE |
|
MMS Charging Information |
||
Originator Info |
ITE |
|
Recipient Info |
ITE |
|
User Location Info |
ITE |
|
UE Time Zone |
ITE |
|
RAT Type |
ITE |
|
Submission Time |
ITE |
|
MM Content Type |
ITE |
|
Priority |
ITE |
|
Message ID |
ITE |
|
Message Type |
ITE |
|
Message Size |
ITE |
|
Message Class |
ITE |
|
Delivery Report Requested |
ITE |
|
Read Reply Report Requested |
ITE |
|
Applic ID |
ITE |
|
Reply Applic ID |
ITE |
|
Aux Applic Info |
ITE |
|
Content Class |
ITE |
|
DRM Content |
ITE |
|
Adaptations |
ITE |
|
VAS Identifier |
ITE |
|
VASP Identifier |
ITE |
Table 6.4.3.2 defines the basic structure of the supported fields in the Charging Data Response message for MMS converged charging.
Table 6.4.3.2: Supported fields in Charging Data Response message
Information Element |
Node Type |
MMS Node |
---|---|---|
Supported Operation Types |
ITE |
|
Session Identifier |
ITE |
|
Invocation Timestamp |
ITE |
|
Invocation Result |
ITE |
|
Invocation Sequence Number |
ITE |
|
Session Failover |
I– |
|
Triggers |
– |
|
Multiple Unit information |
I-E |
|
Result Code |
I– |
|
Rating Group |
I– |
|
Granted Unit |
I– |
|
Validity Time |
I– |
|
Final Unit Indication |
– |
|
Time Quota Threshold |
– |
|
Volume Quota Threshold |
– |
|
Unit Quota Threshold |
– |
|
Quota Holding Time |
– |
|
Triggers |
– |
6.4.4 Formal MMS converged charging parameter description
6.4.4.1 MMS charging CHF CDR parameters
The detailed definitions, abstract syntax and encoding of the MMS charging CHF CDR parameters are specified in TS 32.298 [51].
6.4.4.2 MMS charging resources attributes
The detailed definitions of resources attributes used for MMS charging are specified in TS 32.291 [3].
6.5 Bindings for MMS converged charging
This mapping between the Information Elements, resource attributes and CHF CDR parameters for MMS converged charging is described in clause 7 of TS 32.291 [3].
Annex A (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in the present document.
Annex B (informative):
Change history
Change history |
||||||||
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
Sep 2003 |
SA_21 |
SP-030412 |
— |
— |
Submitted to TSG SA#21 for Information |
— |
1.0.0 |
|
Sep 2004 |
SA_25 |
SP-040555 |
— |
— |
Submitted to TSG SA#25 for Approval |
— |
2.0.0 |
6.0.0 |
Dec 2004 |
SA_26 |
SP-040780 |
0001 |
— |
Introduce Application Data in MMS Charging – Align with T2’s TS 23.140 (MMS6) |
F |
6.0.0 |
6.1.0 |
Dec 2004 |
SA_26 |
SP-040780 |
0002 |
— |
Introduce Content Adaptation in MMS Charging – Align with T2’s 23.140 (MMS6) |
F |
6.0.0 |
6.1.0 |
Dec 2004 |
SA_26 |
SP-040780 |
0003 |
— |
Correction on VASP MMS CDR triggers |
F |
6.0.0 |
6.1.0 |
Mar 2005 |
SA_27 |
SP-050031 |
0004 |
— |
Align MM10 charging functionality with T2’s TS 23.140 |
F |
6.1.0 |
6.2.0 |
Mar 2005 |
SA_27 |
SP-050031 |
0005 |
— |
Charge MMS VASP for getting Terminal Capabilities information – Align with T2’s TS 23.140 |
F |
6.1.0 |
6.2.0 |
Mar 2005 |
SA_27 |
SP-050031 |
0006 |
— |
Correct condition for generating a MM Deletion CDR – Align with T2’s TS 23.140 |
F |
6.1.0 |
6.2.0 |
Mar 2005 |
SA_27 |
SP-050031 |
0007 |
— |
Extension of the charging functionality for MM cancellation and replacement Align with T2’s TS 23.140 |
F |
6.1.0 |
6.2.0 |
Jun 2005 |
SA_28 |
SP-050277 |
0008 |
— |
Correction to scope |
F |
6.2.0 |
6.3.0 |
Jun 2005 |
SA_28 |
SP-050277 |
0009 |
— |
Correction to references |
F |
6.2.0 |
6.3.0 |
Jun 2005 |
SA_28 |
SP-050277 |
0010 |
— |
Corrections and alignments |
F |
6.2.0 |
6.3.0 |
Sep 2005 |
SA_29 |
SP-050440 |
0011 |
— |
Correct use of Content Type information |
F |
6.3.0 |
6.4.0 |
Sep 2005 |
SA_29 |
SP-050440 |
0012 |
— |
Correct MMS triggers for offline charging |
F |
6.3.0 |
6.4.0 |
Sep 2005 |
SA_29 |
SP-050440 |
0013 |
— |
Correct VASP MMS Recipient Charging – Align with TS 22.140 |
F |
6.3.0 |
6.4.0 |
Dec 2005 |
SA_30 |
SP-050701 |
0014 |
— |
Align with 32.299: remove CC-Subsession-Id, CC-Correlation-Id, User-Name and Acct-Multi-Session-Id from the relevant parts of the CCR and CCA messages |
F |
6.4.0 |
6.5.0 |
Dec 2005 |
SA_30 |
SP-050701 |
0016 |
— |
Use of User location information and RAT type in MMS charging – Align with 22.140 requirements |
F |
6.4.0 |
6.5.0 |
Mar 2006 |
SA_31 |
SP-060085 |
0017 |
— |
Correct the use of Immediate Event Charging (IEC) as an online charging principle for MMS – Align with 32.299 |
F |
6.5.0 |
6.6.0 |
Jun 2007 |
SA_36 |
SP-070273 |
0018 |
— |
Correction to failure handling procedures for online charging |
F |
6.6.0 |
7.0.0 |
Sep 2007 |
SA_37 |
SP-070605 |
0020 |
— |
Correction on MMBox charging – Align with 32.299 |
A |
7.0.0 |
7.1.0 |
Dec 2008 |
SA_42 |
SP-080841 |
0021 |
– |
Correction on Multiple Unit Operation category |
F |
7.1.0 |
7.2.0 |
Dec 2008 |
SA_42 |
— |
— |
— |
Upgrade to Release 8 |
— |
7.0.0 |
8.0.0 |
Dec 2009 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
– |
8.0.0 |
9.0.0 |
Oct 2010 |
SA_49 |
SP-100497 |
0022 |
— |
Correction on MMS Online Charging principles |
D |
9.0.0 |
9.1.0 |
Mar 2011 |
SA_51 |
SP-110109 |
0023 |
1 |
Add E.164 harmonized address format to the current E.212 in MMS Charging |
F |
9.1.0 |
10.0.0 |
Sep 2011 |
— |
— |
— |
— |
Correction of CR history (9.2.0 instead of 10.0.0) |
— |
10.0.0 |
10.0.1 |
Sep 2012 |
SA_57 |
SP-120575 |
0024 |
1 |
Addition of MS Timezone for NetLo |
B |
10.0.1 |
11.0.0 |
2014-07 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
– |
11.0.0 |
11.0.1 |
2014-09 |
SA_65 |
SP-140564 |
0027 |
1 |
Corrections for alignment between charging specifications |
F |
11.0.1 |
12.0.0 |
2014-12 |
SA_66 |
SP-140804 |
0028 |
– |
Additional corrections for removal of I-WLAN solution |
F |
12.0.0 |
12.1.0 |
SP-140805 |
0029 |
– |
Corrections on definition for parameter category |
F |
||||
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 |
0031 |
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 |
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |
2022-09 |
SA#97e |
SP-220866 |
0032 |
1 |
B |
Addition of converged charging architecture |
18.0.0 |
2022-09 |
SA#97e |
SP-220866 |
0033 |
1 |
B |
Addition of converged charging scenarios |
18.0.0 |
2022-09 |
SA#97e |
SP-220866 |
0034 |
1 |
B |
Addition of converged charging information |
18.0.0 |