6 Definition of charging information
32.2783GPPCharging managementMonitoring event chargingRelease 17Telecommunication managementTS
6.1 Data description for monitoring event offline charging
6.1.1 Rf message contents
6.1.1.1 General
The Monitoring Event Offline Charging uses the Charging Data Transfer messages Charging Data Request and Charging Data Response defined in TS 32.299 [50].
The Charging Data Request can be of type event and includes all charging information. The Charging Data Response is an acknowledgement of the Charging Data Request.
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
|
Message |
Source |
Destination |
|
Charging Data Request |
MECN |
CDF |
|
Charging Data Response |
CDF |
MECN |
This clause describes 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.1.1.2 Charging data request message
Table 6.1.1.2.1 illustrates the basic structure of a Charging Data Request message from the MECN as used for Monitoring Event offline charging.
Table 6.1.1.2.1: Charging Data Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [50] |
|
Originator Host |
M |
Described in TS 32.299 [50] |
|
Originator Domain |
M |
Described in TS 32.299 [50] |
|
Destination Domain |
M |
Described in TS 32.299 [50] |
|
Operation Type |
M |
Described in TS 32.299 [50] |
|
Operation Number |
M |
Described in TS 32.299 [50] |
|
Operation Identifier |
OC |
Described in TS 32.299 [50] |
|
User Name |
OC |
Described in TS 32.299 [50] |
|
Destination Host |
OC |
Described in TS 32.299 [50] |
|
Operation Interval |
OC |
Described in TS 32.299 [50] |
|
Origination State |
OC |
Described in TS 32.299 [50] |
|
Origination Timestamp |
OC |
Described in TS 32.299 [50] |
|
Proxy Information |
OC |
Described in TS 32.299 [50] |
|
Route Information |
OC |
Described in TS 32.299 [50] |
|
Operation Token |
OM |
This field identifies the Monitoring Event Services. |
|
Service Information |
OM |
This field holds the Monitoring Event specific information described in clause 6.3. |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.1.1.3 Charging data response message
Table 6.1.1.3.1 illustrates the basic structure of a Charging Data Response message as used for the MECN.
Table 6.1.1.3.1: Charging Data Response message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Result |
M |
Described in TS 32.299 [50] |
|
Originator Host |
M |
Described in TS 32.299 [50] |
|
Originator Domain |
M |
Described in TS 32.299 [50] |
|
Operation Type |
M |
Described in TS 32.299 [50] |
|
Operation Number |
OC |
Described in TS 32.299 [50] |
|
Operation Identifier |
OC |
Described in TS 32.299 [50] |
|
Operation Interval |
OC |
Described in TS 32.299 [50] |
|
Error Reporting Host |
OC |
Described in TS 32.299 [50] |
|
Origination State |
OC |
Described in TS 32.299 [50] |
|
Origination Timestamp |
OC |
Described in TS 32.299 [50] |
|
Proxy Information |
OC |
Described in TS 32.299 [50] |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.1.2 Ga message contents
Refer to clause 5.2.4 for further information.
6.1.3 CDR description on the Bmn interface
6.1.3.1 General
The following standard CDR content and formats are considered:
– ME-CO-CDR generated for a single Monitoring Event configuration request.
– ME-RE-CDR generated for a set of Monitoring Event reports.
For each of the CDR types, a parameter table, which gives a short description of the parameters, is provided. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.1.3.2 Monitoring Event Configuration Request charging data (ME-CO-CDR)
If enabled, a Monitoring Event Configuration Request record shall be produced for each monitoring configuration request received. Renewal requests are captured in a separate record from the original request. The fields in the record are specified in table 6.1.3.2.1.
Table 6.1.3.2.1: Monitoring Event Configuration Request charging data (ME-CO-CDR)
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Monitoring Event Configuration Request |
|
Retransmission |
Oc |
This parameter, when present, indicates that information from retransmitted Accounting Requests has been used in this CDR. |
|
Record Opening Time |
OC |
A time stamp reflecting the time the CDF opened this record. |
|
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
|
Service Context Id |
OM |
This parameter indicates the CDR is applicable to Monitoring Event service. |
|
Node Id |
OM |
Name of the recording entity. |
|
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record Time Stamp |
OM |
This parameter indicates the date and time when the CDR was produced. |
|
Event Timestamp |
OM |
This parameter contains the timestamp of the event that triggered the generation of charging information for the Monitoring Event configuration request. |
|
Monitoring Event Configuration Activity |
M |
This parameter indicates the configuration action requested: create, transfer, update, and delete. |
|
SCEF Reference ID |
M |
This parameter, created by the SCEF, to identify a Monitoring Request. When combined with the SCEF Id, serves a globally unique identifier for the Monitoring Request. |
|
SCEF Id |
M |
This parameter indicates the SCEF to which the Monitoring Indication message has to be sent. |
|
Monitoring Type |
M |
This parameter identifies the specific Monitoring Event being requested. |
|
Maximum Number of Reports |
Oc |
This parameter, when present, indicates the maximum number of event reports to be generated until the associated Monitoring Event is considered to expire. A value of one implies a single event report is to be generated which makes it equivalent to a One-time Monitoring Request. This parameter is not applicable to the "Availability after DDN Failure" Monitoring Event type. |
|
Monitoring Duration |
Oc |
This parameter, when present, indicates the absolute time at which the related Monitoring Event request is considered to expire. |
|
Chargeable Party Identifier |
Oc |
This parameter, when present, identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements. |
|
Monitored User |
Oc |
This parameter identifies the user that is monitored and is applicable to the "Loss of connectivity", "UE reachability", "Location Reporting", "Communication Failure" and "Availability after DDN Failure" Monitoring Event types. |
|
Maximum Detection Time |
Oc |
This parameter, when present, indicates the maximum period of time without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable and is applicable to the "Loss of connectivity" Monitoring Event type. The value is on the order of 1 minute to multiple hours. |
|
Reachability Configuration |
Oc |
This parameter contains the details for configuration for UE reachability and is applicable to the "UE reachability" Monitoring Event type, which includes "Reachability Type", "Maximum Latency" and "Maximum Response Time". |
|
Location Type |
Oc |
This parameter indicates whether the request is for Current Location or Last Known Location and is applicable to the "Location Reporting" and "Number of UEs present in a geographic area" Monitoring Event type. |
|
Accuracy |
Oc |
This parameter indicates desired level of accuracy of the requested location information and is applicable to the "Location Reporting" Monitoring Event type. Accuracy could be at cell level (CGI/ECGI), eNB, TA/RA level. |
|
List of Locations |
Oc |
This parameter identifies the list of cells, eNBs and/or RAI(s)/TAI(s) for determination of the number of UEs in the area and is applicable to the "Number of UEs present in a geographic area" Monitoring Event type. |
|
Monitoring Event Config Status |
M |
This parameter identifies whether the request was successful or not. |
|
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.3.3 Monitoring Event Report charging data (ME-RE-CDR)
If enabled, a Monitoring Event Report record shall be produced for a set of Monitoring Event reports sent. In the normal case, only one Monitoring Event report will be included in the CDR. During times when a burst of Monitoring Event reports are sent, multiple event reports can be captured in the CDR. The fields in the record are specified in table 6.1.3.3.1.
Table 6.1.3.3.1: Monitoring Event Report charging data (ME-RE-CDR)
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
Monitoring Event Report |
|
Retransmission |
Oc |
This parameter, when present, indicates that information from retransmitted Accounting Requests has been used in this CDR. |
|
Record Opening Time |
OC |
A time stamp reflecting the time the CDF opened this record. |
|
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
|
Service Context Id |
OM |
This parameter indicates the CDR is applicable to Monitoring Event service. |
|
Node Id |
OM |
Name of the recording entity. |
|
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record Time Stamp |
OM |
This parameter indicates the date and time when the CDR was produced. |
|
List of Monitoring Event Report Data |
OM |
This parameter contains the charging information associated with a set of Monitoring Event reports. The fields for each report are specified in table 6.1.3.3.2. |
|
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
Table 6.1.3.3.2: Individual Monitoring Event Report charging data within List of Monitoring Event Report Data
|
Field |
Category |
Description |
|---|---|---|
|
Event Timestamp |
OM |
This parameter contains the timestamp of the event that triggered the generation of charging information for the Monitoring Event report. |
|
SCEF Reference ID |
M |
This parameter, created by the SCEF, to identify a Monitoring Request. When combined with the SCEF Id, serves a globally unique identifier for the Monitoring Request. |
|
SCEF Id |
M |
This parameter indicates the SCEF to which the Monitoring Indication message has to be sent. |
|
Monitoring Event Report Number |
M |
This parameter indicates the number of the report being sent for the specific request from this MECN. The number is monotonically increasing for each report starting at 1 for each unique request. |
|
Chargeable Party Identifier |
Oc |
This parameter, when present, identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements. |
|
Monitored User |
Oc |
This parameter identifies the user that is monitored and is applicable to the "Loss of connectivity", "UE reachability", "Location Reporting", "Communication Failure" and "Availability after DDN Failure" monitoring event types. |
|
Monitoring Type |
Oc |
This parameter identifies the specific Monitoring Event being reporting. |
|
Reachability Information |
Oc |
This parameter identifies the reachability status of the UE and is applicable to the "UE reachability" Monitoring Event type. |
|
Reported Location |
Oc |
This parameter indicates the reported 3GPP system specific location information and is applicable to the "Location Reporting" Monitoring Event type. |
|
Communication Failure Information |
Oc |
This parameter indicates the reported the reason for communication failure and is applicable to the "Communication Failure" Monitoring Event type. |
|
List of Number Of UEs Per Location Reports |
Oc |
This parameter contains a list of the location information along with the number of UEs found at each location by the MME/SGSN. It’s applicable to the "the number of UEs at a given geographic location" Monitoring Event type. |
6.2 Data description for monitoring event online charging
6.2.1 Ro message contents
Not specified in this document.
6.2.2 Monitoring event specific application information
Not specified in this document.
6.3 Monitoring event charging specific parameters
6.3.1 Definition of monitoring event charging information
6.3.1.1 Monitoring event charging information assignment for service information
The components in the Service Information that are used for Monitoring Event charging can be found in table 6.3.1.1.1.
Table 6.3.1.1.1: Service Information used for monitoring event 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]. |
|
Subscriber Identifier |
OC |
This field contains the identification of the monitored user (e.g. IMSI) if offline charging applies. It is not applicable for the "Number of UEs present in a geographic area" event. |
|
PS Information |
Oc |
This is a structured IE and hold PS specification parameters. |
|
Node Id |
Oc |
This IE holds the name of the Node. |
|
Monitoring Event Information |
OM |
This is a structured field and holds the Monitoring Event specific parameters. |
6.3.1.2 Definition of the monitoring event information
Monitoring Event specific charging information is provided within the Monitoring Event Information. The fields of the Monitoring Event Information are indicated with the node (MME, SGSN, IWK-SCEF) from which the information is sent.
The detailed structure of the Monitoring Event Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the monitoring event information
|
Information Element |
Category |
Description |
|
Monitoring Event functionality |
M |
This IE holds the Monitoring Event functionality is used, i.e. monitoring event configuration, monitoring event reporting. |
|
Event Timestamp |
Oc |
This parameter contains the timestamp of the event that triggered the generation of charging information. |
|
Monitoring Event Configuration Activity |
Oc |
This parameter indicates the configuration action requested: create, transfer, update, and delete. |
|
SCEF Reference ID |
Oc |
This parameter, created by the SCEF, to identify a Monitoring Request. When combined with the SCEF Id, serves a globally unique identifier for the Monitoring Request. |
|
SCEF Id |
Oc |
This parameter indicates the SCEF to which the Monitoring Indication message has to be sent. |
|
Monitoring Type |
Oc |
This parameter identifies the specific Monitoring Event being requested. |
|
Maximum Number of Reports |
Oc |
This parameter, when present, indicates the maximum number of event reports to be generated until the associated Monitoring Event is considered to expire. A value of one implies a single event report is to be generated which makes it equivalent to a One-time Monitoring Request. This parameter is not applicable to the "Availability after DDN Failure" Monitoring Event type. |
|
Monitoring Duration |
Oc |
This parameter, when present, indicates the absolute time at which the related Monitoring Event request is considered to expire. |
|
Chargeable Party Identifier |
Oc |
This parameter, when present, identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements. |
|
Maximum Detection Time |
Oc |
This parameter, when present, indicates the maximum period of time without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable and is applicable to the "Loss of connectivity" Monitoring Event type. The value is on the order of 1 minute to multiple hours. |
|
Reachability Configuration |
Oc |
This parameter contains the details for configuration for UE reachability and and is applicable to the "UE reachability" Monitoring Event type, which includes "Reachability Type", "Maximum Latency" and "Maximum Response Time".. |
|
Location Type |
Oc |
This parameter indicates whether the request is for Current Location or Last Known Location and is applicable to the "Location Reporting" and "Number of UEs present in a geographic area" Monitoring Event type. |
|
Accuracy |
Oc |
This parameter indicates desired level of accuracy of the requested location information and is applicable to the "Location Reporting" Monitoring Event type. Accuracy could be at cell level (CGI/ECGI), eNB, TA/RA level. |
|
Location information |
Oc |
This parameter identifiesan individual location, e.g. cells, eNBs and/or RAI(s)/TAI(s) for determination of the number of UEs in the area and is applicable to the "Number of UEs present in a geographic area" Monitoring Event type. It will be repeated for each location for which the number of UEs is requested. |
|
Monitoring Event Config Status |
Oc |
This parameter identifies whether the request was successful or not. When the request is not success, a specific value is chosen to indicate the error occurred during handling of the Requested action for the Monitoring event. |
|
Monitoring Event Report Data |
Oc |
This parameter contains the charging information associated with a Monitoring Event report. It shall be repeated for each report to be captured in the CDR. |
|
Event Timestamp |
OM |
This parameter contains the timestamp of the event that triggered the generation of charging information for the Monitoring Event report. |
|
SCEF Reference ID |
M |
This parameter, created by the SCEF, to identify a Monitoring Request. When combined with the SCEF Id, serves a globally unique identifier for the Monitoring Request. |
|
SCEF Id |
M |
This parameter indicates the SCEF to which the Monitoring Indication message has to be sent. |
|
Monitoring Event Report Number |
M |
This parameter indicates the number of the report being sent for the specific request from this MECN. The number is monotonically increasing for each report starting at 1 for each unique request. |
|
Chargeable Party Identifier |
Oc |
This parameter, when present, identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements. |
|
Monitored User |
Oc |
This parameter identifies the user that is monitored and is applicable to the "Loss of connectivity", "UE reachability", "Location Reporting", "Communication Failure" and "Availability after DDN Failure" monitoring event types. |
|
Monitoring Type |
Oc |
This parameter identifies the specific Monitoring Event being reporting. |
|
Reachability Information |
Oc |
This parameter identifies the reachability status of the UE and is applicable to the "UE reachability" Monitoring Event type. |
|
Reported Location |
Oc |
This parameter indicates the reported 3GPP system specific location information and is applicable to the "Location Reporting" Monitoring Event type. |
|
Communication Failure Information |
Oc |
This parameter indicates the reported the reason for communication failure and is applicable to the "Communication Failure" Monitoring Event type. |
|
Number Of UEs Per Location Report |
Oc |
This parameter contains the location information along with the number of UEs found at that location by the MME/SGSN. It’s applicable to the "the number of UEs at a given geographic location" Monitoring Event type. It shall be repeated for each location for which the number of UEs is reported. |
6.3.2 Formal monitoring event charging parameter description
6.3.2.1 Monitoring event CDR parameters
The detailed definitions, abstract syntax and encoding of the Monitoring Event CDR parameters are specified in TS 32.298 [51].
6.3.2.2 Monitoring event AVPs
The detailed definitions of Monitoring Event AVPs are specified in TS 32.299 [50].
6.3.3 Detailed message format for offline charging
The following clause specifies per Operation Type the charging data that are sent by MECN for different functionality, i.e. Monitoring Event configuration and Monitoring Event reporting.
The Operation Types are listed in the following order: S (Start)/I (Interim)/S (Stop)/E (Event). Therefore, when all Operation Types are possible it is marked as SISE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. SIS or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. SI-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 Charging Data Request message for Monitoring Event offline charging.
Table 6.3.3.1: Supported fields in Charging Data Request message
|
Information Element |
Service Type |
Monitoring Event Configuration |
Monitoring Event Reporting |
|---|---|---|---|
|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
|
|
Session Identifier |
—E |
—E |
|
|
Originator Host |
—E |
—E |
|
|
Originator Domain |
—E |
—E |
|
|
Destination Domain |
—E |
—E |
|
|
Operation Type |
—E |
—E |
|
|
Operation Number |
—E |
—E |
|
|
Operation Identifier |
—E |
—E |
|
|
User Name |
—E |
—E |
|
|
Destination Host |
—E |
—E |
|
|
Operation Interval |
—E |
—E |
|
|
Origination State |
—E |
—E |
|
|
Origination Timestamp |
—E |
—E |
|
|
Proxy Information |
—E |
—E |
|
|
Route Information |
—E |
—E |
|
|
Operation Token |
—E |
—E |
|
|
Subscriber Identifier |
—E |
—E |
|
|
Node Id |
—E |
—E |
|
|
Monitoring Event Functionality |
—E |
—E |
|
|
Event Timestamp |
—E |
—E |
|
|
Monitoring Event Configuration Activity |
—E |
||
|
SCEF Reference ID |
—E |
—E |
|
|
SCEF Id |
—E |
—E |
|
|
Monitoring Type |
—E |
—E |
|
|
Maximum Number of Reports |
—E |
– |
|
|
Monitoring Duration |
—E |
– |
|
|
Chargeable Party Identifier |
—E |
– |
|
|
Maximum Detection Time |
—E |
– |
|
|
Reachability Configuration |
—E |
– |
|
|
Location Type |
—E |
– |
|
|
Accuracy |
—E |
– |
|
|
Location information |
—E |
– |
|
|
Monitoring Event Config Status |
—E |
– |
|
|
Monitoring Event Report Data |
– |
—E |
|
|
Monitoring Event Report Number |
– |
—E |
|
|
Monitored User |
– |
—E |
|
|
Reachability Information |
– |
—E |
|
|
Reported Location |
– |
—E |
|
|
Communication Failure Information |
– |
—E |
|
|
Number Of UEs Per Location Report |
– |
—E |
|
Table 6.3.3.2 illustrates the basic structure of the supported fields in the Charging Data Responsemessage for Monitoring Event offline charging.
Table 6.3.3.2: Supported fields in Charging Data Response message
|
Information Element |
Service Type |
Monitoring Event Configuration |
Monitoring Event Reporting |
|---|---|---|---|
|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
|
|
Session Identifier |
—E |
—E |
|
|
Operation Result |
—E |
—E |
|
|
Originator Host |
—E |
—E |
|
|
Originator Domain |
—E |
—E |
|
|
Operation Type |
—E |
—E |
|
|
Operation Number |
—E |
—E |
|
|
Operation Identifier |
—E |
—E |
|
|
Operation Interval |
—E |
—E |
|
|
Error Reporting Host |
—E |
—E |
|
|
Origination State |
—E |
—E |
|
|
Origination Timestamp |
—E |
—E |
|
|
Proxy Information |
—E |
—E |
|
|
Route Information |
—E |
—E |
|
6.3.4 Detailed message format for online charging
Not specified in this document.
6.4 Bindings for monitoring event offline charging
This clause aims to describe the mapping between the Diameter Accounting AVPs, IEs and CDR parameters for Monitoring Event offline charging.
Table 6.4.1 describes the mapping of the Diameter Accounting AVPs, IEs, and CDR parameters of ME-CO-CDR and ME-RE-CDR in Monitoring Event offline charging.
Table 6.4.1: Bindings of CDR Parameters, Information Elements and AVPs
|
CDR Parameter |
Information Element |
AVP |
|---|---|---|
|
Record Opening Time |
– |
– |
|
Local Record Sequence Number |
– |
– |
|
Service Context Id |
Service Context Id |
Service-Context-Id |
|
Service Information |
Service-Information |
|
|
Monitored User |
Subscriber Identifier |
Subscription-Id |
|
Monitoring Event Information |
Monitoring-Event-Information |
|
|
Record Type |
Monitoring Event Functionality |
Monitoring-Event-Functionality |
|
Event Timestamp |
Event Timestamp |
Event-Timestamp |
|
Monitoring Event Configuration Activity |
Monitoring Event Configuration Activity |
Monitoring-Event-Configuration- Activity |
|
SCEF Reference ID |
SCEF Reference ID |
SCEF-Reference-ID |
|
SCEF Id |
SCEF Id |
SCEF-ID |
|
Monitoring Type |
Monitoring Type |
Monitoring-Type |
|
Maximum Number of Reports |
Maximum Number of Reports |
Maximum-Number-of-Reports |
|
Monitoring Duration |
Monitoring Duration |
Monitoring-Duration |
|
Chargeable Party Identifier |
Chargeable Party Identifier |
Charged-Party |
|
Maximum Detection Time |
Maximum Detection Time |
Maximum-Detection-Time |
|
Reachability Configuration |
Reachability Configuration |
UE-Reachability-Configuration |
|
Location Type |
Location Type |
MONTE-Location-Type |
|
Accuracy |
Accuracy |
Accuracy |
|
List of Locations |
Location information |
Number-Of-UE-Per-Location-Configuration |
|
Monitoring Event Config Status |
Monitoring Event Config Status |
Monitoring-Event-Config-Status |
|
List of Monitoring Event Report Data |
Monitoring Event Report Data |
Monitoring-Event-Report-Data |
|
Event Timestamp |
Event Timestamp |
Event-Timestamp |
|
SCEF Reference ID |
SCEF Reference ID |
SCEF-Reference-ID |
|
SCEF Id |
SCEF Id |
SCEF-ID |
|
Monitoring Event Report Number |
Monitoring Event Report Number |
Monitoring-Event-Report-Number |
|
Chargeable Party Identifier |
Chargeable Party Identifier |
Charged-Party |
|
Monitored User |
Monitored User |
Subscription-Id |
|
Monitoring Type |
Monitoring Type |
Monitoring-Type |
|
Reachability Information |
Reachability Information |
Reachability-Information |
|
Reported Location |
Reported Location |
EPS-Location-information |
|
Communication Failure Information |
Communication Failure Information |
Communication-Failure-Information |
|
List of Number Of UEs Per Location Report |
Number Of UEs Per Location Report |
Number-Of-UE-Per-Location-Report |
|
PS Information |
PS-Information |
|
|
Node Id |
Node Id |
Node-ID |
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
Oct 2015 |
— |
— |
S5-155265:TS 32.278 v0.0.0 MONTE charging skeleton S5-155266:Rel-13 pCR 32.278 General Sections for Monitoring Event Charging S5-155267:Rel-13 pCR 32.278 High level Monitoring Event architecture S5-155268:Rel-13 pCR 32.278 Monitoring Event offline charging and online charging architecture S5-155269:Monitoring Event Recording |
0.1.0 |
|||
|
Nov 2015 |
— |
— |
S5-156194: changes for EditHelp S5-156051: Corrections for Monitoring Event charging S5-156294: Charging principles for Monitoring Event charging S5-156195: Rf, Ga, Ro message content of Monitoring Event charging |
0.1.0 |
0.2.0 |
||
|
Dec 2015 |
SA#70 |
SP-150685 |
Presented for information |
0.2.0 |
1.0.0 |
||
|
Jan 2016 |
— |
— |
S5-161258: CDR parameters alignment S5-161259: charging information definition and bindings |
1.0.0 |
1.1.0 |
||
|
Feb 2016 |
SA#71 |
SP-160024 |
Minor MCC editorial corrections and presentation for approval. |
1.1.0 |
2.0.0 |
||
|
Mar 2016 |
Upgrade to change control version |
2.0.0 |
13.0.0 |
||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
SP-170138 |
0003 |
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 |