A Blog dedicated to Declutter 3GPP specifications

Showing posts with label LTE. Show all posts
Showing posts with label LTE. Show all posts

Monday, November 16, 2020

Mobility enhancement in E-UTRAN Release -16


 Dual Active Protocol Stack (DAPS) handover

DAPS Handover is a handover procedure that maintains the source eNB connection after reception of RRC message for handover and until releasing the source cell after successful random access to the target eNB.

-    If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB.

-    Upon reception of the handover command, the UE:

-     Creates a MAC entity for target cell;

-     Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

-     For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

-     Retains rest of the source link configurations until release of the source.

-     When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

Conditional Handover (CHO)

A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met.

-    UE maintains connection with source eNB after receiving CHO configuration, and starts evaluating the CHO execution condition(s) for the CHO candidate cell(s) and executes the HO command once the execution condition(s) are met for a CHO candidate cell.

-    To improve the robustness, the network can provide the up to 8 candidate cell configuration(s) associated with execution condition (s) to UE. If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source eNB, applies the stored corresponding configuration for that candidate cell and synchronises to that candidate cell. UE stops evaluating the execution condition(s) for other candidate cells once the handover is triggered.

-    The UE accesses to the target eNB and completes the handover procedure by sending RRCConnectionReconfigurationComplete message to target eNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure.

-    When initial CHO execution attempt fails or HO fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

DL MIMO efficiency enhancements for LTE


MIMO is an effective technique to improve spectral efficiency and increase overall network capacity. SRS can be utilized to improve DL MIMO performance, especially for massive MIMO in TDD. In release-16 SRS capacity and coverage are enhanced by introducing more than one SRS symbol in a UL normal subframe and introducing virtual cell ID for SRS.

More than one symbol for SRS in a UL normal subframe

With the introduction of more than one SRS symbol in a UL normal subframe, the SRS capacity and coverage can be increased. These additional SRS symbol(s) are referred to as trigger type 2 SRS.

1 to 13 symbols of the first 13 symbols of a UL normal subframe can be configured to a UE for aperiodically triggered SRS transmission. Intra-subframe repetition, frequency hopping and antenna switching of the additional SRS symbols can be supported. A guard period of one SC-FDMA symbol can be configured for frequency hopping and antenna switching.

The number of repetitions can be configured from the set {1, 2, 3, 4, 6, 7, 8, 9, 12, 13}. If a UE has more receive antennas than transmit chains (e.g. 1T2R), the UE can be configured to transmit the additional SRS with antenna switching. And a UE can additionally be configured with frequency hopping for the additional SRS. The number of antennas (pairs) to switch is:

-    2 for 1T2R, or the number of pairs is configured as 2 for 2T4R

-    3 if the number of pairs is configured as 3 for 2T4R

-    4 for 1T4R

Both legacy SRS and additional SRS can be configured to the same UE, and transmission of legacy SRS and additional SRS symbol(s) in the same subframe for the UE is supported.

For sequence generation, per-symbol group hopping and sequence hopping are supported.

Independent open loop and close loop power control is supported for additional SRS, and DCI formats 3/3A/3B are used for close loop power control.

UEs not configured with SPUCCH/SPUSCH are not expected to be triggered with additional SRS in the same subframe as PUSCH/PUCCH in the same serving cell. UEs configured with SPUCCH/SPUSCH drop the SRS transmission in the symbols colliding with SPUCCH/SPUSCH in the same serving cell.

The additional SRS transmission in the symbols colliding with PUSCH/PUCCH of another serving cell in the same TAG, the same band and with the same CP, is dropped.

The additional SRS transmission in the symbols colliding with PUSCH/PUCCH of another serving cell in the different TAG is dropped if the total transmission power exceeds the PCMAX in any overlapping portion.

Virtual cell ID

Virtual cell ID within the range from 0 to 503 can be configured for SRS to increase SRS capacity.

The virtual cell ID can be configured to only additional SRS symbol(s) or both legacy and additional SRS symbol(s). If virtual cell ID is not configured, the physical cell ID is used.

Optimisations of UE radio capability signalling


UE Radio Capability ID

UE Capability Segmentation

Background

With the increase in the size of UE radio capabilities driven by additional supported bands, the size of the UE Radio Capabilities will significantly grow from Rel-15 onwards, therefore an efficient approach to signal UE Radio Capability information was needed.

UE Radio Capability ID

The system optimisations for the 5GS (documented in TS 23.501) and for the EPS (documented in TS 23.401), that apply to both NR and E-UTRA, but not NB-IoT, consisting of using UE Radio Capability IDs as an alternative to signaling the UE Radio Capabilities container in system procedures:

-  between the UE and the CN (over Uu)

- between the CN and the RAN (impacting N2/S1 interfaces)

-  within the RAN in e.g. the handover procedures (impacting Xn/X2/S1/N2 interfaces)

-  within the CN.

The UE Radio Capability ID format is defined in TS 23.003. The UE Radio Capability ID is signaled by the UE in NAS as specified in TS 24.501 for the 5GS and as specified in TS 24.301 for the EPS. Two possible options for the assignment of UE Radio Capability ID exist:

-  Manufacturer-assigned: The UE Radio Capability ID may be assigned by the UE manufacturer in which case it includes a UE manufacturer identification (i.e. a Vendor ID). In this case, the UE Radio Capability ID uniquely identifies a set of UE radio capabilities for a UE by this manufacturer in any network.

-  Network-assigned: If a manufacturer-assigned UE Radio Capability ID is not used by the UE or the serving network, or it is not recognised by the serving network’s UE Capability Management Function (UCMF), the UCMF may allocate UE Radio Capability IDs for the UE corresponding to each different set of UE radio capabilities which the network may receive from the UE at different times. In this case, the UE Radio Capability IDs which the UE receives are applicable to the serving network and uniquely identify the corresponding sets of UE radio capabilities in this network. The network-assigned UE Radio Capability ID includes a Version ID in its format. The value of the Version ID is the one configured in the UCMF, at the time when the UE Radio Capability ID value is assigned. The Version ID value makes it possible to detect whether a UE Radio Capability ID is current or outdated.

 

UE Radio Capability IDs and the mapping to the corresponding UE radio capabilities are stored in a new function called the UE Capability Management Function (UCMF) in the CN. The UCMF is used for:

- storage of dictionary entries corresponding to either Network-assigned or Manufacturer-assigned UE Radio Capability IDs.

- assigning Network-assigned UE Radio Capability ID values.

-  provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF performed from an AF that interacts with the UCMF either directly or via the NEF/SCEF (or via Network Management).

    

UCMF architecture and related reference points in 5GS (left) and EPS (right)
UCMF architecture and related reference points in 5GS (left) and EPS (right)

System procedures are defined for 5GS in TS 23.502 and for EPS in TS 23.401.

UE Capability Segmentation

The RAN work item [10] calls for specification of a segmentation mechanism, so that in cases of excessively large UE capability signalling (e.g. capability information messages exceeding the maximum size of a PDCP SDU), the capability can be segmented into multiple RRC messages.  Segmentation applies to both NR and E-UTRA.

Segmentation is performed in the RRC protocol layer, with a separate RRC PDU for each segment.  The UE encodes the capability information message, then divides the encoded message into segments such that the size of each segment does not exceed the maximum size of a PDCP SDU (8188 octets in E-UTRA, 9000 octets in NR); the RAN node (eNB or gNB) receives the segments and reassembles them to reconstruct the original capability information message.  Segmentation is applied only in case the size of the encoded capability information message exceeds the maximum size of a PDCP SDU.  The signalling formats support up to 16 segments for a single capability information message.

Sunday, November 15, 2020

LTE in high speed


 In Rel-13 and 14, the mobility and throughput performance were enhanced to cover high speeds (up to 350 km/h) by specifying the requirements for UE RRM, UE demodulation and base station demodulation, considering the two types of operator’s practical deployments shown in Figures 1 and 2. Figure 1 shows the case where no specific installation is deployed to handle high-speed trains, i.e. UEs in the train use the "standard" LTE eNBs. Alternatively, figure 2 shows the case where Single Frequency Network (SFN) are deployed. SFNs use so-called "Remote Radio Heads" (RRH), which are dedicated antennas deployed along the train track. In this case, the baseband unit (BBU) is connected to the RRH, e.g. using fiber.

Non-Single Frequency Network (SFN) high speed scenario
Fig.1: Non-Single Frequency Network (SFN) high speed scenario


 

SFN high speed scenario
Fig2: SFN high speed scenario

These Rel-13 and 14 enhancements were conducted both for non-SFN and for SFN, but only for LTE single carrier, i.e. not covering Carrier Aggregation (CA).

Rel-16 improves the mobility and throughput performance, now considering CA and speeds up to 500 km/h. To this aim, it enhances RRM, UE demodulation and base station demodulation: it specifies enhanced RRM core requirements and corresponding RRC signals in respectively TS 36.133 and TS 36.331.

 

RRM requirements enhancements:

In Release 14 cases (limited to 350 km/h and single carrier), the latency requirements under DRX configuration up to 1.28s DRX cycle were enhanced by reducing the cell identification delay in connected mode and cell reselection delay in idle mode [1].

In Rel-16, considering Carrier Aggregation and speeds up to 500km/h, the following enhanced requirements were introduced to achieve good mobility performance and less paging outage:

1.    Enhanced RRM requirements for active SCells (for 350km/h velocity)The same requirements specified in Rel-14 high speed WI are applied to active SCells.

2. Enhanced RRM requirements for deactivated SCells (for 350km/h velocity)The cell identification delay and measurement period are reduced.

3.  Enhanced RRM requirements in DRX in connected mode (for 500km/h velocity):  The cell identification delay and measurement period on 1.28s DRX cycle are further reduced from those in Rel-14 high speed WI.

4.      Enhanced RRM requirements in idle mode (for 500km/h velocity)The cell detection delay is further reduced from those in Rel-14 high speed WI.

5.    Enhanced UL timing adjustment requirements in connected mode (for 500km/h velocity)The larger maximum autonomous time adjustment step is applied when the downlink bandwidth is wider than 10MHz.

 

Demodulation enhancements

6.      For UE and base station demodulation enhancements: In Release 14, UE and base station demodulation requirements were enhanced, for both cases of operator’s practical deployments shown in figures 1 and 2.

In Release 16, regarding the CA case in SFN (figure 2), the requirements specified in Rel-14 are expanded to Dual Connectivity's Secondary Cells (SCells) as defined in TS 36.331. Regarding further high speed up to 500 km/h, additional requirements are introduced to ensure the PDSCH/PUSCH/PRACH demodulation performance with larger Doppler shift.

Architecture enhancements for 3GPP support of advanced V2X services


Architecture enhancements to the 5G System are specified in TS 23.287 in order to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, over the following reference points, based on service requirements defined in TS 22.185 and TS 22.186:

- PC5 reference point: NR PC5 RAT, LTE PC5 RAT.

- Uu reference point: NR, E-UTRA.

Interworking between EPS V2X and 5GS V2X is also specified.

The following architectural reference models are specified:

-  5G System architectures for V2X communication over PC5 and Uu reference points

-  5G System architecture for AF-based service parameter provisioning for V2X communications

-  Architecture reference model for interworking with EPS V2X

The various parameters for V2X communications over PC5 and Uu reference points are specified and these parameters may be made available to the UE in following ways:

-  pre-configured in the ME; or

-  configured in the UICC; or

-  preconfigured in the ME and configured in the UICC; or

-  provided/updated by the V2X Application Server via PCF and/or V1 reference point; or

-  provided/updated by the PCF to the UE.

In addition to PCF initiated Policy Provisioning procedure, the UE may perform UE triggered Policy Provisioning procedure to the PCF when the UE determines the V2X Policy/Parameter is invalid (e.g. Policy/Parameter is outdated, missing or invalid).

Regarding V2X communication over PC5 reference point, two types of PC5 reference points exist: the LTE based PC5 reference point as defined in TS 23.285, and the NR based PC5 reference point as defined in TS 23.287. A UE may use either type of PC5 or both for V2X communication depending on the services the UE supports. The V2X communication over PC5 reference point supports roaming and inter-PLMN operations. V2X communication over PC5 reference point is supported when UE is "served by NR or E-UTRA" or when the UE is "not served by NR or E-UTRA".

V2X communication over NR based PC5 reference point supports broadcast mode, groupcast mode and unicast mode. For unicast mode, Layer-2 link establishment, Link identifier update, Layer-2 link release, Layer-2 link modification and Layer-2 link maintenance procedures are specified. Per-Flow PC5 QoS Model is introduced for V2X communication over NR based PC5 reference point.

Architecture enhancements for EPS to support V2X communication over NR PC5 reference point are specified in TS 23.285 [4].

For V2X communication over Uu reference point, only unicast is supported. Latency reduction for V2X message transfer via unicast may be achieved by using various mechanisms, including via e.g., edge computing defined in TS 23.501.

Notification on QoS Sustainability Analytics to the V2X Application Server is specified so that the V2X Application Server may request notifications on QoS Sustainability Analytics for an indicated geographic area and time interval in order to adjust the application behaviour in advance with potential QoS change.

To support V2X applications that can operate with different configurations (e.g. different bitrates or delay requirements), the V2X Application Server, acting as the Application Function, can provide, in addition to the requested level of service requirements, Alternative Service Requirements to the 5G System. This enables the 5G System to act on the Alternative Service Requirements and apply them for the extended NG-RAN notification (i.e. Alternative QoS Profiles are provided from SMF to NG-RAN), as described in TS 23.501 and TS 23.503.

In order to facilitate deployment of dedicated network slice for use of, for example, automotive industry and to facilitate roaming support, a new standardized Slice/Service Type (SST) value dedicated for V2X services, i.e. 4 is defined in TS 23.501.

Security aspects of 3GPP support for advanced V2X services are specified in TS 33.536.

 TS 24.587 and TS 24.588 are new specifications for V2X .

MTC enhancements for LTE - Rel 16


Release 16 adds on the LTE features for Machine-Type Communications (MTC) introduced in earlier releases (e.g. low-complexity UE categories M1 and M2, and Coverage Enhancement Modes A and B) by further improving network operation and efficiency in a range of areas.

All New features are optional for the UE and can be supported by Cat-M1 and Cat-M2 and by normal LTE UEs supporting CE mode unless explicitly specified. All features are applicable to both CE modes (A and B) in all duplex modes (HD-FDD, FD-FDD, and TDD) unless otherwise stated.

Improved DL transmission efficiency and UE power consumption

Reduced UE power consumption is achieved through reduced downlink monitoring and reduced signalling, building on features introduced in earlier releases.

              UE-group wake-up signals (GWUS): Reduced UE power consumption in idle mode was enabled in Rel-15 by the introduction of the wake-up signal (WUS), a compact signal transmitted a configurable time before the paging occasion (PO) when a UE is being paged, allowing the UE to maximize its sleep time during periods when there is no paging. In Rel-16, an enhancement is introduced that allows a WUS to wake up a configurable group of UEs rather than all UEs that happen to monitor the same PO. This helps reduce the power consumption even further. The mapping of GWUS in the time and frequency domains is highly configurable.

              Mobile-terminated early data transmission (MT-EDT): For scenarios where the UE only needs to transmit a small amount of data, the early data transmission (EDT) feature in Rel-15 enables the UE to transmit up to (slightly more than) 100 bytes of data already in Msg3 during the random-access procedure, and to receive data already in Msg4. If needed, eNB can order fallback to legacy random-access procedure during the EDT procedure. In Rel-16, an enhancement is introduced that allows not only mobile-originated (MO) EDT access but also mobile-terminated (MT) EDT. When the MME triggers MT-EDT, an indication is included in the paging message, after which the UE triggers random access to resume the connection (in case the UP CIoT EPS optimization is used) or initiate MO-EDT (in case the CP CIoT EPS optimization is used). MT traffic is received in Msg4. MT-EDT is only supported when UE is connected to EPC (not 5GC).

  Improved DL quality reporting: Legacy CE mode A supports both periodic and aperiodic CSI reporting which can be used to assist PDSCH link adaptation. In Rel-16, a new type of DL quality reporting is introduced which reflects MPDCCH quality rather than PDSCH quality. The report represents the required number of MPDCCH subframe repetitions for reliable MPDCCH reception. It can be sent in connected mode, but it can also be sent already in Msg3 during the random access procedure, which means that the report can be used for guiding the UE-specific MPDCCH configuration, which helps optimize power consumption, latency, and spectral efficiency.

 MPDCCH performance improvement: In legacy LTE-MTC, MPDCCH demodulation is DMRS-based. With this feature, the UE can use a combination of DMRS and CRS for MPDCCH demodulation to improve the MPDCCH performance. The feature takes the configured DMRS-to-CRS power ratio into account. The feature can be used for transmissions in idle mode and/or connected mode. In idle mode, the DMRS-to-CRS mapping is based on precoder cycling, whereas in connected mode, it can be configured to be precoder cycling based, CSI-based, or (in case of TDD) reciprocity-based.

Preconfigured uplink resources (PUR)

In Rel-15, signalling overhead and power consumption reductions were introduced by the (mobile-originated) early data transmission (EDT) feature, where data can be transmitted already in Msg3 during the random-access procedure.

In Rel-16, the earlier transmission of UL data payload has been further enhanced by introducing UL transmission using preconfigured uplink resources (PUR). When the feature is configured, both the random-access preamble transmission (Msg1) and the random-access response (Msg2) can be omitted, and the data transmission can be completed in only two messages (i.e., Msg3 and Msg4).

The UE is configured with PUR via dedicated RRC signaling while in connected mode. Configuring a UE with PUR can be triggered by the network or requested by the UE. Before performing a PUR transmission, the UE must evaluate the validity of the timing advance (TA) based on either individual or combined usage of any of the following attributes: a) serving cell change, b) TA timer, c) RSRP change. Additionally, it is possible to configure the TA as always valid within a given cell.

There are two schemes for transmitting using PUR, dedicated PUR and shared PUR, the latter allows up to two users to transmit simultaneously when the number of PUSCH repetitions is greater than or equal to 64 for full-PRB allocation.

Scheduling of multiple transport blocks

In legacy LTE-MTC operation, each DCI carried by MPDCCH schedules a single PDSCH or PUSCH transport block (TB). In Rel-16, a possibility to schedule multiple TBs using a single is introduced. This can help improve the resource utilization by reducing the number of physical resource blocks (PRBs) spent on MPDCCH transmission and the number of subframes spent on guard time for DL-to-UL and UL-to-DL transition (in half-duplex FDD operation).

 Unicast multi-TB scheduling: When the feature is configured, a single DCI can schedule multi TBs for PDSCH or PUSCH (up to 8 TBs in CE mode A, or up to 4 TBs in CE mode B). The number of TBs is dynamically controlled by the DCI. The TBs can be configured to be transmitted consecutively or subframe interleaved (in case of subframe repetition). For PDSCH multi-TB scheduling, HARQ-ACK bundling can optionally be used to improve the resource utilization further for UEs in good coverage. For PUSCH multi-TB scheduling, early termination of the PUSCH transmission is supported through indication of positive HARQ-ACK in the DCI.

  Multicast multi-TB scheduling: When the feature is configured a single DCI can schedule up to 8 TBs for PDSCH for a SC-MTCH, with configurable time gaps between the TBs if desired. The number of TBs is dynamically controlled by the DCI.

CE mode improvements for non-Cat-M UEs

The features in this work item can be supported both by Cat-M UEs and non-Cat-M UEs that support CE mode A or B. In addition, the following features have been specified specifically for non-Cat-M UEs that support CE mode A or B.

 Enhancements to idle mode mobility: A possibility is introduced for a non-Cat-M UE in a non-standalone LTE-MTC cell to use enhanced coverage functionality to camp in the cell even if the S-criterion indicates that the UE is in normal coverage. This functionality is enabled/disabled by a configuration provided in SIB1. (This is the default behavior for the standalone LTE-MTC case described in the next section in this document.)

  CSI feedback based on CSI-RS: In legacy CE mode A, periodic and aperiodic CSI feedback is based on up to 4 CRS antenna ports. This feature introduces support for periodic CSI feedback based on 8 CSI-RS antenna ports in TM9 for non-Cat-M UEs in CE mode A. The feature can help improve the DL link adaptation and hence the DL performance. As a separate UE capability, the feature can also optionally be supported in combination with codebook subset restriction.

  ETWS/CMAS in connected mode: In legacy LTE-MTC, ETWS/CMAS notification indication is supported using DCI format 6-2 in MPDCCH common search space Type-1 in idle mode. This feature introduces ETWS/CMAS notification indication using DCI format 6-1A/B in MPDCCH common search space Type-0 in connected mode for non-Cat-M UEs in CE mode A/B. This means that a UE can be notified without releasing the UE to idle mode.

Stand-alone deployment

In legacy LTE-MTC operation, the first few OFDM symbols in each DL subframe are unused by LTE-MTC since they are assumed to be occupied by LTE control channels for normal LTE UEs (PCFICH, PDCCH, PHICH). This feature enables transmission of MPDCCH and/or PDSCH to UEs in CE mode A/B in the “LTE control channel region” on carriers that are not used for normal LTE. The feature can be used for transmissions in idle mode and/or connected mode. The potential DL transmission efficiency gain is about 14% (corresponding to 2 out of 14 OFDM symbols) for 1.4 MHz carriers and about 7% (corresponding to 1 out of 14 OFDM symbols) for wider carriers.

Mobility enhancements

In Rel-15, two new LTE-MTC signals were introduced, the resynchronization signal (RSS) and the wake-up signal (WUS), and in Rel-16 the following mobility enhancements are introduced which make use of the Rel-15 signals.

 RSS-based measurements: In Rel-15, support for a resynchronization signal (RSS) was introduced and its configuration is provided by the serving cell. In Rel-16, signaling of RSS configurations for neighbor cells is introduced. Both broadcasted and dedicated signaling can be used to provide the configurations. The primary purpose of RSS is to improved synchronization performance, but with the Rel-16 signaling, the UE may also use RSS for improved measurement performance for intra-frequency RSRP measurements for neighbor cells in both idle and connected mode.

  RRM measurement relaxation: The legacy LTE-MTC UE behavior requires the UE to measure on the serving cell and evaluate the cell selection criterion at least every DRX cycle. The wake-up signal (WUS) introduced in Rel-15 would allow the UE to sleep for multiple paging cycles and wake up to receive paging after a configurable time duration, but the UE power saving gain from WUS cannot be fully utilized since the UE is still required to wake up for measurements. Therefore, an RRM measurement relaxation is introduced in Rel-16, which allows the UE meet the requirements using a longer measurement cycle to save power, where the cycle is configurable under certain conditions.

Performance improvement for NR coexistence

Spectrum sharing with legacy (Rel-13/14/15) LTE-MTC is already supported in Rel-15 NR, and the RF coexistence aspects described in TR 37.823. The following features are introduced in Rel-16 LTE-MTC in order to further improve the performance of the coexistence with NR.

  DL/UL resource reservation: Legacy LTE-MTC supports configuration of invalid DL/UL subframes, which can be used in order to avoid mapping LTE-MTC transmissions to subframes that are needed for NR transmissions. Rel-16 takes a step further by introducing finer-granularity LTE-MTC resource reservation in both the time domain (with subframe, slot, or symbol level granularity) and the frequency domain (with LTE RBG level granularity) for unicast MPDCCH/PDSCH/PUSCH/PUCCH transmissions in connected mode in CE mode A/B. The resource reservation patterns are configurable using parameter combinations based on bitmaps, periodicities and offsets. For PDSCH/PUSCH, the DCI can indicate that the resource reservation should be overridden, in which case the PDSCH/PUSCH transmission becomes continuous.

 DL subcarrier puncturing: In order to achieve PRB alignment between LTE-MTC and NR, a possibility to puncture 1 or 2 DL subcarriers at the lower or higher edge of each 6-PRB narrowband is introduced. The puncturing affects MPDCCH/PDSCH transmissions in connected mode in CE mode A/B. The performance loss from the puncturing should typically be insignificant.

Connection to 5GC

In Rel-16, support for connecting LTE-MTC UEs to 5GC is introduced. It resembles the Rel-15 functionality for connecting LTE UEs to 5GC. The RRC_INACTIVE state is supported and additionally the User Plane CIoT 5GS optimisation is supported in RRC_IDLE (similar to the corresponding EPC feature). Some features, such as EDT and PUR are supported only in RRC_IDLE using the UP-optimisation solution and are not supported in RRC_INACTIVE. Long extended DRX in RRC_IDLE is supported, and RAN paging cycles of 5.12 s and 10.24 s are supported in RRC_INACTIVE.

Saturday, November 7, 2020

Enhancements of Public Warning System - Rel 16


The ePWS feature enhances the Public Warning System by defining behaviours for UEs with no user interface or with a user interface that is incapable of displaying text-based Warning Notifications and providing how to improve the comprehension of a Warning Notification to users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies and users who are not fluent in the language of the Warning Notifications. In addition, additional requirements are specified for PWS-UEs and ePWS-UEs that play the role of a relay UE or a remote UE to conform behaviours when receiving a Warning Notification via the relay functionality. The requirements can be found in 3GPP TS 22.268 [1] and corresponding solutions in 3GPP TS 23.041 [2].

 

Additional requirements for an enhanced Public Warning System (ePWS) are specified as an update to Technical Specification (TS) 22.268 [1].

3GPP Public Warning Systems were first specified in Release 8, allowing for direct warnings to be sent to mobile users on conventional User Equipment (PWS-UE), capable of displaying a text-based and language-dependent Warning Notification.

Since that time, there has been a growth in the number of mobile devices with little or no user interface - including wrist bands, sensors and cameras – many of which are not able to display Warning Notifications. The recent growth in the number of IoT devices - not used by human users – also highlights the need for an alternative to text based Warning Notifications. If those devices can be made aware of the type of incident (e.g. a fire or flood) in some other way than with a text message, then they may take preventive actions (e.g. lift go to ground floor automatically).

The ePWS feature also specifies how graphical symbols or images can now be used to better disseminate Warning Notifications, specifically aimed at the following categories of users:

-    Users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies; and

-    Users who are not fluent in the language of the Warning Notifications.

Much of the work on enhancing the Public Warning System is set out in the ePWS requirements in 3GPP TS 22.268 [1] and in ePWS protocol solutions in 3GPP TS 23.041 [2] in Release 16, covering:

-    Specifying Message Identifiers for ePWS-UE, especially IoT devices that are intended for machine type communications

-    Enabling language-independent content to be included in Warning Notifications

The work on ePWS in 3GPP TS 22.268 [1] and 3GPP TS 23.041 (Release 16) is expected to help manufacturers of User Equipment meet any future regulatory requirements dedicated to such products.

Requirements defined for PWS-UEs in clause 4 of 3GPP TS 22.268 [1] are applicable for ePWS-UEs unless dedicated ePWS-UE requirements described in clause 9 of 3GPP TS 22.268 [1] supersede them.

 

References

[1] TS 22.268, Public Warning System (PWS) requirements

[2] TS 23.041, Technical realization of Cell Broadcast Service (CBS)

Release 16 enhancements for NB-IoT


This Feature builds on the base NB-IoT feature in Rel-13, and enhancements in Rel-14 and Rel-15, and adds features such as DL/UL transmission efficiency improvement, UE power consumption improvement, scheduling enhancement, network management tool enhancement, latency improvement, enhancement on coexistence with NR and connection to 5GC. 

Improved DL transmission efficiency and UE power consumption

Reduced UE power consumption and improved transmission efficiency are achieved through reduced downlink monitoring and reduced signalling, building on features introduced in earlier releases.

UE-group wake-up signals (GWUS) (FDD):

With the introduction of Rel-15 wake-up signalling (WUS), UE can skip the paging procedures if the wake-up signal is not detected to save power. This feature (UE-group WUS) allows eNB to transmit a UE-group WUS to instruct the UEs in the group that they must monitor NPDCCH for paging. This allows the UE to skip the paging procedures to save more power if eNB sends UE-group WUS to UEs in other groups. The UEs are grouped according to their paging probability and/or their UE ID based on system information configuration.

Mobile-terminated early data transmission (MT-EDT) (FDD):

Rel-15 Mobile Originating Early Data Transmission (MO-EDT) allows one uplink data transmission optionally followed by one downlink data transmission during the random access procedure, avoiding transition to RRC_CONNECTED mode. Rel-16 Mobile Terminating Early Data Transmission (MT-EDT) allows one downlink data transmission during the random access procedure triggered in response to a paging message. This feature allows the eNB to decide whether to initiate Mobile Terminated EDT procedures towards the UE based on the data size received from the core network. Mobile Terminating Early Data Transmission (MT-EDT) is only supported in EPC.

Support for Preconfigured uplink resources (PUR) in idle mode (FDD)

In Rel-15, signalling overhead and power consumption reductions were introduced by the (mobile-originated) early data transmission (EDT) feature, where data can be transmitted already in Msg3 during the random-access procedure.

In Rel-16, the earlier transmission of UL data payload has been further enhanced by introducing UL transmission using preconfigured uplink resources (PUR). This feature allows eNB to configure uplink resources, in which a UE in IDLE mode can send UL transmission without performing random access procedures. The UE can be potentially configured with a cyclic shift of DMRS, which allows sharing of the preconfigured resources under which up to two users can transmit NPUSCH simultaneously when the NPUSCH transmission is larger than or equal to 64ms for 12-tone allocation. By skipping the random access procedures, the uplink transmission efficiency can be improved and UE power consumption is reduced. Before performing a PUR transmission, the UE must evaluate the validity of the timing advance (TA) based on either individual or combined usage of any of the following attributes: a) serving cell change, b) TA timer, c) RSRP change. Additionally, it is possible to configure the TA as always valid within a given cell.

Scheduling of multiple DL/UL transport blocks with single DCI (FDD)

This feature allows the scheduling of up to two transport blocks (TB) with a single DCI for uplink or downlink unicast transmission, where the number of TBs is indicated by DCI. The transmission of multiple TBs can be configured to be contiguous or interleaved. And HARQ bundling can be potentially configured when transmission is configured as interleaved. It also allows the scheduling of up to eight transport blocks with a single DCI for SC-MTCH, where the number of TBs is indicated by DCI. The DCI overhead can be reduced for contiguous UL/DL transmissions.

Network management tool enhancements - SON (FDD and TDD)

Rel-16 introduces SON features: RACH report, RLF report and ANR for network resource optimisation. The ANR measurements are performed when the UE is in RRC_IDLE and reported next time the UE enters RRC_CONNECTED.  The NPRACH configuration of the NB-IoT Cells are exchanged between neighbour eNBs for RACH optimization. And the RLF report from UE is forwarded to the old eNB to determine the nature of the failure.

SON features are only supported in EPC.

Improved multicarrier operations - Quality report in Msg3 and connected mode (FDD)

In cells with interference, the coverage level corresponding to the estimate RSRP may be mismatched with the channel quality. This feature allows the eNB to configure a UE in IDLE mode to report the downlink channel quality in Msg3 for non-anchor access. It also allows the UE to report the downlink channel quality in connected mode other than Msg3 for anchor and non-anchor carriers. This allows the eNB to schedule NPDCCH and NPDSCH more accurately, especially in cases with mismatch between coverage level and channel quality.

Presence of NRS on a non-anchor carrier for paging (FDD)

This feature allows eNB to transmit NRS in subframes on a non-anchor carrier for paging even when no paging NPDCCH is transmitted. The NRS are present in the first M subframes out of the 10 NB-IoT DL subframes before the Paging Occasion (PO), where the PO can be a subset of POs or a whole set of POs, and the values of M depend on the value of nB as defined in TS 36.304.

When NRS is present on a non-anchor paging carrier and the conditions for NRSRP measurement on non-anchor carrier are met as defined in TS 36.133, the UE may perform serving cell measurements on the non-anchor paging carrier.

Mobility enhancements - Idle mode inter-RAT cell selection to/from NB-IoT (FDD and TDD)

With this feature, NB-IoT can provide assistance information for inter-RAT cell selection to E-UTRAN/GERAN and E-UTRAN can provide assistance information for inter-RAT cell selection to NB-IoT. A UE may use the assistance information provided by the network for cell selection to/from NB-IoT.

Improved latency - UE Specific DRX (FDD and TDD)

Rel-16 introduces support for UE specific DRX to reduce paging latency.  The eNB may broadcast a minimum UE specific DRX value shorter than the cell default DRX value.  When UE specific DRX is configured by the upper layers and the minimum UE specific DRX value is broadcast, the UE monitors paging according to the longer of the two values.

Coexistence of NB-IoT with NR (FDD and TDD)

This feature allows the configuration of the DL/UL resource reservation in subframe/slot/symbol-levels on non-anchor carriers for unicast transmission to avoid resource overlapping with NR channels/signals. The configuration can be for 10ms or 40ms duration, with a periodicity from {10ms, 20ms, 40ms, 80ms, 160ms} and a start position in a granularity of 10ms, which is independent from legacy configurations. It also allows dynamic indication whether the resource reservation is applied or not.

Three system scenarios have been studied and captured in TR 37.824:

             For NB-IoT operation in NR in-band, RB alignment, power boosting and numerologies have been addressed.

             For NB-IoT operation in NR guard band, RF requirements will not be specified.

             For NB-IoT standalone operation, based on coexistence study, it is concluded that there is no issue for NB-IoT standalone coexistence with NR.

Connection to 5GC (FDD and TDD)

Rel-16 introduces support for connection to 5GC reusing eLTE as a baseline, including Unified Access Control (UAC). RRC_INACTIVE, NR SDAP and NR PDCP are not supported and a maximum of two PDU sessions mapped to two default DRBs is supported.

Rel-16 also introduces support for the CIoT 5GS optimisation, in particular extended DRX (eDRX) in RRC_IDLE, control plane and user plane CIoT optimisation, MO-EDT for the control plane and user plane CIoT optimisation, RRC Connection Reestablishment for the control plane and restriction of use of Enhanced Coverage.

Similar backhaul signalling to support control plane and user plane CIoT optimisation are introduced over NG interface (between ng-eNB and AMF) and over Xn interface (between ng-eNBs), including e.g. early UE radio capability retrieval from core network after msg3, NB-IoT CP relocation procedures to support connection reestablishment, Paging assistance information exchanging, UE differentiation information exchanging, etc.