6 Definition of charging information
32.2743GPPCharging managementRelease 17Short Message Service (SMS) chargingTelecommunication managementTS
6.1 Data description for SMS offline charging
6.1.1 Rf message contents
6.1.1.1 Summary of offline charging message formats
The SMS Node generates accounting information that can be transferred from the CTF to the CDF. For this purpose, SMS offline charging utilizes the Charging Data Transfer Operation that is specified in the 3GPP accounting application described in TS 32.299 [4].
The Charging Data Transfer operation employs the Charging Data Request and Charging Data Response messages.
Table 6.1.1.1.1 describes the use of these messages for offline charging.
Table 6.1.1.1.1: Offline charging messages reference table
|
Command-Name |
Source |
Destination |
|---|---|---|
|
Charging Data Request |
CTF |
CDF |
|
Charging Data Response |
CDF |
CTF |
This clause describes the different fields used in the Charging Data messages and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [2].
6.1.1.2 Structure for the offline charging message formats
6.1.1.2.1 Charging Data Request message
Table 6.1.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for SMS offline charging.
Table 6.1.1.2.1.1: Charging Data Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [4] |
|
Originator Host |
M |
Described in TS 32.299 [4] |
|
Originator Domain |
M |
Described in TS 32.299 [4] |
|
Destination Domain |
M |
Described in TS 32.299 [4] |
|
Operation Type |
M |
This field contains event type transfer |
|
Operation Number |
M |
Described in TS 32.299 [4] |
|
Operation Identifier |
OM |
Described in TS 32.299 [4] |
|
User Name |
OC |
This field contains the identification of the source node. |
|
Origination Timestamp |
OC |
Described in TS 32.299 [4] |
|
Proxy Information |
OC |
Described in TS 32.299 [4] |
|
Route Information |
OC |
Described in TS 32.299 [4] |
|
Operation Token |
OM |
This field contains the service context, i.e. SMS charging. |
|
Service Information |
OM |
This field holds the 3GPP specific SMS parameter. |
6.1.1.2.2 Charging Data Response message
Table 6.1.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for SMS offline charging.
Table 6.1.1.2.2.1: Charging Data Response Message Contents
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [4] |
|
Operation Result |
M |
Described in TS 32.299 [4] |
|
Originator Host |
M |
Described in TS 32.299 [4] |
|
Originator Domain |
M |
Described in TS 32.299 [4] |
|
Operation Type |
M |
This field contains event type transfer |
|
Operation Number |
M |
Described in TS 32.299 [4] |
|
Operation Identifier |
OM |
Described in TS 32.299 [4] |
|
User Name |
OC |
This field contains the identification of the source node. |
|
Destination Host |
OC |
Described in TS 32.299 [4] |
|
Error Reporting Host |
OC |
Described in TS 32.299 [4] |
|
Origination Timestamp |
OC |
Described in TS 32.299 [4] |
|
Proxy Information |
OC |
Described in TS 32.299 [4] |
6.1.2 Ga message contents
Refer to clause 5.2.4 for further information.
6.1.3 CDR description on the Bsm interface
6.1.3.1 CDR field types
The following Standard CDR content and format are considered:
– generated from SMS-SC:
– SC-SMO CDR;
– SC-SMT CDR;
– SC-SMO-T4 CDR;
– SC-DVT-T4 CDR.
– generated from IP-SM-GW:
– ISM-SMO CDR;
– ISM-SMT CDR.
Thecontent of each CDR type is defined in the tables in clauses 6.1.3.3 to 6.1.3.8.
For each CDR type the field definition includes the field name, category and description. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [2].
The detailed specification of the CDR parameters and their encoding is contained in TS 32.298 [3], while TS 32.297 [5] specifies the details of the CDR file transfer to the Billing Domain (BD). Additional CDR formats and contents may be available at the interface to the billing system to meet the requirements of the Billing System (BS), these are outside of the scope of 3GPP standardization.
6.1.3.2 CDR triggers
The generation of the SMS related CDRs is based on reception of Charging Data Request[event] messages transferred from the SMS node to the CDF. One CDR is created in the CDF for each Charging Data Request[event] message received.
6.1.3.3 SC-SMO CDR content
The content of SC-SMO CDR is defined in the table 6.1.3.3.1.
Table 6.1.3.3.1: SC-SMO record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
SMS-SC SMS originated. |
|
SMS Node Address |
M |
This field holds the address (e.g. E.164) of the SMS-service centre sending the Charging Data Request used for producing the record. (SMSC Address) |
|
Originator Info |
OM |
This field is a grouped field and holds information on originator of the SM. |
|
Originator IMSI |
OM |
This field holds the IMSI of the subscriber sending the short message, in case of Mobile Originating message, if available. |
|
Originator MSISDN |
OC |
This field holds the primary MSISDN of the subscriber sending the message, if available. |
|
Originator Other Address |
OM |
This field holds the address of the originator of the SM, when different from IMSI and MSISDN, if available: e.g. email, short code. Multiple addresses may be carried. |
|
Originator SCCP Address |
OC |
This field holds the SCCP calling address used to receive the SM at the SMS node, when applicable. |
|
Originator Received Address |
OC |
This field holds the original, unmodified address of the originator of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. |
|
SM Originator Interface |
OM |
This field contains information describing the interface on which the SM was received by the SMS node. In case the charging event is for application to person messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application sending the SM. |
|
SM Originator Protocol Id |
OC |
This field holds the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [7] describing the protocol used for the SM by originator. |
|
Recipient Info |
OM |
This field is a grouped field and holds recipient information for the SM. Multiple occurrences of this field are allowed in case: – all other charging information is identical for all recipients. |
|
Recipient IMSI |
OC |
This field holds the IMSI of the recipient of the SM, as received by the SMS Node, if available. |
|
Recipient MSISDN |
OC |
This field holds the MSISDN of the recipient of the SM, as received by the SMS Node, if available. |
|
Recipient Other Address |
OC |
This field holds the address of the recipient of the SM, as received by the SMS Node, when different from IMSI and MSISDN, if available: e.g. email, short code, external identifier. Multiple addresses may be carried. |
|
Recipient Received Address |
OC |
This field holds the original, unmodified address of the recipient of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. |
|
SM Destination Interface |
OM |
This is a structured field containing information describing the interface on which the SM is to be delivered (i.e. the next hop). In case the charging event is for person to application messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application. |
|
Served IMEI |
OC |
The field holds IMEI or IMEISV of the UE, if available |
|
Event Time stamp |
M |
This field holds the timestamp of when the submitted SM arrived at the SMS-SC. |
|
Message Reference |
M |
This field holds the identity used to identify an SM in the SMS node associated with entity that submitted it, and corresponds to the TP-Message-Reference (TP-MR) as defined in TS 23.040 [7]. |
|
SM Total Number |
OC |
This field holds the total number of short messages when this SM is part of concatenated short message. This field is present only in case of concatenated short message. |
|
SM sequence Number |
OC |
This field holds the sequence number of this SM within the concatenated short message when applicable. This field is present only in case of concatenated short message. |
|
Message size |
OC |
This field holds the length of the user data part of the SM, and corresponds to the TP-User-Data-Length (TP-UDL) as defined in TS 23.040 [7]. |
|
Message Class |
OM |
Used as defined in TS 32.270 [13]. It is implementation dependent the value selected for a specific transaction. |
|
SM Delivery Report Requested |
OC |
This field holds indication whether a delivery report is requested by the SM originator, and corresponds to the TP-Status-Report-Request (TP-SRR) as defined in TS 23.040 [7]. |
|
SM Data Coding Scheme |
OM |
This field holds the data coding scheme used within the SM. The information to populate this field is obtained from TP-DCS header. |
|
SM Message Type |
OM |
This field identifies the message that triggered the generation of charging information. |
|
SM Reply Path Requested |
Oc |
This field holds an indication of whether a reply SM to an original SM shall follow the same path as identified by the TP-Reply-Path (TP-RP) flag. |
|
SM User Data Header |
Oc |
This field carries the user data header extracted from the user data of the SM. The user data header (TP-UDH) is specified in TS 23.040 [7] |
|
User Location Info |
Oc |
This field holds the information about the location of the subscriber as defined in TS 29.061 [203] "3GPP-User-Location-Info"during the SMS transaction, in case of Mobile Originating message, if available. "NCGI", "5GS TAI", "5GS TAI and NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" values are applicable. |
|
RAT Type |
Oc |
This field holds the Radio Access Technology (RAT) type used for the SMS transaction, in case of Mobile Originating message, if available. |
|
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, in case of Mobile Originating message, if available. |
|
SMS Result |
C |
The field holds the result of the attempted SM submission, if unsuccessful. |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.4 SC-SMT CDR content
The content of SC-SMT CDR is defined in table 6.1.3.4.1.
Table 6.1.3.4.1: SC-SMT record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
SMS-SC SMS Terminated. |
|
SMS Node Address |
M |
This field holds the address (e.g. E.164) of the SMS-service centre sending the Charging Data Request used for producing the record. (SMSC Address). |
|
Recipient Info |
OM |
This field is a grouped field and holds information on the recipient for the SM. |
|
Recipient IMSI |
OM |
The IMSI of the subscriber the short message was delivered to, in case of Mobile Terminating message, if available. |
|
Recipient MSISDN |
OC |
The primary MSISDN of the subscriber the short message was delivered to, if available. |
|
Recipient Other Address |
Oc |
This field holds the address of the recipient of the SM, when different from IMSI and MSISDN, if available: e.g. email, short code. Multiple addresses may be carried. This field holds the external identifier of the recipient of the SM, when the SM is to be delivered for Device Trigger, if available. |
|
Recipient SCCP Address |
OC |
This field holds the SCCP called address used by the SMS node to onward deliver the SM. |
|
Recipient Received Address |
OC |
This field holds the original, unmodified address of the recipient of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. |
|
SM Destination Interface |
OM |
This is a structured field containing information describing the interface on which the SM was requested to be delivered (i.e. the next hop). In case the charging event is for person to application messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application. In case the SM is for Device Trigger, thisfield is not present . |
|
SM Recipient Protocol Id |
OC |
This field holds the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [7]. In case the SM is for Device Trigger, this field holds the "Device Triggering Short Message code". |
|
Originator Info |
OM |
This field is a grouped field and holds information on the originator of the SM, if available. |
|
Originator IMSI |
OM |
This field holds the IMSI of the subscriber originator of the SM, if available. |
|
Originator MSISDN |
OC |
This field holds the MSISDN of the subscriber originator of the SM, if available. |
|
Originator Other Address |
OM |
This field holds the address of the originator of the SM, when different from IMSI and MSISDN, if available: e.g. short-code. Multiple addresses may be carried. In case the SM is for Device Trigger, this field holds the SME address of the Service Capability Server that is requesting a device trigger to the UE as specified in TS 29.337 [18]. |
|
Originator Received Address |
OC |
This field holds the original, unmodified address of the originator of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. |
|
SM Originator Interface |
OC |
This field contains information describing the interface on which the SM was received by the SMS node. In case the charging event is for application to person messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application sending the SM. In case the SM is for Device Trigger, thisfield is not present . |
|
Served IMEI |
OC |
The field holds IMEI or IMEISV of the UE, if available. |
|
Submission Time |
OC |
This field holds the timestamp of when the submitted SM arrived at the originating SMS Node. The information to populate this field is obtained from the TP-Service-Center-Time-Stamp (TP-SCTS) as defined in TS 23.040 [7]. |
|
Event Time stamp |
M |
This field holds the timestamp of result (successful or unsuccessful) of SM delivery: last result in case of multiple retries. |
|
SM Priority |
Oc |
This field holds any priority information associated with an SM, as defined in TS 23.040 [7]. |
|
Message Reference |
OM |
This field holds the identity used to identify an SM in the SMS node associated with entity that submitted it, and corresponds to the TP-Message-Reference (TP-MR) as defined in TS 23.040 [7]. This information is only applicable to delivery report charging procedures. |
|
SM Total Number |
Oc |
This field holds the total number of short messages when this SM is part of concatenated short message. This field is present only in case of concatenated short message. |
|
SM Sequence Number |
Oc |
This field holds the sequence number of this SM within the concatenated short message when applicable. This field is present only in case of concatenated short message. |
|
Message size |
Oc |
This field holds the length of the user data part of the SM, and corresponds to the TP-User-Data-Length (TP-UDL) as defined in TS 23.040 [7]. |
|
Message Class |
OM |
Used as defined in TS 32.270 [13]. It is implementation dependent the value selected for a specific transaction. |
|
SM Delivery Report Requested |
Oc |
This field holds indication whether a delivery report was requested by the SM originator, and corresponds to the TP-Status-Report-Indication (TP-SRI) as defined in TS 23.040 [7]. |
|
SM Data Coding Scheme |
OM |
This field holds the data coding scheme used within the SM. The information to populate this field is obtained from TP-DCS header. |
|
SM Message Type |
OM |
This field identifies the message that triggered the generation of charging information. |
|
SM Reply Path Requested |
Oc |
This field holds an indication of whether a reply SM to an original SM was requested to follow the same path as identified by the TP-Reply-Path (TP-RP) flag. |
|
SM User Data Header |
Oc |
This field carries the user data header extracted from the user data of the SM. The user data header (TP-UDH) is specified in TS 23.040 [7]. |
|
SM Status |
Oc |
This field holds the information from the TP-Status field in a Status-Report TPDU. This information is only applicable to delivery report charging procedures. |
|
SM Discharge Time |
Oc |
This field holds the time associated with the event being reported in the SM Status field. This information is only applicable to delivery report charging procedures. |
|
User Location Info |
Oc |
This field holds the information about the location of the subscriber as defined in TS 29.061 [203] "3GPP-User-Location-Info",during the SMS transaction, in case of Mobile Terminating message, if available. "NCGI", "5GS TAI", "5GS TAI and NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" values are applicable. |
|
RAT Type |
Oc |
This field holds the Radio Access Technology (RAT) type as defined in TS 29.061 [203] "3GPP-RAT-type", used for the SMS transaction, in case of Mobile Terminating message, if available. "NG-RAN" value is applicable. |
|
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, in case of Mobile Terminating message, if available. |
|
SMS Result |
C |
The field holds the result of the attempted SM delivery, if unsuccessful. |
|
SM Device Trigger information |
Oc |
This field holds the set of information related to SMS submission to SMS-SC for Device Trigger. |
|
SM DT Reference Number |
Oc |
This field holds the Reference Number related to the device trigger request, if available. |
|
SMS Application Port ID |
Oc |
This field holds the Application Port ID of the triggering application for the device trigger request, if available. |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.5 SC-DVT-T4 CDR content
The content of SC-DVT-T4 CDR is defined in the table 6.1.3.5.1.
Table 6.1.3.5.1: SC-DVT-T4 record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Device Trigger over T4. |
|
SMS Node Address |
M |
This field holds the address (e.g. E.164) of the SMS-service centre sending the Charging Data Request used for producing the record. (SMSC Address) |
|
Event Time stamp |
M |
This field holds the timestamp of when the Device Trigger request arrived at the SMS-SC. |
|
Originator Info |
OM |
This field is a grouped field and holds information on originator of the Device Trigger. |
|
Originator Other Address |
OM |
This field holds the SME address of the Service Capability Server that is requesting a device trigger to the UE as specified in TS 29.337 [18], |
|
Recipient Info |
OM |
This field is a grouped field and holds recipient information for the SM to be delivered. |
|
Recipient IMSI |
OM |
This field holds the IMSI of the recipient of the SM to be delivered for Device Trigger, as received in the User Identifier from MTC-IWF, specified in TS 29.337 [18]. |
|
Recipient MSISDN |
OC |
This field holds the MSISDN of the recipient of the SM to be delivered for Device Trigger, as received in the User Identifier from MTC-IWF, specified in TS 29.337 [18], if available. |
|
Recipient Other Address |
OC |
This field holds the the external identifier of the recipient of the SM to be delivered for Device Trigger, as received in the User Identifier from MTC-IWF, specified in TS 29.337 [18], if available. |
|
SM Device Trigger Indicator |
Oc |
This field holds indication on the device trigger submission to SMS-SC: trigger, replace or recall. |
|
SM Device Trigger information |
Oc |
This field holds the set of information related to Device Trigger submission to SMS-SC. |
|
MTC IWF Address |
Oc |
This field holds the MTC IWF address from which device trigger is received. |
|
SM DT Reference Number |
Oc |
This field holds the Reference Number related to the device trigger request, if available. |
|
SM Old DT Reference Number |
Oc |
This field holds the Reference Number related to the device trigger intended to be replaced or recalled in the request. This information element shall be present if SM Device Trigger Indicator is recall or replace. |
|
SM Serving Node |
Oc |
This field holds the serving node identity, i.e. SGSN/MME/MSC identity serving the UE, as received from MTC-IWF, if available. |
|
SM DT Validity Period |
Oc |
This field holds the validity period of the device trigger request, if available. |
|
SM DT Priority Indication |
Oc |
This field holds the priority of the device trigger request, if available. |
|
SMS Application Port ID |
Oc |
This field holds the Application Port ID of the triggering application for the device trigger request, if available. |
|
Result |
M |
This field holds the result of Device Trigger request to SMS-SC |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.6 SC-SMO-T4 CDR content
The content of SC-SMO-T4 CDR is defined in the table 6.1.3.6.1.
Table 6.1.3.6.1: SC-SMO-T4 record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
SMS originated via T4. |
|
SMS Node Address |
M |
This field holds the address (e.g. E.164) of the SMS-service centre sending the Charging Data Request used for producing the record. (SMSC Address) |
|
Originator Info |
OM |
This field is a grouped field and holds information on originator of the SM. |
|
Originator IMSI |
OM |
This field holds the IMSI of the subscriber sending the short message, if available. |
|
Originator SCCP Address |
OC |
This field holds the SCCP calling address used to receive the SM at the SMS node, when applicable. |
|
SM Originator Protocol Id |
OC |
This field holds the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [7] describing the protocol used for the SM by originator. |
|
Recipient Info |
OM |
This field is a grouped field and holds recipient information for the SM. |
|
Recipient Other Address |
OC |
This field holds the SME address of the SCS/AS, recipient of the SM, as received by the SMS-SC. |
|
Served IMEI |
OC |
The field holds IMEI or IMEISV of the UE, if available |
|
Event Time stamp |
M |
This field holds the timestamp of when the submitted SM arrived at the SMS-SC. |
|
Message Reference |
M |
This field holds the identity used to identify an SM in the SMS node associated with entity that submitted it, and corresponds to the TP-Message-Reference (TP-MR) as defined in TS 23.040 [7]. |
|
Message size |
OC |
This field holds the length of the user data part of the SM, and corresponds to the TP-User-Data-Length (TP-UDL) as defined in TS 23.040 [7]. |
|
Message Class |
OM |
Used as defined in TS 32.270 [13]. It is implementation dependent the value selected for a specific transaction. |
|
SM Delivery Report Requested |
OC |
This field holds indication whether a delivery report is requested by the SM originator, and corresponds to the TP-Status-Report-Request (TP-SRR) as defined in TS 23.040 [7]. |
|
SM Data Coding Scheme |
OM |
This field holds the data coding scheme used within the SM. The information to populate this field is obtained from TP-DCS header. |
|
SM Message Type |
OM |
This field identifies the message that triggered the generation of charging information, indicating "MO-SMS via T4 submission" |
|
SM Reply Path Requested |
Oc |
This field holds an indication of whether a reply SM to an original SM shall follow the same path as identified by the TP-Reply-Path (TP-RP) flag. |
|
SM User Data Header |
Oc |
This field carries the user data header extracted from the user data of the SM. The user data header (TP-UDH) is specified in TS 23.040 [7] |
|
User Location Info |
Oc |
This field holds the information about the location of the subscriber during the SMS transaction, if available. |
|
RAT Type |
Oc |
This field holds the Radio Access Technology (RAT) type used for the SMS transaction, if available. |
|
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, if available. |
|
SMS Result |
C |
The field holds the result of the attempted SM submission, if unsuccessful. |
|
MTC IWF Address |
Oc |
This field holds the MTC IWF address used by the SMS-SC for the Mobile Originating message transfer to the SCS/AS. |
|
SMS Application Port ID |
Oc |
This field holds the Application Port ID of the Mobile Originating message handled by the SMS-SC. |
|
External Identifier |
OM |
This field holds the External Identifier associated to the sender of the Mobile Originated short message, if available. |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.7 ISM-SMO CDR content
The content of ISM-SMO CDR is defined in the table 6.1.3.7.1.
Table 6.1.3.7.1: ISM-SMO record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
IP-SM-GW SMS originated. |
|
SMS Node Address |
M |
This field holds the address of the IP-SM-GW sending the Charging Data Request used for producing the record. |
|
Originator Info |
OM |
This field and sub-fields are described in table 6.1.3.3.1 |
|
Recipient Info |
OM |
This field and sub-fields are described in table 6.1.3.3.1 |
|
Subscriber Equipment Number |
OC |
This field holds the subscriber equipment information. |
|
Event Time stamp |
M |
Described in table 6.1.3.3.1 |
|
Message Reference |
M |
Described in table 6.1.3.3.1 |
|
SM Total Number |
OC |
Described in table 6.1.3.3.1 |
|
SM sequence Number |
OC |
Described in table 6.1.3.3.1 |
|
Message size |
OC |
Described in table 6.1.3.3.1 |
|
Message Class |
OM |
Described in table 6.1.3.3.1 |
|
SM Delivery Report Requested |
OC |
Described in table 6.1.3.3.1 |
|
SM Data Coding Scheme |
OM |
Described in table 6.1.3.3.1 |
|
SM Message Type |
OM |
Described in table 6.1.3.3.1 |
|
SM Reply Path Requested |
Oc |
Described in table 6.1.3.3.1 |
|
SM User Data Header |
Oc |
Described in table 6.1.3.3.1 |
|
SMS Result |
C |
Described in table 6.1.3.3.1 |
|
User Location Info |
Oc |
Described in table 6.1.3.3.1 |
|
RAT Type |
Oc |
Described in table 6.1.3.3.1 |
|
UE Time Zone |
Oc |
Described in table 6.1.3.3.1 |
|
PDP Address |
Oc |
This field holds the IP address used by the subscriber for the SMS transaction. |
|
User Session Id |
Oc |
This field holds the session identifier. For a SIP session the Session-ID contains the SIP Call ID. |
|
Number Portability routing information |
Oc |
This field includes information on number portability after DNS/ENUM request from S-CSCF in the sms originator user’s home network. |
|
Carrier Select routing information |
Oc |
This field includes information on carrier select after DNS/ENUM request from S-CSCF in the sms originator user’s home network. |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.8 ISM-SMT CDR content
The content of ISM-SMT CDR is defined in table 6.1.3.8.1.
Table 6.1.3.8.1: ISM-SMT record
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
IP-SM-GW SMS Terminated. |
|
SMS Node Address |
M |
This field holds the address of the IP-SM-GW sending the Charging Data Request used for producing the record. |
|
Recipient Info |
OM |
This field and sub-fields are described in table 6.1.3.4.1, except for Device trigger which is not applicable. |
|
Originator Info |
OM |
This field and sub-fields are described in table 6.1.3.4.1, except for Device trigger which is not applicable. |
|
Subscriber Equipment Number |
OC |
This field holds the subscriber equipment information. |
|
Submission Time |
OC |
Described in table 6.1.3.4.1 |
|
Event Time stamp |
M |
Described in table 6.1.3.4.1 |
|
SM Priority |
Oc |
Described in table 6.1.3.4.1 |
|
Message Reference |
OM |
Described in table 6.1.3.4.1 |
|
SM Total Number |
Oc |
Described in table 6.1.3.4.1 |
|
SM Sequence Number |
Oc |
Described in table 6.1.3.4.1 |
|
Message size |
Oc |
Described in table 6.1.3.4.1 |
|
Message Class |
OM |
Described in table 6.1.3.4.1 |
|
SM Delivery Report Requested |
Oc |
Described in table 6.1.3.4.1 |
|
SM Data Coding Scheme |
OM |
Described in table 6.1.3.4.1 |
|
SM Message Type |
OM |
Described in table 6.1.3.4.1 |
|
SM Reply Path Requested |
Oc |
Described in table 6.1.3.4.1 |
|
SM User Data Header |
Oc |
Described in table 6.1.3.4.1 |
|
SM Status |
Oc |
Described in table 6.1.3.4.1 |
|
SM Discharge Time |
Oc |
Described in table 6.1.3.4.1 |
|
SMS Result |
C |
Described in table 6.1.3.4.1 |
|
User Location Info |
Oc |
Described in table 6.1.3.4.1 |
|
RAT Type |
Oc |
Described in table 6.1.3.4.1 |
|
UE Time Zone |
Oc |
Described in table 6.1.3.4.1 |
|
PDP Address |
Oc |
This field holds the IP address used by the subscriber for the SMS transaction. |
|
User Session Id |
Oc |
This field holds the session identifier. For a SIP session the Session-ID contains the SIP Call ID. |
|
Number Portability routing information |
Oc |
This field includes information on number portability after DNS/ENUM request from S-CSCF in the sms recipient user’s home network. |
|
Carrier Select routing information |
Oc |
This field includes information on carrier select after DNS/ENUM request from S-CSCF in the sms recipient user’s home network. |
|
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.2 Data description for SMS online charging
6.2.1 Ro message contents
6.2.1.0 Introduction
The SMS node generates Debit / Reserve Units information that can be transferred from the CTF to the OCF. For this purpose, SMS online charging utilizes the Debit Units and Reserve Units procedure that is specified in the 3GPP Debit / Reserve Units operation in TS 32.299 [4].
The SMS node generates refund information that can be transferred from the CTF to the OCF. For this purpose, it uses REFUND procedure defined in IETF RFC 4006 [12] with extended AVPs.
The Debit / Reserve Units procedure employs the Debit / Reserve Units Request and Debit / Reserve Units Response messages.
The Refund Account procedure employs the Debit Units Request (Refund Account) request and response messages.
Table 6.2.1.0.1 describes the use of these messages for SMS online charging.
Table 6.2.1.0.1: SMS online charging messages contents
|
Command-Name |
Source |
Destination |
|
Debit / Reserve Units Request |
CTF |
OCS |
|
Debit / Reserve Units Response |
OCS |
CTF |
This clause describes the different fields used in the Debit / Reserve Units Request and Debit / Reserve Units Reponse messages and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [2].
Detailed descriptions of the fields are provided in TS 32.299 [4].
6.2.1.1 Summary of message formats
6.2.1.2 Structure for the Credit-Control message formats
6.2.1.2.1 Debit/Reserve Units Request message
Table 6.2.1.2.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from SMS node as used for SMS online charging.
Table 6.2.1.2.1.1: Debit / Reserve Units Request message contents for SMS
|
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 context, i.e. SMS charging. |
|
Operation Type |
M |
This field defines the transfer type: event for immediate event based charging and initial, terminate for ECUR 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 source node. |
|
Origination State |
OC |
Used for ECUR only. |
|
Origination Timestamp |
OC |
This field contains the time when the operation is requested. |
|
Subscriber Identifier |
OM |
This field contains the identification of the subscriber (i.e. MSISDN) that uses the requested service. |
|
Termination Cause |
OC |
This field contains information about the cause for termination of a Credit-Control session. Used for terminating Credit-Control sessions in ECUR only. |
|
Requested-Action |
OC |
This field contains the requested action, used for IEC only. |
|
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 |
OC |
This field contains the identification of the user equipment used to access service. Included if information is made available to the node. |
|
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 SMS specific parameter and is described in clause 6.3. |
6.2.1.2.2 Debit / Reserve Units Response message
Table 6.2.1.2.2.1 illustrates the basic structure of a Debit / Reserve Units Response message as used for SMS charging.
This message is always used by the OCS as specified below, independent of the receiving SMS node and the operation type that is being replied to.
Table 6.2.1.2.2.1: Debit / Reserve Units Response message contents for SMS
|
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 SMS in 3GPP. |
|
Multiple Unit Operation |
OC |
This field contains the parameter for the quota management. Used in IEC for refund purpose and in ECUR. |
|
Operation Failure Action |
OC |
This field defines the resulting operation at the SMS node if a failure has occurred at the OCS for ECUR. |
|
Operation Event Failure Action |
OC |
This field defines the resulting operation at the SMS node if a failure has occurred at the OCS for IEC. |
|
Redirection Host |
OC |
|
|
Redirection Host Usage |
OC |
|
|
Redirection Cache Time |
OC |
|
|
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 |
OC |
This field contains SMS specific information. |
Editor’s Note: The mechanism to carry refund information is For Future Study.
6.2a Data description for SMS 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 [57] 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 |
SMSF |
CHF |
|
Charging Data Response |
CHF |
SMSF |
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 [2].
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 structure of a Charging Data Request message from table 7.1 in TS 32.290 [57] as used for SMS 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 [57] |
|
Subscriber Identifier |
OM |
Described in TS 32.290 [57] |
|
NF Consumer Identification |
M |
Described in TS 32.290 [57] |
|
Charging Identifier |
OM |
Described in TS 32.290 [57] |
|
Invocation Timestamp |
M |
Described in TS 32.290 [57] |
|
Invocation Sequence Number |
M |
Described in TS 32.290 [57] |
|
Retransmission Indicator |
– |
This field is not applicable. |
|
One-time Event |
OC |
Described in TS 32.290 [57] |
|
One-time Event Type |
OC |
Described in TS 32.290 [57] |
|
Service Specification Information |
OC |
Described in TS 32.290 [57] |
|
Notify URI |
OC |
This field is not applicable. |
|
Supported Features |
OC |
Described in TS 32.290 [57] |
|
Service Specification Information |
OC |
Described in TS 32.290 [57] |
|
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 SMS) |
|
Rating Group |
M |
Described in TS 32.290 [57] |
|
Requested Unit |
OC |
Described in TS 32.290 [57] |
|
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 holds the amount of requested SMS, if it is more than one SMS. |
|
Used Unit Container |
OC |
This field holds SMS charging information when more than one SMS. It may have multiple occurrences. |
|
Service Identifier |
– |
This field is not applicable. |
|
Quota management Indicator |
OC |
Described in TS 32.290 [57] |
|
Triggers |
OC |
Described in TS 32.290 [57] |
|
Trigger Timestamp |
OC |
Described in TS 32.290 [57] |
|
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 Unit |
OC |
This field holds the amount of used SMS, if it is more than one SMS. |
|
Event Time Stamps |
OC |
This field holds the timestamps of the SMS reported in the Service Specific Units. |
|
Local Sequence Number |
OM |
Described in TS 32.290 [57] |
|
SMS Charging Information |
OM |
This field holds the SMS 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 structure of a Charging Data Response message from table 7.2 in TS 32.290 [57] as used for SMS 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 [57] |
|
Invocation Timestamp |
M |
Described in TS 32.290 [57] |
|
Invocation Result |
OC |
Described in TS 32.290 [57] |
|
Invocation Sequence Number |
M |
Described in TS 32.290 [57] |
|
Session Failover |
OC |
Described in TS 32.290 [57] |
|
Supported Features |
OC |
Described in TS 32.290 [57] |
|
Triggers |
– |
This field is not applicable. |
|
Multiple Unit information |
OC |
This field is applicable for ECUR. |
|
Result Code |
OC |
Described in TS 32.290 [57] |
|
Rating Group |
OM |
Described in TS 32.290 [57] |
|
Granted Unit |
OC |
This field is present when the number of units is beyond one i.e., more than one SMS |
|
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 holds the number of granted SMS, if it is more than one SMS. |
|
Validity Time |
OC |
Described in TS 32.290 [57] |
|
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.2a.2 Ga message contents
Refer to clause 5.4.4.
6.2a.3 CDR description on the Bsm interface
6.2a.3.1 General
This clause describes the CDR content and format generated for SMS converged charging.
The following tables provide a brief description of each CDR parameter. The category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [2]. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [3].
6.2a.3.2 SMS charging CHF CDR data
If enabled, CHF CDRs for SMS charging shall be produced for SMS chargeable events.
The fields of SMS charging CHF CDR are specified in table 6.2a.3.2.1.
Table 6.2a.3.2.1: SMS charging CHF record data
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Described in TS 32.298 [3] |
|
Recording Network Function ID |
OM |
Described in TS 32.298 [3] |
|
Subscriber Identifier |
M |
This field holds the 5G Subscription Permanent Identifier (SUPI) of the served party. |
|
NF Consumer Information |
M |
This field holds the information of the SMSF that used the charging service. |
|
NF Functionality |
M |
This field contains the function of the node (i.e. SMSF) |
|
NF Name |
OC |
This field holds the name of the SMSF used. |
|
NF Address |
OC |
This fields holds the IP Address of the SMSF used. |
|
NF PLMN ID |
Oc |
This field holds the PLMN identifier (MCC MNC) of the SMSF. |
|
Triggers |
– |
This field is not applicable. |
|
List of Multiple Unit Usage |
OM |
This field is present when the number of units is beyond one (i.e. more than one SMS) |
|
Record Opening Time |
OC |
Described in TS 32.298 [3] |
|
Duration |
M |
Described in TS 32.298 [3] |
|
Record Sequence Number |
C |
Described in TS 32.298 [3] |
|
Cause for Record Closing |
M |
Described in TS 32.298 [3] |
|
Local Record Sequence Number |
OM |
Described in TS 32.298 [3] |
|
Record Extensions |
OC |
Described in TS 32.298 [3] |
|
SMS Charging Information |
OM |
This field holds the SMS specific information defined in clause 6.x |
6.3 SMS charging specific parameters
6.3.1 Definition of the SMS charging information
6.3.1.1 SMS charging information assignment for Service Information
The components in the Service-Information that are use for SMS charging can be found in table 6.3.1.1.1
Table 6.3.1.1.1: Service-Information used for SMS 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 [4]. For SMS Charging the SMS-Information and selected parameters of MMS Information, PS-Information and IMS information are used. |
|
SMS Information |
OM |
This is a structured field and holds the SMS specific parameters. The details are defined in table 6.3.1.2. |
|
MMS Information |
OM |
This is a structure field and the following parameters are specific to SMS. The complete structure is defined in TS 32.270 [13] |
|
Originator Address |
OM |
This field holds the address of the originator of the SM. This is typically an E.164 number or a short-code. Multiple addresses may be carried if additional information is available, e.g. IMSI and E.164 number. This field holds the SME address of the SCS requesting a device trigger to the UE as specified in TS 29.337 [18], in case of SM for Device Trigger. |
|
Submission Time |
OC |
This field holds the timestamp of when the submitted SM arrived at the originating SMS Node. The information to populate this field is obtained from the TP-Service-Center-Time-Stamp (TP-SCTS) as defined in TS 23.040 [7]. If a refund or retransmission is required, the timestamp carries the timestamp associated with the original submitted SM. |
|
Priority |
OC |
This field holds any priority information associated with an SM. |
|
Message Id |
OM |
This field carries the identity used to identify an SM in the SMS node associated with entity that submitted it. The information to populate this field is obtained from the TP-Message-Reference (TP-MR) as defined in TS 23.040 [7]. |
|
Message Size |
OM |
This field carries the length of the user data part of the SM. The information to populate this field is obtained from the TP-User-Data-Length (TP-UDL) as defined in TS 23.040 [7] |
|
Message Class |
OM |
Used as defined in TS 32.270 [13]. It is implementation dependent the value selected for a specific transaction. |
|
Delivery Report Requested |
OC |
This field indicates whether a delivery report is requested by the SM originator. The information to populate this field is obtained from the TP-Status-Report-Request (TP-SRR) as defined in TS 23.040 [7] |
|
PS Information |
OC |
This is a structured field and the following parameters are specific to SMS. The complete structure is defined in TS 32.251 [10]. |
|
PDP Address |
OC |
This field holds the IP address used by the subscriber for the SMS transaction. Included if the SMS node is the IP-SM-GW. |
|
3GPP User Location Info |
OC |
This field holds the information about the location of the subscriber as defined in TS 29.061 [203] "3GPP-User-Location-Info", during the SMS transaction. "NCGI", "5GS TAI", "5GS TAI and NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" values are applicable. |
|
3GPP RAT Type |
OC |
This field holds information about the radio access technology as defined in TS 29.061 [203] "3GPP-RAT-type", used for the SMS transaction. "NG-RAN" value is applicable. |
|
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. |
|
User Equipment Info |
OC |
This field holds the identification of the terminal (IMEI or IMEISV…) |
|
IMS Information |
OC |
This is a structured field and the following parameters are specific to SMS. The complete structure is defined in TS 32.260 [15]. |
|
User Session Id |
OC |
This field holds the session identifier. For a SIP session the Session-ID contains the SIP Call ID. |
|
Number Portability routing information |
OC |
This field includes information on number portability after DNS/ENUM request from S-CSCF in the calling user’s home network. |
|
Carrier Select routing information |
OC |
This field includes information on carrier select after DNS/ENUM request from S-CSCF in the calling user’s home network. |
6.3.1.2 Definition of the SMS Information
The components in the SMS Information that are used for SMS charging can be found in table 6.3.1.2.1
Table 6.3.1.2.1: SMS Information used for SMS Charging
|
Information Element |
Category |
Description |
|
SMS Node |
OM |
Identifies the SMS Node as IP-SM-GW or SMS Router or a combined IP-SM-GW / SMS Router or as SMS-SC. |
|
SM Client Address |
OM |
This field holds the address of the SMS node to which the charging system is connected to. This may be the same as the SMSC Address field. |
|
Originator SCCP Address |
OC |
This field holds the SCCP calling address used to receive the SM at the SMS node. Only present if SMSIP is not used for the inward connection. |
|
Originator Received Address |
OC |
This field holds the original, unmodified address of the originator of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. This is typically an E.164 number or a short-code. Multiple addresses may be carried if additional information is available, e.g. IMSI and E.164 number. |
|
Recipient Info |
OC |
This field holds recipient information for the SM. Each occurrence of this field denotes a different recipient. Multiple occurrences of this field are allowed in case: – multiple recipients are associated with the charged event and – all other charging information is identical for all recipients. In case the SM contains a Delivery Report, as described in clause 5.3.2.3, this field identifies the recipient of this Delivery Report. This recipient information shall correspond to the originator information of the message that triggered this Delivery Report. (Note 2) |
|
Recipient Address |
OC |
This field holds the address of the recipient of the SM. This is typically an E.164 number or a short-code. Multiple addresses may be carried if additional information is available, e.g. short-code, IMSI, E.164 number, long/short code of the SCS/AS, or external identifier for Device Trigger. |
|
Recipient Received Address |
OC |
This field holds the original, unmodified address of the recipient of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. This is typically an E.164 number or a short-code. Multiple addresses may be carried if additional information is available, e.g. short-code, IMSI, or E.164 number. |
|
Recipient SCCP Address |
OC |
This field holds the SCCP called address used by the SMS node to onward deliver the SM. Only present if SMSIP is not used for the outward connection. |
|
SM Destination Interface |
OM |
This is a structured field containing information describing the interface on which the SM is to be delivered (i.e. the next hop). In case the charging event is for person to application messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application. (See also Note 3) |
|
SM Protocol Id |
OC |
This field holds the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [7]. This field relates to the recipient when charging MT SMS messages as specified in TS 32.240 [2]. |
|
SMSC Address |
OM |
This field holds the address of the SMSC to which the originating or terminating SM is directed to. |
|
SM Data Coding Scheme |
OM |
This field holds the data coding scheme used within the SM. The information to populate this field is obtained from TP-DCS header. |
|
SM Message Type |
OM |
This field identifies the message that triggered the generation of charging information. |
|
SM Originator Interface |
OM |
This is a structured field containing information describing the interface on which the SM was received by the SMS node (i.e. the previous hop) In case the charging event is for application to person messaging or for application to application messaging (see clause 5.1.1) this field holds the identification of the application. (See also Note 3) |
|
SM Protocol Id |
OC |
This field holds the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [7]. This field relates to the originator when charging MO SMS messages as specified in TS 32.240 [2]. |
|
SM Reply Path Requested |
OC |
This field carries an indication of whether a reply SM to an original SM shall follow the same path as identified by the TP-Reply-Path (TP-RP) flag. |
|
SM User Data Header |
OC |
This field carries the user data header extracted from the user data of the SM. The user data header (TP-UDH) is specified in TS 23.040 [7] |
|
SM Status |
OC |
This field holds the information from the TP-Status field in a Status-Report TPDU. This information is only applicable to delivery report charging procedures or where ECUR is employed. |
|
SM Discharge Time |
OC |
This field holds the time associated with the event being reported in the SM Status field. This information is only applicable to delivery report charging procedures. |
|
Number of Messages Sent |
OC |
Indicates the number of SMSs sent by the IMS application or the total number of short messages when this SM is part of concatenated short message, if applicable. |
|
SM Service Type |
OC |
This field indicates the type of SM service that caused the charging interaction. It is only applicable for SM supplementary service procedures. |
|
SM Sequence Number |
OC |
This field holds the sequence number of this SM within the concatenated short message when applicable. This field is present only in case of concatenated short message. |
|
SMS result |
C |
The field holds the result of the attempted SM transaction, if unsuccessful. |
|
SM Device Trigger Indicator |
OC |
This field holds indication on the device trigger submission to SMS-SC: request, replace or recall. |
|
SM Device Trigger information |
OC |
This field holds the set of information related to SMS transaction for Device Trigger. |
|
MTC IWF Address |
OC |
This field holds the MTC IWF address which originated the device trigger. |
|
SM DT Reference Number |
OC |
This field holds the Reference Number related to the device trigger request, if available. |
|
SM Serving Node |
OC |
This field holds the serving node identity, i.e. SGSN/MME/MSC identity serving the UE, as received from MTC-IWF, if available. |
|
SM DT Validity Period |
OC |
This field holds the validity period of the device trigger request, if available. |
|
SM DT Priority Indication |
OC |
This field holds the priority of the device trigger request, if available. |
|
SMS Application Port ID |
OC |
This field holds the Application Port ID of the triggering application for the device trigger request, if available. |
|
MTC IWF Address |
OC |
This field holds the MTC IWF address used by the SMS-SC for the Mobile Originating message transfer to the SCS/AS. |
|
SMS Application Port ID |
OC |
This field holds the Application Port ID of the Mobile Originating message handled by the SMS-SC. |
|
External Identifier |
OM |
This field holds the External Identifier associated to the sender of the Mobile Originated short message, if available. |
NOTE 1: The case of multi-destinations of SMS refers to SMS and Internet Electronic Mail interworking as specified in clause 3.8 of TS 23.040 [7].
NOTE 2: Implementations vary as to the originator address that is presented to an end user for a Delivery Report. Typically the originator address either identifies the SMS node that generated the Delivery Report or the originator address of a Delivery Report identifies the recipient of the original message that triggered this Report. It is expected that the charging event contains the information presented to the end user.
NOTE 3: There is a distinction between short numbers (as conveyed in originator and/or recipient address fields) and the identification of SM applications (as carried in SM Originator Interface and/or SM Destination Interface). Short numbers are used by end users to address a service of an applications. Multiple short numbers may map to one application capable of multiple services. The identification of an application is how an application is know to the operator.
6.3.1A Detailed message format for offline charging
This clause specifies the charging data that are sent by the SMS Node in the Charging Data Request, with [event] Operation Type.
When a particular field is not supported, this field is marked with "-".
Table 6.3.1A.1 illustrates the basic structure of the supported fields in Service Information of the Charging Data Request message for SMS offline charging.
Table 6.3.1A.1: Supported fields in Charging Data Request message
|
Information Element |
Node Type |
SMS-C |
IP-SM-GW |
||||
|---|---|---|---|---|---|---|---|
|
CDR Type |
SC-SMO |
SC-SMT |
SC-DVT-T4 |
SC-SMO-T4 |
ISM-SMO |
ISM-SMT |
|
|
Supported Operation Types |
E |
E |
E |
E |
E |
E |
|
|
Session Identifier |
E |
E |
E |
E |
E |
E |
|
|
Originator Host |
E |
E |
E |
E |
E |
E |
|
|
Originator Realm |
E |
E |
E |
E |
E |
E |
|
|
Destination Domain |
E |
E |
E |
E |
E |
E |
|
|
Operation Type |
E |
E |
E |
E |
E |
E |
|
|
Operation Number |
E |
E |
E |
E |
E |
E |
|
|
Operation Identifier |
E |
E |
E |
E |
E |
E |
|
|
User Name |
E |
E |
E |
E |
E |
E |
|
|
Destination Host |
E |
E |
E |
E |
E |
E |
|
|
Operation Interval |
– |
– |
– |
– |
– |
– |
|
|
Origination State |
E |
E |
E |
E |
E |
E |
|
|
Origination Timestamp |
E |
E |
E |
E |
E |
E |
|
|
Proxy Information |
E |
E |
E |
E |
E |
E |
|
|
Route Information |
E |
E |
E |
E |
E |
E |
|
|
Operation Token |
E |
E |
E |
E |
E |
E |
|
|
Service Information with MMS, PS, IMS and SMS Information |
|||||||
|
SMS Node |
– |
– |
– |
E |
– |
– |
|
|
SM Client Address |
E |
E |
E |
E |
E |
E |
|
|
Originator SCCP Address |
E |
E |
– |
E |
E |
E |
|
|
Originator Received Address |
E |
E |
– |
E |
E |
E |
|
|
Recipient Info |
E |
E |
E |
E |
E |
E |
|
|
SMSC Address |
– |
– |
– |
– |
– |
– |
|
|
SM Data Coding Scheme |
E |
E |
– |
E |
E |
E |
|
|
SM Message Type |
E |
E |
E |
E |
E |
E |
|
|
SM Originator Interface |
– |
E |
– |
– |
– |
E |
|
|
SM Protocol Id |
E |
– |
– |
E |
E |
– |
|
|
SM Reply Path Requested |
E |
E |
– |
E |
E |
E |
|
|
SM User Data Header |
E |
E |
– |
E |
E |
E |
|
|
SM Status |
– |
E |
– |
E |
– |
E |
|
|
SM Discharge Time |
– |
E |
– |
– |
– |
E |
|
|
Number of Messages Sent |
E |
E |
– |
– |
E |
E |
|
|
SM Service Type |
– |
– |
– |
– |
– |
– |
|
|
SMS result |
E |
E |
E |
E |
E |
E |
|
|
SM Sequence Number |
E |
E |
– |
– |
E |
E |
|
|
SM Device Trigger Indicator |
– |
– |
E |
E |
– |
– |
|
|
SM Device Trigger information |
– |
E |
E |
E |
– |
E |
|
|
Originator Address |
E |
E |
E |
E |
E |
E |
|
|
Submission Time |
E |
E |
E |
E |
E |
E |
|
|
Priority |
– |
E |
– |
– |
– |
E |
|
|
Message Id |
E |
E |
– |
E |
E |
E |
|
|
Message Size |
E |
E |
– |
E |
E |
E |
|
|
Message Class |
E |
E |
– |
E |
E |
E |
|
|
Delivery Report Requested |
E |
E |
– |
E |
E |
E |
|
|
PDP Address |
– |
– |
– |
– |
E |
E |
|
|
3GPP User Location Info |
E |
E |
– |
E |
E |
E |
|
|
3GPP RAT Type |
E |
E |
– |
E |
E |
E |
|
|
MS Time Zone |
E |
E |
– |
E |
E |
E |
|
|
User Equipment Info |
E |
E |
– |
E |
E |
E |
|
|
User Session Id |
– |
– |
– |
– |
E |
E |
|
|
Number Portability routing information |
– |
– |
– |
– |
E |
E |
|
|
Carrier Select routing information |
– |
– |
– |
– |
E |
E |
|
|
MTC IWF Address |
– |
– |
– |
E |
– |
– |
|
|
SMS Application Port ID |
– |
– |
– |
E |
– |
– |
|
|
External Identifier |
– |
– |
– |
E |
– |
– |
|
6.3.2 Formal parameter description
6.3.2.1 SMS charging information for CDRs
The detailed definitions, abstract syntax and encoding of the SMS CDR parameters are specified in TS 32.298 [3].
6.3.2.2 SMS charging information for charging events
The detailed charging event parameter definitions are specified in TS 32.299 [50].
6.3.3 Detailed message format for online charging
The Operation types are listed in the following order: I [initial]/ T [terminate]/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.3.3.1 illustrates the basic structure of the supported fields in the Debit / Reserve Units Request for SMS, T4 Device Triggering, and for MO-SMS via T4 submission, online charging.
Table 6.3.3.1: Supported fields in Debit / Reserve Units Request message
|
Information Element |
Service Type |
SMS |
T4 Device Triggering |
MO-SMS T4 |
|---|---|---|---|---|
|
Supported Operation Types |
I/T/E |
E |
I/T |
|
|
Session Identifier |
ITE |
E |
IT |
|
|
Originator Host |
ITE |
E |
IT |
|
|
Originator Domain |
ITE |
E |
IT |
|
|
Destination Domain |
ITE |
E |
IT |
|
|
Operation Identifier |
ITE |
E |
IT |
|
|
Operation Token |
ITE |
E |
IT |
|
|
Operation Type |
ITE |
E |
IT |
|
|
Operation Number |
ITE |
E |
IT |
|
|
Destination Host |
ITE |
E |
IT |
|
|
User Name |
ITE |
E |
IT |
|
|
Origination State |
ITE |
– |
IT |
|
|
Origination Timestamp |
ITE |
E |
IT |
|
|
Subscriber Identifier |
ITE |
E |
IT |
|
|
Termination Cause |
-T- |
– |
-T |
|
|
Requested Action |
–E |
E |
– |
|
|
Multiple Operation |
ITE |
E |
IT |
|
|
Multiple Unit Operation |
ITE |
E |
IT |
|
|
Subscriber Equipment Number |
ITE |
– |
IT |
|
|
Proxy Information |
ITE |
E |
IT |
|
|
Route Information |
ITE |
E |
IT |
|
|
Service Information |
ITE |
E |
IT |
|
|
Service Information with MMS, PS, IMS and SMS Information |
||||
|
SMS Node |
ITE |
– |
IT |
|
|
SM Client Address |
ITE |
E |
IT |
|
|
Originator Info |
ITE |
E |
IT |
|
|
Recipient Info |
ITE |
E |
IT |
|
|
SMSC Address |
ITE |
– |
– |
|
|
SM Data Coding Scheme |
ITE |
– |
IT |
|
|
SM Message Type |
ITE |
E |
IT |
|
|
SM Originator Interface |
ITE |
– |
– |
|
|
SM Protocol Id |
ITE |
– |
IT |
|
|
SM Reply Path Requested |
ITE |
– |
IT |
|
|
SM User Data Header |
ITE |
– |
IT |
|
|
SM Status |
ITE |
– |
IT |
|
|
SM Discharge Time |
ITE |
– |
– |
|
|
Number of Messages Sent |
ITE |
– |
– |
|
|
SM Service Type |
ITE |
– |
– |
|
|
SMS result |
– |
E |
IT |
|
|
SM Sequence Number |
– |
– |
– |
|
|
SM Device Trigger Indicator |
ITE |
E |
– |
|
|
SM Device Trigger information |
ITE |
E |
– |
|
|
Originator Address |
ITE |
– |
IT |
|
|
Submission Time |
ITE |
E |
IT |
|
|
Priority |
ITE |
– |
IT |
|
|
Message Id |
ITE |
– |
IT |
|
|
Message Size |
ITE |
– |
IT |
|
|
Message Class |
ITE |
– |
IT |
|
|
Delivery Report Requested |
ITE |
– |
IT |
|
|
PDP Address |
ITE |
– |
– |
|
|
3GPP User Location Info |
ITE |
– |
IT |
|
|
3GPP RAT Type |
ITE |
– |
IT |
|
|
MS Time Zone |
ITE |
– |
IT |
|
|
User Equipment Info |
– |
– |
– |
|
|
User Session Id |
ITE |
– |
– |
|
|
Number Portability routing information |
ITE |
– |
– |
|
|
Carrier Select routing information |
ITE |
– |
– |
|
|
MTC IWF Address |
– |
– |
IT |
|
|
SMS Application Port ID |
– |
– |
IT |
|
|
External Identifier |
– |
– |
-T |
|
6.4 Bindings for SMS charging
This clause describes the mapping between the Service Information fields, AVPs and CDR parameters for SMS charging.
Table 6.4.1 describes the mapping of the Information Element, AVP and CDR parameter of SC-SMO and
SC-SMT CDRs in SMS charging.
Table 6.4.1: Bindings of CDR parameter, Information Element and AVP
|
CDR parameter |
Information Element |
AVP |
|---|---|---|
|
Service Information |
Service-Information |
|
|
SMS Information |
SMS-Information |
|
|
– |
SMS Node |
SMS-Node |
|
SMS Node Address |
SM Client Address |
Client-Address |
|
Originator SCCP Address |
Originator SCCP Address |
Originator-SCCP-Address |
|
Originator Received Address |
Originator Received Address |
Originator-Received-Address |
|
Recipient Info |
Recipient Info |
Recipient-Info |
|
Recipient IMSI |
Recipient Address |
Recipient-Address |
|
Recipient MSISDN |
Recipient Address |
Recipient-Address |
|
Recipient Other Address |
Recipient Address |
Recipient-Address |
|
Recipient Received Address |
Recipient Received Address |
Recipient-Received-Address |
|
Recipient SCCP Address |
Recipient SCCP Address |
Recipient-SCCP-Address |
|
SM Destination Interface |
SM Destination Interface |
Destination-Interface |
|
SM Recipient Protocol Id |
SM Protocol Id |
SM-Protocol-Id |
|
– |
SMSC Address |
SMSC-Address |
|
SM Data Coding Scheme |
SM Data Coding Scheme |
Data-Coding-Scheme |
|
SM Message Type |
SM Message Type |
SM-Message-Type |
|
SM Originator Interface |
SM Originator Interface |
Originator-Interface |
|
SM Originator Protocol Id |
SM Protocol Id |
SM-Protocol-Id |
|
SM Reply Path Requested |
SM Reply Path Requested |
Reply-Path-Requested |
|
SM User Data Header |
SM User Data Header |
SM-User-Data-Header |
|
SM Status |
SM Status |
SM-Status |
|
SM Discharge Time |
SM Discharge Time |
SM-Discharge-Time |
|
SM Total Number |
Number of Messages Sent |
Number-of-Messages-Sent |
|
– |
SM Service Type |
SM-Service-Type |
|
SMS result |
SMS result |
SMS-result |
|
SM Sequence Number |
SM Sequence Number |
SM-Sequence-Number |
|
SM Device Trigger Indicator |
SM Device Trigger Indicator |
SM-Device-Trigger-Indicator |
|
SM Device Trigger information |
SM Device Trigger information |
SM-Device-Trigger-information |
|
MTC IWF Address |
MTC IWF Address |
MTC-IWF-Address |
|
SM DT Reference Number |
SM DT Reference Number |
Reference-Number |
|
SM Serving Node |
SM Serving Node |
Serving-Node |
|
SM DT Validity Period |
SM DT Validity Period |
Validity-Time |
|
SM DT Priority Indication |
SM DT Priority Indication |
Priority-Indication |
|
SMS Application Port ID |
SMS Application Port ID |
Application-Port-Identifier |
|
MTC IWF Address |
MTC IWF Address |
MTC-IWF-Address |
|
SMS Application Port ID |
SMS Application Port ID |
Application-Port-Identifier |
|
External Identifier |
External Identifier |
External-Identifier |
|
– |
MMS Information |
MMS-Information |
|
Originator IMSI |
Originator Address |
Originator-Address |
|
Originator MSISDN |
Originator Address |
Originator-Address |
|
Originator Other Address |
Originator Address |
Originator-Address |
|
Event Time stamp |
Submission Time |
Submission-Time |
|
Submission Time |
Submission Time |
Submission-Time |
|
SM Priority |
Priority |
Priority |
|
Message Reference |
Message Id |
Message-ID |
|
Message size |
Message Size |
Message-Size |
|
Message Class |
Message Class |
Message-Class |
|
SM Delivery Report Requested |
Delivery Report Requested |
Delivery-Report-Requested |
|
– |
PS Information |
PS-Information |
|
PDP Address |
PDP Address |
PDP-Address |
|
User Location Info |
3GPP User Location Info |
3GPP-User-Location-Info |
|
RAT Type |
3GPP RAT Type |
3GPP-RAT-Type |
|
UE Time Zone |
MS Time Zone |
3GPP-MS-Time-Zone |
|
Served IMEI |
User Equipment Info |
User-Equipment-Info |
|
Subscriber Equipment Number |
User Equipment Info |
User-Equipment-Info |
|
– |
IMS Information |
IMS-Information |
|
User Session Id |
User Session Id |
User-Session-Id |
|
Number Portability routing information |
Number Portability routing information |
Number-Portability-routing-information |
|
Carrier Select routing information |
Carrier Select routing information |
Carrier-Select-routing-information |
6.5 Definition of the SMS converged charging information
6.5.1 General
The Charging Information parameter used for SMS converged charging is provided in the following sub-clauses.
6.5.2 Definition of SMS charging information
SMS specific charging information used for SMS converged charging is provided within the SMS charging Information.
Table 6.5.2.1: Structure of SMS Charging information
|
Information Element |
Category |
Description |
|
Originator Info |
OM |
This field is a grouped field and holds information on originator of the SMS |
|
Originator SUPI |
OM |
This field holds the SUPI of the originator of the SMS, if available. This field is present if different from subscriber identifier field. |
|
Originator GPSI |
OC |
This field holds the GPSI of the originator of the SMS, if available. |
|
Originator Other Address |
OM |
This field holds the address of the originator of the SMS, when different from SUPI and GPSI, if available: e.g. email, short code. This field may have multiple occurences. |
|
Originator Received Address |
OC |
Described in table 6.3.1.2.1 |
|
Originator SCCP Address |
OC |
Described in table 6.3.1.2.1 |
|
SM Originator Interface |
OM |
Described in table 6.3.1.2.1 |
|
SM Originator Protocol Id |
OC |
Described in table 6.3.1.2.1: SM Protocol Id information element |
|
Recipient Info |
OC |
Described in table 6.3.1.2.1 |
|
Recipient SUPI |
OM |
This field holds the SUPI of the recipient of the SMS, if available. This field is present if different from subscriber identifier field. |
|
Recipient GPSI |
OC |
This field holds the GPSI of the recipient of the SMS, if available. |
|
Recipient Other Address |
OC |
This field holds the address of the recipient of the SMS, when different from SUPI and GPSI, if available: e.g. email, short code. This field may have multiple occurences |
|
Recipient Received Address |
OC |
Described in table 6.3.1.2.1 |
|
Recipient SCCP Address |
OC |
Described in table 6.3.1.2.1 |
|
SM Destination Interface |
OM |
Described in table 6.3.1.2.1 |
|
SM Recipient Protocol Id |
OC |
Described in table 6.3.1.2.1: SM Protocol Id information element. |
|
User Equipment Info |
OC |
This field holds the identification of the terminal (i.e. PEI, MAC Address) used by the UE the SMS transaction, if available. |
|
Roamer In Out |
OC |
This field holds an indication of the UE is an in-bound roamer. This field is present only if UE is identified as a roamer. |
|
User Location Info |
OC |
Described in table 6.3.1.1.1 |
|
UE Time Zone |
OC |
Described in table 6.3.1.1.1 |
|
RAT Type |
OC |
Described in table 6.3.1.2.1 "NR RedCap" value is also applicable. |
|
SMSC Address |
OM |
Described in table 6.3.1.1.1 |
|
SM Data Coding Scheme |
OM |
Described in table 6.3.1.2.1 |
|
SM Message Type |
OM |
Described in table 6.3.1.2.1 |
|
SM Reply Path Requested |
OC |
Described in table 6.3.1.2.1 |
|
SM User Data Header |
OC |
Described in table 6.3.1.2.1 |
|
SM Status |
OC |
Described in table 6.3.1.2.1 |
|
SM Discharge Time |
OC |
Described in table 6.3.1.2.1 |
|
Number of Messages Sent |
OC |
Described in table 6.3.1.2.1 |
|
SM Service Type |
OC |
Described in table 6.3.1.2.1 |
|
SM Sequence Number |
OC |
Described in table 6.3.1.2.1 |
|
SMS result |
C |
Described in table 6.3.1.2.1 |
|
Submission Time |
OC |
Described in table 6.3.1.1.1 |
|
SM Priority |
OC |
Described in table 6.3.1.1.1 |
|
Message Reference |
OM |
Described in table 6.3.1.1.1 |
|
Message Size |
OM |
Described in table 6.3.1.1.1 |
|
Message Class |
OM |
Described in table 6.3.1.1.1 |
|
Delivery Report Requested |
OC |
Described in table 6.3.1.1.1 |
6.5.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by SMS Node for 5G SMS 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.5.3.1 defines the basic structure of the supported fields in the Charging Data Request message for SMS converged charging.
Table 6.5.3.1: Supported fields in Charging Data Request message
|
Information Element |
Node Type |
SMSF |
|---|---|---|
|
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 |
|
|
Service Specification Information |
ITE |
|
|
Notify URI |
– |
|
|
Supported Features |
I-E |
|
|
Service Specification Information |
ITE |
|
|
Triggers |
– |
|
|
Multiple Unit Usage |
ITE |
|
|
Rating Group |
ITE |
|
|
Requested Unit |
I– |
|
|
Used Unit Container |
-TE |
|
|
SMS Charging Information |
||
|
Originator Info |
ITE |
|
|
Recipient Info |
ITE |
|
|
User Equipment Info |
ITE |
|
|
Roamer In Out |
ITE |
|
|
User Location Info |
ITE |
|
|
UE Time Zone |
ITE |
|
|
RAT Type |
ITE |
|
|
SMSC Address |
ITE |
|
|
SM Data Coding Scheme |
ITE |
|
|
SM Message Type |
ITE |
|
|
SM Reply Path Requested |
ITE |
|
|
SM User Data Header |
ITE |
|
|
SM Status |
ITE |
|
|
SM Discharge Time |
ITE |
|
|
Number of Messages Sent |
ITE |
|
|
SM Service Type |
ITE |
|
|
SM Sequence Number |
ITE |
|
|
SMS result |
ITE |
|
|
Submission Time |
ITE |
|
|
SMPriority |
ITE |
|
|
Message Reference |
ITE |
|
|
Message Size |
ITE |
|
|
Message Class |
ITE |
|
|
Delivery Report Requested |
ITE |
|
Table 6.5.3.2 defines the basic structure of the supported fields in the Charging Data Response message for SMS converged charging.
Table 6.5.3.2: Supported fields in Charging Data Response message
|
Information Element |
Node Type |
SMSF |
|---|---|---|
|
Supported Operation Types |
ITE |
|
|
Session Identifier |
ITE |
|
|
Invocation Timestamp |
ITE |
|
|
Invocation Result |
ITE |
|
|
Invocation Sequence Number |
ITE |
|
|
Session Failover |
I– |
|
|
Supported Features |
I-E |
|
|
Triggers |
– |
|
|
Multiple Unit information |
I-E |
|
|
Result Code |
I-E |
|
|
Rating Group |
I-E |
|
|
Granted Unit |
I– |
|
|
Validity Time |
I– |
|
|
Final Unit Indication |
– |
|
|
Time Quota Threshold |
– |
|
|
Volume Quota Threshold |
– |
|
|
Unit Quota Threshold |
– |
|
|
Quota Holding Time |
– |
|
|
Triggers |
– |
|
6.5.4 Formal SMS converged charging parameter description
6.5.4.1 SMS charging CHF CDR parameters
The detailed definitions, abstract syntax and encoding of the SMS charging CHF CDR parameters are specified in TS 32.298 [51].
6.5.4.2 SMS charging resources attributes
The detailed definitions of resources attributes used for SMS charging are specified in TS 32.291 [58].
6.6 Bindings for SMS converged charging
This mapping between the Information Elements, resource attributes and CHF CDR parameters for SMS converged charging is described in clause 7 of TS 32.291 [58].
Annex A (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in this specification.
Annex B (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
|
Sep 2007 |
SP-37 |
SP-070620 |
— |
— |
Submitted to TSG SA#37 for Information |
— |
1.0.0 |
|
|
Dec 2007 |
SP-38 |
SP-070748 |
— |
— |
Submitted to TSG SA#38 for Approval |
— |
2.0.0 |
8.0.0 |
|
Dec 2007 |
— |
— |
— |
— |
editHelp: the figures are now visible in normal view |
— |
8.0.0 |
8.0.1 |
|
Mar 2008 |
SP-39 |
SP-080074 |
0001 |
— |
Correction on Service Information for SMS Charging |
F |
8.0.1 |
8.1.0 |
|
Jun 2008 |
SP-40 |
SP-080330 |
0002 |
— |
Support of Number Portability and Carrier Selection in SMS Online Charging |
B |
8.1.0 |
8.2.0 |
|
Sep 2008 |
SP-41 |
SP-081216 |
0003 |
— |
Multiple SMS destination – Alignment with TS 23.040 |
C |
8.2.0 |
8.3.0 |
|
Sep 2008 |
SP-41 |
SP-081224 |
0004 |
— |
Introduce Online Charging from SMS-SC into 3GPP TS 32.274 |
B |
8.2.0 |
8.3.0 |
|
Dec 2008 |
SP-42 |
SP-080706 |
0005 |
— |
Correction on Multiple Unit Operation category |
F |
8.3.0 |
8.4.0 |
|
Dec 2008 |
SP-42 |
SP-080706 |
0006 |
— |
Add SMS-SC as SMS node type |
B |
8.3.0 |
8.4.0 |
|
Dec 2008 |
SP-42 |
SP-080706 |
0007 |
— |
Additional Address Info for SMS charging |
B |
8.3.0 |
8.4.0 |
|
Dec 2008 |
SP-42 |
SP-080706 |
0008 |
— |
Add charging of SMS services to 32.274 |
B |
8.3.0 |
8.4.0 |
|
Mar 2009 |
SP-43 |
SP-090045 |
0009 |
— |
SMS IE structure alignment |
F |
8.4.0 |
8.5.0 |
|
Jun 2009 |
SP-44 |
SP-090293 |
0010 |
— |
Clarification of "Termination charge" and application addressing |
F |
8.5.0 |
8.6.0 |
|
Sep 2009 |
SP-45 |
SP-090536 |
0011 |
— |
IE usage for Delivery Reports and Application Identifiers |
F |
8.6.0 |
8.7.0 |
|
Dec 2009 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
– |
8.7.0 |
9.0.0 |
|
Mar 2011 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
– |
9.0.0 |
10.0.0 |
|
Sep-2012 |
SP-57 |
SP-120575 |
0014 |
– |
Addition of MS Timezone for NetLoc |
B |
10.0.0 |
11.0.0 |
|
Mar 2013 |
SP-59 |
SP-130055 |
0017 |
1 |
Introduction of SMS-SC Offline Charging Architecture |
B |
11.0.0 |
12.0.0 |
|
Mar 2013 |
Editorial changes on CDR tables (MCC) |
12.0.0 |
12.0.1 |
|||||
|
Jun-2013 |
SP-60 |
SP-130274 |
0018 |
1 |
Introduction SMS Offline charging principles and flows |
B |
12.0.1 |
12.1.0 |
|
Dec-2013 |
SP-62 |
SP-130628 |
0020 |
1 |
Introduce Charging Data Request/Response in flow description |
B |
12.1.0 |
12.2.0 |
|
0021 |
– |
Introduction of offline charging Diameter error cases |
B |
|||||
|
0022 |
1 |
Introduction of Rf message content |
B |
|||||
|
Mar-2014 |
SP-63 |
SP-140045 |
0024 |
1 |
Introduction of information for SMS offline Charging |
B |
12.2.0 |
12.3.0 |
|
0027 |
– |
SCS Identity identified as Originator for Device Triggering |
B |
|||||
|
0028 |
1 |
Introduction of new SC-SMO and SC-SMT CDRs description |
B |
|||||
|
2014-07 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
– |
12.3.0 |
12.3.1 |
|
2014-09 |
SP-65 |
SP-140564 |
0029 |
1 |
Corrections for alignment between charging specifications |
F |
12.3.1 |
12.4.0 |
|
2014-12 |
SP-66 |
SP-140805 |
0030 |
– |
Corrections on definition for parameter category |
F |
12.4.0 |
12.5.0 |
|
2015-06 |
SP-68 |
SP-150327 |
0031 |
– |
Correction on category for MSISDN from Om to Oc for SMS CDRs |
F |
12.5.0 |
12.6.0 |
|
2016-01 |
Update to Rel-13 (MCC) |
12.6.0 |
13.0.0 |
|||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-09 |
SA#73 |
SP-160622 |
0032 |
1 |
F |
Correction on use of Multiple Operation and Multiple Unit Operation for IEC |
13.1.0 |
|
2016-12 |
SA#74 |
SP-160847 |
0033 |
1 |
F |
Correction SMS Delivery handling |
14.0.0 |
|
2017-03 |
SA#75 |
SP-170138 |
0034 |
1 |
D |
Remove reference to RFC 3588 |
14.1.0 |
|
2017-03 |
SA#75 |
SP-170135 |
0035 |
1 |
B |
Introduce charging principle for MSISDN-less MO-SMS via T4 |
14.1.0 |
|
2017-03 |
SA#75 |
SP-170135 |
0036 |
– |
B |
Introduce Message flows offline charging for MSISDN-less MO-SMS via T4 |
14.1.0 |
|
2017-03 |
SA#75 |
SP-170135 |
0037 |
1 |
B |
Remove Editor’s Note in clause 5.2.3, 5.2.4, 5.2.5, and 6.1.2 |
14.1.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0038 |
1 |
B |
Improve Message flows offline charging for SMS delivery |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0039 |
1 |
B |
Introduce additional Message flows offline charging for Device Triggering |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0040 |
1 |
B |
Introduce Message flows online charging for Device Triggering |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0041 |
1 |
B |
Introduce Message flows online charging for MSISDN-less MO-SMS via T4 |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0046 |
1 |
B |
Introduce new CDR for Device Triggering |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0047 |
– |
B |
Clarify the chargeable events for SMS via T4 |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0048 |
– |
B |
Remove T4 Device Trigger dedicated fields from SC-SMO and SC-SMT CDRs |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0049 |
1 |
B |
Introduce Device Trigger and SMS MO via T4 in SMS information |
14.2.0 |
|
2017-06 |
SA#76 |
SP-170500 |
0050 |
– |
B |
Introduce new CDR for SMS MO via T4 |
14.2.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0053 |
1 |
B |
Addition of Converged Charging |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0054 |
1 |
B |
Introduction of SMSF as a new Node for SMS charging |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0056 |
1 |
B |
Introduction of CHF CDR generation for SMSF |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0057 |
2 |
B |
Introduction of Message content charging SMSF |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0058 |
2 |
B |
Introduction of CHF CDR description for SMSF |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0059 |
3 |
B |
Introduction of SMS information converged charging |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0060 |
– |
B |
Introduction of 5GS for SMS charging via Ro Rf |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0061 |
1 |
B |
Introduction of offline charging for IP-SM-GW architecture and flows |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0062 |
1 |
B |
Introduction of offline charging for IP-SM-GW CDRs |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0063 |
1 |
B |
Introduction of Detailed message format |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0064 |
– |
B |
Introduction of clauses on formal description and binding |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181052 |
0680 |
1 |
B |
Addition of SMS Charging to CHF CDR |
15.1.0 |
|
2019-03 |
SA#83 |
SP-190117 |
0065 |
– |
F |
Correction of NF Consumer Information |
15.2.0 |
|
2019-03 |
SA#83 |
SP-190117 |
0066 |
– |
F |
Correction of category Invocation result |
15.2.0 |
|
2019-12 |
SA#86 |
SP-191163 |
0067 |
1 |
F |
Addition of Post Event Charging flows |
15.3.0 |
|
2019-12 |
SA#86 |
SP-191163 |
0068 |
– |
F |
Correction of message content for Post Event Charging |
15.3.0 |
|
2019-12 |
SA#86 |
SP-191160 |
0069 |
– |
F |
Correction of Service Specification Information |
15.3.0 |
|
2019-12 |
SA#86 |
SP-191163 |
0070 |
1 |
F |
Clarify CHF selection via NRF and roaming |
15.3.0 |
|
2019-12 |
SA#86 |
SP-191163 |
0071 |
1 |
F |
Correction of Multiple Unit Information |
15.3.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2020-09 |
SA#89e |
SP-200813 |
0076 |
– |
F |
Add Retransmission IE – non applicable |
16.1.0 |
|
2020-12 |
SA#90e |
SP-201051 |
0077 |
– |
F |
Correction on Triggers field for converged charging |
16.2.0 |
|
2020-12 |
SA#90e |
SP-201051 |
0079 |
1 |
F |
Correction of flows for IEC, ECUR and PEC |
16.2.0 |
|
2021-06 |
SA#92e |
SP-210418 |
0081 |
1 |
F |
Correcting SMS Result coding |
16.3.0 |
|
2021-06 |
SA#92e |
SP-210407 |
0080 |
1 |
C |
Correction on Reference Points for 5GS |
17.0.0 |
|
2022-06 |
SA#96 |
SP-220562 |
0084 |
1 |
A |
Add descriptions for SMS Charging information |
17.1.0 |
|
2022-06 |
SA#96 |
SP-220521 |
0085 |
1 |
B |
Add charging requirement for SMSF to support NR RedCap |
17.1.0 |
|
2022-09 |
SA#97e |
SP-220850 |
0087 |
2 |
F |
Correcting session and charging identifiers |
17.2.0 |