Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 32.817  Word version:  14.1.0

Top   Top   None   None   Next
0…   2…

 

0  IntroductionWord‑p. 4

Data volume measurements for RAN sharing are specified in TS 36.314:
4.1.9 Data Volume for Shared Networks
The objective of this measurement is to measure the data volume transmitted or received by the eNB in a configured measurement period, for the different PLMN identities in a shared network. The measurement is performed per configured PLMN ID per configured QoS profile criteria.
The QoS profile criteria may include one or more of the following criteria: one QCI indicator, one GBR Indicator, one ARP Indicator, where
  • a QCI Indicator identifies one specific QCI value. QCI values range from 1 to 256. If the indicator is not set then all QCI values should be taken into account.
  • a GBR Indicator identifies one GBR range value defined by OAM. If the indicator is not set then all GBR ranges should be taken into account.
  • an ARP Indicator identifies one ARP priority value. ARP values range from 1 to 15. If the indicator is not set then all ARP priority values should be taken into account.
The QoS profile criteria are satisfied when all the configured indicators are matched. It is possible that none of the QoS parameters are configured in which case the measurement is collected per configured PLMN ID.
4.1.9.1 Data volume for shared networks in DL
Protocol Layer: PDCP
Definition
Data Volume for shared networks in DL. Amount of PDCP SDU bits in downlink delivered from PDCP layer to RLC layer in a measurement period. The measurement is performed per configured PLMN ID per configured DL QoS profile criteria.
The unit is Mbit.
4.1.9.2 Data Volume for shared networks in UL
Protocol Layer: PDCP
Definition
Data Volume for shared networks in UL. Amount of PDCP SDU bits successfully received by the eNB in uplink in a measurement period. The measurement is performed per configured PLMN ID per configured UL QoS profile criteria.
The unit is Mbit.
 
TS 36.300 specified the following for Resource usage reporting for shared networks:
23.12 Resource usage reporting for shared networks
The eNB may be configured to report the resource usage as data volume for the different PLMN identities of the operators in a shared network. The measurements, which are defined in TS 36.314, are based on the QoS parameter values exchanged at E-RAB setup/modification.
OAM configures data volume reporting criteria. The configured data volume criteria define the PLMN IDs and the QoS profile criteria for the collection and reporting. The data volume reports are per configured PLMN ID and per configured QoS profile per DL/UL.
The QoS profile configuration shall be the same for all configured PLMN IDs and for all eNBs. The configured QoS profile criteria can differ in UL and DL in terms of GBR ranges. It shall be possible to collect and report up to 200 counter types and a maximum of 200 counter instances.
Data volumes for the DL/UL direction of a GBR bearer shall be collected within a given DL/UL GBR range if the DL/UL E-RAB guaranteed bit rate is within a configured DL/UL range delimited by a minimum and maximum value. The GBR ranges shall be five in number for DL and five in number for UL. GBR ranges shall be non-overlapping and configurable. The configured set of GBR ranges applies to the whole RAN and to all PLMN IDs in the RAN. "
 
This means that the PM mechanism needs to be changed to support limitation of the number of measurements. It is further necessary to ensure that the report format supports to describe how these measurements are defined or limited.
The solutions might be beneficial also for other measurements.
Up

1  ScopeWord‑p. 6

The study is to investigate:
  • Solutions for how to manage measurement collection in network sharing context over Itf-N.
  • Solutions for how to indicate high reliability to different E-UTRAN measurements.
  • Whether the PM file format would need to be changed and possible solutions.
The solution is intended to be valid for data volume measurements, but a more generically applicable solution should be considered, if feasible. The solution can be valid also for non-shared networks.

Up   Top   ToC