Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 21.917  Word version:  17.0.1

Top   Top   Up   Prev   Next
0…   5…   5.2   6…   6.3…   6.3.2…   6.3.3…   6.3.4…   7…   7.4…   8…   9…   10…   11…   11.9…   12…   13…   14…   15…   15.6…   16…   17…   18…   18.10…   19…

 

12  New Radio (NR) enhancements other than layer 1p. 123

12.1  NR Uplink Data Compression (UDC)p. 123

UID Name Acronym WG WID WI rapporteur name/company
911006NR Uplink Data Compression (UDC)NR_UDCRP-220140CATT
911106Core part: NR_UDCNR_UDC-CoreR2RP-220140CATT
Summary based on the input provided by CATT in RP-220142.
This work item specifies NR Uplink Data Compression (UDC), i.e. uplink data can be compressed at the UE and can be decompressed at the NG-RAN node.
In this WI, DEFLATE based UDC solution is introduced which uses LTE UDC as baseline.
DEFLATE based UDC solution could achieve higher compression efficiency which would save more uplink resources and reduce the transmission latency. The NG-RAN node can configure the UE to use UDC or not. If UDC is configured for a DRB, ROHC or EHC is not used for that DRB. One byte UDC header is introduced to indicate whether the PDCP SDU is compressed by UDC or not, whether the compression buffer is reset or not, and 4 validation bits of checksum are used to indicate whether the compression and decompression buffers are synchronous. For each DRB, the maximum compression buffer is 8192 bytes. If there are errors or failures due to buffer mismatching, the NG-RAN node can send a PDCP control PDU for error notification to the UE, the UE may reset the compression buffer when such notification has been received.
Similar as for LTE UDC, to improve compression efficiency of the first packets, two types of pre-defined dictionary can be used for UDC. One is standard dictionary for SIP and SDP signalling as defined in RFC 3485, and another is operator defined dictionary. The NG-RAN node configures whether or which dictionary is used for a UDC DRB.
NR UDC can be applied to NR-DC, NE-DC and NGEN-DC scenarios. Also, NR UDC can be applied to split bearer type. For NR-DC, NE-DC and NGEN-DC scenarios, MN can send an indication to SN regarding the maximum number of UDC DRBs allowed to SN terminated bearer. Furthermore, NR UDC can also be applied to CU CP and UP splitting scenario, where corresponding configuration parameters can be carried via E1 interface.
NR UDC continuity is also supported, which is similar as the ROHC continuity mechanism.
UDC related capabilities are also defined for UEs. There are four capabilities defined: supporting basic UDC function, supporting standard dictionary, supporting operator defined dictionary, and supporting UDC continuity. If the UE supports operator defined dictionary, it shall report the version of the dictionary and the associated PLMN ID to assist the NG-RAN node to identify the dictionary stored by the UE. The NG-RAN node configures UDC according to the signalled UE capabilities.
References
Related CRs:
[12.1-1]
RP-220141: Status Report for WI: NR Uplink Data Compression (UDC); CATT
Up

12.2  NR QoE management and optimizations for diverse servicesp. 123

UID Name Acronym WG WID WI rapporteur name/company
911008NR QoE management and optimizations for diverse servicesNR_QoERP-211406China Unicom
911108Core part: NR QoE management and optimizations for diverse servicesNR_QoE-CoreR3RP-211406China Unicom
860061Study on NR QoE (Quality of Experience) management and optimizations for diverse servicesFS_NR_QoER3RP-193256China Unicom
Summary based on the input provided by China Unicom in RP-220556.
This WI specifies the NR QoE functionality.
The QoE Measurement Collection function enables the collection of application layer measurements from the UE. The measurements are supported for Streaming services, MTSI services, and VR services. Both signalling based and management based QoE measurement collection are supported. In this Release, basic application layer measurement collection mechanism is supported, and RAN visible QoE measurement mechanism and metrics are supported.
In the WI, the feature of QoE Measurement Collection function 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), using UE-associated signalling. One or more QoE measurement collection jobs can be activated at a UE per service type. The application layer measurement configuration and measurement reporting is supported in RRC_CONNECTED state only. The 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. When a service is provided within a configured slice, the QoE Measurement Collection 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.
The 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 for RAN overload situation. The gNB can send a downlink RRC message to temporarily stop the application layer measurement reports associated to one or multiple QoE configurations from UE to the network.
The QoE Measurement Collection continuity for intra-system intra-RAT mobility is supported in R17, with the area scope parameters configured by the OAM. The NG-RAN node is responsible for keeping track and identify 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 NG-RAN node indicates to the UE to release the QoE configuration.
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 to 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 service.
Radio-related measurements may be collected via immediate MDT for the supported services. The MCE/TCE performs the correlation of the immediate MDT results and the QoE measurement results collected at the same UE.
The following alignments are supported in this Release:
  • Alignment between a signalling-based QoE measurement and a signalling-based MDT measurement.
  • Alignment between a management-based QoE measurement and a management-based MDT measurement.
References
Related CRs:
[12.2-1]
RP-220554: Status report of SR for WI on NR QoE, China Unicom
Up

Up   Top   ToC