Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.9…   16.10…   16.12…   16.13…   16.14…   17…   18…   19…   A…   B…   C…

 

19  Support for NR coverage enhancements |R17|Word‑p. 182

To improve NR uplink coverage for both FR1 and FR2, the following enhancements on PUSCH, PUCCH and MSG3 PUSCH are supported:
  • Enhanced aggregation of multiple slots with TB repetition is supported for both PUSCH transmission with dynamic and configured grant. In addition, counting based on available slots is supported. The maximum number of aggregated slots for counting based on available slots and counting based on physical slots are both 32.
  • TB processing over multiple slots with and without repetition is supported for both PUSCH transmission with dynamic grant and configured grant. For a single transmission of TB processing over multiple slots PUSCH, the TB size is determined based on multiple slots.
  • DMRS bundling where the UE maintains phase continuity and power consistency across PUSCH transmissions or PUCCH repetitions to enable improved channel estimation is supported. Inter-slot frequency hopping with DMRS bundling is supported.
  • Dynamic PUCCH repetition factor indication configured per PUCCH resource is introduced, applicable to all PUCCH formats.
  • Aggregation of multiple slots with TB repetition for MSG3 transmission is supported on both NUL and SUL, applicable to CBRA with 4-step RA type. If configured, the UE requests MSG3 repetition via separate PRACH resource when the RSRP of DL path-loss reference is lower than a configured threshold.
Up

20  Support for Multi-USIM devices |R17|Word‑p. 183

20.1  GeneralWord‑p. 183

NG-RAN may support one or more of the following enhancements for MUSIM device operation:
  • Paging Collision Avoidance, as described in clause 20.2;
  • UE notification on Network Switching, as described in clause 20.3;

20.2  Paging Collision AvoidanceWord‑p. 183

The purpose of paging collision avoidance is to address the overlap of paging occasions on both USIMs when a MUSIM device (e.g. dual USIM device) is in RRC_IDLE/RRC_INACTIVE state in both the networks (e.g. Network A and Network B) associated with respective USIMs. Network A is NR and Network B is E-UTRA or NR.
A MUSIM device may determine potential paging collision on two networks and may trigger actions to prevent potential paging collision on NR network as specified in TS 23.501.
Up

20.3  UE notification on Network SwitchingWord‑p. 183

For MUSIM operation, a MUSIM device in RRC_CONNECTED state in Network A may have to switch from Network A to Network B. Network A is NR and Network B can either be E-UTRA or NR. Before switching from Network A, a MUSIM device should notify Network A to either leave RRC_CONNECTED state, or be kept in RRC_CONNECTED state in Network A while temporarily switching to Network B.
When configured to do so, a MUSIM device can signal the network A a preference to leave RRC_CONNECTED state by using RRC or NAS signaling. After sending a preference to leave RRC_CONNECTED state by using RRC signaling, if the MUSIM device does not receive an RRCRelease message from the Network A within a certain time period (configured by the Network A), the MUSIM device can enter RRC_IDLE state in Network A.
When configured to do so, a MUSIM device can signal the network A a preference to be kept in RRC_CONNECTED state in Network A while temporarily switching to network B. This is indicated by scheduling gaps preference.This preference can include information for setup or release of gap(s). The network A can configure at most 3 gap patterns for MUSIM purpose: two periodic gaps and a single aperiodic gap.
Up

21  Application Layer Measurement Collection |R17|Word‑p. 184

21.1  OverviewWord‑p. 184

The QoE Measurement Collection function enables collection of application layer measurements from the UE. The supported service types are:
  • QoE Measurement Collection for streaming services;
  • QoE Measurement Collection for MTSI services;
  • QoE Measurement Collection for VR services.
Both signalling based and management based QoE measurement collection are supported.
Up

21.2  QoE Measurement ConfigurationWord‑p. 184

21.2.1  QoE Measurement Collection Activation and ReportingWord‑p. 184

The feature is activated in the NG-RAN either by direct configuration from the OAM system (management-based activation), or by signalling from the OAM via the Core Network (signalling-based activation), containing UE-associated QoE configuration. One or more QoE measurement collection jobs can be activated at a UE per service type, and each QoE measurement configuration is uniquely identified by a QoE Reference.
For signalling-based QoE measurements, the OAM initiates the QoE measurement activation for a specific UE via the Core Network, and the NG-RAN node receives one or more QoE measurement configurations by means of UE-associated signalling. The QoE measurement configuration for signalling-based activation includes an application layer measurement configuration list and the corresponding information for QoE measurement collection, e.g., QoE Reference, service type, MCE IP Address, Slice Scope, Area Scope, MDT Alignment Information and the indication of available RAN visible QoE metrics. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node forwards the corresponding QoE measurement configuration(s) to the UE in a downlink RRC message containing AppLayerMeasConfig, as specified in TS38.331 [12].
For management-based QoE measurement activation, the OAM sends one or more the QoE measurement configurations to the NG-RAN node. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and the corresponding information for QoE measurement collection. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node selects UE(s) that meet the required QoE measurement capability, Area Scope and Slice Scope.
The UE reports QoE measurement results to the NG-RAN node in an uplink RRC message, as specified in TS38.331 [12]. The NG-RAN node transmits the QoE report and the corresponding QoE Reference ID to the MCE.
The QoE measurement collection is handled by application layer measurement configuration and measurement reporting, supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE as Application layer configuration in the RRCReconfiguration message (there can be multiple configurations in the same message). Application layer measurement reports received from UE's higher layer are encapsulated in a transparent container and sent to the network in the MeasurementReportAppLayer message, as specified in TS 38.331. The UE can send multiple application layer measurement reports to the gNB in one MeasurementReportAppLayer message. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. A measConfigAppLayerId conveyed in the RRC signalling is used to identify the application layer measurement configuration and report between the gNB and the UE. The RRC identifier is mapped to the QoE Reference in the gNB. The application layer measurement report is forwarded to OAM together with the QoE Reference. gNB can release one or multiple application layer measurement configurations from the UE in one RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session starts or stops for a certain application layer measurement configuration.
Up

21.2.2  QoE Measurement Collection DeactivationWord‑p. 185

QoE Measurement Collection deactivation permanently stops all or some of QoE measurement collection jobs towards a UE, resulting in the release of the corresponding QoE measurement configuration(s) in the UE. The deactivation of QoE measurement collection is supported by using UE-associated signalling. A list of QoE Reference is used to deactivate the corresponding QoE measurement collection job(s).
Upon reception of QoE release command in an application layer measurement configuration, the UE discards any unsent application layer measurement reports corresponding to the released application layer configuration. The UE discards the reports received from application layer when it has no associated application layer measurement configuration configured.
The network can replace a configuration with another one by deactivating an existing measurement and configuring another measurement of the same configuration type.
Up

21.2.3  Handling of QMC during RAN OverloadWord‑p. 185

QoE Measurement Collection pause/resume procedure is used to pause/resume the reporting for all QoE reports or to pause/resume QoE reporting per QoE configuration in a UE in RAN overload situation.
gNB can use the RRCReconfiguration message to temporarily stop application layer measurement reports associated to one or multiple application layer measurement configurations from being sent from the UE to the gNB. When the UE receives the QoE pause indication, UE temporarily stores application layer measurement reports in AS layer. When the UE receives the QoE resume indication, UE sends the stored application layer measurement reports to the gNB.
Up

21.2.4  QoE Measurement Handling in RRC_IDLE and RRC_INACTIVE StatesWord‑p. 185

If the UE enters RRC_INACTIVE, the UE AS configuration for the QoE is stored in the UE Inactive AS context.
If the UE enters RRC_IDLE state, the UE releases all the application layer measurement configurations.

21.2.5  Per-slice QoE MeasurementWord‑p. 185

When a service is provided within a configured slice, the QoE Measurement for this service type could also be configured together with the corresponding slice scope, so that the user experience of this service could also be evaluated on a per-slice basis. Multiple QoE measurement configurations can be configured for the same service type with different slices, where each QoE measurement configuration is identified with a QoE Reference.
The UE includes the slice ID inside the QoE report container when reporting QoE measurement.
Up

21.3  QoE Measurement Continuity for MobilityWord‑p. 185

The QoE Measurement Collection continuity for intra-system intra-RAT mobility is supported, with the Area Scope parameters configured by the OAM, where the network is responsible for keeping track of whether the UE is inside or outside the Area Scope. A UE should continue an ongoing measurement even if it leaves the Area Scope, unless the network indicates to the UE to release the QoE configuration.
For RRC_CONNECTED state mobility, the source NG-RAN node may transmit the QoE measurement configuration(s) and/or the information related to the configuration(s) of a specific UE to the target NG-RAN node via XnAP or NGAP. For signalling-based QoE, QoE Reference, MCE IP Address, Measurement Configuration Application layer ID, MDT Alignment Information, Area Scope, Slice Scope and Measurement Status are passed to the target node. For management-based QoE, Measurement Configuration Application Layer ID, MCE IP Address and Measurement Status are passed to the target node. For RRC_INACTIVE state mobility, QoE measurement configuration(s) of a specific UE can be restored from the node hosting the UE context when it resumes to RRC_CONNECTED state. Multiple sets of QoE measurement configurations should be supported during mobility.
For signalling based QoE, at handover to a target gNB which supports QoE, the target gNB decides which application layer measurement configurations to keep and which to release, e.g. based on application layer measurement configuration information received from the source gNB in Xn/NG signalling.
When the UE resumes the connection in a gNB not supporting QoE, the UE releases all application layer measurement configurations.
Up

21.4  RAN Visible QoE MeasurementsWord‑p. 186

RAN visible QoE measurements are configured by the NG-RAN node, where a subset of QoE metrics is reported from the UE as an explicit IE readable by the NG-RAN node. RAN visible QoE measurements (e.g., RAN visible QoE metrics, RAN visible QoE values) could be utilized by the NG-RAN node for network optimization. RAN visible QoE measurements are supported for the DASH streaming and VR services. The NG-RAN node configures the RAN visible QoE measurement to collect all or some of the available RAN visible QoE metrics, where the indication of metric availability is received from the OAM or CN. The set of available RAN visible QoE metrics is a subset of the metrics which are already configured as part of QoE measurement configuration encapsulated in the transparent container. The PDU session ID(s) corresponding to the service that is subject to QoE measurements can also be reported by the UE along with the RAN visible QoE measurement results.
RAN visible QoE measurements can be reported with a reporting periodicity different from the one of regular QoE. If there is no reporting periodicity defined in the RAN visible QoE configuration, RAN visible QoE reports should be sent together with the legacy QoE reports.
RAN visible application layer measurement is supported only for streaming and VR services. The gNB can use RAN visible application layer measurement configurations to instruct the UE to collect application layer measurements for RRM purposes. Multiple simultaneous RAN visible application layer measurements configuration and reports can be supported for RAN visible application layer measurement, and each RAN visible application layer measurement configuration and report is identified by the same measConfigAppLayerId as the application layer measurement configuration and measurement report. gNB configures the required RAN visible QoE metrics in the RAN visible application measurement configuration for the UE to report. After receiving the RAN visible application layer measurement configuration, the UE RRC layer forwards the configuration to the application layer, indicating the service type, the RRC identifier and the periodicity. RAN visible application layer configuration can only be configured if there is a corresponding application layer measurement configuration for the same service type configured at the UE. The application layer sends the RAN visible application layer measurement report associated with the RRC identifier to the UE's AS layer. UE can send both RAN visible application layer measurement reports and the application layer measurement reports to the gNB in the same MeasurementReportAppLayer message. gNB can release one or multiple RAN visible application layer measurement configurations from the UE in one RRC message at any time.
The UE still reports the configured RAN visible application layer measurements, even though the corresponding non RAN visible application layer measurement reporting is paused.
Up

21.5  Alignment of MDT and QoE MeasurementsWord‑p. 186

Radio-related measurements may be collected via immediate MDT for all types of supported services for the purpose of QoE analysis. The MCE/TCE performs the correlation of the immediate MDT results and the QoE measurement results collected at the same UE.
The following is supported:
  • Alignment between a signalling-based QoE measurement and a signalling-based MDT measurement. In this case, the signalling-based QoE configuration sent to the NG-RAN node includes the NG-RAN Trace ID of the signalling-based MDT measurement.
  • Alignment between a management-based QoE measurement and a management-based MDT measurement.
The UE configured for QoE measurements can send to the NG-RAN node a Session Start Indication or a Session End Indication to inform the NG-RAN node about the start or the end of a session of configured QoE measurements. The NG-RAN node can activate the MDT measurements that are to be aligned with the QoE measurements performed by the UE upon/after receiving the Session Start Indication from the UE. The NG-RAN node may activate the MDT measurements upon/after receiving the MDT activation message from OAM. The NG-RAN node can deactivate the aligned MDT measurements according to OAM command which may, e.g., be triggered by the Session End Indication.
The NG-RAN node includes time stamp information to the QoE reports to enable the correlation of corresponding measurement results of MDT and QoE at the MCE/TCE. In addition, the NG-RAN node includes the MDT session identifiers (Trace Reference and Trace Recording Session Reference) to the corresponding QoE report.
Up

Up   Top   ToC