6.5 Charging Requirements

Table 11: Charging Requirements

Requirement ID Description Release
CHG-001 The oneM2M System shall support collection of charging specific information related to the individual services facilitated by the oneM2M System (e.g. Data Management, Device Management and/or Connectivity Management).
Collection of charging specific information shall be possible concurrent with the resource usage. The format of the recorded information shall be fully specified including mandatory and optional elements.
Implemented in Rel-1
(see note 4)
CHG-002 The oneM2M System shall support mechanisms to facilitate correlation of charging information (e.g. of a User) collected for M2M Services, M2M Application Services and services provided by Underlying Network Operators. Partially implemented
(see note 2)
CHG-003 The oneM2M System shall provide means to coordinate charging data records for data usages with differentiated QoS from the Underlying Network. Not implemented
CHG-004 The oneM2M System shall be able to utilize existing charging mechanisms of Underlying Networks. Not implemented
(see note 3)
CHG-005 The oneM2M System shall support transfer of the charging information records to the billing domain of the M2M Service Provider, for the purpose of:
subscriber billing;
inter-provider billing;
provider-to-subscriber accounting including additional functions like statistics.
Implemented in Rel-1
CHG-006 The oneM2M System should support generation of charging events for the purpose of requesting resource usage Authorization from the real time credit control system where the subscriber account is located. The information contained in the charging events and the relevant chargeable events shall be fully specified including mandatory and optional elements (see note 1). Not implemented
CHG-007
See REQ-2017-0031R05
The oneM2M System shall support mechanisms to correlate charging information (e.g. data/records) from different M2M Application Service Providers. Rel-3/ future releases?
CHG-008
See ARC-2018-0062
The oneM2M System shall support charging event detection, statistics collection and charging records generation mechanisms based on M2M Service Subscriber and M2M Service User identification.

NOTE1: A chargeable event is any activity, a provider may want to charge for that utilizes the resources and related M2M Services offered by such provider. A charging event is the set of charging information needed by the credit control system for resource authorization.

NOTE 2: Information collected can be sent to the Underlying Networks which may used it for charging.

NOTE 3: The oneM2M service layer can pass info to Underlying Networks but cannot use Underlying Network mechanism. Charging can be done by Underlying Network. This is covered by CHG-002.

NOTE 4: Only supported in the Infrastructure Node.